February 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

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

24 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1196060 https://bugzilla.suse.com/show_bug.cgi?id=1196060#c9 --- Comment #9 from Tony Jones <tonyj(a)suse.com> --- (In reply to Richard Biener from comment #8) > (In reply to Tony Jones from comment #5) > > ok. definitely a regression here vs SP3. I'll look at it. > > > > # stap -vv --poison-cache -l 'module("ext4").function("*")' > > ... > > derive-probes (location #0): module("ext4").function("*") of keyword at > > <input>:1:1 > > semantic error: resolution failed in DWARF builder > > thrown from: elaborate.cxx:1093 > > semantic error: resolution failed in DWARF builder > > thrown from: elaborate.cxx:1093 > > semantic error: while resolving probe point: identifier 'module' at > > <input>:1:7 > > thrown from: elaborate.cxx:1081 > > source: probe module("ext4").function("*") {} > > ^ > > > > semantic error: no match > > thrown from: elaborate.cxx:1044 > > Is this with the same kernel/module .ko or comparing results with different > .kos (from SP3 and Tumbleweed)? Same OS in all cases. Also SP3 works fine. > Eventually it's also elfutils (CCing maintainer) which systemtap seems to > use for DWARF parsing (libdw, that is). Sorry I thought you were the libdw maintainer. The problem appears to be debugging a kernel module ("module.function") in systemtap syntax when the main .ko for the module has been stripped and the debugging info is in a separate debuginfo. - systemtap is not having an issue debugging the primary kernel (aka "kernel.function works fine"). - systemtap is not having an issue debugging modules for a hand built kernel (here "module.function" works). So I don't think it's a DWARF5 vs DWARF4 issue. I don't think dwz is an issue (though I am curious why there is no support for it in elfutils). As I said in previous comment, the debuginfo version of the ext4.ko is where the debug info resides yet is not being referenced at all (per strace log). I'll look more at systemtap today. The ability to debug what is going on at this level isn't great. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1194224] New: Thinkpad T14 Gen 2 / ACPI BIOS Error (bug): Could not resolve symbol / power supply + thermal zone
by bugzilla_noreply＠suse.com 24 Feb '22

24 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194224 Bug ID: 1194224 Summary: Thinkpad T14 Gen 2 / ACPI BIOS Error (bug): Could not resolve symbol / power supply + thermal zone Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: obs(a)akr.yagii.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 854898 --> http://bugzilla.opensuse.org/attachment.cgi?id=854898&action=edit dmesg output There are several resolution failures with ACPI on a new T14 Gen 2. I do not know, whether the "thermal zone" one is critical. Two examples are as follows: [ 6.018461] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input5 [ 6.023730] intel_pmc_core INT33A1:00: initialized [ 6.026588] intel-hid INTC1051:00: failed to read mode [ 6.035743] ACPI: AC: AC Adapter [AC] (off-line) [ 6.035840] ACPI: button: Sleep Button [SLPB] [ 6.035887] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input6 [ 6.041139] usb 3-9: new full-speed USB device number 4 using xhci_hcd [ 6.041931] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.RP09.PEGP.DDNT], AE_NOT_FOUND (20210730/psargs-330) [ 6.041938] ACPI Error: Aborting method \_SB.PC00.LPCB.EC.SEN4._TMP due to previous error (AE_NOT_FOUND) (20210730/psparse-531) [ 6.042537] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.RP09.PEGP.DDNT], AE_NOT_FOUND (20210730/psargs-330) [ 6.042540] ACPI Error: Aborting method \_SB.PC00.LPCB.EC.SEN4._TMP due to previous error (AE_NOT_FOUND) (20210730/psparse-531) [ 6.042543] thermal thermal_zone4: failed to read out thermal zone (-5) [ 6.045149] ACPI: button: Lid Switch [LID] [ 6.045178] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input7 [ 6.045215] ACPI: button: Power Button [PWRF] [ 6.116945] thinkpad_acpi: ThinkPad ACPI Extras v0.26 [ 6.116947] thinkpad_acpi: http://ibm-acpi.sf.net/ [ 6.116948] thinkpad_acpi: ThinkPad BIOS N34ET46W (1.46 ), EC N34HT37W [ 6.116949] thinkpad_acpi: Lenovo ThinkPad T14 Gen 2i, model 20W000ATGE [ 6.117217] thinkpad_acpi: radio switch found; radios are enabled [ 6.117226] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver [ 6.117226] thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... [ 6.118698] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked [ 6.119551] thinkpad_acpi: rfkill switch tpacpi_wwan_sw: radio is blocked [ 6.134407] thinkpad_acpi: battery 1 registered (start 0, stop 100) and [ 6.041139] usb 3-9: new full-speed USB device number 4 using xhci_hcd [ 6.041931] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.RP09.PEGP.DDNT], AE_NOT_FOUND (20210730/psargs-330) [ 6.041938] ACPI Error: Aborting method \_SB.PC00.LPCB.EC.SEN4._TMP due to previous error (AE_NOT_FOUND) (20210730/psparse-531) [ 6.042537] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.RP09.PEGP.DDNT], AE_NOT_FOUND (20210730/psargs-330) [ 6.042540] ACPI Error: Aborting method \_SB.PC00.LPCB.EC.SEN4._TMP due to previous error (AE_NOT_FOUND) (20210730/psparse-531) [ 6.042543] thermal thermal_zone4: failed to read out thermal zone (-5) The thermal zone error shows again after wake-up from suspend. -- You are receiving this mail because: You are the assignee for the bug.

