From: Luca Coelho <luca@coelho.fi>
To: Chris Clayton <chris2553@googlemail.com>,
Stuart Little <achirvasub@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: PROBLEM: 5.3.0-rc* causes iwlwifi failure
Date: Thu, 22 Aug 2019 17:27:39 +0300 [thread overview]
Message-ID: <9c101e4016e73831c92d228ee90689e835a9d7d0.camel@coelho.fi> (raw)
In-Reply-To: <5e3ed328-7eea-f112-45d7-4ddee04c4b77@googlemail.com>
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.
next prev parent reply other threads:[~2019-08-22 14:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190817214448.GB1070 () chirva-slack ! chirva-slack>
2019-08-18 8:17 ` PROBLEM: 5.3.0-rc* causes iwlwifi failure Chris Clayton
2019-08-18 10:55 ` Stuart Little
2019-08-22 8:59 ` Chris Clayton
2019-08-22 14:27 ` Luca Coelho [this message]
2019-08-17 4:12 Stuart Little
2019-08-17 5:30 ` Stuart Little
2019-08-17 8:59 ` Serge Belyshev
2019-08-17 13:45 ` Stuart Little
2019-08-17 21:44 ` Stuart Little
2019-08-20 10:45 ` Luciano Coelho
2019-08-20 23:37 ` Stuart Little
2019-08-21 5:04 ` Luciano Coelho
2019-08-21 6:49 ` Sedat Dilek
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=9c101e4016e73831c92d228ee90689e835a9d7d0.camel@coelho.fi \
--to=luca@coelho.fi \
--cc=achirvasub@gmail.com \
--cc=chris2553@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.