March 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1196779] New: Bluetooth adapter with ID not included in modul btusb
by bugzilla_noreply＠suse.com 07 Mar '22

07 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196779 Bug ID: 1196779 Summary: Bluetooth adapter with ID not included in modul btusb Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: RMurr(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The bluetooth adapter with ID 04f2:b49f from Chicony Electronics Co., Ltd Bluetooth Radio (Realtek RTL8723BE) is not included in Kernel modul btusb.c. Although the modul btusb is loaded automatically there is neither any device recognized nor the adapter is discoverable. Root cause: the line with following entry is missing in btusb.c { USB_DEVICE(0x04f2, 0xb49f), .driver_info = BTUSB_REALTEK }, As soon as the line is inserted all devices in range are recognized and are pairable. (Tested with Kernel 5.4.0 on Linux Mint distribution) I could not find any kernel version where the entry in btusb.c is included. -- You are receiving this mail because: You are the assignee for the bug.

1 19

[Bug 1196835] New: [riscv64][Unmatched] CPU#0 stuck forever while trying to reboot the board.
by bugzilla_noreply＠suse.com 07 Mar '22

07 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196835 Bug ID: 1196835 Summary: [riscv64][Unmatched] CPU#0 stuck forever while trying to reboot the board. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: RISC-V OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: chester.lin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 856812 --> http://bugzilla.opensuse.org/attachment.cgi?id=856812&action=edit reboot log Image: openSUSE-Tumbleweed-RISC-V-JeOS-hifiveunmatched.riscv64-2022.03.03-Build1.5.raw The CPU#0 always gets stuck when trying to run the "reboot" command. The full log is attached. However, the shutdown command works fine. Symptom ======= [ OK ] Reached target System Reboot. [ 946.451940][ T1] reboot: Restarting system [ 972.949373][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [systemd-shutdow:1] [ 972.956785][ C0] Modules linked in: af_packet iwlmvm mac80211 libarc4 btusb mscc macsec btrtl btbcm macb btintel iwlwifi phylink bluetooth of_mdio fixed_phy fwnode_m [ 973.016111][ C0] CPU: 0 PID: 1 Comm: systemd-shutdow Not tainted 5.16.11-1-default #1 openSUSE Tumbleweed 6860fdcc9bf06bdf6df5c525bc26813c2d19712e [ 973.029484][ C0] Hardware name: SiFive HiFive Unmatched A00 (DT) [ 973.035739][ C0] epc : machine_restart+0xc/0xe [ 973.040428][ C0] ra : machine_restart+0xc/0xe [ 973.045119][ C0] epc : ffffffff80003a4a ra : ffffffff80003a4a sp : ffffffd00400bd70 [ 973.053023][ C0] gp : ffffffff81771220 tp : ffffffe07fe79c00 t0 : ffffffff8178052f [ 973.060927][ C0] t1 : ffffffff81780518 t2 : 0000000000000000 s0 : ffffffd00400bd80 [ 973.068831][ C0] s1 : 0000000001234567 a0 : 0000000000000000 a1 : 0000000000000000 [ 973.076734][ C0] a2 : 0000000000000000 a3 : 0000000000000231 a4 : 0000000000000000 [ 973.084639][ C0] a5 : 0000000000000000 a6 : c0000000ffffdfff a7 : ffffffffffffffff [ 973.092543][ C0] s2 : ffffffffffffffea s3 : ffffffff81619118 s4 : fffffffffee1dead [ 973.100447][ C0] s5 : d38c929a8bffd198 s6 : 0000000000000000 s7 : 0000000000000000 [ 973.108351][ C0] s8 : 0000000000000000 s9 : 0000003fc7360d08 s10: 0000000000080080 [ 973.116255][ C0] s11: 0000000000000000 t3 : 0000000000000072 t4 : ffffffffffffffff [ 973.124159][ C0] t5 : ffffffff81618fd0 t6 : ffffffd00400bae8 [ 973.130152][ C0] status: 0000000200000120 badaddr: 0000000000000000 cause: 8000000000000005 [ 973.138753][ C0] [<ffffffff80031470>] __do_sys_reboot+0x176/0x226 [ 973.145092][ C0] [<ffffffff80031532>] sys_reboot+0x12/0x1a [ 973.150824][ C0] [<ffffffff80003024>] ret_from_syscall+0x0/0x2 [ 982.539352][ C0] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 34s! [ 1006.459281][ C0] rcu: INFO: rcu_sched self-detected stall on CPU [ 1006.464780][ C0] rcu: 0-....: (5979 ticks this GP) idle=ccb/1/0x4000000000000002 softirq=6008/6008 fqs=2972 [ 1006.474941][ C0] (t=6001 jiffies g=7405 q=80) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196778] amdgpu bug
by bugzilla_noreply＠suse.com 07 Mar '22

07 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1196778 https://bugzilla.suse.com/show_bug.cgi?id=1196778#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Then this has to be reported to the upstream devs and handled there. Please report the bug to gitlab.freedesktop.org Issues. https://gitlab.freedesktop.org/drm/amd/-/issues -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196778] amdgpu bug
by bugzilla_noreply＠suse.com 07 Mar '22

07 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1196778 https://bugzilla.suse.com/show_bug.cgi?id=1196778#c4 --- Comment #4 from James Sevener <james(a)sevener.us> --- Thanks for the reply @Takashi. I've tested with both to the noted kernels from OBS and still have the same issue. Please let me know what is next! -James -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196797] amdgpu: AMD RX6500XT (Navi24) not yet supported?
by bugzilla_noreply＠suse.com 07 Mar '22

07 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196797 http://bugzilla.opensuse.org/show_bug.cgi?id=1196797#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to He Chenlan from comment #6) > Thanks for your help. With 5.16 kernel, my display card work properly. OK, that's a good start. > But, is it possible to use 5.3 kernel from leap 15.3 or 5.14 kernel from > leap 15.4? This kernel is from Tumbleweed which upgrade so frequently. Yes, you can install Leap 15.4 kernel on top of your Leap 15.3 system. Just grab kernel-default, kernel-default-extra and kernel-default-optional packages from OBS Kernel:SLE15-SP4 repo, http://download.opensuse.org/repositories/Kernel:/SLE15-SP4/pool/ and install them. But, tt may be better to increase the number of installable kernels beforehand by editing /etc/zypp/zypp.conf; just add more entries for multiversion.kernels = .... line, e.g. multiversion.kernels = latest,latest-1,latest-2,latest-3,running This will keep more kernels on your system without purge. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196438] New: Consider switching to 300HZ default
by bugzilla_noreply＠suse.com 07 Mar '22

07 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1196438 Bug ID: 1196438 Summary: Consider switching to 300HZ default 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: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I recently stumbled over the 300 HZ option in the kernel configuration. Currently we are using 250 HZ with IDLE_HZ. The HZ setting is used as far as I can see to determine when jiffies are advancing, so it influences the granularity of a couple of things like kvmclock, timers and so on. Also USER_HZ is 100 HZ which is the granularity to which some metrics are exported to user space. 300 is divisible without remainder by 100, unlike 250. so it appears there are good reasons for switching the default, and it is "just" 20% more timer interrupts than before, so it should not be a huge issue. I also did a test build and a 300 HZ kernel is by a few bytes smaller than a 250 HZ kernel, indicating that the compiler can optimize away a few things. I am seeing an increase in a few small functions, and I'm looking into making the code size increase go away with a source level tweak. I've benchmarked both versions in a micro benchmark that does a billion invocations of both, and while the code is larger, it runs in exactly the same runtime (+/- 3% which I consider my benchmark noise level) on a Ryzen Zen 2+. In the Kconfig description of 300 HZ option, it appears this is more recommended for multimedia usecases because it is divisible without remainder for common rates, like 30 (fps), 60 fps , 120 fps, 44.1khZ and others that are often needed. This is imho not only usable for desktop, but also for servers that are using multimedia related applications. I've seen that fedora-like distributions use 1000 HZ, arch linux uses 300 Hz and debian defaults to 250 HZ. So there is no clear trend. I'd be fine with 300 or 1000 HZ. Comments? Would like to hear your feedback before sending a change to the Tumbleweed configs. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1196797] amdgpu: AMD RX6500XT (Navi24) not yet supported?
by bugzilla_noreply＠suse.com 07 Mar '22

