FS#75666 - Massive Kernel issues with 5.19 and Thinkpad X1 Carbon Gen10

Attached to Project: Arch Linux
Opened by Benedict Schlüter (Kakashiy) - Monday, 22 August 2022, 07:35 GMT
Last edited by Toolybird (Toolybird) - Friday, 05 May 2023, 21:32 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
David Runge (dvzrv)
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 9
Private No

Details

Description: Since the update to 5.19, I have many issues with the Kernel. I cannot locate the root cause, but something is messing up the kernel heavily, which also brings it to fail at other parts. From what I can tell, it is somehow Intel driver-related.

Sometimes the laptop isn't booting correctly (nullprt dereference and only a black screen), sometimes there are only errors in dmesg, and sometimes unrelated systemscalls fail and firefox isn't loading the webpage.

I have multiple dmesg kernel logs of this behavior.

Additional info:
* 5.19.2-arch1-2

Steps to reproduce:
Boot recent kernel on a Thinkpad X1 Carbon Gen10 (i7 1260p 32GB Ram 1TB SSD, fm350-gl)
This task depends upon

Closed by  Toolybird (Toolybird)
Friday, 05 May 2023, 21:32 GMT
Reason for closing:  Fixed
Additional comments about closing:  If any further issues crop up, please report upstream.
Comment by mindless_canary (mindless_canary) - Monday, 22 August 2022, 08:11 GMT
I can confirm that for my T480 (Intel Core i5 8250U with Intel UHD Graphics 620, 16GB RAM).
I basically can't use the linux kernel package and had to switch to linux-lts last monday (15.08.). Sometimes the kernel panics with nullptr dereference on loading gdm, sometimes it takes some minutes after logging in.

```
Aug 15 15:03:31 elanor.local kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000
Aug 15 15:03:31 elanor.local kernel: #PF: supervisor instruction fetch in kernel mode
Aug 15 15:03:31 elanor.local kernel: #PF: error_code(0x0010) - not-present page
```

I can't provide any logs. Cause there simply aren't any apart from the above. I can't reproduce anything on tty. It's absolutely frustrating.

Comment by Benedict Schlüter (Kakashiy) - Monday, 22 August 2022, 08:16 GMT
Yep, I also tried a custom kernel, but it seems Linux Firmware hasn't been updated to use GUC 70.XXX (https://www.phoronix.com/news/GuC-Firmware-ADL-P-Linux-5.19). At least the custom Kernel reports GUC 69.XXX. Not sure if I did something wrong or if the Firmware package hasn't been upgraded.
Comment by AK (Andreaskem) - Monday, 22 August 2022, 11:15 GMT
GuC 69 is supposed to be supported. The corresponding commit landed in 5.19rc8:

https://lwn.net/Articles/902348/

Daniele Ceraolo Spurio (1):
drm/i915/guc: support v69 in parallel to v70
Comment by Jozsef Lazar (joelazar) - Monday, 22 August 2022, 14:59 GMT
I'm experiencing some trouble with my Thinkpad X1 Carbon Gen 9 too. I got a kernel panic with 5.19.3 today -->

