mvebu: Problem booting Armada XP with mainline U-Boot
Hi!
I'm currently testing Linux booting from mainline U-Boot (full version with DDR training integrated as SPL - no bin_hdr) on the Marvell Armada XP Development Board DB-MV784MP-GP. And this results in (at least) those 2 problems:
a) Secondary CPU(s) fail to come online:
...
[ 0.130692] CPU: Testing write buffer coherency: ok [ 0.135785] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.141892] Setting up static identity map for 0x82c0 - 0x8318 [ 0.148013] mvebu-soc-id: MVEBU SoC ID=0x7846, Rev=0x2 [ 0.153357] mvebu-pmsu: Initializing Power Management Service Unit [ 0.160323] Booting CPU 1 [ 1.158867] CPU1: failed to come online [ 1.162960] Booting CPU 2 [ 2.158866] CPU2: failed to come online [ 2.162954] Booting CPU 3 [ 3.158865] CPU3: failed to come online [ 3.162810] Brought up 1 CPUs [ 3.165870] SMP: Total of 1 processors activated (1594.16 BogoMIPS). [ 3.172329] CPU: All CPU(s) started in SVC mode.
...
b) Booting hangs completely while/after loading some device drivers:
...
[ 4.031651] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 4.038209] ehci-pci: EHCI PCI platform driver [ 4.042694] ehci-orion: EHCI orion driver [ 4.046784] orion-ehci f1050000.usb: EHCI Host Controller [ 4.052207] orion-ehci f1050000.usb: new USB bus registered, assigned bus number 1 [ 4.059851] orion-ehci f1050000.usb: irq 27, io mem 0xf1050000
Disabling USB results in this hangup :
...
[ 4.076795] Registering SWP/SWPB emulation handler [ 4.082575] rtc-mv f1010300.rtc: setting system clock to 2013-01-01 13:27:46 UTC (1357046866)
etc...
This happens with v4.1 and v4.0.5. Please find the complete boot log attached.
Any ideas why those problems might occur with mainline U-Boot? Most likely some register setup is missing that is usually done in bin_hdr. Where could I check / test for this CPU online problem?
Thanks,
Stefan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: linux-boot.log
Type: text/x-log
Size: 12484 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150624/0c5e7993/attachment.bin>
Dear Stefan Roese,
Quoted 17 lines · Stefan Roese
a) Secondary CPU(s) fail to come online:
...
[ 0.130692] CPU: Testing write buffer coherency: ok [ 0.135785] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.141892] Setting up static identity map for 0x82c0 - 0x8318 [ 0.148013] mvebu-soc-id: MVEBU SoC ID=0x7846, Rev=0x2 [ 0.153357] mvebu-pmsu: Initializing Power Management Service Unit [ 0.160323] Booting CPU 1 [ 1.158867] CPU1: failed to come online [ 1.162960] Booting CPU 2 [ 2.158866] CPU2: failed to come online [ 2.162954] Booting CPU 3 [ 3.158865] CPU3: failed to come online [ 3.162810] Brought up 1 CPUs [ 3.165870] SMP: Total of 1 processors activated (1594.16 BogoMIPS). [ 3.172329] CPU: All CPU(s) started in SVC mode.
Quoted 1 line
...
This one I don't really have an idea, it needs some investigation.
Quoted 9 lines
b) Booting hangs completely while/after loading some device drivers:
...
[ 4.031651] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 4.038209] ehci-pci: EHCI PCI platform driver [ 4.042694] ehci-orion: EHCI orion driver [ 4.046784] orion-ehci f1050000.usb: EHCI Host Controller [ 4.052207] orion-ehci f1050000.usb: new USB bus registered, assigned bus number 1 [ 4.059851] orion-ehci f1050000.usb: irq 27, io mem 0xf1050000
Maybe missing USB PHY initialization or SERDES lanes initialization. These are done by the binary header, so I guess they are missing in the mainline U-Boot. We are hoping to work on such topics in the kernel in the near future, though, so that the kernel is taking of PHY and SERDES lanes initialization, and can also power them up/down for power management needs.
Quoted 4 lines
Any ideas why those problems might occur with mainline U-Boot? Most likely some register setup is missing that is usually done in
bin_hdr. Where could I check / test for this CPU online problem?
Hard to say, probably the easiest is to read the binary header code to see what they are doing.
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
Hi Thomas,
On 24.06.2015 19:24, Thomas Petazzoni wrote:
<snip>
Quoted 10 lines
Quoted 9 lines
b) Booting hangs completely while/after loading some device drivers:
...
[ 4.031651] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 4.038209] ehci-pci: EHCI PCI platform driver [ 4.042694] ehci-orion: EHCI orion driver [ 4.046784] orion-ehci f1050000.usb: EHCI Host Controller [ 4.052207] orion-ehci f1050000.usb: new USB bus registered, assigned bus number 1 [ 4.059851] orion-ehci f1050000.usb: irq 27, io mem 0xf1050000
Quoted 3 lines
Maybe missing USB PHY initialization or SERDES lanes initialization. These are done by the binary header, so I guess they are missing in the mainline U-Boot.
This SERDES / PHY initialization code from the Marvell bin_hdr is already integrated in mainline U-Boot SPL. So this is most likely not the root cause for this hangup.
Quoted 4 lines
We are hoping to work on such topics in the kernel in
the near future, though, so that the kernel is taking of PHY and SERDES lanes initialization, and can also power them up/down for power management needs.
Good to know. Thanks.
Quoted 7 lines
Quoted 4 lines
Any ideas why those problems might occur with mainline U-Boot? Most likely some register setup is missing that is usually done in
bin_hdr. Where could I check / test for this CPU online problem?Hard to say, probably the easiest is to read the binary header code to see what they are doing.
I thought that somebody might have a quick idea about something obvious going wrong here. If this is not the case, then I'll dig into the bin_hdr code again...
Thanks,
Stefan