From: Kalle Valo <kvalo@codeaurora.org>
To: Norbert Preining <norbert@preining.info>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
ilw@linux.intel.com
Subject: Re: IWL AC 8260, kernel 5.3.*, many kernel WARNING
Date: Fri, 27 Sep 2019 15:33:02 +0300 [thread overview]
Message-ID: <87blv5j4w1.fsf@tynnyri.adurom.net> (raw)
In-Reply-To: <20190927010452.b576njhcvgowasf3@burischnitzel.preining.info> (Norbert Preining's message of "Fri, 27 Sep 2019 10:04:52 +0900")
Norbert Preining <norbert@preining.info> writes:
> Dear all,
>
> (please cc)
>
> linux 5.3.1
> Debian/sid
> Thinkpad X260
> iwlwifi 0000:04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208
> iwlwifi 0000:04:00.0: loaded firmware version 36.8fd77bb3.0 op_mode iwlmvm
>
> since about 5.3.0 I get a lot of warnings in the syslog about iwlmvm.
>
> It starts with
> Sep 27 09:08:35 burischnitzel kernel: iwlwifi 0000:04:00.0: Microcode SW error detected. Restarting 0x82000000.
> Sep 27 09:08:35 burischnitzel kernel: iwlwifi 0000:04:00.0: Start IWL Error Log Dump:
> Sep 27 09:08:35 burischnitzel kernel: iwlwifi 0000:04:00.0: Status: 0x00000080, count: 6
> Sep 27 09:08:35 burischnitzel kernel: iwlwifi 0000:04:00.0: Loaded firmware version: 36.8fd77bb3.0
> Sep 27 09:08:35 burischnitzel kernel: iwlwifi 0000:04:00.0: 0x00000038 | BAD_COMMAND
> Sep 27 09:08:35 burischnitzel kernel: iwlwifi 0000:04:00.0: 0x000002F0 | trm_hw_status0
> Sep 27 09:08:35 burischnitzel kernel: iwlwifi 0000:04:00.0: 0x00000000 | trm_hw_status1
> ....
>
> after that
> Sep 27 09:08:35 burischnitzel kernel: ieee80211 phy0: Hardware restart was requested
> Sep 27 09:08:35 burischnitzel kernel: iwlwifi 0000:04:00.0: FW Error notification: type 0x00000000 cmd_id 0x05
> Sep 27 09:08:35 burischnitzel kernel: iwlwifi 0000:04:00.0: FW Error notification: seq 0x0030 service 0x00000005
> Sep 27 09:08:35 burischnitzel kernel: iwlwifi 0000:04:00.0: FW Error notification: timestamp 0x000000000037F460
> Sep 27 09:08:35 burischnitzel kernel: iwlwifi 0000:04:00.0: FW error in SYNC CMD GEO_TX_POWER_LIMIT
I'm guessing this should fix it:
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git/commit/?id=fddbfeece9c7882cc47754c7da460fe427e3e85b
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2019-09-27 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 1:04 Norbert Preining
2019-09-27 7:45 ` Paul Bolle
2019-09-27 12:33 ` Kalle Valo [this message]
2019-09-27 17:08 ` Norbert Preining
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=87blv5j4w1.fsf@tynnyri.adurom.net \
--to=kvalo@codeaurora.org \
--cc=ilw@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=norbert@preining.info \
/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
all inboxes | Powered by JetHome®