March 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1196104] no resume or bad resume after suspend
by bugzilla_noreply＠suse.com 03 Mar '22

03 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196104 http://bugzilla.opensuse.org/show_bug.cgi?id=1196104#c20 --- Comment #20 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Klaus Schneider-Grosch from comment #19) > After installation of crash and decompression of > vmlinux-5.16.11-lp153.2.g90630c5-default: > > crash /var/crash/2022-03-01-19\:09/vmlinux-5.16.11-lp153.2.g90630c5-default > /var/crash/2022-03-01-19\:09/vmcore > > crash 7.2.9 > Copyright (C) 2002-2020 Red Hat, Inc. > Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation > Copyright (C) 1999-2006 Hewlett-Packard Co > Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited > Copyright (C) 2006, 2007 VA Linux Systems Japan K.K. > Copyright (C) 2005, 2011 NEC Corporation > Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc. > Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc. > This program is free software, covered by the GNU General Public License, > and you are welcome to change it and/or distribute copies of it under > certain conditions. Enter "help copying" to see the conditions. > This program has absolutely no warranty. Enter "help warranty" for details. > > crash: /var/crash/2022-03-01-19:09/vmlinux-5.16.11-lp153.2.g90630c5-default: > no debugging data available > crash: vmlinux-5.16.11-lp153.2.g90630c5-default.debug: debuginfo file not > found > > crash: either install the appropriate kernel debuginfo package, or > copy vmlinux-5.16.11-lp153.2.g90630c5-default.debug to this machine You could install the corresponding package, kernel-default-debuginfo from the URL you downloaded the kernel, too. > The notebook works only perfectly with the kernel > 5.16.11-lp153.2.g90630c5-default from kernel stable backport repo. Wait: how was this kdump created? Wasn't it at the state where the machine got stuck after resume? Otherwise it's almost nonsense; we want the kdump at the broken state, not the working state. > I tried > it also with Kernel 5.3.18-150300.59.49-default, but I could not achieve a > kdump after trying resume. The system got stuck in a unknown state. And alt-sysrq-c didn't trigger the kdump at that state? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196104] no resume or bad resume after suspend
by bugzilla_noreply＠suse.com 03 Mar '22

03 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196104 http://bugzilla.opensuse.org/show_bug.cgi?id=1196104#c19 --- Comment #19 from Klaus Schneider-Grosch <funedv(a)gmx.de> --- After installation of crash and decompression of vmlinux-5.16.11-lp153.2.g90630c5-default: crash /var/crash/2022-03-01-19\:09/vmlinux-5.16.11-lp153.2.g90630c5-default /var/crash/2022-03-01-19\:09/vmcore crash 7.2.9 Copyright (C) 2002-2020 Red Hat, Inc. Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation Copyright (C) 1999-2006 Hewlett-Packard Co Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited Copyright (C) 2006, 2007 VA Linux Systems Japan K.K. Copyright (C) 2005, 2011 NEC Corporation Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc. Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc. This program is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Enter "help copying" to see the conditions. This program has absolutely no warranty. Enter "help warranty" for details. crash: /var/crash/2022-03-01-19:09/vmlinux-5.16.11-lp153.2.g90630c5-default: no debugging data available crash: vmlinux-5.16.11-lp153.2.g90630c5-default.debug: debuginfo file not found crash: either install the appropriate kernel debuginfo package, or copy vmlinux-5.16.11-lp153.2.g90630c5-default.debug to this machine The notebook works only perfectly with the kernel 5.16.11-lp153.2.g90630c5-default from kernel stable backport repo. I tried it also with Kernel 5.3.18-150300.59.49-default, but I could not achieve a kdump after trying resume. The system got stuck in a unknown state. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196060] systemtap fails to build simple example from docs
by bugzilla_noreply＠suse.com 02 Mar '22

02 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1196060 https://bugzilla.suse.com/show_bug.cgi?id=1196060#c17 Tony Jones <tonyj(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Depends on|1196510 | Resolution|--- |FIXED --- Comment #17 from Tony Jones <tonyj(a)suse.com> --- fix for elfutils accepted to SP4, closing. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196060] systemtap fails to build simple example from docs
by bugzilla_noreply＠suse.com 02 Mar '22

