Panda Boot hang w/ linaro 2.6.39 kernel
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro Android |
Fix Released
|
Undecided
|
Unassigned | ||
Linaro Linux |
Fix Released
|
High
|
Avik Sil |
Bug Description
As reported on linaro-kernel:
Trying to boot pandaboard w/ linaro-2.6.39 kernel hangs in early boot.
Enabling EARLY_PRINTK showed the hang happening after:
[ 0.420776] print_constraints: dummy:
[ 0.425170] NET: Registered protocol family 16
[ 0.430206] GPMC revision 6.0
[ 0.437591] OMAP GPIO hardware version 0.1
[ 0.442474] OMAP GPIO hardware version 0.1
[ 0.446807] omap_device: omap_gpio.2: new worst case activate latency 0: 3057
[ 0.454833] OMAP GPIO hardware version 0.1
[ 0.459686] OMAP GPIO hardware version 0.1
[ 0.464569] OMAP GPIO hardware version 0.1
[ 0.469390] OMAP GPIO hardware version 0.1
[ 0.476440] omap_mux_init: Add partition: #1: core, flags: 2
[ 0.483764] omap_mux_init: Add partition: #2: wkup, flags: 2
[ 0.489807] error setting wl12xx data
[ 0.496032] omap_device: omap_uart.0: new worst case deactivate latency 0: 37
[ 0.504150] omap_device: omap_uart.1: new worst case activate latency 0: 3057
[ 0.517211] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
[ 0.524322] hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-st.
[ 0.531951] hw-breakpoint: maximum watchpoint size is 4 bytes.
I bisected the issue down to:
arm: omap4: support pmu - 4fefbe94a77c3d3
However, after reverting that patch against linaro-2.6.39, it then hangs
a bit later after:
[ 2.630554] omapdss HDMI: cannot lock PLL
[ 2.630554] omapdss HDMI: CFG1 0xc00
[ 2.630554] omapdss HDMI: CFG2 0x2004
[ 2.630584] omapdss HDMI: CFG4 0x23955
[ 2.630584] omapdss HDMI error: failed to power on device
[ 2.630645] omapdss error: failed to power on
[ 2.630645] omapfb omapfb: Failed to enable display 'hdmi'
[ 2.630645] omapfb omapfb: failed to initialize default display
[ 2.632202] omapfb omapfb: failed to setup omapfb
[ 2.632232] omapfb: probe of omapfb failed with error -5
[ 2.632720] regulator_
[ 2.632873] regulator_
[ 2.633056] regulator_
[ 2.633209] regulator_
[ 2.633392] regulator_
[ 2.633544] regulator_
[ 2.633697] regulator_
[ 2.633880] regulator_
This second hang however seems to be config related (likely something changed through the bisection), as it disappeared after I went back to my original config.
Changed in linux-linaro: | |
importance: | Undecided → High |
Changed in linaro-android: | |
status: | New → Fix Committed |
Changed in linux-linaro: | |
status: | Fix Committed → Fix Released |
Changed in linaro-android: | |
status: | Fix Committed → Fix Released |
Config for sha 54dab05c329c5fb 6121d89fddf9b82 e0fed35efb from linaro-2.6.39 tree that can be used to reproduce the hang.