linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Clayton <chris2553@googlemail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: iwlwifi: microcode SW error detected
Date: Sun, 18 Aug 2019 09:21:54 +0100	[thread overview]
Message-ID: <cdf38da2-def1-cf0d-2d35-f31cc8fe122a@googlemail.com> (raw)
In-Reply-To: <42e782e0-78be-b3d4-d222-1a75df35b078@googlemail.com>



On 17/08/2019 08:19, Chris Clayton wrote:
> Hi.
> 
> I just found the following error in the output from dmesg.
> 
> [ 4023.460058] iwlwifi 0000:02:00.0: Microcode SW error detected. Restarting 0x0.

Since reporting, I've found that this problem is being explored in the thread that starts at
https://marc.info/?l=linux-kernel&m=156601519111113.

Chris

  reply	other threads:[~2019-08-18  8:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-17  7:19 iwlwifi: microcode SW error detected Chris Clayton
2019-08-18  8:21 ` Chris Clayton [this message]
2019-08-20  8:29   ` Chris Clayton

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=cdf38da2-def1-cf0d-2d35-f31cc8fe122a@googlemail.com \
    --to=chris2553@googlemail.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).