Walter Alejandro Iglesias <[email protected]> wrote: > On Sun, Feb 08, 2026 at 08:51:38AM -0800, Mike Larkin wrote: > > On Sun, Feb 08, 2026 at 11:18:26AM +0100, Walter Alejandro Iglesias wrote: > > > Hi Mike, > > > > > > Unfortunately, I'm still able to reproduce the panic. > > > > > > In case this is relevant. With #667 the panic followed by the debugger > > > interface message happened right after the image was uncompressed. With > > > current versions, I have to run startx to get a first single line > > > message panic, and then reboot again to get a second panic with the > > > debugger message. I can send you pictures if you want. > > > > > > > ok maybe... > > The first lines of the report of the panic seem to be the same. The > affected functions are pool_cache_get() pool_get(), m_clget(), etc. > > Some times I get just this single line message: > > pool_cache_item_magic_check: mcl2k cpu free list modified: item addr \ > 0xfffffd800bc00800+16 0x0!=0xced49a541a9360d4
It appears to always be memory corruption of something in currently allocated dma reachable memory. I think it would help to have a diff which prints the physical page where the corruption occurs, and see if that is repeatable.
