Additional info: reporter: libreport-2.14.0 WARNING: CPU: 4 PID: 237 at drivers/char/tpm/tpm_tis_core.c:249 tpm_tis_status+0x66/0x70 Modules linked in: fuse CPU: 4 PID: 237 Comm: rngd Not tainted 5.10.9-201.fc33.x86_64 #1 Hardware name: Dell Inc. XPS 13 9310/0GG9PT, BIOS 1.2.5 12/10/2020 RIP: 0010:tpm_tis_status+0x66/0x70 Code: 23 75 05 48 83 c4 10 c3 31 c0 80 3d 90 e3 56 01 00 75 f0 48 c7 c7 44 32 43 a6 88 44 24 07 c6 05 7c e3 56 01 01 e8 57 e7 3b 00 <0f> 0b 0f b6 44 24 07 eb d0 90 0f 1f 44 00 00 41 57 41 56 41 55 41 RSP: 0018:ffffa11f4033bcd0 EFLAGS: 00010286 RAX: 000000000000001b RBX: ffff89a387c08000 RCX: ffff89a6ff718a88 RDX: 00000000ffffffd8 RSI: 0000000000000027 RDI: ffff89a6ff718a80 RBP: ffff89a387c08000 R08: 0000000000000000 R09: ffffa11f4033bb00 R10: ffffa11f4033baf8 R11: ffffffffa6b44748 R12: ffff89a387bff1a8 R13: ffff89a388409000 R14: 0000000000000000 R15: ffffa11f4033bd8a FS: 00007f432a15a840(0000) GS:ffff89a6ff700000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fa789ec4000 CR3: 0000000107eea004 CR4: 0000000000770ee0 PKRU: 55555554 Call Trace: tpm_tis_send_data+0x2b/0x230 ? tpm_tcg_write_bytes+0x33/0x50 tpm_tis_send_main+0x1e/0xe0 tpm_transmit+0xd8/0x3d0 tpm_transmit_cmd+0x25/0x90 tpm2_get_random+0xd7/0x1d0 ? tpm_chip_start+0x6a/0xb0 tpm_get_random+0x5b/0x70 rng_dev_read+0x1b8/0x2c0 vfs_read+0xab/0x1a0 ksys_read+0x4f/0xc0 do_syscall_64+0x33/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f432a9da0fc Code: ec 28 48 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 19 fc ff ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 34 44 89 c7 48 89 44 24 08 e8 6f fc ff ff 48 RSP: 002b:00007ffc3337e180 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 RAX: ffffffffffffffda RBX: 00000000000009c4 RCX: 00007f432a9da0fc RDX: 00000000000009c4 RSI: 00007ffc3337e200 RDI: 0000000000000003 RBP: 00007ffc3337e200 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000008 R11: 0000000000000246 R12: 000055f69ebd36c0 R13: 0000000000000000 R14: 00007ffc3337e200 R15: 000055f69ebd36f0
Created attachment 1750889 [details] File: dmesg
Description of problem: happened on startup Version-Release number of selected component: kernel-core-5.10.11-200.fc33 Additional info: reporter: libreport-2.14.0 cmdline: BOOT_IMAGE=(hd1,gpt2)/vmlinuz-5.10.11-200.fc33.x86_64 root=UUID=83da62ea-0e0b-4e0a-9420-1133da62f016 ro rootflags=subvol=root rhgb quiet crash_function: tpm_tis_send_data kernel: 5.10.11-200.fc33.x86_64 runlevel: unknown type: Kerneloops Truncated backtrace: WARNING: CPU: 7 PID: 237 at drivers/char/tpm/tpm_tis_core.c:249 tpm_tis_status+0x66/0x70 Modules linked in: fuse CPU: 7 PID: 237 Comm: rngd Not tainted 5.10.11-200.fc33.x86_64 #1 Hardware name: Dell Inc. Precision 5550/084FKM, BIOS 1.6.1 12/24/2020 RIP: 0010:tpm_tis_status+0x66/0x70 Code: 23 75 05 48 83 c4 10 c3 31 c0 80 3d 00 e1 56 01 00 75 f0 48 c7 c7 2c 37 43 85 88 44 24 07 c6 05 ec e0 56 01 01 e8 cb 03 3c 00 <0f> 0b 0f b6 44 24 07 eb d0 90 0f 1f 44 00 00 41 57 41 56 41 55 41 RSP: 0018:ffffa476c02f3cd0 EFLAGS: 00010286 RAX: 000000000000001b RBX: ffff91054012f000 RCX: ffff9108bd7d8a88 RDX: 00000000ffffffd8 RSI: 0000000000000027 RDI: ffff9108bd7d8a80 RBP: ffff91054012f000 R08: 0000000000000000 R09: ffffa476c02f3b00 R10: ffffa476c02f3af8 R11: ffffffff85b44748 R12: ffff910547800868 R13: ffff910548496000 R14: 0000000000000000 R15: ffffa476c02f3d8a FS: 00007f162cd78840(0000) GS:ffff9108bd7c0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ffcb7f1fd28 CR3: 0000000108086002 CR4: 00000000007706e0 PKRU: 55555554 Call Trace: tpm_tis_send_data+0x2b/0x230 ? tpm_tcg_write_bytes+0x33/0x50 tpm_tis_send_main+0x1e/0xe0 tpm_transmit+0xd8/0x3d0 tpm_transmit_cmd+0x25/0x90 tpm2_get_random+0xd7/0x1d0 ? tpm_chip_start+0x6a/0xb0 tpm_get_random+0x5b/0x70 rng_dev_read+0x1b8/0x2c0 vfs_read+0xab/0x1a0 ksys_read+0x4f/0xc0 do_syscall_64+0x33/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f162d5f80fc Code: ec 28 48 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 19 fc ff ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 34 44 89 c7 48 89 44 24 08 e8 6f fc ff ff 48 RSP: 002b:00007ffc36ea8300 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 RAX: ffffffffffffffda RBX: 00000000000009c4 RCX: 00007f162d5f80fc RDX: 00000000000009c4 RSI: 00007ffc36ea8380 RDI: 0000000000000003 RBP: 00007ffc36ea8380 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000008 R11: 0000000000000246 R12: 00005627fd6c16c0 R13: 0000000000000000 R14: 00007ffc36ea8380 R15: 00005627fd6c16f0
*** Bug 1931262 has been marked as a duplicate of this bug. ***
*** Bug 1934034 has been marked as a duplicate of this bug. ***
Description of problem: restarted system after update Version-Release number of selected component: kernel-core-5.10.19-200.fc33 Additional info: reporter: libreport-2.14.0 cmdline: BOOT_IMAGE=(hd0,gpt3)/vmlinuz-5.10.19-200.fc33.x86_64 root=UUID=36e1c0c8-718f-4da7-bcca-afeac6b02685 ro rootflags=subvol=root rhgb quiet crash_function: tpm_tis_send_data kernel: 5.10.19-200.fc33.x86_64 runlevel: unknown type: Kerneloops Truncated backtrace: WARNING: CPU: 4 PID: 293 at drivers/char/tpm/tpm_tis_core.c:249 tpm_tis_status+0x66/0x70 Modules linked in: hid_sensor_hub intel_ishtp_loader intel_ishtp_hid i915 nouveau hid_multitouch mxm_wmi ttm rtsx_pci_sdmmc i2c_algo_bit mmc_core drm_kms_helper cec crct10dif_pclmul crc32_pclmul crc32c_intel drm nvme intel_ish_ipc ghash_clmulni_intel nvme_core rtsx_pci serio_raw intel_ishtp wmi i2c_hid video pinctrl_cannonlake fuse CPU: 4 PID: 293 Comm: rngd Not tainted 5.10.19-200.fc33.x86_64 #1 Hardware name: Dell Inc. XPS 15 9500/0XWT2F, BIOS 1.6.1 12/24/2020 RIP: 0010:tpm_tis_status+0x66/0x70 Code: 23 75 05 48 83 c4 10 c3 31 c0 80 3d 3f ce 56 01 00 75 f0 48 c7 c7 24 3a 43 85 88 44 24 07 c6 05 2b ce 56 01 01 e8 ff 10 3c 00 <0f> 0b 0f b6 44 24 07 eb d0 90 0f 1f 44 00 00 41 57 41 56 41 55 41 RSP: 0018:ffffafe64048bcd0 EFLAGS: 00010286 RAX: 000000000000001b RBX: ffff94f108b92000 RCX: ffff95004d518a88 RDX: 00000000ffffffd8 RSI: 0000000000000027 RDI: ffff95004d518a80 RBP: ffff94f108b92000 R08: 0000000000000000 R09: ffffafe64048bb00 R10: ffffafe64048baf8 R11: ffffffff85b44748 R12: ffff94f108c780e8 R13: ffff94f101e2c000 R14: 0000000000000000 R15: ffffafe64048bd8a FS: 00007f69afeb5840(0000) GS:ffff95004d500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f9512bfc0a8 CR3: 000000010921c004 CR4: 00000000007706e0 PKRU: 55555554 Call Trace: tpm_tis_send_data+0x2b/0x230 tpm_tis_send_main+0x1e/0xe0 tpm_transmit+0xd8/0x3d0 tpm_transmit_cmd+0x25/0x90 tpm2_get_random+0xd7/0x1d0 ? tpm_chip_start+0x6a/0xb0 tpm_get_random+0x5b/0x70 rng_dev_read+0x1b8/0x2c0 vfs_read+0xab/0x1a0 ksys_read+0x4f/0xc0 do_syscall_64+0x33/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f69b07390fc Code: ec 28 48 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 19 fc ff ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 34 44 89 c7 48 89 44 24 08 e8 6f fc ff ff 48 RSP: 002b:00007fff05803bf0 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 RAX: ffffffffffffffda RBX: 00000000000009c4 RCX: 00007f69b07390fc RDX: 00000000000009c4 RSI: 00007fff05803c70 RDI: 0000000000000003 RBP: 00007fff05803c70 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000008 R11: 0000000000000246 R12: 000055761171f6c0 R13: 0000000000000000 R14: 00007fff05803c70 R15: 000055761171f6f0
*** Bug 1934713 has been marked as a duplicate of this bug. ***
*** Bug 1939529 has been marked as a duplicate of this bug. ***
*** Bug 1941183 has been marked as a duplicate of this bug. ***
Description of problem: I just booted the system. As soon as I logged in, the abrt notification popped up. Version-Release number of selected component: kernel-core-5.11.7-200.fc33 Additional info: reporter: libreport-2.14.0 cmdline: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.11.7-200.fc33.x86_64 root=UUID=dbf6b658-2ff2-4bc4-a9cf-d0e516d2c194 ro rootflags=subvol=root rhgb quiet crash_function: tpm_tis_send_data kernel: 5.11.7-200.fc33.x86_64 runlevel: unknown type: Kerneloops Truncated backtrace: #1 tpm_tis_send_data #2 tpm_tis_send_main #3 tpm_transmit #4 tpm_transmit_cmd #5 tpm2_get_random #6 ? tpm_chip_start #7 tpm_get_random #8 rng_dev_read #9 vfs_read #10 ksys_read
*** Bug 1941564 has been marked as a duplicate of this bug. ***
*** Bug 1945561 has been marked as a duplicate of this bug. ***
*** Bug 1946068 has been marked as a duplicate of this bug. ***
*** Bug 1946730 has been marked as a duplicate of this bug. ***
Description of problem: I the steps which got me here are: 1. Cold boot 2. Unlock Disk Encryption 3. Enter username & password with a valid network connection but no connection to our LDAP server 4. Something causes this session to crash to login manager before I get a session 5. Enter username & password again, still with no LDAP connection 6. this hangs for ~5 minutes, before logging in But this might be a complete red herring. Steps 1-5 are normal for this device Version-Release number of selected component: kernel-core-5.11.11-200.fc33 Additional info: reporter: libreport-2.14.0 cmdline: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.11.11-200.fc33.x86_64 root=/dev/mapper/vg-root ro resume=/dev/mapper/vg-swap rd.luks.uuid=luks-56918aa4-5b97-438c-bb5c-ecae477f2cfb rd.lvm.lv=vg/root rd.lvm.lv=vg/swap rhgb quiet crash_function: tpm_tis_send_data kernel: 5.11.11-200.fc33.x86_64 runlevel: unknown type: Kerneloops Truncated backtrace: #1 tpm_tis_send_data #2 tpm_tis_send_main #3 tpm_transmit #4 tpm_transmit_cmd #5 tpm2_get_random #6 ? tpm_chip_start #7 tpm_get_random #8 rng_dev_read #9 vfs_read #10 ksys_read
Description of problem: I've just upgraded the kernel to this version (5.11.18-200.fc33.x86_64) and this error appeared right after boot. Version-Release number of selected component: kernel-core-5.11.18-200.fc33 Additional info: reporter: libreport-2.14.0 cmdline: BOOT_IMAGE=(hd2,gpt2)/vmlinuz-5.11.18-200.fc33.x86_64 root=UUID=1cd6d8ad-c103-4ba3-9933-c73e5bedc506 ro rootflags=subvol=root rd.luks.uuid=luks-e83d9dcf-bc1f-49c4-ac86-3a79a61becb3 rhgb quiet systemd.unified_cgroup_hierarchy=0 crash_function: tpm_tis_send_data kernel: 5.11.18-200.fc33.x86_64 runlevel: N 5 type: Kerneloops Truncated backtrace: WARNING: CPU: 10 PID: 268 at drivers/char/tpm/tpm_tis_core.c:205 tpm_tis_status+0x66/0x70 Modules linked in: hid_sensor_hub intel_ishtp_loader intel_ishtp_hid i915 nouveau hid_multitouch mxm_wmi drm_ttm_helper ttm i2c_algo_bit drm_kms_helper rtsx_pci_sdmmc mmc_core cec crct10dif_pclmul crc32_pclmul crc32c_intel drm ghash_clmulni_intel nvme serio_raw nvme_core rtsx_pci intel_ish_ipc wmi intel_ishtp i2c_hid video pinctrl_cannonlake fuse CPU: 10 PID: 268 Comm: rngd Not tainted 5.11.18-200.fc33.x86_64 #1 Hardware name: Dell Inc. XPS 15 9500/0RHXRG, BIOS 1.6.1 12/24/2020 RIP: 0010:tpm_tis_status+0x66/0x70 Code: 23 75 05 48 83 c4 10 c3 31 c0 80 3d 38 02 56 01 00 75 f0 48 c7 c7 94 67 43 aa 88 44 24 07 c6 05 24 02 56 01 01 e8 4a 53 3c 00 <0f> 0b 0f b6 44 24 07 eb d0 90 0f 1f 44 00 00 41 57 41 56 41 55 41 RSP: 0018:ffffb2018056fcd0 EFLAGS: 00010286 RAX: 000000000000001b RBX: ffff98bc07d73000 RCX: ffff98bf7d698ac8 RDX: 00000000ffffffd8 RSI: 0000000000000027 RDI: ffff98bf7d698ac0 RBP: ffff98bc07d73000 R08: 0000000000000000 R09: ffffb2018056fb00 R10: ffffb2018056faf8 R11: ffffffffaab44f08 R12: ffff98bc07e637a8 R13: ffff98bc08d79000 R14: 0000000000000000 R15: ffffb2018056fd8a FS: 00007fbb6f7af840(0000) GS:ffff98bf7d680000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005607f7fb9b08 CR3: 0000000107e84005 CR4: 00000000007706e0 PKRU: 55555554 Call Trace: tpm_tis_send_data+0x2b/0x230 tpm_tis_send_main+0x1e/0xe0 tpm_transmit+0xd8/0x3d0 tpm_transmit_cmd+0x25/0x90 tpm2_get_random+0xd7/0x1d0 ? tpm_chip_start+0x6a/0xb0 tpm_get_random+0x5b/0x70 rng_dev_read+0x1c0/0x2b0 vfs_read+0xab/0x1a0 ksys_read+0x4f/0xc0 do_syscall_64+0x33/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fbb6ffd10fc Code: ec 28 48 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 19 fc ff ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 34 44 89 c7 48 89 44 24 08 e8 6f fc ff ff 48 RSP: 002b:00007ffc020547c0 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 RAX: ffffffffffffffda RBX: 00000000000009c4 RCX: 00007fbb6ffd10fc RDX: 00000000000009c4 RSI: 00007ffc02054840 RDI: 0000000000000003 RBP: 00007ffc02054840 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000008 R11: 0000000000000246 R12: 000055f2bfde6760 R13: 0000000000000000 R14: 00007ffc02054840 R15: 000055f2bfde6760
*** Bug 1966637 has been marked as a duplicate of this bug. ***
*** Bug 1966641 has been marked as a duplicate of this bug. ***
A quick status update on this, kernel 5.12.6 and newer contains a set of fixes which seems to fix all tpm_tis related kernel oopses/backtraces, except for a set of 3 (sofar) different backtraces, which all only seem to happen on "Dell Inc. XPS 13 9310" models. Note the original backtrace here was on a "Dell Inc. XPS 15 9500", but since the 5.12.6 kernel release we have so far only seen this (and the 2 other) backtrace happen on the "Dell Inc. XPS 13 9310" model.
Everyone who is seeing this, can you please try the following: 1. Run "dmesg --level=warn" and check that your currently still seeing this problem. If you are still seeing this problem then the "dmesg --level=warn" output should include a backtrace similar to the one from comment 0. 2. If you are still seeing this problem, please run: "sudo grubby --update-kernel=ALL --args=tpm_tis.interrupts=0"; and then reboot (first save any work you may have open). 3. After rebooting run "dmesg --level=warn" again and see the problem still persists. Please let us know if adding tpm_tis.interrupts=0 to the kernel commandline like this helps.
Setting tpm_tis.interrupts=0 has silenced this issue for me on a Dell Precision 5550, Fedora 34. Thanks!
Jordan, thank you for testing, have you perhaps also switched to a new kernel at the same time? Specifically a kernel >= 5.12.6 ? 5.12.6 contains a bunch of TPM fixes and seems to resolve this issue without needing the tpm_tis.interrupts=0 parameter. Either way it would be good if you can test of tpm_tis.interrupts=0 is still necessary with kernel versions >= 5.12.6 . The reason I was still asking about testing with tpm_tis.interrupts=0 is because of this still happening with "Dell Inc. XPS 13 9310" models. With newer kernels that seems to be the only model where this is still happening though, so hopefully things will work fine even without tpm_tis.interrupts=0 on your Dell Precision 5550.
Hans, thanks for the quick reply. Looks like I don't need the kernel parameter anymore as the warning no longer appears. I'm using kernel 5.12.8 according to uname. ➜ uname -a Linux fedora 5.12.8-300.fc34.x86_64 #1 SMP Fri May 28 15:20:54 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux My initial dmesg output shows the boot command-line doesn't have the tpm_tis.interrupts=0 option. [ 0.000000] Linux version 5.12.8-300.fc34.x86_64 (mockbuild.fedoraproject.org) (gcc (GCC) 11.1.1 20210428 (Red Hat 11.1.1-1), GNU ld version 2.35.1-41.fc34) #1 SMP Fri May 28 15:20:54 UTC 2021 [ 0.000000] Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.12.8-300.fc34.x86_64 root=UUID=4d740417-526d-4c29-9711-3d1acb3c579d ro rootflags=subvol=root rd.luks.uuid=luks-8c4845be-8495-406d-a634-2d7265698bda rhgb quiet And for completeness, here is the output of dmesg --level=warn. [ 0.173488] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' [ 0.739587] efifb: Ignoring BGRT: unexpected or invalid BMP data [ 0.808270] usb: port power management may be unreliable [ 0.810693] i8042: Warning: Keylock active [ 1.153662] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) [ 1.153707] wmi_bus wmi_bus-PNP0C14:03: WQBC data block query control method not found [ 1.153708] acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) [ 1.314741] ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210105/nsarguments-61) [ 1.314773] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210105/nsarguments-61) [ 6.409821] r8152 4-2.4:1.0 (unnamed net_device) (uninitialized): Invalid header when reading pass-thru MAC addr [ 6.482959] kauditd_printk_skb: 8 callbacks suppressed [ 61.143690] kauditd_printk_skb: 3 callbacks suppressed [ 61.637519] systemd-sysv-generator[1563]: SysV service '/etc/rc.d/init.d/livesys' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. [ 61.637566] systemd-sysv-generator[1563]: SysV service '/etc/rc.d/init.d/livesys-late' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. [ 62.067543] iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver [ 62.284922] thermal thermal_zone13: failed to read out thermal zone (-61) [ 63.203518] Bluetooth: hci0: MSFT filter_enable is already on [ 1764.057106] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #08!!!
Thank you for looking into this problem. I am on kernel 5.12.8-300 and don't see this problem any more. For what it's worth: I am using a "Dell Inc. XPS 13 9310" and saw this bug with an earlier kernel. I don't remember when it stopped happening though. ---Florian
Still happens on 5.12.9-200 (F33) as well.
(In reply to Steven Bakker from comment #24) > Still happens on 5.12.9-200 (F33) as well. What laptop model are you seeing this on. I guess you are using a Dell XPS 13 9310 ? Quoting from comment 19: """ Everyone who is seeing this, can you please try the following: 1. Run "dmesg --level=warn" and check that your currently still seeing this problem. If you are still seeing this problem then the "dmesg --level=warn" output should include a backtrace similar to the one from comment 0. 2. If you are still seeing this problem, please run: "sudo grubby --update-kernel=ALL --args=tpm_tis.interrupts=0"; and then reboot (first save any work you may have open). 3. After rebooting run "dmesg --level=warn" again and see the problem still persists. Please let us know if adding tpm_tis.interrupts=0 to the kernel commandline like this helps. """ As you say this still happens, 1. is already done, so please run the provided grubby command to add "tpm_tis.interrupts=0" to your kernel commandline and see if that helps.
Hi Hans, Yes, it's an XPS 13 9310. Will try the suggested actions.
The "tpm_tis.interrupts=0" seems to have done the trick. No more crash report on boot.
(In reply to Steven Bakker from comment #27) > The "tpm_tis.interrupts=0" seems to have done the trick. No more crash > report on boot. Great, just to be sure can you run: sudo grubby --update-kernel=ALL --remove-args=tpm_tis.interrupts=0 To undo the workaround, reboot and confirm that the problem then comes back (it should be visible in "dmesg --level=warn" output if it is back) ? We have had some cases where this seemed fixed but it turned out that the problem happed sporadically rather then every boot. I've reported your findings upstream, since with the latest batch of fixes (which landed in 5.12.6) all tpm_tis problems seems to be resolved except on the Dell XPS 13 9310, we will probably end up adding a quirk for the Dell XPS 13 9310 to disable interrupts automatically there. This assumes that the upstream devs agree with me that that is the best way forward.
*** Bug 1972044 has been marked as a duplicate of this bug. ***
Created attachment 1791497 [details] dmesg --level=warn on 5.12.9 (F33) without tpm_tis.interrupts=0 Dell XPS 9310 - "dmesg --level=warn" on 5.12.9 (F33) with tpm_tis.interrupts=0
Just booted 5.12.9 (F33) with the tpm_tis.interrupts=0 and the original warning is not there. However, there's another one now. [ 3.355397] TPM returned invalid status [ 3.355412] WARNING: CPU: 5 PID: 243 at drivers/char/tpm/tpm_tis_core.c:205 tpm_tis_status+0x66/0x70 I attached a dmesg dump in attachment 1791497 [details] (see above)
(In reply to Steven Bakker from comment #31) > Just booted 5.12.9 (F33) with the tpm_tis.interrupts=0 and the original > warning is not there. However, there's another one now. > > [ 3.355397] TPM returned invalid status > [ 3.355412] WARNING: CPU: 5 PID: 243 at > drivers/char/tpm/tpm_tis_core.c:205 tpm_tis_status+0x66/0x70 > > I attached a dmesg dump in attachment 1791497 [details] (see above) Why do you describe this as "another one" ? This is the same backtrace as the original backtrace from comment 0. So it seems that adding tpm_tis.interrupts=0 unfortunately does not help.
Apologies, I noticed the the "WARNING" line was different than the subject on this ticket (tpm_tis_status), so I thought it was a different issue. Also, I made a mistake in the description of comment #31 - I meant to say I *removed* the "tpm_tis.interrupts=0" line from the kernel command line. Sorry, my brain is a bit fried. %-o So, when *removing* "tpm_tis.interrupts=0" from the kernel command line, the warning reappeared. Will boot with "tpm_tis.interrupts=0" again to confirm that this makes it disappear.
(In reply to Steven Bakker from comment #33) > Apologies, I noticed the the "WARNING" line was different than the subject > on this ticket (tpm_tis_status), so I thought it was a different issue. > > Also, I made a mistake in the description of comment #31 - I meant to say I > *removed* the "tpm_tis.interrupts=0" line from the kernel command line. > Sorry, my brain is a bit fried. %-o No problem, thank you for rectifying things and thank you for testing this.
The upstream kernel developers looking into this have asked for acpidump-s of the laptop models which are known to still have this issues with the latest kernels (Dell XPS 13 9310, Dell XPS 15 9500, Dell Precision 7750). If you have one of these models please run the following commands: sudo dnf install acpica-tools sudo acpidump -o acpidump.hex And then attach the generated acpidump.hex file here, together with a comment/description for which laptop model it is.
Created attachment 1796263 [details] acpidump output from a Dell XPS 13 9310 that no longer has a problem I have a Dell XPS 13 9310, and I am no longer seeing this issue with Kernel 5.12.12-300 on Fedora 34. However, in case it is useful to compare with a system that does still have the problem, I have attached my acpidump output. I do not have tpm_tis.interrupts=0 in the kernel command line.
Thank you for the acpidump.
Created attachment 1797044 [details] ACPI dump for a XPS 15 9500 not suffering from this problem System Information Manufacturer: Dell Inc. Product Name: XPS 15 9500 BIOS Information Vendor: Dell Inc. Version: 1.7.1 Release Date: 03/29/2021 ROM Size: 32 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.7
Created attachment 1797067 [details] acpidump for Dell XPS 9310 (with Qualcomm QCA6390) acpidump for Dell XPS 9310 (with Qualcomm QCA6390)
(In reply to Steven Bakker from comment #39) > Created attachment 1797067 [details] > acpidump for Dell XPS 9310 (with Qualcomm QCA6390) > > acpidump for Dell XPS 9310 (with Qualcomm QCA6390) Note that this is for a 9310 where the problem does still exist (without tpm_tis.interrupts=0 in the kernel cmdline). [ 3.486335] ------------[ cut here ]------------ [ 3.486338] TPM returned invalid status [ 3.486358] WARNING: CPU: 6 PID: 252 at drivers/char/tpm/tpm_tis_core.c:205 tpm_tis_status+0x66/0x70 Kernel 5.12.13-200.fc33.x86_64 (Yes, I am still on F33, because under F34 bluetooth doesn't work and S2 sleep is broken even more than under F33).
*** Bug 1979004 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.