From: Chris Wright <chrisw@osdl.org>
To: Jussi Hamalainen <count@theblah.fi>
Cc: Chris Wright <chrisw@osdl.org>,
Thomas Backlund <tmb@mandriva.org>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
Andy <genanr@emsphone.com>
Subject: Re: WARNING : kernel 2.6.11.7 (others) kills megaraid 4e/Si dead
Date: Tue, 5 Jul 2005 23:31:59 -0700 [thread overview]
Message-ID: <20050706063158.GY9046@shell0.pdx.osdl.net> (raw)
In-Reply-To: <Pine.LNX.4.62.0507060735570.24203@mir.senvnet.fi>
* Jussi Hamalainen (count@theblah.fi) wrote:
> On Tue, 5 Jul 2005, Chris Wright wrote:
>
> >>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...
> >
> >Last known good one (that Andy tested) was 2.6.10. His was the only
> >report I've seen, and I haven't found any more details on it.
>
> I have several PE1850s running 2.6.11.10 and above. I have never had
> a megaraid controller die on me. This might be something related to a
> particular firmware version or setup. I could check the firmware
> versions if you want.
Good to hear. Andy gave this firmware info:
Megaraid (256 mb cache), firmware : 516A BIOS : H418
next prev parent reply other threads:[~2005-07-06 8:05 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
2005-07-05 15:58 ` Chris Wright
2005-07-06 4:38 ` Jussi Hamalainen
2005-07-06 6:31 ` Chris Wright [this message]
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=20050706063158.GY9046@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=count@theblah.fi \
--cc=genanr@emsphone.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tmb@mandriva.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