March 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1197422] New: [riscv64][Unmatched] Crash during boot
by bugzilla_noreply＠suse.com 04 Apr '22

04 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1197422 Bug ID: 1197422 Summary: [riscv64][Unmatched] Crash during boot 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: hare(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Booting openSUSE-Tumbleweed-RISC-V-KDE-hifiveunmatched.riscv64-2022.03.08-Build2.3 on HiFive Unmatched crashes the system: Loading Linux 5.16.14-1-default ... Loading initial ramdisk ... EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Exiting boot services... [ 6.285566][ T55] Unable to handle kernel paging request at virtual address 00000000200b2f00 [ 6.293429][ T55] Oops [#1] [ 6.296377][ T55] Modules linked in: [ 6.300114][ T55] CPU: 3 PID: 55 Comm: kworker/u8:1 Not tainted 5.16.14-1-default #1 openSUSE Tumbleweed f3df1d20fd39837388447c5d684dd4708bd93651 [ 6.313315][ T55] Hardware name: SiFive HiFive Unmatched A00 (DT) [ 6.319570][ T55] Workqueue: efi_rts_wq efi_call_rts [ 6.324693][ T55] epc : 0x2003332c [ 6.328254][ T55] ra : 0x2003349e [ 6.331815][ T55] epc : 000000002003332c ra : 000000002003349e sp : ffffffd0041fbd00 [ 6.339720][ T55] gp : ffffffff81771228 tp : ffffffe080185400 t0 : 0000000000000040 [ 6.347623][ T55] t1 : 0000000000000003 t2 : ffffffff80ce5b38 s0 : ffffffd00400bd80 [ 6.355527][ T55] s1 : 00000000200b3328 a0 : ffffffd00400bda8 a1 : ffffffff80ed49f0 [ 6.363431][ T55] a2 : 0000000000000000 a3 : ffffffd00400bd80 a4 : ffffffd00400bd78 [ 6.371335][ T55] a5 : 0000000000000000 a6 : ffffffff80ed49f0 a7 : 0000000000000000 [ 6.379239][ T55] s2 : 0000000000000000 s3 : 0000000000000000 s4 : 0000000000000000 [ 6.387144][ T55] s5 : ffffffd00400bd80 s6 : ffffffd00400bd78 s7 : 0000000200000022 [ 6.395048][ T55] s8 : ffffffe0800d2d34 s9 : ffffffff80a13600 s10: ffffffff80a13600 [ 6.402952][ T55] s11: ffffffe0800d2cc0 t3 : 0000000000000116 t4 : 0000000000000001 [ 6.410855][ T55] t5 : ffffffff81619118 t6 : ffffffff81619120 [ 6.416849][ T55] status: 0000000200000120 badaddr: 00000000200b2f00 cause: 000000000000000d [ 6.425485][ T55] ---[ end trace 10f1eb5c3fa3d30c ]--- -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 1197558] New: kernel 5.17 not recovering from sleep or hibernation
by bugzilla_noreply＠suse.com 03 Apr '22

03 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 Bug ID: 1197558 Summary: kernel 5.17 not recovering from sleep or hibernation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: graeme.w.murray(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Latest Kernel 5.17.0-4.gcae6180-default not recovering from sleep or hibernation correctly. Sleep - machine restarts but no display and no usb, so impossible to gain access to machine. Hibernation- machine restarts same results but then reboots. On kernel 5.16 all working fine on this hardware. -- You are receiving this mail because: You are the assignee for the bug.

1 48

[Bug 1197460] Atheros AR9462 (ath9k) not connecting in Linux 5.16.15
by bugzilla_noreply＠suse.com 31 Mar '22

31 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1197460 http://bugzilla.opensuse.org/show_bug.cgi?id=1197460#c12 --- Comment #12 from Takashi Iwai <tiwai(a)suse.com> --- Only kernel-default. And the latest kernel is found in OBS Kernel:stable repo, http://download.opensuse.org/repositories/Kernel:/stable/standard/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1197460] Atheros AR9462 (ath9k) not connecting in Linux 5.16.15
by bugzilla_noreply＠suse.com 30 Mar '22

30 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1197460 http://bugzilla.opensuse.org/show_bug.cgi?id=1197460#c11 --- Comment #11 from Arnaud Mez <arnaudmez(a)vivaldi.net> --- (In reply to Takashi Iwai from comment #9) > The upstream decided to revert the problematic commit in the end. > I pushed the fix to stable branch. It'll be included to the future TW > kernel (likely together with 5.17.1 update). I installed your kernel and tried to boot o it but no success, also I see 2 entries: kernel-default-5.17.0-1.1.gb5aa39a.x86_64.rpm kernel-default-devel-5.17.0-1.1.gb5aa39a.x86_64.rpm should I install both or just the first one sorry to ask I never done this before, so i want to be sure -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1197746] New: [Staging] Kernel 5.17 fails to boot with SELinux enabled setup
by bugzilla_noreply＠suse.com 30 Mar '22

30 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1197746 Bug ID: 1197746 Summary: [Staging] Kernel 5.17 fails to boot with SELinux enabled setup Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://openqa.opensuse.org/tests/2272740/modules/disk _boot/steps/4 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario microos-Staging:O-Staging-DVD-x86_64-container-host-microos@64bit-2G-HD40G fails in [disk_boot](https://openqa.opensuse.org/tests/2272740/modules/disk_boot/step… The system is SELinux enabled, but fails to boot ## Reproducible Fails since (at least) Build [O.136.3](https://openqa.opensuse.org/tests/2261447) ## Expected result Last good: [O.136.2](https://openqa.opensuse.org/tests/2257082) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=microos… -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1197627] [RPI] Unexpected XHCI event TRB
by bugzilla_noreply＠suse.com 30 Mar '22

30 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1197627 https://bugzilla.suse.com/show_bug.cgi?id=1197627#c6 --- Comment #6 from Philippe Corbes <pcorbes(a)averyberkel.fr> --- No the 2022-04-rc5 do not fail. I'm using an OpenSuse 15.3. The original "u-boot-rpi4-2021.01-5.1.rpm" crash. I downloaded the last tag from the U-Boot project and built the "u-boot.bin" file. I updated only the "u-boot.bin" binary file in /boot/efi/. I didn't change anything else to solve this issue. This issue will be solved when OpenSuse will package u-boot-rpi4-2022.03.. or newer. Or backport the comit I included before. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183962] System freeze when wake up from sleep
by bugzilla_noreply＠suse.com 30 Mar '22

30 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1183962 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P4 - Low |P5 - None Found By|Customer |--- -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1197627] [RPI] Unexpected XHCI event TRB
by bugzilla_noreply＠suse.com 30 Mar '22

30 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1197627 https://bugzilla.suse.com/show_bug.cgi?id=1197627#c5 --- Comment #5 from Oliver Neukum <oneukum(a)suse.com> --- (In reply to Philippe Corbes from comment #4) > I solved my issue with the 2022-04-rc5 tag. > I nalysed sources on the Git repository and I think this issue has been > solved since the 2022-04-rc3. > See the commit to solve this issue: > https://github.com/u-boot/u-boot/commit/ > d5daa02d8d9e7c403a3339db1966e8413e64e408 1. This somehow makes no sense. You tested rc5. rc5 fails. rc3 is supposed to have fixed the issue- Has the fix been reverted? 2. The kernel has a list of quirky devices. Should u-boot share it? 3. Do both of these devices do this? Then they should be marked quirky in the kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1197460] Atheros AR9462 (ath9k) not connecting in Linux 5.16.15
by bugzilla_noreply＠suse.com 30 Mar '22

30 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1197460 http://bugzilla.opensuse.org/show_bug.cgi?id=1197460#c10 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arnaudmez(a)vivaldi.net --- Comment #10 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- *** Bug 1197701 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196779] Bluetooth adapter not included in modul btusb
by bugzilla_noreply＠suse.com 30 Mar '22

30 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1196779 https://bugzilla.suse.com/show_bug.cgi?id=1196779#c32 --- Comment #32 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2022:1037-1: An update that solves 12 vulnerabilities and has 25 fixes is now available. Category: security (important) Bug References: 1176447,1176774,1178134,1179439,1181147,1191428,1192273,1193731,1193787,1193864,1194463,1194516,1195211,1195254,1195403,1195612,1195897,1195905,1195939,1195949,1195987,1196079,1196095,1196132,1196155,1196299,1196301,1196433,1196468,1196472,1196627,1196723,1196779,1196830,1196836,1196866,1196868 CVE References: CVE-2021-0920,CVE-2021-39657,CVE-2021-44879,CVE-2022-0487,CVE-2022-0617,CVE-2022-0644,CVE-2022-24448,CVE-2022-24958,CVE-2022-24959,CVE-2022-25258,CVE-2022-25636,CVE-2022-26490 JIRA References: Sources used: SUSE Linux Enterprise Module for Public Cloud 15-SP3 (src): kernel-azure-5.3.18-150300.38.50.1, kernel-source-azure-5.3.18-150300.38.50.1, kernel-syms-azure-5.3.18-150300.38.50.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0