tg3: reports "eth0: DMA Status error. Resetting chip.", fails to work
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Debian) |
Fix Released
|
Unknown
|
|||
linux (Ubuntu) |
Fix Released
|
High
|
Joseph Salisbury | ||
Precise |
Fix Released
|
High
|
Joseph Salisbury |
Bug Description
I recently upgraded a Hewlett-Packard ProLiant DL385 G1 to precise from lucid, landing on linux-image-
When I rebooted, I was unable to log in over the network. I examined the serial console and found the following (full dmesg attached). This sequence is emitted over and over until "ifdown eth0" is run.
tg3 0000:03:06.0: eth0: DMA Status error. Resetting chip.
tg3 0000:03:06.0: eth0: 0x00000000: 0x164814e4, 0x22b00146, 0x02000010, 0x00804010
<many lines removed - see attached dmesg>
tg3 0000:03:06.0: eth0: 0x00007010: 0x44ea66f0, 0x00014a00, 0x009f0020, 0xa184a053
tg3 0000:03:06.0: eth0: 0: Host status block [00000007:
tg3 0000:03:06.0: eth0: 0: NAPI info [00000000:
tg3 0000:03:06.0: tg3_stop_block timed out, ofs=4800 enable_bit=2
The problem (or a very similar one) is also present in oneiric's kernel (I tested linux-image-
CVE References
tags: | added: regression-release |
Changed in linux (Ubuntu Precise): | |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
no longer affects: | linux (Ubuntu Oneiric) |
Changed in linux (Ubuntu): | |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
Changed in linux (Ubuntu Precise): | |
status: | Confirmed → Fix Committed |
Changed in linux (Ubuntu): | |
status: | Confirmed → Fix Released |
tags: | removed: performing-bisect |
Changed in linux (Debian): | |
status: | Unknown → New |
Changed in linux (Debian): | |
status: | New → Fix Released |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1005699
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.