02 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1196060 Bug 1196060 depends on bug 1196510, which changed state. Bug 1196510 Summary: elfutils needs zstd support https://bugzilla.suse.com/show_bug.cgi?id=1196510 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196104] no resume or bad resume after suspend
by bugzilla_noreply＠suse.com 02 Mar '22

02 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196104 http://bugzilla.opensuse.org/show_bug.cgi?id=1196104#c18 --- Comment #18 from Takashi Iwai <tiwai(a)suse.com> --- Weird, something went wrong in kdump. But we can try to run crash program for the given vmcore. Try to install crash package, and run it with the vmlinux and the vmcore files. crash /var/crash/.../vmlinux-*.gz /var/crash/.../vmcore (You might need to uncompress vmlinux-* beforehand, I'm not sure whether crash program can handle vmlinux.gz) Then in the crash prompt, run "dmesg" command. It'll show the dmesg there. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196104] no resume or bad resume after suspend
by bugzilla_noreply＠suse.com 02 Mar '22

02 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196104 http://bugzilla.opensuse.org/show_bug.cgi?id=1196104#c17 --- Comment #17 from Klaus Schneider-Grosch <funedv(a)gmx.de> --- you are right. But there is no dmesg in the output: ls -l /var/crash/2022-03-01-19\:09/ insgesamt 181728 drwxr-xr-x 2 root root 4096 1. M�r 19:10 ./ drwxr-xr-x 5 root root 4096 1. M�r 19:09 ../ -rw-r--r-- 1 root root 200 1. M�r 19:10 README.txt -rw-r--r-- 1 root root 5886484 1. M�r 19:10 System.map-5.16.11-lp153.2.g90630c5-default -rw------- 1 root root 167831356 1. M�r 19:10 vmcore -rw-r--r-- 1 root root 12350556 1. M�r 19:10 vmlinux-5.16.11-lp153.2.g90630c5-default.xz -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196104] no resume or bad resume after suspend
by bugzilla_noreply＠suse.com 02 Mar '22

02 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196104 http://bugzilla.opensuse.org/show_bug.cgi?id=1196104#c16 --- Comment #16 from Takashi Iwai <tiwai(a)suse.com> --- I guess dmesg.txt above is from the normal working state, right? Could you upload dmesg file found in the generated /var/crash/* at the resume? That's the most important piece. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196104] no resume or bad resume after suspend
by bugzilla_noreply＠suse.com 02 Mar '22

02 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196104 http://bugzilla.opensuse.org/show_bug.cgi?id=1196104#c15 --- Comment #15 from Klaus Schneider-Grosch <funedv(a)gmx.de> --- Created attachment 856702 --> http://bugzilla.opensuse.org/attachment.cgi?id=856702&action=edit output from dmesg dmesg > dmesg.txt -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196465] [Build 20220223] openQA test fails in LTP waitid10
by bugzilla_noreply＠suse.com 02 Mar '22

02 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1196465 https://bugzilla.suse.com/show_bug.cgi?id=1196465#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chrubis(a)suse.com, | |fvogt(a)suse.com Assignee|kernel-bugs(a)opensuse.org |petr.vorel(a)suse.com --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- The test does: volatile int a, zero = 0; a = 1 / zero; exit(a); and expects SIGFPE to happen. But integer division / 0 is undefined behaviour. This might work better by using float instead. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196633] New: Raspberry Pi 4 - kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
by bugzilla_noreply＠suse.com 02 Mar '22

02 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196633 Bug ID: 1196633 Summary: Raspberry Pi 4 - kernel: Bluetooth: hci0: Failed to read codec capabilities (-56) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/2220365/modules/jour nal_check/steps/10 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, dmueller(a)suse.com, mbrugger(a)suse.com Found By: openQA Blocker: Yes openQA shows kernel errors related to Bluetooth on RPi 4: Raspberry Pi 4 - kernel: Bluetooth: hci0: Failed to read codec capabilities (-56) See: https://openqa.opensuse.org/tests/2220365/modules/journal_check/steps/10) -- You are receiving this mail because: You are the assignee for the bug.

1 1