1 6

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

24 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1196060 https://bugzilla.suse.com/show_bug.cgi?id=1196060#c8 Richard Biener <rguenther(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mliska(a)suse.cz --- Comment #8 from Richard Biener <rguenther(a)suse.com> --- (In reply to Tony Jones from comment #5) > ok. definitely a regression here vs SP3. I'll look at it. > > # stap -vv --poison-cache -l 'module("ext4").function("*")' > ... > derive-probes (location #0): module("ext4").function("*") of keyword at > <input>:1:1 > semantic error: resolution failed in DWARF builder > thrown from: elaborate.cxx:1093 > semantic error: resolution failed in DWARF builder > thrown from: elaborate.cxx:1093 > semantic error: while resolving probe point: identifier 'module' at > <input>:1:7 > thrown from: elaborate.cxx:1081 > source: probe module("ext4").function("*") {} > ^ > > semantic error: no match > thrown from: elaborate.cxx:1044 Is this with the same kernel/module .ko or comparing results with different .kos (from SP3 and Tumbleweed)? There might be changes in the debug info that systemtap does not recognize, I'm not sure if the above diagnostics are a sign of that - somebody more familiar with systemtap should see what 'semantic error: resolution failed in DWARF builder' actually means. It could be it just fails to lookup a symbol, but maybe it's more. There's both the compiler and eventually dwz coming into play - to rule out the latter can you try disabling dwz? (I think you can do #!BuildIgnore: dwz when building the kernel and modules) You can also try if it's some new DWARF5 that confuses sytemtap by forcing GCC to use DWARF4 - you somehow need to inject -gdwarf-4 into the kernel/modules build to test that. Eventually it's also elfutils (CCing maintainer) which systemtap seems to use for DWARF parsing (libdw, that is). -- 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 24 Feb '22

24 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196104 http://bugzilla.opensuse.org/show_bug.cgi?id=1196104#c4 --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- You may try to set up kdump for catching the crash. It's not always reliable in such a case, but we might be lucky. Also, it'd be worth to set no_console_suspend boot option for keeping the console during suspend/resume more verbosely, too. -- 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 24 Feb '22

24 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1196060 https://bugzilla.suse.com/show_bug.cgi?id=1196060#c7 --- Comment #7 from Tony Jones <tonyj(a)suse.com> --- # strace -o /tmp/log stap --poison-cache -l 'module("ext4").function("write_mmp_block")' # grep ext4 /tmp/log execve("/bin/stap", ["stap", "--poison-cache", "-l", "module(\"ext4\").function(\"write_m"...], 0x7ffc2a83d928 /* 62 vars */) = 0 newfstatat(AT_FDCWD, "/lib/modules/5.16.10-1-default/kernel/fs/ext4", {st_mode=S_IFDIR|0755, st_size=4096, ...}, 0) = 0 openat(AT_FDCWD, "/lib/modules/5.16.10-1-default/kernel/fs/ext4", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 3 newfstatat(AT_FDCWD, "/lib/modules/5.16.10-1-default/kernel/fs/ext4/ext4.ko", {st_mode=S_IFREG|0644, st_size=1972179, ...}, 0) = 0 newfstatat(AT_FDCWD, "/lib/modules/5.16.10-1-default/kernel/fs/ext4/ext4.ko.zst", {st_mode=S_IFREG|0644, st_size=476572, ...}, 0) = 0 [I manually uncompressed ext4.ko.zst -> ext4.ko] -- 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 24 Feb '22

