WARNING: at /build/buildd/linux-2.6.32/net/sched/sch_generic.c:261 dev_watchdog+0x262/0x270()

Bug #535315 reported by Mossroy
108
This bug affects 20 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
High
Unassigned

Bug Description

This sometimes happens when I plug an USB device (it is an OpenMoko Freerunner GTA02 v7).
This device is normally detected as a network interface (eth1 : eth0 is my normal network interface). I have configured network-manager to manually configure the IP/netmask etc.

Steps to reproduce : plug-in the device, un-plug it, plug it in again etc until the crash finally occurs.

I use Ubuntu 10.04 alpha 3 with all updates (kernel 2.6.32-16).
I was previously using Ubuntu 9.10 on another computer : when plugging in and out several times, it sometimes froze my system. I suppose it's the same problem.

ProblemType: KernelOops
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: xxxxx 2111 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfbff8000 irq 22'
   Mixer name : 'Intel G45 DEVIBX'
   Components : 'HDA:10ec0889,1458a022,00100004 HDA:80862804,80860101,00100000'
   Controls : 47
   Simple ctrls : 25
Date: Tue Mar 9 19:52:12 2010
DistroRelease: Ubuntu 10.04
Failure: oops
HibernationDevice: RESUME=UUID=ab164ede-bbb0-4c19-8c75-1cb68eb90472
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 eth1 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. H55/H57-UD3H
Package: linux-image-2.6.32-16-generic 2.6.32-16.24
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=89af8148-6135-4499-bc8d-604c7428e531 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.32-16.24-generic
Regression: No
RelatedPackageVersions: linux-firmware 1.32
Reproducible: Yes
RfKill:

SourcePackage: linux
TestedUpstream: No
Title: WARNING: at /build/buildd/linux-2.6.32/net/sched/sch_generic.c:261 dev_watchdog+0x262/0x270()
Uname: Linux 2.6.32-16-generic x86_64
dmi.bios.date: 12/30/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: H55/H57-UD3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd12/30/2009:svnGigabyteTechnologyCo.,Ltd.:pnH55/H57-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55/H57-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: H55/H57-UD3H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Mossroy (mossroy) wrote :
Revision history for this message
Mossroy (mossroy) wrote :

Same problem with 2.6.32-19

Revision history for this message
Matt Zimmerman (mdz) wrote :

I see the same when connecting a G1 running Android. This worked OK in 9.10, but fails (most recently tested on 2.6.32-20.30)

Revision history for this message
Matt Zimmerman (mdz) wrote :

(when I have USB tethering enabled, which causes the device to appear as a network interface usb0)

tags: added: regression-potential
Changed in linux (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Slonik (slonik123) wrote :

Just logged in remotely to my ubuntu pc and seen that apport detected a crash. Don't know how it occured.

Revision history for this message
sam tygier (samtygier) wrote :

just received this. i also have a openmoko freerunner connected by USB to my computer

tags: added: kernel-net kernel-reviewed
Revision history for this message
Stefan Bader (smb) wrote :

Is this still seen on the latest (-23 or -24) Lucid kernel which include the updates to upstream stable 2.6.32.15?

Revision history for this message
Mossroy (mossroy) wrote :

I still have these warnings with latest lucid kernel (2.6.32-23 on my machine) : I had it once today and once yesterday in /var/log/messages
Anyway, these warnings did not make apport open (as it did at the beginning) : I would not have noticed them if I did not check my logs

Lee Jones (lag)
Changed in linux (Ubuntu):
assignee: nobody → Lee Jones (lag)
Revision history for this message
Lee Jones (lag) wrote :

Couple of things:
  1. Is this just a warning, or does it stop the device from working?
  2. Can you try these kernels and report back here please?
      If the bug still occurs, can you post the new dmesg here also?

Firstly Lucid, with extra debug:
  http://people.canonical.com/~ljones/lp535315-lucid/

Secondly the latest Maverick kernel:
  http://people.canonical.com/~ljones/lp605716-maverick/

Revision history for this message
Mossroy (mossroy) wrote :

Thanks for your help Lee.

Question 1 : I'm not sure, I'll have to check. It happens that the FreeRunner connected through USB is not reachable via ssh (host not found). But I'll have to check if it's not for another reason. In these cases, I simply disconnect and reconnect it, and ssh works. It seems probable to me that it happens when there is this error message.
Question 2 : I just installed your lucid kernel with extra debug, and will try to reproduce the problem and give you more details. It currently writes 6 lines in /var/log/messages every 6 seconds, so I hope I will not have to wait for too long ;-)

