WARNING: at /build/buildd/linux-3.0.0/net/sched/sch_generic.c:255 dev_watchdog+0x1e6/0x1f0()

Bug #934812 reported by Daniel Richard G.
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linux
Incomplete
Undecided
Unassigned
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

I have a Toshiba laptop (Satellite A65) with a built-in Ethernet adapter, running Ubuntu Oneiric with the stock kernel 3.0.0-16.28. After some time in operation, while the system is in use, the network connection stops working and I find the following in /var/log/syslog:

Feb 18 02:20:44 lemon kernel: [12023.008097] ------------[ cut here ]------------
Feb 18 02:20:44 lemon kernel: [12023.008129] WARNING: at /build/buildd/linux-3.0.0/net/sched/sch_generic.c:255 dev_watchdog+0x1e6/0x1f0()
Feb 18 02:20:44 lemon kernel: [12023.008138] Hardware name: Satellite A65
Feb 18 02:20:44 lemon kernel: [12023.008146] NETDEV WATCHDOG: eth0 (8139too): transmit queue 0 timed out
Feb 18 02:20:44 lemon kernel: [12023.008152] Modules linked in: ppdev pcmcia snd_atiixp_modem snd_atiixp snd_ac97_codec ac97_bus snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd psmouse yenta_socket serio_raw pcmcia_rsrc pcmcia_core pcspkr soundcore snd_page_alloc joydev radeon ttm parport_pc drm_kms_helper drm i2c_algo_bit video i2c_piix4 shpchp ati_agp lp parport usbhid hid 8139too 8139cp pata_atiixp
Feb 18 02:20:44 lemon kernel: [12023.008276] Pid: 0, comm: swapper Not tainted 3.0.0-16-generic #28-Ubuntu
Feb 18 02:20:44 lemon kernel: [12023.008285] Call Trace:
Feb 18 02:20:44 lemon kernel: [12023.008306] [<c1047cd2>] warn_slowpath_common+0x72/0xa0
Feb 18 02:20:44 lemon kernel: [12023.008319] [<c14546a6>] ? dev_watchdog+0x1e6/0x1f0
Feb 18 02:20:44 lemon kernel: [12023.008332] [<c14546a6>] ? dev_watchdog+0x1e6/0x1f0
Feb 18 02:20:44 lemon kernel: [12023.008346] [<c1047da3>] warn_slowpath_fmt+0x33/0x40
Feb 18 02:20:44 lemon kernel: [12023.008359] [<c14546a6>] dev_watchdog+0x1e6/0x1f0
Feb 18 02:20:44 lemon kernel: [12023.008377] [<c1054c1f>] call_timer_fn+0x2f/0x110
Feb 18 02:20:44 lemon kernel: [12023.008394] [<c152e8bd>] ? _raw_spin_lock_irqsave+0x2d/0x40
Feb 18 02:20:44 lemon kernel: [12023.008410] [<c10ae98d>] ? force_qs_rnp+0xfd/0x140
Feb 18 02:20:44 lemon kernel: [12023.008423] [<c14544c0>] ? qdisc_reset+0x40/0x40
Feb 18 02:20:44 lemon kernel: [12023.008437] [<c105631b>] run_timer_softirq+0xeb/0x210
Feb 18 02:20:44 lemon kernel: [12023.008448] [<c14544c0>] ? qdisc_reset+0x40/0x40
Feb 18 02:20:44 lemon kernel: [12023.008464] [<c104e900>] ? local_bh_enable_ip+0x90/0x90
Feb 18 02:20:44 lemon kernel: [12023.008476] [<c104e900>] ? local_bh_enable_ip+0x90/0x90
Feb 18 02:20:44 lemon kernel: [12023.008487] [<c104e981>] __do_softirq+0x81/0x1a0
Feb 18 02:20:44 lemon kernel: [12023.008501] [<c104e900>] ? local_bh_enable_ip+0x90/0x90
Feb 18 02:20:44 lemon kernel: [12023.008510] <IRQ> [<c104ecc6>] ? irq_exit+0x76/0xa0
Feb 18 02:20:44 lemon kernel: [12023.008531] [<c1535ec9>] ? smp_apic_timer_interrupt+0x59/0x88
Feb 18 02:20:44 lemon kernel: [12023.008545] [<c1056ef5>] ? get_next_timer_interrupt+0x75/0xf0
Feb 18 02:20:44 lemon kernel: [12023.008556] [<c152ef29>] ? apic_timer_interrupt+0x31/0x38
Feb 18 02:20:44 lemon kernel: [12023.008569] [<c107007b>] ? sysctl_check_table+0x19b/0x240
Feb 18 02:20:44 lemon kernel: [12023.008585] [<c1009aec>] ? mwait_idle+0x7c/0x1d0
Feb 18 02:20:44 lemon kernel: [12023.008598] [<c100175a>] ? cpu_idle+0x8a/0xc0
Feb 18 02:20:44 lemon kernel: [12023.008611] [<c1501a75>] ? rest_init+0x5d/0x68
Feb 18 02:20:44 lemon kernel: [12023.008628] [<c17c1763>] ? start_kernel+0x352/0x358
Feb 18 02:20:44 lemon kernel: [12023.008642] [<c17c13a2>] ? pass_bootoption.constprop.2+0xe2/0xe2
Feb 18 02:20:44 lemon kernel: [12023.008655] [<c17c10a9>] ? i386_start_kernel+0xa9/0xaf
Feb 18 02:20:44 lemon kernel: [12023.008663] ---[ end trace e4b87fe15e496637 ]---
Feb 18 02:20:47 lemon kernel: [12026.016082] 8139too 0000:02:07.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Feb 18 02:20:59 lemon kernel: [12038.016067] 8139too 0000:02:07.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Feb 18 02:21:11 lemon kernel: [12050.016074] 8139too 0000:02:07.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Feb 18 02:21:23 lemon kernel: [12062.016072] 8139too 0000:02:07.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Feb 18 02:21:35 lemon kernel: [12074.016070] 8139too 0000:02:07.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Feb 18 02:21:47 lemon kernel: [12086.016055] 8139too 0000:02:07.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Feb 18 02:21:59 lemon kernel: [12098.016086] 8139too 0000:02:07.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Feb 18 02:22:11 lemon kernel: [12110.016069] 8139too 0000:02:07.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Feb 18 02:22:23 lemon kernel: [12122.016223] 8139too 0000:02:07.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

