Hello all,
I'm experiencing an iwlwifi crash with Linux 4.18.9 in the following situation:
1) I'm suspending the laptop (into S3 sleep state)
2) Sometimes the laptop immediately wakes up again (as if a wake event fires)
3) In the immediate wakeup case iwlwifi crashes
I'm not sure if in step 2), iwlwifi or something else is causing the immediate
S3 wakeup after suspend.
Full dmesg is attached.
Please CC: me on any replies as I'm not subscribed to the mailing lists.
Thanks,
Udo
[40676.001160] PM: suspend exit
[40678.564050] iwlwifi 0000:03:00.0: Error sending REPLY_SCAN_ABORT_CMD: time out after 2000ms.
[40678.564066] iwlwifi 0000:03:00.0: Current CMD queue read_ptr 24 write_ptr 25
[40678.564106] iwlwifi 0000:03:00.0: Loaded firmware version: 18.168.6.1
[40678.564281] iwlwifi 0000:03:00.0: 0x00000000 | OK
[40678.564282] iwlwifi 0000:03:00.0: 0x00000000 | uPc
[40678.564283] iwlwifi 0000:03:00.0: 0x00000000 | branchlink1
[40678.564284] iwlwifi 0000:03:00.0: 0x00000000 | branchlink2
[40678.564285] iwlwifi 0000:03:00.0: 0x00000000 | interruptlink1
[40678.564286] iwlwifi 0000:03:00.0: 0x00000000 | interruptlink2
[40678.564287] iwlwifi 0000:03:00.0: 0x00000000 | data1
[40678.564288] iwlwifi 0000:03:00.0: 0x00000000 | data2
[40678.564289] iwlwifi 0000:03:00.0: 0x00000000 | line
[40678.564290] iwlwifi 0000:03:00.0: 0x00000000 | beacon time
[40678.564291] iwlwifi 0000:03:00.0: 0x00000000 | tsf low
[40678.564292] iwlwifi 0000:03:00.0: 0x00000000 | tsf hi
[40678.564293] iwlwifi 0000:03:00.0: 0x00000000 | time gp1
[40678.564294] iwlwifi 0000:03:00.0: 0x00000000 | time gp2
[40678.564295] iwlwifi 0000:03:00.0: 0x00000000 | time gp3
[40678.564296] iwlwifi 0000:03:00.0: 0x00000000 | uCode version
[40678.564297] iwlwifi 0000:03:00.0: 0x00000000 | hw version
[40678.564298] iwlwifi 0000:03:00.0: 0x00000000 | board version
[40678.564299] iwlwifi 0000:03:00.0: 0x00000000 | hcmd
[40678.564300] iwlwifi 0000:03:00.0: 0x00000000 | isr0
[40678.564301] iwlwifi 0000:03:00.0: 0x00000000 | isr1
[40678.564302] iwlwifi 0000:03:00.0: 0x00000000 | isr2
[40678.564303] iwlwifi 0000:03:00.0: 0x00000000 | isr3
[40678.564304] iwlwifi 0000:03:00.0: 0x00000000 | isr4
[40678.564305] iwlwifi 0000:03:00.0: 0x00000000 | isr_pref
[40678.564306] iwlwifi 0000:03:00.0: 0x00000000 | wait_event
[40678.564307] iwlwifi 0000:03:00.0: 0x00000000 | l2p_control
[40678.564308] iwlwifi 0000:03:00.0: 0x00000000 | l2p_duration
[40678.564309] iwlwifi 0000:03:00.0: 0x00000000 | l2p_mhvalid
[40678.564310] iwlwifi 0000:03:00.0: 0x00000000 | l2p_addr_match
[40678.564311] iwlwifi 0000:03:00.0: 0x00000000 | lmpm_pmg_sel
[40678.564311] iwlwifi 0000:03:00.0: 0x00000000 | timestamp
[40678.564312] iwlwifi 0000:03:00.0: 0x00000000 | flow_handler
[40678.564398] iwlwifi 0000:03:00.0: Start IWL Event Log Dump: nothing in log
[40678.564406] iwlwifi 0000:03:00.0: Command REPLY_RXON failed: FW Error
[40678.564407] iwlwifi 0000:03:00.0: Error clearing ASSOC_MSK on BSS (-5)
[40678.575927] ieee80211 phy0: Hardware restart was requested
[40678.582344] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[40678.876317] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[40678.970186] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
On Wed, 2018-09-26 at 06:50 +0200, Udo Steinberg wrote:
> Hello all,
Hi Udo,
> I'm experiencing an iwlwifi crash with Linux 4.18.9 in the following
> situation:
> 1) I'm suspending the laptop (into S3 sleep state)
> 2) Sometimes the laptop immediately wakes up again (as if a wake
> event fires)
> 3) In the immediate wakeup case iwlwifi crashes
>
> I'm not sure if in step 2), iwlwifi or something else is causing the
> immediate
> S3 wakeup after suspend.
>
> Full dmesg is attached.
>
> Please CC: me on any replies as I'm not subscribed to the mailing
> lists.
This is a known bug and unfortunately we cannot fix it anymore since
it's a pretty old HW and we don't really have the time to debug it.
For reference, this is the bugzilla entry:
https://bugzilla.kernel.org/show_bug.cgi?id=190281
From your dmesg, it seems that we are trying to cancel an ongoing scan
before going to suspend and that fails and causes the suspend process
to abort. This explains why it only happens sporadically -- i.e. a
scan must be running when you suspend.
If you're feeling adventurous, you could try to check the code that
sends the scan cancellation request when entering suspend and remove
that or move it earlier somehow. You don't seem to be using WoWLAN, so
not canceling the scan shouldn't hurt because the FW will be stopped
and started again anyway.
Good luck!
--
Cheers,
Luca.