From: Ben Hutchings <ben@decadent.org.uk>
To: Neela Syam Kolli <megaraidlinux@lsi.com>
Cc: 632187@bugs.debian.org, operator@ins.uni-bonn.de,
Vasily Averin <vvs@sw.ru>, LKML <linux-kernel@vger.kernel.org>
Subject: megaraid vs i2o for PCI device ID 101e:1960
Date: Fri, 15 Jul 2011 15:29:56 +0100 [thread overview]
Message-ID: <1310740196.8783.288.camel@localhost> (raw)
In-Reply-To: <4E1EB3E8.1090503@ins.uni-bonn.de>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
On Thu, 2011-07-14 at 11:16 +0200, Alexander Schier wrote:
> On 07/14/2011 09:19 AM, Alexander Schier wrote:
> > Hi!
> >
> > On 07/13/2011 06:29 AM, Ben Hutchings wrote:
> >> Can you try adding 'blacklist=i2o_core' to the kernel parameters, so
> >> only the megaraid driver is used?
> > We will try this.
> Now it works, when i2o_core is blacklisted.
Alexander reported in <http://bugs.debian.org/632187> that the kernel
took a very long time to boot, and the log showed first i2o_core and
then megaraid failing to probe a device (ID 101e:1960). But above he
reports that megaraid is able to probe it successfully if i2o_core
didn't break it first.
Should this device be blacklisted from i2o_core? Are there likely other
MegaRAID devices that use the I2O PCI class but don't work with this
generic driver?
Ben.
--
Ben Hutchings
Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next parent reply other threads:[~2011-07-15 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E0C5B57.2020104@ins.uni-bonn.de>
[not found] ` <handler.632187.B.130943320529363.ack@bugs.debian.org>
[not found] ` <4E0D8BAE.1000004@ins.uni-bonn.de>
[not found] ` <1310531358.8783.249.camel@localhost>
[not found] ` <4E1E989A.2090307@ins.uni-bonn.de>
[not found] ` <4E1EB3E8.1090503@ins.uni-bonn.de>
2011-07-15 14:29 ` Ben Hutchings [this message]
2011-07-15 14:48 ` megaraid vs i2o for PCI device ID 101e:1960 Alan Cox
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=1310740196.8783.288.camel@localhost \
--to=ben@decadent.org.uk \
--cc=632187@bugs.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=megaraidlinux@lsi.com \
--cc=operator@ins.uni-bonn.de \
--cc=vvs@sw.ru \
/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