Revision history for this message
Mossroy (mossroy) wrote :

Hi, I reproduced the problem this morning.
So, for question 1 : I can confirm that the device does not work when this error occurs. The network device usb0 exists, and has the correct IP address 192.168.0.200 (which indicates that NetworkManager detected correctly the MAC Address of the FreeRunner), but the IP address of the FreeRunner (192.168.0.202) is not pingable : 100% packet loss

For question 2, you will find in the attchment file the log lines in /var/log/messages (a few seconds before and a few seconds after)

My FreeRunner will stay plugged in this state for the next 2 hours, but I'll have to disconnect it after (after all, this is my cell phone ;-) ). In the mean time, I might run more tests if you wish.

Please tell me if I can install the normal kernel of Lucid back, or if I should install the one from Maverick

Revision history for this message
Lee Jones (lag) wrote :

Thanks for that.

Can you try the Maverick kernel I sent you please?

I'd like to know if this bug has regressed, or has been fixed on Maverick.

Revision history for this message
Mossroy (mossroy) wrote :

OK : I installed the Maverick kernel (2.6.35-16) and reproduced the error (see attached log lines)
The behavior is the same : usb0 interface exists with correct IP address, but FreeRunner is not pingable

Revision history for this message
mido (filo17) wrote : Re: [Bug 535315] Re: WARNING: at/build/buildd/linux-2.6.32/net/sched/sch_generic.c:261dev_watchdog+0x262/0x270()
Download full text (3.6 KiB)

Sorry for the late posting a reply, I can't test this bug because I have another computer and I have the ubuntu marverick
Michal Filo

 ______________________________________________________________
 > Od: "Lee Jones"
 > Komu: <email address hidden>
 > Datum: 11.10.2010 12:03
 > Předmět: [Bug 535315] Re: WARNING: at/build/buildd/linux-2.6.32/net/sched/sch_generic.c:261dev_watchdog+0x262/0x270()
 >
 Thanks for that.

 Can you try the Maverick kernel I sent you please?

 I'd like to know if this bug has regressed, or has been fixed on
 Maverick.

 --
 WARNING: at /build/buildd/linux-2.6.32/net/sched/sch_generic.c:261 dev_watchdog+0x262/0x270()
 https://bugs.launchpad.net/bugs/535315
 You received this bug notification because you are a direct subscriber
 of a duplicate bug (543534).

 Status in “linux” package in Ubuntu: Confirmed

 Bug description:
 This sometimes happens when I plug an USB device (it is an OpenMoko Freerunner GTA02 v7).
 This device is normally detected as a network interface (eth1 : eth0 is my normal network interface). I have configured network-manager to manually configure the IP/netmask etc.

 Steps to reproduce : plug-in the device, un-plug it, plug it in again etc until the crash finally occurs.

 I use Ubuntu 10.04 alpha 3 with all updates (kernel 2.6.32-16).
 I was previously using Ubuntu 9.10 on another computer : when plugging in and out several times, it sometimes froze my system. I suppose it's the same problem.

 ProblemType: KernelOops
 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
 Annotation: Your system might become unstable now and might need to be restarted.
 Architecture: amd64
 AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  boris      2111 F.... pulseaudio
 CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
 Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfbff8000 irq 22'
   Mixer name : 'Intel G45 DEVIBX'
   Components : 'HDA:10ec0889,1458a022,00100004 HDA:80862804,80860101,00100000'
   Controls      : 47
   Simple ctrls  : 25
 Date: Tue Mar  9 19:52:12 2010
 DistroRelease: Ubuntu 10.04
 Failure: oops
 HibernationDevice: RESUME=UUID=ab164ede-bbb0-4c19-8c75-1cb68eb90472
 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113)
 IwConfig:
 lo        no wireless extensions.

 eth0      no wireless extensions.

 eth1      no wireless extensions.
 MachineType: Gigabyte Technology Co., Ltd. H55/H57-UD3H
 Package: linux-image-2.6.32-16-generic 2.6.32-16.24
 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=89af8148-6135-4499-bc8d-604c7428e531 ro quiet splash
 ProcVersionSignature: Ubuntu 2.6.32-16.24-generic
 Regression: No
 RelatedPackageVersions: linux-firmware 1.32
 Reproducible: Yes
 RfKill:

 SourcePackage: linux
 TestedUpstream: No
 Title: WARNING: at /build/buildd/linux-2.6.32/net/sched/sch_generic.c:261 dev_watchdog+0x262/0x270()
 Uname: Linux 2.6.32-16-generic x86_64
 dmi.bios.date: 12/30/2009
 dmi.bios.vendor: Award Software International, Inc.
 dmi.bios.version: F2
 dmi.board.name: H55/H57-UD3H
 dmi.board.vendor: Gigabyte Technology Co., Ltd.
 dmi.board.version: x.x
 dmi.chassis.type: 3
 dmi.chassis....

