Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen

Bug #1991704 reported by Jonathan Kamens
142
This bug affects 23 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Critical
Unassigned

Bug Description

After today's Kinetic update my Framework laptop won't boot.

The boot hangs after this output:

[0.813802] pci 0000:00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci 0000:00:07.1: DPC: RP PIO log size 8 is invalid
[0.815754] pci 0000:00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci 0000:00:07.3: DPC: RP PIO log size 0 is invalid
[2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst
ead

Falling back to 5.19.0-15-generic works.

My Thinkpad X1 Carbon 6th gen does not have this problem.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-15-generic 5.19.0-15.15
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jik 4014 F.... wireplumber
 /dev/snd/seq: jik 4009 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 4 13:55:09 2022
InstallationDate: Installed on 2022-09-17 (16 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
MachineType: Framework Laptop (12th Gen Intel Core)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.19.0-15-generic N/A
 linux-backports-modules-5.19.0-15-generic N/A
 linux-firmware 20220923.gitf09bebf3-0ubuntu1
SourcePackage: linux
UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago)
dmi.bios.date: 07/15/2022
dmi.bios.release: 3.4
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.04
dmi.board.asset.tag: *
dmi.board.name: FRANMACP04
dmi.board.vendor: Framework
dmi.board.version: A4
dmi.chassis.asset.tag: FRANDACPA423350021
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A4
dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04:
dmi.product.family: 13in Laptop
dmi.product.name: Laptop (12th Gen Intel Core)
dmi.product.sku: FRANDACP04
dmi.product.version: A4
dmi.sys.vendor: Framework

Revision history for this message
Jonathan Kamens (jik) wrote :
Revision history for this message
Jonathan Kamens (jik) wrote :

One difference between my Framework laptop (where the problem is happening) and my ThinkPad is that the Framework laptop has a separate Windows boot partition. Don't know if that's relevant, but thought it worth mentioning just in case.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: New Kinetic kernel (5.19.0-18-generic) won't boot

I have the same issue with 5.19.0-18-generic on:

  * Microsoft Surface Laptop 4
  * Intel NUC 12 desktop

Although the last seen kernel log messages are a bit different for each machine so I'm not sure how relevant they are.

summary: - New Kinetic kernel (5.19.0-18-generic) won't boot on Framework laptop
+ New Kinetic kernel (5.19.0-18-generic) won't boot
Changed in linux (Ubuntu):
importance: Undecided → Critical
tags: added: regression-release
Revision history for this message
Daniel van Vugt (vanvugt) wrote (last edit ):

I can still ssh into the machine but there is no /dev/dri/, so that's one reason why we wouldn't see any graphical startup.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Is the problem only Intel 11th/12th gen?

tags: added: rls-kk-incoming
Revision history for this message
Mariusz Dykierek (mariusz.dykierek) wrote :

It is i915 that fails. recovery boot works.
[ 1.671342] kernel: Call Trace:
[ 1.671344] kernel: <TASK>
[ 1.671346] kernel: ? __intel_wait_for_register_fw+0xf5/0x200 [i915]
[ 1.671406] kernel: intel_bw_init_hw+0x120/0x140 [i915]
[ 1.671470] kernel: i915_driver_hw_probe+0x2cc/0x370 [i915]
[ 1.671525] kernel: i915_driver_probe+0x19b/0x490 [i915]
[ 1.671574] kernel: ? drm_privacy_screen_get+0x16d/0x190 [drm]
[ 1.671604] kernel: ? acpi_dev_found+0x64/0x80
[ 1.671609] kernel: i915_pci_probe+0x56/0x150 [i915]
[ 1.671664] kernel: local_pci_probe+0x44/0x90
[ 1.671667] kernel: pci_call_probe+0x55/0x190
[ 1.671669] kernel: pci_device_probe+0x84/0x120
[ 1.671672] kernel: really_probe+0x1dc/0x3b0
[ 1.671675] kernel: __driver_probe_device+0x12c/0x1b0
[ 1.671677] kernel: driver_probe_device+0x24/0xd0
[ 1.671679] kernel: __driver_attach+0xe0/0x210
[ 1.671681] kernel: ? __device_attach_driver+0x130/0x130
[ 1.671683] kernel: bus_for_each_dev+0x8d/0xe0
[ 1.671686] kernel: driver_attach+0x1e/0x30
[ 1.671687] kernel: bus_add_driver+0x187/0x230
[ 1.671689] kernel: driver_register+0x8f/0x100
[ 1.671691] kernel: __pci_register_driver+0x62/0x70
[ 1.671694] kernel: i915_pci_register_driver+0x23/0x30 [i915]
[ 1.671744] kernel: i915_init+0x3b/0xf2 [i915]
[ 1.671804] kernel: ? 0xffffffffc08b0000
[ 1.671806] kernel: do_one_initcall+0x5b/0x240
[ 1.671810] kernel: do_init_module+0x50/0x210
[ 1.671813] kernel: load_module+0xb7d/0xcd0
[ 1.671815] kernel: __do_sys_finit_module+0xc4/0x140
[ 1.671818] kernel: ? __do_sys_finit_module+0xc4/0x140
[ 1.671820] kernel: __x64_sys_finit_module+0x18/0x30
[ 1.671822] kernel: do_syscall_64+0x58/0x90
[ 1.671826] kernel: ? do_syscall_64+0x67/0x90
[ 1.671828] kernel: ? __do_sys_newfstatat+0x53/0x90
[ 1.671831] kernel: ? exit_to_user_mode_prepare+0x30/0xb0
[ 1.671834] kernel: ? syscall_exit_to_user_mode+0x26/0x50
[ 1.671837] kernel: ? __x64_sys_newfstatat+0x1c/0x30
[ 1.671839] kernel: ? do_syscall_64+0x67/0x90
[ 1.671841] kernel: ? do_syscall_64+0x67/0x90
[ 1.671843] kernel: ? sysvec_call_function+0x4b/0xd0
[ 1.671845] kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd

Revision history for this message
Balint Kozma (balint-kozma) wrote :

Intel i9-9900K on Z390 with TPM2.0 module boots.
Asus UX425EA Intel i7-1165G7 doesn't boot.

Revision history for this message
Mariusz Dykierek (mariusz.dykierek) wrote (last edit ):

i7-1165G7 has Iris X graphics like mine. If you checked dmesg.0 log from failed boot, you should see same i915 failure.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

No bug on Intel 10th gen either. So it's only 11th gen and later that's a problem.

tags: added: i915
summary: - New Kinetic kernel (5.19.0-18-generic) won't boot
+ New Kinetic kernel (5.19.0-18-generic) won't boot on Intel 11th/12th gen
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: New Kinetic kernel (5.19.0-18-generic) won't boot on Intel 11th/12th gen

We should also clarify "won't boot" is just an illusion. The OS boots and runs but you don't get any working graphics.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I see the same crash as comment #7, at least on the i7-12700.

Revision history for this message
Jonathan Kamens (jik) wrote :

>We should also clarify "won't boot" is just an illusion.

For me it doesn't finish booting.

I suspect this is because it hangs attempting to switch to a graphical console to prompt for a decryption passphrase for my encrypted root filesystem.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Adding the "nosplash" kernel parameter might help you get to the decryption prompt.

Revision history for this message
Mariusz Dykierek (mariusz.dykierek) wrote :

By default, we expect (many of us using Linux laptops/desktops) that we get a GUI. Now it fails to initialize graphics properly. For now the system is only usable through ssh as I don't even get text console locally. The 'nosplash' ultimately will change nothing or very little.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

More data points since bug 1992126 was reported:

PASS 5.19.0-15-generic
PASS 5.19.0-16-generic
???? 5.19.0-17-generic
FAIL 5.19.0-18-generic
FAIL 5.19.0-19-generic

Revision history for this message
Ted Cabeen (ted-cabeen) wrote (last edit ):

On my Alder Lake system this appears to be a failure to load the Intel driver in some way.

I get the following error in XOrg.0.log on 5.19.0-18:

[ 3.817] (EE) open /dev/dri/card0: No such file or directory

On 5.19.0-15, it loads the card correctly, and that device does exist.

Revision history for this message
Ted Cabeen (ted-cabeen) wrote :
Download full text (6.1 KiB)

Here's the full trace, #7 cuts off the start of the BUG:

[ 2.390194] kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
[ 2.390270] kernel: BUG: kernel NULL pointer dereference, address: 000000000000002e
[ 2.390272] kernel: #PF: supervisor write access in kernel mode
[ 2.390273] kernel: #PF: error_code(0x0002) - not-present page
[ 2.390273] kernel: PGD 0 P4D 0
[ 2.390275] kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI
[ 2.390277] kernel: CPU: 10 PID: 516 Comm: systemd-udevd Not tainted 5.19.0-18-generic #18-Ubuntu
[ 2.390278] kernel: Hardware name: Dell Inc. OptiPlex 7000/0R8DWV, BIOS 1.3.62 06/13/2022
[ 2.390279] kernel: RIP: 0010:tgl_get_bw_info.isra.0+0x473/0x6c0 [i915]
[ 2.390352] kernel: Code: fa 0b 0f 86 e7 00 00 00 41 39 c2 0f 8e 77 fc ff ff e9 3a 5c 0f 00 49 8d b5 e4 21 00 00 0f b7 85 30 ff ff ff 8b 8d 4c ff ff ff <c6> 46 2e 00 66 41 89 85 e0 21 00 00 85 c9 0f 85 f2 fd ff ff e9 08
[ 2.390354] kernel: RSP: 0000:ffffae11c088f770 EFLAGS: 00010206
[ 2.390355] kernel: RAX: 0000000000000301 RBX: 0000000000000003 RCX: 0000000000000001
[ 2.390356] kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000001
[ 2.390356] kernel: RBP: ffffae11c088f860 R08: 0000000000000000 R09: 0000000000000000
[ 2.390357] kernel: R10: 0000000000000002 R11: 0000000000000001 R12: 0000000000000100
[ 2.390358] kernel: R13: ffffa0aa063b00f0 R14: 0000000000000005 R15: ffffa0aa063b0000
[ 2.390359] kernel: FS: 00007f42f4c368c0(0000) GS:ffffa0b16f880000(0000) knlGS:0000000000000000
[ 2.390359] kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 2.390360] kernel: CR2: 000000000000002e CR3: 00000001042a4005 CR4: 0000000000770ee0
[ 2.390361] kernel: PKRU: 55555554
[ 2.390362] kernel: Call Trace:
[ 2.390363] kernel: <TASK>
[ 2.390364] kernel: ? __intel_wait_for_register_fw+0xf5/0x200 [i915]
[ 2.390412] kernel: intel_bw_init_hw+0xe5/0x140 [i915]
[ 2.390461] kernel: i915_driver_hw_probe+0x2cc/0x370 [i915]
[ 2.390502] kernel: i915_driver_probe+0x19b/0x490 [i915]
[ 2.390538] kernel: ? drm_privacy_screen_get+0x16d/0x190 [drm]
[ 2.390558] kernel: ? acpi_dev_found+0x64/0x80
[ 2.390562] kernel: i915_pci_probe+0x56/0x150 [i915]
[ 2.390599] kernel: local_pci_probe+0x44/0x90
[ 2.390602] kernel: pci_call_probe+0x55/0x190
[ 2.390603] kernel: pci_device_probe+0x84/0x120
[ 2.390605] kernel: really_probe+0x1dc/0x3b0
[ 2.390607] kernel: __driver_probe_device+0x12c/0x1b0
[ 2.390608] kernel: driver_probe_device+0x24/0xd0
[ 2.390609] kernel: __driver_attach+0xe0/0x210
[ 2.390611] kernel: ? __device_attach_driver+0x130/0x130
[ 2.390612] kernel: bus_for_each_dev+0x8d/0xe0
[ 2.390614] kernel: driver_attach+0x1e/0x30
[ 2.390615] kernel: bus_add_driver+0x187/0x230
[ 2.390616] kernel: driver_register+0x8f/0x100
[ 2.390617] kernel: __pci_register_driver+0x62/0x70
[ 2.390618] kernel: i915_pci_register_driver+0x23/0x30 [i915]
[ 2.390651] kernel: i915_init+0x3b/0xf2 [i915]
[ 2.390695] kernel: ? 0xffffffffc27bb000
[ 2.390697] kernel: do_one_initcall+0x5b/0x240
[ 2.390700] kernel: do_init_module+0x50/0x210
[ 2.39...

Read more...

Revision history for this message
Mariusz Dykierek (mariusz.dykierek) wrote :

Same thing with 5.19.0-19.

Revision history for this message
Huw Ogilvie (nycticebus) wrote :
Download full text (4.8 KiB)

I am also encountering the same bug in 5.19.0-19, ThinkPad X1 Carbon Gen 9, with Intel Core i7-1165G7 CPU and TigerLake-LP GT2 [Iris Xe Graphics]

[ 3.739068] kernel: i915 0000:00:02.0: enabling device (0006 -> 0007)
[ 3.740132] kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access
[ 3.740589] kernel: Console: switching to colour dummy device 80x25
[ 3.740623] kernel: intel_tcc_cooling: Programmable TCC Offset detected
[ 3.740633] kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
[ 3.740682] kernel: i915 0000:00:02.0: [drm] Transparent Hugepage mode 'huge=within_size'
[ 3.741600] kernel: BUG: kernel NULL pointer dereference, address: 000000000000002e
[ 3.741605] kernel: #PF: supervisor write access in kernel mode
[ 3.741608] kernel: #PF: error_code(0x0002) - not-present page
[ 3.741610] kernel: PGD 0 P4D 0
[ 3.741614] kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI
[ 3.741617] kernel: CPU: 4 PID: 378 Comm: systemd-udevd Not tainted 5.19.0-19-generic #19-Ubuntu
[ 3.741621] kernel: Hardware name: LENOVO 20XWCTO1WW/20XWCTO1WW, BIOS N32ET80W (1.56 ) 08/29/2022
[ 3.741624] kernel: RIP: 0010:tgl_get_bw_info.isra.0+0x473/0x6c0 [i915]
[ 3.741729] kernel: Code: fa 0b 0f 86 e7 00 00 00 41 39 c2 0f 8e 77 fc ff ff e9 3a 5c 0f 00 49 8d b5 e4 21 00 00 0f b7 85 30 ff ff ff 8b 8d 4c ff ff ff <c6> 46 2e 00 66 41 89 85 e0 21 00 00 85 c9 0f 85 f2 fd ff ff e9 08
[ 3.741732] kernel: RSP: 0018:ffffa7a380bcf840 EFLAGS: 00010202
[ 3.741735] kernel: RAX: 0000000000000004 RBX: ffffa7a380bcf8c6 RCX: 0000000000000004
[ 3.741738] kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002
[ 3.741740] kernel: RBP: ffffa7a380bcf930 R08: 0000000000000000 R09: 0000000000000000
[ 3.741742] kernel: R10: 0000000000000008 R11: 0000000000000004 R12: 0000000000000080
[ 3.741744] kernel: R13: ffff9ad750b880f0 R14: 0000000000000005 R15: ffff9ad750b88000
[ 3.741746] kernel: FS: 00007f7729e268c0(0000) GS:ffff9ade7f700000(0000) knlGS:0000000000000000
[ 3.741748] kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 3.741749] kernel: CR2: 000000000000002e CR3: 0000000107be6004 CR4: 0000000000770ee0
[ 3.741751] kernel: PKRU: 55555554
[ 3.741752] kernel: Call Trace:
[ 3.741754] kernel: <TASK>
[ 3.741756] kernel: ? __intel_wait_for_register_fw+0xf5/0x200 [i915]
[ 3.741815] kernel: intel_bw_init_hw+0x120/0x140 [i915]
[ 3.741881] kernel: i915_driver_hw_probe+0x2cc/0x370 [i915]
[ 3.741935] kernel: i915_driver_probe+0x19b/0x490 [i915]
[ 3.741984] kernel: ? drm_privacy_screen_get+0x16d/0x190 [drm]
[ 3.742011] kernel: ? acpi_dev_found+0x64/0x80
[ 3.742015] kernel: i915_pci_probe+0x56/0x150 [i915]
[ 3.742066] kernel: local_pci_probe+0x44/0x90
[ 3.742069] kernel: pci_call_probe+0x55/0x190
[ 3.742071] kernel: pci_device_probe+0x84/0x120
[ 3.742073] kernel: really_probe+0x1dc/0x3b0
[ 3.742076] kernel: __driver_probe_device+0x12c/0x1b0
[ 3.742078] kernel: driver_probe_device+0x24/0xd0
[ 3.742080] kernel: __driver_attach+0xe0/0x210
[ 3.742082] kernel: ? __device_attach_driver+0x130/0x130
[ 3.742084] kernel: bus_for_each_dev+0x8d...