Unloading/reloading the 8139too/8139cp modules doesn't help at that point, only rebooting. Seeing as the logged stack trace goes through some SMP-related functions, I am currently running this system with the "nosmp" kernel parameter and so far that appears to be keeping this bug at bay.
---
ApportVersion: 1.23-0ubuntu4
Architecture: i386
DistroRelease: Ubuntu 11.10
Package: linux (not installed)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Tags: oneiric
Uname: Linux 3.2.13-030213-generic i686
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout floppy plugdev video

Revision history for this message
Daniel Richard G. (skunk) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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

apport-collect 934812

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
tags: added: oneiric
Revision history for this message
Daniel Richard G. (skunk) wrote : Re: 8139too: NIC stops working with "NETDEV WATCHDOG: eth0 (8139too): transmit queue 0 timed out"

This is a minimal install running off a CompactFlash card, so I actually don't have the apport-collect command. I can provide any telemetry that is needed manually, however.

(Note that I've encountered this same error previously with a stock install, so the bug is clearly independent of the minimal nature of this system)

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Daniel Richard G., thank you for reporting this bug and helping make Ubuntu better. Could you please attach all apport information following https://help.ubuntu.com/community/ReportingBugs#Filing_bugs_when_off-line ? As well, please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please 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 <replace-with-bug-number>

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.

summary: - 8139too: NIC stops working with "NETDEV WATCHDOG: eth0 (8139too):
- transmit queue 0 timed out"
+ WARNING: at /build/buildd/linux-3.0.0/net/sched/sch_generic.c:255
+ dev_watchdog+0x1e6/0x1f0()
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Daniel Richard G. (skunk) wrote :

Thank you Christopher, please see comment #3.

I will attempt to test this issue with a mainline kernel when the opportunity arises.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Daniel Richard G. (skunk) wrote :

Confirmed this issue with the 3.2.13-030213-generic mainline kernel.

tags: added: apport-collected
description: updated
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Daniel Richard G. (skunk) wrote :

Attached is the system's complete syslog, from bootup to NIC failure.

(Note that the Apport-collected info is from the mainline kernel running with "nosmp", as the failure happens early on, and of course once that's happened the system cannot contact Launchpad.)

Revision history for this message
penalvch (penalvch) wrote :

Daniel Richard G., the issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at http://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html . If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Triaged
Changed in linux:
status: New → Incomplete
Revision history for this message
penalvch (penalvch) wrote :

Daniel Richard G., 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? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

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 (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. 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. For example:
kernel-fixed-upstream-v3.12

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

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

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
tags: added: needs-kernel-logs needs-upstream-testing regression-potential
removed: apport-collected
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.