Bug 2187206 - Thinkpad P16s stuck on boot using kernel 6.2.8 or 6.2.9 (works with 6.1.14) - probably related with nouveau
Summary: Thinkpad P16s stuck on boot using kernel 6.2.8 or 6.2.9 (works with 6.1.14) -...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 37
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-17 07:49 UTC by Émeric L
Modified: 2023-04-19 11:51 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-19 11:51:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Journalctl -b -1 -k corresponding to the failure (132.97 KB, text/plain)
2023-04-17 07:50 UTC, Émeric L
no flags Details

Description Émeric L 2023-04-17 07:49:55 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/111.0
Build Identifier: 

After updating to kernel 6.2.x, my Thinkpad P16s (from 2022) is now stuck when booting with 6.2.8 or 6.2.9. I have to use kernel 6.1.14 to keep it functional.

The behavior looks like the one described in bug 2182684 - but on a much more recent hardware and, obviously, the solution is not the same.

In journalctl, when i compare outputs from kernel 6.2.9 with (working) 6.1.14, i see that nouveau fails to start.

Reproducible: Always

Steps to Reproduce:
1. On my thinkpad, i use a pretty standard Fedora 37 installation - graphical configuration is the default
2. Update to kernel 6.2.x (i noticed it starting with 6.2.8, confirmed in 6.2.9)
3. Simply boot.
Actual Results:  
Graphical interface never shows up.
I cannot access any commandline either (but that may very well because i'm new to fedora).

Expected Results:  
Normal start of display manager.

For context : I'm new to Fedora, i chose this distro to put on a professional PC to get some stability and to be able to share with less linux-loving colleagues. I'm used to Archlinux for my personal projects.

Being on a professional PC, i have limited time to investigate. Do not expect instant responses.

Comment 1 Émeric L 2023-04-17 07:50:43 UTC
Created attachment 1957793 [details]
Journalctl -b -1 -k corresponding to the failure

Comment 2 Émeric L 2023-04-17 09:53:19 UTC
Edit : I found an answer in https://discussion.fedoraproject.org/t/latest-6-2-kernel-prevent-gdm-session-to-start/80522
So I suppose this could be classified as an upstream bug.

However, my computer has also the i915 possibility - i would have expected the Intel driver to be used as a fallback. But, this might be a bit off-topic here...

[irma@fedora ~]$ lspci -k | grep -EA3 'VGA|3D|Display'
00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c)
        Subsystem: Lenovo Device 22ea
        Kernel driver in use: i915
        Kernel modules: i915
--
03:00.0 3D controller: NVIDIA Corporation TU117GLM [T550 Laptop GPU] (rev a1)
        Subsystem: Lenovo Device 22ea
        Kernel driver in use: nouveau
        Kernel modules: nouveau


Note You need to log in before you can comment on or make changes to this bug.