[Kernel-packages] [Bug 1728651] Re: System hangs after iwlwifi firmware crash
I'm now on 4.16.3 kernel, and while I haven't encountered freeze since moving to 4.15.13+, the WiFi connection becomes slow/unstable after few minutes. I'm not sure this is connected to the same part of code, or my HW meanwhile degraded a bit (did the 4.4 kernel work without a hitch? I may try to boot it for few days to see if it's HW issue, or still regression in kernel and wifi card driver). At this moment this is just a disclaimer to my post above, to make people not expect everything works perfectly after update of kernel, YMMV. For me it at least doesn't freeze any more. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1728651 Title: System hangs after iwlwifi firmware crash Status in linux-firmware package in Ubuntu: Confirmed Bug description: Since upgrading to Kubuntu 17.10 my HP EliteBook 820 G3 hangs at unpredictable times. I have experienced probably 20 hangs. Once the system is hung no mouse movement, NumLock toggle, VT switch, Ctrl+Alt+Del, SysRq keys, SSH attempts have any effect whatsoever. Any audio playing is stuck looping in the hardware buffer. The system is really stuck. Only the keyboard backlight is still responsive. The only correlation I have noticed is that the system only hangs if WiFi is enabled. This morning I experienced two hangs in ten minutes necessitating reboots. Having disabled WiFi the system has been stable since ~1100 (~5 hours). Often, I see a iwlwifi hardware reset in the logs before the system dies: /var/log/syslog:Oct 30 11:49:30 fry kernel: [ 6529.550751] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x8200. (apport has hopefully uploaded the full log, please lmk if not). Sometimes the message doesn't make it into the logs, and ext4 truncates the file at the next mount. There seems to be no correlation with any messages immediately before the wifi chip dies. It doesn't seem to matter whether I'm at home or at work. I have wired ethernet at work simultaneously with wifi, but the wifi provides IPv6 so I would imagine most traffic uses wifi, so it's hard to say whether there's any effect of the traffic load on the probability of failure. Here is a sample of the firmware load: /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.604743] iwlwifi :02:00.0: enabling device ( -> 0002) /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611790] iwlwifi :02:00.0: Direct firmware load for iwlwifi-8000C-33.ucode failed with error -2 /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611930] iwlwifi :02:00.0: Direct firmware load for iwlwifi-8000C-32.ucode failed with error -2 /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.620028] iwlwifi :02:00.0: loaded firmware version 31.532993.0 op_mode iwlmvm /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.650972] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) Any help appreciated. Thanks, Bruce ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CompositorRunning: None CurrentDesktop: KDE Date: Mon Oct 30 16:15:43 2017 DistUpgraded: 2017-10-15 14:47:25,517 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: kubuntu GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 520 [103c:807c] InstallationDate: Installed on 2016-09-09 (416 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP EliteBook 820 G3 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/kubuntu--vg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-15 (15 days ago) dmi.bios.date: 11/01/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.13 dmi.board.name: 807C dmi.board.vendor: HP dmi.board.version: KBC Version 85.74 dmi.chassis.asset.tag: 5CG6354JW5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.13:bd11/01/2016:svnHP:pnHPEliteBook820G3:pvr:rvnHP:rn807C:rvrKBCVersion85.74:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 820 G3 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
[Kernel-packages] [Bug 1728651] Re: System hangs after iwlwifi firmware crash
I did switch to mainline kernel 4.15.13 about 10 days back, and so far no single freeze happened. I did use this web page for instructions/etc: https://wiki.ubuntu.com/Kernel/MainlineBuilds I'm on KDE Neon distro, which is basically Ubuntu 16.04 LTS (with latests KDE packages on top of it). This was very annoying period of time (full 3 months?) on the 4.13 kernel with freezing at least 2-3 times per week, I wonder if there's not large enough portion of users affected to check if the update of kernel for ordinary users can be accelerated? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1728651 Title: System hangs after iwlwifi firmware crash Status in linux-firmware package in Ubuntu: Confirmed Bug description: Since upgrading to Kubuntu 17.10 my HP EliteBook 820 G3 hangs at unpredictable times. I have experienced probably 20 hangs. Once the system is hung no mouse movement, NumLock toggle, VT switch, Ctrl+Alt+Del, SysRq keys, SSH attempts have any effect whatsoever. Any audio playing is stuck looping in the hardware buffer. The system is really stuck. Only the keyboard backlight is still responsive. The only correlation I have noticed is that the system only hangs if WiFi is enabled. This morning I experienced two hangs in ten minutes necessitating reboots. Having disabled WiFi the system has been stable since ~1100 (~5 hours). Often, I see a iwlwifi hardware reset in the logs before the system dies: /var/log/syslog:Oct 30 11:49:30 fry kernel: [ 6529.550751] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x8200. (apport has hopefully uploaded the full log, please lmk if not). Sometimes the message doesn't make it into the logs, and ext4 truncates the file at the next mount. There seems to be no correlation with any messages immediately before the wifi chip dies. It doesn't seem to matter whether I'm at home or at work. I have wired ethernet at work simultaneously with wifi, but the wifi provides IPv6 so I would imagine most traffic uses wifi, so it's hard to say whether there's any effect of the traffic load on the probability of failure. Here is a sample of the firmware load: /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.604743] iwlwifi :02:00.0: enabling device ( -> 0002) /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611790] iwlwifi :02:00.0: Direct firmware load for iwlwifi-8000C-33.ucode failed with error -2 /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611930] iwlwifi :02:00.0: Direct firmware load for iwlwifi-8000C-32.ucode failed with error -2 /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.620028] iwlwifi :02:00.0: loaded firmware version 31.532993.0 op_mode iwlmvm /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.650972] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) Any help appreciated. Thanks, Bruce ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CompositorRunning: None CurrentDesktop: KDE Date: Mon Oct 30 16:15:43 2017 DistUpgraded: 2017-10-15 14:47:25,517 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: kubuntu GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 520 [103c:807c] InstallationDate: Installed on 2016-09-09 (416 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP EliteBook 820 G3 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/kubuntu--vg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-15 (15 days ago) dmi.bios.date: 11/01/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.13 dmi.board.name: 807C dmi.board.vendor: HP dmi.board.version: KBC Version 85.74 dmi.chassis.asset.tag: 5CG6354JW5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.13:bd11/01/2016:svnHP:pnHPEliteBook820G3:pvr:rvnHP:rn807C:rvrKBCVersion85.74:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 820 G3 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev:
[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0
I'm slightly affected, or maybe actually my kernel is "fixed" to correctly clear the error report even when device is not found internally (referring to the #27 brief analysis), as I do see the AER error in dmesg, periodically showing up, but only about once per couple of minutes. It's still beyond being acceptable for me, so I used the "pci=noaer" workaround, which stops the messages appearing. Error log: [ 487.987496] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 487.987503] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 487.987505] pcieport :00:1c.0: device [8086:a110] error status/mask=0001/2000 [ 487.987507] pcieport :00:1c.0:[ 0] Receiver Error (First) Further errors have the same 1c.0 address (Intel Corporation Wireless 3165) and details. Kernel version: 4.4.0-59-generic CPU: Intel(R) Core(TM) i5-6300HQ CPU @ 2.30GHz # lspci -vt -[:00]-+-00.0 Intel Corporation Sky Lake Host Bridge/DRAM Registers +-01.0-[01]00.0 NVIDIA Corporation GM107M [GeForce GTX 960M] +-02.0 Intel Corporation Skylake Integrated Graphics +-14.0 Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller +-14.2 Intel Corporation Sunrise Point-H Thermal subsystem +-16.0 Intel Corporation Sunrise Point-H CSME HECI #1 +-17.0 Intel Corporation Sunrise Point-H SATA Controller [AHCI mode] +-1c.0-[02]00.0 Intel Corporation Wireless 3165 +-1c.3-[03]00.0 Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller +-1f.0 Intel Corporation Sunrise Point-H LPC Controller +-1f.2 Intel Corporation Sunrise Point-H PMC +-1f.3 Intel Corporation Sunrise Point-H HD Audio \-1f.4 Intel Corporation Sunrise Point-H SMBus MSI Notebook GP62 6QF-678XCZ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Note: Current workaround is to add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A
