From: Christian Hoffmann <email@christianhoffmann.info>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: Chris Hoffmann <chrmhoffmann@gmail.com>, linux-omap@vger.kernel.org
Subject: Re: CPU_IDLE causes random reboots on custom 4430
Date: Tue, 25 Sep 2012 23:10:08 +0200 [thread overview]
Message-ID: <50621DB0.9090607@christianhoffmann.info> (raw)
In-Reply-To: <CAMQu2gw=Tki8uk_65w9iu645LY798Fr_GMHydF5XfZf8Xch5Yg@mail.gmail.com>
On 09/23/2012 06:11 PM, Shilimkar, Santosh wrote:
> On Sat, Sep 22, 2012 at 10:41 PM, Chris Hoffmann <chrmhoffmann@gmail.com> wrote:
>> On 09/22/2012 07:45 AM, Shilimkar, Santosh wrote:
>>>
>>> On Sat, Sep 22, 2012 at 4:19 AM, Chris Hoffmann <chrmhoffmann@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.
Hi Santosh, all,
the p-android-omap-3.0 doesn't have the persistent_trace but I was able
to backport it from 3.4 without major issues (only tricky part is that
in p-android-3.4 there's no apparent user of that device in omapzoom
kernel).
The problem is now that the omap-watchdog doesn't kick the device to
reboot but rather to shutdown, so I still have no trace. Soft-rebooting
shows that I can get persistent_trace.
Switching the persistent tracer to ecc=true does not help as it seems to
overload the device completely when activating the tracing.
Rgds,
Chris
prev parent reply other threads:[~2012-09-25 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 22:49 CPU_IDLE causes random reboots on custom 4430 Chris Hoffmann
2012-09-22 5:45 ` Shilimkar, Santosh
2012-09-22 17:11 ` Chris Hoffmann
2012-09-23 16:11 ` Shilimkar, Santosh
2012-09-25 21:10 ` Christian Hoffmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50621DB0.9090607@christianhoffmann.info \
--to=email@christianhoffmann.info \
--cc=chrmhoffmann@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).