April 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1184291] New: module hidp should get loaded after module bluetooth for proper bluetooth audio

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1184291 Bug ID: 1184291 Summary: module hidp should get loaded after module bluetooth for proper bluetooth audio Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: webforen(a)posteo.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Problem: You want to connect a bluetooth HiFi headset/headphone and enjoy high quality audio using the a2dp_sink with pulseaudio, but you get only low quality, handset quality audio, because a2dp_sink is not available. How to reproduce: Connect your bt HiFi headphone, while module hidp is NOT loaded and invoke "pactl list" from pulseaudio utils, you may see this line: a2dp_sink: High Fidelity Playback (A2DP-target) (sinks: 1, sources: 0, priority: 40, available: no) ==> "available: no" this tells you, A2DP is not available for your bt headphone Root of the problem: In some cases the hidp module does not get automatically loaded, to me this seems the case with laptops that have integrated bluetooth. The module bluetooth gets loaded, but not hidp. When using an external USB bluetooth dongle, manually connected, hidp *may* get loaded. Solution: It must be sure, that module hidp gets loaded after module bluetooth was loaded Without module hidp there will be no A2DP audio over bluetooth. You may consider to add this line to /etc/modprobe.d/50-bluetooth.conf softdep bluetooth post: hidp Checking the problem is solved by suggested solution: After hidp was loaded, connect your HiFi bt headset/headphone again and invoke "pactl list" you should then this: a2dp_sink: High Fidelity Playback (A2DP-Ziel) (sinks: 1, sources: 0, priority: 40, available: yes) ==> "available: yes" is what you want, A2DP audio now works -- You are receiving this mail because: You are the assignee for the bug.

1 year, 4 months

1
4
0 0

[Bug 1184252] New: Focusrite Scarlett 2i2 (3rd gen) stops working in latest default kernel (5.11.11-1.1.gdbc4a02.x86_64)

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1184252 Bug ID: 1184252 Summary: Focusrite Scarlett 2i2 (3rd gen) stops working in latest default kernel (5.11.11-1.1.gdbc4a02.x86_64) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: peter.terpstra(a)mail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Dear people, Just want to make this announcement, discovered that the latest kernel upgrade, gave me this message in /var/log/messages 2021-03-31T16:55:01.192647-07:00 chenrezi kernel: [ 200.463947] usb 1-3: USB disconnect, device number 6 2021-03-31T16:55:09.980751-07:00 chenrezi kernel: [ 209.251375] usb 1-3: new high-speed USB device number 7 using xhci_hcd 2021-03-31T16:55:10.128643-07:00 chenrezi kernel: [ 209.400167] usb 1-3: New USB device found, idVendor=1235, idProduct=8210, bcdDevice= 5.ff 2021-03-31T16:55:10.128680-07:00 chenrezi kernel: [ 209.400181] usb 1-3: New USB device strings: Mfr=1, Product=3, SerialNumber=2 2021-03-31T16:55:10.128686-07:00 chenrezi kernel: [ 209.400186] usb 1-3: Product: Scarlett 2i2 USB 2021-03-31T16:55:10.128689-07:00 chenrezi kernel: [ 209.400191] usb 1-3: Manufacturer: Focusrite 2021-03-31T16:55:10.128692-07:00 chenrezi kernel: [ 209.400195] usb 1-3: SerialNumber: Y81V7690CABC66 2021-03-31T16:55:10.156652-07:00 chenrezi kernel: [ 209.429102] usb 1-3: Focusrite Scarlett Gen 2/3 Mixer Driver enabled pid=0x8210 2021-03-31T16:55:10.156695-07:00 chenrezi kernel: [ 209.429759] usb 1-3: Device has no software configuration 2021-03-31T16:55:10.156701-07:00 chenrezi kernel: [ 209.429940] usb 1-3: Scarlett Gen 2 USB response result cmd 800000 was 16 expected 19 2021-03-31T16:55:10.156705-07:00 chenrezi kernel: [ 209.429997] snd-usb-audio: probe of 1-3:1.0 failed with error -22 2021-03-31T16:55:10.166431-07:00 chenrezi mtp-probe: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3" 2021-03-31T16:55:10.167394-07:00 chenrezi mtp-probe: bus: 1, device: 7 was not an MTP device In kernel 5.11.10-2.gfa5dcf1-default it was: 2021-03-31T16:48:26.892232-07:00 chenrezi kernel: [ 388.071580] usb 1-3: new high-speed USB device number 7 using xhci_hcd 2021-03-31T16:48:27.040176-07:00 chenrezi kernel: [ 388.220024] usb 1-3: New USB device found, idVendor=1235, idProduct=8210, bcdDevice= 5.ff 2021-03-31T16:48:27.040208-07:00 chenrezi kernel: [ 388.220037] usb 1-3: New USB device strings: Mfr=1, Product=3, SerialNumber=2 2021-03-31T16:48:27.040211-07:00 chenrezi kernel: [ 388.220043] usb 1-3: Product: Scarlett 2i2 USB 2021-03-31T16:48:27.040213-07:00 chenrezi kernel: [ 388.220048] usb 1-3: Manufacturer: Focusrite 2021-03-31T16:48:27.040215-07:00 chenrezi kernel: [ 388.220051] usb 1-3: SerialNumber: Y81V7690CABC66 2021-03-31T16:48:27.066796-07:00 chenrezi mtp-probe: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3" 2021-03-31T16:48:27.067211-07:00 chenrezi mtp-probe: bus: 1, device: 7 was not an MTP device 2021-03-31T16:48:27.106776-07:00 chenrezi systemd-udevd[3225]: Process '/usr/sbin/alsactl restore 1' failed with exit code 99. 2021-03-31T16:48:27.110835-07:00 chenrezi systemd[2119]: Reached target Sound Card. And the Focus Scarlett Gen 3, still works on this kernel, also on the 5.3.18-lp152.66.2.x86_64 kernel. Please let me know if you need more information. Kindly, Peter -- You are receiving this mail because: You are the assignee for the bug.

