public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Chris Lee <labmonkey42@gmail.com>
Cc: linux-kernel@vger.kernel.org, "'Ju,
	Seokmann'" <Seokmann.Ju@lsil.com>,
	linux-scsi@vger.kernel.org, Neela.Kolli@engenio.com
Subject: Re: Problem with legacy megaraid
Date: Sat, 30 Sep 2006 23:02:59 -0700	[thread overview]
Message-ID: <20060930230259.497b7bc9.akpm@osdl.org> (raw)
In-Reply-To: <451f5496.40cc4d00.1456.ffffef37@mx.gmail.com>

On Sun, 1 Oct 2006 00:39:37 -0500
"Chris Lee" <labmonkey42@gmail.com> wrote:

> Thanks for your response Andrew.  Comment responses in-line:
> 
> > 
> > > I am not subscribed to this list.  Please CC me on replies.
> > 
> > (more cc's added)
> > 
> 
> Outstanding; thank you.
> 
> > > I have a machine I'm trying to use as a file server.  I 
> > have a RAID10 and a
> > > RAID5 on a single Dell PERC2/DC (AMI Megaraid 467) 
> > controller.  Both arrays
> > > are also on the same SCSI channel.  The system runs fine 
> > for days on end
> > > until I put some heavy I/O load on either array and sustain 
> > it for a few
> > > seconds.
> > 
> > We recently discovered that "The old megaraid driver is 
> > apparently borken
> > for firmware newer than 6.61.".  So please check that and see if a
> > downgrade is needed.
> > 
> 
> The Dell firmware version on the card currently is 1.06.  I have not found a
> newer firmware version than that one.
> 
> > Is there some reason why you cannot use the new megaraid driver?
> > 
> 
> The config help for the megaraid drivers suggested that the new megaraid
> driver would not support a PERC2.  I had enabled both drivers in the kernel
> which is having this problem.:
> 
> CONFIG_MEGARAID_NEWGEN=y
> CONFIG_MEGARAID_MM=y
> CONFIG_MEGARAID_MAILBOX=y
> CONFIG_MEGARAID_LEGACY=y
> 
> After your suggestion I rebuilt the kernel with legacy disabled.:
> 
> CONFIG_MEGARAID_NEWGEN=y
> CONFIG_MEGARAID_MM=y
> CONFIG_MEGARAID_MAILBOX=y
> # CONFIG_MEGARAID_LEGACY is not set
> 
> The new megaraid driver does not detect the PERC2/DC just as I feared it
> would not.  Unless I'm missing some kernel commandline arguments necessary
> to make the new driver find the card, I'm stuck with legacy.

Oh well.  I was just guessing - I've never even seen a megaraid controller,
sorry.

> > 
> > > 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?

  reply	other threads:[~2006-10-01  6:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <451e87fa.60a54fb4.44c0.4562@mx.gmail.com>
2006-09-30 22:54 ` Problem with legacy megaraid Andrew Morton
2006-10-01  5:39   ` Chris Lee
2006-10-01  6:02     ` Andrew Morton [this message]
2006-10-01  6:44       ` Chris Lee
2006-10-04 10:21 Chris Lee
  -- strict thread matches above, loose matches on Subject: below --
2006-10-04 13:01 Kolli, Neela

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=20060930230259.497b7bc9.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=Neela.Kolli@engenio.com \
    --cc=Seokmann.Ju@lsil.com \
    --cc=labmonkey42@gmail.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