[Touch-packages] [Bug 2053288] [NEW] systemd-networkd IPv6 default routes dropped under load, don't recover
Public bug reported: Ubuntu 22.04.3 LTS systemd 249.11-0ubuntu3.12 systemd issue tracker says this version is too old to report upstream and I should report to downstream bug tracker. IPv6 default routes are getting lost and not renewed. We're using IPv6 RA to find default routes for our servers and desktops. The RAs come from HP/Aruba routers and have a short lifetime of about 46s. Occasionally, we will see the default routes get dropped. Despite receiving RAs, the default routes don't get recreated. The most recent machine to be affected had a user running an excessively large job (load average 157). This is the state of the network when the machine is working: ```sh # ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 2c:ea:7f:56:9a:66 brd ff:ff:ff:ff:ff:ff altname enp4s0f0 3: eno2: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 2c:ea:7f:56:9a:66 brd ff:ff:ff:ff:ff:ff permaddr 2c:ea:7f:56:9a:67 altname enp4s0f1 4: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 2c:ea:7f:56:9a:66 brd ff:ff:ff:ff:ff:ff inet xxx.xxx.202.112/24 brd 129.215.202.255 scope global bond0 valid_lft forever preferred_lft forever inet6 :xxx:xxx:202:2eea:7fff:fe56:9a66/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 2591994sec preferred_lft 604794sec inet6 fe80::2eea:7fff:fe56:9a66/64 scope link valid_lft forever preferred_lft forever # ip -6 r ::1 dev lo proto kernel metric 256 pref medium :xxx:xxx:202::/64 dev bond0 proto ra metric 1024 expires 2591998sec pref medium fe80::/64 dev bond0 proto kernel metric 256 pref medium default proto ra metric 1024 expires 28sec pref medium nexthop via fe80::609:73ff:fe48:c000 dev bond0 weight 1 nexthop via fe80::609:73ff:fe48:6500 dev bond0 weight 1 ``` When the problem arises, the last three lines disappear. `tcpdump icmp6` shows RAs being received but networkd doesn't create the routes in the kernel. The machine keeps its IPv6 addresses, but without a default route it can't make any IPv6 connections or answer incoming IPv6 connections. Sorry, reproduction method is unclear. Here's a best guess: 1. Configure networkd using netplan: ```yaml --- network: bonds: bond0: addresses: - xxx.xxx.202.112/24 dhcp4: false interfaces: - eth0 - eth1 macaddress: 2C:EA:7F:56:9A:66 parameters: mii-monitor-interval: 1 mode: active-backup ethernets: eth0: dhcp4: false match: macaddress: 2C:EA:7F:56:9A:66 eth1: dhcp4: false match: macaddress: 2C:EA:7F:56:9A:67 renderer: networkd version: 2 ``` 2. Load the machine, or just wait. Possibly this is related to packets being dropped, but I would expect the system to recover once the load is removed. 3. Note the lack of IPv6 connectivity, inability to log in with ssh, etc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2053288 Title: systemd-networkd IPv6 default routes dropped under load, don't recover Status in systemd package in Ubuntu: New Bug description: Ubuntu 22.04.3 LTS systemd 249.11-0ubuntu3.12 systemd issue tracker says this version is too old to report upstream and I should report to downstream bug tracker. IPv6 default routes are getting lost and not renewed. We're using IPv6 RA to find default routes for our servers and desktops. The RAs come from HP/Aruba routers and have a short lifetime of about 46s. Occasionally, we will see the default routes get dropped. Despite receiving RAs, the default routes don't get recreated. The most recent machine to be affected had a user running an excessively large job (load average 157). This is the state of the network when the machine is working: ```sh # ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 2c:ea:7f:56:9a:66 brd ff:ff:ff:ff:ff:ff altname enp4s0f0 3: eno2: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 2c:ea:7f:56:9a:66 brd ff:ff:ff:ff:ff:ff permaddr 2c:ea:7f:56:9a:67
[Touch-packages] [Bug 1992235] [NEW] Xorg freeze
Public bug reported: Updated to 22.10 beta last week. When I return after screensaver activation, the display freezes. Sometimes the greeter fades in a little bit, sometimes it is just the background image. Every time, I can move the mouse and the cursor changes when hovering over the password box (or where it would have been). I can type my password and the session unlocks. I know this because the greeter process is gone, and the mouse cursor now changes as if it were my desktop (input boxes, buttons, etc) but the display still has never updated. This has happened about 5 times now, but reproducing it could be hard because it only seems to happen after an idle period when the screen locks itself. Manually locking/unlocking the screen works fine. Switching off the monitors with "xset dpms force off" also doesn't seem to trigger it. There doesn't appear to be anything useful in the log files, but I think apport has attached them anyway. Happy to do any debugging necessary. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.0.0-06-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Sat Oct 8 11:12:25 2022 DistUpgraded: 2022-10-05 00:54:56,716 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi/9904, 5.15.0-48-generic, x86_64: installed backport-iwlwifi/9904, 5.19.0-18-generic, x86_64: installed backport-iwlwifi/9904, 6.0.0-06-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:8760] InstallationDate: Installed on 2021-06-24 (470 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP EliteBook 845 G7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-06-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to kinetic on 2022-10-04 (3 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 10.0 dmi.bios.vendor: HP dmi.bios.version: S77 Ver. 01.10.00 dmi.board.name: 8760 dmi.board.vendor: HP dmi.board.version: KBC Version 07.3A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 7.58 dmi.modalias: dmi:bvnHP:bvrS77Ver.01.10.00:bd07/15/2022:br10.0:efr7.58:svnHP:pnHPEliteBook845G7NotebookPC:pvr:rvnHP:rn8760:rvrKBCVersion07.3A.00:cvnHP:ct10:cvr:sku8VZ07AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 845 G7 Notebook PC dmi.product.sku: 8VZ07AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.112-3ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang freeze kinetic kubuntu third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1992235 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Updated to 22.10 beta last week. When I return after screensaver activation, the display freezes. Sometimes the greeter fades in a little bit, sometimes it is just the background image. Every time, I can move the mouse and the cursor changes when hovering over the password box (or where it would have been). I can type my password and the session unlocks. I know this because the greeter process is gone, and the mouse cursor now changes as if it were my desktop (input boxes, buttons, etc) but the display still has never updated. This has happened about 5 times now, but reproducing it could be hard because it only seems to happen after an idle period when the screen locks itself. Manually locking/unlocking the screen works fine. Switching off the monitors with "xset dpms force off" also doesn't seem to trigger it. There doesn't appear to be anything useful in the log files, but I think apport has attached them anyway. Happy to do any debugging necessary. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 Uname: Linux
[Touch-packages] [Bug 1251178] Re: qdbus and qdbusviewer crash with "No such file or directory"
The solution is indeed to install the qt5-default package. Maybe this package could be added as a dependency in newer releases? There is also perhaps an upstream bug where qtchooser could try the "other" qt version if one fails. (I had installed qdbus5, and qtchooser was trying qdbus4, which was not installed or wanted.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1251178 Title: qdbus and qdbusviewer crash with "No such file or directory" Status in qt4-x11 package in Ubuntu: Confirmed Status in qtchooser package in Ubuntu: Confirmed Bug description: Release: Ubuntu 13.10 (32-bit) Package versions: qtdbus 4:4.8.4+dfsg-0ubuntu18 qtchooser 26-3ubuntu2 Expected behavior: The `qdbus` program runs, as does the related program `qdbusviewer`. Actual behavior: If I run the `qdbus` program, it always crashes: user@host:~$ qdbus --help qdbus: could not exec '/usr/lib/i386-linux-gnu/qt5/bin/qdbus': No such file or directory The `qdbus` executable is actually: user@host:~$ ls --full-time $(which qdbus) lrwxrwxrwx 1 root root 9 2013-08-07 14:48:40.0 + /usr/bin/qdbus -> qtchooser Note that `/usr/lib/i386-linux-gnu/qt4/bin/qdbus` exists and seems to work if I invoke it directly. There's a `qdbus-qt5` package in the universe repository. It was not pulled in as a dependency, but manually installing it fixes the issue. Therefore it's either a packaging error or a bug in qtchooser. A similar thing happens if I run `qdbusviewer`: user@host:~$ qdbusviewer qdbusviewer: could not exec '/usr/lib/i386-linux-gnu/qt5/bin/qdbusviewer': No such file or directory except that installing `qdbus-qt5` doesn't fix the issue. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: qdbus 4:4.8.4+dfsg-0ubuntu18 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Thu Nov 14 09:34:24 2013 MarkForUpload: True SourcePackage: qt4-x11 UpgradeStatus: Upgraded to saucy on 2013-10-23 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1251178/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728651] Re: System hangs after iwlwifi firmware crash
** Package changed: xorg (Ubuntu) => linux-firmware (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1728651 Title: System hangs after iwlwifi firmware crash Status in linux-firmware package in Ubuntu: New 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: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1728651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1728651] Re: System hangs after iwlwifi firmware crash
I don't easily see the firmware hang message in the attached files, so I'm pasting it here: Microcode SW error detected. Restarting 0x8200. Start IWL Error Log Dump: Status: 0x0200, count: 6 0x0038 | BAD_COMMAND 0x0220 | trm_hw_status0 0x | trm_hw_status1 0x00010040 | branchlink2 0x00028DA6 | interruptlink1 0x | interruptlink2 0x009A001C | data1 0x029B | data2 0x009B | data3 0x31818996 | beacon time 0xDA54AE68 | tsf low 0x0927 | tsf hi 0x | time gp1 0x34A281CF | time gp2 0x0001 | uCode revision type 0x001F | uCode version major 0x00082201 | uCode version minor 0x0201 | hw version 0x00489008 | board version 0x009A001C | hcmd 0x24022080 | isr0 0x0100 | isr1 0x2820180A | isr2 0x00417CC0 | isr3 0x | isr4 0x0099014E | last cmd Id 0x | wait_event 0x4288 | l2p_control 0x00018030 | l2p_duration 0x03BF | l2p_mhvalid 0x00E7 | l2p_addr_match 0x000D | lmpm_pmg_sel 0x15062149 | timestamp 0xE0F0 | flow_handler Start IWL Error Log Dump: Status: 0x0200, count: 7 0x0070 | ADVANCED_SYSASSERT 0x | umac branchlink1 0xC0086B70 | umac branchlink2 0xC00844E0 | umac interruptlink1 0xC00844E0 | umac interruptlink2 0x0800 | umac data1 0xC00844E0 | umac data2 0xDEADBEEF | umac data3 0x001F | umac major 0x00082201 | umac minor 0xC088627C | frame pointer 0xC088627C | stack pointer 0x009A001C | last host cmd 0x | isr status reg FW Error notification: type 0x cmd_id 0x1C FW Error notification: seq 0x009A service 0x001C FW Error notification: timestamp 0x34A1CCC1 (I trimmed words from the start of each line like: "Oct 23 16:31:59 fry kernel: [29533.463611] iwlwifi :02:00.0:") -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1728651 Title: System hangs after iwlwifi firmware crash Status in xorg package in Ubuntu: New 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]
[Touch-packages] [Bug 1728651] [NEW] System hangs after iwlwifi firmware crash
Public bug reported: 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: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful fonts kubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1728651 Title: System hangs after iwlwifi firmware crash Status in xorg package in Ubuntu: New 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
