December 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1217344] New: Linux 6.6.1 fails to boot
by bugzilla_noreply＠suse.com 16 Dec '23

16 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 Bug ID: 1217344 Summary: Linux 6.6.1 fails to boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: neronio(a)outlook.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The default 6.6.1 kernel installed on my Tumbleweed system does not boot. Upon selecting it in GRUB, I see: "Loading Linux 6.6.1-1-default ..." "Loading initial ramdisk ..." and the system hangs on this screen forever. My workstation's diagnostic LEDs turn on in a pattern that, according to the service manual, indicates an "other type of failure". The workstation is a Dell T5600. CPU: 2x Intel Xeon E5-2680 (v1) RAM: 8x 8 GB DDR3 1600 MHz GPU: Nvidia NVS510, I'm using nouveau drivers. My kernel cmdline: root=UUID=5136bb35-acaa-4796-b463-8c9ef307025d splash=silent quiet mitigations=auto The latest default 6.5.9 kernel works fine on this machine. I'm available for all kinds of testing/debugging, including kernel recompilation with experimental patches and the like. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 1213830] New: rather current notebook hw (from 2021) has no deep sleep /sys/power/mem_sleep - desktop hw and really old hw does have it
by bugzilla_noreply＠suse.com 15 Dec '23

15 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1213830 Bug ID: 1213830 Summary: rather current notebook hw (from 2021) has no deep sleep /sys/power/mem_sleep - desktop hw and really old hw does have it Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: abittner(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello Opensuse Kernel team, how come that my rather new notebook hardware (hp probook with amd apu, from 2021) does not sleep properly and eats up the battery all the time. barely any difference between when leaving an idle desktop (KDE) sitting around and blanking the screen and when only s2idle sleeping it (lid close, or kde function: sleep) i have tried to make sense of all of this, also reading about the linux folks over at framework-laptop e.g. <https://community.frame.work/t/responded-linux-deep-sleep/2491> all i can find is the value: cat /sys/power/mem_sleep [s2idle] cat /sys/power/state freeze mem disk also added the kernel boot parameter mem_sleep_default=deep command line via yast2 to grub2 or something: ---------- sudo dmesg -e | grep mem_sleep [ +0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.7-default root=/dev/mapper/system-root splash=silent resume=/dev/system/swap preempt=full quiet security=apparmor mem_sleep_default=deep mitigations=auto [ +0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.7-default root=/dev/mapper/system-root splash=silent resume=/dev/system/swap preempt=full quiet security=apparmor mem_sleep_default=deep mitigations=auto --------------- to sum it up, the system eats away the battery/power at high rates even when sleeping, lid closed etc. how to make this work on leap 15.5 with proper (deep?) memory sleep states and all? is this maybe incompatible with FDE, secureboot? this kernel lockdown stuff? i am not understanding much of this i guess. i am wondering why a really old system and other also older desktop systems just instantly show deep mem_sleep feature activated and working? this system: UEFI ans secureboot system [ +0.109168] smpboot: CPU0: AMD Ryzen 7 5800U with Radeon Graphics (family: 0x19, model: 0x50, stepping: 0x0) full disk encryption on single nvme drive thanks for helping. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1217344] Linux 6.6.x fails to boot
by bugzilla_noreply＠suse.com 14 Dec '23

14 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 https://bugzilla.suse.com/show_bug.cgi?id=1217344#c22 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(neronio(a)outlook.c | |om) | --- Comment #22 from Takashi Iwai <tiwai(a)suse.com> --- The upstream fix commit 50d7cdf7a9b1 landed to Linus tree: efi/x86: Avoid physical KASLR on older Dell systems I'm going to backport the fix. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1216647] Missing dummy in kernel-default-base
by bugzilla_noreply＠suse.com 14 Dec '23

14 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1216647 Petr Vorel <petr.vorel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1210335 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1216647] Missing dummy in kernel-default-base
by bugzilla_noreply＠suse.com 14 Dec '23

14 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1216647 Petr Vorel <petr.vorel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1217364 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1216647] Missing dummy in kernel-default-base
by bugzilla_noreply＠suse.com 14 Dec '23

14 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1216647 https://bugzilla.suse.com/show_bug.cgi?id=1216647#c6 --- Comment #6 from Petr Vorel <petr.vorel(a)suse.com> --- (In reply to Fabian Vogt from comment #4) > (In reply to Fabian Vogt from comment #3) > > Submitted to TW (sr#1121191) and SP5 (sr#311823). > > s/SP5/SP6/. > > If there is a particular reason to backport this, please reopen. I would say if it's in 15-SP6, it should be also in 15-SP5. But OTOH nobody complains, to that it's actually OK not include it. FYI dummy module was also needed to test CVE-2023-1829 (bsc#1210335), but that's possible only on 15-SP6 - older versions don't have it, e.g. 15-SP5 (bsc#1217364), but this is not a reason to add the module (not a real request from Leap users). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218005] Leap 15.5 does not boot with any of the kernel-default from update repository
by bugzilla_noreply＠suse.com 14 Dec '23

14 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218005 https://bugzilla.suse.com/show_bug.cgi?id=1218005#c11 --- Comment #11 from Anders Stedtlund <falolaf+suse(a)gmail.com> --- I tested now with only pcie_aspm=off and the kernel booted up. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218005] Leap 15.5 does not boot with any of the kernel-default from update repository
by bugzilla_noreply＠suse.com 14 Dec '23

