On Thu, 21 Nov 2013, Michael Schmitz wrote:
> Serial or early fb console looks the only way to debug this.
It hangs at "K", which means that none of the messages that would normally
appear on the early console have appeared yet.
Based on the first screen shot posted by Patrick, the first couple of
lines to appear should have been,
[ 0.000000 ] Linux version 3.12...
[ 0.000000 ] m68k_parse_bootinfo...
[ 0.000000 ] bootconsole [early0] enabled
Problem is, I've no idea why none of this shows up. Is it because the hang
happened before the bootconsole was enabled? Maybe even before before the
first printk ("Linux version 3.12...")?
Is there a way to get console messages given that the bootconsole might
not be enabled yet? Otherwise, I still favour "git bisect".
Though I suppose we could go fishing based on the interrupt hypothesis,
and somehow inhibit the normal interrupt initialisation, so that the
bootconsole might start. Not sure where that leads though.
Finn
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive:
http://lists.debian.org/[email protected]
