WARNING: at /build/buildd/linux-2.6.35/net/sched/sch_generic.c:258 dev_watchdog+0x25f/0x270()

Bug #890552 reported by Antonio Dolcetta
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Running Ubuntu 10.10
Server reboots every 2-3 days or so, every time it does i find something similar to this in the dmesg output:

Nov 11 10:42:37 yushan kernel: [918106.903204] ------------[ cut here ]------------
Nov 11 10:42:37 yushan kernel: [918106.903217] WARNING: at /build/buildd/linux-2.6.35/net/sched/sch_generic.c:258 dev_watchdog+0x25f/0x270()
Nov 11 10:42:37 yushan kernel: [918106.903223] Hardware name: GA-880GM-USB3
Nov 11 10:42:37 yushan kernel: [918106.903227] NETDEV WATCHDOG: eth1 (e1000): transmit queue 0 timed out
Nov 11 10:42:37 yushan kernel: [918106.903231] Modules linked in: radeon ttm drm_kms_helper drm serio_raw i2c_algo_bit i2c_piix4 lp parport edac_core edac_mce_amd k10temp shpchp r8169 ahci libahci e1000 pata_atiixp mii aacraid
Nov 11 10:42:37 yushan kernel: [918106.903263] Pid: 0, comm: swapper Not tainted 2.6.35-30-server #61-Ubuntu
Nov 11 10:42:37 yushan kernel: [918106.903267] Call Trace:
Nov 11 10:42:37 yushan kernel: [918106.903271] <IRQ> [<ffffffff810615bf>] warn_slowpath_common+0x7f/0xc0
Nov 11 10:42:37 yushan kernel: [918106.903287] [<ffffffff810616b6>] warn_slowpath_fmt+0x46/0x50
Nov 11 10:42:37 yushan kernel: [918106.903294] [<ffffffff814cd1cf>] dev_watchdog+0x25f/0x270
Nov 11 10:42:37 yushan kernel: [918106.903301] [<ffffffff8108a633>] ? ktime_get+0x63/0xe0
Nov 11 10:42:37 yushan kernel: [918106.903308] [<ffffffff8108e20e>] ? clockevents_program_event+0x5e/0xa0
Nov 11 10:42:37 yushan kernel: [918106.903315] [<ffffffff8108f888>] ? tick_dev_program_event+0x48/0x110
Nov 11 10:42:37 yushan kernel: [918106.903321] [<ffffffff814ccf70>] ? dev_watchdog+0x0/0x270
Nov 11 10:42:37 yushan kernel: [918106.903327] [<ffffffff814ccf70>] ? dev_watchdog+0x0/0x270
Nov 11 10:42:37 yushan kernel: [918106.903335] [<ffffffff81070142>] call_timer_fn+0x42/0x120
Nov 11 10:42:37 yushan kernel: [918106.903341] [<ffffffff814ccf70>] ? dev_watchdog+0x0/0x270
Nov 11 10:42:37 yushan kernel: [918106.903348] [<ffffffff81071704>] run_timer_softirq+0x154/0x270
Nov 11 10:42:37 yushan kernel: [918106.903355] [<ffffffff8106862d>] __do_softirq+0xbd/0x200
Nov 11 10:42:37 yushan kernel: [918106.903362] [<ffffffff810ca8f0>] ? handle_IRQ_event+0x50/0x160
Nov 11 10:42:37 yushan kernel: [918106.903369] [<ffffffff8100afdc>] call_softirq+0x1c/0x30
Nov 11 10:42:37 yushan kernel: [918106.903375] [<ffffffff8100cab5>] do_softirq+0x65/0xa0
Nov 11 10:42:37 yushan kernel: [918106.903380] [<ffffffff810684e5>] irq_exit+0x85/0x90
Nov 11 10:42:37 yushan kernel: [918106.903387] [<ffffffff815aa645>] do_IRQ+0x75/0xf0
Nov 11 10:42:37 yushan kernel: [918106.903395] [<ffffffff815a3213>] ret_from_intr+0x0/0x11
Nov 11 10:42:37 yushan kernel: [918106.903399] <EOI> [<ffffffff81336898>] ? acpi_idle_enter_simple+0xe1/0x11a
Nov 11 10:42:37 yushan kernel: [918106.903413] [<ffffffff81336894>] ? acpi_idle_enter_simple+0xdd/0x11a
Nov 11 10:42:37 yushan kernel: [918106.903422] [<ffffffff814876c2>] cpuidle_idle_call+0x92/0x140
Nov 11 10:42:37 yushan kernel: [918106.903429] [<ffffffff81008d93>] cpu_idle+0xb3/0x110
Nov 11 10:42:37 yushan kernel: [918106.903435] [<ffffffff8159ab7c>] start_secondary+0x100/0x102
Nov 11 10:42:37 yushan kernel: [918106.903441] ---[ end trace 9892eb882f936781 ]---
Nov 11 10:42:40 yushan kernel: [918109.951632] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Nov 11 10:42:44 yushan kernel: [918114.010264] e1000 0000:04:06.0: eth1: Detected Tx Unit Hang
Nov 11 10:42:44 yushan kernel: [918114.010268] Tx Queue <0>
Nov 11 10:42:44 yushan kernel: [918114.010271] TDH <8d>
Nov 11 10:42:44 yushan kernel: [918114.010273] TDT <bc>
Nov 11 10:42:44 yushan kernel: [918114.010275] next_to_use <bc>
Nov 11 10:42:44 yushan kernel: [918114.010277] next_to_clean <8b>
Nov 11 10:42:44 yushan kernel: [918114.010279] buffer_info[next_to_clean]
Nov 11 10:42:44 yushan kernel: [918114.010281] time_stamp <1057878a0>
Nov 11 10:42:44 yushan kernel: [918114.010283] next_to_watch <8d>
Nov 11 10:42:44 yushan kernel: [918114.010285] jiffies <105787919>
Nov 11 10:42:44 yushan kernel: [918114.010287] next_to_watch.status <0>
Nov 11 10:42:46 yushan kernel: [918116.010239] e1000 0000:04:06.0: eth1: Detected Tx Unit Hang

Revision history for this message
Antonio Dolcetta (antoni6) wrote :
Revision history for this message
Antonio Dolcetta (antoni6) wrote :
Revision history for this message
Antonio Dolcetta (antoni6) wrote :
Revision history for this message
Antonio Dolcetta (antoni6) wrote :
tags: added: needs-upstream-testing
affects: linux-meta (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
importance: Undecided → Medium
status: Incomplete → Confirmed
Revision history for this message
AZ (m-dev) wrote :
Revision history for this message
penalvch (penalvch) wrote :

Antonio Dolcetta, 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? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . 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 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. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

summary: - server reboots (e1000): transmit queue 0 timed out
+ WARNING: at /build/buildd/linux-2.6.35/net/sched/sch_generic.c:258
+ dev_watchdog+0x25f/0x270()
tags: added: maverick
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.