From: "Zhang, Rui" <rui.zhang@intel.com>
To: "Greenman, Gregory" <gregory.greenman@intel.com>,
"Berg, Johannes" <johannes.berg@intel.com>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: "bagasdotme@gmail.com" <bagasdotme@gmail.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"kvalo@kernel.org" <kvalo@kernel.org>,
"Baruch, Yaara" <yaara.baruch@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Torvalds, Linus" <torvalds@linux-foundation.org>,
"Ben Ami, Golan" <golan.ben.ami@intel.com>,
"edumazet@google.com" <edumazet@google.com>,
"Sisodiya, Mukesh" <mukesh.sisodiya@intel.com>,
"Larry.Finger@lwfinger.net" <Larry.Finger@lwfinger.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>
Subject: Re: [Regression][BISECTED] kernel boot hang after 19898ce9cf8a ("wifi: iwlwifi: split 22000.c into multiple files")
Date: Sun, 9 Jul 2023 13:27:33 +0000 [thread overview]
Message-ID: <4153ce0aac6dc760a3a9c7204c5c9141b60839a4.camel@intel.com> (raw)
In-Reply-To: <c65d0837-5e64-bec7-9e56-04aa91148d05@leemhuis.info>
On Sat, 2023-07-08 at 16:17 +0200, Thorsten Leemhuis wrote:
> On 07.07.23 12:55, Linux regression tracking (Thorsten Leemhuis)
> wrote:
> > On 07.07.23 10:25, Zhang, Rui wrote:
> > >
> > > I run into a NULL pointer dereference and kernel boot hang after
> > > switching to latest upstream kernel, and git bisect shows that
> > > below
> > > commit is the first offending commit, and I have confirmed that
> > > commit
> > > 19898ce9cf8a has the issue while 19898ce9cf8a~1 does not.
> >
> > FWIW, this is the fourth such report about this that I'm aware of.
> >
> > The first is this one (with two affected users afaics):
> > https://bugzilla.kernel.org/show_bug.cgi?id=217622
> >
> > The second is this one:
> > https://lore.kernel.org/all/CAAJw_Zug6VCS5ZqTWaFSr9sd85k%3DtyPm9DEE%2BmV%3DAKoECZM%2BsQ@mail.gmail.com/
> >
> > The third:
> > https://lore.kernel.org/all/9274d9bd3d080a457649ff5addcc1726f08ef5b2.camel@xry111.site/
> >
> > And in the past few days two people from Fedora land talked to me
> > on IRC
> > with problems that in retrospective might be caused by this as
> > well.
>
> I got confirmation: one of those cases is also caused by 19898ce9cf8a
> But I write for a different reason:
>
> Larry (now CCed) looked at the culprit and spotted something that
> looked
> suspicious to him; he posted a patch and looks for testers:
> https://lore.kernel.org/all/0068af47-e475-7e8d-e476-c374e90dff5f@lwfinger.net/
I applied this patch but the problem still exists.
thanks,
rui
>
> Ciao, Thorsten
>
> > This many reports about a problem at this stage of the cycle makes
> > me
> > suspect we'll see a lot more once -rc1 is out. That's why I raising
> > the
> > awareness of this. Sadly a simple revert of just this commit is not
> > possible. :-/
> >
> > Ciao, Thorsten
> >
> > > commit 19898ce9cf8a33e0ac35cb4c7f68de297cc93cb2 (refs/bisect/bad)
> > > Author: Johannes Berg <johannes.berg@intel.com>
> > > AuthorDate: Wed Jun 21 13:12:07 2023 +0300
> > > Commit: Johannes Berg <johannes.berg@intel.com>
> > > CommitDate: Wed Jun 21 14:07:00 2023 +0200
> > >
> > > wifi: iwlwifi: split 22000.c into multiple files
> > >
> > > Split the configuration list in 22000.c into four new files,
> > > per new device family, so we don't have this huge unusable
> > > file. Yes, this duplicates a few small things, but that's
> > > still much better than what we have now.
> > >
> > > Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> > > Signed-off-by: Gregory Greenman <gregory.greenman@intel.com>
> > > Link:
> > > https://lore.kernel.org/r/20230621130443.7543603b2ee7.Ia8dd54216d341ef1ddc0531f2c9aa30d30536a5d@changeid
> > > Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> > >
> > > I have some screenshots which show that RIP points to
> > > iwl_mem_free_skb,
> > > I can create a kernel bugzilla and attach the screenshots there
> > > if
> > > needed.
> > >
> > > BTW, lspci output of the wifi device and git bisect log attached.
> > >
> > > If any other information needed, please let me know.
> >
> > --
> > Everything you wanna know about Linux kernel regression tracking:
> > https://linux-regtracking.leemhuis.info/about/#tldr
> > That page also explains what to do if mails like this annoy you.
> >
> > P.S.: for regzbot
> >
> > #regzbot ^introduced 19898ce9cf8a
> > #regzbot dup-of:
> > https://lore.kernel.org/all/a5cdc7f8-b340-d372-2971-0d24b01de217@gmail.com/
next prev parent reply other threads:[~2023-07-09 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 8:25 Zhang, Rui
2023-07-07 10:55 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-08 14:17 ` Thorsten Leemhuis
2023-07-09 13:27 ` Zhang, Rui [this message]
2023-07-09 16:28 ` Larry Finger
2023-07-09 16:31 ` Linus Torvalds
2023-07-09 18:07 ` Johannes Berg
2023-07-10 1:54 ` Zhang, Rui
2023-07-10 10:39 ` Linux regression tracking (Thorsten Leemhuis)
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=4153ce0aac6dc760a3a9c7204c5c9141b60839a4.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=Larry.Finger@lwfinger.net \
--cc=bagasdotme@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=golan.ben.ami@intel.com \
--cc=gregory.greenman@intel.com \
--cc=johannes.berg@intel.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mukesh.sisodiya@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=regressions@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
--cc=yaara.baruch@intel.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
all inboxes | Powered by JetHome®