[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.1006171341420.8191@boston.corp.fedex.com>
Date: Thu, 17 Jun 2010 14:05:32 +0800 (SGT)
From: Jeff Chua <jeff.chua.linux@...il.com>
To: Robert Hancock <hancockrwd@...il.com>,
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: What is HSM violation? Causing ata1.00 hard resetting link
Hi,
I just got an external e-SATA hard disk, and I'm testing for backup.
When I tried to "tar" 90GB to it, it caused a HSM violation, and since
this
is the root file system, system is brain-dead. "Bus error" for every
command
issued!
Error is (typed as was captured in the screen) ...
ata1.00: exception Emask 0x2 SAct 0x7 SErr 0x3000400 action 0x6
ata1.00: irq_stat 0x44000008
ata1.00: cmd 60/30:00:37:b0:84/00:00:17:00:00/40 tag 0 ncq 24576 in
res 40/00:08:6f:b0:84/00:00:17:00:00/40 Emask 0x2 (HSM violation)
ata1.00: cmd 60/50:08:6f:b0:84/00:00:17:00:00/40 tag 1 ncq 40960 in
res 51/04:00:6f:b0:84/00:00:17:00:00/40 Emask 0x403 (HSM violation)
ata1.00: cmd 60/00:10:bf:b0:84/01:00:17:00:00/40 tag 2 ncq 131072 in
res 40/00:08:6f:b0:84/00:00:17:00:00/40 Emask 0x2 (HSM violation)
ata1: hard resetting link
ata1: softreset failed (device not ready)
ata1: hard resetting link
ata1: softreset failed (device not ready)
ata1: hard resetting link
ata1: link is slow to respond, please be patient (ready=0)
Running on SSD on Linux 2.6.35-rc3.
This does not happen all the time, but I've seen this if it's copying
intensively.
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/
Powered by blists - more mailing lists