Read more...

Revision history for this message
Mossroy (mossroy) wrote :

I just upgraded the BIOS of my motherboard (Gigabyte H55-UD3H) to latest version (F10), but the problem remains

Revision history for this message
Lee Jones (lag) wrote :

I'm fairly sure it's not a BIOS issue.

I'd like to do some proper investigation, but it's proving difficult without affected hardware. I have been searching the code for clues and placing on lots of further debug. Hopefully, there should be a kernel (debug only) for you to test tomorrow.

In the mean time, can you place this on your kernel command line and tell me if the problem still occurs?

pcie_aspm=off

Thank you.

Revision history for this message
Lee Jones (lag) wrote :

I've compiled you up some more kernels to help me debug this issue. I hope you bear with me as I would like to have this fixed as much as you.

I have made the kernels available here:
  http://people.canonical.com/~ljones/lp535315-maverick/

If you'd be so kind as to test and post me your full logs (no snipping), it would help me a lot.

Revision history for this message
Mossroy (mossroy) wrote :

Lee, thanks again for your help on this problem.
I booted with pcie_apsm=off kernel parameter : same behavior

I'll try your new kernel and keep you informed.
Which log do you need? /var/log/messages or another one?

description: updated
Revision history for this message
Mossroy (mossroy) wrote :

Just reproduced the problem with your last kernel (2.6.35-23).
You'll find attached the /var/log/messages since the reboot.
I started the computer with the FreeRunner unplugged, waited around 2 minutes, then plugged it : that's all.
I'm connected through an USB hub : maybe you would want me to try without the hub?

Revision history for this message
Mossroy (mossroy) wrote :

Reproduced the same problem with the FreeRunner plugged directly to the computer (no USB hub). See attached log

Revision history for this message
Lee Jones (lag) wrote :

The debug appears to be missing from the above log.

Can you try again please?

I have made them available here:
  http://people.canonical.com/~ljones/lp535315-netdev-watchdog-maverick/

Both /var/log/kern.log and /var/log/messages would be helpful to me.

Thanks again.

Revision history for this message
Mossroy (mossroy) wrote :

Could you please generate the amd64 versions of your kernel ? My ubuntu is a 64-bit version

Revision history for this message
Lee Jones (lag) wrote :

The *-amd64 kernel is rolled, just uploading.

I'm doing so many things at the moment, my network is saturated.

Shouldn't be too long now.

Revision history for this message
Lee Jones (lag) wrote :

Okay, check now.

Revision history for this message
Mossroy (mossroy) wrote :

You'll find attached the logs with your kernel. But I don't see more debug lines

Revision history for this message
Mossroy (mossroy) wrote :
Revision history for this message
Lee Jones (lag) wrote :

Oddly, it looks like the i386 kernel is fine, by the amd64 one is not.

My sincerest apologies.

New one would be up in ~30mins.

Revision history for this message
Lee Jones (lag) wrote :

Okay, that should have sorted it.

Revision history for this message
Mossroy (mossroy) wrote :

This time I have a lot of debug lines.
You'll find the complete log in attached files.
As usually, I started the computer with the FreeRunner unplugged, waited 2 minutes after startup, then plugged the FreeRunner.
This seems to trigger the error each time.
In the attached logs, the FreeRunner is plugged in at 20:56:17, and the error message appears at 20:56:27

Revision history for this message
Mossroy (mossroy) wrote :
Revision history for this message
Lee Jones (lag) wrote :

I've been doing some research and it look as if this is a known issue.

There are very similar bugs already open, such as here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/472057

I do plan to get to the bottom of them, but it will take some time.

I have build some new kernels with new debug contained.

These kernels enlarge the time out by quite a bit.

Can you give them a go and report back your entire /var/log/kern.log please?