Read more...

Changed in linux (Ubuntu):
status: Confirmed → Triaged
summary: - New Kinetic kernel (5.19.0-18-generic) won't boot on Intel 11th/12th gen
+ Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
Revision history for this message
Dmitry Buzdyk (dbuzdyk) wrote :

Got this problem on HP x360-14 with i7-1165g7.

I tried to find if problem related to Ubuntu or upstream kernel and tested mainline builds available at https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

Both 5.19.0 and 5.19.13 upstream builds boot successfully.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

If the full range of 5.19.x upstream kernels boot successfully then this bug may be caused by an Ubuntu customization.

Revision history for this message
Dmitry Buzdyk (dbuzdyk) wrote :

Went through all upstream 5.19.x available at https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

5.19 - OK
5.19.1 - OK
5.19.2 - OK
5.19.3 - OK
5.19.4 - no amd64 build available
5.19.5 - OK
5.19.6 - NG - same problem as reported
5.19.7 - NG - same problem as reported
5.19.8 - OK
5.19.9 - OK
5.19.10 - OK
5.19.11 - OK
5.19.12 - intentionally skipped due to reported backlight problems on intel laptops
5.19.13 - OK
5.19.14 - no amd64 build available

Revision history for this message
Dmitry Buzdyk (dbuzdyk) wrote :
Revision history for this message
Dmitry Buzdyk (dbuzdyk) wrote :
Revision history for this message
Alex Murray (alexmurray) wrote :
Revision history for this message
Paolo Pisati (p-pisati) wrote :

