From: "Chris Lee" <labmonkey42@gmail.com>
To: <linux-kernel@vger.kernel.org>
Cc: "'Andrew Morton'" <akpm@osdl.org>,
"'Ju, Seokmann'" <Seokmann.Ju@lsil.com>,
<linux-scsi@vger.kernel.org>, <Neela.Kolli@engenio.com>
Subject: RE: Problem with legacy megaraid
Date: Wed, 4 Oct 2006 05:21:55 -0500 [thread overview]
Message-ID: <45238b42.596f8da9.6d92.ffff908d@mx.gmail.com> (raw)
In-Reply-To:
> > > >
> > > > > Distro: Gentoo Linux
> > > > > Kernel: 2.6.17-gentoo-r7
> > > > >
> > > > > Hardware:
> > > > > Motherboard: Tyan Thunder i7501 Pro (S2721-533)
> > > > > CPUs: Dual 2.8Ghz P4 HT Xeons
> > > > > RAM: 4GB registered (3/1 split, flat model)
> > > > > RAID: Dell PERC2/DC (AMI Megaraid 467)
> > > > > SCSI: Adaptec AHA-2940U2/U2W PCI
> > > > > NICs: onboard e100 and dual onboard e1000
> > > > >
> >
> > Did it work correctly under any earlier kernel version? If
> > so, which?
>
> I've recently built the system and the problem was present
> with both 2.6.16-gentoo-r4 and now 2.6.17-gentoo-r7. I've
> not used any earlier kernel versions in this system.
To update... I've rolled back to 2.6.{12,11,9} and can still reproduce the
problem on all of them. I'm out of ideas as to where I can look for the
cause. If anyone (LSI, Dell people maybe?) has any ideas please let me
know.
Thanks,
Chris
next reply other threads:[~2006-10-04 10:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 10:21 Chris Lee [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-04 13:01 Problem with legacy megaraid Kolli, Neela
2006-09-30 15:06 Chris Lee
2006-09-30 22:54 ` Andrew Morton
2006-10-01 5:39 ` Chris Lee
2006-10-01 6:02 ` Andrew Morton
2006-10-01 6:44 ` Chris Lee
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=45238b42.596f8da9.6d92.ffff908d@mx.gmail.com \
--to=labmonkey42@gmail.com \
--cc=Neela.Kolli@engenio.com \
--cc=Seokmann.Ju@lsil.com \
--cc=akpm@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