On 2/4/26 23:50, Tytus Rogalewski wrote:
> Just had another crash and it is still happening in 6.18.8 . Here is
> claude output this time as i am lazy :)

I'm lazy and ignore AI slop. :)

[...]

>
>    Feb 04 21:42:16 pve12 kernel: BUG: unable to handle page fault for
> address: ff164aee00000000
>    Feb 04 21:42:16 pve12 kernel: #PF: supervisor read access in kernel mode
>    Feb 04 21:42:16 pve12 kernel: #PF: error_code(0x0000) - not-present page
>    Feb 04 21:42:16 pve12 kernel: PGD 4602067 P4D 0
>    Feb 04 21:42:16 pve12 kernel: Oops: Oops: 0000 [#1] SMP NOPTI
>    Feb 04 21:42:16 pve12 kernel: CPU: 125 UID: 0 PID: 783442 Comm: qm
> Not tainted 6.18.8-pbk #1 PREEMPT(voluntary)
>    Feb 04 21:42:16 pve12 kernel: Hardware name:  TURIN2D24G-2L+/500W/
> TURIN2D24G-2L+/500W, BIOS 10.12 11/14/2024
>    Feb 04 21:42:16 pve12 kernel: RIP: 0010:walk_pgd_range+0x6ff/0xbb0
>    Feb 04 21:42:16 pve12 kernel: Code: 08 49 39 dd 0f 84 8c 01 00 00 49
> 89 de 49 8d 9e 00 00 20 00 48 8b 75 b8 48 81 e3 00 00 e0 ff 48 8d 43 ff
> 48 39 f0 49 0f 43 dd <49> f7 04 24 9f ff ff ff 0f 84 e2 fd ff ff 48 8b
> 45 c0 41 c7 47 20
>    Feb 04 21:42:16 pve12 kernel: RSP: 0018:ff643a4c403439a8 EFLAGS: 00010287
>    Feb 04 21:42:16 pve12 kernel: RAX: 000071afc01fffff RBX:
> 000071afc0200000 RCX: 0000000000000000
>    Feb 04 21:42:16 pve12 kernel: RDX: 0000000000000000 RSI:
> 000071afffffffff RDI: 80002fd0000002b7
>    Feb 04 21:42:16 pve12 kernel: RBP: ff643a4c40343a88 R08:
> 0000000000000080 R09: 0000000000000000
>    Feb 04 21:42:16 pve12 kernel: R10: ffffffffb84588c0 R11:
> 0000000000000000 R12: ff164aee00000000
>    Feb 04 21:42:16 pve12 kernel: R13: 000071b000000000 R14:
> 000071afc0000000 R15: ff643a4c40343b08
>    Feb 04 21:42:16 pve12 kernel: FS:  0000767454f93b80(0000)
> GS:ff161c21bdefe000(0000) knlGS:0000000000000000
>    Feb 04 21:42:16 pve12 kernel: CS:  0010 DS: 0000 ES: 0000 CR0:
> 0000000080050033
>    Feb 04 21:42:16 pve12 kernel: CR2: ff164aee00000000 CR3:
> 00000080dff18005 CR4: 0000000000f71ef0
>    Feb 04 21:42:16 pve12 kernel: PKRU: 55555554
>    Feb 04 21:42:16 pve12 kernel: Call Trace:
>    Feb 04 21:42:16 pve12 kernel:  <TASK>
>    Feb 04 21:42:16 pve12 kernel:  __walk_page_range+0x8e/0x220
>    Feb 04 21:42:16 pve12 kernel:  walk_page_vma+0x92/0xe0
>    Feb 04 21:42:16 pve12 kernel:  smap_gather_stats.part.0+0x8c/0xd0
>    Feb 04 21:42:16 pve12 kernel:  show_smaps_rollup+0x258/0x420
>    Feb 04 21:42:16 pve12 kernel:  seq_read_iter+0x137/0x4c0
>    Feb 04 21:42:16 pve12 kernel:  seq_read+0xf5/0x140
>    Feb 04 21:42:16 pve12 kernel:  vfs_read+0xbb/0x350
>    Feb 04 21:42:16 pve12 kernel:  ksys_read+0x69/0xf0
>    Feb 04 21:42:16 pve12 kernel:  __x64_sys_read+0x19/0x30
>    Feb 04 21:42:16 pve12 kernel:  x64_sys_call+0x2180/0x25a0
>    Feb 04 21:42:16 pve12 kernel:  do_syscall_64+0x80/0xce0
>    Feb 04 21:42:16 pve12 kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
>    Feb 04 21:42:16 pve12 kernel:  </TASK>
>    Feb 04 21:42:16 pve12 kernel: Modules linked in: sctp ip6_udp_tunnel


Yeah, same thing again.

Can you retry without vfio passthrough to see whether it's triggered by
that?

vfio recently gained support for installing huge mappings into user page
tables. I wonder whether it is related to that.

--
Cheers,

David