http://people.canonical.com/~ljones/lp535315-netdev-watchdog-maverick/

Revision history for this message
Mossroy (mossroy) wrote :

The same steps reproduced the problem with you latest kernel.
You'll find the kern.log attached.
I plugged in the FreeRunner around 15:04:04, and the error appears at 15:04:20

Revision history for this message
carloslp (carloslp) wrote :

I am running Ubuntu 10.04 Server LTS. A few days ago I upgraded the kernel from 2.6.32-25-server to 2.6.32-26-server.

I am attaching lsmod output and kern.log.

I don't think the syn flood messages matters here. I always receive a lot of this kind of messages (its related to P2P stuff), but its the first time that the kernel crashs.

After this error my Internet connection reseted and the ppp daemon restarted it:

Dec 4 04:45:01 quark pppd[958]: LCP terminated by peer
Dec 4 04:45:01 quark pppd[958]: Connect time 2045.3 minutes.
Dec 4 04:45:01 quark pppd[958]: Sent 546375938 bytes, received 2573596158 bytes.
Dec 4 04:45:04 quark pppd[958]: Connection terminated.
Dec 4 04:45:05 quark pppd[958]: Modem hangup
Dec 4 04:45:35 quark pppd[958]: PPP session is 1388
Dec 4 04:45:35 quark pppd[958]: Connected to XX:XX:XX:XX:XX:XX via interface eth1
Dec 4 04:45:35 quark pppd[958]: Using interface ppp0
Dec 4 04:45:35 quark pppd[958]: Connect: ppp0 <--> eth1
Dec 4 04:45:38 quark pppd[958]: CHAP authentication succeeded: Welcome to use Quidway ROUTER, Huawei Tech.^M^J
Dec 4 04:45:38 quark pppd[958]: CHAP authentication succeeded
Dec 4 04:45:38 quark pppd[958]: peer from calling number XX:XX:XX:XX:XX:XX authorized
Dec 4 04:45:38 quark pppd[958]: local IP address YY.YY.YY.YY
Dec 4 04:45:38 quark pppd[958]: remote IP address YY.YY.YY.ZZ
Dec 4 04:45:38 quark pppd[958]: primary DNS address YY.YY.YY.ZX
Dec 4 04:45:38 quark pppd[958]: secondary DNS address YY.YY.YY.ZX

I replaced MAC and IP address by [XYZ]

Revision history for this message
carloslp (carloslp) wrote :

And here is the lsmod output

Revision history for this message
carloslp (carloslp) wrote :

I want to add that this never happened me before with 2.6.32-25-server or earlier.

This happened me for first time after upgrading to 2.6.32-26-server a few days ago (only happened once for the moment)

Perhaps is a bug introduced in 2.6.32-26-server

Revision history for this message
Lee Jones (lag) wrote :

I need to remove myself from this bug, as I have moved on.

I hope someone picks it up in the near future.

Changed in linux (Ubuntu):
assignee: Lee Jones (lag) → nobody
Revision history for this message
Mossroy (mossroy) wrote :

@Lee Jones : too bad you can't continue investigating this bug.
Could you at least explain here which ideas you had, which assumptions were right or wrong etc. So that we might not start from scratch again with someone else
In any case, thank you for your work on it.

@carloslp : I don't think it's a bug introduced in 2.6.32-26, as I initially reported it on a 2.6.32-16 kernel

Anyway, the problem is still there on my Ubuntu 10.04.1 (although I reinstalled it from scratch in August 2010) : it occurs around once a day, appears in my logs, and make my openmoko unreachable until I disconnect and reconnect it.

Revision history for this message
sam tygier (samtygier) wrote :

i no longer get this on plugging in an openmoko on 2.6.38-1-generic kernel in natty

Revision history for this message
Mossroy (mossroy) wrote :

I still get thisonce a day on lucid with kernel 2.6.32-28-generic

tags: removed: regression-potential
Revision history for this message
David Peall (dkpeall) wrote :
Download full text (3.2 KiB)

Took down my server:

