All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Merlijn B.W. Wajer" <merlijn@archive.org>,
	linux-omap <linux-omap@vger.kernel.org>,
	Tony Lindgren <tony@atomide.com>, Dev Null <devnull@uvos.xyz>,
	Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
	Sebastian Reichel <sre@kernel.org>,
	"H. Nikolaus Schaller" <hns@goldelico.com>
Subject: Re: Oops while booting 5.15.2 on Nokia N900
Date: Wed, 8 Dec 2021 22:04:00 +0100	[thread overview]
Message-ID: <20211208220400.1f9cff00@aktux> (raw)
In-Reply-To: <20211208205700.GA12125@duo.ucw.cz>

Hi,

On Wed, 8 Dec 2021 21:57:00 +0100
Pavel Machek <pavel@ucw.cz> wrote:

> Hi!
> 
> You may want to cc: linux-kernel@vger.kernel.org and
> phone-devel@vger.kernel.org, since this is kernel issue.
> 
> > > I am back with a bit more news, but no solution.  
> > 
> > It looks like commit fb2c599f056640d289b2147fbe6d9eaee689f1b2 ("ARM:
> > omap3: enable off mode automatically") is causing these failures on the
> > Nokia N900. Reverting this commit on top of v5.10 (with
> > 21b2cec61c04bd175f0860d9411a472d5a0e7ba1 also reverted), makes the
> > problem go away (I tried 10 times).
> > 
> > The same holds for 5.15.y, just reverting
> > fb2c599f056640d289b2147fbe6d9eaee689f1b2 makes the system "stable" (at
> > least the problem reported in the first email is gone).
> > 
> > Perhaps the "pwrst->next_state" change is causing these problems, since
> > I can enter OFF mode just fine with init=/bin/sh and a custom
> > script?  
> 
> fb2c599f056640d28 has some hints in it. Perhaps Andreas can mention
> what boards he tested it on?
> 
well, I tested it on gta04a4 and gta04a5 (both dm3730).
There is one 1Ghz issue at least on the a5, so I disabled that opp.

> And rather than reverting it, we may want to delete ti,twl4030-idle*
> hints from n900 device tree for now?
> 
well, it has side effects on power consumption, power consumption
should be worse without ti,twl4030-idle-*. So the real solution would
be to understand what is causing the trouble here.

Regards,
Andreas

  reply	other threads:[~2021-12-08 21:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-26 23:11 Oops while booting 5.15.2 on Nokia N900 Merlijn B.W. Wajer
2021-11-27 15:40 ` Merlijn B.W. Wajer
2021-12-08 14:12   ` Merlijn B.W. Wajer
2021-12-08 15:04     ` Merlijn B.W. Wajer
2021-12-08 20:57       ` Pavel Machek
2021-12-08 21:04         ` Andreas Kemnade [this message]
2021-12-08 22:34           ` Merlijn B.W. Wajer
2021-12-10 11:13             ` Aaro Koskinen
2021-12-10 23:43               ` Merlijn Wajer
2021-12-10 23:46               ` Merlijn Wajer
2021-12-11  6:57                 ` Tony Lindgren
2021-12-11 11:10                   ` Merlijn Wajer
2021-12-13  5:47                     ` Tony Lindgren
2021-12-13 10:36                       ` Merlijn Wajer
2021-12-13 10:50                         ` Merlijn Wajer
2021-12-13 13:50                           ` Tony Lindgren
2021-12-16 11:38                             ` Merlijn Wajer
2021-12-18  7:34                               ` Tony Lindgren

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=20211208220400.1f9cff00@aktux \
    --to=andreas@kemnade.info \
    --cc=devnull@uvos.xyz \
    --cc=hns@goldelico.com \
    --cc=ivo.g.dimitrov.75@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=merlijn@archive.org \
    --cc=pavel@ucw.cz \
    --cc=sre@kernel.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 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.