http://bugzilla.opensuse.org/show_bug.cgi?id=1187736 http://bugzilla.opensuse.org/show_bug.cgi?id=1187736#c3 --- Comment #3 from S Dziegiel --- I have added the repo via yast. Can you confirm that the version that I should test is kernel-debug version 5.13.1-lp153.2.1.gbebf622 or something very similar? -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1187736 http://bugzilla.opensuse.org/show_bug.cgi?id=1187736#c5 --- Comment #5 from S Dziegiel --- Created attachment 850906 --> http://bugzilla.opensuse.org/attachment.cgi?id=850906&action=edit Upstream kernel fails to load -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1187736 http://bugzilla.opensuse.org/show_bug.cgi?id=1187736#c7 --- Comment #7 from S Dziegiel --- Retested with zypper install kernel-default-5.13.2-lp153.2.1.g89416ca.x86_64.rpm Switched off Secure Boot. The upstream kernel loads. Log in. Leave the PC alone for approximately 10 minutes and it reboots itself. I now believe that it reboots after a period of approx 10 minutes of inactivity (so not random). There was no stack dump in /var/log/messages. I will retry a few more times. Is there a way to force the dump? -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1187736 http://bugzilla.opensuse.org/show_bug.cgi?id=1187736#c9 --- Comment #9 from S Dziegiel --- Created attachment 851207 --> http://bugzilla.opensuse.org/attachment.cgi?id=851207&action=edit FIrst reboot with upstream kernel + drm.debug=0x1e Rebooted with upstream kernel5.13.2-lp153.2.g89416ca-default and drm.debug=0x1e. Logged in. Machine unattended and reboots after 10 minutes -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1187736 http://bugzilla.opensuse.org/show_bug.cgi?id=1187736#c12 --- Comment #12 from S Dziegiel --- Agreed, all I can see are extra i915 log messages. Correct, the reboot is not recorded in the logs at all (/var/log/messages), hence my question about the logs showing anything useful. If you concatenate the two upstream logs that I attached then that is all you see in /var/log/messages for those two sessions. Is there anywhere else it might log? The system just blanks the screen and reboots itself. The only time I have ever captured anything that looked useful was in attachment 1 using the standard Leap kernel back in June. I will try again this weekend. Do you still want me to gather logs from the upstream kernel? I will only post new logs if I see something notably different from the two upstream logs that I posted over the weekend. -- You are receiving this mail because: You are the assignee for the bug.