From: Jordan Glover <Golden_Miller83@protonmail.ch>
To: Luca Coelho <luca@coelho.fi>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linuxwifi@intel.com" <linuxwifi@intel.com>
Subject: Re: [BUG] Microcode SW error detected
Date: Wed, 06 Feb 2019 13:20:54 +0000 [thread overview]
Message-ID: <NR7zW4fbUVRT2M-BPgYpYxw3vAnf4ljS4lveqH_pNztV_jTFnS85yO3kRbEcLzB8rZhwq797ENsyVXJoWARQ3ydzhPF9yMyTqivEBfXIwUU=@protonmail.ch> (raw)
In-Reply-To: <1592d4db90b6cee8bc794bcbce06a14fd5226b16.camel@coelho.fi>
On Wednesday, February 6, 2019 7:08 AM, Luca Coelho <luca@coelho.fi> wrote:
>
> This seems to be related to this bugzilla:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=202397
>
> Can you please comment on that report stating that you are experiencing
> the same (or something similar)?
>
> Thanks!
>
>
> Cheers,
> Luca.
Thank you for the reply.
It may be similar problem but I'm not getting
"NULL pointer dereference error" as described in linked issue.
I already created separate bug report at:
https://bugzilla.kernel.org/show_bug.cgi?id=202513
I think this issue may be caused by firmware update for intel 8000
series which could be buggy itself or just uncovered bugs in iwlwifi
driver:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=8707ef3313ee0f6737683c93aa2cb1dff6483643
Downgrading linux-firmware package to version before that commit seems
to make this issue go away.
Jordan
prev parent reply other threads:[~2019-02-06 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 14:24 [BUG] Microcode SW error detected Jordan Glover
2019-02-06 6:08 ` Luca Coelho
2019-02-06 13:20 ` Jordan Glover [this message]
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='NR7zW4fbUVRT2M-BPgYpYxw3vAnf4ljS4lveqH_pNztV_jTFnS85yO3kRbEcLzB8rZhwq797ENsyVXJoWARQ3ydzhPF9yMyTqivEBfXIwUU=@protonmail.ch' \
--to=golden_miller83@protonmail.ch \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=luca@coelho.fi \
/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.