From: Adam Ford <aford173@gmail.com>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: Peng Fan <peng.fan@nxp.com>, "S.J. Wang" <shengjiu.wang@nxp.com>,
"abelvesa@kernel.org" <abelvesa@kernel.org>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"sboyd@kernel.org" <sboyd@kernel.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
dl-linux-imx <linux-imx@nxp.com>,
"shengjiu.wang@gmail.com" <shengjiu.wang@gmail.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Mark Brown <broonie@kernel.org>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>
Subject: Re: clk_imx8mp_audiomix_runtime_resume Kernel panic regression on v6.12
Date: Sun, 13 Oct 2024 20:37:00 -0500 [thread overview]
Message-ID: <CAHCN7xKmrAYad2Mc29cUvDovbP7Hhv0sOFaNtjpdVWZeET-egQ@mail.gmail.com> (raw)
In-Reply-To: <84371A37-9C3D-44AF-8796-7427B39DC3D4@dolcini.it>
On Tue, Oct 8, 2024 at 7:24 AM Francesco Dolcini <francesco@dolcini.it> wrote:
>
> Il 8 ottobre 2024 14:19:15 CEST, Adam Ford <aford173@gmail.com> ha scritto:
> >On Tue, Oct 8, 2024 at 3:51 AM Peng Fan <peng.fan@nxp.com> wrote:
> >>
> >> > Subject: RE: clk_imx8mp_audiomix_runtime_resume Kernel panic
> >> > regression on v6.12
> >> >
> >> > > Subject: clk_imx8mp_audiomix_runtime_resume Kernel panic
> >> > regression on
> >> > > v6.12
> >> > >
> >> > >
> >> > > Is it now back?
> >> >
> >> > With tag: next-20240930, I need see this issue on i.MX8MP-EVK board.
> >>
> >> Sorry, typo. I not see issue on my board.
> >
> >I tested RC1 on the Beacon board and didn't see any issues, but I can
> >try testing linux-next when I have some time.
> >
>
> I forgot to mention that the issue is not systematic as it was in the original report.
>
> And it was reproduced on v6.12-rc2, not with -next.
I tested RC3, and I cannot replicate it. Are you still having issues?
adam
>
> Francesco
>
>
> >adam
> >>
> >> Regards,
> >> Peng.
> >>
> >> >
> >> > Regards,
> >> > Peng.
> >> >
> >> > >
> >> > > [ 4.012850] SError Interrupt on CPU2, code 0x00000000bf000002 -
> >> > -
> >> > > SError
> >> > > [ 4.012862] CPU: 2 UID: 0 PID: 186 Comm: (udev-worker) Not
> >> > tainted
> >> > > 6.12.0-rc2-0.0.0-devel-00004-g8b1b79e88956 #1
> >> > > [ 4.012869] Hardware name: Toradex Verdin iMX8M Plus WB on
> >> > > Dahlia Board (DT)
> >> > > [ 4.012872] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -
> >> > SSBS
> >> > > BTYPE=--)
> >> > > [ 4.012877] pc :
> >> > clk_imx8mp_audiomix_runtime_resume+0x38/0x48
> >> > > [ 4.012891] lr : pm_generic_runtime_resume+0x2c/0x44
> >> > > [ 4.012897] sp : ffff8000821cb740
> >> > > [ 4.012899] x29: ffff8000821cb740 x28: ffff8000793c48d8 x27:
> >> > > ffff8000793c48c0
> >> > > [ 4.012908] x26: ffff0000c0ec90f4 x25: 0000000000000000 x24:
> >> > > 0000000000000000
> >> > > [ 4.012916] x23: 0000000000000000 x22: ffff0000c1bef180 x21:
> >> > > 0000000000000000
> >> > > [ 4.012923] x20: ffff0000c0a73000 x19: ffff0000c0ecbc10 x18:
> >> > > ffffffffffffffff
> >> > > [ 4.012930] x17: 3030303064623033 x16: 2f7375622e303030 x15:
> >> > > 756e285472656c6c
> >> > > [ 4.012937] x14: ffff800081267458 x13: 6d692c6c73664361 x12:
> >> > > 0000000000000000
> >> > > [ 4.012944] x11: 00353333333d4d55 x10: ffff8000818020ae x9 :
> >> > > 0000000000000008
> >> > > [ 4.012951] x8 : 0000000000000008 x7 : 0000000000000000 x6 :
> >> > > ffff0000c5bf2080
> >> > > [ 4.012958] x5 : ffff800081f10000 x4 : ffff800080c182e8 x3 :
> >> > > ffff0000c0ee7088
> >> > > [ 4.012965] x2 : 0000000000000000 x1 : 0000000000000004 x0 :
> >> > > ffff800081f10300
> >> > > [ 4.012973] Kernel panic - not syncing: Asynchronous SError
> >> > Interrupt
> >> > > [ 4.012976] CPU: 2 UID: 0 PID: 186 Comm: (udev-worker) Not
> >> > tainted
> >> > > 6.12.0-rc2-0.0.0-devel-00004-g8b1b79e88956 #1
> >> > > [ 4.012982] Hardware name: Toradex Verdin iMX8M Plus WB on
> >> > > Dahlia Board (DT)
> >> > > [ 4.012985] Call trace:
> >> > > [ 4.012988] dump_backtrace+0xd0/0x120
> >> > > [ 4.012998] show_stack+0x18/0x24
> >> > > [ 4.013005] dump_stack_lvl+0x60/0x80
> >> > > [ 4.013013] dump_stack+0x18/0x24
> >> > > [ 4.013019] panic+0x168/0x350
> >> > > [ 4.013025] add_taint+0x0/0xbc
> >> > > [ 4.013029] arm64_serror_panic+0x64/0x70
> >> > > [ 4.013034] do_serror+0x3c/0x70
> >> > > [ 4.013039] el1h_64_error_handler+0x30/0x54
> >> > > [ 4.013046] el1h_64_error+0x64/0x68
> >> > > [ 4.013050] clk_imx8mp_audiomix_runtime_resume+0x38/0x48
> >> > > [ 4.013059] __genpd_runtime_resume+0x30/0x80
> >> > > [ 4.013066] genpd_runtime_resume+0x114/0x29c
> >> > > [ 4.013073] __rpm_callback+0x48/0x1e0
> >> > > [ 4.013079] rpm_callback+0x68/0x80
> >> > > [ 4.013084] rpm_resume+0x3bc/0x6a0
> >> > > [ 4.013089] __pm_runtime_resume+0x50/0x9c
> >> > > [ 4.013095] pm_runtime_get_suppliers+0x60/0x8c
> >> > > [ 4.013101] __driver_probe_device+0x4c/0x14c
> >> > > [ 4.013108] driver_probe_device+0x3c/0x120
> >> > > [ 4.013114] __driver_attach+0xc4/0x200
> >> > > [ 4.013119] bus_for_each_dev+0x7c/0xe0
> >> > > [ 4.013125] driver_attach+0x24/0x30
> >> > > [ 4.013130] bus_add_driver+0x110/0x240
> >> > > [ 4.013135] driver_register+0x68/0x124
> >> > > [ 4.013142] __platform_driver_register+0x24/0x30
> >> > > [ 4.013149] sdma_driver_init+0x20/0x1000 [imx_sdma]
> >> > > [ 4.013163] do_one_initcall+0x60/0x1e0
> >> > > [ 4.013168] do_init_module+0x5c/0x21c
> >> > > [ 4.013175] load_module+0x1a98/0x205c
> >> > > [ 4.013181] init_module_from_file+0x88/0xd4
> >> > > [ 4.013187] __arm64_sys_finit_module+0x258/0x350
> >> > > [ 4.013194] invoke_syscall.constprop.0+0x50/0xe0
> >> > > [ 4.013202] do_el0_svc+0xa8/0xe0
> >> > > [ 4.013208] el0_svc+0x3c/0x140
> >> > > [ 4.013215] el0t_64_sync_handler+0x120/0x12c
> >> > > [ 4.013222] el0t_64_sync+0x190/0x194
> >> > > [ 4.013228] SMP: stopping secondary CPUs
> >> > > [ 4.013237] Kernel Offset: disabled
> >> > > [ 4.013239] CPU features: 0x00,00000000,00200000,4200420b
> >> > > [ 4.013243] Memory Limit: none
> >> > > [ 4.316721] ---[ end Kernel panic - not syncing: Asynchronous SError
> >> > > Interrupt ]---
> >> > >
> >> > >
> >> > > Francesco
> >>
>
> Hello,
next prev parent reply other threads:[~2024-10-14 1:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 13:25 clk_imx8mp_audiomix_runtime_resume Kernel panic regression on v6.12 Francesco Dolcini
2024-10-08 8:47 ` Peng Fan
2024-10-08 8:51 ` Peng Fan
2024-10-08 12:19 ` Adam Ford
2024-10-08 12:24 ` Francesco Dolcini
2024-10-14 1:37 ` Adam Ford [this message]
2024-11-12 7:59 ` Francesco Dolcini
2024-11-12 9:20 ` Francesco Dolcini
2024-11-15 3:13 ` Shengjiu Wang
2024-11-15 14:47 ` Francesco Dolcini
2024-11-19 9:35 ` Shengjiu Wang
2024-11-19 11:22 ` Francesco Dolcini
2024-11-19 14:05 ` Adam Ford
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=CAHCN7xKmrAYad2Mc29cUvDovbP7Hhv0sOFaNtjpdVWZeET-egQ@mail.gmail.com \
--to=aford173@gmail.com \
--cc=abelvesa@kernel.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=francesco@dolcini.it \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=regressions@lists.linux.dev \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=shengjiu.wang@gmail.com \
--cc=shengjiu.wang@nxp.com \
--cc=ulf.hansson@linaro.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).