* Armada XP doesn't boot in v3.12-rc3 @ 2013-10-02 10:39 Matthew Minter 2013-10-02 12:43 ` Jason Cooper 0 siblings, 1 reply; 10+ messages in thread From: Matthew Minter @ 2013-10-02 10:39 UTC (permalink / raw) To: linux-arm-kernel Hi, I am having the same issue as "Re: mvebu: Armada XP doesn't boot in v3.12-rc1". except that I am running rc3. I am wondering if the mentioned patch was ever released as I currently have an un-bootable board. Best regards, Matthew -- ------------------------------ For additional information including the registered office and the treatment of Xyratex confidential information please visit www.xyratex.com ------------------------------ ^ permalink raw reply [flat|nested] 10+ messages in thread
* Armada XP doesn't boot in v3.12-rc3 2013-10-02 10:39 Armada XP doesn't boot in v3.12-rc3 Matthew Minter @ 2013-10-02 12:43 ` Jason Cooper 2013-10-02 13:51 ` Ezequiel Garcia 2013-10-02 15:55 ` Matthew Minter 0 siblings, 2 replies; 10+ messages in thread From: Jason Cooper @ 2013-10-02 12:43 UTC (permalink / raw) To: linux-arm-kernel On Wed, Oct 02, 2013 at 11:39:53AM +0100, Matthew Minter wrote: > Hi, > > I am having the same issue as > "Re: mvebu: Armada XP doesn't boot in v3.12-rc1". > except that I am running rc3. > > I am wondering if the mentioned patch was ever released as I currently > have an un-bootable board. Yes, it's: 7b0dd72 arm: clocksource: mvebu: Use the main timer as clock source from DT which made it into v3.12-rc3. We'll need more information in order to diagnose your problem. You've either stumbled across a different problem, or need to try a clean build. But I'm just guessing since I'm not in front of your box ;-) hth, Jason. ^ permalink raw reply [flat|nested] 10+ messages in thread
* Armada XP doesn't boot in v3.12-rc3 2013-10-02 12:43 ` Jason Cooper @ 2013-10-02 13:51 ` Ezequiel Garcia 2013-10-02 15:55 ` Matthew Minter 1 sibling, 0 replies; 10+ messages in thread From: Ezequiel Garcia @ 2013-10-02 13:51 UTC (permalink / raw) To: linux-arm-kernel On Wed, Oct 02, 2013 at 08:43:20AM -0400, Jason Cooper wrote: > On Wed, Oct 02, 2013 at 11:39:53AM +0100, Matthew Minter wrote: > > Hi, > > > > I am having the same issue as > > "Re: mvebu: Armada XP doesn't boot in v3.12-rc1". > > except that I am running rc3. > > > > I am wondering if the mentioned patch was ever released as I currently > > have an un-bootable board. > > Yes, it's: > > 7b0dd72 arm: clocksource: mvebu: Use the main timer as clock source from DT > > which made it into v3.12-rc3. > > We'll need more information in order to diagnose your problem. You've > either stumbled across a different problem, or need to try a clean > build. But I'm just guessing since I'm not in front of your box ;-) > The latest DT timer fixes you pushed to arm-soc, doesn't appear to be in v3.12-rc3. I'll fetch the mail and ping Olof. Matthew, in case you need the commits: commit c1bbd430d617faa2bc610c5404486b01d72c34bc Author: Ezequiel Garcia <ezequiel.garcia@free-electrons.com> Date: Tue Aug 20 12:45:50 2013 -0300 ARM: mvebu: Add the reference 25 MHz fixed-clock to Armada XP commit 3a3c07001b0d4a5eec83bb87284048cd75b81510 Author: Ezequiel Garcia <ezequiel.garcia@free-electrons.com> Date: Tue Aug 20 12:45:51 2013 -0300 ARM: mvebu: Add clock properties to Armada XP timer node Which you can pick from git://git.infradead.org/linux-mvebu.git fixes. -- Ezequiel Garc?a, Free Electrons Embedded Linux, Kernel and Android Engineering http://free-electrons.com ^ permalink raw reply [flat|nested] 10+ messages in thread
* Armada XP doesn't boot in v3.12-rc3 2013-10-02 12:43 ` Jason Cooper 2013-10-02 13:51 ` Ezequiel Garcia @ 2013-10-02 15:55 ` Matthew Minter 2013-10-02 16:07 ` Thomas Petazzoni 2013-10-02 20:25 ` Ezequiel Garcia 1 sibling, 2 replies; 10+ messages in thread From: Matthew Minter @ 2013-10-02 15:55 UTC (permalink / raw) To: linux-arm-kernel Hi, Thanks for the reply. To give a little background the box is a Marvell DB-MV784MP-GP. It also appears that it is a revision B0 which various materials seem to imply matters but I am not sure of the significance. I have tried a number of configurations including the defaults for the mach and various settings including turning CONFIG_HAVE_ARM_ARCH_TIMER on and off. Some configurations result in no output after uBoot's booting kernel line, but some reach theline "calibrating timer loop" then hang indefinitely. I am now trying the fixes branch at git://git.infradead.org/linux-mvebu.git (thanks Ezequiel) to see if that contains a solution. Once I have tried that I shall see what changes it made and mail back any results. (I am talking to the board down a serial over USB connection so can get a fair amount of diagnostics from the early printk system). Best regards, Matthew On 2 October 2013 13:43, Jason Cooper <jason@lakedaemon.net> wrote: > On Wed, Oct 02, 2013 at 11:39:53AM +0100, Matthew Minter wrote: >> Hi, >> >> I am having the same issue as >> "Re: mvebu: Armada XP doesn't boot in v3.12-rc1". >> except that I am running rc3. >> >> I am wondering if the mentioned patch was ever released as I currently >> have an un-bootable board. > > Yes, it's: > > 7b0dd72 arm: clocksource: mvebu: Use the main timer as clock source from DT > > which made it into v3.12-rc3. > > We'll need more information in order to diagnose your problem. You've > either stumbled across a different problem, or need to try a clean > build. But I'm just guessing since I'm not in front of your box ;-) > > hth, > > Jason. -- ------------------------------ For additional information including the registered office and the treatment of Xyratex confidential information please visit www.xyratex.com ------------------------------ ^ permalink raw reply [flat|nested] 10+ messages in thread
* Armada XP doesn't boot in v3.12-rc3 2013-10-02 15:55 ` Matthew Minter @ 2013-10-02 16:07 ` Thomas Petazzoni 2013-10-02 16:42 ` Ezequiel Garcia 2013-10-02 20:25 ` Ezequiel Garcia 1 sibling, 1 reply; 10+ messages in thread From: Thomas Petazzoni @ 2013-10-02 16:07 UTC (permalink / raw) To: linux-arm-kernel Dear Matthew Minter, On Wed, 2 Oct 2013 16:55:25 +0100, Matthew Minter wrote: > To give a little background the box is a Marvell DB-MV784MP-GP. > It also appears that it is a revision B0 which various materials seem > to imply matters but I am not sure of the significance. I don't remember which version of the SoC we have here, but I can check this tomorrow. Also, which U-Boot version do you have on this machine? > I have tried a number of configurations including the defaults for the > mach and various settings including turning CONFIG_HAVE_ARM_ARCH_TIMER > on and off. > > Some configurations result in no output after uBoot's booting kernel > line, but some reach theline "calibrating timer loop" then hang > indefinitely. The first case means the kernel really doesn't boot. It can be due to an incorrect earlyprintk configuration, for example (but also other things). The second case is due to the timer being broken, which normally the patches pointed by Ezequiel should be fixing. > I am now trying the fixes branch at > git://git.infradead.org/linux-mvebu.git (thanks Ezequiel) to see if > that contains a solution. Once I have tried that I shall see what > changes it made and mail back any results. (I am talking to the board > down a serial over USB connection so can get a fair amount of > diagnostics from the early printk system). It's a shame that 3.12-rc still isn't fixed, and that 3.12-rc1 was broken in the first place :/ We used to be quite good at having at least bootable quality even at -rc1 stage, and many people and reporting problems now that 3.12-rc1 doesn't even boot on Armada 370/XP. Ezequiel, Jason, can you ping the relevant maintainers to make sure the relevant patches are merged quickly and land in the next -rc? Thanks a lot! Thomas -- Thomas Petazzoni, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com ^ permalink raw reply [flat|nested] 10+ messages in thread
* Armada XP doesn't boot in v3.12-rc3 2013-10-02 16:07 ` Thomas Petazzoni @ 2013-10-02 16:42 ` Ezequiel Garcia 0 siblings, 0 replies; 10+ messages in thread From: Ezequiel Garcia @ 2013-10-02 16:42 UTC (permalink / raw) To: linux-arm-kernel On Wed, Oct 02, 2013 at 06:07:02PM +0200, Thomas Petazzoni wrote: > > It's a shame that 3.12-rc still isn't fixed, and that 3.12-rc1 was > broken in the first place :/ Yeah, it's a damn shame. FWIW, I certainly learned a lesson from this and will be much careful in the future. > > Ezequiel, Jason, can you ping the relevant maintainers to make sure the > relevant patches are merged quickly and land in the next -rc? > I already did earlier this morning. Jason sent the PR on September 19th so it was more or less in time for -rc2, I'm a bit puzzled about why it's not in Linus' yet. -- Ezequiel Garc?a, Free Electrons Embedded Linux, Kernel and Android Engineering http://free-electrons.com ^ permalink raw reply [flat|nested] 10+ messages in thread
* Armada XP doesn't boot in v3.12-rc3 2013-10-02 15:55 ` Matthew Minter 2013-10-02 16:07 ` Thomas Petazzoni @ 2013-10-02 20:25 ` Ezequiel Garcia 2013-10-03 9:41 ` Matthew Minter 1 sibling, 1 reply; 10+ messages in thread From: Ezequiel Garcia @ 2013-10-02 20:25 UTC (permalink / raw) To: linux-arm-kernel Hi Matthew: On Wed, Oct 02, 2013 at 04:55:25PM +0100, Matthew Minter wrote: [...] > > I have tried a number of configurations including the defaults for the > mach and various settings including turning CONFIG_HAVE_ARM_ARCH_TIMER > on and off. > > Some configurations result in no output after uBoot's booting kernel > line, but some reach theline "calibrating timer loop" then hang > indefinitely. > Yup, that's the two different bugs the patches should fix. > I am now trying the fixes branch at > git://git.infradead.org/linux-mvebu.git (thanks Ezequiel) to see if > that contains a solution. Once I have tried that I shall see what > changes it made and mail back any results. (I am talking to the board > down a serial over USB connection so can get a fair amount of > diagnostics from the early printk system). > Please test git://git.infradead.org/linux-mvebu.git or some recent linux-next. You should be able to boot with/without CONFIG_HAVE_ARM_ARCH_TIMER. I expect all the fixes land in -rc4, which means mainline should be fixed by next week. Let me know any problems! Thanks a lot for reporting! -- Ezequiel Garc?a, Free Electrons Embedded Linux, Kernel and Android Engineering http://free-electrons.com ^ permalink raw reply [flat|nested] 10+ messages in thread
* Armada XP doesn't boot in v3.12-rc3 2013-10-02 20:25 ` Ezequiel Garcia @ 2013-10-03 9:41 ` Matthew Minter 2013-10-03 10:28 ` Thomas Petazzoni 0 siblings, 1 reply; 10+ messages in thread From: Matthew Minter @ 2013-10-03 9:41 UTC (permalink / raw) To: linux-arm-kernel Hi, It seems the latest build of "for-next" from git://git.infradead.org/linux-mvebu.git works the charm. For reference I have a version of uBoot that came with the board, I am reluctant to reflash it as I would then have no way of recovering and it has not seemed to cause any issues anyway. (the only drawback is that it seems to prefer to appended dtb image and not explicit passing). The version is as follows but is likely not useful as it seems to be a build customised for the hardware, it does support uImages and the new format however: U-Boot 2011.12-00036-g664db9a-dirty (Oct 16 2012 - 14:12:23) Marvell version: 2012_Q4.1 I am still working through some small driver issues (trying to mount various SSDs) but the early boot failure is resolved with those patches and the default configuration (plus early printk). Thank you all so much for the help, I think this board is now working fine but will report any other issues I come across later. Best regards, Matthew On 2 October 2013 21:25, Ezequiel Garcia <ezequiel.garcia@free-electrons.com> wrote: > Hi Matthew: > > On Wed, Oct 02, 2013 at 04:55:25PM +0100, Matthew Minter wrote: > [...] >> >> I have tried a number of configurations including the defaults for the >> mach and various settings including turning CONFIG_HAVE_ARM_ARCH_TIMER >> on and off. >> >> Some configurations result in no output after uBoot's booting kernel >> line, but some reach theline "calibrating timer loop" then hang >> indefinitely. >> > > Yup, that's the two different bugs the patches should fix. > >> I am now trying the fixes branch at >> git://git.infradead.org/linux-mvebu.git (thanks Ezequiel) to see if >> that contains a solution. Once I have tried that I shall see what >> changes it made and mail back any results. (I am talking to the board >> down a serial over USB connection so can get a fair amount of >> diagnostics from the early printk system). >> > > Please test git://git.infradead.org/linux-mvebu.git or some recent > linux-next. You should be able to boot with/without CONFIG_HAVE_ARM_ARCH_TIMER. > > I expect all the fixes land in -rc4, which means mainline should be > fixed by next week. > > Let me know any problems! > > Thanks a lot for reporting! > > -- > Ezequiel Garc?a, Free Electrons > Embedded Linux, Kernel and Android Engineering > http://free-electrons.com -- ------------------------------ For additional information including the registered office and the treatment of Xyratex confidential information please visit www.xyratex.com ------------------------------ ^ permalink raw reply [flat|nested] 10+ messages in thread
* Armada XP doesn't boot in v3.12-rc3 2013-10-03 9:41 ` Matthew Minter @ 2013-10-03 10:28 ` Thomas Petazzoni 2013-10-03 11:45 ` Jason Cooper 0 siblings, 1 reply; 10+ messages in thread From: Thomas Petazzoni @ 2013-10-03 10:28 UTC (permalink / raw) To: linux-arm-kernel Dear Matthew Minter, On Thu, 3 Oct 2013 10:41:07 +0100, Matthew Minter wrote: > It seems the latest build of "for-next" from > git://git.infradead.org/linux-mvebu.git works the charm. > For reference I have a version of uBoot that came with the board, I am > reluctant to reflash it as I would then have no way of recovering and > it has not seemed to cause any issues anyway. (the only drawback is > that it seems to prefer to appended dtb image and not explicit > passing). Don't worry: there is a way of recovering, through the UART, using the kwboot tool that Sebastian and I have added to the Barebox sources. Sebastian and I have already been able to run Barebox (a different bootloader) on Armada 370 and Armada XP platforms, though the support is limited to the serial port for the moment, so it's quite useless for any practical usage. As of today, there is no Armada 370/XP support in the mainline U-Boot, and Marvell has not yet released an U-Boot version that has Device Tree support, so we're stuck with appended DTB for now. However, Marvell is working on a DT-capable version of their U-Boot, which should arrive at some point in the future. > The version is as follows but is likely not useful as it seems to be a > build customised for the hardware, it does support uImages and the new > format however: > > U-Boot 2011.12-00036-g664db9a-dirty (Oct 16 2012 - 14:12:23) Marvell > version: 2012_Q4.1 It is useful for us, as we can compare it to the U-Boot version we're using, and we also have the possibility of upgrading our U-Boot to a different version if needed. > I am still working through some small driver issues (trying to mount > various SSDs) but the early boot failure is resolved with those > patches and the default configuration (plus early printk). Great. Regarding SSDs, we successfully tested the SATA support on Armada XP GP with hard drives, and the SATA support was also successfully tested on OpenBlocks AX3-4 (which has an Armada XP) using a SSD. > Thank you all so much for the help, I think this board is now working > fine but will report any other issues I come across later. Sure! As soon as the relevant fixes of mvebu/for-next hit mainline, you'll be able to switch back to using the mainline kernel. Note that you can also use 3.11 for the moment, which should also work on this platform. Thanks! Thomas -- Thomas Petazzoni, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com ^ permalink raw reply [flat|nested] 10+ messages in thread
* Armada XP doesn't boot in v3.12-rc3 2013-10-03 10:28 ` Thomas Petazzoni @ 2013-10-03 11:45 ` Jason Cooper 0 siblings, 0 replies; 10+ messages in thread From: Jason Cooper @ 2013-10-03 11:45 UTC (permalink / raw) To: linux-arm-kernel On Thu, Oct 03, 2013 at 12:28:01PM +0200, Thomas Petazzoni wrote: > Dear Matthew Minter, > > On Thu, 3 Oct 2013 10:41:07 +0100, Matthew Minter wrote: > > > It seems the latest build of "for-next" from > > git://git.infradead.org/linux-mvebu.git works the charm. Great! > As soon as the relevant fixes of mvebu/for-next hit mainline, you'll be > able to switch back to using the mainline kernel. Note that you can > also use 3.11 for the moment, which should also work on this platform. It looks like Linus pulled from arm-soc/fixes last night, so you may want to give mainline a try. I rebase mvebu/for-next frequently, so it's not stable. It's purpose is for quick verification as you did yesterday, not extended use. hth, Jason. ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2013-10-03 11:45 UTC | newest] Thread overview: 10+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2013-10-02 10:39 Armada XP doesn't boot in v3.12-rc3 Matthew Minter 2013-10-02 12:43 ` Jason Cooper 2013-10-02 13:51 ` Ezequiel Garcia 2013-10-02 15:55 ` Matthew Minter 2013-10-02 16:07 ` Thomas Petazzoni 2013-10-02 16:42 ` Ezequiel Garcia 2013-10-02 20:25 ` Ezequiel Garcia 2013-10-03 9:41 ` Matthew Minter 2013-10-03 10:28 ` Thomas Petazzoni 2013-10-03 11:45 ` Jason Cooper
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).