```
Aug 22 15:02:16 thinkpad-x1 kernel: PKRU: 55555554
Aug 22 15:02:16 thinkpad-x1 kernel: CR2: 0000000000000380 CR3: 000000015e14c001 CR4: 0000000000f70ef0
Aug 22 15:02:16 thinkpad-x1 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 22 15:02:16 thinkpad-x1 kernel: FS: 0000000000000000(0000) GS:ffff945dcf600000(0000) knlGS:0000000000000000
Aug 22 15:02:16 thinkpad-x1 kernel: R13: ffff945ac3c101e8 R14: 0000000000000000 R15: ffff945c2246b6c0
Aug 22 15:02:16 thinkpad-x1 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff945a81edb810
Aug 22 15:02:16 thinkpad-x1 kernel: RBP: ffff945ac3c101a8 R08: 0000000000000000 R09: 0000000000000000
Aug 22 15:02:16 thinkpad-x1 kernel: RDX: 0000000000000380 RSI: ffff945a80051000 RDI: 0000000000000140
Aug 22 15:02:16 thinkpad-x1 kernel: RAX: 0000000000000206 RBX: 0000000000000206 RCX: 000000000b9b2a00
Aug 22 15:02:16 thinkpad-x1 kernel: RSP: 0018:ffffb59e8601fe28 EFLAGS: 00010006
Aug 22 15:02:16 thinkpad-x1 kernel: Code: 00 0f 0b e9 d8 fc ff ff 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 0f 1f 44 00 00 53 9c 58 0f 1f 40 00 48 89 c3 fa 0f 1f 44 00 00 <f0> 48 0f ba 2a 00 73 15 31 c9 80 e7 02 74 06 fb 0f 1f 44 00 00 89
Aug 22 15:02:16 thinkpad-x1 kernel: RIP: 0010:queue_work_on+0x19/0x50
Aug 22 15:02:16 thinkpad-x1 kernel: ---[ end trace 0000000000000000 ]---
Aug 22 15:02:16 thinkpad-x1 kernel: CR2: 0000000000000380
Aug 22 15:02:16 thinkpad-x1 kernel: acpi_cpufreq():1 pcc_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 fjes():1 acpi_cpufreq():1
Aug 22 15:02:16 thinkpad-x1 kernel: Unloaded tainted modules: pcc_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1>
Aug 22 15:02:16 thinkpad-x1 kernel: processor_thermal_device_pci_legacy i2c_hid processor_thermal_device cfg80211 processor_thermal_rfim intel_lpss_pci processor_thermal_mbox mac_hid intel_lpss processor_thermal_rapl intel_hid int3400_thermal intel_rapl_common rfkill idma64 in>
Aug 22 15:02:16 thinkpad-x1 kernel: soundwire_intel soundwire_generic_allocation soundwire_cadence vfat snd_sof_intel_hda fat snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core>
Aug 22 15:02:16 thinkpad-x1 kernel: Modules linked in: iptable_mangle iptable_raw xt_connmark xt_mark ip6table_mangle ip6table_raw wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel udp_tunnel uinput rfco>
Aug 22 15:02:16 thinkpad-x1 kernel: </TASK>
Aug 22 15:02:16 thinkpad-x1 kernel: ret_from_fork+0x1f/0x30
Aug 22 15:02:16 thinkpad-x1 kernel: ? kthread_complete_and_exit+0x20/0x20
Aug 22 15:02:16 thinkpad-x1 kernel: kthread+0x13c/0x160
Aug 22 15:02:16 thinkpad-x1 kernel: ? process_one_work+0x410/0x410
Aug 22 15:02:16 thinkpad-x1 kernel: worker_thread+0x55/0x4d0
Aug 22 15:02:16 thinkpad-x1 kernel: process_one_work+0x255/0x410
Aug 22 15:02:16 thinkpad-x1 kernel: acpi_os_execute_deferred+0x17/0x30
Aug 22 15:02:16 thinkpad-x1 kernel: acpi_ev_notify_dispatch+0x4b/0x63
Aug 22 15:02:16 thinkpad-x1 kernel: ucsi_acpi_notify+0xa8/0xb9 [ucsi_acpi aa80e2b9fc348e78bb20c12eb17c1bdafc3ceb45]
Aug 22 15:02:16 thinkpad-x1 kernel: <TASK>
Aug 22 15:02:16 thinkpad-x1 kernel: Call Trace:
Aug 22 15:02:16 thinkpad-x1 kernel: PKRU: 55555554
Aug 22 15:02:16 thinkpad-x1 kernel: CR2: 0000000000000380 CR3: 000000015e14c001 CR4: 0000000000f70ef0
Aug 22 15:02:16 thinkpad-x1 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 22 15:02:16 thinkpad-x1 kernel: FS: 0000000000000000(0000) GS:ffff945dcf600000(0000) knlGS:0000000000000000
Aug 22 15:02:16 thinkpad-x1 kernel: R13: ffff945ac3c101e8 R14: 0000000000000000 R15: ffff945c2246b6c0
Aug 22 15:02:16 thinkpad-x1 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff945a81edb810
Aug 22 15:02:16 thinkpad-x1 kernel: RBP: ffff945ac3c101a8 R08: 0000000000000000 R09: 0000000000000000
Aug 22 15:02:16 thinkpad-x1 kernel: RDX: 0000000000000380 RSI: ffff945a80051000 RDI: 0000000000000140
Aug 22 15:02:16 thinkpad-x1 kernel: RAX: 0000000000000206 RBX: 0000000000000206 RCX: 000000000b9b2a00
Aug 22 15:02:16 thinkpad-x1 kernel: RSP: 0018:ffffb59e8601fe28 EFLAGS: 00010006
Aug 22 15:02:16 thinkpad-x1 kernel: Code: 00 0f 0b e9 d8 fc ff ff 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 0f 1f 44 00 00 53 9c 58 0f 1f 40 00 48 89 c3 fa 0f 1f 44 00 00 <f0> 48 0f ba 2a 00 73 15 31 c9 80 e7 02 74 06 fb 0f 1f 44 00 00 89
Aug 22 15:02:16 thinkpad-x1 kernel: RIP: 0010:queue_work_on+0x19/0x50
Aug 22 15:02:16 thinkpad-x1 kernel: Workqueue: kacpi_notify acpi_os_execute_deferred
Aug 22 15:02:16 thinkpad-x1 kernel: Hardware name: LENOVO 20XWCTO1WW/20XWCTO1WW, BIOS N32ET76W (1.52 ) 04/08/2022
Aug 22 15:02:16 thinkpad-x1 kernel: CPU: 0 PID: 52605 Comm: kworker/0:0 Tainted: G U OE 5.19.3-zen1-1-zen #1 2e8831c2f52fc0efe7a851816bca15ed55b4761c
Aug 22 15:02:16 thinkpad-x1 kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI
Aug 22 15:02:16 thinkpad-x1 kernel: PGD 0 P4D 0
Aug 22 15:02:16 thinkpad-x1 kernel: #PF: error_code(0x0002) - not-present page
Aug 22 15:02:16 thinkpad-x1 kernel: #PF: supervisor write access in kernel mode
Aug 22 15:02:16 thinkpad-x1 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000380
Aug 22 15:02:15 thinkpad-x1 kernel: usb 3-6.3: USB disconnect, device number 8
Aug 22 15:02:15 thinkpad-x1 kernel: usb 3-6.2: USB disconnect, device number 7
Aug 22 15:02:15 thinkpad-x1 kernel: usb 3-6.1: USB disconnect, device number 6
Aug 22 15:02:15 thinkpad-x1 kernel: usb 3-6: USB disconnect, device number 4
```
Comment by Toolybird (Toolybird) - Wednesday, 24 August 2022, 06:47 GMT
If this is a kernel regression (which it appears to be), you can try to help things along by following [1].

