From: Marc Bevand <bevand_m@epita.fr>
To: linux-ide@vger.kernel.org
Subject: Generic bug/race in the IDE/SATA code ?
Date: Mon, 4 Oct 2004 09:10:27 +0000 (UTC) [thread overview]
Message-ID: <cjr423$kjk$1@sea.gmane.org> (raw)
In-Reply-To: 20040915134543.GA23786@iah.epita.fr
On 2004-09-15, Marc Bevand <bevand_m@epita.fr> wrote:
| What the hell could be the problem on Paul's system and mine ?
| Both of us have a Tyan motherboard (but not the same model).
I realize our problem is very similar to this one (excerpt from
linux-x86_64 release notes):
Reports that dual Tyan S2885 and S2880 can lock up when multiple IDE channels
are stressed in parallel. "noapic" or "ideFOO=serialize" seems to work
around it. Andre Hedrick thinks it's a generic bug/race in the IDE code.
(appart the fact we are stressing SATA channels, and that "noapic"
does not work around the problem for me).
I have done an interesting experiment: conduct the exact same test
under another OS, FreeBSD/amd64 (5.2.1, SMP kernel). The result is
that it works perfectly: the Promise card outputs data at the
continuous rate of 210 MB/s and the system never locks up even after
25min of activity (while it takes about 30sec to happen under Linux).
So is this a generic bug/race in the Linux IDE/SATA code ?
--
Marc Bevand http://www.epita.fr/~bevand_m
Computer Science School EPITA - System, Network and Security Dept.
prev parent reply other threads:[~2004-10-04 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 21:14 libata problems with 66Mhz Promise SATA150 TX4 Paul Fisher
2004-09-14 18:03 ` Marc Bevand
2004-09-14 23:13 ` Jeff Garzik
2004-09-15 0:18 ` Andy Warner
2004-09-15 9:02 ` Marc Bevand
2004-09-15 13:08 ` Andy Warner
2004-09-15 13:45 ` Marc Bevand
2004-10-04 9:10 ` Marc Bevand [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='cjr423$kjk$1@sea.gmane.org' \
--to=bevand_m@epita.fr \
--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).