[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aXjBnu8MAg5ly76z@debian.local>
Date: Tue, 27 Jan 2026 13:46:06 +0000
From: Chris Bainbridge <chris.bainbridge@...il.com>
To: "Korenblit, Miriam Rachel" <miriam.rachel.korenblit@...el.com>
Cc: "kvalo@...nel.org" <kvalo@...nel.org>,
"Berg, Johannes" <johannes.berg@...el.com>,
"benjamin@...solutions.net" <benjamin@...solutions.net>,
"gustavoars@...nel.org" <gustavoars@...nel.org>,
"linux-intel-wifi@...el.com" <linux-intel-wifi@...el.com>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH] Revert "wifi: iwlwifi: trans: remove STATUS_SUSPENDED"
On Tue, Jan 27, 2026 at 01:22:06PM +0000, Korenblit, Miriam Rachel wrote:
>
>
> > -----Original Message-----
> > From: Chris Bainbridge <chris.bainbridge@...il.com>
> > Sent: Tuesday, January 27, 2026 2:22 PM
> > To: Korenblit, Miriam Rachel <miriam.rachel.korenblit@...el.com>
> > Cc: kvalo@...nel.org; Berg, Johannes <johannes.berg@...el.com>;
> > benjamin@...solutions.net; gustavoars@...nel.org; linux-intel-wifi@...el.com;
> > linux-wireless@...r.kernel.org; netdev@...r.kernel.org; linux-
> > kernel@...r.kernel.org; stable@...r.kernel.org
> > Subject: Re: [PATCH] Revert "wifi: iwlwifi: trans: remove STATUS_SUSPENDED"
> >
> > On Tue, Jan 27, 2026 at 05:05:31AM +0000, Korenblit, Miriam Rachel wrote:
> > >
> > > Just making sure: have you been able to reproduce the assert
> > (ADVANCED_SYSASSERT in the log), and then the panic didn't happen?
> >
> > Yes, the ADVANCED_SYSASSERT was logged but there was no subsequent null
> > pointer dereference.
> >
> > > If yes, please test the attached patch, which is supposed to fix the assert itself.
> > With this, you are not even supposed to see an assert.
> >
> > I ran this through 15 suspend/resume cycles with network traffic. The
> > ADVANCED_SYSASSERT did not occur, so it looks like the patch does fix the
> > SYSASSERT. There was a warning logged once out of the 15 cycles:
> >
> > I think that this is probably a different bug though - checking previous logs with
> > journalctl, I see the same warning occurred once with 6.17.0-06871-
> > gf79e772258df which predates the "remove STATUS_SUSPENDED"
> > commit.
>
> Thanks for the help!
>
> Regarding the warning, please open Bugzilla ticket for that
>
> Miri
Sure, ticket is https://bugzilla.kernel.org/show_bug.cgi?id=221017
Powered by blists - more mailing lists