http://bugzilla.opensuse.org/show_bug.cgi?id=1190608 Bug ID: 1190608 Summary: Boot fails/hangs/freezes with kernel 5.14.2-1-default; System works with 5.14.1-1-default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: awoo@posteo.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.82 Safari/537.36 Build Identifier: My initial description, with some photos of my screen as the boot freezes can be found at https://www.reddit.com/r/openSUSE/comments/ppyfcd/optimus_laptop_hangs_on_bo... I received some initial guidance by https://www.reddit.com/u/MasterPatricko/ (Thank you!) The system is a Tongfang GK5CP0Z / XMG Neo 15 Early 2019 with NVIDIA RTX 2060. I am using it with an external HDMI monitor. HDMI is only available in nvidia mode, so I use prime-select to choose nvidia over intel. Nvidia 470.63.01-43.1 is in use. Kernel 5.14.1-1-default boots and runs perfectly. Kernel 5.14.2-1-default fails to boot. Photo of screen as it freezes on boot: https://imgur.com/eFegmCV Kernel parameters (as copied from grub.cfg): root=/dev/mapper/system-root ${extra_cmdline} resume=/dev/system/swap acpi_osi=! acpi_osi=Linux acpi_os_name=Linux acpi_rev_override=1 nouveau.modeset=0 nouveau.runpm=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 mem_sleep_default=deep mitigations=auto Reproducible: Always Steps to Reproduce: 1. Boot into zypper post snapshot after installing updates yesterday 2. Kernel 5.14.2-1-default starts booting 3. Prints twice ���xhci_hcd: can't change power state from D3cold to D0 (config space inaccessible)��� 4. Prints some other USB-related messages (see photo) 5. Freeze Actual Results: Freezes. No reaction of caps lock LED. No reaction of virtual terminal hotkey (Ctrl+Alt+F1 - F12) Can only hard-reboot by holding physical power button. Expected Results: Kernel 5.14.2-1-default should boot just the same as 5.14.1-1-default does. I tried booting the broken kernel (5.14.2-1-default) from its zypper post snapshot by appending an additional boot param `systemd.unit=multi-user.target`, but that made no difference at all. Same freeze, same messages. Journalctl does not seem to contain any of the frozen boots. Output of lsmod: https://paste.opensuse.org/36050901 Output of lspci: https://paste.opensuse.org/12105741 -- You are receiving this mail because: You are the assignee for the bug.