- openSUSE Kernel Bugs

[Bug 1228318] kernel crash on two laptops during shutdown/reboot
by bugzilla_noreply＠suse.com 26 Jul '24

26 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228318 https://bugzilla.suse.com/show_bug.cgi?id=1228318#c5 --- Comment #5 from Eric Benton <erbenton(a)comcast.net> --- I thought kdump required a debug kernel? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1228318] kernel crash on two laptops during shutdown/reboot
by bugzilla_noreply＠suse.com 26 Jul '24

26 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228318 https://bugzilla.suse.com/show_bug.cgi?id=1228318#c4 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(erbenton@comcast. | |net) CC| |erbenton(a)comcast.net --- Comment #4 from Jiri Slaby <jslaby(a)suse.com> --- So I would recommend to go back to -default and setup kdump. So that we can move forward. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1228318] kernel crash on two laptops during shutdown/reboot
by bugzilla_noreply＠suse.com 26 Jul '24

26 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228318 https://bugzilla.suse.com/show_bug.cgi?id=1228318#c3 --- Comment #3 from Eric Benton <erbenton(a)comcast.net> --- Yes, I have tried kdump but when i switch to the debug kernel the crash hasn't happened. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1228318] kernel crash on two laptops during shutdown/reboot
by bugzilla_noreply＠suse.com 26 Jul '24

26 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228318 https://bugzilla.suse.com/show_bug.cgi?id=1228318#c2 --- Comment #2 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #1) > (In reply to Eric Benton from comment #0) > > resets. Am I right that this indicates a kernel crash? > > Likely. > > > Not sure where to go from here. > > Have you enabled kdump at all? As it looks like it didn't trigger kdump, > given blinking leds and reboot after 90 s. systemctl statud kdump will tell you. Also you need to set crashkernel kernel parameter. https://doc.opensuse.org/documentation/leap/tuning/html/book-tuning/cha-tun… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1228318] kernel crash on two laptops during shutdown/reboot
by bugzilla_noreply＠suse.com 26 Jul '24

26 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228318 https://bugzilla.suse.com/show_bug.cgi?id=1228318#c1 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com --- Comment #1 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Eric Benton from comment #0) > resets. Am I right that this indicates a kernel crash? Likely. > Not sure where to go from here. Have you enabled kdump at all? As it looks like it didn't trigger kdump, given blinking leds and reboot after 90 s. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1228318] New: kernel crash on two laptops during shutdown/reboot
by bugzilla_noreply＠suse.com 25 Jul '24

25 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228318 Bug ID: 1228318 Summary: kernel crash on two laptops during shutdown/reboot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: erbenton(a)comcast.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have 2 laptops - one is an ASUS ZenBook UX535LI_UX535LI the other is : MSI Katana GF66 11UE At random times I get kernel crashes, but mostly on reboot while its shutting down. I installed the debug kernel on the ASUS along with kdump and cockpit hoping to get more detailed information but, of course, then it wont crash. This doesn't happen every reboot, but it's often enough to be annoying and its happening across multiple kernels. Occasionally, I get a crash while I am surfing the web or just moving the mouse. ok, why do i think its a kernel crash? Because the system hangs and the caps lock led flashes on & off rapidly for about 90 seconds and then the laptop resets. Am I right that this indicates a kernel crash? Not sure where to go from here. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1189479] Ryzen 5500U: Changing Brightness and external screen does not work
by bugzilla_noreply＠suse.com 24 Jul '24

24 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1189479 https://bugzilla.suse.com/show_bug.cgi?id=1189479#c6 Ferdinand Thiessen <rpm(a)fthiessen.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #6 from Ferdinand Thiessen <rpm(a)fthiessen.de> --- This was fixed by a kernel update. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1228224] 'Sleep verb "hibernate" not supported' with secure boot + encrypted swap
by bugzilla_noreply＠suse.com 24 Jul '24

24 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228224 https://bugzilla.suse.com/show_bug.cgi?id=1228224#c4 --- Comment #4 from Alexander Krupp <obs(a)akr.yagii.de> --- After reading up I understand now, that the efi secret key is meant to be provided in a "confidential computing" scenario, including certain hardware measures with a focus on trusted cloud computing. I am not an expert in this area, however, I am wondering if this feature could be exploited somehow in a UEFI secure boot setting? I can not accept the reasoning given by some people, that the battery backed suspend states (even if they last for a month) are a sufficient replacement for hibernation. This argument is IMHO based on purely anecdotal evidence and personal work style. Hibernation has several advantages, like, e.g., being able to replace a battery in mid-work with laptops that have a removable one, or, being able to "suspend" when being troubled with a broken battery. Meanwhile, at least for laptop users, it would be nice to have the option of running an officially signed kernel without hibernation lockdown. My reasoning in bug 1208766 comment 23 may be flawed and it possibly reiterates internal discussions at OpenSuSE, however, I would prefer such line of argumentation to be taken into consideration before I start to compile, and, sign my personal kernel flavor just to be able to upgrade to a security and usability level comparable to a well known commercial OS vendor. I have encrypted hibernation with TPM support, secure boot, kernel lockdown working on 15.5 and would very much hesitate to dispense with these features. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1228228] kernel lockdown
by bugzilla_noreply＠suse.com 24 Jul '24

24 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228228 https://bugzilla.suse.com/show_bug.cgi?id=1228228#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Flags|needinfo?(gfbraff@wolfenet. | |com) | Status|NEW |RESOLVED --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- When you boot from a snapshot, the system directory would be root-only: https://doc.opensuse.org/documentation/leap/archive/15.0/reference/html/boo… So it's the designed behavior. You need to do a proper roll-back procedure via "snapper rollback". -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1228275] New: i915 0000:00:02.0: [drm] *ERROR* Unexpected DE Misc interrupt: 0x00080000
by bugzilla_noreply＠suse.com 24 Jul '24

24 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228275 Bug ID: 1228275 Summary: i915 0000:00:02.0: [drm] *ERROR* Unexpected DE Misc interrupt: 0x00080000 Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Starting with kernel 6.9.9 I got the error message from the subject about every two minutes. I found the setting i915.enable_dc=0 as a workaround, which stopped the error messages on my system, too, but a more permanent solution would be great. System is Operating System: openSUSE Tumbleweed 20240716 KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.9.9-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9310 2-in-1 -- You are receiving this mail because: You are the assignee for the bug.

1 1