It's also worth:

- trying latest -rc kernel to see if problems are resolved
- performing a git bisection to find the offending commit [2]

then report back here with any findings.

[1] https://wiki.archlinux.org/title/Kernel#Debugging_regressions
[2] https://wiki.archlinux.org/title/Bisecting_bugs_with_Git
Comment by none given (hoban) - Thursday, 25 August 2022, 19:15 GMT
I'm seeing this issue with a similar model (Thinkpad X1 Extreme (Gen 1)):
```
❯ sudo journalctl --since "2022-08-16" | grep "Oops" | tail -3
Aug 22 09:55:24 x1e kernel: Oops: 0010 [#38] PREEMPT SMP PTI
Aug 22 09:55:39 x1e kernel: Oops: 0010 [#39] PREEMPT SMP PTI
Aug 22 09:55:39 x1e kernel: Oops: 0010 [#40] PREEMPT SMP PTI

❯ sudo journalctl --since "2022-08-16" | grep "Oops" | wc -l
1013
```

I stopped seeing those logs & stopped having system lock ups by downgrading & ignoring upgrades for the following packages:
```
warning: linux: ignoring package upgrade (5.18.16.arch1-1 => 5.19.3.arch1-1)
warning: linux-headers: ignoring package upgrade (5.18.16.arch1-1 => 5.19.3.arch1-1)
warning: nvidia: ignoring package upgrade (515.65.01-2 => 515.65.01-8)
```

