On 10/25/17 11:55, blubee blubeeme wrote: > "os.lock_mtx" > Oct 25 17:52:58 blubee kernel: 1st os.lock_mtx _at_ nvidia_os.c:841 > Oct 25 17:52:58 blubee kernel: 2nd os.lock_mtx _at_ nvidia_os.c:841 > Oct 25 17:52:58 blubee kernel: stack backtrace: > Oct 25 17:52:58 blubee kernel: #0 0xffffffff80ab6f30 at > witness_debugger+0x70 > Oct 25 17:52:58 blubee kernel: #1 0xffffffff80ab6e23 at > witness_checkorder+0xe23 > Oct 25 17:52:58 blubee kernel: #2 0xffffffff80a35293 at > __mtx_lock_flags+0x93 > Oct 25 17:52:58 blubee kernel: #3 0xffffffff82f4097b at > os_acquire_spinlock+0x1b > Oct 25 17:52:58 blubee kernel: #4 0xffffffff82c45b15 at _nv012002rm+0x185 > Oct 25 17:52:58 blubee kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: > Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] > (20170531/nsarguments-205) > Oct 25 17:52:59 blubee kernel: nvidia-modeset: Allocated GPU:0 > (GPU-54a7b304-c99d-efee-0117-0ce119063cd6) _at_ PCI:0000:01:00.0 > > Hi, Try: CTRL+ALT+F1 Or SSH into this machine. Then do: procstat -ak It will reveal any hangs and deadlocks. Further I note you're using 12-current with the NVIDIA driver. That might not be a supported configuration :-( Especially nowadays some core kernel structures are changing, which means NVIDIA needs to recompile their binary blob aswell! --HPSReceived on Wed Oct 25 2017 - 08:00:54 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:13 UTC