[hardy] traceback when plugging in usb-audio device

Bug #193550 reported by Martin Pool
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: linux-source-2.6.22

I just plugged a Logitech usb headset (model A-0205A) into my hardy machine and got this traceback

Feb 20 13:16:42 grace kernel: [16707.751370] sysfs: duplicate filename 'card1' can not be created
Feb 20 13:16:42 grace kernel: [16707.751375] WARNING: at /build/buildd/linux-2.6.24/fs/sysfs/dir.c:424 sysfs_add_one()
Feb 20 13:16:42 grace kernel: [16707.751379] Pid: 1689, comm: khubd Not tainted 2.6.24-8-generic #1
Feb 20 13:16:42 grace kernel: [16707.751392] [sysfs_add_one+0x9f/0xe0] sysfs_add_one+0x9f/0xe0
Feb 20 13:16:42 grace kernel: [16707.751404] [usbcore:sysfs_create_link+0x8a/0x6f0] sysfs_create_link+0x8a/0x110
Feb 20 13:16:42 grace kernel: [16707.751415] [usbcore:device_add+0x14c/0x510] device_add+0x14c/0x510
Feb 20 13:16:42 grace kernel: [16707.751424] [md_mod:kobject_init+0x29/0x210] kobject_init+0x29/0x40
Feb 20 13:16:42 grace kernel: [16707.751431] [usbcore:device_create+0x88/0xd20] device_create+0x88/0xc0
Feb 20 13:16:42 grace kernel: [16707.751438] [<f8a4ec84>] snd_card_register+0x284/0x320 [snd]
Feb 20 13:16:42 grace kernel: [16707.751457] [<f8f67261>] usb_audio_probe+0x3b1/0x8b0 [snd_usb_audio]
Feb 20 13:16:42 grace kernel: [16707.751473] [sysfs_addrm_finish+0x14/0x1c0] sysfs_addrm_finish+0x14/0x1c0
Feb 20 13:16:42 grace kernel: [16707.751487] [<f898f5a9>] usb_probe_interface+0xb9/0x140 [usbcore]
Feb 20 13:16:42 grace kernel: [16707.751512] [driver_probe_device+0x88/0x190] driver_probe_device+0x88/0x190
Feb 20 13:16:42 grace kernel: [16707.751517] [klist_next+0x55/0xb0] klist_next+0x55/0xb0
Feb 20 13:16:42 grace kernel: [16707.751525] [bus_for_each_drv+0x44/0x70] bus_for_each_drv+0x44/0x70
Feb 20 13:16:42 grace kernel: [16707.751533] [device_attach+0x86/0x90] device_attach+0x86/0x90
Feb 20 13:16:42 grace kernel: [16707.751536] [__device_attach+0x0/0x10] __device_attach+0x0/0x10
Feb 20 13:16:42 grace kernel: [16707.751542] [bus_attach_device+0x45/0x90] bus_attach_device+0x45/0x90
Feb 20 13:16:42 grace kernel: [16707.751549] [usbcore:device_add+0x418/0x510] device_add+0x418/0x510
Feb 20 13:16:42 grace kernel: [16707.751560] [<f898d4f2>] usb_set_configuration+0x392/0x5d0 [usbcore]
Feb 20 13:16:42 grace kernel: [16707.751590] [<f8995956>] generic_probe+0x76/0xb0 [usbcore]
Feb 20 13:16:42 grace kernel: [16707.751615] [<f898f363>] usb_probe_device+0x33/0x40 [usbcore]
Feb 20 13:16:42 grace kernel: [16707.751631] [driver_probe_device+0x88/0x190] driver_probe_device+0x88/0x190
Feb 20 13:16:42 grace kernel: [16707.751638] [klist_next+0x55/0xb0] klist_next+0x55/0xb0
Feb 20 13:16:42 grace kernel: [16707.751645] [bus_for_each_drv+0x44/0x70] bus_for_each_drv+0x44/0x70
Feb 20 13:16:42 grace kernel: [16707.751653] [device_attach+0x86/0x90] device_attach+0x86/0x90
Feb 20 13:16:42 grace kernel: [16707.751656] [__device_attach+0x0/0x10] __device_attach+0x0/0x10
Feb 20 13:16:42 grace kernel: [16707.751661] [bus_attach_device+0x45/0x90] bus_attach_device+0x45/0x90
Feb 20 13:16:42 grace kernel: [16707.751669] [usbcore:device_add+0x418/0x510] device_add+0x418/0x510
Feb 20 13:16:42 grace kernel: [16707.751679] [<f89882c6>] usb_new_device+0x56/0xa0 [usbcore]
Feb 20 13:16:42 grace kernel: [16707.751701] [<f8989a67>] hub_thread+0x687/0xcb0 [usbcore]
Feb 20 13:16:42 grace kernel: [16707.751721] [ext3:rb_erase+0x15e/0x310] rb_erase+0x15e/0x280
Feb 20 13:16:42 grace kernel: [16707.751736] [<c0141bb0>] autoremove_wake_function+0x0/0x40
Feb 20 13:16:42 grace kernel: [16707.751744] [<f89893e0>] hub_thread+0x0/0xcb0 [usbcore]
Feb 20 13:16:42 grace kernel: [16707.751763] [kthread+0x42/0x70] kthread+0x42/0x70
Feb 20 13:16:42 grace kernel: [16707.751766] [kthread+0x0/0x70] kthread+0x0/0x70
Feb 20 13:16:42 grace kernel: [16707.751771] [kernel_thread_helper+0x7/0x10] kernel_thread_helper+0x7/0x10
Feb 20 13:16:42 grace kernel: [16707.751778] =======================

Tags: cft-2.6.27
Revision history for this message
Martin Pool (mbp) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Martin,

