Fedora is getting a bunch of bug reports about the I2O block
driver not working in 2.6.19 kernels.
Everything looks like it loads OK, but no block IO can be
done, not even reading the partition table:
I2O subsystem v1.325
i2o: max drivers = 8
i2o: Checking for PCI I2O controllers...
ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC4] -> GSI 19 (level, low) -> IRQ 19
iop0: controller found (0000:01:07.0)
iop0: limit sectors per request to 128
iop0: using 64-bit DMA
iop0: PCI I2O controller at E0000000 size=1048576
iop0: Installed at IRQ 19
i2o: iop0: Activating I2O controller...
i2o: iop0: This may take a few minutes if there are many devices
iop0: HRT has 1 entries of 16 bytes each.
Adapter 00000012: TID 0000:[HPC*]:PCI 1: Bus 1 Device 22 Function 0
i2o: iop0: Controller added
I2O Block Device OSM v1.325
block-osm: registered device at major 80
i2o/hda:<3>Buffer I/O error on device i2o/hda, logical block 0
Buffer I/O error on device i2o/hda, logical block 0
Buffer I/O error on device i2o/hda, logical block 0
unable to read partition table
block-osm: device added (TID: 209): i2o/hda
The driver looks unchanged except for cleanups...
Chuck Ebbert <cebbert <at> redhat.com> writes:
>
> Fedora is getting a bunch of bug reports about the I2O block
> driver not working in 2.6.19 kernels.
>
> Everything looks like it loads OK, but no block IO can be
> done, not even reading the partition table:
...[snip]
This is reproduced on my SMP 2.6.19 machine. Under 2.6.18 the i2o drive is
fine; under the latest 2.6.19 kernel, it throws errors at startup as reported in
this thread. i2o firmware version is v001.62 2002/11/06.
> i2o/hda:<3>Buffer I/O error on device i2o/hda, logical block 0
> Buffer I/O error on device i2o/hda, logical block 0
Same error here. Both 2.6.19 and 2.6.20 kernels, using Adaptec 2400A RAID.
(cc's restored. Please, always do reply-to-all)
> On Fri, 23 Feb 2007 22:57:27 +0000 (UTC) Mark Gray <[email protected]> wrote:
> > i2o/hda:<3>Buffer I/O error on device i2o/hda, logical block 0
> > Buffer I/O error on device i2o/hda, logical block 0
>
> Same error here. Both 2.6.19 and 2.6.20 kernels, using Adaptec 2400A RAID.
Is Adaptec 2400 controlled by drivers/message/i2o? I assume so...
If so, thats's at least three people reporting breakage in 2.6.19 and later.
Is anyone able perform a git-bisect to identify the offending commit? It
would really help.
Thanks.
Hello,
Andrew Morton wrote:
> (cc's restored. Please, always do reply-to-all)
>> On Fri, 23 Feb 2007 22:57:27 +0000 (UTC) Mark Gray <[email protected]> wrote:
>>> i2o/hda:<3>Buffer I/O error on device i2o/hda, logical block 0
>>> Buffer I/O error on device i2o/hda, logical block 0
>> Same error here. Both 2.6.19 and 2.6.20 kernels, using Adaptec 2400A RAID.
> Is Adaptec 2400 controlled by drivers/message/i2o? I assume so...
> If so, thats's at least three people reporting breakage in 2.6.19 and later.
> Is anyone able perform a git-bisect to identify the offending commit? It
> would really help.
> Thanks.
I've already reversed the changes from 2.6.19 for the I2O subsystem, but
it wasn't the solution. Probably it has something to do with the DMA
handling, because some commands go through very well, while others
don't. I'm working on the issue and report back as soon as i find a
solution.
Best regards,
Markus Lidel
------------------------------------------
Markus Lidel (Senior IT Consultant)
Shadow Connect GmbH
Carl-Reisch-Weg 12
D-86381 Krumbach
Germany
Phone: +49 82 82/99 51-0
Fax: +49 82 82/99 51-11
E-Mail: [email protected]
URL: http://www.shadowconnect.com
Gesch?ftsf?hrer/CEO: Markus Lidel
HRB 10357, Amtsgericht Memmingen