January 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1181104] Unplugging TeVII DVB-S2 USB adapter crashes kernel
by bugzilla_noreply＠suse.com 20 Jan '21

20 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1181104 https://bugzilla.suse.com/show_bug.cgi?id=1181104#c12 --- Comment #12 from Takashi Iwai <tiwai(a)suse.com> --- Thanks, I'm going to submit the fix. Actually the fix patch contains also the possible memory leak fixes, and I'm considering whether to split the patch or not. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180404] New: high idle power consumption of amd gpu 5700xt with kernel 5.10.1
by bugzilla_noreply＠suse.com 19 Jan '21

19 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180404 Bug ID: 1180404 Summary: high idle power consumption of amd gpu 5700xt with kernel 5.10.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PC OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: benoit.monin(a)gmx.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On opensuse tumbleweed with kernel 5.10.1, the idle power consumption of my AMD graphic card (5700xt navi 10) increased from 8W to 29W over previous kernel versions. This is annoying as the graphic card periodically starts and stops the fan to deal with the increased temperature while simply displaying the desktop. I only have one monitor attached (1920x1200@60Hz) but the VRAM clock is now set to 850MHz all the time, while it was as 100MHz with earlier kernels. Is there any way to revert to the old behaviour? With 5.10.1-1-default: cat /sys/kernel/debug/dri/0/amdgpu_pm_info GFX Clocks and Power: 875 MHz (MCLK) 800 MHz (SCLK) 1300 MHz (PSTATE_SCLK) 625 MHz (PSTATE_MCLK) 725 mV (VDDGFX) 29.0 W (average GPU) GPU Temperature: 52 C GPU Load: 0 % MEM Load: 0 % SMC Feature Mask: 0x00000623a3ddaffb VCN: Disabled Clock Gating Flags Mask: 0x38099f05 Graphics Medium Grain Clock Gating: On Graphics Medium Grain memory Light Sleep: Off Graphics Coarse Grain Clock Gating: On Graphics Coarse Grain memory Light Sleep: Off Graphics Coarse Grain Tree Shader Clock Gating: Off Graphics Coarse Grain Tree Shader Light Sleep: Off Graphics Command Processor Light Sleep: Off Graphics Run List Controller Light Sleep: Off Graphics 3D Coarse Grain Clock Gating: Off Graphics 3D Coarse Grain memory Light Sleep: Off Memory Controller Light Sleep: On Memory Controller Medium Grain Clock Gating: On System Direct Memory Access Light Sleep: On System Direct Memory Access Medium Grain Clock Gating: On Bus Interface Medium Grain Clock Gating: On Bus Interface Light Sleep: On Unified Video Decoder Medium Grain Clock Gating: Off Video Compression Engine Medium Grain Clock Gating: Off Host Data Path Light Sleep: On Host Data Path Medium Grain Clock Gating: On Digital Right Management Medium Grain Clock Gating: Off Digital Right Management Light Sleep: Off Rom Medium Grain Clock Gating: Off Data Fabric Medium Grain Clock Gating: Off Address Translation Hub Medium Grain Clock Gating: On Address Translation Hub Light Sleep: On With 5.9.14-1-default: cat /sys/kernel/debug/dri/0/amdgpu_pm_info Clock Gating Flags Mask: 0x38099f05 Graphics Medium Grain Clock Gating: On Graphics Medium Grain memory Light Sleep: Off Graphics Coarse Grain Clock Gating: On Graphics Coarse Grain memory Light Sleep: Off Graphics Coarse Grain Tree Shader Clock Gating: Off Graphics Coarse Grain Tree Shader Light Sleep: Off Graphics Command Processor Light Sleep: Off Graphics Run List Controller Light Sleep: Off Graphics 3D Coarse Grain Clock Gating: Off Graphics 3D Coarse Grain memory Light Sleep: Off Memory Controller Light Sleep: On Memory Controller Medium Grain Clock Gating: On System Direct Memory Access Light Sleep: On System Direct Memory Access Medium Grain Clock Gating: On Bus Interface Medium Grain Clock Gating: On Bus Interface Light Sleep: On Unified Video Decoder Medium Grain Clock Gating: Off Video Compression Engine Medium Grain Clock Gating: Off Host Data Path Light Sleep: On Host Data Path Medium Grain Clock Gating: On Digital Right Management Medium Grain Clock Gating: Off Digital Right Management Light Sleep: Off Rom Medium Grain Clock Gating: Off Data Fabric Medium Grain Clock Gating: Off Address Translation Hub Medium Grain Clock Gating: On Address Translation Hub Light Sleep: On GFX Clocks and Power: 100 MHz (MCLK) 800 MHz (SCLK) 1300 MHz (PSTATE_SCLK) 625 MHz (PSTATE_MCLK) 750 mV (VDDGFX) 8.0 W (average GPU) GPU Temperature: 35 C GPU Load: 0 % MEM Load: 0 % SMC Feature Mask: 0x00000623a3ddaffb VCN: Disabled -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1181133] New: Logitech QuickCam Zoom (pwc) no longer working on TW 20210115
by bugzilla_noreply＠suse.com 19 Jan '21

