http://bugzilla.suse.com/show_bug.cgi?id=979049 http://bugzilla.suse.com/show_bug.cgi?id=979049#c1 --- Comment #1 from Dr. Werner Fink --- Created attachment 676138 --> http://bugzilla.suse.com/attachment.cgi?id=676138&action=edit alsa-info.txt The output of alsa-info.sh -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=979049 http://bugzilla.suse.com/show_bug.cgi?id=979049#c3 --- Comment #3 from Dr. Werner Fink --- Created attachment 676159 --> http://bugzilla.suse.com/attachment.cgi?id=676159&action=edit yet an other kernel log -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=979049 http://bugzilla.suse.com/show_bug.cgi?id=979049#c5 --- Comment #5 from Dr. Werner Fink --- (In reply to Takashi Iwai from comment #4) Could be ... and indeed I had only once for a second some audio with aptX but afterwards the device becomes disconnected to be (re)connected again. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=979049 http://bugzilla.suse.com/show_bug.cgi?id=979049#c7 --- Comment #7 from Dr. Werner Fink --- Just tried modprobe -r usbhid modprobe usbhid quirks=0x1395:0x002c:0x4 but see or better hear the same problem, as far as I try to connect the headphone to the Sennheiser BTD 500 USB I hear an endless loop of lost connection and connected reported by the headphone ... and the kernel log shows: [770940.602590] usb 5-1: new full-speed USB device number 49 using uhci_hcd [770941.597993] usb 5-1: New USB device found, idVendor=1395, idProduct=002c [770941.597999] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [770941.598002] usb 5-1: Product: Sennheiser BTD 500 USB [770947.699928] usb 5-1: USB disconnect, device number 49 [770948.007749] usb 5-1: new full-speed USB device number 50 using uhci_hcd [770949.001057] usb 5-1: New USB device found, idVendor=1395, idProduct=002c [770949.001062] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [770949.001065] usb 5-1: Product: Sennheiser BTD 500 USB [770956.376621] usb 5-1: USB disconnect, device number 50 [770956.748474] usb 5-1: new full-speed USB device number 51 using uhci_hcd [770957.741558] usb 5-1: New USB device found, idVendor=1395, idProduct=002c [770957.741564] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [770957.741567] usb 5-1: Product: Sennheiser BTD 500 USB [770965.053390] usb 5-1: USB disconnect, device number 51 [770965.361184] usb 5-1: new full-speed USB device number 52 using uhci_hcd [770966.330191] usb 5-1: New USB device found, idVendor=1395, idProduct=002c [770966.330196] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [770966.330199] usb 5-1: Product: Sennheiser BTD 500 USB [770972.990353] usb 5-1: USB disconnect, device number 52 [770973.422178] usb 5-1: new full-speed USB device number 53 using uhci_hcd [770984.529970] usb 5-1: new full-speed USB device number 54 using uhci_hcd [770985.530582] usb 5-1: New USB device found, idVendor=1395, idProduct=002c [770985.530587] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [770985.530590] usb 5-1: Product: Sennheiser BTD 500 USB [770991.331452] usb 5-1: USB disconnect, device number 54 [770991.735249] usb 5-1: new full-speed USB device number 55 using uhci_hcd [770992.734862] usb 5-1: New USB device found, idVendor=1395, idProduct=002c [770992.734864] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [770992.734866] usb 5-1: Product: Sennheiser BTD 500 USB [770999.016490] usb 5-1: USB disconnect, device number 55 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=979049 http://bugzilla.suse.com/show_bug.cgi?id=979049#c8 --- Comment #8 from Dr. Werner Fink --- Same for modprobe usbhid quirks=0x1395:0x002c:0x6 that is that usbhid does not touch (AFAICS from linux/include/linux/hid.h) ... does this mean that this could be more a ALSA problem: May 18 10:34:03 boole kernel: usb 5-1: USB disconnect, device number 57 May 18 10:34:03 boole kernel: usb 5-1: new full-speed USB device number 58 using uhci_hcd May 18 10:34:04 boole kernel: usb 5-1: New USB device found, idVendor=1395, idProduct=002c May 18 10:34:04 boole kernel: usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 May 18 10:34:04 boole kernel: usb 5-1: Product: Sennheiser BTD 500 USB May 18 10:34:06 boole pulseaudio[2294]: [pulseaudio] sink.c: Default and alternate sample rates are the same. May 18 10:34:06 boole rtkit-daemon[2295]: Supervising 3 threads of 1 processes of 1 users. May 18 10:34:06 boole rtkit-daemon[2295]: Successfully made thread 15904 of process 2294 (/usr/bin/pulseaudio) owned by 'werner' RT at priority 5. May 18 10:34:06 boole rtkit-daemon[2295]: Supervising 4 threads of 1 processes of 1 users. May 18 10:34:11 boole pulseaudio[2294]: [alsa-sink-USB Audio] alsa-util.c: Got POLLNVAL from ALSA May 18 10:34:11 boole pulseaudio[2294]: [alsa-sink-USB Audio] alsa-util.c: Could not recover from POLLERR|POLLNVAL|POLLHUP with snd_pcm_prepare(): No such device May 18 10:34:11 boole kernel: usb 5-1: USB disconnect, device number 58 that is that ALSA does not detect the headphone I/O if the headphone is connected to the Bluetooth aptX device? Is there any way to increase debug output of ALSA in the kernel as well as of the ALSA user space API? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=979049 http://bugzilla.suse.com/show_bug.cgi?id=979049#c10 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(werner@suse.com) | --- Comment #10 from Dr. Werner Fink --- (In reply to Oliver Neukum from comment #9) OK ... takes some minutes ... now with usbcore.autosuspend=-1 ... same result. Now with quirks=0x1395:0x002c:0x6 ... same result. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=979049 http://bugzilla.suse.com/show_bug.cgi?id=979049#c12 --- Comment #12 from Dr. Werner Fink --- Sound status changes if headphone causes such a disconnect/connected loop boole:~ # cat /proc/asound/card1/pcm0p/sub0/status cat: /proc/asound/card1/pcm0p/sub0/status: No such file or directory boole:~ # cat /proc/asound/card1/pcm0p/sub0/status closed boole:~ # cat /proc/asound/card1/pcm0p/sub0/status state: RUNNING owner_pid : 2700 trigger_time: 7861.302359409 tstamp : 7861.700180974 delay : 4941 avail : 0 avail_max : 0 ----- hw_ptr : 19200 appl_ptr : 23997 boole:~ # cat /proc/asound/card1/pcm0p/info card: 1 device: 0 subdevice: 0 stream: PLAYBACK id: USB Audio name: USB Audio subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 boole:~ # cat /proc/asound/card1/pcm0p/info card: 1 device: 0 subdevice: 0 stream: PLAYBACK id: USB Audio name: USB Audio subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 boole:~ # cat /proc/asound/card1/pcm0p/info cat: /proc/asound/card1/pcm0p/info: No such file or directory boole:~ # cat /proc/asound/card1/pcm0p/sub0/hw_params cat: /proc/asound/card1/pcm0p/sub0/hw_params: No such file or directory boole:~ # cat /proc/asound/card1/pcm0p/sub0/hw_params closed boole:~ # cat /proc/asound/card1/pcm0p/sub0/hw_params access: MMAP_INTERLEAVED format: S16_LE subformat: STD channels: 2 rate: 48000 (48000/1) period_size: 1199 buffer_size: 4797 boole:~ # cat /proc/asound/card1/pcm0p/sub0/sw_params tstamp_mode: ENABLE period_step: 1 avail_min: 1199 start_threshold: 18446744073709551615 stop_threshold: 5400941853124067328 silence_threshold: 0 silence_size: 0 boundary: 5400941853124067328 boole:~ # cat /proc/asound/card1/pcm0p/sub0/sw_params closed boole:~ # cat /proc/asound/card1/pcm0p/sub0/sw_params cat: /proc/asound/card1/pcm0p/sub0/sw_params: No such file or directory -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=979049 http://bugzilla.suse.com/show_bug.cgi?id=979049#c14 --- Comment #14 from Dr. Werner Fink --- Same problem with latest kernel 4.1.21-14-default -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=979049 http://bugzilla.suse.com/show_bug.cgi?id=979049#c16 --- Comment #16 from Takashi Iwai --- Note that there is no BT audio support in ALSA at all... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=979049 http://bugzilla.suse.com/show_bug.cgi?id=979049#c18 --- Comment #18 from Takashi Iwai --- (In reply to Dr. Werner Fink from comment #17)

(In reply to Takashi Iwai from comment #16)

I've bought this stick because a) it has a builtin BT audio support (A"DP as well as aptX, that is nothing to do for alsa) and b) it had worked in past with older kernel/alsa version (compare with comment #2). The question rises: why does now not work with current kernel/alsa version? Is there any way to cause alsa usb driver to wait on BTD USB device currently connecting to the headphone up to the point where it is ready ... currently alsa reports POLLNVAL to pulseaudio:

pulseaudio[2112]: [alsa-sink-USB Audio] alsa-util.c: Got POLLNVAL from ALSA pulseaudio[2112]: [alsa-sink-USB Audio] alsa-util.c: Could not recover from POLLERR|POLLNVAL|POLLHUP with snd_pcm_prepare(): No such device

As the error indicate, PA is likely trying to access to the stale device that has been reset and thus virtually disconnected. At the reconnect, the USB-audio driver registers as another sound card. Maybe PA is confused for the resume recovery while the device itself got lost. You can try the older kernel on your Leap 42.1 system to confirm that it's a kernel side regression, too. -- You are receiving this mail because: You are on the CC list for the bug.