linux-kernel - Re: [regression] iwlwifi driver broken on Intel 3165 network card

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <cb081b034d9283284c4754e62c083567b516d68b.camel@sipsolutions.net>
Date:   Wed, 12 Jul 2023 12:39:49 +0200
From:   Johannes Berg <johannes@...solutions.net>
To:     Linux regressions mailing list <regressions@...ts.linux.dev>,
        Aloka Dixit <quic_alokad@...cinc.com>,
        John Crispin <john@...ozen.org>
Cc:     Aditya Kumar Singh <quic_adisi@...cinc.com>,
        linux-wireless@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [regression] iwlwifi driver broken on Intel 3165 network card

On Wed, 2023-07-12 at 11:59 +0200, Linux regression tracking (Thorsten
Leemhuis) wrote:
> 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.

That indeed is odd as well, but from the log it looks like r8169 is
actually present on the machine, so perhaps this messes with some PCI
bugs configuration badly enough? It looks harmless enough, but who
knows.

Anyway, thanks for letting me know.

johannes