as far as i can see you see a lockup under certain circumstances, right?
this debug option catches use-after-free and other types of invalid
memory accesses. When it catches a bug the kernel most likely crashes
and produces a backlog. Because you are in graphical mode that is not
visible.
This would possibly be debuggable if you set up netconsole logging to
another system on a local LAN - see
Documentation/networking/netconsole.txt.
Vegard - would it be possible to make DEBUG_PAGEALLOC faults single-shot
and non-fatal, just like kmemcheck does it? That way people would see a
nice kernel message instead of an immediate crash. That means we'd have
to find a reliable filter for DEBUG_PAGEALLOC-provoked pagefaults though
...
Ingo
--
