[Bug 1233675] New: Kernel stops for 20-30 seconds during boot due to i915 issue
https://bugzilla.suse.com/show_bug.cgi?id=1233675 Bug ID: 1233675 Summary: Kernel stops for 20-30 seconds during boot due to i915 issue Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: alanhants@gmail.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 878686 --> https://bugzilla.suse.com/attachment.cgi?id=878686&action=edit Kernel messages during boot (dmesg) Installation of the 6.11.8 kernel on Tumbleweed has introduced a new problem during boot of my laptop (booting either from cold or restoring for sleep mode). The normal Plymouth startup screen flashes up on my display, then the screen goes blank for between 20 and 30 seconds (time varies from instance to instance) before reappearing prior to the login screen displaying. During the blank period, the laptop is completely non-responsive. My laptop is a Dell Inspiron 16 Plus 7640 factory fitted with an NVIDIA GeForce RTX 4060 Laptop GPU. It is fully updated to the latest Tumbleweed (20041119) as of this bug report's submission date. I have attached the output of dmesg generated immediately after booting the laptop and logging in. Note that there is a pause in the messages between 5.605256 and 22.595812 that roughly corresponds with the observed blank period; following this are two messages that indicate a kernel issue with i915: [ 22.595812] [ T11] i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy component didn't bind within the expected timeout [ 22.595919] [ T11] i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy handler failed to init -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1233675 https://bugzilla.suse.com/show_bug.cgi?id=1233675#c1 Sebastian Kuhne <sebastian.kuhne@mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian.kuhne@mailbox.org --- Comment #1 from Sebastian Kuhne <sebastian.kuhne@mailbox.org> --- I can confirm the same issue. My system: Operating System: openSUSE Tumbleweed 20241121 KDE Plasma Version: 6.2.3 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Kernel Version: 6.11.8-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 8700G w/ Radeon 780M Graphics Memory: 30.4 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASRock Product Name: B650M Pro RS Text excerpt of dmesg (with long pause in between): [ 6.428240] [ T116] scsi 6:0:0:0: Direct-Access NORELSYS 1081CS0 PQ: 0 ANSI: 6 [ 6.428771] [ T116] scsi 6:0:0:1: Direct-Access NORELSYS 1081CS1 PQ: 0 ANSI: 6 [ 6.429046] [ T116] sd 6:0:0:0: Attached scsi generic sg1 type 0 [ 6.429185] [ T117] sd 6:0:0:0: [sda] Media removed, stopped polling [ 6.429220] [ T116] sd 6:0:0:1: Attached scsi generic sg2 type 0 [ 6.429416] [ T115] sd 6:0:0:1: [sdb] Media removed, stopped polling [ 6.429449] [ T117] sd 6:0:0:0: [sda] Attached SCSI removable disk [ 6.429677] [ T115] sd 6:0:0:1: [sdb] Attached SCSI removable disk [ 34.738843] [ T299] systemd-journald[299]: Received SIGTERM from PID 1 (systemd). [ 34.797936] [ T1] systemd[1]: systemd 256.7+suse.9.gc7671762b3 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA -SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -XKBCOMMON -UTMP +SYSVINIT +LIBARCHIVE) [ 34.797940] [ T1] systemd[1]: Detected architecture x86-64. [ 34.957011] [ T1] systemd[1]: bpf-restrict-fs: LSM BPF program attached [ 35.048822] [ T1] systemd[1]: Configuration file /etc/systemd/system/wol.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway. [ 35.048891] [ T1] systemd[1]: Configuration file /etc/systemd/system/computer-shutdown.timer is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway. [ 35.048980] [ T1] systemd[1]: Configuration file /etc/systemd/system/computer-shutdown.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway. [ 35.059611] [ T1] systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1233675 https://bugzilla.suse.com/show_bug.cgi?id=1233675#c2 --- Comment #2 from Sebastian Kuhne <sebastian.kuhne@mailbox.org> --- However, I cannot confirm an ERROR message within dmesg. The pause seems to appear out of the blue. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1233675 https://bugzilla.suse.com/show_bug.cgi?id=1233675#c3 --- Comment #3 from Sebastian Kuhne <sebastian.kuhne@mailbox.org> --- I guess, this is the same issue: https://bugzilla.opensuse.org/show_bug.cgi?id=1233532 -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1233675 https://bugzilla.suse.com/show_bug.cgi?id=1233675#c5 --- Comment #5 from Alan Hughes <alanhants@gmail.com> --- (In reply to Takashi Iwai from comment #4)
Could you check whether it's a recent plymouth issue? e.g. try to boot with options "plymouth.enable=0 splash=none". Does the 20 seconds delay still happen?
Tried as requested, the 20 second delay *does* disappear, so I guess it is linked to plymouth. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1233675 https://bugzilla.suse.com/show_bug.cgi?id=1233675#c7 --- Comment #7 from Alan Hughes <alanhants@gmail.com> --- (In reply to Thomas Zimmermann from comment #6)
(In reply to Alan Hughes from comment #5)
(In reply to Takashi Iwai from comment #4)
Could you check whether it's a recent plymouth issue? e.g. try to boot with options "plymouth.enable=0 splash=none". Does the 20 seconds delay still happen?
Tried as requested, the 20 second delay *does* disappear, so I guess it is linked to plymouth.
I have a plymouth fix pending for the recent upgrade. The test repo is linked at https://bugzilla.suse.com/show_bug.cgi?id=1233532#c29. If possible, could you give it a test?
This *did not* solve the problem; the 20 second delay was still present. I'll attach the latest dmesg output, although a superficial glance suggests that it is the same as before. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1233675 https://bugzilla.suse.com/show_bug.cgi?id=1233675#c8 --- Comment #8 from Alan Hughes <alanhants@gmail.com> --- Created attachment 878722 --> https://bugzilla.suse.com/attachment.cgi?id=878722&action=edit Kernel demesg generated for the test Plymouth installation. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1233675 Alan Hughes <alanhants@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Kernel stops for 20-30 |Kernel stops for 20-30 |seconds during boot due to |seconds during boot due to |i915 issue |Plymouth issue -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1233675 https://bugzilla.suse.com/show_bug.cgi?id=1233675#c10 --- Comment #10 from Alan Hughes <alanhants@gmail.com> --- Updated to Plymouth 22.02.122+180.b1d5aa9-4.1, no change in the problem (still seeing a 20 second pause in the boot). -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1233675 https://bugzilla.suse.com/show_bug.cgi?id=1233675#c11 Alan Hughes <alanhants@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #11 from Alan Hughes <alanhants@gmail.com> --- Problems appears to have been resolved following update to TW 20241129. Marking this as RESOLVED. -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply＠suse.com