On Thu, Aug 25, 2011 at 4:09 PM, Luciano Coelho <coelho@xxxxxx> wrote: > Hi, > > There seems to be a problem with 3.1-rc3, which prevents it from booting > on my PandaBoard (ARM OMAP4). > > 3.1-rc2 works fine, so I have bisected the problem and it turns out to > be caused by this: > > commit f3637a5f2e2eb391ff5757bc83fb5de8f9726464 > Author: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx> > Date: Thu Jul 7 22:32:17 2011 +0200 > > irq: Always set IRQF_ONESHOT if no primary handler is specified > > After reverting this commit, -rc3 boots fine. I'm not sure where > exactly the problem is. Maybe it's something in the omap code which is > broken and this patch causes the bug to show up? > > What happens is that the booting process hangs after printing out this: > fyi, http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=69dd3d8e29e294caaf63eb5e8a72d250279f9e5f;hp=fcb8ce5cfe30ca9ca5c9a79cdfe26d1993e65e0c -- Thanks, Govindraj.R > [...] > [ 7.408477] EXT3-fs: barriers not enabled > [ 7.415008] kjournald starting. Commit interval 5 seconds > [ 7.446228] EXT3-fs (mmcblk0p5): using internal journal > [ 7.452087] EXT3-fs (mmcblk0p5): mounted filesystem with ordered data mode > [ 7.459625] VFS: Mounted root (ext3 filesystem) on device 179:5. > [ 7.466094] Freeing init memory: 312K > [ 7.471710] Failed to execute /init. Attempting defaults... > [ 10.254333] EXT3-fs (mmcblk0p5): using internal journal > > The full boot logs can be found here: > > http://pastebin.pandaboard.org/index.php/view/88995306 > > Any ideas what may be going wrong? > > -- > Cheers, > Luca. > > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