May 28 18:06:19 host2 kernel: [16516634.010636] ------------[ cut here ]------------
May 28 18:06:19 host2 kernel: [16516634.010649] WARNING: at /build/buildd/linux-2.6.32/net/sched/sch_generic.c:261 dev_watchdog+0x262/0x270()
May 28 18:06:19 host2 kernel: [16516634.010652] Hardware name: PowerEdge 2950
May 28 18:06:19 host2 kernel: [16516634.010654] NETDEV WATCHDOG: eth0 (bnx2): transmit queue 0 timed out
May 28 18:06:19 host2 kernel: [16516634.010656] Modules linked in: btrfs zlib_deflate crc32c libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs exportfs reiserfs ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables bridge stp joydev kvm_intel kvm usbhid usb_storage fbcon tileblit font bitblit softcursor hid vga16fb vgastate radeon ttm drm_kms_helper drm i2c_algo_bit dell_wmi dcdbas psmouse serio_raw bnx2 i5000_edac edac_core i5k_amb shpchp lp parport ses enclosure aic79xx megaraid_sas
May 28 18:06:19 host2 kernel: [16516634.010711] Pid: 0, comm: swapper Not tainted 2.6.32-25-server #45-Ubuntu
May 28 18:06:19 host2 kernel: [16516634.010714] Call Trace:
May 28 18:06:19 host2 kernel: [16516634.010716] <IRQ> [<ffffffff81065f3b>] warn_slowpath_common+0x7b/0xc0
May 28 18:06:19 host2 kernel: [16516634.010726] [<ffffffff81065fe1>] warn_slowpath_fmt+0x41/0x50
May 28 18:06:19 host2 kernel: [16516634.010729] [<ffffffff8148c492>] dev_watchdog+0x262/0x270
May 28 18:06:19 host2 kernel: [16516634.010734] [<ffffffff81019103>] ? native_sched_clock+0x13/0x60
May 28 18:06:19 host2 kernel: [16516634.010739] [<ffffffff8108a225>] ? sched_clock_local+0x25/0x90
May 28 18:06:19 host2 kernel: [16516634.010742] [<ffffffff8148c230>] ? dev_watchdog+0x0/0x270
May 28 18:06:19 host2 kernel: [16516634.010746] [<ffffffff8107667b>] run_timer_softirq+0x19b/0x340
May 28 18:06:19 host2 kernel: [16516634.010750] [<ffffffff812b7ddd>] ? rb_insert_color+0x9d/0x160
May 28 18:06:19 host2 kernel: [16516634.010754] [<ffffffff8108e543>] ? ktime_get+0x63/0xe0
May 28 18:06:19 host2 kernel: [16516634.010758] [<ffffffff8106d477>] __do_softirq+0xb7/0x1e0
May 28 18:06:19 host2 kernel: [16516634.010762] [<ffffffff810934ca>] ? tick_program_event+0x2a/0x30
May 28 18:06:19 host2 kernel: [16516634.010766] [<ffffffff810132ec>] call_softirq+0x1c/0x30
May 28 18:06:19 host2 kernel: [16516634.010769] [<ffffffff81014cb5>] do_softirq+0x65/0xa0
May 28 18:06:19 host2 kernel: [16516634.010772] [<ffffffff8106d315>] irq_exit+0x85/0x90
May 28 18:06:19 host2 kernel: [16516634.010777] [<ffffffff8155f391>] smp_apic_timer_interrupt+0x71/0x9c
May 28 18:06:19 host2 kernel: [16516634.010780] [<ffffffff81012cb3>] apic_timer_interrupt+0x13/0x20
May 28 18:06:19 host2 kernel: [16516634.010782] <EOI> [<ffffffff8101a571>] ? mwait_idle+0x71/0xd0
May 28 18:06:19 host2 kernel: [16516634.010789] [<ffffffff8155cf2a>] ? atomic_notifier_call_chain+0x1a/0x20
May 28 18:06:19 host2 kernel: [16516634.010793] [<ffffffff81010e63>] ? cpu_idle+0xb3/0x110
May 28 18:06:19 host2 kernel: [16516634.010797] [<ffffffff81551fab>] ? start_secondary+0xa8/0xaa
May 28 18:06:19 host2 kernel: [16516634.0108...

Read more...

Revision history for this message
Mossroy (mossroy) wrote :

I'm not 100% sure but I do not seem to face this issue with precise alpha (kernel 3.2.0-12-generic).

I have another issue with my FreeRunner on Precise (it's not correctly recognised at startup, so NetworkManager does not find the right MAC address, does not set the fix IP adress and keeps trying DHCP on it) , but I suppose it's not related to this one.

Revision history for this message
penalvch (penalvch) wrote :

Mossroy, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/535315/comments/41 regarding this being fixed with an update. 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.

Changed in linux (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.