This report was filed against the Gutsty 2.6.22 kernel but from your comment and the stack trace output it seems you are indeed running Hardy 2.6.24. I'm changing the source package name over to 'linux' which is the Hardy kernel source package (the naming convention changed from linux-source-2.6.xx to just linux at the beginning of Hardy). If you can, could you verify if this is still an issue on the latest 2.6.24-11 kernel? If so, care to attach the full dmesg output which captures the error messages. Thanks!

Changed in linux-source-2.6.22:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Martin Pool (mbp) wrote : Re: [Bug 193550] Re: [hardy] traceback when plugging in usb-audio device

This was still a problem when I tried it about a month ago on hardy.
I've recently upgraded that machine to intrepid and will try to
re-test.

--
Martin <http://launchpad.net/~mbp/>

Revision history for this message
Martin Pool (mbp) wrote :

working ok for me in 2.6.27-3-generic

Changed in linux:
status: Incomplete → Fix Committed
Revision history for this message
C Filorux (breakfast) wrote :
Download full text (4.1 KiB)

By way of confirmation, I'm running 2.6.24-19-generic. While playing sound through the headset, I bumped the connector, and got the crash below - this is unusual on my system. The device is .. Bus 004 Device 007: ID 046d:0a0c Logitech, Inc. dmesg says this - from when I originally plugged it in (time+1021), to when I bumped it (time+2176), to when I plugged it in again (in a different slot) (time+2184).:

[ 1021.218771] usb 4-1: USB disconnect, address 3
[ 1021.298316] usb 4-1: new full speed USB device using uhci_hcd and address 4
[ 1021.331405] usb 4-1: configuration #1 chosen from 1 choice
[ 1021.409206] input: Logitech Logitech USB Headset as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1:1.3/input/input10
[ 1021.449868] input,hidraw0: USB HID v1.00 Device [Logitech Logitech USB Headset] on usb-0000:00:1d.0-1
[ 2176.936148] usb 4-1: USB disconnect, address 4
[ 2177.224556] usb 4-1: new full speed USB device using uhci_hcd and address 5
[ 2177.437552] usb 4-1: configuration #1 chosen from 1 choice
[ 2177.512373] sysfs: duplicate filename 'card1' can not be created
[ 2177.512379] WARNING: at /build/buildd/linux-2.6.24/fs/sysfs/dir.c:424 sysfs_add_one()
[ 2177.512383] Pid: 1671, comm: khubd Not tainted 2.6.24-19-generic #1
[ 2177.512404] [<c01d748f>] sysfs_add_one+0x9f/0xe0
[ 2177.512418] [<c01d827a>] sysfs_create_link+0x8a/0x110
[ 2177.512431] [<c028088c>] device_add+0x14c/0x510
[ 2177.512441] [<c0215619>] kobject_init+0x29/0x40
[ 2177.512450] [<c0280f08>] device_create+0x88/0xc0
[ 2177.512458] [<f8a5dc84>] snd_card_register+0x284/0x320 [snd]
[ 2177.512478] [<f8ba0261>] usb_audio_probe+0x3b1/0x8b0 [snd_usb_audio]
[ 2177.512497] [<c01d7714>] sysfs_addrm_finish+0x14/0x1c0
[ 2177.512513] [<f88c05d9>] usb_probe_interface+0xb9/0x140 [usbcore]
[ 2177.512544] [<c0282858>] driver_probe_device+0x88/0x190
[ 2177.512550] [<c0319f35>] klist_next+0x55/0xb0
[ 2177.512559] [<c0281b54>] bus_for_each_drv+0x44/0x70
[ 2177.512568] [<c0282a26>] device_attach+0x86/0x90
[ 2177.512571] [<c0282960>] __device_attach+0x0/0x10
[ 2177.512578] [<c0281ac5>] bus_attach_device+0x45/0x90
[ 2177.512586] [<c0280b58>] device_add+0x418/0x510
[ 2177.512597] [<f88be522>] usb_set_configuration+0x392/0x5d0 [usbcore]
[ 2177.512633] [<f88c6b06>] generic_probe+0x76/0xb0 [usbcore]
[ 2177.512663] [<f88c0393>] usb_probe_device+0x33/0x40 [usbcore]
[ 2177.512679] [<c0282858>] driver_probe_device+0x88/0x190
[ 2177.512692] [<c0319f35>] klist_next+0x55/0xb0
[ 2177.512703] [<c0281b54>] bus_for_each_drv+0x44/0x70
[ 2177.512712] [<c0282a26>] device_attach+0x86/0x90
[ 2177.512715] [<c0282960>] __device_attach+0x0/0x10
[ 2177.512721] [<c0281ac5>] bus_attach_device+0x45/0x90
[ 2177.512729] [<c0280b58>] device_add+0x418/0x510
[ 2177.512740] [<f88b92f6>] usb_new_device+0x56/0xa0 [usbcore]
[ 2177.512768] [<f88baa97>] hub_thread+0x687/0xcb0 [usbcore]
[ 2177.512805] [<c0140c40>] autoremove_wake_function+0x0/0x40
[ 2177.512816] [<f88ba410>] hub_thread+0x0/0xcb0 [usbcore]
[ 2177.512839] [<c0140982>] kthread+0x42/0x70
[ 2177.512843] [<c0140940>] kthread+0x0/0x70
[ 2177.512849] [<c0105677>] kernel_thread_helper+0x7/0x10
[ 2177.512858] =======================
[ 2177.52061...

Read more...

Revision history for this message
Martin Pool (mbp) wrote :

This is consistently ok for me in intrepid.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Since Martin is the original bug reporter, I'm marking this "Fix Released" for Intrepid. Thanks.

Changed in linux:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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