Comment 17 for bug 2026790

Revision history for this message
beadon (bryant-eadon) wrote :

This may be unrelated -- but I am also seeing "x86/split lock detection" errors. Is this just a red herring ? Only seeing these when using the VirtualBox to drive the GPU.

[Tue Jul 11 14:50:44 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000
[Tue Jul 11 14:50:44 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000
[Tue Jul 11 14:50:44 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000
[Tue Jul 11 14:50:45 2023] Bluetooth: RFCOMM TTY layer initialized
[Tue Jul 11 14:50:45 2023] Bluetooth: RFCOMM socket layer initialized
[Tue Jul 11 14:50:45 2023] Bluetooth: RFCOMM ver 1.11
[Tue Jul 11 14:50:47 2023] thunderbolt 1-1: new device found, vendor=0x127 device=0x2
[Tue Jul 11 14:50:47 2023] thunderbolt 1-1: Razer Core X Chroma
[Tue Jul 11 14:50:48 2023] rfkill: input handler disabled
[Tue Jul 11 14:50:53 2023] thunderbolt 1-101: new device found, vendor=0x127 device=0x3
[Tue Jul 11 14:50:53 2023] thunderbolt 1-101: Razer Core X Chroma
[Tue Jul 11 14:50:54 2023] rfkill: input handler enabled
[Tue Jul 11 14:50:54 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000
[Tue Jul 11 14:50:54 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000
[Tue Jul 11 14:50:54 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000
[Tue Jul 11 14:50:59 2023] rfkill: input handler disabled
[Tue Jul 11 14:56:33 2023] SUPR0GipMap: fGetGipCpu=0x1b
[Tue Jul 11 14:56:33 2023] vboxdrv: 0000000000000000 VMMR0.r0
[Tue Jul 11 14:56:33 2023] vboxdrv: 0000000000000000 VBoxDDR0.r0
[Tue Jul 11 14:56:41 2023] x86/split lock detection: #AC: EMT-1/4206 took a split_lock trap at address: 0x7f698f296453
[Tue Jul 11 14:57:03 2023] x86/split lock detection: #AC: EMT-2/4207 took a split_lock trap at address: 0x7f698f296453
[Tue Jul 11 14:57:03 2023] x86/split lock detection: #AC: EMT-0/4205 took a split_lock trap at address: 0x7f698f296453

Unsure why there is a magic address space number there: 0x7f698f296453