February 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1219593] New: CONFIG_READ_ONLY_THP_FOR_FS enabled on Leap/SLE, but not on Tumbleweed
by bugzilla_noreply＠suse.com 05 Feb '24

05 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219593 Bug ID: 1219593 Summary: CONFIG_READ_ONLY_THP_FOR_FS enabled on Leap/SLE, but not on Tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: aaronpuchert(a)alice-dsl.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- While I'm aware that CONFIG_READ_ONLY_THP_FOR_FS is still experimental, I found it odd that it seems to be enabled on Leap/SLE kernels but not on Tumbleweed (6.7.2-1-default). Is there a reason for that, or is it just an oversight? My reason for asking is that I'd like to try out section alignment for LLVM, since some have reported noticeable performance gains by mapping into huge pages. (See https://easyperf.net/blog/2022/09/01/Utilizing-Huge-Pages-For-Code. LLVM has a large .text and tends to wildly jump around, leaving to a trail of L1 TLB misses that can significantly slow it down. And it's large enough that the alignment shouldn't increase size too much.) I'd expect that some other large binaries could also benefit from this, such as browsers. Since they tend to be long-running, we wouldn't even need MADV_COLLAPSE and could just wait for the kernel to automatically replace by THP. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219522] Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 05 Feb '24

05 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c13 --- Comment #13 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- (In reply to Takashi Iwai from comment #12) > Actually it should be "quiet" to be removed instead "verbose". The recovery mode does not contain this line. If you want i can use the "normal boot" without this item. > And, the photo snapshot was taken with "nomodeset" boot session? This > option disables the native graphics, hence if it's the case of native > graphics, the kernel continues to use EFI frame buffer, which is more robust. yes > Also, at this moment, is LED flushing? If so, it's weird; the LED flush > indicates usually a kernel panic, and a kernel panic should print something > to the screen as much as possible. Output stops and the capslock is blinking. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219056] New: ASUS Expertbook B5302F - system doesn't sleep properly, no s0 residency in s2idle
by bugzilla_noreply＠suse.com 05 Feb '24

05 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219056 Bug ID: 1219056 Summary: ASUS Expertbook B5302F - system doesn't sleep properly, no s0 residency in s2idle 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: davor.virag(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:121.0) Gecko/20100101 Firefox/121.0 Build Identifier: I'm using Intel's S0ixSelftestTool (https://github.com/intel/S0ixSelftestTool/) as I was getting seemingly high battery drain in sleep. According to the logs, it can get the CPU into PC10 state, but the logs state: "Your system supports S0ix substates, but did not achieve the shallowest s0i2.0" I have tried "powertop --calibrate" and "powertop --auto-tune", but the s0 self-etst logs still look the same Reproducible: Always Steps to Reproduce: 1. Run "s0ix-selftest-tool.sh -s" 2. Check for s0 residency Actual Results: CPU Core C7 residency after S2idle is: 98.34 GFX RC6 residency after S2idle is: CPU Package C-state 2 residency after S2idle is: 2.79 CPU Package C-state 3 residency after S2idle is: 2.26 CPU Package C-state 8 residency after S2idle is: 0.21 CPU Package C-state 9 residency after S2idle is: 1.33 CPU Package C-state 10 residency after S2idle is: 88.21 S0ix residency after S2idle is: 0.00 Your system supports S0ix substates, but did not achieve the shallowest s0i2.0 Here is the S0ix substates status: Substate Residency S0i2.0 0 S0i3.0 0 (...) Did not detect the potential blockers from substate_requirements, need to check substate_status_registers file for the advanced debug. (...) Your system south port controller power gating state is OK after 30 seconds runtime check. Expected Results: Residency in one of the s0 states -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1219522] Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 05 Feb '24

05 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c11 --- Comment #11 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- Created attachment 872462 --> https://bugzilla.suse.com/attachment.cgi?id=872462&action=edit stops at this point -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219522] Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 05 Feb '24

05 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c10 --- Comment #10 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- Included a photo. After this point the caplock is blinking. * "Verbose" is not in the grub menu, so nothing to remove * remove "splash=*" does not help (is this not equal to "recovery mode"? This line does not contain it either) * "nomodeset" does not help for both modes Is there not a verbose mode in Linux with just tells us which driver is actually loaded? Upgrading the kernel seems to fail to that "zfs" bug. I appreciate the help. I also understand that people can create bugs. But the interface/feedback of the boot process is horrible. Not sure if related. But the only special thing about my laptop is that a thunderbolt3 is "broken". This was a flash bug of Intel/Lenovo and it fails to flash. Since this issue Windows fails to display output using the Thunderbolt3 port (but the usb-c port works just fine). And Linux did work fine using the Thunderbolt3 port (but i assume it fallbacks to dp-alt). This not works for at least a year. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219522] Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 05 Feb '24

05 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c8 --- Comment #8 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- (In reply to Takashi Iwai from comment #7) > OK, relieved :) > > And why are you booting with recovery mode? Didn't the normal boot work in > the past? The recovery mode isn't meant for the daily use. For normal day-to-day usage i use the normal grub line. (need to figure out how to make it stick to the old kernel though because have to wait 2 seconds after each click in the grub menu. Seems still a issue years later). I only use the recovery mode to see the log lines. Hoped it would show something useful to debug such issue. Not sure what is the plan here. I can update to a new kernel and maybe it is already fixed. In that case i also can wait for months to update Suse? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219522] Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 05 Feb '24

05 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c6 --- Comment #6 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- No custom stuff (afaik). The error seems normal? https://forums.opensuse.org/t/upgrade-to-kernel-default-6-5-4-1-1-fails-on-… But grub does not contain another kernel to select. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219522] Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 05 Feb '24

05 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c4 --- Comment #4 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- Not a success. Hope it does not break my system. sudo rpm -i kernel-default-6.8~rc3-1.1.gae4495f.x86_64.rpm warning: kernel-default-6.8~rc3-1.1.gae4495f.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 03579c1d: NOKEY dracut[I]: Executing: /usr/bin/dracut -f /boot/initrd-6.8.0-rc3-1.gae4495f-default 6.8.0-rc3-1.gae4495f-default dracut[I]: Module 'systemd-pcrphase' will not be installed, because command '/usr/lib/systemd/systemd-pcrphase' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command 'portablectl' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command '/usr/lib/systemd/systemd-portabled' could not be found! dracut[I]: Module 'systemd-repart' will not be installed, because command 'systemd-repart' could not be found! dracut[I]: Module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut[I]: Module 'rngd' will not be installed, because command 'rngd' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut[I]: Module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found! dracut[I]: Module 'nvmf' will not be installed, because command 'nvme' could not be found! dracut[I]: Module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! dracut[I]: Module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut[I]: memstrack is not available dracut[I]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut[I]: Module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut[I]: Module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut[I]: Module 'systemd-pcrphase' will not be installed, because command '/usr/lib/systemd/systemd-pcrphase' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command 'portablectl' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command '/usr/lib/systemd/systemd-portabled' could not be found! dracut[I]: Module 'systemd-repart' will not be installed, because command 'systemd-repart' could not be found! dracut[I]: Module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut[I]: Module 'rngd' will not be installed, because command 'rngd' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut[I]: Module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found! dracut[I]: Module 'nvmf' will not be installed, because command 'nvme' could not be found! dracut[I]: Module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut[I]: memstrack is not available dracut[I]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut[I]: Module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut[I]: Module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut[I]: *** Including module: systemd *** dracut[I]: *** Including module: systemd-initrd *** dracut[I]: *** Including module: i18n *** dracut[I]: *** Including module: drm *** dracut[I]: *** Including module: plymouth *** dracut[I]: *** Including module: btrfs *** dracut[I]: *** Including module: kernel-modules *** dracut[I]: *** Including module: kernel-modules-extra *** dracut[I]: *** Including module: zfs *** dracut-install: Failed to find module 'zfs' dracut[E]: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.uflnAv/initramfs -H -N ^i2o_scsi$ --kerneldir /lib/modules/6.8.0-rc3-1.gae4495f-default/ -m zfs dracut[F]: installkernel failed in module zfs warning: %post(kernel-default-6.8~rc3-1.1.gae4495f.x86_64) scriptlet failed, exit status 1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219522] Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 04 Feb '24

04 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c2 --- Comment #2 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- I am using the "recovery mode". I do not see a "splash" line. Also i do not see a "verbose" option. I tried "${extra_cmdline} nomodeset" and does not change anything. I am hesitant to install kernels. My grub list contains 3 items. 2 broken. If it will remove my working kernel i can not boot anymore. Also unclear which rpm i should install. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219056] ASUS Expertbook B5302F - system doesn't sleep properly, no s0 residency in s2idle
by bugzilla_noreply＠suse.com 04 Feb '24

04 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219056 https://bugzilla.suse.com/show_bug.cgi?id=1219056#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Is it a regression? If yes, we can try to narrow down the regression range and identify the cause. Otherwise, it's an upstream problem, and better to report there. We can help backporting the fix in distro side, of course, so feel fee to put me to Cc. -- You are receiving this mail because: You are the assignee for the bug.

1 0