Re: Memory probing fails after 2.6.30 (bisected)

[Anders Eriksson]

bdonlan@xxxxxxxxx said:
> Looks like the boot succeeded, at least long enough to mount the root fs.
> Assuming you're not using bootsplash or something, you should have seen
> something. Are you sure this is the log from the failed boot? If it didn't
> make it to userspace, it won't leave anything in kern.log. 

Yes I am.

2.6.31 --> instant reboot. Not one line of printk on the screen.
35d5a9a61490bf39d2e48d7f499c8c801a39ebe9 and 'lower' --> Get a 16 16MB env 
which didn't boot.

I got clued up and booted with init=/bin/bash, so for the fingered commit 
(i.e. the one switching from all-happy e820 to bios-88), I managed to 
remount / rw and capture dmesg.

Not sure how that interacts with earlyprintk=vga though. Did I get everyting 
there is to get?

-A

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/