From: Gunnlaugur Thor Briem <gthb@hi.is>
To: Ryan Verner <xfesty@computeraddictions.com.au>
Cc: LinuxSA ML <linuxsa@linuxsa.org.au>, linux-kernel@vger.kernel.org
Subject: Re: Promise PDC20269 (Ultra133 TX2) + Software RAID
Date: Tue, 03 Feb 2004 09:07:31 +0000 [thread overview]
Message-ID: <401F64D3.90501@hi.is> (raw)
In-Reply-To: <E9A39380-560F-11D8-8E3C-000A95CEEE4E@computeraddictions.com.au>
Ryan Verner wrote:
> On 03/02/2004, at 2:08 PM, Ryan Verner wrote:
>
>> And the machine is randomly locking up, and of course, on reboot, the
>> raid array is rebuilt. Ouch. Any clues as to why? I'm sure the
>> hard drive hasn't failed as it's brand new; I suspect a chipset
>> compatibility problem or something.
>
>
> Definitely seems to be this. Swapped the drives back over to the
> onboard-IDE chipset, which is much slower (raid rebuilds at only
> 7MB/sec instead of 25), but certainly none of these problems.
>
> Known issue?
Yep: http://bugzilla.kernel.org/show_bug.cgi?id=1888
I'm getting this with the Promise 20376. Presumably not a hardware
problem: I can't reproduce it under Windows XP with Promise's supplied
Windows driver, and Jeff Garzik calls it a known bug -- "should have a
fix soon".
Jeff, is it "known" in the sense that you know roughly what goes wrong,
but just haven't gotten around to fixing it? I'd like to tinker and try
to fix it, but am "unfamiliar around those parts".
- Gulli
next prev parent reply other threads:[~2004-02-03 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 3:38 Promise PDC20269 (Ultra133 TX2) + Software RAID Ryan Verner
2004-02-03 6:12 ` Ryan Verner
2004-02-03 8:47 ` Pasi Kärkkäinen
2004-02-03 9:07 ` Gunnlaugur Thor Briem [this message]
2004-02-04 20:46 ` Pedro Larroy
2004-02-04 21:22 ` Andreas Steinmetz
2004-02-04 22:06 ` Bartlomiej Zolnierkiewicz
2004-02-04 22:41 ` Pedro Larroy
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=401F64D3.90501@hi.is \
--to=gthb@hi.is \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxsa@linuxsa.org.au \
--cc=xfesty@computeraddictions.com.au \
/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