From: Friso Smit <fw.smit01@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: iwlwifi: failed to load firmware chunk
Date: Tue, 13 Apr 2021 18:05:49 +0200 [thread overview]
Message-ID: <aef9af7e-9a5b-4eb4-e130-e5ee11d76891@gmail.com> (raw)
In-Reply-To: <b606a193-3e4d-cdd7-a2e4-c5b801e2f8fc@gmail.com>
Okay, this is weird. Right now it's still messed up in Windows, but not
anymore in Linux (even though it started while running linux). Dmesg
currently doesn't show any errors for iwlwifi. Does anyone have an idea
what part of the wifi chip could be broken here (driver, firmware, etc.)?
On 4/11/21 10:56 PM, Friso Smit wrote:
> On 4/11/21 10:11 PM, Chris Murphy wrote:
>> On Sun, Apr 11, 2021 at 2:24 AM Friso Smit <fw.smit01@gmail.com> wrote:
>>> Hi,
>>>
>>> After upgrading to linux 5.11.12.arch1-1 I suddenly had no wifi
>>> connection. I immediately tried downgrading again, but to no avail.
>> Did only kernel version change? 5.11.12 has one iwlwifi related commit:
>>
>> commit 6159f947fb047fd8ecbfbcbcc86a8337e801bd10
>> iwlwifi: pcie: don't disable interrupts for reg_lock
>>
> It's not the only thing that changed, but this one stood out to me as
> the possible cause. Some other things to note are that I sometimes
> have to force shutdown my laptop, because of a long time issue in
> nouveau. I don't know if this can cause these kinds of issues. And I
> want to stress as well that the issue persisted even on another
> operating system, so something must have been thoroughly messed up
> somehow.
>
> Here's a full list of (Arch) packages that were upgraded:
>
> expat (2.2.10-2 -> 2.3.0-1)
> glib2 (2.68.0-5 -> 2.68.1-1)
> libcups (1:2.3.3op2-1 -> 1:2.3.3op2-2)
> cups (1:2.3.3op2-1 -> 1:2.3.3op2-2)
> dleyna-core (0.6.0+2+g1c6853f-2 -> 0.7.0-1)
> dleyna-connector-dbus (0.3.0-3 -> 0.4.0-1)
> libdrm (2.4.104-1 -> 2.4.105-1)
> mesa (21.0.1-1 -> 21.0.2-1)
> dleyna-renderer (0.6.0-4 -> 0.7.0-1)
> dleyna-server (0.6.0+2+geb895ae-2 -> 0.7.0-1)
> gdk-pixbuf2 (2.42.4-1 -> 2.42.6-1)
> geoclue (2.5.7-2 -> 2.5.7-3)
> glib2-docs (2.68.0-5 -> 2.68.1-1)
> gtk-update-icon-cache (1:4.2.0-2 -> 1:4.2.0-3)
> gtk3 (1:3.24.28-1 -> 1:3.24.28-2)
> lib32-expat (2.2.10-1 -> 2.3.0-2)
> lib32-glib2 (2.68.0-5 -> 2.68.1-1)
> lib32-gdk-pixbuf2 (2.42.4-1 -> 2.42.6-1)
> lib32-libva-mesa-driver (21.0.1-2 -> 21.0.2-1)
> lib32-mesa (21.0.1-2 -> 21.0.2-1)
> lib32-vulkan-intel (21.0.1-2 -> 21.0.2-1)
> libmwaw (0.3.17-1 -> 0.3.18-1)
> libva-mesa-driver (21.0.1-1 -> 21.0.2-1)
> linux (5.11.11.arch1-1 -> 5.11.12.arch1-1)
> linux-headers (5.11.11.arch1-1 -> 5.11.12.arch1-1)
> lua (5.4.2-1 -> 5.4.3-1)
> mesa-vdpau (21.0.1-1 -> 21.0.2-1)
> meson (0.57.1-1 -> 0.57.2-1)
> npm (7.8.0-1 -> 7.9.0-1)
> opera-ffmpeg-codecs (88.0.4324.192-1 -> 89.0.4389.90-1)
> proj (6.3.2-1 -> 8.0.0-1)
> qt5-base (5.15.2+kde+r171-2 -> 5.15.2+kde+r171-3)
> wlroots (0.12.0-1 -> 0.13.0-1)
> sway (1:1.5.1-2 -> 1:1.6-1)
> vulkan-headers (1:1.2.173-1 -> 1:1.2.174-1)
> vulkan-intel (21.0.1-1 -> 21.0.2-1)
> wine (6.5-2 -> 6.6-1)
> wine-mono (6.0.0-1 -> 6.1.1-1)
>
next prev parent reply other threads:[~2021-04-13 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-11 8:24 iwlwifi: failed to load firmware chunk Friso Smit
2021-04-11 20:11 ` Chris Murphy
2021-04-11 20:56 ` Friso Smit
2021-04-13 16:05 ` Friso Smit [this message]
2021-05-02 12:14 ` Friso Smit
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=aef9af7e-9a5b-4eb4-e130-e5ee11d76891@gmail.com \
--to=fw.smit01@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lists@colorremedies.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;
as well as URLs for NNTP newsgroup(s).