From: Fabien Penso <penso@linuxfr.org>
To: linux-scsi@vger.kernel.org
Subject: megaraid problem
Date: Sun, 28 Mar 2004 01:27:25 +0100 [thread overview]
Message-ID: <873c7id6sa.fsf@linuxfr> (raw)
Hi to everyone.
I have a megaraid raid card :
Vendor: MegaRAID Model: LD0 RAID5 52095R Rev: E
Type: Direct-Access ANSI SCSI revision: 02
We used to run 2.4.23 very well for a long time, but we need to upgrade
because of all the security problems (never too late :) to 2.4.25. I've
tried for days with no luck; booting gives us :
megarid: Waiting for 3 commands to flush: iter:1000
megarid: Waiting for 3 commands to flush: iter:2000
and so on. I tried to copy the megaraid2.c/megaraid2.h from 2.4.23 (who
knows...) but it doesn't work better.
I am out of ideas here, so I just wonder if someone has a solution.
Thanks.
next reply other threads:[~2004-04-05 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-28 0:27 Fabien Penso [this message]
2004-04-05 11:09 ` megaraid problem Fabien Penso
2004-04-05 11:11 ` Fabien Penso
-- strict thread matches above, loose matches on Subject: below --
2004-05-10 12:51 Megaraid problem support
2004-05-10 14:23 ` Matthias Andree
2004-03-28 0:27 megaraid problem Fabien Penso
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=873c7id6sa.fsf@linuxfr \
--to=penso@linuxfr.org \
--cc=linux-scsi@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