From: Marc Bevand <bevand_m@epita.fr>
To: linux-ide@vger.kernel.org
Subject: Re: libata problems with 66Mhz Promise SATA150 TX4
Date: Tue, 14 Sep 2004 20:03:51 +0200 [thread overview]
Message-ID: <41473287.7050101@epita.fr> (raw)
In-Reply-To: <m34qm13m8h.fsf@zathras.nivin.org>
Paul Fisher wrote:
> We're experiencing failures on a Promise SATA150 TX4 when run at 66Mhz
> on either PCI-X bus on a Tyan S2882 (dual Opteron system). The
> problems manifest themselves rather quickly on an SMP-enabled kernel,
> and it takes a bit longer to kill a non-SMP kernel.
> [...]
> The only way we can get a stable system is to run the SATA150 TX4 off
> the 33Mhz PCI bus.
> [...]
> We've tested 2.6.8, 2.6.9-rc1, and 2.6.9-rc1-bk16.
> [...]
> CPU 0: Machine Check Exception: 4 Bank 4: b200000000070f0f
I have *exactly* the same problem (MCE b200000000070f0f, which indicates
a watchdog timer timeout), on the same hardware (Promise SATA150 TX4).
Like you, I get the problem only when using a 66MHz PCI bus (no problem
at 33MHz). Like you, the stack trace indicate the problem comes from
the Promise hardware. And like you the watchdog timeout is much harder
to reproduce with a non-SMP kernel.
Here is a short summary of my config:
- Dual Opteron 244
- Tyan S2885
- 4 x 133MHz/64-bit PCI-X slots
- 1 x 33MHz/32-bit PCI slot
- Promise SATA150 TX4,
running at either 66MHz (PCI-X slot), or 33MHz (PCI slot)
- 4 x Seagate 160Go 7200 RPM S-ATA Barracuda 7200.7
An easy way to reproduce the problem is to run 4 instances of 'dd' reading
from 4 disks at the same time. It is much harder to reproduce when reading
from 3 disks, and quasi-impossible to reproduce when reading from 2 disks.
I have tried kernels 2.6.5 and 2.6.9-rc1 (arch x86_64). I have tried the
latest BIOS for my motherboard, the latest BIOS for the Promise card, and
all the PCI-X slots of the motherboard.
It seems the Promise chip has some problems under high-load conditions:
the throughput I obtain when reading from 4 disks is 100 MB/s (at 33MHz)
and 215 MB/s (at 66MHz)...
I contacted the Promise support some months ago, but they "did not get
this issue before", and finally they told me they "do not support 64 bit
or even PCI-X slots [for this model]" :-/
Actually I would be very interested to know if *anybody* is successfully
using this card at 66MHz with 3 or 4 disks attached to it.
--
Marc Bevand http://www.epita.fr/~bevand_m
Computer Science School EPITA - System, Network and Security Dept.
next prev parent reply other threads:[~2004-09-14 18:11 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 [this message]
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 ` Generic bug/race in the IDE/SATA code ? Marc Bevand
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=41473287.7050101@epita.fr \
--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).