Re: v3.19-rc1 regression(?) on N900
From: Pali RohÃr
Date: Thu Dec 25 2014 - 03:32:50 EST
On Wednesday 24 December 2014 23:57:38 Nishanth Menon wrote:
> based on automated testing with u-boot as a chained
> v3.18: boots fine:
> v3.19-rc1: hung
> in the interim, my farm had a bit of breakdown around the time
> of n900 breakdown..
> as per my last functional linux-next logs:
> omap2plus_defconfig/n900.txt -> hung.
> omap2plus_defconfig/n900.txt -> working.
> DEBUG_LL, CONFIG_DEBUG_OMAP3UART3=y and early_printk did not
> yield information either
> Note: I am using the combined uImage+dtb image.
> I think this might just be my setup..(i use chained loader ->
> NOLO->u-boot->serial download->kernel) but anyways.. Since
> Pali thought others might be interested in sharing
>  http://slexy.org/raw/s2osxhhwbR
CCing other people.
I see same problem in qemu with 3.19-rc1 kernel when doing DT
boot. In qemu I'm using direct booting from OneNAND (X-Loader -->
NOLO --> kernel) without U-Boot. After NOLO load & boot kernel I
do not see any other output from serial console. Also on qemu
screen there is no new output (just NOKIA logo from bootloader).
I do not have this problem when doing legacy/board code boot with
3.19-rc1 kernel, so this problem is related to DT.
Kernel 3.18-rc1 worked fine for both DT and legacy boot.
Can somebody look what broke DT booting?
Description: This is a digitally signed message part.