> May 19 13:03:39 production kernel: i2o_block: Checking for Boot device...
> May 19 13:03:39 production kernel: i2o_block: Checking for I2O Block
> devices... May 19 13:03:39 production kernel: i2ob: Installing tid 11 device
> at unit 0
> May 19 13:03:39 production kernel: i2o/hda: Max segments 28, queue depth 8,
> byte limit 49152.
> May 19 13:03:39 production kernel: i2o/hda: Type 130: 621795MB, 512 byte
> sectors.
> May 19 13:03:39 production kernel: i2o/hda: Maximum sectors/read set to 96.
> May 19 13:03:39 production kernel: i2o/hda: i2o/hda1
So it found the card, found a non boot volume and is quite happy
with it. The type seems bogus but they do on all the promise devices.
> May 19 13:05:59 production kernel: i2o/iop0: No handler for event
> (0x00000020)
> May 19 13:05:59 production kernel: i2o/iop0: No handler for event
> (0x00000020)
It sent us two event messages for events we've never head of (or asked
for)
> May 19 13:06:04 production kernel: i2o/iop0: Hardware Failure: Unknown Error
and then exploded
> PDC20276: IDE controller on PCI bus 03 dev 00
> PCI: Device 03:00.0 not available because of resource collisions
> PCI: Device 03:00.0 not available because of resource collisions
> PDC20276: (ide_setup_pci_device:) Could not enable device.
> PDC20276: IDE controller on PCI bus 03 dev 08
> PCI: Device 03:01.0 not available because of resource collisions
> PCI: Device 03:01.0 not available because of resource collisions
> PDC20276: (ide_setup_pci_device:) Could not enable device.
> PDC20276: IDE controller on PCI bus 03 dev 10
> PCI: Device 03:02.0 not available because of resource collisions
> PCI: Device 03:02.0 not available because of resource collisions
> PDC20276: (ide_setup_pci_device:) Could not enable device.
So it skipped the PDC controllers, which is good
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/