mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "John Madden" <jmadden@ivytech.edu>
To: <linux-kernel@vger.kernel.org>
Subject: 2.6.x, megaraid, new driver version?
Date: Thu, 1 Jul 2004 16:33:54 -0500 (EST)	[thread overview]
Message-ID: <35545.10.0.15.208.1088717634.squirrel@mail.ivytech.edu> (raw)

In the process of eagerly moving my machines to the 2.6 series, I've run
across some intermittent issues with the built-in megaraid2 driver. 
Machines (Dell 2450's with PERC-3's and 1750's with PERC-4Di's) are
hanging with messages like:

megaraid: ABORTING- 345c5 cmd=2a <c=0 t=0 l=0>
megaraid: ABORTING- 345c5[47] fw owner.

...generally under I/O stress.

I see that the driver version is v2.00.3, released in Feb 2003 and that
the later 2.4.x kernels ship with much newer drivers.  Since I'm having no
trouble with the 1.1x driver on the machines that are still 2.4.x-based, I
have to either roll my boxen back to 2.4.26 or stick it out with 2.6.7 and
hope it turns out to be a good day.  I found in the archives mention of a
"unified driver" and I'm assuming that's referring to a single driver
between both kernel trees, but I saw no mention of a tentative release
date, what version of the driver that's to be based on, etc.

So I'm looking for suggestions -- what do I do driver-wise, how can I keep
them running on 2.6.x if possible, how soon before there's a unified
driver release in the mainline kernel, etc.?

Thanks,
  John




-- 
John Madden
UNIX Systems Engineer
Ivy Tech State College
jmadden@ivytech.edu



                 reply	other threads:[~2004-07-01 21:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=35545.10.0.15.208.1088717634.squirrel@mail.ivytech.edu \
    --to=jmadden@ivytech.edu \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®