From: Nicholas Miell <nmiell@comcast.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: SATA timeouts with Seagate disk on VIA VT6420 controller
Date: Thu, 23 Feb 2006 00:56:15 -0800 [thread overview]
Message-ID: <1140684975.9471.3.camel@entropy> (raw)
In-Reply-To: <1140068654.3274.12.camel@entropy>
On Wed, 2006-02-15 at 21:44 -0800, Nicholas Miell wrote:
> >From time to time, I've been experiencing timeouts with my SATA disk (a
> Seagate ST3300831AS) attached to a VIA VT6420 controller on a VIA
> K8T800-based MSI motherboard. This has happened somewhat rarely on a
> variety of Fedora kernel versions.
>
> Basically, sometimes IO will get really slow and I'll start getting
> "ata1: command 0x35 timeout, stat 0x50 host_stat 0x4" in my logs, with
> the occasional "ata1: command 0x25 timeout, stat 0x50 host_stat 0x4" and
> "ata1: command 0xb0 timeout, stat 0x50 host_stat 0x0" thrown in for good
> measure.
>
> The disk (and/or controller) isn't unresponsive -- I can do a smartctl
> -a -d ata /dev/sda and it'll complete (eventually), and IO to the disk
> continues (very slowly), but it's generally unusable until the next
> reboot.
I actually managed to successfully unmount the filesystem and deactivate
the LVM volume group for once, which allowed me to remove and reload
sata_via, libata, sd_mod and scsi_mod.
After the drivers were reloaded, IO to the disk worked fine, which leads
me to think that sata_via and/or libata needs the ability to reset the
hardware when errors occur.
--
Nicholas Miell <nmiell@comcast.net>
prev parent reply other threads:[~2006-02-23 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 5:44 SATA timeouts with Seagate disk on VIA VT6420 controller Nicholas Miell
2006-02-23 8:56 ` Nicholas Miell [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=1140684975.9471.3.camel@entropy \
--to=nmiell@comcast.net \
--cc=jgarzik@pobox.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