From: Fred Moyer <fred@redhotpenguin.com>
To: Robert Hancock <hancockr@shaw.ca>
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:09:43 -0700 [thread overview]
Message-ID: <464610F7.6030202@redhotpenguin.com> (raw)
In-Reply-To: <46460C1B.6000609@shaw.ca>
Robert Hancock wrote:
> 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.
Here's smartctl -a for this drive - same output for both sda and sdb.
Smartd is currently running. Any advice appreciated.
Previously on 2.6.15 I was seeing sdb remount as readonly under heavy
i/o. I have not seen that issue yet with 2.6.21 (with Robert's patch
from May 5th for sata_nv), but that occurrence of remounts read-only was
infrequently, so that issue may be solved.
app2 ~ # smartctl -a /dev/sda
smartctl version 5.36 [x86_64-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
Device: ATA ST3808110AS Version: n/a
Serial number: 5LR8895K
Device type: disk
Local Time is: Sat May 12 12:05:58 2007 PDT
Device does not support SMART
Error Counter logging not supported
[GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on']
Device does not support Self Test logging
app2 ~ # ps aux | grep smart
root 5227 0.0 0.0 2892 672 ? S May11 0:00
/usr/sbin/smartd -p /var/run/smartd.pid
root 19510 0.0 0.0 2648 648 pts/0 S+ 12:07 0:00 grep
--colour=auto smart
next prev parent reply other threads:[~2007-05-12 19:09 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 ` [2.6.21.1] SATA freeze Robert Hancock
2007-05-12 19:09 ` Fred Moyer [this message]
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=464610F7.6030202@redhotpenguin.com \
--to=fred@redhotpenguin.com \
--cc=hancockr@shaw.ca \
--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).