You are not logged in.

Pages: 1

#1 2018-02-15 17:41:06

clofresh
Member
Registered: 2015-05-23
Posts: 8

"general protection fault: 0000 [#1] PREEMPT SMP PTI" in thunderbolt

I'm getting errors in my logs when I close the lid of my dell xps 13 9350 laptop when it's plugged into my dell tb16 thunderbolt3 dock. I have a monitor and several usb devices plugged into the dock that normally work, but when I open the lid, only the monitor works, but not the usb devices. I tried 

sudo rmmod xhci_pci xhci_hcd  && sudo modprobe xhci_pci xhci_hcd

but they don't come back.

Feb 14 23:29:23 carlo-xps13-arch kernel: general protection fault: 0000 [#1] PREEMPT SMP PTI
Feb 14 23:29:23 carlo-xps13-arch kernel: Modules linked in: wacom hid_logitech_hidpp snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_seq_device hid_logitech_dj hid_generic cdc_ether usbnet r8152 mii thunderbolt xt_nat xt_tcpudp ve
Feb 14 23:29:23 carlo-xps13-arch kernel:  snd_soc_acpi fat kvm_intel wmi_bmof dell_wmi snd_soc_core dell_smbios_wmi iwlwifi intel_wmi_thunderbolt dell_wmi_descriptor snd_hda_codec_realtek snd_hda_codec_generic kvm snd_compress d
Feb 14 23:29:23 carlo-xps13-arch kernel:  vboxpci(O) vboxdrv(O) crypto_user ip_tables x_tables ext4 crc16 mbcache jbd2 fscrypto algif_skcipher af_alg hid_multitouch usbhid hid dm_crypt dm_mod crct10dif_pclmul crc32_pclmul crc32c
Feb 14 23:29:23 carlo-xps13-arch kernel: CPU: 3 PID: 5487 Comm: kworker/3:3 Tainted: G     U  W  O     4.15.2-2-ARCH #1
Feb 14 23:29:23 carlo-xps13-arch kernel: Hardware name: Dell Inc. XPS 13 9350/09JHRY, BIOS 1.4.13 12/28/2016
Feb 14 23:29:23 carlo-xps13-arch kernel: Workqueue: events tb_cfg_request_work [thunderbolt]
Feb 14 23:29:23 carlo-xps13-arch kernel: RIP: 0010:tb_cfg_request_dequeue+0x28/0x80 [thunderbolt]
Feb 14 23:29:23 carlo-xps13-arch kernel: RSP: 0018:ffff9fa2c63ffe78 EFLAGS: 00010246
Feb 14 23:29:23 carlo-xps13-arch kernel: RAX: dead000000000200 RBX: ffff9130348acf00 RCX: 0000000000000001
Feb 14 23:29:23 carlo-xps13-arch kernel: RDX: dead000000000100 RSI: ffff9fa2c218f7d8 RDI: ffff9130b8d0c970
Feb 14 23:29:23 carlo-xps13-arch kernel: RBP: ffff9130b8d0c970 R08: 00004b0977a63c00 R09: 0000000000000000
Feb 14 23:29:23 carlo-xps13-arch kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
Feb 14 23:29:23 carlo-xps13-arch kernel: R13: 0000000000000000 R14: ffff9130d065e0c0 R15: ffff9132beda1000
Feb 14 23:29:23 carlo-xps13-arch kernel: FS:  0000000000000000(0000) GS:ffff9132bed80000(0000) knlGS:0000000000000000
Feb 14 23:29:23 carlo-xps13-arch kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 14 23:29:23 carlo-xps13-arch kernel: CR2: 00007f20221604e0 CR3: 0000000391008004 CR4: 00000000003606e0
Feb 14 23:29:23 carlo-xps13-arch kernel: Call Trace:
Feb 14 23:29:23 carlo-xps13-arch kernel:  tb_cfg_request_work+0x2b/0x40 [thunderbolt]
Feb 14 23:29:23 carlo-xps13-arch kernel:  process_one_work+0x1df/0x420
Feb 14 23:29:23 carlo-xps13-arch kernel:  worker_thread+0x216/0x3d0
Feb 14 23:29:23 carlo-xps13-arch kernel:  ? process_one_work+0x420/0x420
Feb 14 23:29:23 carlo-xps13-arch kernel:  kthread+0x113/0x130
Feb 14 23:29:23 carlo-xps13-arch kernel:  ? kthread_create_on_node+0x70/0x70
Feb 14 23:29:23 carlo-xps13-arch kernel:  ? do_syscall_64+0x75/0x190
Feb 14 23:29:23 carlo-xps13-arch kernel:  ? SyS_exit_group+0x10/0x10
Feb 14 23:29:23 carlo-xps13-arch kernel:  ret_from_fork+0x35/0x40
Feb 14 23:29:23 carlo-xps13-arch kernel: Code: 00 00 00 0f 1f 44 00 00 55 53 48 89 fb 48 8b 47 08 48 8d 68 70 48 89 ef e8 56 e1 59 eb 48 8b 83 b0 00 00 00 48 8b 93 a8 00 00 00 <48> 89 42 08 48 89 10 48 b8 00 01 00 00 00 00 ad de
Feb 14 23:29:23 carlo-xps13-arch kernel: RIP: tb_cfg_request_dequeue+0x28/0x80 [thunderbolt] RSP: ffff9fa2c63ffe78
Feb 14 23:29:23 carlo-xps13-arch kernel: ---[ end trace b24d7eb012c7e056 ]---

Kernel is 

Linux carlo-xps13-arch 4.15.2-2-ARCH #1 SMP PREEMPT Thu Feb 8 18:54:52 UTC 2018 x86_64 GNU/Linux

Not sure if it's related, but while it was suspended, I kept getting this spammed in the logs over and over again:

Feb 14 23:31:00 carlo-xps13-arch systemd[1]: Starting Suspend...
Feb 14 23:31:00 carlo-xps13-arch systemd-sleep[10910]: Suspending system...
Feb 14 23:31:00 carlo-xps13-arch kernel: PM: suspend entry (deep)
Feb 14 23:31:00 carlo-xps13-arch kernel: PM: Syncing filesystems ... done.
Feb 14 23:31:20 carlo-xps13-arch kernel: Freezing user space processes ... 
Feb 14 23:31:20 carlo-xps13-arch kernel: Freezing of tasks failed after 20.005 seconds (1 tasks refusing to freeze, wq_busy=0):
Feb 14 23:31:20 carlo-xps13-arch kernel: tlp             D    0 10327  10302 0x00000104
Feb 14 23:31:20 carlo-xps13-arch kernel: Call Trace:
Feb 14 23:31:20 carlo-xps13-arch kernel:  ? __schedule+0x24b/0x8c0
Feb 14 23:31:20 carlo-xps13-arch kernel:  schedule+0x32/0x90
Feb 14 23:31:20 carlo-xps13-arch kernel:  schedule_preempt_disabled+0x14/0x20
Feb 14 23:31:20 carlo-xps13-arch kernel:  __mutex_lock.isra.0+0x274/0x520
Feb 14 23:31:20 carlo-xps13-arch kernel:  ? control_store+0x41/0xc0
Feb 14 23:31:20 carlo-xps13-arch kernel:  control_store+0x41/0xc0
Feb 14 23:31:20 carlo-xps13-arch kernel:  kernfs_fop_write+0x10b/0x190
Feb 14 23:31:20 carlo-xps13-arch kernel:  __vfs_write+0x36/0x180
Feb 14 23:31:20 carlo-xps13-arch kernel:  ? __fd_install+0x51/0xd0
Feb 14 23:31:20 carlo-xps13-arch kernel:  ? preempt_count_add+0x68/0xa0
Feb 14 23:31:20 carlo-xps13-arch kernel:  ? _raw_spin_lock+0x13/0x40
Feb 14 23:31:20 carlo-xps13-arch kernel:  ? set_close_on_exec+0x30/0x70
Feb 14 23:31:20 carlo-xps13-arch kernel:  vfs_write+0xb1/0x1a0
Feb 14 23:31:20 carlo-xps13-arch kernel:  SyS_write+0x52/0xc0
Feb 14 23:31:20 carlo-xps13-arch kernel:  do_syscall_64+0x75/0x190
Feb 14 23:31:20 carlo-xps13-arch kernel:  entry_SYSCALL_64_after_hwframe+0x21/0x86
Feb 14 23:31:20 carlo-xps13-arch kernel: RIP: 0033:0x7fe9c8ba2444
Feb 14 23:31:20 carlo-xps13-arch kernel: RSP: 002b:00007fff99c27288 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
Feb 14 23:31:20 carlo-xps13-arch kernel: RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fe9c8ba2444
Feb 14 23:31:20 carlo-xps13-arch kernel: RDX: 0000000000000003 RSI: 00005639a8423b20 RDI: 0000000000000001
Feb 14 23:31:20 carlo-xps13-arch kernel: RBP: 00005639a8423b20 R08: 000000000000000a R09: 0000000000000001
Feb 14 23:31:20 carlo-xps13-arch kernel: R10: 000000000000000a R11: 0000000000000246 R12: 0000000000000003
Feb 14 23:31:20 carlo-xps13-arch kernel: R13: 0000000000000001 R14: 00007fe9c8e6d5c0 R15: 0000000000000003
Feb 14 23:31:20 carlo-xps13-arch kernel: OOM killer enabled.
Feb 14 23:31:20 carlo-xps13-arch kernel: Restarting tasks ... done.
Feb 14 23:31:20 carlo-xps13-arch rtkit-daemon[13064]: The canary thread is apparently starving. Taking action.
Feb 14 23:31:20 carlo-xps13-arch rtkit-daemon[13064]: Demoting known real-time threads.
Feb 14 23:31:20 carlo-xps13-arch rtkit-daemon[13064]: Successfully demoted thread 13059 of process 13059 (/usr/bin/pulseaudio).
Feb 14 23:31:20 carlo-xps13-arch rtkit-daemon[13064]: Demoted 1 threads.
Feb 14 23:31:20 carlo-xps13-arch kernel: PM: suspend exit

I tried kill -9 on tlp but it still sticks around.

Offline

#2 2021-11-09 08:02:32

lkraav
Member
Registered: 2011-04-08
Posts: 37

Re: "general protection fault: 0000 [#1] PREEMPT SMP PTI" in thunderbolt

@clofresh did you ever figure this out?

I'm seeing a similar traceback with `tb_cfg_request_work`, and there are near-zero results on Google for this.

Offline

Pages: 1

Board footer

Powered by FluxBB