1 year, 4 months

1
8
0 0

[Bug 1184074] New: switching video output from nvidia to hd530, system won't reboot/shutdown anymore

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1184074 Bug ID: 1184074 Summary: switching video output from nvidia to hd530, system won't reboot/shutdown anymore Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: pandre.x(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 847740 --> http://bugzilla.opensuse.org/attachment.cgi?id=847740&action=edit output trying to reboot the system I installed the whole system with an Nvidia GT710. I know decided to use the internal gpu (HD530) and get ride of the nvidia. The system stopped to switch off and reboot properly. I have to do it brutally every single time. It seems it hangs without a particular reason. Switching back the HDMI cable to the nvidia, everything goes back to normal. -- You are receiving this mail because: You are the assignee for the bug.

1 year, 4 months

1
9
0 0

[Bug 1183872] New: Regression: System hang when connecting HMDI with i915

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1183872 Bug ID: 1183872 Summary: Regression: System hang when connecting HMDI with i915 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: milanfix(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 847526 --> http://bugzilla.opensuse.org/attachment.cgi?id=847526&action=edit Hardware info This bug doesn't occur on Leap 15.2 but it happens very consistently on Tumbleweed. How to reproduce: 1) Connect an external screen by HDMI *after* turning on the computer Expected behavior: The screen is recognized Actual behavior: Both screen go blank and the system is unusable If the screen is connected before turning on the computer then it will work as expected, but if it's re-plugged it will still hang. This isn't a desktop environment specific issue and it happens even without any X server at all. Speculation: This is most likely a kernel issue, specifically a bug in the i915 driver. If so, it was introduced between Linux 5.3 and 5.11. Things that were tried: i915.enable_psr=0 still, intel_idle.max_cstate=1 and i915.enable_dc=0 where all tried but the bug still occur. Tried to get a dump with kdump but nothing was written in /var/crash. Any tips to debug this issue so it can be narrowed down would be really helpful. I'm currently trying to find a way to test every kernel from 5.3 to 5.11 without having to actually compile them on tumbleweed, so it can, without a doubt confirmed it's a kernel issue and also find the version on which the regression was introduced. -- You are receiving this mail because: You are the assignee for the bug.

1 year, 4 months

1
20
0 0

2022

2021

2020

openSUSE Kernel Bugs April 2021