Bug 204577

Summary: iwlwifi: 8260: firmware crashes repeatedly with LMAC ASSERT 0xEDC
Product: Drivers Reporter: Bob Vincent (pillarsdotnet)
Component: network-wirelessAssignee: Intel Linux Wireless (linuxwifi)
Severity: normal CC: linuxwifi, luca, pillarsdotnet
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 5.2.0-050200rc4-lowlatency Tree: Mainline
Regression: No
Attachments: dmesg output
firmware crash log

Description Bob Vincent 2019-08-14 13:31:58 UTC
Created attachment 284383 [details]
dmesg output

Folllowed directions on https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging

Attaching dmesg and crash log, encrypted to the developers, as directed.
Comment 1 Bob Vincent 2019-08-14 13:32:57 UTC
Created attachment 284385 [details]
firmware crash log
Comment 2 Bob Vincent 2019-08-14 13:36:28 UTC
Created attachment 284387 [details]
Comment 3 Bob Vincent 2019-08-14 13:42:11 UTC
From a user perspective, network traffic suddenly stops.  Typing "ip addr" shows no address associated with the wireless interface.  But NetworkManager still shows the device as connected.

Disconnecting / Reconnecting temporarily resolves the problem.

Starting a large number of connections (such as "apt-get update") usually causes the problem to reoccur.

I am running Ubuntu Disco with the lowlatency kernel:

Package: linux-lowlatency
Priority: optional
Section: kernel
Source: linux-meta
Origin: Ubuntu
Maintainer: Ubuntu Kernel Team <kernel-team@lists.ubuntu.com>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 15.4 kB
Depends: linux-image-lowlatency (=, linux-headers-lowlatency (=
Supported: 9m
Download-Size: 1,860 B
APT-Sources: http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages
Description: Complete lowlatency Linux kernel
 This package will always depend on the latest complete lowlatency Linux kernel
Comment 4 Bob Vincent 2019-08-14 13:44:36 UTC
bobvin@T560:~/Downloads/iwlwifi-bug-report ethtool -i wlp4s0 | grep firmware
firmware-version: 36.9f0a2d68.0
Comment 5 Luca Coelho 2019-08-20 13:14:26 UTC

*** This bug has been marked as a duplicate of bug 203315 ***