Bug 150098

Summary: usb-audio fails with no obvious reason
Product: [openSUSE] openSUSE 11.0 Reporter: Forgotten User --EoyBps8f <forgotten_--EoyBps8f>
Component: SoundAssignee: Takashi Iwai <tiwai>
Status: RESOLVED NORESPONSE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P3 - Medium    
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Forgotten User --EoyBps8f 2006-02-10 22:13:01 UTC 
I use a Logitech USB-headset. I regularly get warnings about:

Feb 10 20:56:14 pc192s kernel: ALSA sound/usb/usbaudio.c:1225: current rate 48000 is different from the runtime rate 8000
Feb 10 20:56:14 pc192s kernel: ALSA sound/usb/usbaudio.c:1225: current rate 8000 is different from the runtime rate 48000

But they do no harm apparently.

Yet after a while of usage, e.g. with skype, the device fails, i.e. is disabled.

A hundred or so per second of these:
Feb 10 21:54:11 pc192s kernel: ALSA sound/usb/usbaudio.c:358: frame 0 active: -84

and then:

Feb 10 21:54:11 pc192s kernel: hub 1-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
Feb 10 21:54:11 pc192s kernel: usb 1-2: USB disconnect, address 3
Feb 10 21:54:11 pc192s kernel: ALSA sound/usb/usbaudio.c:358: frame 0 active: -18
Feb 10 21:54:11 pc192s kernel: ALSA sound/usb/usbaudio.c:656: cannot submit urb (err = -19)
Feb 10 21:54:12 pc192s resmgr[4632]: set_facl() - ACL error on /dev/dsp1, acl_set_file: No such file or directory
Feb 10 21:54:12 pc192s resmgr[4632]: set_facl() - ACL error on /dev/audio1, acl_set_file: No such file or directory
Feb 10 21:54:12 pc192s resmgr[4632]: set_facl() - ACL error on /dev/mixer1, acl_set_file: No such file or directory
Feb 10 21:54:20 pc192s kernel: ALSA sound/core/pcm_lib.c:2429: capture read error (DMA or IRQ trouble?)
Feb 10 21:58:02 pc192s kernel: usb 1-2: new full speed USB device using uhci_hcd and address 4
Feb 10 21:58:02 pc192s kernel: ALSA sound/usb/usbaudio.c:1225: current rate 8000 is different from the runtime rate 48000
Feb 10 21:58:02 pc192s kernel: ALSA sound/usb/usbaudio.c:1225: current rate 8000 is different from the runtime rate 48000
Feb 10 21:58:02 pc192s kernel: input: USB HID v1.00 Device [Logitech Logitech USB Headset] on usb-0000:00:11.2-2
Feb 10 21:58:02 pc192s kernel: usb 1-1: USB disconnect, address 2
Feb 10 21:58:03 pc192s resmgr[4632]: set_facl() - ACL error on /dev/snd/pcmC1D0c, acl_set_file: No such file or directory
Feb 10 21:58:03 pc192s resmgr[4632]: set_facl() - ACL error on /dev/snd/pcmC1D0p, acl_set_file: No such file or directory
Feb 10 21:58:03 pc192s resmgr[4632]: set_facl() - ACL error on /dev/snd/controlC1, acl_set_file: No such file or directory
Feb 10 21:59:27 pc192s kernel: ALSA sound/usb/usbaudio.c:1225: current rate 48000 is different from the runtime rate 8000
Feb 10 21:59:27 pc192s kernel: ALSA sound/usb/usbaudio.c:1225: current rate 8000 is different from the runtime rate 48000

After the device got disabled, KDE was unresponsive due to kmix using 80% CPU. After I killed it, I un-plugged all USB-devices (headset and a hub with no devices attached) and plugged the headset back in. After some seconds it worked again.

Since there is a line stated in the warning-message, I thought there might be a chance to track down the bug and thus reported it.
Comment 1 Forgotten User --EoyBps8f 2008-02-29 09:07:23 UTC 
No response in over two years, I guess devs would have used the "NOREPSONSE" a long time ago.
Comment 2 Christoph Thiel 2008-04-25 14:49:58 UTC 
Closing NOREPSONSE, due to missing information for more than 21 days. Please 
feel free to reopen and provide the requested information.
Comment 3 Forgotten User --EoyBps8f 2008-04-25 23:11:17 UTC 
I know it's kind of embarrassing, but if the NEEDINFO is set to a Novell employee, you should not close the bug.
Comment 4 Andreas Jaeger 2008-10-24 08:33:05 UTC 
Sven, NEEDINFO reset is allowed for everybody.

Takashi, what do you want to do with this bug?
Comment 5 Takashi Iwai 2008-10-31 07:27:38 UTC 
No worth to tracking for the deprecated distro version.

Sven, does it still happen with the latest version?
Comment 6 Takashi Iwai 2008-12-09 07:07:28 UTC 
Resolved as NORESPONSE.
Comment 7 Forgotten User --EoyBps8f 2009-01-07 08:48:31 UTC 
Still valid for 11.0
Comment 8 Takashi Iwai 2009-01-08 10:43:39 UTC 
Well, the latest vesrion is 11.1...
Any chance to test on it?
Comment 9 Stefan Behlert 2010-07-21 09:45:52 UTC 
No response since months. Re-open once you have the requested information, thanks.