http://bugzilla.opensuse.org/show_bug.cgi?id=1190608 http://bugzilla.opensuse.org/show_bug.cgi?id=1190608#c2 --- Comment #2 from Bunte Katze --- As proposed by https://www.reddit.com/user/ditzypoet/ I tried booting kernel 5.14.2-1-default only with minimal boot params: linuxefi /boot/vmlinuz-5.14.2-1-default root=/dev/mapper/system-root ${extra_cmdline} resume=/dev/system/swap mitigations=auto However, the result was unfortunately *exactly the same* as with my default boot params (which grew to a long list after applying a whole number of workarounds to fix adjustable laptop screen backlight, keyboard backlights etc.): linuxefi /boot/vmlinux-<kernel version> 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 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1190608 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oneukum@suse.com, | |tiwai@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1190608 http://bugzilla.opensuse.org/show_bug.cgi?id=1190608#c5 --- Comment #5 from Bunte Katze --- Mid-air comment collision. My comment: 1) I have now tried nvidia.prime=intel, but unfortunately that did not make a difference: https://imgur.com/a/SvJfthS 2) I also tried it in combination with modprobe.blacklist=nvidia, but that did not help either. (Which is no surprise, since disabling all nvidia drivers made no difference: https://imgur.com/a/1tX1HoL) 3) Given that the suspicious "can't change power state from D3cold to D0 (config space inaccessible)" message comes from xhci_hcd, and the issue occurs just the same when using module_blacklist on *all* nvidia modules (https://imgur.com/a/1tX1HoL), this issue does not seem to be related to nvidia at all. 4) On reddit, u/ditzypoet made me aware (https://www.reddit.com/r/openSUSE/comments/ppyfcd/optimus_laptop_hangs_on_bo...) of this repository: https://github.com/ReimuNotMoe/Linux-on-GK5CP6V-S Therefore, I tried to boot with the following kernel params: linuxefi /boot/vmlinuz-5.14.2-1-default root=/dev/mapper/system-root ${extra_cmdline} noresume mitigations=auto pci=nommconf acpi_osi=Linux intel_iommu=off However, that did not make any difference: https://imgur.com/a/iK9rlXQ -- My response: @Takashi Iwai Thank you for your hint! I will try this kernel. Probably I need to only disable secure boot in the bios setup? I'll let you know when I figured this out and tried the kernel! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1190608 http://bugzilla.opensuse.org/show_bug.cgi?id=1190608#c7 Michael Pujos changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pujos.michael@gmail.com --- Comment #7 from Michael Pujos --- I'm pretty persuaded it is suse-prime udev rules for NVIDIA power management that are causing this issue: https://github.com/openSUSE/SUSEPrime/blob/master/90-nvidia-udev-pm-G05.rule... (installed in /usr/lib/udev/rules.d/90-nvidia-udev-pm-G05.rules_ and : https://github.com/openSUSE/SUSEPrime/blob/master/09-nvidia-modprobe-pm-G05.... (installed in /usr/lib/modprobe.d/09-nvidia-modprobe-pm-G05.conf) With new suse-prime 0.8.2 that was just published in TW, there is this new nvidia.prime= parameter that allow to override whatever druver (intel, nvidia) was set previously by user. nvidia.prime=intel will cause nvidia modules to not be loaded, allowing the machine to boot. The next testing step would be to disable the power management. Try commenting all lines in /usr/lib/udev/rules.d/90-nvidia-udev-pm-G05.rules (and /usr/lib/modprobe.d/09-nvidia-modprobe-pm-G05.conf although this one might not be necessary) then attempt to boot normally (or use nvidia.prime=nvidia) to check if it boots. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1190608 http://bugzilla.opensuse.org/show_bug.cgi?id=1190608#c9 --- Comment #9 from Bunte Katze --- @Michael Pujos I did already try nvidia.prime=intel with 5.14.2-1-default, but that changed nothing. The nvidia driver appears to not be the culprit. As Takashi Iwai advised, I tried a later kernel from https://download.opensuse.org/repositories/Kernel:/stable/standard/ (5.14.5-1.gfdb6afd-default), which worked, and continued working as I installed the nvidia kernel module and switched back from intel to nvidia. (I am currently writing this on that new setup.) Do you think it is still necessary for bug diagnostics to disable the udev power management rules? (https://bugzilla.opensuse.org/show_bug.cgi?id=1190608#c7) I will have a hard time doing any file modifications, since I can only get to the broken kernel by booting a readonly btrfs snapshot - which fails to boot. (It should probably be possible to choose a previous kernel from the boot menu? I can try if you think it will help figure out the bug, even though 5.14.5 turned out working fine.) Unfortunately, snapper even cleaned out my previous working setup (kernel 5.14.1) before I could increase the NUMBER_LIMIT in /etc/snapper/configs/root. ��\_(���)_/�� -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1190608 http://bugzilla.opensuse.org/show_bug.cgi?id=1190608#c11 --- Comment #11 from Michael Pujos --- The very latest TW snapshot has suse-prime 0.8.2. Although it has rather lager changes, it should not bring bad surprises since the udev rules for dynamic power management I mentioned were already in 0.7.17. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1190608 http://bugzilla.opensuse.org/show_bug.cgi?id=1190608#c13 --- Comment #13 from Bunte Katze --- @Michael Pujos Indeed I am now running bbswitch 0.8-11.28, and it all runs fine on kernel 5.14.5. I believe bbswitch is not the culprit here. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1190608 http://bugzilla.opensuse.org/show_bug.cgi?id=1190608#c15 --- Comment #15 from Michael Pujos --- bbswitch is used (if installed) only in "intel" or "intel2" mode for prime-select, to disable the NVIDIA card entirely. Otherwise, it does nothing (the module is not even loaded). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1190608 http://bugzilla.opensuse.org/show_bug.cgi?id=1190608#c17 --- Comment #17 from Michael Pujos --- @Leo The bbswitch module is only loaded by the prime-select systemd service (which in turn call /usr/sbin/prime-select) if prime-select operates in Intel mode ('prime-select intel' or 'prime-select intel2'). That service (eventually loading the bbswitch module in the cases mentioned above) is called at the very end of the boot process, just before the Display Manager is spawned. Old versions of the suse-prime package did not pull bbswitch (you had to use the suse-prime-bbswitch package for that) but the new version does as it combines both packages. The use of bbswitch to disable a PCI device (the NVIDIA card) can be dangerous and not work everywhere. Though it works on my laptop with a Pascal NVIDIA GPU, on all kernels. The suse-prime package update made all users use bbswitch now (again, only in Intel mode) which is probably not a good idea. I will create a bug report for the upstream project. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1190608 http://bugzilla.opensuse.org/show_bug.cgi?id=1190608#c19 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #19 from Stefan Dirsch --- The initial issue appears to be fixed with later kernels. and Lee's issue with bbswitch meanwhile addressed by https://github.com/openSUSE/SUSEPrime/issues/70 https://build.opensuse.org/request/show/920110 I think we can close this ticket now. -- You are receiving this mail because: You are on the CC list for the bug.