14 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218005 https://bugzilla.suse.com/show_bug.cgi?id=1218005#c10 --- Comment #10 from Takashi Iwai <tiwai(a)suse.com> --- It means that it's triggered by changes in other parts, e.g. PCI core. Did you test only with pcie_aspm=off boot option? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188954] black screen because dm tries to start before /dev/dri/card0 has been created during init
by bugzilla_noreply＠suse.com 14 Dec '23

14 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1188954 https://bugzilla.suse.com/show_bug.cgi?id=1188954#c31 --- Comment #31 from Felix Miata <mrmazda(a)earthlink.net> --- Created attachment 871337 --> https://bugzilla.suse.com/attachment.cgi?id=871337&action=edit Xorg.0.log from the initial post-boot X failure on KBL GT2 Slowroll host ab250 Host ab250 here is Intel Kaby Lake with Tumbleweed, Slowroll, 15.4, 15.5 and 15.5, among other distros, installed on it. Like several other openSUSE installations here on various hosts, TW, SR & Leap, X will fail to start, claiming /dev/dri/card0 does not exist, but instead of a black screen, it exhibits multi-user.target behavior. When I login and systemctl restart xdm, the greeter starts, and X is running using /dev/dri/card1, with /dev/dri/card0 non-existant. # systemd-analyze Startup finished in 13.602s (firmware) + 9.196s (loader) + 1.801s (kernel) + 2.357s (initrd) + 4.994s (userspace) = 31.953s graphical.target reached after 4.993s in userspace # systemd-analyze critical-chain ... graphical.target @4.993s └─multi-user.target @4.993s └─kbdsettings.service @2.865s +2.126s └─systemd-vconsole-setup.service @2.655s +175ms └─systemd-journald.socket └─system.slice └─-.slice # dmesg | grep aile [ 6.200638] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 6.200641] cfg80211: failed to load regulatory.db [ 6.538658] i915 0000:00:02.0: [drm] [ENCODER:94:DDI A/PHY A] failed to retrieve link info, disabling eDP # journalctl -b --no-hostname | grep aile Dec 13 21:43:06 kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 Dec 13 21:43:06 kernel: cfg80211: failed to load regulatory.db Dec 13 21:43:06 kernel: i915 0000:00:02.0: [drm] [ENCODER:94:DDI A/PHY A] failed to retrieve link info, disabling eDP Dec 13 21:43:06 systemd[1]: kbdsettings.service: Failed with result 'signal'. # -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1216861] Request for application of patch for kernel issue with cilium and NFS shares
by bugzilla_noreply＠suse.com 13 Dec '23

13 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1216861 https://bugzilla.suse.com/show_bug.cgi?id=1216861#c21 --- Comment #21 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:4810-1: An update that solves 12 vulnerabilities, contains three features and has 26 security fixes can now be installed. Category: security (important) Bug References: 1084909, 1210447, 1214286, 1214976, 1215124, 1215292, 1215420, 1215458, 1215710, 1216058, 1216105, 1216259, 1216584, 1216693, 1216759, 1216844, 1216861, 1216909, 1216959, 1216965, 1216976, 1217036, 1217068, 1217086, 1217124, 1217140, 1217195, 1217200, 1217205, 1217332, 1217366, 1217515, 1217598, 1217599, 1217609, 1217687, 1217731, 1217780 CVE References: CVE-2023-2006, CVE-2023-25775, CVE-2023-39197, CVE-2023-39198, CVE-2023-4244, CVE-2023-45863, CVE-2023-45871, CVE-2023-46862, CVE-2023-5158, CVE-2023-5717, CVE-2023-6039, CVE-2023-6176 Jira References: PED-3184, PED-5021, PED-7237 Sources used: openSUSE Leap 15.4 (src): kernel-obs-qa-5.14.21-150400.24.100.1, kernel-obs-build-5.14.21-150400.24.100.2, kernel-syms-5.14.21-150400.24.100.1, kernel-default-base-5.14.21-150400.24.100.2.150400.24.46.2, kernel-source-5.14.21-150400.24.100.2, kernel-livepatch-SLE15-SP4_Update_21-1-150400.9.3.2 openSUSE Leap Micro 5.3 (src): kernel-default-base-5.14.21-150400.24.100.2.150400.24.46.2 openSUSE Leap Micro 5.4 (src): kernel-default-base-5.14.21-150400.24.100.2.150400.24.46.2 SUSE Linux Enterprise Micro for Rancher 5.3 (src): kernel-default-base-5.14.21-150400.24.100.2.150400.24.46.2 SUSE Linux Enterprise Micro 5.3 (src): kernel-default-base-5.14.21-150400.24.100.2.150400.24.46.2 SUSE Linux Enterprise Micro for Rancher 5.4 (src): kernel-default-base-5.14.21-150400.24.100.2.150400.24.46.2 SUSE Linux Enterprise Micro 5.4 (src): kernel-default-base-5.14.21-150400.24.100.2.150400.24.46.2 Basesystem Module 15-SP4 (src): kernel-default-base-5.14.21-150400.24.100.2.150400.24.46.2, kernel-source-5.14.21-150400.24.100.2 Development Tools Module 15-SP4 (src): kernel-source-5.14.21-150400.24.100.2, kernel-obs-build-5.14.21-150400.24.100.2, kernel-syms-5.14.21-150400.24.100.1 SUSE Linux Enterprise Live Patching 15-SP4 (src): kernel-livepatch-SLE15-SP4_Update_21-1-150400.9.3.2 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