linux-kernel - Re: What is HSM violation? Causing ata1.00 hard resetting link

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <AANLkTimvGbDNOTPeuH79ZnJMR14pv7ehQ8vZ3ib_eKrP@mail.gmail.com>
Date:	Thu, 17 Jun 2010 20:53:46 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Jeff Chua <jeff.chua.linux@...il.com>
Cc:	Jeff Garzik <jgarzik@...hat.com>, Greg KH <greg@...ah.com>,
	kristen.c.accardi@...el.com, Dely Sy <dely.l.sy@...el.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	lkml <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>, Matthew Wilcox <willy@...com>
Subject: Re: What is HSM violation? Causing ata1.00 hard resetting link

On Thu, Jun 17, 2010 at 8:33 PM, Jeff Chua <jeff.chua.linux@...il.com> wrote:
>
>
> On Fri, Jun 18, 2010 at 7:41 AM, Robert Hancock <hancockrwd@...il.com>
> wrote:
>>
>> On Thu, Jun 17, 2010 at 12:05 AM, Jeff Chua <jeff.chua.linux@...il.com>
>> wrote:
>>
>> > ata1.00: exception Emask 0x2 SAct 0x7 SErr 0x3000400 action 0x6
>> > ata1.00: irq_stat 0x44000008
>>
>> The controller is reporting a protocol violation in Serror, and the
>> IRQ status reports a taskfile error and unknown FIS received from the
>> device.
>>
>> What kind of external drive is this? Seems to me like either it's
>> doing something not quite kosher, or there's some other problem (maybe
>> the eSATA cable is bad, or it doesn't seat properly in the connector -
>> apparently that's not uncommon).
>
> ata1.00 is the internal AHCI connector [Intel Corporation 5 Series/3400
> Series Chipset 6 port SATA AHCI Controller (rev 06)] with a  [SAMSUNG
> MMDOE56GG5MXP-OVB rev 0 with f/w VBM1801Q] (256GB SATA) attached.
>
> The errors were pointing to ata1.00 and after the HSM violation appeared,
> the disk was no longer accessible.

OK, so it was the SSD that had the problem, not the eSATA drive.

It does seem like the drive did something the controller really didn't
like, though. Is there any firmware update available for the drive?

>
> The external e-SATA has a JMicro [JMicron JMB360 AHCI Controller (rev 02)]
> with the same model Samsung SSD attached.
>
> If I do a "sync" every 3 seconds, I don't see any error. I had seen this
> errors in the past doing tar to external USB2 disks ... and it could be the
> same problem but just didn't notice it before.
>
> Thanks,
> Jeff
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/