On Sun, Jan 30, 2011 at 06:37, Michael Schmitz
<schmitzmic@xxxxxxxxxxxxxx> wrote:
I've seen a similar panic as the one you posted when I had quite a bit of
memory pressure due to ext2fsck running. Otherwise, the kernel built with my
old binutils boots fine and eventually crashes the emulator with:
terminate called after throwing an instance of 'm68k_exception'
after getting well into runlevel 2 and starting a few services.
Retesting your kernel - when I leave swap off I also get to runlevel 2, and
it starts to throw panic messages as soon as inetd is started.
I've tried a few leads related to network stuff, but in the end replacing
the Âoption CONFIG_SLUB=y by CONFIG_SLAB=y did fix it.
Whatever the reason - the SLUB allocator either is buggy outright for m68k,
or we run into memory pressure a lot sooner than other architectures and the
VM subsystem needs optimizing for SLUB.
I'd just replace the Debian default for the m68k kernels....
If switching from SLUB to SLAB fixes the problem, please enable
CONFIG_SLUB_DEBUG and bring it up on lkml/with the SLUB people.
Gr{oetje,eeting}s,
            Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
             Â Â -- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
