linux-kernel - megaraid vs i2o for PCI device ID 101e:1960

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <1310740196.8783.288.camel@localhost>
Date:	Fri, 15 Jul 2011 15:29:56 +0100
From:	Ben Hutchings <ben@...adent.org.uk>
To:	Neela Syam Kolli <megaraidlinux@....com>
Cc:	632187@...s.debian.org, operator@....uni-bonn.de,
	Vasily Averin <vvs@...ru>, LKML <linux-kernel@...r.kernel.org>
Subject: megaraid vs i2o for PCI device ID 101e:1960

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

Download attachment "signature.asc" of type "application/pgp-signature" (829 bytes)