Skip to contentSkip to conversation

Problem with I2O block Driver in 2.4.17 and 2.4.18-pre9

DISCUSSION T. A. 2 participants 2 messages Feb 11, 2002

lore
Share & tools
lore

T. A.

author
#0 lore raw

Hi,

I have a rackmount system with an Intel RAID controller doing RAID 1
mirroring. This controller uses the I2O drivers. I've compiled 2.4.17 and 1.4.18-pre9 with the I2O drivers linked into the kernel. However both these kernels would then oops (looks like on initializing the I2O block driver) when the kernel boots up. This problem does not appear to be present in the RedHat 2.9.7 kernel and the Linus 2.4.5 kernels. However in my tests with both those kernels the I2O drivers were loaded as modules, if that makes any difference. Unfortunately because of where this system is located I was unable and will be unable in the near future to generate an Ooops report.

Is there a known bug in the I2O drivers (probably block) included in the
current 2.4.17 and 2.4.18-pre9 kernels?

Are the latest I2O drivers or patches located anywhere?

Thanks in advance for any help.

#1 lore raw
Quoted 2 lines

Is there a known bug in the I2O drivers (probably block) included in the
current 2.4.17 and 2.4.18-pre9 kernels?

Its a known problem. Use the Red Hat kernel tree for now and all will be well. I've spent some time working on this and after a long false trail caused by what appear to be very very nasty bios bugs in the ASUS AM7-266D mainboard I think I have the i2o_block and i2o_core problems sorted for x86, at least on the FC920 and Promise cards I have for testing. i2o_scsi I have some thinking left to do and may not be able to fix because it works on my cards and fails on some others.

Fixing i2o for 2.5 is a major undertaking and I don't plan to address that until close to the point 2.5 is frozen for a new stable release.

Alan