* megaraid vs i2o for PCI device ID 101e:1960
[not found] ` <4E1EB3E8.1090503@ins.uni-bonn.de>
@ 2011-07-15 14:29 ` Ben Hutchings
2011-07-15 14:48 ` Alan Cox
0 siblings, 1 reply; 2+ messages in thread
From: Ben Hutchings @ 2011-07-15 14:29 UTC (permalink / raw)
To: Neela Syam Kolli; +Cc: 632187, operator, Vasily Averin, LKML
[-- 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 --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: megaraid vs i2o for PCI device ID 101e:1960
2011-07-15 14:29 ` megaraid vs i2o for PCI device ID 101e:1960 Ben Hutchings
@ 2011-07-15 14:48 ` Alan Cox
0 siblings, 0 replies; 2+ messages in thread
From: Alan Cox @ 2011-07-15 14:48 UTC (permalink / raw)
To: Ben Hutchings; +Cc: Neela Syam Kolli, 632187, operator, Vasily Averin, LKML
> 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?
I²O will probe I²O class devices. How well it works depends upon the
firmware version of the specific board.
The fix in this case is either updated firmware, or to go into the
configuration for the board and turn off I2O support in the bios config.
Alan
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-07-15 14:46 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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 ` megaraid vs i2o for PCI device ID 101e:1960 Ben Hutchings
2011-07-15 14:48 ` Alan Cox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox