From: Raphael Jacquot <raphael.jacquot@imag.fr>
To: Brad Campbell <brad@wasp.net.au>
Cc: Neil Whelchel <koyama@firstlight.net>, linux-kernel@vger.kernel.org
Subject: Re: SATA Promise TX4 Crash
Date: Mon, 21 Mar 2005 10:42:17 +0100 [thread overview]
Message-ID: <423E96F9.2010301@imag.fr> (raw)
In-Reply-To: <423E70D7.8060707@wasp.net.au>
Brad Campbell wrote:
> Neil Whelchel wrote:
>
>> Hello,
>> I have two Promise SATA TX4 cards connected to a total of 6 Maxtor 250 GB
>> drives (7Y250M0) configured into a RAID 5. All works well with small
>> disk load, but when a large number of requests are issued, it causes
>> crash
>> similar to the attached, except that the errors before the crash are on a
>
>
>> EFLAGS: 00010046 (2.6.11.2)
>> EIP is at scsi_put_command+0xbb/0x100
>
>
> Oooh Oooh Oooh, pick me Mr Kotter!
> I have seen this repeatedly, fought it and "apparently" beat it by
> upgrading my PSU.
> I could reliably reproduce it by running a raid resync and issuing SMART
> queries
> to the drives, but after a PSU upgrade it has gone away.
> I have tried hard to reproduce it recently but I just can't get it to
> crash anymore.
>
> I have a similar setup 4x SATA-TX4 cards and 15x 7Y250M0 drives. I'm
> thought it was actually
> a bug, but as I can't reproduce it anymore it's making it a bit hard to
> track down.
>
> Not much help, sorry.
>
> Brad
I have similar crashes with a (netbooted) epia and 4 250G Seagate 7200.8
PATA drives.
removing the kernel preempt stuff & realtime scheduling and stuff
alleviates the issue a bit but it occured again yesterday.
a quirk in the epia forces me to reboot the box by power cycling it.
next prev parent reply other threads:[~2005-03-21 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 0:18 SATA Promise TX4 Crash Neil Whelchel
2005-03-21 6:59 ` Brad Campbell
2005-03-21 9:42 ` Raphael Jacquot [this message]
[not found] <1111898649.185617.170980@g14g2000cwa.googlegroups.com>
2005-03-27 22:17 ` Neil Whelchel
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=423E96F9.2010301@imag.fr \
--to=raphael.jacquot@imag.fr \
--cc=brad@wasp.net.au \
--cc=koyama@firstlight.net \
--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