On 06/12/25(Sat) 21:41, Christoph Liebender wrote: > On 12/6/25 21:26, Theo de Raadt wrote: > > Christoph Liebender <[email protected]> wrote: > > > > > On 12/6/25 21:11, Theo de Raadt wrote: > > > > if I read this correctly, you got more information from ddb and > > > > then didn't share it with us. > > > > > > as I said: > > > > > > - unfortunately the email would get too big. Therefore, please see > > > them under: liebender dot dev slash pub. Thanks and sorry for the > > > inconvenience. > > > > > > anyway I attached the panic message. More details at the above link. > > > > You can type it out, or you can debug it yourself. > > Quoting https://www.openbsd.org/ddb.html > > ... but if you are on a VGA console you can scroll the console back and > take readable pictures with a phone or camera. > > Anyway:
Thanks Christoph. If you can reproduce the crash, please report the panic just like this one. It is not clear to me with a single report where the memory corruption might come from. > panic: pool_cache_item_magic_check: anonpl cpu free list modified: item addr > 0xfffffd80a6800e08+16 0x8d407afd95864b71!= > 0x7bba06ef6cf3f271 > Stopped at db_enter+0x14: popq %rbp > TID PID UID PRFLAGS PFLAGS CPU COMMAND > *377025 10609 1000 0x100000 0 2 sh > 57391 30284 1000 0x2 0 0 thunderbird > db_enter() at db_enter+0x14 > panic(ffffffff826533ff) at panic+0xd5 > pool_cache_get(ffffffff82bb7b80) at pool_cache_get+0x279 > pool_get(ffffffff82bb7b80,2) at pool_get+0x6d > uvm_analloc() at uvm_analloc+0x27 > uvmfault_promote(ffff800054d30a38,fffffd81022dd180,ffff800054d308c0,ffff800054d308c8) > at uvmfault_promote+0x91 > uvm_fault_upper(ffff800054d30a38,ffff800054d30a70,ffff800054d30930) at > uvm_fault_upper+0x41d > uvm_fault(fffffd80226502e8,eebff9af000,0,2) at uvm_fault+0xce > upageflttrap(ffff800054d30bb0,eebff9af508) at upageflttrap+0x6c > usertrap(ffff800054d30bb0) at usertrap+0x28b > recall_trap() at recall_trap+0x8 > end of kernel >
