From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Johannes Berg <johannes@sipsolutions.net>,
Linux regressions mailing list <regressions@lists.linux.dev>,
Aloka Dixit <quic_alokad@quicinc.com>,
John Crispin <john@phrozen.org>
Cc: Aditya Kumar Singh <quic_adisi@quicinc.com>,
linux-wireless@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [regression] iwlwifi driver broken on Intel 3165 network card
Date: Wed, 12 Jul 2023 11:59:25 +0200 [thread overview]
Message-ID: <c71e376e-4e44-a1b3-6feb-2ed1ba7d325b@leemhuis.info> (raw)
In-Reply-To: <047c7bdc8057175f2bb78981a5f1a1aa6b493153.camel@sipsolutions.net>
On 10.07.23 17:02, Johannes Berg wrote:
> On Mon, 2023-07-10 at 10:32 +0200, Linux regression tracking (Thorsten
> Leemhuis) wrote:
>> Hi, Thorsten here, the Linux kernel's regression tracker.
>>
>> I noticed a regression report in bugzilla.kernel.org. As many (most?)
>> kernel developers don't keep an eye on it, I decided to forward it by mail.
>>
>> Aloka Dixit, apparently it's cause by a change of yours: bd54f3c2907
>> ("wifi: mac80211: generate EMA beacons in AP mode") [v6.4-rc1]
>>
>
> That bisect result seems unlikely to be correct. Those changes are in
> "how to get beacons" (in AP mode) which isn't even used in client mode
> here.
You where right, the second bisect resulted in a different outcome.
Currently looks like 5fc3f6c90cc ("r8169: consolidate disabling ASPM
before EPHY access") [v6.4-rc1] is the culprit; this is somewhat odd as
well, but confirmed partially, as blacklisting r8169 apparently fixes
the issue. I nevertheless asked the reporter to recheck by reverting
that commit. Once that happened I'll notify the author of 5fc3f6c90cc.
Thx again and sorry for the noise.
BTW, in case anyone wants details, see:
https://bugzilla.kernel.org/show_bug.cgi?id=217635
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.
next prev parent reply other threads:[~2023-07-12 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 8:32 Linux regression tracking (Thorsten Leemhuis)
2023-07-10 15:02 ` Johannes Berg
2023-07-12 9:59 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-07-12 10:39 ` Johannes Berg
2023-07-12 11:24 ` [regression] r8169 ASPM changes broke iwlwifi driver for Intel 3165 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=c71e376e-4e44-a1b3-6feb-2ed1ba7d325b@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=johannes@sipsolutions.net \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_adisi@quicinc.com \
--cc=quic_alokad@quicinc.com \
--cc=regressions@lists.linux.dev \
/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®