karmic cciss: error messages on working device

[Mattias Wadenstein]

Binary package hint: linux-image-2.6.31-5-generic

On my shiny new bl460c g6 blade with onboard p410i controller I have a raid 1 configured with current karmic installed. This boots and works, but the kernel keeps logging:

[ 6888.914389] end_request: I/O error, dev cciss/c1d0, sector 0
[ 6919.199942] end_request: I/O error, dev cciss/c1d0, sector 0
[ 6919.205875] end_request: I/O error, dev cciss/c1d0, sector 0

c1d0 is the device that is partitioned with root and boot etc on, as well as the disk that grub is installed on. As far as I can tell, there isn't anything wrong with the storage (hpacucli says everything is OK, debsums reports no errors, the system boots off that disks etc) so maybe this is a driver issue?

The frequency of the error messages goes up with disk activity.

[Mattias Wadenstein (maswan)]

Still an issue on linux-image-2.6.31-11-server version 2.6.31-11.36, this makes using the console really annoying.

[pingou67 (pingou67)]

I have exactly the same logging message and same symptoms on an HP DL360G5 with a p400i controller, but only when I create an lvm snapshot.

[Mattias Wadenstein (maswan)]

Fixed with current 2.6.31.14.25, thanks!

[Jeremy Foshee (jeremyfoshee)]

Hi Mattias,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 413070

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Mattias Wadenstein (maswan)]

Note my comment on 2009-10-16:
"Fixed with current 2.6.31.14.25, thanks!"

Which means the bug was fixed then.