From: Pavel Machek <pavel@denx.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Pavel Machek <pavel@denx.de>,
niklas.soderlund+renesas@ragnatech.se,
yoshihiro.shimoda.uh@renesas.com, geert+renesas@glider.be,
biju.das.jz@bp.renesas.com, Chris.Paterson2@renesas.com,
stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org
Subject: Re: renesas_sdhi problems in 5.10-stable was Re: [PATCH 5.10 000/226] 5.10.198-rc1 review
Date: Tue, 24 Oct 2023 21:22:19 +0200 [thread overview]
Message-ID: <ZTgZa1ic1iFbdaTM@duo.ucw.cz> (raw)
In-Reply-To: <2023101057-runny-pellet-8952@gregkh>
[-- Attachment #1: Type: text/plain, Size: 3520 bytes --]
Hi!
> > > And testing failed. So
> > >
> > > commit f5799b4e142884c2e7aa99f813113af4a3395ffb
> > > Author: Wolfram Sang <wsa+renesas@sang-engineering.com>
> > > Date: Tue Nov 10 15:20:57 2020 +0100
> > >
> > > mmc: renesas_sdhi: populate SCC pointer at the proper place
> > >
> > > [ Upstream commit d14ac691bb6f6ebaa7eeec21ca04dd47300ff5b6 ]
> > >
> > > seems to be the buggy commit that breaks renesas boards in 5.10.
> >
> > This patch was part of a series. Did the other two patches come with it?
> >
> > b161d87dfd3d ("mmc: renesas_sdhi: probe into TMIO after SCC parameters have been setup")
>
> Yes.
>
> > 45bffc371fef ("mmc: renesas_sdhi: only reset SCC when its pointer is populated")
>
> No :(
>
> > If not, I could imagine that could lead to a crash. No idea why only
> > with 5.10, though.
>
> The above commit is only in 5.11, so newer kernels should be fine.
>
> I'll go queue up the one missing patch now, thanks.
Thank you. Patch indeed appears to be in 5.10.199.
But we still have failures on Renesas with 5.10.199-rc2:
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/1047368849
And they still happed during MMC init:
2.638013] renesas_sdhi_internal_dmac ee100000.mmc: Got CD GPIO
[ 2.638846] INFO: trying to register non-static key.
[ 2.644192] ledtrig-cpu: registered to indicate activity on CPUs
[ 2.649066] The code is fine but needs lockdep annotation, or maybe
[ 2.649069] you didn't initialize this object before use?
[ 2.649071] turning off the locking correctness validator.
[ 2.649080] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.10.199-rc2-arm64-renesas-ge31b6513c43d #1
[ 2.649082] Hardware name: HopeRun HiHope RZ/G2M with sub board (DT)
[ 2.649086] Call trace:
[ 2.655106] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[ 2.661354] dump_backtrace+0x0/0x194
[ 2.661361] show_stack+0x14/0x20
[ 2.667430] usbcore: registered new interface driver usbhid
[ 2.672230] dump_stack+0xe8/0x130
[ 2.672238] register_lock_class+0x480/0x514
[ 2.672244] __lock_acquire+0x74/0x20ec
[ 2.681113] usbhid: USB HID core driver
[ 2.687450] lock_acquire+0x218/0x350
[ 2.687456] _raw_spin_lock+0x58/0x80
[ 2.687464] tmio_mmc_irq+0x410/0x9ac
[ 2.688556] renesas_sdhi_internal_dmac ee160000.mmc: mmc0 base at 0x00000000ee160000, max clock rate 200 MHz
[ 2.744936] __handle_irq_event_percpu+0xbc/0x340
[ 2.749635] handle_irq_event+0x60/0x100
[ 2.753553] handle_fasteoi_irq+0xa0/0x1ec
[ 2.757644] __handle_domain_irq+0x7c/0xdc
[ 2.761736] efi_header_end+0x4c/0xd0
[ 2.765393] el1_irq+0xcc/0x180
[ 2.768530] arch_cpu_idle+0x14/0x2c
[ 2.772100] default_idle_call+0x58/0xe4
[ 2.776019] do_idle+0x244/0x2c0
[ 2.779242] cpu_startup_entry+0x20/0x6c
[ 2.783160] rest_init+0x164/0x28c
[ 2.786561] arch_call_rest_init+0xc/0x14
[ 2.790565] start_kernel+0x4c4/0x4f8
[ 2.794233] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000014
[ 2.803011] Mem abort info:
from https://lava.ciplatform.org/scheduler/job/1025535
from
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/5360973735 .
Is there something else missing?
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2023-10-24 19:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 12:59 [PATCH 5.10 000/226] 5.10.198-rc1 review Greg Kroah-Hartman
2023-10-09 19:33 ` Pavel Machek
2023-10-09 20:13 ` renesas_sdhi problems in 5.10-stable was " Pavel Machek
2023-10-10 11:18 ` Pavel Machek
2023-10-10 12:05 ` Pavel Machek
2023-10-10 19:07 ` Wolfram Sang
2023-10-10 19:14 ` Greg Kroah-Hartman
2023-10-24 19:22 ` Pavel Machek [this message]
2023-10-25 10:47 ` Geert Uytterhoeven
2023-10-25 10:53 ` Geert Uytterhoeven
2023-10-25 12:35 ` Geert Uytterhoeven
2023-10-25 17:05 ` Geert Uytterhoeven
2023-10-25 18:39 ` Guenter Roeck
2023-10-25 19:53 ` Geert Uytterhoeven
2023-10-25 21:26 ` Geert Uytterhoeven
2023-10-26 12:08 ` Geert Uytterhoeven
2023-10-26 12:20 ` Geert Uytterhoeven
2023-10-25 22:00 ` Pavel Machek
2023-10-26 1:23 ` Guenter Roeck
2023-10-09 20:24 ` Florian Fainelli
2023-10-09 22:57 ` Shuah Khan
2023-10-10 9:57 ` Jon Hunter
2023-10-10 18:18 ` Guenter Roeck
2023-10-11 1:40 ` Naresh Kamboju
2023-10-11 6:47 ` luomeng
2023-10-11 9:18 ` Pavel Machek
2023-10-11 9:38 ` Pavel Machek
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=ZTgZa1ic1iFbdaTM@duo.ucw.cz \
--to=pavel@denx.de \
--cc=Chris.Paterson2@renesas.com \
--cc=akpm@linux-foundation.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=yoshihiro.shimoda.uh@renesas.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