From: Vasily Averin <vvs@sw.ru>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Tejun Heo <htejun@gmail.com>,
linux-ide@vger.kernel.org, j.e.van.grootheest@caiway.nl,
devel@openvz.org
Subject: Re: VIA VT6420: SATA disconnects
Date: Tue, 19 Jun 2007 15:14:04 +0400 [thread overview]
Message-ID: <4677BA7C.1060704@sw.ru> (raw)
In-Reply-To: <465694E4.9020601@pobox.com>
Jeff Garzik wrote:
> Vasily Averin wrote:
>> Jeff, Tejun,
>>
>> Our RHEL5-based OpenVZ linux kernel reports about SATA-related issues:
>> VIA VT6420 SATA RAID Controller on MSI motherboard, x86_64 kernel based on latest RHEL5 kernel,
>> On booting hardware initialized properly and all works fine some time, but then it detects timeout and disables devices. We have replaced SATA cables, but issue didn't go away and still present.
>>
>> I've googled and found similair bugreport in linux-ide@
>> http://www.mail-archive.com/linux-ide@vger.kernel.org/msg06011.html
>>
>> Are you know something about this issue? I've seen that you have fixed SATA reset procedure recently, probably this issue was fixed already?
>
> RHEL5 SATA is unfortunately way out of date :( The next RHEL5 update
> should include a boatload of fixes.
>
> Try running the latest upstream kernel (2.6.21.3 or 2.6.22-rc2-git7),
> and see if the problem is reproducible.
I've reproduced this issue. But on this kernel EH works well and node is still alive:
Linux version 2.6.22-rc4 (vvs@vvs.work.ve) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3)) #1 SMP Fri Jun 8 14:32:01 MSD 2007
...
hda: lost interrupt
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata1.00: cmd ca/00:78:30:1a:24/00:00:00:00:00/e2 tag 0 cdb 0x0 data 61440 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1: soft resetting port
ATA: abnormal status 0x7F on port 0x000000000001c007
ATA: abnormal status 0x7F on port 0x000000000001c007
ata1.00: qc timeout (cmd 0x27)
ata1.00: ata_hpa_resize 1: sectors = 156301488, hpa_sectors = 0
ata1.00: failed to set xfermode (err_mask=0x40)
ata1: failed to recover some devices, retrying in 5 secs
ata1: soft resetting port
ATA: abnormal status 0x7F on port 0x000000000001c007
ATA: abnormal status 0x7F on port 0x000000000001c007
ata1.00: qc timeout (cmd 0x27)
ata1.00: ata_hpa_resize 1: sectors = 156301488, hpa_sectors = 0
ata1.00: failed to set xfermode (err_mask=0x40)
ata1.00: limiting speed to UDMA/133:PIO3
ata1: failed to recover some devices, retrying in 5 secs
ata1: soft resetting port
ATA: abnormal status 0x7F on port 0x000000000001c007
ATA: abnormal status 0x7F on port 0x000000000001c007
ata1.00: qc timeout (cmd 0x27)
ata1.00: ata_hpa_resize 1: sectors = 156301488, hpa_sectors = 0
ata1.00: failed to set xfermode (err_mask=0x40)
ata1.00: disabled
ata1: EH complete
sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
You can find some additional details in bug #8650
http://bugzilla.kernel.org/show_bug.cgi?id=8650
thank you,
Vasily Averin
prev parent reply other threads:[~2007-06-19 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 7:41 VIA VT6420: SATA disconnects Vasily Averin
2007-05-25 7:48 ` Jeff Garzik
2007-05-25 10:14 ` Vasily Averin
2007-05-25 14:36 ` Jan Evert van Grootheest
2007-06-19 11:14 ` Vasily Averin [this message]
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=4677BA7C.1060704@sw.ru \
--to=vvs@sw.ru \
--cc=devel@openvz.org \
--cc=htejun@gmail.com \
--cc=j.e.van.grootheest@caiway.nl \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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).