19 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1181133 Bug ID: 1181133 Summary: Logitech QuickCam Zoom (pwc) no longer working on TW 20210115 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: javier(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Today I have upgraded a PC from TW 20201218 to TW 20210115. Unfortunately, the Logitech QuickCam Zoom plugged to it is no longer working. All I get is a black screen. Tested on Zoom and Firefox. pwc: Failed to allocate urb buffer 0 It worked fine before. I assume it has something to do with the new kernel. kernel-default-5.9.14-1.2.x86_64: OK kernel-default-5.10.7-1.2.x86_64: NON-OK Workaround: boot up with the previous kernel. lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 13d3:3414 IMC Networks Bluetooth Radio Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader Bus 001 Device 007: ID 046d:08b3 Logitech, Inc. QuickCam Zoom Bus 001 Device 006: ID 1a81:1004 Holtek Semiconductor, Inc. Wireless Dongle 2.4 GHZ HT82D40REW Bus 001 Device 004: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub hwinfo --cam 01: USB 00.2: 10f00 Camera [Created at usb.122] Unique ID: cOn9.AN_e7XL7ryA Parent ID: cLrx.d7FDLX76qXB SysFS ID: /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2 SysFS BusID: 1-2.3:1.2 Hardware Class: camera Model: "Logitech QuickCam Zoom" Hotplug: USB Vendor: usb 0x046d "Logitech, Inc." Device: usb 0x08b3 "QuickCam Zoom" Driver: "snd-usb-audio" Driver Modules: "snd_usb_audio" Speed: 12 Mbps Module Alias: "usb:v046Dp08B3d0000dc00dsc00dp00ic01isc02ip00in02" Driver Info #0: Driver Status: pwc is active Driver Activation Cmd: "modprobe pwc" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #3 (Hub) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1181104] New: Unplugging TeVII DVB-S2 USB adapter crashes kernel
by bugzilla_noreply＠suse.com 19 Jan '21

19 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1181104 Bug ID: 1181104 Summary: Unplugging TeVII DVB-S2 USB adapter crashes kernel Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: seife(a)novell.slipkontur.de QA Contact: qa-bugs(a)suse.de CC: oneukum(a)suse.com Found By: --- Blocker: --- Created attachment 845254 --> http://bugzilla.opensuse.org/attachment.cgi?id=845254&action=edit dmesg after finally crashing at third unplug cycle Recently I plugged a seldom-used TeVii S660 DVB-S2 Adapter into my laptop and after undocking found a kernel oops. I tracked this down to "Last working Kernel 4.17", even tried to bisect it but was not successful (ended up in an obviously unrelated commit). This is probably some kind of race condition, since reproducing in a KVM VM (with usb passthroug) sometimes only crashes after a few tries. On real hardware it crashes pretty reliably for me, this is why I prefer to test this in a VM :-) See attached dmesg of the oopsed kenrel. I can try whatever you deem useful :-) -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1181018] floppy broken in 5.3.18-lp152.57.1 under KVM
by bugzilla_noreply＠suse.com 19 Jan '21

19 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1181018 https://bugzilla.suse.com/show_bug.cgi?id=1181018#c23 --- Comment #23 from Michal Suchanek <msuchanek(a)suse.com> --- Also the patch as is is ok for 15.2 but in upstream it is likely broken. Upstream has changed like this: -- if (test_bit(FD_OPEN_SHOULD_FAIL_BIT, &drive_state[drive].flags)) +- if (test_bit(FD_OPEN_SHOULD_FAIL_BIT, &UDRS->flags)) and the code added in the patch does not reflect that. Test kernel for 15.2 should build shortly at https://build.opensuse.org/project/monitor/home:michals:kernel-test-15 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1181018] floppy broken in 5.3.18-lp152.57.1 under KVM
by bugzilla_noreply＠suse.com 19 Jan '21

19 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1181018 https://bugzilla.suse.com/show_bug.cgi?id=1181018#c22 --- Comment #22 from Michal Suchanek <msuchanek(a)suse.com> --- Comment on attachment 845273 --> https://bugzilla.suse.com/attachment.cgi?id=845273 [PATCH] floppy: reintroduce O_NDELAY fix >Fixes: 09954bad4 ("floppy: refactor open() flags handling") >Fixe: f2791e7ead ("Revert "floppy: refactor open() flags handling"") +s -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1181097] Microphone no longer working after kernel update
by bugzilla_noreply＠suse.com 19 Jan '21

19 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1181097 https://bugzilla.suse.com/show_bug.cgi?id=1181097#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. Hmm, it's puzzling. Could you try recording manually via arecord? e.g. % pasuspender -- aplay -Dplughw:0 -vv foo.wav This should record from the headset mic. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1181104] Unplugging TeVII DVB-S2 USB adapter crashes kernel
by bugzilla_noreply＠suse.com 19 Jan '21

19 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1181104 https://bugzilla.suse.com/show_bug.cgi?id=1181104#c10 --- Comment #10 from Takashi Iwai <tiwai(a)suse.com> --- Created attachment 845275 --> https://bugzilla.suse.com/attachment.cgi?id=845275&action=edit Another fix patch -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1181104] Unplugging TeVII DVB-S2 USB adapter crashes kernel
by bugzilla_noreply＠suse.com 19 Jan '21

19 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1181104 https://bugzilla.suse.com/show_bug.cgi?id=1181104#c9 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seife(a)novell.slipkontur.de Flags| |needinfo?(seife(a)novell.slip | |kontur.de) --- Comment #9 from Takashi Iwai <tiwai(a)suse.com> --- Now I looked at the code again, and found that the real problem is rather the dvb-usb core stuff. dvb_usb_device_init() copies the properties object, but the dev->desc still points to the old properties. So, the patch in dw2012 driver is correct, per se, but the dvb-usb core behaved wrong. Below is the another patch to fix the issue. Please give it a try. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1181018] floppy broken in 5.3.18-lp152.57.1 under KVM
by bugzilla_noreply＠suse.com 19 Jan '21

19 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1181018 https://bugzilla.suse.com/show_bug.cgi?id=1181018#c21 --- Comment #21 from Jiri Kosina <jkosina(a)suse.com> --- Created attachment 845273 --> https://bugzilla.suse.com/attachment.cgi?id=845273&action=edit [PATCH] floppy: reintroduce O_NDELAY fix I believe this patch might be the cure. Could anyone who is able to reproduce the issue easily please test it? I'll in parallel discuss this upstream, I still have no idea why revert happened back in 2016 instead of taking my proper fix. -- You are receiving this mail because: You are the assignee for the bug.

1 0