From: Francesco Dolcini <francesco@dolcini.it>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: Francesco Dolcini <francesco@dolcini.it>,
Jerome Neanne <jneanne@baylibre.com>,
Shree Ramamoorthy <s-ramamoorthy@ti.com>,
Mark Brown <broonie@kernel.org>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Kevin Hilman <khilman@baylibre.com>,
Roger Quadros <rogerq@kernel.org>,
Tony Lindgren <tony@atomide.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: tps65219/am62p kernel oops
Date: Wed, 30 Apr 2025 10:01:09 +0200 [thread overview]
Message-ID: <20250430080109.GA65078@francesco-nb> (raw)
In-Reply-To: <20250429185240.6a7644bf@akair>
On Tue, Apr 29, 2025 at 06:52:40PM +0200, Andreas Kemnade wrote:
> Am Tue, 29 Apr 2025 15:21:19 +0200
> schrieb Francesco Dolcini <francesco@dolcini.it>:
>
> > Hello all,
> > while working on adding support in mainline for a new board based on TI
> > AM62P SoC I noticed the following Kernel Oops.
> >
> > This oops was reproduced running current Linux
> > master, 6.15.0-rc4+, ca91b9500108d4cf083a635c2e11c884d5dd20ea, but I was able
> > to reproduce the same with 6.14.4.
> >
>
> [...]
> > [ +0.000022] Call trace:
> > [ +0.000011] regulator_notifier_call_chain+0x20/0xa4 (P)
> > [ +0.000018] tps65219_regulator_irq_handler+0x34/0x80
>
> wild guessing: maybe because irqdata->rdev is not initalized in
> _probe()? At least I do not see where it would be initialized.
your wild guess seems correct, I'll send a proper patch with your
suggested-by after doing a couple of more tests, thanks.
Francesco
next prev parent reply other threads:[~2025-04-30 8:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 13:21 tps65219/am62p kernel oops Francesco Dolcini
2025-04-29 16:52 ` Andreas Kemnade
2025-04-30 8:01 ` Francesco Dolcini [this message]
2025-04-30 10:21 ` Francesco Dolcini
2025-05-01 15:32 ` Shree Ramamoorthy
2025-12-09 13:43 ` Francesco Dolcini
2025-12-09 18:16 ` Shree Ramamoorthy
2025-12-10 8:10 ` Francesco Dolcini
2026-03-16 17:41 ` Alexander Sverdlin
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=20250430080109.GA65078@francesco-nb \
--to=francesco@dolcini.it \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=broonie@kernel.org \
--cc=jneanne@baylibre.com \
--cc=khilman@baylibre.com \
--cc=kristo@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=rogerq@kernel.org \
--cc=s-ramamoorthy@ti.com \
--cc=tony@atomide.com \
--cc=vigneshr@ti.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