From: Chris Hoffmann <chrmhoffmann@gmail.com>
To: linux-omap@vger.kernel.org
Subject: CPU_IDLE causes random reboots on custom 4430
Date: Sat, 22 Sep 2012 00:49:33 +0200 [thread overview]
Message-ID: <505CEEFD.1080507@gmail.com> (raw)
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.
The problem is that kmsg_last doesn't not show any useful information
and the fiq debugger refuses to work when the device is locked up. We
also enabled various kernel lock debugging configs to get more info ...
in vain.
Experimenting with it for a while (removing non-standard drivers like
accel, charger, battery, etc) we found that removing CONFIG_CPU_IDLE or
setting disallow_smp_idle in cpuidle44xx.c seems to cure the random
lockups and make the board work fine (apart from the maybe obvious
consequences that it doesn't go to deep sleep anymore).
Further below a few sample infos from the board.
We'd very much appreciate any further help on how to proceed to find the
root cause and happy to provide any more info from sys, debug or
omapconf tool.
Rgds,
Chris
A dmesg from a normal boot:
https://dl.dropbox.com/u/21820416/CPU_IDLE_CRASH/dmesg.log
Kernel source:
https://github.com/Kuzma30/kernel3NookTablet/tree/jellybean
omapconf --cpuinfo
https://dl.dropbox.com/u/21820416/CPU_IDLE_CRASH/omapconf.cpuinfo
cat /sys/kernel/debug/clock/summary
https://dl.dropbox.com/u/21820416/CPU_IDLE_CRASH/clock.summary
... what else can we provide to track this down?
next reply other threads:[~2012-09-21 22:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 22:49 Chris Hoffmann [this message]
2012-09-22 5:45 ` CPU_IDLE causes random reboots on custom 4430 Shilimkar, Santosh
2012-09-22 17:11 ` Chris Hoffmann
2012-09-23 16:11 ` Shilimkar, Santosh
2012-09-25 21:10 ` Christian Hoffmann
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=505CEEFD.1080507@gmail.com \
--to=chrmhoffmann@gmail.com \
--cc=linux-omap@vger.kernel.org \
/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).