From: Maxime Ripard <maxime@cerno.tech>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Doug Berger <opendmb@gmail.com>,
bcm-kernel-feedback-list@broadcom.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Nicolas Saenz Julienne <nsaenz@kernel.org>
Subject: Re: Kernel Panic in skb_release_data using genet
Date: Mon, 24 May 2021 17:13:29 +0200 [thread overview]
Message-ID: <20210524151329.5ummh4dfui6syme3@gilmour> (raw)
In-Reply-To: <a53f6192-3520-d5f8-df4b-786b3e4e8707@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]
Hi Florian,
On Mon, May 24, 2021 at 07:49:25AM -0700, Florian Fainelli wrote:
> Hi Maxime,
>
> On 5/24/2021 6:01 AM, Maxime Ripard wrote:
> > Hi Doug, Florian,
> >
> > I've been running a RaspberryPi4 with a mainline kernel for a while,
> > booting from NFS. Every once in a while (I'd say ~20-30% of all boots),
> > I'm getting a kernel panic around the time init is started.
> >
> > I was debugging a kernel based on drm-misc-next-2021-05-17 today with
> > KASAN enabled and got this, which looks related:
>
> Is there a known good version that could be used for bisection or you
> just started to do this test and you have no reference point?
I've had this issue for over a year and never (I think?) got a good
version, so while it might be a regression, it's not a recent one.
> How stable in terms of clocking is the configuration that you are using?
> I could try to fire up a similar test on a Pi4 at home, or use one of
> our 72112 systems which is the closest we have to a Pi4 and see if that
> happens there as well.
I'm not really sure about the clocking. Is there any clock you want to
look at in particular?
My setup is fairly simple: the firmware and kernel are loaded over TFTP
and the rootfs is mounted over NFS, and the crash always occur around
init start, so I guess when it actually starts to transmit a decent
amount of data?
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2021-05-24 15:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 13:01 Kernel Panic in skb_release_data using genet Maxime Ripard
2021-05-24 14:49 ` Florian Fainelli
2021-05-24 15:13 ` Maxime Ripard [this message]
2021-05-24 15:37 ` Florian Fainelli
2021-05-28 16:21 ` Florian Fainelli
2021-05-28 16:32 ` Maxime Ripard
2021-05-28 16:48 ` Florian Fainelli
2021-06-01 2:36 ` Florian Fainelli
2021-06-01 9:33 ` nicolas saenz julienne
2021-06-02 13:28 ` Maxime Ripard
2021-06-10 21:33 ` Florian Fainelli
2021-06-25 12:59 ` Maxime Ripard
2021-07-02 16:49 ` Florian Fainelli
2021-07-06 8:16 ` Maxime Ripard
2022-05-13 14:56 ` Maxime Ripard
2022-05-14 16:35 ` Florian Fainelli
2022-05-17 7:52 ` Maxime Ripard
2022-08-12 3:33 ` Florian Fainelli
2022-08-15 7:07 ` Maxime Ripard
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=20210524151329.5ummh4dfui6syme3@gilmour \
--to=maxime@cerno.tech \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nsaenz@kernel.org \
--cc=opendmb@gmail.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;
as well as URLs for NNTP newsgroup(s).