You are not logged in.
I have an intel system with up to date arch linux.
After a recent upgrade I find that my display blanks after one or two lines of boot messages (the grub menu shows fine). I cannot use either X11 or the various consoles (ctrl-alt fn).
If I revert from linux-6.8.2.arch2-1 to linux-6.5.9-arch2-1 then both X11 and console displays are fine.
I believe the hardware is Intel Tigerlake Iris Xe GT2.
There are no obvious messages in the dmesg output. However, I do see some messages related to bluetooth and various ACPI errors.
Is there some way to diagnose the issue. I do have ssh access.
Last edited by replabrobin (2024-04-05 08:53:19)
Offline
If you have ssh access, ssh in and post the journal/the link you get from
sudo journalctl -b | curl -F 'file=@-' 0x0.stOffline
$ sudo journalctl -b | curl -F 'file=@-' 0x0.st
http://0x0.st/Xib8.txtthis is the hardware
$ lspci -k | grep -EA3 'VGA|3D|Display'
00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)
DeviceName: Onboard - Video
Subsystem: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics]
Kernel driver in use: i915Offline
Apr 05 16:57:10 brandykat kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Apr 05 16:57:10 brandykat kernel: i915 0000:00:02.0: [drm] Using Transparent Hugepages
Apr 05 16:57:10 brandykat kernel: i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Apr 05 16:57:10 brandykat kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/tgl_dmc_ver2_12.bin (v2.12)
Apr 05 16:57:10 brandykat kernel: i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized
Apr 05 16:57:10 brandykat kernel: ------------[ cut here ]------------
Apr 05 16:57:10 brandykat kernel: i915 0000:00:02.0: drm_WARN_ON(!connector->dp.dsc_decompression_aux || !connector->dp.dsc_decompression_enabled)
Apr 05 16:57:10 brandykat kernel: WARNING: CPU: 2 PID: 155 at drivers/gpu/drm/i915/display/intel_dp.c:3193 intel_dp_sink_disable_decompression+0x63/0xf0 [i915]
Apr 05 16:57:10 brandykat kernel: Modules linked in: i915(+) i2c_algo_bit drm_buddy ttm nvme intel_gtt drm_display_helper nvme_core crc32c_intel xhci_pci cec nvme_auth xhci_pci_renesas video wmi
Apr 05 16:57:10 brandykat kernel: CPU: 2 PID: 155 Comm: (udev-worker) Not tainted 6.8.2-arch2-1 #1 a430fb92f7ba43092b62bbe6bac995458d3d442d
Apr 05 16:57:10 brandykat kernel: Hardware name: Intel(R) Client Systems NUC11TNKi7/NUC11TNBi7, BIOS TNTGL357.0070.2022.1028.1209 10/28/2022
Apr 05 16:57:10 brandykat kernel: RIP: 0010:intel_dp_sink_disable_decompression+0x63/0xf0 [i915]
Apr 05 16:57:10 brandykat kernel: Code: 8b 5f 50 48 85 db 0f 84 95 00 00 00 e8 b6 96 b0 d8 48 c7 c1 30 77 7e c0 48 89 da 48 c7 c7 89 34 80 c0 48 89 c6 e8 6d b3 27 d8 <0f> 0b 5b 5d c3 cc cc cc cc 83 e0 fd 31 d2 88 86 a1 09 00 00 e8 d4
Apr 05 16:57:10 brandykat kernel: RSP: 0018:ffffb6e482ec3780 EFLAGS: 00010282
Apr 05 16:57:10 brandykat kernel: RAX: 0000000000000000 RBX: ffff9be9021b9540 RCX: ffffffff9a6ca688
Apr 05 16:57:10 brandykat kernel: RDX: 0000000000000000 RSI: 00000000ffffefff RDI: 0000000000000001
Apr 05 16:57:10 brandykat kernel: RBP: ffff9be90ae8c000 R08: 0000000000000000 R09: ffffb6e482ec3610
Apr 05 16:57:10 brandykat kernel: R10: ffffb6e482ec3608 R11: 0000000000000003 R12: ffff9be90ad4b9c0
Apr 05 16:57:10 brandykat kernel: R13: ffff9be909b2f000 R14: ffff9be90b3d8000 R15: ffff9be9010d8000
Apr 05 16:57:10 brandykat kernel: FS: 00007b356a5f9540(0000) GS:ffff9bf090480000(0000) knlGS:0000000000000000
Apr 05 16:57:10 brandykat kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 05 16:57:10 brandykat kernel: CR2: 00005b493f5cc368 CR3: 0000000109ac0005 CR4: 0000000000f70ef0
Apr 05 16:57:10 brandykat kernel: PKRU: 55555554
Apr 05 16:57:10 brandykat kernel: Call Trace:
Apr 05 16:57:10 brandykat kernel: <TASK>
Apr 05 16:57:10 brandykat kernel: ? intel_dp_sink_disable_decompression+0x63/0xf0 [i915 547fc484a13c50a49810001a7e67ee556ad7aa67]
Apr 05 16:57:10 brandykat kernel: ? __warn+0x81/0x130
Apr 05 16:57:10 brandykat kernel: ? intel_dp_sink_disable_decompression+0x63/0xf0 [i915 547fc484a13c50a49810001a7e67ee556ad7aa67]
Apr 05 16:57:10 brandykat kernel: ? report_bug+0x171/0x1a0
Apr 05 16:57:10 brandykat kernel: ? console_unlock+0x78/0x120
Apr 05 16:57:10 brandykat kernel: ? handle_bug+0x3c/0x80
Apr 05 16:57:10 brandykat kernel: ? exc_invalid_op+0x17/0x70
Apr 05 16:57:10 brandykat kernel: ? asm_exc_invalid_op+0x1a/0x20
Apr 05 16:57:10 brandykat kernel: ? intel_dp_sink_disable_decompression+0x63/0xf0 [i915 547fc484a13c50a49810001a7e67ee556ad7aa67]
Apr 05 16:57:10 brandykat kernel: intel_disable_ddi+0x133/0x1f0 [i915 547fc484a13c50a49810001a7e67ee556ad7aa67]
Apr 05 16:57:10 brandykat kernel: intel_encoders_disable+0x8a/0xb0 [i915 547fc484a13c50a49810001a7e67ee556ad7aa67]
Apr 05 16:57:10 brandykat kernel: hsw_crtc_disable+0x129/0x140 [i915 547fc484a13c50a49810001a7e67ee556ad7aa67]
Apr 05 16:57:10 brandykat kernel: intel_atomic_commit_tail+0x46d/0xf80 [i915 547fc484a13c50a49810001a7e67ee556ad7aa67]
Apr 05 16:57:10 brandykat kernel: intel_atomic_commit+0x2c8/0x310 [i915 547fc484a13c50a49810001a7e67ee556ad7aa67]
Apr 05 16:57:10 brandykat kernel: drm_atomic_commit+0x97/0xd0
Apr 05 16:57:10 brandykat kernel: ? __pfx___drm_printfn_info+0x10/0x10
Apr 05 16:57:10 brandykat kernel: intel_initial_commit+0x16a/0x200 [i915 547fc484a13c50a49810001a7e67ee556ad7aa67]
Apr 05 16:57:10 brandykat kernel: intel_display_driver_probe+0x26/0x90 [i915 547fc484a13c50a49810001a7e67ee556ad7aa67]
Apr 05 16:57:10 brandykat kernel: i915_driver_probe+0x6a9/0xba0 [i915 547fc484a13c50a49810001a7e67ee556ad7aa67]
Apr 05 16:57:10 brandykat kernel: local_pci_probe+0x42/0xa0
Apr 05 16:57:10 brandykat kernel: pci_device_probe+0xc1/0x260
Apr 05 16:57:10 brandykat kernel: ? sysfs_do_create_link_sd+0x6e/0xe0
Apr 05 16:57:10 brandykat kernel: really_probe+0x19b/0x3e0
Apr 05 16:57:10 brandykat kernel: ? __pfx___driver_attach+0x10/0x10
Apr 05 16:57:10 brandykat kernel: __driver_probe_device+0x78/0x160
Apr 05 16:57:10 brandykat kernel: driver_probe_device+0x1f/0x90
Apr 05 16:57:10 brandykat kernel: __driver_attach+0xd2/0x1c0
Apr 05 16:57:10 brandykat kernel: bus_for_each_dev+0x85/0xd0
Apr 05 16:57:10 brandykat kernel: bus_add_driver+0x116/0x220
Apr 05 16:57:10 brandykat kernel: driver_register+0x59/0x100
Apr 05 16:57:10 brandykat kernel: i915_init+0x22/0xc0 [i915 547fc484a13c50a49810001a7e67ee556ad7aa67]
Apr 05 16:57:10 brandykat kernel: ? __pfx_i915_init+0x10/0x10 [i915 547fc484a13c50a49810001a7e67ee556ad7aa67]
Apr 05 16:57:10 brandykat kernel: do_one_initcall+0x58/0x320
Apr 05 16:57:10 brandykat kernel: do_init_module+0x60/0x240
Apr 05 16:57:10 brandykat kernel: init_module_from_file+0x89/0xe0
Apr 05 16:57:10 brandykat kernel: idempotent_init_module+0x120/0x2b0
Apr 05 16:57:10 brandykat kernel: __x64_sys_finit_module+0x5e/0xb0
Apr 05 16:57:10 brandykat kernel: do_syscall_64+0x86/0x170
Apr 05 16:57:10 brandykat kernel: ? ksys_read+0x6f/0xf0
Apr 05 16:57:10 brandykat kernel: ? syscall_exit_to_user_mode+0x80/0x230
Apr 05 16:57:10 brandykat kernel: ? do_syscall_64+0x96/0x170
Apr 05 16:57:10 brandykat kernel: ? do_syscall_64+0x96/0x170
Apr 05 16:57:10 brandykat kernel: ? syscall_exit_to_user_mode+0x80/0x230
Apr 05 16:57:10 brandykat kernel: ? do_syscall_64+0x96/0x170
Apr 05 16:57:10 brandykat kernel: ? do_syscall_64+0x96/0x170
Apr 05 16:57:10 brandykat kernel: ? exc_page_fault+0x7f/0x180
Apr 05 16:57:10 brandykat kernel: entry_SYSCALL_64_after_hwframe+0x6e/0x76
Apr 05 16:57:10 brandykat kernel: RIP: 0033:0x7b356b0d888d
Apr 05 16:57:10 brandykat kernel: Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 73 14 0d 00 f7 d8 64 89 01 48
Apr 05 16:57:10 brandykat kernel: RSP: 002b:00007fffa9f78848 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Apr 05 16:57:10 brandykat kernel: RAX: ffffffffffffffda RBX: 00005b493f5f1e20 RCX: 00007b356b0d888d
Apr 05 16:57:10 brandykat kernel: RDX: 0000000000000000 RSI: 00007b356b1ed376 RDI: 000000000000002a
Apr 05 16:57:10 brandykat kernel: RBP: 00007b356b1ed376 R08: 0000000000000001 R09: fffffffffffffe88
Apr 05 16:57:10 brandykat kernel: R10: 0000000000000050 R11: 0000000000000246 R12: 0000000000020000
Apr 05 16:57:10 brandykat kernel: R13: 00005b493f5f2910 R14: 0000000000000000 R15: 00005b493f5f3790
Apr 05 16:57:10 brandykat kernel: </TASK>
Apr 05 16:57:10 brandykat kernel: ---[ end trace 0000000000000000 ]---
Apr 05 16:57:10 brandykat kernel: [drm] Initialized i915 1.6.0 20230929 for 0000:00:02.0 on minor 1
Apr 05 16:57:10 brandykat kernel: ACPI: video: Video Device [GFX0] (multi-head: yes rom: no post: no)Mhm... There have been a bunch of fixes across the drm subsystem in 6.8.3 maybe try 6.8.4 from testing (... or when it lands in stable) and just from where it crashes, try the kernel param
i915.enable_fbc=0Offline
thanks I did not knew I was submitting stuff, but anyhow I will wait for 6.8.3/4 and report back when that appears.
Last edited by replabrobin (2024-04-05 21:43:12)
Offline
I tried installing 6.8.4 from core-testing ie
sudo -U /var/cache/pacman/pkg/linux-6.8.4.arch1-1-x86_64.pkg.tar.zst /var/cache/pacman/pkg/linux-headers-6.8.4.arch1-1-x86_64.pkg.tar.zstthe display has no signal after the boot reaches the line :: Triggering events in the boot output. I get the same result with kernel param i915.enable_fbc=0
Offline