Hello, I updated Debian to the testing version on the host system, I got the same error, but after deleting the lines, I get the following on startup:
[ 1.349298] general protection fault: 0000 [#1] SMP PTI
[ 1.349749] CPU: 0 PID: 10 Comm: rcu_sched Not tainted 4.19.0-10-amd64 #1 Debian 4.19.132-1
[ 1.350404] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-1 04/01/2014
[ 1.351074] RIP: 0010:switch_mm_irqs_off+0x2a5/0x4f0
[ 1.351512] Code: 41 5c 41 5d 41 5e 41 5f c3 65 48 8b 05 9c 42 9b 77 48 3b 87 18 04 00 00 0f 84 ed fd ff ff b9 49 00 00 00 b8 01 00 00 00 31 d2 <0f> 30 48 8b 87 18 04 00 00 65 48 89 05 72 42 9b 77 e9 cb fd ff ff
[ 1.353169] RSP: 0000:ffffb34b0011bd88 EFLAGS: 00010046
[ 1.353173] RAX: 0000000000000001 RBX: ffff9c7896381340 RCX: 0000000000000049
[ 1.353173] RDX: 0000000000000000 RSI: ffff9c7896381340 RDI: ffff9c78962b4a00
[ 1.353173] RBP: ffffffff8967ccc0 R08: ffff9c789fa22ae0 R09: 0000000000000000
[ 1.353173] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ 1.353173] R13: ffff9c78962b4a00 R14: ffff9c7896381340 R15: ffff9c7896381340
[ 1.353173] FS: 0000000000000000(0000) GS:ffff9c789fa00000(0000) knlGS:0000000000000000
[ 1.353173] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1.353173] CR2: 00007f5057e24486 CR3: 000000000760a001 CR4: 0000000000360ef0
[ 1.353173] Call Trace:
[ 1.353173] __schedule+0x263/0x870
[ 1.353173] schedule+0x28/0x80
[ 1.353173] schedule_timeout+0x16b/0x390
[ 1.353173] ? __next_timer_interrupt+0xc0/0xc0
[ 1.353173] rcu_gp_kthread+0x40d/0x850
[ 1.353173] ? call_rcu_sched+0x20/0x20
[ 1.353173] kthread+0x112/0x130
[ 1.353173] ? kthread_bind+0x30/0x30
[ 1.353173] ret_from_fork+0x35/0x40
[ 1.353173] Modules linked in:
[ 1.353173] —[ end trace 7e86a46bf8972822 ]—
[ 1.353173] RIP: 0010:switch_mm_irqs_off+0x2a5/0x4f0
[ 1.353173] Code: 41 5c 41 5d 41 5e 41 5f c3 65 48 8b 05 9c 42 9b 77 48 3b 87 18 04 00 00 0f 84 ed fd ff ff b9 49 00 00 00 b8 01 00 00 00 31 d2 <0f> 30 48 8b 87 18 04 00 00 65 48 89 05 72 42 9b 77 e9 cb fd ff ff
[ 1.353173] RSP: 0000:ffffb34b0011bd88 EFLAGS: 00010046
[ 1.353173] RAX: 0000000000000001 RBX: ffff9c7896381340 RCX: 0000000000000049
[ 1.353173] RDX: 0000000000000000 RSI: ffff9c7896381340 RDI: ffff9c78962b4a00
[ 1.353173] RBP: ffffffff8967ccc0 R08: ffff9c789fa22ae0 R09: 0000000000000000
[ 1.353173] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ 1.353173] R13: ffff9c78962b4a00 R14: ffff9c7896381340 R15: ffff9c7896381340
[ 1.353173] FS: 0000000000000000(0000) GS:ffff9c789fa00000(0000) knlGS:0000000000000000
[ 1.353173] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1.353173] CR2: 00007f5057e24486 CR3: 000000000760a001 CR4: 0000000000360ef0
I tried searching for your error but I can’t find anything helpful. Try sticking with stable on the host for a better experience. Some years back I was running testing because it had newer packages and had some close calls for reinstalling my system because an update fucked something up like crippling DE startup. I saw some random bugs show up then go away on their own during the release cycle and so went with stable for a more predictable workflow.
randomwhonixuser via Whonix Forum:
[ 1.351074] RIP: 0010:switch_mm_irqs_off+0x2a5/0x4f0
Looks like a kernel panic. Search the web for “kernel rip”. Issue not
caused by Whonix and should be resolved as per