07 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196797 http://bugzilla.opensuse.org/show_bug.cgi?id=1196797#c6 --- Comment #6 from He Chenlan <210hcl(a)gmail.com> --- Thanks for your help. With 5.16 kernel, my display card work properly. With 'inxi -Ga', it tells me that my card now work with amdgpu, not ATI or radeon. But, is it possible to use 5.3 kernel from leap 15.3 or 5.14 kernel from leap 15.4? This kernel is from Tumbleweed which upgrade so frequently. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193889] [Build 20211215] openQA test fails in reconnect_mgmt_console because yast.ssh can not restart the operating system
by bugzilla_noreply＠suse.com 07 Mar '22

07 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193889 http://bugzilla.opensuse.org/show_bug.cgi?id=1193889#c57 Sarah Kriesch <ada.lovelace(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #57 from Sarah Kriesch <ada.lovelace(a)gmx.de> --- Thank you for the collaboration to all included participants! This bug is resolved because Berthold has identified the issue, that the static IP address has not been used after the restart. This bug has been resolved with bug #1196582. We have got a new Tumbleweed release now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196797] amdgpu: AMD RX6500XT (Navi24) not yet supported?
by bugzilla_noreply＠suse.com 07 Mar '22

07 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1196797 https://bugzilla.suse.com/show_bug.cgi?id=1196797#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Takashi Iwai from comment #4) > That's a pretty new model, indeed, and even not supported by 5.14 kernel, > i.e. even Leap 15.4 doesn't include the support. Correction, Leap 15.4 kernel already has the code to add this PCI ID, so it may work there. But let's check the behavior with the latest upstream kernel (from OBS Kernel:stable:Backport) at first. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196797] amdgpu: AMD RX6500XT (Navi24) not yet supported?
by bugzilla_noreply＠suse.com 07 Mar '22

07 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1196797 https://bugzilla.suse.com/show_bug.cgi?id=1196797#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |210hcl(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(210hcl(a)gmail.com) --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- That's a pretty new model, indeed, and even not supported by 5.14 kernel, i.e. even Leap 15.4 doesn't include the support. I can try to build a kernel with the patch to add the support for this chip (it seems Beige Goby). But before that, please check whether the recent TW backport kernel in OBS Kernel:stable:Backport works with it. http://download.opensuse.org/repositories/Kernel:/stable:/Backport/standard/ If it works, please upload the full output of hwinfo and the output of dmesg from that kernel. Use attachments, not pasting on the text form. -- You are receiving this mail because: You are the assignee for the bug.

1 0