linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-sh@vger.kernel.org
Subject: Re: ap4 (sh7372) regression in 3.3 / 3.4 with serial console - boot failures
Date: Tue, 22 May 2012 16:55:27 +0000	[thread overview]
Message-ID: <201205221855.27493.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.64.1205161431380.30283@axis700.grange>

On Tuesday, May 22, 2012, Laurent Pinchart wrote:
> Hi Paul,
> 
> On Thursday 17 May 2012 09:46:04 Paul Mundt wrote:
> > On Wed, May 16, 2012 at 03:36:10PM +0200, Guennadi Liakhovetski wrote:
> > > I'm observing a regression with 3.3 and 3.4 kernels, 3.2 seems to be ok.
> > > The system (confirmed with mackerel and ap4evb) hangs during boot at
> > > random times. This can be directly after "freeing init memory," or some
> > > time during the OS start up, or immediately after the start up has
> > > completed. But if it managed to boot, it continues to run, I've never seen
> > > it hanging after I ssh onto the system. It also seems, that the
> > > probability to hang increases with time after the initial system power on.
> > > A simple short power off doesn't solve the problem.
> > 
> > So you experience random hangs at boot and you have a known good and
> > known bad version. If only there were some sort of a bisection tool one
> > could use..
> 
> I'm experiencing the same issue on mackerel. I don't know at which kernel 
> version the problems started in my case though.
> 
> Bisecting this would take quite a long time given the random nature of the 
> problem. If there's no other option we'll of course need to go that way, but 
> it certainly made sense to raise the matter on the list before investigating 
> it in case someone was already working on a fix (or, better, had already 
> written a fix :-)).

Well, why would they work on it if they didn't know that the issue was there?

Whatever.

Please try to add an extra pm_runtime_get() to the serial console initialization
to prevent it from being suspended and see if the problem is still reproducible
then.

Thanks,
Rafael

      parent reply	other threads:[~2012-05-22 16:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 13:36 ap4 (sh7372) regression in 3.3 / 3.4 with serial console - boot failures Guennadi Liakhovetski
2012-05-17  0:46 ` Paul Mundt
2012-05-22 16:13 ` Laurent Pinchart
2012-05-22 16:55 ` Rafael J. Wysocki [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=201205221855.27493.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-sh@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).