I think maybe https://bbs.archlinux.org/viewtopic.php?id=279027 is related. I'll mention this bug report also.
Comment by Benedict Schlüter (Kakashiy) - Friday, 26 August 2022, 11:07 GMT
I try to bisect it over the weekend (can take some time to compile tho), but 5.18 was fine, so I assume was introduced somewhere in 5.19
Comment by loqs (loqs) - Friday, 26 August 2022, 20:02 GMT
You can find some prebuilt bisection kernels in https://bbs.archlinux.org/viewtopic.php?id=279027&p=2 that may help.
Edit:
One issue was bisected to 87d0e2f41b8cc2018499be4e8003fa8c09b6f2fb https://bugzilla.kernel.org/show_bug.cgi?id=216422
Comment by Adam Beavan (ajbeavan) - Monday, 05 September 2022, 19:17 GMT
I have the same problem with continual freezing, but nothing in the log files
Comment by loqs (loqs) - Monday, 05 September 2022, 20:04 GMT Comment by loqs (loqs) - Thursday, 08 September 2022, 22:27 GMT
Is the issue resolved with linux 5.19.8.arch1-1 now in testing?
Comment by Benedict Schlüter (Kakashiy) - Sunday, 11 September 2022, 07:44 GMT
Nope, testd with 5.19.8.arch1-1 and still the same issue as in the logs above. Tried to bisect it and apparently it was introduced in the 5.19 merge window. Vanilla mainline still has the same issue. Problem is that my X1 throttled down to 0.8GHz if I have heavy load on the machine (good job Lenovo) so it takes some to time to recompile every time.
Comment by loqs (loqs) - Sunday, 11 September 2022, 08:51 GMT
If it helps I can build the bisection kernels for you. I would need your current `git bisect log`.
Comment by Benedict Schlüter (Kakashiy) - Sunday, 11 September 2022, 20:24 GMT
Thanks, I already managed to get some results. However, not very useful since this bug only appears occasionally, it is hard to tell whether the current commit is stable or not. Nevertheless, I hypothesize that some of the introduced i915 changes caused the bug. Attached is the journalctl log of the 5.19.8 crash.
Comment by loqs (loqs) - Sunday, 11 September 2022, 20:28 GMT
I would suggest trying 6.0-rc5 after it is released see if the issue has already been fixed upstream.
Comment by Benedict Schlüter (Kakashiy) - Sunday, 11 September 2022, 20:35 GMT
I tried the current master (b96fbd602d35739b5cdb49baa02048f2c41fdab1), but this was extremely unstable. Had Some errors in the filesystem driver or something related and my /var/log dir got corrupted. Had to run xfs_repair. But before I could boot into my WM, I had one or two crashes. So at least right now it is not fixed :(

I wonder if this is solved on the other Thinkpad models since my log looks different from theirs.
Comment by Iyan (iyanmv) - Saturday, 17 September 2022, 10:19 GMT
I have a Thinkpad X1 Yoga Gen 6 (exactly same hardware as the Thinkpad X1 Carbon Gen 9 except for the screen) and I haven't notice any of the issues described here. Are all of you using the latest BIOS/firmware from Lenovo?
Comment by Benedict Schlüter (Kakashiy) - Monday, 03 October 2022, 07:58 GMT
Yes, I am using the newest firmware. I've tested on 6.0.0 now, and it seems to work (booted multiple times without a panic).
Comment by shapeshifter (shapeshifter) - Tuesday, 11 October 2022, 13:54 GMT
I'm also having similar problems with a new Lenovo X1 Yoga Gen7. Attached are two logs.

gpf.txt: general protection fault; swaywm completely froze while I was using the pen. I noticed that I could unplug and replug the external screen and it would come back, so "something" was still alive, but I could not switch to another TTY or do anything to recover. The log also shows that it registered lid closing etc.

i915.txt: this happened directly after booting. When booting, I get the login prompt (no DM) and I can log in. If I run sway *immediately*, I get an error from [wlr] that they can't open any DRM device. Seems like the GPU isn't ready. After a few seconds, the screen brightness changes and now I can run sway. But sometimes, as in the case of this log, the kernel panics if I run sway right around the time that the GPU becomes ready.
   gpf.txt (12.1 KiB)
   i915.txt (7.8 KiB)
Comment by Benedict Schlüter (Kakashiy) - Thursday, 13 October 2022, 17:52 GMT
Fixed for me now with 6.0.1-arch1-1. Can someone confirm?
Comment by shapeshifter (shapeshifter) - Friday, 14 October 2022, 21:47 GMT
Well I can't say it got much better with Linux 6. I get a kernel panic during boot that throws me into the recovery shell. But the machine keeps booting and if I exit the recovery shell after a couple of seconds, it boots successfully.

Kernel bug attached.
Comment by shapeshifter (shapeshifter) - Saturday, 15 October 2022, 12:55 GMT
Actually it got a lot worse. Sometimes, shortly after booting, I now get several crashes per second (logs attached) and the machine also won't shut down any more being stuck at:

[ OK ] Finished System Reboot.
[ OK ] Reached target System Reboot.
** 367 printk messages dropped **
[ 562.471444] watchdog: watchdog0: watchdog did not stop!

Sometimes this just doesn't happen and then it's fine. But in any case, it always freezes randomly after a few hours of running.
Comment by Iyan (iyanmv) - Saturday, 15 October 2022, 16:14 GMT
shapeshifter: Try updating the BIOS with fwupdmgr
Comment by shapeshifter (shapeshifter) - Sunday, 16 October 2022, 09:29 GMT
Iyan: I already had.

This morning again I was greeted by a blinking capslock light indicating a kernel crash. No logs. I'll try adding intel_idle.max_cstate=1 i915.enable_dc=0 ahci.mobile_lpm_policy=1 now to see if any of those help at all...
Comment by Tobias Brunner (tobru) - Monday, 17 October 2022, 06:36 GMT
I can confirm that it isn't any better on my device (X1 Carbon Gen 10).

Example:

```
Okt 17 07:55:11 carbon kernel: ------------[ cut here ]------------
Okt 17 07:55:11 carbon kernel: i915 0000:00:02.0: Block 42 min_size is zero
Okt 17 07:55:11 carbon kernel: WARNING: CPU: 15 PID: 602 at drivers/gpu/drm/i915/display/intel_bios.c:477 intel_bios_init+0x84b/0x1ea0 [i915]
Okt 17 07:55:11 carbon kernel: Modules linked in: pcc_cpufreq(-) idma64 acpi_cpufreq(-) cfg80211 i915(+) processor_thermal_device_pci thunderbolt(+) processor_thermal_device processor_thermal_rfim drm_buddy processor_thermal_mbox intel_vsec tpm_crb processor_thermal_rapl ttm intel_rapl_common drm_display_helper cec ucsi_acpi intel_gtt typec_ucsi typec tpm_tis igen6_edac tpm_tis_core roles wmi mac_hid nxp_nci_i2c nxp_nci thinkpad_acpi nci ledtrig_audio platform_profile i2c_hid_acpi nfc snd i2c_hid soundcore int3403_thermal int340x_thermal_zone soc_button_array video intel_hid sparse_keymap int3400_thermal acpi_thermal_rel acpi_tad acpi_pad btusb btrtl btbcm btintel btmtk bluetooth ecdh_generic rfkill crypto_user acpi_call(OE) fuse bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 dm_crypt cbc encrypted_keys trusted asn1_encoder tee tpm rng_core dm_mod serio_raw atkbd crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni polyval_generic libps2 gf128mul vivaldi_fmap nvme
Okt 17 07:55:11 carbon kernel: ghash_clmulni_intel aesni_intel crypto_simd nvme_core xhci_pci cryptd xhci_pci_renesas nvme_common i8042 serio
Okt 17 07:55:11 carbon kernel: Unloaded tainted modules: pcc_cpufreq():1 acpi_cpufreq():1 fjes():1 fjes():1 pcc_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 fjes():1 acpi_cpufreq():1 pcc_cpufreq():1 fjes():1 acpi_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 fjes():1 fjes():1 pcc_cpufreq():1 acpi_cpufreq():1 fjes():1 acpi_cpufreq():1 pcc_cpufreq():1 fjes():1 pcc_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1
Okt 17 07:55:11 carbon kernel: CPU: 15 PID: 602 Comm: systemd-udevd Tainted: G OE 6.0.1-arch1-1 #1 773d2fab595a0bd9100530a8ec29fc4b17be47c9
Okt 17 07:55:11 carbon kernel: Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET66W (1.31 ) 09/09/2022
Okt 17 07:55:11 carbon kernel: RIP: 0010:intel_bios_init+0x84b/0x1ea0 [i915]
Okt 17 07:55:11 carbon kernel: Code: 48 8b 78 08 4c 8b 7f 50 4d 85 ff 75 03 4c 8b 3f e8 3a 4e 81 ea 44 89 e9 4c 89 fa 48 c7 c7 60 9b 0d c1 48 89 c6 e8 54 d3 bd ea <0f> 0b e9 d3 fb ff ff 48 89 df 49 83 c6 10 e8 72 8d 36 ea 48 c7 c0
Okt 17 07:55:11 carbon kernel: RSP: 0000:ffffb3f880ffba50 EFLAGS: 00010286
Okt 17 07:55:11 carbon kernel: RAX: 0000000000000000 RBX: ffffb3f8810048f3 RCX: 0000000000000027
Okt 17 07:55:11 carbon kernel: RDX: ffffa0d8ff7e1668 RSI: 0000000000000001 RDI: ffffa0d8ff7e1660
Okt 17 07:55:11 carbon kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffffb3f880ffb8d8
Okt 17 07:55:11 carbon kernel: R10: 0000000000000003 R11: ffffffffacccb508 R12: 0000000000000000
Okt 17 07:55:11 carbon kernel: R13: 000000000000002a R14: ffffffffc10a6ad8 R15: ffffa0d1c2c0bd80
Okt 17 07:55:11 carbon kernel: FS: 00007fd62894f200(0000) GS:ffffa0d8ff7c0000(0000) knlGS:0000000000000000
Okt 17 07:55:11 carbon kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Okt 17 07:55:11 carbon kernel: CR2: 000055b9ce7d3378 CR3: 0000000108120005 CR4: 0000000000f70ee0
Okt 17 07:55:11 carbon kernel: PKRU: 55555554
Okt 17 07:55:11 carbon kernel: Call Trace:
Okt 17 07:55:11 carbon kernel: <TASK>
Okt 17 07:55:11 carbon kernel: ? drm_vblank_worker_init+0x6b/0x80
Okt 17 07:55:11 carbon kernel: intel_modeset_init_noirq+0x39/0x240 [i915 dd9f3eb412454e575fe47632c732050a55c3a43e]
Okt 17 07:55:11 carbon kernel: i915_driver_probe+0x476/0xd70 [i915 dd9f3eb412454e575fe47632c732050a55c3a43e]
Okt 17 07:55:11 carbon kernel: ? intel_modeset_probe_defer+0x4f/0x60 [i915 dd9f3eb412454e575fe47632c732050a55c3a43e]
Okt 17 07:55:11 carbon kernel: ? i915_pci_probe+0x43/0x160 [i915 dd9f3eb412454e575fe47632c732050a55c3a43e]
Okt 17 07:55:11 carbon kernel: local_pci_probe+0x42/0x80
Okt 17 07:55:11 carbon kernel: pci_device_probe+0xc1/0x220
Okt 17 07:55:11 carbon kernel: ? sysfs_do_create_link_sd+0x6e/0xe0
Okt 17 07:55:11 carbon kernel: really_probe+0xdb/0x380
Okt 17 07:55:11 carbon kernel: ? pm_runtime_barrier+0x54/0x90
Okt 17 07:55:11 carbon kernel: __driver_probe_device+0x78/0x170
Okt 17 07:55:11 carbon kernel: driver_probe_device+0x1f/0x90
Okt 17 07:55:11 carbon kernel: __driver_attach+0xd5/0x1d0
Okt 17 07:55:11 carbon kernel: ? __device_attach_driver+0x110/0x110
Okt 17 07:55:11 carbon kernel: bus_for_each_dev+0x88/0xd0
Okt 17 07:55:11 carbon kernel: bus_add_driver+0x1b2/0x200
Okt 17 07:55:11 carbon kernel: driver_register+0x8d/0xe0
Okt 17 07:55:11 carbon kernel: i915_init+0x23/0x83 [i915 dd9f3eb412454e575fe47632c732050a55c3a43e]
Okt 17 07:55:11 carbon kernel: ? 0xffffffffc1204000
Okt 17 07:55:11 carbon kernel: do_one_initcall+0x5a/0x220
Okt 17 07:55:11 carbon kernel: do_init_module+0x4a/0x1e0
Okt 17 07:55:11 carbon kernel: __do_sys_init_module+0x17f/0x1b0
Okt 17 07:55:11 carbon kernel: do_syscall_64+0x5c/0x90
Okt 17 07:55:11 carbon kernel: ? syscall_exit_to_user_mode+0x1b/0x40
Okt 17 07:55:11 carbon kernel: ? do_syscall_64+0x6b/0x90
Okt 17 07:55:11 carbon kernel: ? exc_page_fault+0x74/0x170
Okt 17 07:55:11 carbon kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd
Okt 17 07:55:11 carbon kernel: RIP: 0033:0x7fd6292e8eae
Okt 17 07:55:11 carbon kernel: Code: 48 8b 0d dd ee 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d aa ee 0c 00 f7 d8 64 89 01 48
Okt 17 07:55:11 carbon kernel: RSP: 002b:00007ffe745e4e18 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
Okt 17 07:55:11 carbon kernel: RAX: ffffffffffffffda RBX: 000055ebb8c1c840 RCX: 00007fd6292e8eae
Okt 17 07:55:11 carbon kernel: RDX: 00007fd629733343 RSI: 00000000006a7e60 RDI: 00007fd626e2d010
Okt 17 07:55:11 carbon kernel: RBP: 00007fd629733343 R08: 0000000000261000 R09: 9e3779b185ebca87
Okt 17 07:55:11 carbon kernel: R10: 000000000000f681 R11: 0000000000000246 R12: 0000000000020000
Okt 17 07:55:11 carbon kernel: R13: 000055ebb8b636c0 R14: 000055ebb8c1c840 R15: 000055ebb8c0e130
Okt 17 07:55:11 carbon kernel: </TASK>
Okt 17 07:55:11 carbon kernel: ---[ end trace 0000000000000000 ]---
```

All firmware is up-to-date, fwupdmgr doesn't show any new versions.
Comment by CS (JMP64i) - Tuesday, 21 February 2023, 14:28 GMT Comment by CS (JMP64i) - Tuesday, 02 May 2023, 09:55 GMT
Are these errors still present? Because on my devices all problems like that are solved.

Loading...