24 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1196060 https://bugzilla.suse.com/show_bug.cgi?id=1196060#c6 Tony Jones <tonyj(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenther(a)suse.com --- Comment #6 from Tony Jones <tonyj(a)suse.com> --- rguenther so looking at elfutils I see: "checking for zstd... no" is this an issue since kernel-default is packaging ko's with .zst suffix # rpm -ql kernel-default | grep ext4 /usr/lib/modules/5.16.10-1-default/kernel/fs/ext4 /usr/lib/modules/5.16.10-1-default/kernel/fs/ext4/ext4.ko.zst This isn't the issue for this bug as systemtap/elfutils should be opening /usr/lib/debug/usr/lib/modules/5.16.10-1-default/kernel/fs/ext4/ext4.ko.debug from kernel-default-debuginfo However 'strace stap --poison-cache -l 'module("ext4").function("write_mmp_block")' shows it's not accessing this debug file at all. build-id is consistent which has been a cause of these issues before # eu-readelf -a /usr/lib/debug/usr/lib/modules/5.16.10-1-default/kernel/fs/ext4/ext4.ko.debug | grep -A 1 GNU_BUILD_ID GNU 20 GNU_BUILD_ID Build ID: 771c20d08943980047dc325b9101eb04164d1956 # eu-readelf -a /lib/modules/5.16.10-1-default/kernel/fs/ext4/ext4.ko.zst | grep -A 1 GNU_BUILD_ID eu-readelf: failed reading '/lib/modules/5.16.10-1-default/kernel/fs/ext4/ext4.ko.zst': not a valid ELF file # eu-readelf -a /lib/modules/5.16.10-1-default/kernel/fs/ext4/ext4.ko | grep -A 1 GNU_BUILD_ID GNU 20 GNU_BUILD_ID Build ID: 771c20d08943980047dc325b9101eb04164d1956 Hmmn. I shall keep investigating. This is an issue on Factory and SP4. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196213] kernel crash / error_code(0x0000) - not-present page
by bugzilla_noreply＠suse.com 23 Feb '22

23 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1196213 https://bugzilla.suse.com/show_bug.cgi?id=1196213#c14 --- Comment #14 from Alexander Krupp <obs(a)akr.yagii.de> --- vhba built, signed and inserted into your test kernel. I'll be working with this kernel during the next days. -- 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 23 Feb '22

23 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196104 http://bugzilla.opensuse.org/show_bug.cgi?id=1196104#c3 --- Comment #3 from Klaus Schneider-Grosch <funedv(a)gmx.de> --- Checked /var/log/messages (system setup with rsyslog) for "oops" and "panic" after suspend/resume, not found. Is it better to work with journal, does that shows more? The issue is reproducible at each suspend/resume, the events after trying resume are always the same. Added the output of hwinfo. -- 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 23 Feb '22

23 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196104 http://bugzilla.opensuse.org/show_bug.cgi?id=1196104#c2 --- Comment #2 from Klaus Schneider-Grosch <funedv(a)gmx.de> --- Created attachment 856506 --> http://bugzilla.opensuse.org/attachment.cgi?id=856506&action=edit output from hwinfo -- 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 23 Feb '22

23 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1193889 https://bugzilla.suse.com/show_bug.cgi?id=1193889#c53 --- Comment #53 from Mark Post <mpost(a)suse.com> --- Just an update... I still don't know if read_values is causing the problem, but it definitely does have a problem: # read_values -s Floating point exception Copying that file to a working SLES15 SP2 system, and I get this: # ./read_values -s read_values: dl-call-libc-early-init.c:37: _dl_call_libc_early_init: Assertion `sym != NULL' failed. Aborted (core dumped) Time to break out gdb I guess. -- You are receiving this mail because: You are the assignee for the bug.

1 0