From: Roger Quadros <rogerq@ti.com>
To: "tony@atomide.com" <tony@atomide.com>, "Menon, Nishanth" <nm@ti.com>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
Paul Walmsley <paul@pwsan.com>, Kevin Hilman <khilman@linaro.org>,
taras.kondratiuk@linaro.org,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>,
"Kristo, Tero" <t-kristo@ti.com>
Subject: omap4-panda-es boot issues with v3.15-rc4
Date: Thu, 8 May 2014 15:53:24 +0300 [thread overview]
Message-ID: <536B7E44.2040303@ti.com> (raw)
Hi,
Nishant pointed me to a booting issue with omap4-panda-es on linux-next but I'm observing
similar issues, although less frequent, with v3.15-rc4 as well.
Configuration:
- kernel v3.15-rc4 or linux-next (20140507)
- multi_v7_defconfig with LEDS_TRIGGER_HEARTBEAT and LEDS_GPIO enabled
- u-boot/master 173d294b94cf
Observations:
- Out of 10 boots a few may not succeed and hang midway without any warnings. Heartbeat LED stops.
e.g. http://www.hastebin.com/ebumojegoq.vhdl
- Hang more noticeable on linux-next (20140507) than on v3.15-rc4
- Hang more noticeable with USB_EHCI_HCD enabled but hang observed even without USB_EHCI_HCD.
Maybe related to when high speed interrupts occur in the boot process.
- On successful boots following warning is seen
[ 4.010375] gic_timer_retrigger: lost localtimer interrupt
- On successful boots heartbeat LED stops blinking after boot process and left idle. LED can remain stuck in
ON state as well. It does blink again when doing activity on console.
Workaround:
- Disabling CPU_IDLE or even just disabling C3 (MPU OSWR) seems to fix all the above issues.
I don't really know what exactly is the issue but it seems to be specific to OMAP4, GIC, MPU OSWR.
cheers,
-roger
next reply other threads:[~2014-05-08 12:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 12:53 Roger Quadros [this message]
2014-05-08 15:31 ` omap4-panda-es boot issues with v3.15-rc4 Kevin Hilman
2014-05-08 15:40 ` Kevin Hilman
2014-05-08 16:55 ` Tony Lindgren
2014-05-08 18:40 ` Tony Lindgren
2014-05-08 22:15 ` Kevin Hilman
2014-05-09 8:23 ` Roger Quadros
2014-05-09 23:45 ` Kevin Hilman
2014-05-11 15:55 ` Tony Lindgren
2014-05-12 21:40 ` Santosh Shilimkar
2014-05-12 22:07 ` Tony Lindgren
2014-05-13 8:10 ` Roger Quadros
2014-05-13 14:19 ` Santosh Shilimkar
2014-05-12 23:56 ` Kevin Hilman
2014-05-09 8:20 ` Roger Quadros
2014-05-08 17:12 ` Grygorii Strashko
2014-05-09 8:30 ` Roger Quadros
2014-05-09 12:33 ` Nishanth Menon
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=536B7E44.2040303@ti.com \
--to=rogerq@ti.com \
--cc=grygorii.strashko@ti.com \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=paul@pwsan.com \
--cc=santosh.shilimkar@ti.com \
--cc=t-kristo@ti.com \
--cc=taras.kondratiuk@linaro.org \
--cc=tony@atomide.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).