From: Andy <genanr@emsphone.com>
To: linux-kernel@vger.kernel.org
Cc: linux-scsi@vger.kernel.org
Subject: WARNING : kernel 2.6.11.7 (others) kills megaraid 4e/Si dead
Date: Tue, 3 May 2005 10:15:32 -0500 [thread overview]
Message-ID: <20050503151532.GA1316@thumper2> (raw)
cross posted due to the severity of this issue.
I have killed two Dell 1850 (x86_64) with megaraid 4e/SI servers using
kernel 2.6.11.7. When the system boots, it looks like it does not see the
megaraid controller (because it never prints anything about it) and hangs
when it tries to mount root. When rebooted, the system says no firmware
present for embedded raid controller. I then try to flash it, the flash
program says the firmware is corrupt and flashes the controller. However,
upon reboot I still get the no firmware present, thus the machine can no
longer boot off the raid.
Andy
next reply other threads:[~2005-05-03 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 15:15 Andy [this message]
2005-05-03 19:00 ` WARNING : kernel 2.6.11.7 (others) kills megaraid 4e/Si dead Chris Wright
2005-05-06 22:08 ` Thomas Backlund
2005-07-05 14:52 ` Thomas Backlund
2005-07-05 15:58 ` Chris Wright
2005-07-06 4:38 ` Jussi Hamalainen
2005-07-06 6:31 ` Chris Wright
2005-07-06 8:40 ` Thomas Backlund
2005-07-07 7:17 ` Jussi Hamalainen
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=20050503151532.GA1316@thumper2 \
--to=genanr@emsphone.com \
--cc=linux-kernel@vger.kernel.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