Ubuntu
linux package

ioatdma 0000:00:08.0: Channel halted, chanerr = 0

Bug #750516 reported by Marcin Cieślak on 2011-04-04

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

Running:

Linux wikimania2010 2.6.35-28-server #50 SMP Sun Apr 3 22:59:19 CEST 2011 x86_64 GNU/Linux

Ubuntu 2.6.35-28.50-server 2.6.35.11

Compiled (unmodified) from maverick git

Last kernel *not* to exhibit the problem:

linux-image-2.6.35-25-server (2.6.35.25.32)

First kernel to start exhibit the problem:

linux-image-2.6.35-27-server (upgraded on 2011-03-04)

After upgrade on 2011-03-04 the system was running for ca. 16 hours and
then silently died (no entries in the log except for below and had to be
hard rebooted manually). No crashes with 2.6.35-28.50-server as of now.

Currently the dmesg is full of:

[26230.179806] ioatdma 0000:00:08.0: Channel halted, chanerr = 0
[26230.187116] ioatdma 0000:00:08.0: Channel halted, chanerr = 0
[26230.194057] ioatdma 0000:00:08.0: Channel halted, chanerr = 0
[26230.200636] ioatdma 0000:00:08.0: Channel halted, chanerr = 0
[26230.206908] ioatdma 0000:00:08.0: Channel halted, chanerr = 0
[26230.212821] ioatdma 0000:00:08.0: Channel halted, chanerr = 0
[26230.218360] ioatdma 0000:00:08.0: Channel halted, chanerr = 0
[26230.223592] ioatdma 0000:00:08.0: Channel halted, chanerr = 0
[26230.228442] ioatdma 0000:00:08.0: Channel halted, chanerr = 0
[26230.232982] ioatdma 0000:00:08.0: Channel halted, chanerr = 0
[26230.237150] ioatdma 0000:00:08.0: Channel halted, chanerr = 0
[26230.240973] ioatdma 0000:00:08.0: Channel halted, chanerr = 0
[26230.244492] ioatdma 0000:00:08.0: Channel halted, chanerr = 0

today it also exhibited:

[12574.192863] ioatdma 0000:00:08.0: Channel halted, chanerr = 0
[12574.192865] ioatdma 0000:00:08.0: Channel halted, chanerr = 0
[12574.192867] ioatdma 0000:00:08.0: Channel halted, chanerr = 0
[12574.192869] ioatdma 0000:00:08.0: Channel halted, chanerr = 0
[26229.903904] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26229.922568] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26229.931489] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26229.940362] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26229.949300] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26229.958224] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26229.967158] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26229.976099] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26229.985055] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26229.994018] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26230.002988] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26230.011971] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26230.020930] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26230.029953] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26230.038957] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26230.047961] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26230.056976] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26230.066000] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26230.075029] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26230.084066] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26230.093113] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26230.102170] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26230.111212] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26230.120322] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26230.129413] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26230.138518] ioatdma 0000:00:08.0: Channel halted, chanerr = 2
[26230.147256] ioatdma 0000:00:08.0: reset
[26230.147259] ioatdma 0000:00:08.0: chan2, CHANSTS = 0x00000003 CHANERR = 0x0002, clearing
[26230.155873] ioatdma 0000:00:08.0: Channel halted, chanerr = 0
[26230.164203] ioatdma 0000:00:08.0: Channel halted, chanerr = 0

Tags:

Revision history for this message

Marcin Cieślak (saperski) wrote on 2011-04-04:

lspci -vnvn output Edit (47.2 KiB, text/plain)

Marcin Cieślak (saperski) on 2011-04-04

tags:

added: regression-update

Marcin Cieślak (saperski) on 2011-04-04

tags:

added: maverick

Revision history for this message

Brad Figg (brad-figg) wrote on 2011-09-17: Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 750516

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status:	New → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-11-24:

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Cesar Celis (ccelis5215) on 2012-04-24

Changed in linux (Ubuntu):
status:	Expired → New

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-04-24:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Cesar Celis (ccelis5215) wrote on 2012-04-24:

Same behavior

uname -a
Linux engine 2.6.32-40-server #87-Ubuntu SMP Tue Mar 6 02:10:02 UTC 2012 x86_64 GNU/Linux

Do you need and additional log or info?

Revision history for this message

Cesar Celis (ccelis5215) wrote on 2012-05-13:

Hi, do you need any aditional info ?

Regards.

Revision history for this message

penalvch (penalvch) wrote on 2012-10-17:

Marcin Cieślak, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this 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 please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

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 text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

apport-collect -p linux <replace-with-bug-number>

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 text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

tags:	added: needs-kernel-logs needs-upstream-testing
Changed in linux (Ubuntu):
importance:	Undecided → Medium
status:	Confirmed → Incomplete

Revision history for this message

Marcin Cieślak (saperski) wrote on 2012-10-17:

I am sorry, but I have given up using Ubuntu and the server has been decommissioned already; so there is no way for me to reproduce the bug.

Removing myself from bug, as some people reported that affects them as well.

Revision history for this message

penalvch (penalvch) wrote on 2012-10-17:

Marcin Cieślak, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/750516/comments/8 regarding the hardware having been decommissioned. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.