Intel SRCU3-1 RAID (I2O) and 2.4.5-ac18

Date: Sat Jun 30 2001 - 00:41:38 EST

I have configured a RAID5 volume, partitioned it and created
ext2 on it. I can mount it and everything seems to be ok, but
trying to copy a large (+-500MB) file from one directory on
the filesystem on the RAID to another results in something like:

i2o/iop0: No handler for event (0x00000400)
i2o/iop0 requires user configuration
Driver "I2O Block OSM" did not release device!
i2ob_del_device called, but not in dev table!
Driver "I2O Block OSM" did not release device!

and the copying process is frozen. After that I can read
some data from the filesystem (tried to ls some directories)
but cannot umount it and cannot kill the copying process.
The event code in the message's first line sometimes has different
values (0x00000020 for example), the first line happens to
be repeated a few times as well.
The problem is fully reproducible with my system.

The system is RedHat 7.1, the kernel is compiled with SMP,
I2O block OSM, I2O PCI support and without I2O SCSI and I2O net OSMs.
SCSI support is also off. I enabled the enhanced RTC because a
somewhat dated document from Intel concerning support for this
controller with RH62 says it has to be on.
GCC and binutils versions are: egcs-2.91.66 (stock RH71 "kgcc"),
binutils- (stock RH71).

I have the controller working in an Intel L440GX+ board with
two PIII 700MHz processors. The board specs are: 82440GX chipset,
Cirrus Logic CLGD5480 VGA, Adaptec AIC-7896 SCSI (unused), Intel 82559
EtherPro100 (unused). The SRCU31 controller works in an ordinary PCI
slot (32bit/33mhz), the only other PCI card in the system (apart
from the on-board devices) is an Intel EtherPro100.
There are four IBM DDYS-T18350 drives on the controller, three of
them are in the raid. The controller has 32MB RAM as cache,
the system has 512MB of ECC RAM.


Przemek Tomala

PS: if you need additional info or you can help with this,
    please CC me, as I am not subscribed to the list

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

This archive was generated by hypermail 2b29 : Sat Jun 30 2001 - 21:00:23 EST