From: Robert Hancock <hancockr@shaw.ca>
To: Fred Moyer <fred@redhotpenguin.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [2.6.21.1] SATA freeze
Date: Sat, 12 May 2007 12:48:59 -0600 [thread overview]
Message-ID: <46460C1B.6000609@shaw.ca> (raw)
In-Reply-To: <fa.zU1kuoSgByTYCYqY+iCQ5rMJy34@ifi.uio.no>
Fred Moyer wrote:
> I just joined the list today so apologies if this email breaks any email
> client post threading.
>
> I have been seeing similar errors on two different systems. I applied
> Robert's sata_nv patch posted to the list on May 5th, and approved today
> by Jeff Garzik. I've taken several steps to insure that this isn't a
> faulty cable or drive issue. This is running on a hp dl145g2. Here is
> my lspci, dmesg, and relevant kernel config sections:
(snip)
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata1.00: cmd b0/d2:f1:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data
> 123392 in
> res 50/00:f1:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM
> violation)
> ata1: soft resetting port
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: configured for UDMA/100
> ata1: EH complete
This appears to be a different problem. Something is issuing
SMART-related commands (smartd or smartctl perhaps) which the drive
seems to be reacting strangely to. It apparently completed the command
but never raised DRQ to request any data being transferred even though
we expected it to. Maybe SMART is disabled on the drive and that's
causing it to just toss these commands? CCing linux-ide in case anyone
knows what would cause this.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-05-12 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.zU1kuoSgByTYCYqY+iCQ5rMJy34@ifi.uio.no>
2007-05-12 18:48 ` Robert Hancock [this message]
2007-05-12 19:09 ` [2.6.21.1] SATA freeze Fred Moyer
2007-05-13 1:02 ` Robert Hancock
2007-05-13 1:52 ` Fred Moyer
2007-05-13 1:20 ` Robin H. Johnson
2007-05-13 18:18 ` Jim Paris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46460C1B.6000609@shaw.ca \
--to=hancockr@shaw.ca \
--cc=fred@redhotpenguin.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).