[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87y2zsf9ps.fsf@depni.sinp.msu.ru>
Date: Sat, 17 Aug 2019 11:59:59 +0300
From: Serge Belyshev <belyshev@...ni.sinp.msu.ru>
To: Stuart Little <achirvasub@...il.com>
Cc: Johannes Berg <johannes.berg@...el.com>,
Emmanuel Grumbach <emmanuel.grumbach@...el.com>,
Luca Coelho <luciano.coelho@...el.com>,
kernel list <linux-kernel@...r.kernel.org>,
Intel Linux Wireless <linuxwifi@...el.com>,
linux-wireless@...r.kernel.org,
Haim Dreyfuss <haim.dreyfuss@...el.com>
Subject: Re: PROBLEM: 5.3.0-rc* causes iwlwifi failure
> 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@...el.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@...el.com>
Signed-off-by: Luca Coelho <luciano.coelho@...el.com>
is the culprit. (manually) reverting it on top of 5.3-rc4 makes
everything work again.
Powered by blists - more mailing lists