From: Tony Lindgren <tony@atomide.com>
To: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Alex Shi <alex.shi@linaro.org>,
khilman@linaro.org, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org, Roger Quadros <rogerq@ti.com>
Subject: Re: [PATCH] ARM: OMAP4: Fix the boot regression with CPU_IDLE enabled
Date: Mon, 19 May 2014 15:42:13 -0700 [thread overview]
Message-ID: <20140519224212.GL11945@atomide.com> (raw)
In-Reply-To: <537A7522.30007@math.uni-bielefeld.de>
* Tobias Jakobi <tjakobi@math.uni-bielefeld.de> [140519 14:19]:
> Daniel Lezcano wrote:
> >
> > So apparently Santosh, Kevin and Alex say they are not facing the
> > issue anymore with the revert. But Tobias is still facing this issue.
> >
> > There is this simple program [1] which usually makes cpuidle to hang
> > the system more quickly when there is a problem somewhere. May be
> > worth to check with it.
> >
> > Hope that helps.
> >
> > -- Daniel
> >
> > [1]
> > https://git.linaro.org/power/pm-qa.git/blob/HEAD:/cpuidle/cpuidle_killer.c
> >
> Hello,
>
> just to clarify. I never encountered the boot failure problem on my
> Panda ES in the first place. The issue with CPU_IDLE for me, like I also
> say in the bugreport, showed itself through instability of the USB. I
> saw the boot issue on the ml, read that it was caused by CPU_IDLE, and
> thought I should make Tony aware that I have a similar problem.
>
> Now, after applying the latest version of the patch that Santosh
> proposed, the situation with CPU_IDLE improves. But it is still not
> stable for me, since after some while, working with an SSH session of
> WiFi (which IIRC is not connected via USB on the board), this 'BUG'
> storm hits. This does _not_ happen when I disable CPU_IDLE completly.
OK that seems like a different problem.
> But even if I don't connect via WiFi at all, just boot and let me system
> run with serial console connected, after some time I get a kernel 'WARNING':
> http://www.math.uni-bielefeld.de/~tjakobi/archive/dmesg.1.log
>
> So something with CPU_IDLE is not right here. However I can't say if
> it's exactly this boot issue which this thread was initially about.
> Maybe seperate issues are at work here, who knows.
>
> Anyway, I'm going to have a look at that cpuidle killer thingy later.
OK. I gave it a try, but did not get any errors at least after about
30 minutes of testing on my panda es.
I'll apply the patch from Santosh as that gets things booting again
with linux next.
Regards,
Tony
next prev parent reply other threads:[~2014-05-19 22:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 14:39 [PATCH] ARM: OMAP4: Fix the boot regression with CPU_IDLE enabled Santosh Shilimkar
2014-05-14 15:22 ` Tony Lindgren
2014-05-14 19:44 ` Daniel Lezcano
2014-05-14 19:50 ` Santosh Shilimkar
2014-05-14 20:02 ` Daniel Lezcano
2014-05-14 20:56 ` Tony Lindgren
2014-05-14 23:31 ` Tony Lindgren
2014-05-16 0:13 ` Tony Lindgren
2014-05-16 0:40 ` Tony Lindgren
2014-05-14 21:18 ` Santosh Shilimkar
2014-05-15 17:03 ` Santosh Shilimkar
2014-05-15 17:50 ` Daniel Lezcano
2014-05-15 17:54 ` Santosh Shilimkar
2014-05-15 18:29 ` Santosh Shilimkar
2014-05-16 0:33 ` Alex Shi
2014-05-16 13:43 ` Santosh Shilimkar
2014-05-16 21:29 ` Tony Lindgren
2014-05-19 16:45 ` Daniel Lezcano
2014-05-19 17:23 ` Tony Lindgren
2014-05-19 17:34 ` Santosh Shilimkar
2014-05-19 17:51 ` Tony Lindgren
2014-05-19 18:06 ` Daniel Lezcano
2014-05-19 19:36 ` Tony Lindgren
2014-05-19 19:45 ` Daniel Lezcano
2014-05-19 21:18 ` Tobias Jakobi
2014-05-19 22:42 ` Tony Lindgren [this message]
2014-05-23 14:44 ` Tony Lindgren
2014-05-23 18:32 ` Tony Lindgren
[not found] ` <CAKnoXLxj42veWCbRjX98iT3FNAb92J4yR+UAL716JFSOb=pcrQ@mail.gmail.com>
2014-05-27 20:34 ` Tony Lindgren
2014-05-27 21:03 ` Santosh Shilimkar
2014-05-27 21:06 ` Daniel Lezcano
2014-05-19 20:00 ` Santosh Shilimkar
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=20140519224212.GL11945@atomide.com \
--to=tony@atomide.com \
--cc=alex.shi@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=rogerq@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=tjakobi@math.uni-bielefeld.de \
/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).