From: Dirk Behme <dirk.behme@googlemail.com>
To: linux-omap@vger.kernel.org
Cc: "Syed Mohammed, Khasim" <khasim@ti.com>
Subject: Kernel hang on OMAP3 based Beagle board, RTC issue?
Date: Wed, 02 Jul 2008 21:55:22 +0200 [thread overview]
Message-ID: <486BDD2A.5070500@googlemail.com> (raw)
At Beagle IRC there was some discussion [1] [2] today about kernel
hang on OMAP3 based Beagle board. I'll try to summarize discussion and
Khasim's findings, maybe somebody here has an idea.
Latest OMAP git kernel seems to hang on beagle board after some time.
You don't see any crash, but after a while typing, anything doesn't
work. SD stops as well, so you can only do stuff that's in ram, any IO
will block. It can take >1 day to get there, but mostly it's ~30 minutes.
Khasim found that it seems disabling RTC will remove the hang. When
booting the git kernel after some time there are no timer or PRCM
interrupts and the control resides in cpu_idle. We don't know where
exactly the problem in RTC is, but while browsing the history of files
related to RTC Khasim found that some changes were done to the files
to handle T2 interrupts in a centralized way for USB, Battery and RTC.
It seems even Battery broke with this patch set
http://source.mvista.com/git/gitweb.cgi?p=linux-omap-2.6.git;a=commitdiff;h=68d7477caca19c0b52b5d4e85700cd3e6115577f
May be this is the change that is affecting RTC. But it's unclear why
it is affecting GP timer and PRCM interrupts.
Any idea?
Thanks and please correct if something is wrong in the summary
Dirk
[1] http://www.beagleboard.org/irclogs/index.php?date=2008-07-02#T07:19:47
[2] http://www.beagleboard.org/irclogs/index.php?date=2008-07-02#T16:57:47
next reply other threads:[~2008-07-02 19:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 19:55 Dirk Behme [this message]
2008-07-02 20:03 ` Kernel hang on OMAP3 based Beagle board, RTC issue? Gadiyar, Anand
2008-07-02 20:18 ` Koen Kooi
2008-07-05 7:25 ` Dirk Behme
2008-07-05 9:53 ` Gadiyar, Anand
2008-07-05 13:22 ` Gadiyar, Anand
2008-07-07 7:34 ` Högander Jouni
2008-07-14 13:27 ` Gadiyar, Anand
2008-07-15 7:18 ` Koen Kooi
2008-07-15 7:49 ` Paul Walmsley
2008-07-15 7:54 ` Koen Kooi
2008-07-15 11:21 ` Gadiyar, Anand
2008-07-31 13:08 ` Syed Mohammed, Khasim
2008-07-31 13:33 ` Koen Kooi
2008-07-31 13:47 ` Syed Mohammed, Khasim
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=486BDD2A.5070500@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=khasim@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.