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] [day] [month] [year] [list]
Message-ID: <9c101e4016e73831c92d228ee90689e835a9d7d0.camel@coelho.fi>
Date:   Thu, 22 Aug 2019 17:27:39 +0300
From:   Luca Coelho <luca@...lho.fi>
To:     Chris Clayton <chris2553@...glemail.com>,
        Stuart Little <achirvasub@...il.com>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        linux-wireless <linux-wireless@...r.kernel.org>
Subject: Re: PROBLEM: 5.3.0-rc* causes iwlwifi failure

On Thu, 2019-08-22 at 09:59 +0100, Chris Clayton wrote:
> Thanks, Stuart.
> 
> On 18/08/2019 11:55, Stuart Little wrote:
> > On Sun, Aug 18, 2019 at 09:17:59AM +0100, Chris Clayton wrote:
> > > 
> > > On 17/08/2019 22:44, Stuart Little wrote:
> > > > After some private coaching from Serge Belyshev on git-revert I can confirm that reverting that commit atop the current tree resolves the issue (the wifi card scans for and finds networks just fine, no dmesg errors reported, etc.).
> > > > 
> > > 
> > > I've reported the "Microcode SW error detected" issue too, but, wrongly, only to LKML. I'll point that thread to this
> > > one. I've also been experiencing my network stopping working after suspend resume, but haven't got round to reporting
> > > that yet.
> > > 
> > > What was the git magic that you acquired to revert the patch, please?
> > > 
> 
> By following the advice below, I reverted 4fd445a2c855bbcab81fbe06d110e78dbd974a5b and using the resultant kernel I
> haven't seen the "Microcode SW error detected" again. I am, however, still experiencing the problem of my network not
> working after resume from suspend. I've reported it to LKML, so it can be followed there should anyone need/want to.

FWIW, we're tracking the iwlwifi bug here:

https://bugzilla.kernel.org/show_bug.cgi?id=204151

I'm thinking about how to solve this and will probably have a proper
patch by the end of the week.

--
Cheers,
Luca.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