On Sat, Sep 22, 2012 at 10:41 PM, Chris Hoffmann <chrmhoffm...@gmail.com> wrote: > On 09/22/2012 07:45 AM, Shilimkar, Santosh wrote: >> >> On Sat, Sep 22, 2012 at 4:19 AM, Chris Hoffmann <chrmhoffm...@gmail.com> >> wrote: >>> >>> Hi, >>> >>> We're trying to get a custom 4430 board (aka. nook tablet with OMAP4430 >>> ES2.3 HS TWL6030 ES2.1) working with p-android-omap-3.0 on android jelly >>> bean. The board works quite well, but we experience random hangs and the >>> watchdog kicks the board to reboot. >>> >> On the same kernel, you should have support for the persistent log. You >> might >> want to check the output. That should give you pointers on what CPU was >> doing before the freeze which resulted in reboot. > > > Hi, > > I have some problems to provide logs. If I add -DDEBUG to cpuidle44xx.o the > problem doesn't seem to occur. It could be that printk-ing alleviates the > issue. > > Also the watchdog seems to shutdown the device rather than rebooting it (or > it hangs?) and then I can't provide /proc/last_kmsg. > > How could I provide more info? > Check if you have "/sys/kernel/debug/persistent_trace" available on your kernel. This generally helps whenever there are hangs, the last call stack is stored on memory and on the reboot it can be cat'ed to see if some useful information about hang is available.
Regards Santosh -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
