From: Serge Belyshev <belyshev@depni.sinp.msu.ru>
To: Stuart Little <achirvasub@gmail.com>
Cc: Johannes Berg <johannes.berg@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Luca Coelho <luciano.coelho@intel.com>,
kernel list <linux-kernel@vger.kernel.org>,
Intel Linux Wireless <linuxwifi@intel.com>,
linux-wireless@vger.kernel.org,
Haim Dreyfuss <haim.dreyfuss@intel.com>
Subject: Re: PROBLEM: 5.3.0-rc* causes iwlwifi failure
Date: Sat, 17 Aug 2019 11:59:59 +0300 [thread overview]
Message-ID: <87y2zsf9ps.fsf@depni.sinp.msu.ru> (raw)
In-Reply-To: <20190817041258.GA1641@chirva-slack.chirva-slack>
> I am on an Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz running Linux
> x86_64 (Slackware), with a custom-compiled 5.3.0-rc4 (.config
> attached).
>
> I am using the Intel wifi adapter on this machine:
>
> 02:00.0 Network controller: Intel Corporation Device 24fb (rev 10)
>
> with the iwlwifi driver. I am attaching the output to 'lspci -vv -s
> 02:00.0' as the file device-info.
>
> All 5.3.0-rc* versions I have tried (including rc4) cause multiple
> dmesg iwlwifi-related errors (dmesg attached). Examples:
>
> iwlwifi 0000:02:00.0: Failed to get geographic profile info -5
> iwlwifi 0000:02:00.0: Microcode SW error detected. Restarting 0x82000000
> iwlwifi 0000:02:00.0: 0x00000038 | BAD_COMMAND
>
I have my logs filled with similar garbage throughout 5.3-rc*. Also
since 5.3-rcsomething not only it WARNS in dmesg about firmware failure,
but completely stops working after suspend/resume cycle.
It looks like that:
commit 4fd445a2c855bbcab81fbe06d110e78dbd974a5b
Author: Haim Dreyfuss <haim.dreyfuss@intel.com>
Date: Thu May 2 11:45:02 2019 +0300
iwlwifi: mvm: Add log information about SAR status
Inform users when SAR status is changing.
Signed-off-by: Haim Dreyfuss <haim.dreyfuss@intel.com>
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
is the culprit. (manually) reverting it on top of 5.3-rc4 makes
everything work again.
next prev parent reply other threads:[~2019-08-17 9:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-17 4:12 Stuart Little
2019-08-17 5:30 ` Stuart Little
2019-08-17 8:59 ` Serge Belyshev [this message]
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
[not found] ` <20191208203810.GA2920@system76-pc.localdomain>
2019-12-11 5:20 ` PROBLEM: iwlwifi in 5.4 does not load firmware for A.C.
[not found] ` <20191222224207.GA2408@system76-pc.localdomain>
[not found] ` <ec9092a28196f24c39051b89f9dc87b40942b6de.camel@intel.com>
[not found] ` <20191223125742.GA2586@system76-pc.localdomain>
2019-12-23 13:01 ` PROBLEM: iwlwifi in 5.4 does not load firmware for Intel device 9560 Luciano Coelho
[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
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=87y2zsf9ps.fsf@depni.sinp.msu.ru \
--to=belyshev@depni.sinp.msu.ru \
--cc=achirvasub@gmail.com \
--cc=emmanuel.grumbach@intel.com \
--cc=haim.dreyfuss@intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=luciano.coelho@intel.com \
/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®