Hi Thorsten,
I posted a link to the source package earlier. I cancelled the build
though due to this problem.
Right you are, I'll work from that one then.
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....
Cheers,
Michael
--
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
