From: Jeff Garzik <jgarzik@pobox.com>
To: Atul Bhouraskar <atul.bhouraskar@acoustic-technologies.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: PROBLEM: dma timeout errors on reads and large writes (sata_vsc on kernel 2.6.9)
Date: Thu, 09 Dec 2004 01:58:02 -0500 [thread overview]
Message-ID: <41B7F77A.2080404@pobox.com> (raw)
In-Reply-To: <000501c4ddb2$b97cd660$0d65a8c0@SHARK>
Atul Bhouraskar wrote:
> Hi,
>
> I am building a linux-2.6.9 system with 4 250G SATA drives (using the
> intel GD31244 controller).
> I have compiled a monolithic kernel with Vitesse vsc SATA support, ACPI
> and APM have been turned off (see config at end of message).
> The kernel boots up properly and detects all drives correctly (see dmesg
> below).
> I can partition and initialize the drives without any problem (using
> cfdisk and mke2fs).
> I can read and write small files (<100MB) without any problem too.
>
> But when I try to use any of the drives with large files (more than a
> couple of GB), the process invariably hangs with the kernel spewing out
> ATA timeout and other errors (see log below). It usually needs a write
> of more than 5-6GB before it happens, but it usually occurs at around
> 50-100MB while reading. It is not possible to kill the hung process,
> though the rest of the system continues to be responsive. Any further
> access (even an 'ls') on *any* of the SATA drives usually instantly
> meets with the same fate.
>
> It can be reproduced in the following way:
I got a similar report via my employer as well. I don't think anybody
has really tested sata_vsc on the Intel controller, just the one that
Vitesse put out.
You don't happen to have a spare controller, do you?
Jeff
next prev parent reply other threads:[~2004-12-09 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 5:48 PROBLEM: dma timeout errors on reads and large writes (sata_vsc on kernel 2.6.9) Atul Bhouraskar
2004-12-09 6:58 ` Jeff Garzik [this message]
2004-12-09 22:47 ` Atul Bhouraskar
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=41B7F77A.2080404@pobox.com \
--to=jgarzik@pobox.com \
--cc=atul.bhouraskar@acoustic-technologies.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).