From: Thomas Backlund <tmb@mandriva.org>
To: Chris Wright <chrisw@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: WARNING : kernel 2.6.11.7 (others) kills megaraid 4e/Si dead
Date: Tue, 05 Jul 2005 17:52:03 +0300 [thread overview]
Message-ID: <42CA9E93.1050802@mandriva.org> (raw)
In-Reply-To: <20050503190005.GS23013@shell0.pdx.osdl.net>
Chris Wright wrote:
> * Andy (genanr@emsphone.com) wrote:
>
>>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.
>
>
> Not good. There were no megaraid changes in the -stable series. What's
> the last kernel.org kernel that worked for you?
>
Any news on this matter?
I hvr a PE1850 waiting for kernel upgrade, but I'm afraid to do so now...
I can't break my box with tests since it's in active use...
For now I'm running a 2.6.8.1 based kernel on the box...
--
Regards
Thomas
PS.
Please CC me as I'm not subscribed...
next prev parent reply other threads:[~2005-07-05 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 15:15 WARNING : kernel 2.6.11.7 (others) kills megaraid 4e/Si dead Andy
2005-05-03 19:00 ` Chris Wright
2005-05-06 22:08 ` Thomas Backlund
2005-07-05 14:52 ` Thomas Backlund [this message]
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=42CA9E93.1050802@mandriva.org \
--to=tmb@mandriva.org \
--cc=chrisw@osdl.org \
--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