All of lore.kernel.org
 help / color / mirror / Atom feed
From: Merlijn Wajer <merlijn@wizzup.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
	"Merlijn B.W. Wajer" <merlijn@archive.org>,
	Andreas Kemnade <andreas@kemnade.info>,
	Pavel Machek <pavel@ucw.cz>,
	linux-omap <linux-omap@vger.kernel.org>,
	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: Thu, 16 Dec 2021 12:38:51 +0100	[thread overview]
Message-ID: <aaf5d01a-4e31-67cc-7312-4449a30a0de8@wizzup.org> (raw)
In-Reply-To: <YbdPn21Xf8HD6ILM@atomide.com>

Hi,

On 13/12/2021 14:50, Tony Lindgren wrote:
> * Merlijn Wajer <merlijn@wizzup.org> [211213 10:45]:
>
>> and I am no longer seeing the oopses or resets when running "sleep 30;
>> blkid" from minimal userspace.
> 
> If disabling the cpu_thermal makes things behave, chances are we have wrong
> thermal values in the dts for n900 and possible all 34xx devices. The 36xx
> values are behaving AFAIK.

Just disabling the bandgap doesn't seem to be enough. I also tried
disabling just the bandgap and thermal_zones, but that is also isn't
enough. However, *just* disabling cpu_thermal also isn't enough.

Disabling both cpu_thermal and bandgap is enough to stop the oopses [1].
So it sounds like there might potentially be some problems in
cpu_thermal as well then?

Regards,
Merlijn

[1]

> diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dts
> index 1746a44e96bc..7aedd21282e1 100644
> --- a/arch/arm/boot/dts/omap3-n900.dts
> +++ b/arch/arm/boot/dts/omap3-n900.dts
> @@ -28,6 +28,19 @@ &aes2_target {
>         status = "disabled";
>  };
> 
> +&cpu_thermal {
> +       status = "disabled";
> +};
> +
> +&bandgap {
> +       status = "disabled";
> +};
> +//
> +//&thermal_zones {
> +//     status = "disabled";
> +//};
> +
> +
>  / {
>         model = "Nokia N900";
>         compatible = "nokia,omap3-n900", "ti,omap3430", "ti,omap3";

  reply	other threads:[~2021-12-16 11:33 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
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 [this message]
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=aaf5d01a-4e31-67cc-7312-4449a30a0de8@wizzup.org \
    --to=merlijn@wizzup.org \
    --cc=aaro.koskinen@iki.fi \
    --cc=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.