8139too always crash

Bug #449104 reported by DjMix
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

[ 862.874941] ------------[ cut here ]------------
[ 862.875016] WARNING: at /build/buildd/linux-2.6.31/net/sched/sch_generic.c:246 dev_watchdog+0x1f6/0x210()
[ 862.875033] Hardware name: System Name
[ 862.875045] NETDEV WATCHDOG: eth0 (8139too): transmit queue 0 timed out
[ 862.875057] Modules linked in: nfs lockd nfs_acl auth_rpcgss sunrpc tdfx drm agpgart ppdev iptable_filter ip_tables x_tables i2c_voodoo3 i2c_algo_bit lp parport binfmt_misc usbhid 8139too 8139cp mii
[ 862.875168] Pid: 0, comm: swapper Not tainted 2.6.31-13-generic #43-Ubuntu
[ 862.875181] Call Trace:
[ 862.875227] [<c014085d>] warn_slowpath_common+0x6d/0xa0
[ 862.875248] [<c04abd86>] ? dev_watchdog+0x1f6/0x210
[ 862.875267] [<c04abd86>] ? dev_watchdog+0x1f6/0x210
[ 862.875287] [<c01408d6>] warn_slowpath_fmt+0x26/0x30
[ 862.875306] [<c04abd86>] dev_watchdog+0x1f6/0x210
[ 862.875338] [<c01536cb>] ? insert_work+0x5b/0xa0
[ 862.875363] [<c01244a8>] ? default_spin_lock_flags+0x8/0x10
[ 862.875403] [<c056b48a>] ? _spin_lock_irqsave+0x2a/0x40
[ 862.875423] [<c0153a61>] ? __queue_work+0x31/0x40
[ 862.875460] [<c014b8a7>] run_timer_softirq+0x117/0x200
[ 862.875480] [<c04abb90>] ? dev_watchdog+0x0/0x210
[ 862.875500] [<c0146aa0>] __do_softirq+0x90/0x1a0
[ 862.875518] [<c01244a8>] ? default_spin_lock_flags+0x8/0x10
[ 862.875538] [<c056b48a>] ? _spin_lock_irqsave+0x2a/0x40
[ 862.875579] [<c0106882>] ? enable_8259A_irq+0x42/0x60
[ 862.875597] [<c0146bed>] do_softirq+0x3d/0x40
[ 862.875615] [<c0146d2d>] irq_exit+0x5d/0x70
[ 862.875632] [<c0104e00>] do_IRQ+0x50/0xc0
[ 862.875652] [<c0103990>] common_interrupt+0x30/0x40
[ 862.875688] [<c0123835>] ? native_safe_halt+0x5/0x10
[ 862.875709] [<c010a146>] default_idle+0x46/0xd0
[ 862.875728] [<c010202c>] cpu_idle+0x8c/0xd0
[ 862.875753] [<c0559e65>] rest_init+0x55/0x60
[ 862.875779] [<c07858cd>] start_kernel+0x2e6/0x2ec
[ 862.875798] [<c0785406>] ? unknown_bootoption+0x0/0x1ab
[ 862.875817] [<c078507c>] i386_start_kernel+0x7c/0x83
[ 862.875832] ---[ end trace 9ca8154d2a20aa5b ]---

ProblemType: Bug
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: aplay: device_list:223: no soundcards found...
Architecture: i386
ArecordDevices: arecord: device_list:223: no soundcards found...
Date: Mon Oct 12 00:36:21 2009
DistroRelease: Ubuntu 9.10
Lsusb:
 Bus 001 Device 002: ID 0ace:1201 ZyDAS 802.11b WiFi
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System Manufacturer System Name
Package: linux-image-2.6.31-13-generic 2.6.31-13.44
PciMultimedia:

ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-13-generic root=UUID=9227e5a7-6fdd-4ea6-818e-e2cfa3374778 ro quiet splash noapic acpi=off i8042.noloop
ProcEnviron:
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
SourcePackage: linux
Uname: Linux 2.6.31-13-generic i586
XsessionErrors:
 (gnome-settings-daemon:1229): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1229): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:1262): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1271): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1445): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
dmi.bios.date: 04/28/99
dmi.bios.vendor: Award Software, Inc.
dmi.bios.version: #401A0-0207-2
dmi.board.name: P/I-P55T2P4
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: REV 3.X
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 2
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvr#401A0-0207-2:bd04/28/99:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP/I-P55T2P4:rvrREV3.X:cvnChassisManufacture:ct2:cvrChassisVersion:
dmi.product.name: System Name
dmi.product.version: System Version
dmi.sys.vendor: System Manufacturer

Revision history for this message
DjMix (ilario-gottardello) wrote :
Revision history for this message
^_Pepe_^ (jose-angel-fernandez-freire) wrote :

Hi,

Please, can you tell us whether this is still an issue for you?

If so, please, can you include new logs with last kernel, 2.6.31-16? You just only have to run the following command from a
Terminal (Applications->Accessories->Terminal) while running Karmic. It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 449104.

I'd also encourage you to test last kernel version (Lucid upstream) 2.6.32 located on http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32/ and come back here with your results.

Thanks in advance

tags: added: karmic
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi DjMix,

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? Can you try 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 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 449104

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.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
DjMix (ilario-gottardello) wrote :

It turned out it was a conflict with another card.

bing (ingrambj)
Changed in linux (Ubuntu):
status: Incomplete → Invalid
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.