On Tue, Apr 7, 2009 at 4:19 PM, Hugo Vincent <hugo.vincent@xxxxxxxxx> wrote: > On Tue, Apr 7, 2009 at 3:36 PM, David Brownell <david-b@xxxxxxxxxxx> wrote: >> On Monday 06 April 2009, Hugo Vincent wrote: >>> Here is a complete boot log + config: >>> http://hugovincent.com/files/lkml-20090407/boot2.log >> >> Erm, not very complete actually. Enable DEBUG_LL to see >> more early messages ... like the ones starting right >> after the kernel decompression messages. > > How's this? > http://hugovincent.com/files/lkml-20090407/boot3.log > > (In case it isn't clear, we get messages twice because console and > debug_LL are on the same serial port. I also had to increase > CONFIG_LOG_BUF_SHIFT to get a complete log in dmesg.) Can anyone give me any pointers on where to start for fixing the problems shown in the above boot log? It looks like some fairly low level locking bugs (spinlock vs raw_spinlock maybe?) in twl4030 IRQ handling and GP timer/clock event source setup. Hugo -- 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
