Bug 203649
| Summary: | iwlwifi: ASSERT EDC | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Chris van de Sande (cvandesande) |
| Component: | network-wireless | Assignee: | DO NOT USE - assign "network-wireless-intel" component instead (linuxwifi) |
| Status: | CLOSED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | P1 | ||
| Hardware: | Intel | ||
| OS: | Linux | ||
| Kernel Version: | 5.1.2-arch1-1-ARCH | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Attachments: | journal logs | ||
Forgot to cc linuxwifi@intel.com, adding now. What device do you have? *** This bug has been marked as a duplicate of bug 203315 *** |
Created attachment 282845 [details] journal logs Started experiencing this shortly after upgrading from linux-5.0.13.arch1-1-x86_64 to linux-5.1.2.arch1-1-x86_64. This is pretty easily reproducible. I run a Win10 VM with the disk image stored on an NFS volume. The connection to the NFS server is via Wifi, as one would expect booting a Windows VM puts a heavy load on the Wifi. Under normal circumstances Windows boots in 3-4mins. Since upgrading to kernel 5.1.2 I lose complete connectivity shortly after booting Windows 10, the error displayed in my dmesg is: May 15 22:35:16 nuc.opendmz.com kernel: iwlwifi 0000:02:00.0: Microcode SW error detected. Restarting 0x2000000. May 15 22:35:16 nuc.opendmz.com kernel: iwlwifi 0000:02:00.0: Start IWL Error Log Dump: May 15 22:35:16 nuc.opendmz.com kernel: iwlwifi 0000:02:00.0: Status: 0x00000100, count: 6 More logs attached. After the firmware crash, the Wifi will eventually recover, and NetworkManager will reconnect. After a few minutes, it will crash again. If I roll back to 5.0.13 or the LTS kernel I experience no errors whatsoever. Something has definitely changed with the 5.1.2 kernel.