Could you test this kernel - 5.19.0-19.19+i915fix - and report if it fixes your issue?

https://kernel.ubuntu.com/~arighi/lp-1991703/

Revision history for this message
Dmitry Buzdyk (dbuzdyk) wrote :

5.19-0-19.19+i915fix works for me.

tags: added: fixed-in-5.19.8 fixed-upstream
Changed in linux (Ubuntu):
status: Triaged → Fix Committed
Changed in linux (Ubuntu):
milestone: none → ubuntu-22.10
Revision history for this message
Daniel Swarbrick (pressureman) wrote :

Installing linux-image-5.19.0-20-generic from kinetic-proposed resolved this issue for me.

Revision history for this message
Raymond Kimathi (rmkimathi) wrote :

Without linux-image-5.19.0-21-generic i915-fix the USB Live will never boot in an intel Tiger Lake/Alder Lake IGPU

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 5.19.0-21.21

---------------
linux (5.19.0-21.21) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-21.21 -proposed tracker (LP: #1992639)

  * cannot change mount namespace (LP: #1991691)
    - SAUCE: apparmor: Fix getaatr mediation causing snap failures

  * Kernel regresses openjdk on riscv64 (LP: #1992484)
    - SAUCE: Revert "riscv: mmap with PROT_WRITE but no PROT_READ is invalid"

 -- Andrea Righi <email address hidden> Wed, 12 Oct 2022 19:53:36 +0200

Changed in linux (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Alexandre Ghiti (alexghiti) wrote :

> Without linux-image-5.19.0-21-generic i915-fix the USB Live will never boot in an intel Tiger Lake/Alder Lake IGPU

Indeed the live desktop installer fails to boot on a 12th intel cpu: I have lots of kernel backtraces in dmesg caused by nouveau driver. The kernel from the installer is 5.19.0-21.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-hwe-5.19/5.19.0-24.25~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-hwe-5.19 verification-needed-jammy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.