[Kernel-packages] [Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout
** Attachment added: "frozendmesg.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1821194/+attachment/5248375/+files/frozendmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post
[Kernel-packages] [Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout
The directory /var/crash is empty. ** Attachment added: "frozenjournal.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1821194/+attachment/5248393/+files/frozenjournal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: http
[Kernel-packages] [Bug 1821194] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248416/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchp
[Kernel-packages] [Bug 1821194] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248418/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@list
[Kernel-packages] [Bug 1821194] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248421/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-package
[Kernel-packages] [Bug 1821194] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248417/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packa
[Kernel-packages] [Bug 1821194] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248419/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launc
[Kernel-packages] [Bug 1821194] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248422/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1821194] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248420/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launc
[Kernel-packages] [Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout
ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 3364 F pulseaudio /dev/snd/controlC0: u 3364 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-gambit-eagle-kylin+X45 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-22 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Inspiron 3670 NonfreeKernelModules: nvidia_modeset nvidia Package: nvidia-graphics-drivers-410 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1029-oem.efi.signed root=UUID=baab0cd6-ff41-4a5b-93a0-c52386e24070 ro mem_sleep_default=deep quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1029.34-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1029-oem N/A linux-backports-modules-4.15.0-1029-oem N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-1029-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/04/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.7.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.7.2:bd03/04/2019:svnDellInc.:pnInspiron3670:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3670 dmi.sys.vendor: Dell Inc. ** Tags added: apport-collected -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18
[Kernel-packages] [Bug 1821194] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248415/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@list
[Kernel-packages] [Bug 1821194] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248427/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-package
[Kernel-packages] [Bug 1821194] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248424/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-p
[Kernel-packages] [Bug 1821194] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248432/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@
[Kernel-packages] [Bug 1821194] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248431/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.lau
[Kernel-packages] [Bug 1821194] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248430/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.lau
[Kernel-packages] [Bug 1821194] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248429/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-410 package in Ubuntu: Incomplete Bug description: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd- logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@li
[Kernel-packages] [Bug 1834603] Re: SRU request: Include the 430 driver in Ubuntu 18.04
Tried version 430.26-0ubuntu0.18.04.2, it works great. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1834603 Title: SRU request: Include the 430 driver in Ubuntu 18.04 Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in nvidia-graphics-drivers-430 package in Ubuntu: New Status in nvidia-settings package in Ubuntu: In Progress Status in nvidia-graphics-drivers-430 source package in Xenial: In Progress Status in nvidia-settings source package in Xenial: In Progress Status in nvidia-graphics-drivers-430 source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] The nvidia packages in Ubuntu 18.04 do not support recent NVIDIA GPUs. ([10de:2191][10de:1f91][10de:1c91] [Test Case] 1) Enable the bionic-proposed repository, and install the nvidia-430 package 2) Restart and see if the system boots correctly. If unsure, please attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log [Regression Potential] Low, the packages are already in Eoan. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1834603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834603] Re: SRU request: Include the 430 driver in Ubuntu 18.04
** Changed in: oem-priority Assignee: (unassigned) => Cyrus Lien (cyruslien) ** Changed in: oem-priority/bionic Status: New => Fix Released ** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1834603 Title: SRU request: Include the 430 driver in Ubuntu 18.04 Status in OEM Priority Project: Fix Released Status in OEM Priority Project bionic series: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: New Status in nvidia-settings package in Ubuntu: In Progress Status in nvidia-graphics-drivers-430 source package in Xenial: In Progress Status in nvidia-settings source package in Xenial: In Progress Status in nvidia-graphics-drivers-430 source package in Bionic: Fix Released Bug description: SRU Request: [Impact] The nvidia packages in Ubuntu 18.04 do not support recent NVIDIA GPUs. ([10de:2191][10de:1f91][10de:1c91] [Test Case] 1) Enable the bionic-proposed repository, and install the nvidia-430 package 2) Restart and see if the system boots correctly. If unsure, please attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log [Regression Potential] Low, the packages are already in Eoan. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1834603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839818] [NEW] System won't enter suspend after idle over 20 minutes (TSC unstable)
Public bug reported: Summary: System won't enter suspend after idle over 20 minutes Steps to reproduce: 1. install manifest and boot into OS 2. idle system for 20 mins Expected result: System could enter suspend after idle over 20 minutes Actual result: System won't enter suspend after idle over 20 minutes Failure rate: 3/3 Dmesg: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123341] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123365] clocksource: 'hpet' wd_now: e336cfbb wd_last: e2e9b5c5 mask: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123370] clocksource: 'tsc' cs_now: 6299ac5acc cs_last: 6250285866 mask: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123377] tsc: Marking TSC unstable due to clocksource watchdog Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123486] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123491] sched_clock: Marking unstable (158972862012, 149405080)<-(159105581047, 17903053) Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.122862] clocksource: Switched to clocksource hpet ** Affects: oem-priority Importance: Undecided Status: New ** Affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority ** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1839818 Title: System won't enter suspend after idle over 20 minutes (TSC unstable) Status in OEM Priority Project: New Status in linux-oem package in Ubuntu: New Bug description: Summary: System won't enter suspend after idle over 20 minutes Steps to reproduce: 1. install manifest and boot into OS 2. idle system for 20 mins Expected result: System could enter suspend after idle over 20 minutes Actual result: System won't enter suspend after idle over 20 minutes Failure rate: 3/3 Dmesg: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123341] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123365] clocksource: 'hpet' wd_now: e336cfbb wd_last: e2e9b5c5 mask: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123370] clocksource: 'tsc' cs_now: 6299ac5acc cs_last: 6250285866 mask: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123377] tsc: Marking TSC unstable due to clocksource watchdog Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123486] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123491] sched_clock: Marking unstable (158972862012, 149405080)<-(159105581047, 17903053) Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.122862] clocksource: Switched to clocksource hpet To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1839818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839818] Re: System won't enter suspend after idle over 20 minutes (TSC unstable)
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1839818 Title: System won't enter suspend after idle over 20 minutes (TSC unstable) Status in OEM Priority Project: New Status in linux-oem package in Ubuntu: New Bug description: Summary: System won't enter suspend after idle over 20 minutes Steps to reproduce: 1. install manifest and boot into OS 2. idle system for 20 mins Expected result: System could enter suspend after idle over 20 minutes Actual result: System won't enter suspend after idle over 20 minutes Failure rate: 3/3 Dmesg: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123341] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123365] clocksource: 'hpet' wd_now: e336cfbb wd_last: e2e9b5c5 mask: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123370] clocksource: 'tsc' cs_now: 6299ac5acc cs_last: 6250285866 mask: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123377] tsc: Marking TSC unstable due to clocksource watchdog Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123486] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123491] sched_clock: Marking unstable (158972862012, 149405080)<-(159105581047, 17903053) Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.122862] clocksource: Switched to clocksource hpet To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1839818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839818] Re: System won't enter suspend after idle over 20 minutes (TSC unstable)
** Changed in: oem-priority Assignee: (unassigned) => Cyrus Lien (cyruslien) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed ** Description changed: Summary: System won't enter suspend after idle over 20 minutes Steps to reproduce: 1. install manifest and boot into OS 2. idle system for 20 mins Expected result: System could enter suspend after idle over 20 minutes Actual result: System won't enter suspend after idle over 20 minutes Failure rate: 3/3 Dmesg: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123341] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123365] clocksource: 'hpet' wd_now: e336cfbb wd_last: e2e9b5c5 mask: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123370] clocksource: 'tsc' cs_now: 6299ac5acc cs_last: 6250285866 mask: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123377] tsc: Marking TSC unstable due to clocksource watchdog Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123486] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123491] sched_clock: Marking unstable (158972862012, 149405080)<-(159105581047, 17903053) Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.122862] clocksource: Switched to clocksource hpet + + + Upstream bug: + https://bugzilla.kernel.org/show_bug.cgi?id=203183 ** Description changed: Summary: System won't enter suspend after idle over 20 minutes Steps to reproduce: 1. install manifest and boot into OS 2. idle system for 20 mins Expected result: System could enter suspend after idle over 20 minutes Actual result: System won't enter suspend after idle over 20 minutes Failure rate: 3/3 Dmesg: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123341] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123365] clocksource: 'hpet' wd_now: e336cfbb wd_last: e2e9b5c5 mask: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123370] clocksource: 'tsc' cs_now: 6299ac5acc cs_last: 6250285866 mask: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123377] tsc: Marking TSC unstable due to clocksource watchdog Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123486] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123491] sched_clock: Marking unstable (158972862012, 149405080)<-(159105581047, 17903053) Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.122862] clocksource: Switched to clocksource hpet - Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=203183 + lkml patch: + https://lkml.org/lkml/2019/4/10/167 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1839818 Title: System won't enter suspend after idle over 20 minutes (TSC unstable) Status in OEM Priority Project: Confirmed Status in linux-oem package in Ubuntu: New Bug description: Summary: System won't enter suspend after idle over 20 minutes Steps to reproduce: 1. install manifest and boot into OS 2. idle system for 20 mins Expected result: System could enter suspend after idle over 20 minutes Actual result: System won't enter suspend after idle over 20 minutes Failure rate: 3/3 Dmesg: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123341] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123365] clocksource: 'hpet' wd_now: e336cfbb wd_last: e2e9b5c5 mask: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123370] clocksource: 'tsc' cs_now: 6299ac5acc cs_last: 6250285866 mask: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123377] tsc: Marking TSC unstable due to clocksource watchdog Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123486] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123491] sched_clock: Marking unstable (158972862012, 149405080)<-(159105581047, 17903053) Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.122862] clocksource: Switched to clocksource hpet Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=203183 lkml patch: https://lkml.org/lkml/2019/4/10/167 To manage notifications about this bug go to: https://bugs.l
[Kernel-packages] [Bug 1872034] Re: [Focal] No HDMI output through thunderbolt docking station
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Invalid -- 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/1872034 Title: [Focal] No HDMI output through thunderbolt docking station Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Invalid Bug description: I can find monitor in display list, but no output from it. Also, I can't switch to extend mode, it failed to apply the setting and switched back to mirror mode. [Steps] 1. Connect a thunderbolt docking station to thunderbolt port. 2. Connect HDMI monitor to HDMI port on the docking station. 3. Switch mode in display setting ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 16:44:40 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=98c0c28f-278e-442b-8fc9-6d663bacd68d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd01/08/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872034/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839818] Re: System won't enter suspend after idle over 20 minutes (TSC unstable)
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1030.34 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840239/comments/17 ** Changed in: oem-priority Status: Confirmed => Fix Released ** Changed in: linux-oem (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1839818 Title: System won't enter suspend after idle over 20 minutes (TSC unstable) Status in OEM Priority Project: Fix Released Status in linux-oem package in Ubuntu: Fix Released Bug description: Summary: System won't enter suspend after idle over 20 minutes Steps to reproduce: 1. install manifest and boot into OS 2. idle system for 20 mins Expected result: System could enter suspend after idle over 20 minutes Actual result: System won't enter suspend after idle over 20 minutes Failure rate: 3/3 Dmesg: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123341] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123365] clocksource: 'hpet' wd_now: e336cfbb wd_last: e2e9b5c5 mask: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123370] clocksource: 'tsc' cs_now: 6299ac5acc cs_last: 6250285866 mask: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123377] tsc: Marking TSC unstable due to clocksource watchdog Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123486] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123491] sched_clock: Marking unstable (158972862012, 149405080)<-(159105581047, 17903053) Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.122862] clocksource: Switched to clocksource hpet Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=203183 lkml patch: https://lkml.org/lkml/2019/4/10/167 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1839818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
** Changed in: dell-sputnik Status: New => Confirmed ** Changed in: dell-sputnik Importance: Undecided => Critical ** Changed in: dell-sputnik Assignee: (unassigned) => Cyrus Lien (cyruslien) -- 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/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) Status in Dell Sputnik: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled. The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list. To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying. My syslog when this happens: Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3 Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22 Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root. Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21 Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 12133 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c11 of user root. Apr 11 12:25:46 visyu-albat
[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
The kernel is 4.4.0-121-generic(#4), I though it was solved on kernel version >= 4.4.0-93.116. -- 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/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) Status in Dell Sputnik: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled. The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list. To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying. My syslog when this happens: Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3 Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22 Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root. Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21 Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 12133 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c11 of user root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Sockets. Apr 11 12:2
[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
** Attachment added: "collect-log.sh" https://bugs.launchpad.net/dell-sputnik/+bug/1766825/+attachment/5127476/+files/collect-log.sh -- 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/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) Status in Dell Sputnik: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled. The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list. To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying. My syslog when this happens: Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3 Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22 Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root. Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21 Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 12133 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c11 of user root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[121
[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
@Felix, Would you please try this issue on kernel 4.4.0-93.117 ? -- 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/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) Status in Dell Sputnik: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled. The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list. To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying. My syslog when this happens: Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3 Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22 Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root. Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21 Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 12133 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c11 of user root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[
[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
@Felix, Also, need more system information. Please execute attached script by `sudo collect-log.sh' to collect more system information and attach debuglog.tgz here. Thanks! -- 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/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) Status in Dell Sputnik: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled. The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list. To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying. My syslog when this happens: Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3 Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22 Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root. Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21 Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 12133 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c11 of user root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr
[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
I can reproduce it only on AC mode. Still can reproduce it after disable tlp. kernel: 4.4.0-100 BIOS: 1.2.1 -- 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/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) Status in Dell Sputnik: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled. The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list. To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying. My syslog when this happens: Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3 Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22 Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root. Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21 Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 12133 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c11 of user root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Sockets.
[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
A quick workaround is rmmod btusb before suspend and insert btusb after resume. To do this, you can put a executable script of any name in /lib/systemd/system-sleep/. Example: #!/bin/sh if [ "$1" = "pre" ]; then systemctl stop bluetooth && rmmod btusb elif [ "$1" = "post" ]; then modprobe btusb && systemctl start bluetooth fi -- 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/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) Status in Dell Sputnik: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled. The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list. To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying. My syslog when this happens: Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3 Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22 Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root. Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21 Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 12133 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11
[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
Will escalate this issue to Qualcomm. ** Changed in: dell-sputnik Status: Confirmed => Triaged -- 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/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Confirmed Bug description: I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled. The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list. To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying. My syslog when this happens: Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3 Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22 Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root. Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21 Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 12133 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c11 of user root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Sockets. Apr 1
[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
Confirmed, the issue was gone with firmware from https://askubuntu.com/a/1029749/95109. -- 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/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Confirmed Bug description: I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled. The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list. To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying. My syslog when this happens: Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3 Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22 Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root. Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21 Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 12133 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c11 of user root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Sockets. Apr 11 12:25:46 visy
[Kernel-packages] [Bug 1759303] Re: Update Aquantia driver to fix various issues
@Time, Backporting those patches are request from our customer and we really have no idea how to verify those fixes. Is there any way to keep those fixes ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1759303 Title: Update Aquantia driver to fix various issues Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Committed Bug description: ===SRU Justification=== [Impact] According to commit log, there are lots of issues got fixed for Aquantia driver since v4.13. [Test] It's a request from costumer. Unless Aquantia provides a reproducer, we need Aquantia to verify it. [Fix] Update Aquantia driver to 2.0.2.1, basically keep the driver in sync with Linux kernel v4.16. [Regression Potential] Low. The driver is the same one as in v4.16, so it should be well tested by Aquantia. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1664602] Re: Using an NVMe drive causes huge power drain
Verified on 4.4.0-117-generic, APST was enabled. #sudo nvme get-feature -f 0x0c -H /dev/nvme0n1 get-feature:0x0c (Autonomous Power State Transition), Current value: 0x01 Autonomous Power State Transition Enable (APSTE): Enabled Auto PST Entries. Entry[ 0] . Idle Time Prior to Transition (ITPT): 1500 ms Idle Transition Power State (ITPS): 3 . Entry[ 1] ** Attachment added: "nvme-get-feature.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602/+attachment/5087978/+files/nvme-get-feature.log ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1664602 Title: Using an NVMe drive causes huge power drain Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: PCIe NVMe drives are very common in new laptops. The Zesty's kernels (including latest 4.10 rc8 from CKT PPA) does not support APST (autonomous power state transitions). A patch does exist : http://lists.infradead.org/pipermail/linux-nvme/2017-February/008051.html https://github.com/damige/linux-nvme It seems that we cannot expect this before kernel 4.11. Additionally my laptop CPU does never go under PC3 power saving state, powertop says. I don't know if it's related. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ft 1900 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=a04b55bf-b1b6-464c-88ce-44b6adbbbc10 InstallationDate: Installed on 2016-12-12 (63 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 7510 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic root=UUID=0d1f213e-73a9-4097-ae64-9cd963cfba23 ro quiet ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 RelatedPackageVersions: linux-restricted-modules-4.10.0-8-generic N/A linux-backports-modules-4.10.0-8-generic N/A linux-firmware1.163 Tags: zesty Uname: Linux 4.10.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.5 dmi.board.name: 0YH43H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.5:bd12/22/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn0YH43H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 7510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1664602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510570] Re: Bluetooth LE pairing fail
Verified bluez 5.37-0ubuntu5.2 from -proposed, designer mouse works but designer keyboard failed. To fully support BT LE, looks like we need to upgrade bluez >5.44. (verified bluez 5.46-0ubuntu4~somerville1 which comes form artful can make designer keyboard works) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1510570 Title: Bluetooth LE pairing fail Status in OEM Priority Project: Confirmed Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Xenial: Fix Committed Bug description: [Impact] When the Bluetooth adapter is not powered on it is not possible to use it in normal way. We used to have a hack to force powering on by using an udev rule but this doe snot work anymore. Luckily the BlueZ has introduced "AutoEnable" option that makes the stack power on adapters by itself. Backporting this to xenial will improve life of the desktop users and will not require them to hack the solution on their own. The fix itself uses the well known solution to this problem that is floating around there for a while. The upload fixes the bug by enabling the 'AutoEnable' option in the bluetoothd config file. [Original Report] . 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 [Test Case] On xenial install from ppa: https://launchpad.net/~bluetooth/+archive/ubuntu/bluez Now reboot the machine. The BT adapter shall be powered on. [Regression Potential] If things go wrong the adapter will not be powered on after the system boots up. Therefore while testing please focus on the adapter state, i.e. powered on or off. [Other Info] This fix is included in the development release, see: http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22 [What to upload] For xenial as in: ) https://launchpad.net/~bluetooth/+archive/ubuntu/bluez ) https://launchpadlibrarian.net/347480725/bluez_5.37-0ubuntu5_5.37-0ubuntu5.2~build1.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510570] Re: Bluetooth LE pairing fail
Designer keyboard still can not connect on 4.13.0-32-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1510570 Title: Bluetooth LE pairing fail Status in OEM Priority Project: Confirmed Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Xenial: Fix Committed Bug description: [Impact] When the Bluetooth adapter is not powered on it is not possible to use it in normal way. We used to have a hack to force powering on by using an udev rule but this doe snot work anymore. Luckily the BlueZ has introduced "AutoEnable" option that makes the stack power on adapters by itself. Backporting this to xenial will improve life of the desktop users and will not require them to hack the solution on their own. The fix itself uses the well known solution to this problem that is floating around there for a while. The upload fixes the bug by enabling the 'AutoEnable' option in the bluetoothd config file. [Original Report] . 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 [Test Case] On xenial install from ppa: https://launchpad.net/~bluetooth/+archive/ubuntu/bluez Now reboot the machine. The BT adapter shall be powered on. [Regression Potential] If things go wrong the adapter will not be powered on after the system boots up. Therefore while testing please focus on the adapter state, i.e. powered on or off. [Other Info] This fix is included in the development release, see: http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22 [What to upload] For xenial as in: ) https://launchpad.net/~bluetooth/+archive/ubuntu/bluez ) https://launchpadlibrarian.net/347480725/bluez_5.37-0ubuntu5_5.37-0ubuntu5.2~build1.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510570] Re: Bluetooth LE pairing fail
With bluez 5.37-0ubuntu5.2 Designer keyboard still can not connect on 4.13.0-32-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1510570 Title: Bluetooth LE pairing fail Status in OEM Priority Project: Confirmed Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Xenial: Fix Committed Bug description: [Impact] When the Bluetooth adapter is not powered on it is not possible to use it in normal way. We used to have a hack to force powering on by using an udev rule but this doe snot work anymore. Luckily the BlueZ has introduced "AutoEnable" option that makes the stack power on adapters by itself. Backporting this to xenial will improve life of the desktop users and will not require them to hack the solution on their own. The fix itself uses the well known solution to this problem that is floating around there for a while. The upload fixes the bug by enabling the 'AutoEnable' option in the bluetoothd config file. [Original Report] . 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 [Test Case] On xenial install from ppa: https://launchpad.net/~bluetooth/+archive/ubuntu/bluez Now reboot the machine. The BT adapter shall be powered on. [Regression Potential] If things go wrong the adapter will not be powered on after the system boots up. Therefore while testing please focus on the adapter state, i.e. powered on or off. [Other Info] This fix is included in the development release, see: http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22 [What to upload] For xenial as in: ) https://launchpad.net/~bluetooth/+archive/ubuntu/bluez ) https://launchpadlibrarian.net/347480725/bluez_5.37-0ubuntu5_5.37-0ubuntu5.2~build1.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1686061] Re: Precision Rack failed to resume from S4
Test case: fwts --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120 --s4-multiple=30 Result: Pass S4 hibernate/resume test 30 cycles. ** Attachment added: "results.log" https://bugs.launchpad.net/hwe-next/+bug/1686061/+attachment/4887168/+files/results.log ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1686061 Title: Precision Rack failed to resume from S4 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: On a Precision Rack with two CPUs, it failed to resume from S4 at ~70% rate. These two commits can fix the issue: commit 406f992e4a372dafbe3c2cff7efbb2002a5c8ebd Author: Rafael J. Wysocki Date: Thu Jul 14 03:55:23 2016 +0200 x86 / hibernate: Use hlt_play_dead() when resuming from hibernation commit e4630fdd47637168927905983205d7b7c5c08c09 Author: Rafael J. Wysocki Date: Mon Aug 8 15:31:31 2016 +0200 x86/power/64: Always create temporary identity mapping correctly To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1686061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702685] Re: No wifi connectivity with kernel 4.4.0-83
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Assignee: (unassigned) => Shih-Yuan Lee (fourdollars) -- 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/1702685 Title: No wifi connectivity with kernel 4.4.0-83 Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I have wifi connectivity with the previous kernel if I choose it from the GRUB screen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic 4.4.0-83.106 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vasa1 2000 F pulseaudio CRDA: country IN: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 20), (N/A) (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 20), (N/A) CurrentDesktop: Unity Date: Thu Jul 6 18:21:07 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=087adc85-f179-4429-9373-e2227f37cb9a InstallationDate: Installed on 2017-01-02 (185 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed root=UUID=30e6bdd2-27bf-4ef2-8076-333d24f18336 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-83-generic N/A linux-backports-modules-4.4.0-83-generic N/A linux-firmware1.157.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.07.00 dmi.board.name: 0FGN4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.07.00:bd04/07/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1702685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702685] Re: No wifi connectivity with kernel 4.4.0-83 if ath9k-msi dkms is installed
[168c:0042] DW1810 [168c:0036] DW1707 #8 is incorrect platform as bug reported, the manifest for #8 platform doesn't include ath9k-msi dkms. -- 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/1702685 Title: No wifi connectivity with kernel 4.4.0-83 if ath9k-msi dkms is installed Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: I have wifi connectivity with the previous kernel if I choose it from the GRUB screen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic 4.4.0-83.106 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vasa1 2000 F pulseaudio CRDA: country IN: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 20), (N/A) (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 20), (N/A) CurrentDesktop: Unity Date: Thu Jul 6 18:21:07 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=087adc85-f179-4429-9373-e2227f37cb9a InstallationDate: Installed on 2017-01-02 (185 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed root=UUID=30e6bdd2-27bf-4ef2-8076-333d24f18336 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-83-generic N/A linux-backports-modules-4.4.0-83-generic N/A linux-firmware1.157.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.07.00 dmi.board.name: 0FGN4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.07.00:bd04/07/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1702685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702685] Re: No wifi connectivity with kernel 4.4.0-83 if ath9k-msi dkms is installed
Need to confirm the issue on correct platform before online update verify. -- 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/1702685 Title: No wifi connectivity with kernel 4.4.0-83 if ath9k-msi dkms is installed Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: I have wifi connectivity with the previous kernel if I choose it from the GRUB screen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic 4.4.0-83.106 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vasa1 2000 F pulseaudio CRDA: country IN: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 20), (N/A) (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 20), (N/A) CurrentDesktop: Unity Date: Thu Jul 6 18:21:07 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=087adc85-f179-4429-9373-e2227f37cb9a InstallationDate: Installed on 2017-01-02 (185 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed root=UUID=30e6bdd2-27bf-4ef2-8076-333d24f18336 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-83-generic N/A linux-backports-modules-4.4.0-83-generic N/A linux-firmware1.157.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.07.00 dmi.board.name: 0FGN4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.07.00:bd04/07/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1702685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642470] Re: SRU. Please re-enable CONFIG_DRM_MGAG200.
** Changed in: oem-priority Status: New => Triaged ** Changed in: oem-priority Importance: Critical => High ** Tags removed: somerville -- 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/1642470 Title: SRU. Please re-enable CONFIG_DRM_MGAG200. Status in HWE Next: New Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in linux package in Ubuntu: Confirmed Bug description: A new Dell Precision workstation uses Matrox graphics cards. And in order to let Xorg mga driver work. We need to enable CONFIG_DRM_MGAG200. MGAG200 is disabled by this bug. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1042903 Since Dell's laptops needs this to be enabled. I think we need to test lp:1042903 again because it's 4 years ago on HP. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1642470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1450322] [NEW] [i915_bdw] No screen output on specific LCD panel (DPN: 99DCK))
Public bug reported: [Summary] There are no screen output on specific LCD panel (DPN: 99DCK). [Reproduce Steps] 1. Normal install the system 2. start the system [Results]: Only black screen showed up [Additional Information] Kernel: 3.13.0-36-generic ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Trusty) Importance: Critical Assignee: Timo Aaltonen (tjaalton) Status: In Progress ** Attachment added: "var/log" https://bugs.launchpad.net/bugs/1450322/+attachment/4388058/+files/Cedar-LCD-Logs.zip -- 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/1450322 Title: [i915_bdw] No screen output on specific LCD panel (DPN: 99DCK)) Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: In Progress Bug description: [Summary] There are no screen output on specific LCD panel (DPN: 99DCK). [Reproduce Steps] 1. Normal install the system 2. start the system [Results]: Only black screen showed up [Additional Information] Kernel: 3.13.0-36-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
** Tags added: originate-from-2000298 -- 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/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Fix Committed Status in grub2-unsigned package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: [Workaround] Some workarounds have been suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125 [Impact]  * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2.  * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory region starvation in <1G addresses: Type StartEnd # Pages Attributes Available -00086FFF 0087 000F BS_Data00087000-00087FFF 0001 000F Available 00088000-0009EFFF 0017 000F Reserved 0009F000-0009 0001 000F Available 0010-00FF 0F00 000F LoaderCode 0100-01021FFF 0022 000F Available 01022000-238A7FFF 00022886 000F BS_Data238A8000-23927FFF 0080 000F Available 23928000-28860FFF 4F39 000F BS_Data28861000-2AB09FFF 22A9 000F LoaderCode 2AB0A000-2ACF8FFF 01EF 000F BS_Data2ACF9000-2B2FAFFF 0602 000F Available 2B2FB000-2B611FFF 0317 000F BS_Data2B612000-2B630FFF 001F 000F Available 2B631000-2B632FFF 0002 000F BS_Data2B633000-2B63CFFF 000A 000F Available 2B63D000-2B649FFF 000D 000F BS_Data2B64A000-2B64EFFF 0005 000F Available 2B64F000-2B666FFF 0018 000F BS_Data2B667000-2D8D5FFF 226F 000F LoaderCode 2D8D6000-2D8E9FFF 0014 000F BS_Data2D8EA000-2D925FFF 003C 000F LoaderCode 2D926000-2D932FFF 000D 000F BS_Data2D933000-2D969FFF 0037 000F BS_Code2D96A000-2D973FFF 000A 000F BS_Data2D974000-2E377FFF 0A04 000F Available 2E378000-2E37AFFF 0003 000F ... Reserved 3C08B000-4192 58A5 000F ACPI_NVS 4193-41B2 0200 000F ACPI_Recl 41B3-41BFEFFF 00CF 000F BS_Data41BFF000-41BF 0001 000F Available 0001-0002AB7F 001AB800 000F Reserved 000A-000F 0060 Reserved 41C0-43FF 2400 Reserved 4400-47FF 4000 000F Reserved 4940
[Kernel-packages] [Bug 2011768] Re: Fix NVME storage with RAID ON disappeared under Dell factory WINPE environment
Verified pass with kernel 6.1.0-1009-oem. MS diskpart can find nvme after reboot from 6.1.0-1009-oem. For more detail please check https://bugs.launchpad.net/somerville/+bug/1999522/comments/39. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2011768 Title: Fix NVME storage with RAID ON disappeared under Dell factory WINPE environment Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] NVME storage disappeared under Dell factory WINPE environment with RAID ON mode when this WINPE boot entry touched by efibootmgr [Fix] Reset the VMD msi remapping during shutdown. [Test Case] 1. Install Ubuntu 2. Then, system will reboot to WINPE to do some cleanup work. 3. in WINPE, the NVME storage could be listed. [Where problems could occur] Low, the issue may be observed on VMD MSI remapping. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2011768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977815] [NEW] ADLP AX211 iwlwifi firmware crash after resume
Public bug reported: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. wifi failed to connect after the below message. [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 [ 5525.555157] iwlwifi :00:14.3: 0x004D960E | interruptlink2 [ 5525.555160] iwlwifi :00:14.3: 0x004C6C34 | data1 [ 5525.555163] iwlwifi :00:14.3: 0x0100 | data2 [ 5525.555167] iwlwifi :00:14.3: 0x | data3 [ 5525.555170] iwlwifi :00:14.3: 0x1AC138AE | beacon time [ 5525.555174] iwlwifi :00:14.3: 0xFA1F775A | tsf low [ 5525.555177] iwlwifi :00:14.3: 0x0002 | tsf hi [ 5525.555181] iwlwifi :00:14.3: 0x | time gp1 [ 5525.555184] iwlwifi :00:14.3: 0x029BB566 | time gp2 [ 5525.555188] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 5525.555191] iwlwifi :00:14.3: 0x0043 | uCode version major [ 5525.555194] iwlwifi :00:14.3: 0x8F59B80B | uCode version minor [ 5525.555198] iwlwifi :00:14.3: 0x0370 | hw version [ 5525.555202] iwlwifi :00:14.3: 0x00489002 | board version --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-qyburn+X170 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. wlp0s20f3 no wireless extensions. enx00e04f8238df no wireless extensions. MachineType: Dell Inc. Inspiron 16 5620 Package: linux-firmware 1.187.31 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1040-oem root=UUID=202d0ced-071f-4d95-a481-17b8e1078844 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1040.44-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1040-oem N/A linux-backports-modules-5.14.0-1040-oem N/A linux-firmware 1.187.31 Tags: focal Uname: Linux 5.14.0-1040-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0Q901G dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd04/21/2022:br1.1:svnDellInc.:pnInspiron165620:pvr:rvnDellInc.:rn0Q901G:rvrD02:cvnDellInc.:ct10:cvr:sku0BAA: dmi.product.family: Inspiron dmi.product.name: Inspiron 16 5620 dmi.product.sku: 0BAA dmi.sys.vendor: Dell Inc. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected focal ** Description changed: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. + + wifi failed to connect after the below message. + + [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 + [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. + [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: + [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 + [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode + [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN + [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 + [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 + [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 + [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 + [ 5525.555157] iwlwifi :00:14.3: 0x004D960E
[Kernel-packages] [Bug 1977815] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1977815/+attachment/5595229/+files/CRDA.txt -- 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/1977815 Title: ADLP AX211 iwlwifi firmware crash after resume Status in linux-firmware package in Ubuntu: New Bug description: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. wifi failed to connect after the below message. [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 [ 5525.555157] iwlwifi :00:14.3: 0x004D960E | interruptlink2 [ 5525.555160] iwlwifi :00:14.3: 0x004C6C34 | data1 [ 5525.555163] iwlwifi :00:14.3: 0x0100 | data2 [ 5525.555167] iwlwifi :00:14.3: 0x | data3 [ 5525.555170] iwlwifi :00:14.3: 0x1AC138AE | beacon time [ 5525.555174] iwlwifi :00:14.3: 0xFA1F775A | tsf low [ 5525.555177] iwlwifi :00:14.3: 0x0002 | tsf hi [ 5525.555181] iwlwifi :00:14.3: 0x | time gp1 [ 5525.555184] iwlwifi :00:14.3: 0x029BB566 | time gp2 [ 5525.555188] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 5525.555191] iwlwifi :00:14.3: 0x0043 | uCode version major [ 5525.555194] iwlwifi :00:14.3: 0x8F59B80B | uCode version minor [ 5525.555198] iwlwifi :00:14.3: 0x0370 | hw version [ 5525.555202] iwlwifi :00:14.3: 0x00489002 | board version --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-qyburn+X170 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. wlp0s20f3 no wireless extensions. enx00e04f8238df no wireless extensions. MachineType: Dell Inc. Inspiron 16 5620 Package: linux-firmware 1.187.31 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1040-oem root=UUID=202d0ced-071f-4d95-a481-17b8e1078844 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1040.44-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1040-oem N/A linux-backports-modules-5.14.0-1040-oem N/A linux-firmware 1.187.31 Tags: focal Uname: Linux 5.14.0-1040-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0Q901G dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd04/21/2022:br1.1:svnDellInc.:pnInspiron165620:pvr:rvnDellInc.:rn0Q901G:rvrD02:cvnDellInc.:ct10:cvr:sku0BAA: dmi.product.family: Inspiron dmi.product.name: Inspiron 16 5620 dmi.product.sku: 0BAA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1977815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977815] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1977815/+attachment/5595228/+files/AlsaInfo.txt -- 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/1977815 Title: ADLP AX211 iwlwifi firmware crash after resume Status in linux-firmware package in Ubuntu: New Bug description: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. wifi failed to connect after the below message. [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 [ 5525.555157] iwlwifi :00:14.3: 0x004D960E | interruptlink2 [ 5525.555160] iwlwifi :00:14.3: 0x004C6C34 | data1 [ 5525.555163] iwlwifi :00:14.3: 0x0100 | data2 [ 5525.555167] iwlwifi :00:14.3: 0x | data3 [ 5525.555170] iwlwifi :00:14.3: 0x1AC138AE | beacon time [ 5525.555174] iwlwifi :00:14.3: 0xFA1F775A | tsf low [ 5525.555177] iwlwifi :00:14.3: 0x0002 | tsf hi [ 5525.555181] iwlwifi :00:14.3: 0x | time gp1 [ 5525.555184] iwlwifi :00:14.3: 0x029BB566 | time gp2 [ 5525.555188] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 5525.555191] iwlwifi :00:14.3: 0x0043 | uCode version major [ 5525.555194] iwlwifi :00:14.3: 0x8F59B80B | uCode version minor [ 5525.555198] iwlwifi :00:14.3: 0x0370 | hw version [ 5525.555202] iwlwifi :00:14.3: 0x00489002 | board version --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-qyburn+X170 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. wlp0s20f3 no wireless extensions. enx00e04f8238df no wireless extensions. MachineType: Dell Inc. Inspiron 16 5620 Package: linux-firmware 1.187.31 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1040-oem root=UUID=202d0ced-071f-4d95-a481-17b8e1078844 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1040.44-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1040-oem N/A linux-backports-modules-5.14.0-1040-oem N/A linux-firmware 1.187.31 Tags: focal Uname: Linux 5.14.0-1040-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0Q901G dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd04/21/2022:br1.1:svnDellInc.:pnInspiron165620:pvr:rvnDellInc.:rn0Q901G:rvrD02:cvnDellInc.:ct10:cvr:sku0BAA: dmi.product.family: Inspiron dmi.product.name: Inspiron 16 5620 dmi.product.sku: 0BAA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1977815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977815] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1977815/+attachment/5595231/+files/CurrentDmesg.txt -- 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/1977815 Title: ADLP AX211 iwlwifi firmware crash after resume Status in linux-firmware package in Ubuntu: New Bug description: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. wifi failed to connect after the below message. [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 [ 5525.555157] iwlwifi :00:14.3: 0x004D960E | interruptlink2 [ 5525.555160] iwlwifi :00:14.3: 0x004C6C34 | data1 [ 5525.555163] iwlwifi :00:14.3: 0x0100 | data2 [ 5525.555167] iwlwifi :00:14.3: 0x | data3 [ 5525.555170] iwlwifi :00:14.3: 0x1AC138AE | beacon time [ 5525.555174] iwlwifi :00:14.3: 0xFA1F775A | tsf low [ 5525.555177] iwlwifi :00:14.3: 0x0002 | tsf hi [ 5525.555181] iwlwifi :00:14.3: 0x | time gp1 [ 5525.555184] iwlwifi :00:14.3: 0x029BB566 | time gp2 [ 5525.555188] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 5525.555191] iwlwifi :00:14.3: 0x0043 | uCode version major [ 5525.555194] iwlwifi :00:14.3: 0x8F59B80B | uCode version minor [ 5525.555198] iwlwifi :00:14.3: 0x0370 | hw version [ 5525.555202] iwlwifi :00:14.3: 0x00489002 | board version --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-qyburn+X170 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. wlp0s20f3 no wireless extensions. enx00e04f8238df no wireless extensions. MachineType: Dell Inc. Inspiron 16 5620 Package: linux-firmware 1.187.31 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1040-oem root=UUID=202d0ced-071f-4d95-a481-17b8e1078844 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1040.44-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1040-oem N/A linux-backports-modules-5.14.0-1040-oem N/A linux-firmware 1.187.31 Tags: focal Uname: Linux 5.14.0-1040-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0Q901G dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd04/21/2022:br1.1:svnDellInc.:pnInspiron165620:pvr:rvnDellInc.:rn0Q901G:rvrD02:cvnDellInc.:ct10:cvr:sku0BAA: dmi.product.family: Inspiron dmi.product.name: Inspiron 16 5620 dmi.product.sku: 0BAA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1977815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977815] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1977815/+attachment/5595232/+files/Lspci.txt -- 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/1977815 Title: ADLP AX211 iwlwifi firmware crash after resume Status in linux-firmware package in Ubuntu: New Bug description: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. wifi failed to connect after the below message. [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 [ 5525.555157] iwlwifi :00:14.3: 0x004D960E | interruptlink2 [ 5525.555160] iwlwifi :00:14.3: 0x004C6C34 | data1 [ 5525.555163] iwlwifi :00:14.3: 0x0100 | data2 [ 5525.555167] iwlwifi :00:14.3: 0x | data3 [ 5525.555170] iwlwifi :00:14.3: 0x1AC138AE | beacon time [ 5525.555174] iwlwifi :00:14.3: 0xFA1F775A | tsf low [ 5525.555177] iwlwifi :00:14.3: 0x0002 | tsf hi [ 5525.555181] iwlwifi :00:14.3: 0x | time gp1 [ 5525.555184] iwlwifi :00:14.3: 0x029BB566 | time gp2 [ 5525.555188] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 5525.555191] iwlwifi :00:14.3: 0x0043 | uCode version major [ 5525.555194] iwlwifi :00:14.3: 0x8F59B80B | uCode version minor [ 5525.555198] iwlwifi :00:14.3: 0x0370 | hw version [ 5525.555202] iwlwifi :00:14.3: 0x00489002 | board version --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-qyburn+X170 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. wlp0s20f3 no wireless extensions. enx00e04f8238df no wireless extensions. MachineType: Dell Inc. Inspiron 16 5620 Package: linux-firmware 1.187.31 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1040-oem root=UUID=202d0ced-071f-4d95-a481-17b8e1078844 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1040.44-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1040-oem N/A linux-backports-modules-5.14.0-1040-oem N/A linux-firmware 1.187.31 Tags: focal Uname: Linux 5.14.0-1040-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0Q901G dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd04/21/2022:br1.1:svnDellInc.:pnInspiron165620:pvr:rvnDellInc.:rn0Q901G:rvrD02:cvnDellInc.:ct10:cvr:sku0BAA: dmi.product.family: Inspiron dmi.product.name: Inspiron 16 5620 dmi.product.sku: 0BAA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1977815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977815] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1977815/+attachment/5595236/+files/Lsusb-v.txt -- 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/1977815 Title: ADLP AX211 iwlwifi firmware crash after resume Status in linux-firmware package in Ubuntu: New Bug description: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. wifi failed to connect after the below message. [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 [ 5525.555157] iwlwifi :00:14.3: 0x004D960E | interruptlink2 [ 5525.555160] iwlwifi :00:14.3: 0x004C6C34 | data1 [ 5525.555163] iwlwifi :00:14.3: 0x0100 | data2 [ 5525.555167] iwlwifi :00:14.3: 0x | data3 [ 5525.555170] iwlwifi :00:14.3: 0x1AC138AE | beacon time [ 5525.555174] iwlwifi :00:14.3: 0xFA1F775A | tsf low [ 5525.555177] iwlwifi :00:14.3: 0x0002 | tsf hi [ 5525.555181] iwlwifi :00:14.3: 0x | time gp1 [ 5525.555184] iwlwifi :00:14.3: 0x029BB566 | time gp2 [ 5525.555188] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 5525.555191] iwlwifi :00:14.3: 0x0043 | uCode version major [ 5525.555194] iwlwifi :00:14.3: 0x8F59B80B | uCode version minor [ 5525.555198] iwlwifi :00:14.3: 0x0370 | hw version [ 5525.555202] iwlwifi :00:14.3: 0x00489002 | board version --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-qyburn+X170 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. wlp0s20f3 no wireless extensions. enx00e04f8238df no wireless extensions. MachineType: Dell Inc. Inspiron 16 5620 Package: linux-firmware 1.187.31 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1040-oem root=UUID=202d0ced-071f-4d95-a481-17b8e1078844 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1040.44-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1040-oem N/A linux-backports-modules-5.14.0-1040-oem N/A linux-firmware 1.187.31 Tags: focal Uname: Linux 5.14.0-1040-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0Q901G dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd04/21/2022:br1.1:svnDellInc.:pnInspiron165620:pvr:rvnDellInc.:rn0Q901G:rvrD02:cvnDellInc.:ct10:cvr:sku0BAA: dmi.product.family: Inspiron dmi.product.name: Inspiron 16 5620 dmi.product.sku: 0BAA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1977815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977815] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1977815/+attachment/5595239/+files/ProcCpuinfoMinimal.txt -- 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/1977815 Title: ADLP AX211 iwlwifi firmware crash after resume Status in linux-firmware package in Ubuntu: New Bug description: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. wifi failed to connect after the below message. [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 [ 5525.555157] iwlwifi :00:14.3: 0x004D960E | interruptlink2 [ 5525.555160] iwlwifi :00:14.3: 0x004C6C34 | data1 [ 5525.555163] iwlwifi :00:14.3: 0x0100 | data2 [ 5525.555167] iwlwifi :00:14.3: 0x | data3 [ 5525.555170] iwlwifi :00:14.3: 0x1AC138AE | beacon time [ 5525.555174] iwlwifi :00:14.3: 0xFA1F775A | tsf low [ 5525.555177] iwlwifi :00:14.3: 0x0002 | tsf hi [ 5525.555181] iwlwifi :00:14.3: 0x | time gp1 [ 5525.555184] iwlwifi :00:14.3: 0x029BB566 | time gp2 [ 5525.555188] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 5525.555191] iwlwifi :00:14.3: 0x0043 | uCode version major [ 5525.555194] iwlwifi :00:14.3: 0x8F59B80B | uCode version minor [ 5525.555198] iwlwifi :00:14.3: 0x0370 | hw version [ 5525.555202] iwlwifi :00:14.3: 0x00489002 | board version --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-qyburn+X170 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. wlp0s20f3 no wireless extensions. enx00e04f8238df no wireless extensions. MachineType: Dell Inc. Inspiron 16 5620 Package: linux-firmware 1.187.31 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1040-oem root=UUID=202d0ced-071f-4d95-a481-17b8e1078844 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1040.44-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1040-oem N/A linux-backports-modules-5.14.0-1040-oem N/A linux-firmware 1.187.31 Tags: focal Uname: Linux 5.14.0-1040-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0Q901G dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd04/21/2022:br1.1:svnDellInc.:pnInspiron165620:pvr:rvnDellInc.:rn0Q901G:rvrD02:cvnDellInc.:ct10:cvr:sku0BAA: dmi.product.family: Inspiron dmi.product.name: Inspiron 16 5620 dmi.product.sku: 0BAA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1977815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977815] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1977815/+attachment/5595245/+files/RfKill.txt -- 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/1977815 Title: ADLP AX211 iwlwifi firmware crash after resume Status in linux-firmware package in Ubuntu: New Bug description: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. wifi failed to connect after the below message. [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 [ 5525.555157] iwlwifi :00:14.3: 0x004D960E | interruptlink2 [ 5525.555160] iwlwifi :00:14.3: 0x004C6C34 | data1 [ 5525.555163] iwlwifi :00:14.3: 0x0100 | data2 [ 5525.555167] iwlwifi :00:14.3: 0x | data3 [ 5525.555170] iwlwifi :00:14.3: 0x1AC138AE | beacon time [ 5525.555174] iwlwifi :00:14.3: 0xFA1F775A | tsf low [ 5525.555177] iwlwifi :00:14.3: 0x0002 | tsf hi [ 5525.555181] iwlwifi :00:14.3: 0x | time gp1 [ 5525.555184] iwlwifi :00:14.3: 0x029BB566 | time gp2 [ 5525.555188] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 5525.555191] iwlwifi :00:14.3: 0x0043 | uCode version major [ 5525.555194] iwlwifi :00:14.3: 0x8F59B80B | uCode version minor [ 5525.555198] iwlwifi :00:14.3: 0x0370 | hw version [ 5525.555202] iwlwifi :00:14.3: 0x00489002 | board version --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-qyburn+X170 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. wlp0s20f3 no wireless extensions. enx00e04f8238df no wireless extensions. MachineType: Dell Inc. Inspiron 16 5620 Package: linux-firmware 1.187.31 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1040-oem root=UUID=202d0ced-071f-4d95-a481-17b8e1078844 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1040.44-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1040-oem N/A linux-backports-modules-5.14.0-1040-oem N/A linux-firmware 1.187.31 Tags: focal Uname: Linux 5.14.0-1040-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0Q901G dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd04/21/2022:br1.1:svnDellInc.:pnInspiron165620:pvr:rvnDellInc.:rn0Q901G:rvrD02:cvnDellInc.:ct10:cvr:sku0BAA: dmi.product.family: Inspiron dmi.product.name: Inspiron 16 5620 dmi.product.sku: 0BAA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1977815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977815] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1977815/+attachment/5595234/+files/Lsusb.txt -- 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/1977815 Title: ADLP AX211 iwlwifi firmware crash after resume Status in linux-firmware package in Ubuntu: New Bug description: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. wifi failed to connect after the below message. [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 [ 5525.555157] iwlwifi :00:14.3: 0x004D960E | interruptlink2 [ 5525.555160] iwlwifi :00:14.3: 0x004C6C34 | data1 [ 5525.555163] iwlwifi :00:14.3: 0x0100 | data2 [ 5525.555167] iwlwifi :00:14.3: 0x | data3 [ 5525.555170] iwlwifi :00:14.3: 0x1AC138AE | beacon time [ 5525.555174] iwlwifi :00:14.3: 0xFA1F775A | tsf low [ 5525.555177] iwlwifi :00:14.3: 0x0002 | tsf hi [ 5525.555181] iwlwifi :00:14.3: 0x | time gp1 [ 5525.555184] iwlwifi :00:14.3: 0x029BB566 | time gp2 [ 5525.555188] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 5525.555191] iwlwifi :00:14.3: 0x0043 | uCode version major [ 5525.555194] iwlwifi :00:14.3: 0x8F59B80B | uCode version minor [ 5525.555198] iwlwifi :00:14.3: 0x0370 | hw version [ 5525.555202] iwlwifi :00:14.3: 0x00489002 | board version --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-qyburn+X170 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. wlp0s20f3 no wireless extensions. enx00e04f8238df no wireless extensions. MachineType: Dell Inc. Inspiron 16 5620 Package: linux-firmware 1.187.31 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1040-oem root=UUID=202d0ced-071f-4d95-a481-17b8e1078844 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1040.44-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1040-oem N/A linux-backports-modules-5.14.0-1040-oem N/A linux-firmware 1.187.31 Tags: focal Uname: Linux 5.14.0-1040-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0Q901G dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd04/21/2022:br1.1:svnDellInc.:pnInspiron165620:pvr:rvnDellInc.:rn0Q901G:rvrD02:cvnDellInc.:ct10:cvr:sku0BAA: dmi.product.family: Inspiron dmi.product.name: Inspiron 16 5620 dmi.product.sku: 0BAA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1977815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977815] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1977815/+attachment/5595246/+files/UdevDb.txt -- 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/1977815 Title: ADLP AX211 iwlwifi firmware crash after resume Status in linux-firmware package in Ubuntu: New Bug description: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. wifi failed to connect after the below message. [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 [ 5525.555157] iwlwifi :00:14.3: 0x004D960E | interruptlink2 [ 5525.555160] iwlwifi :00:14.3: 0x004C6C34 | data1 [ 5525.555163] iwlwifi :00:14.3: 0x0100 | data2 [ 5525.555167] iwlwifi :00:14.3: 0x | data3 [ 5525.555170] iwlwifi :00:14.3: 0x1AC138AE | beacon time [ 5525.555174] iwlwifi :00:14.3: 0xFA1F775A | tsf low [ 5525.555177] iwlwifi :00:14.3: 0x0002 | tsf hi [ 5525.555181] iwlwifi :00:14.3: 0x | time gp1 [ 5525.555184] iwlwifi :00:14.3: 0x029BB566 | time gp2 [ 5525.555188] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 5525.555191] iwlwifi :00:14.3: 0x0043 | uCode version major [ 5525.555194] iwlwifi :00:14.3: 0x8F59B80B | uCode version minor [ 5525.555198] iwlwifi :00:14.3: 0x0370 | hw version [ 5525.555202] iwlwifi :00:14.3: 0x00489002 | board version --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-qyburn+X170 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. wlp0s20f3 no wireless extensions. enx00e04f8238df no wireless extensions. MachineType: Dell Inc. Inspiron 16 5620 Package: linux-firmware 1.187.31 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1040-oem root=UUID=202d0ced-071f-4d95-a481-17b8e1078844 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1040.44-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1040-oem N/A linux-backports-modules-5.14.0-1040-oem N/A linux-firmware 1.187.31 Tags: focal Uname: Linux 5.14.0-1040-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0Q901G dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd04/21/2022:br1.1:svnDellInc.:pnInspiron165620:pvr:rvnDellInc.:rn0Q901G:rvrD02:cvnDellInc.:ct10:cvr:sku0BAA: dmi.product.family: Inspiron dmi.product.name: Inspiron 16 5620 dmi.product.sku: 0BAA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1977815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977815] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1977815/+attachment/5595243/+files/ProcModules.txt -- 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/1977815 Title: ADLP AX211 iwlwifi firmware crash after resume Status in linux-firmware package in Ubuntu: New Bug description: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. wifi failed to connect after the below message. [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 [ 5525.555157] iwlwifi :00:14.3: 0x004D960E | interruptlink2 [ 5525.555160] iwlwifi :00:14.3: 0x004C6C34 | data1 [ 5525.555163] iwlwifi :00:14.3: 0x0100 | data2 [ 5525.555167] iwlwifi :00:14.3: 0x | data3 [ 5525.555170] iwlwifi :00:14.3: 0x1AC138AE | beacon time [ 5525.555174] iwlwifi :00:14.3: 0xFA1F775A | tsf low [ 5525.555177] iwlwifi :00:14.3: 0x0002 | tsf hi [ 5525.555181] iwlwifi :00:14.3: 0x | time gp1 [ 5525.555184] iwlwifi :00:14.3: 0x029BB566 | time gp2 [ 5525.555188] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 5525.555191] iwlwifi :00:14.3: 0x0043 | uCode version major [ 5525.555194] iwlwifi :00:14.3: 0x8F59B80B | uCode version minor [ 5525.555198] iwlwifi :00:14.3: 0x0370 | hw version [ 5525.555202] iwlwifi :00:14.3: 0x00489002 | board version --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-qyburn+X170 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. wlp0s20f3 no wireless extensions. enx00e04f8238df no wireless extensions. MachineType: Dell Inc. Inspiron 16 5620 Package: linux-firmware 1.187.31 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1040-oem root=UUID=202d0ced-071f-4d95-a481-17b8e1078844 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1040.44-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1040-oem N/A linux-backports-modules-5.14.0-1040-oem N/A linux-firmware 1.187.31 Tags: focal Uname: Linux 5.14.0-1040-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0Q901G dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd04/21/2022:br1.1:svnDellInc.:pnInspiron165620:pvr:rvnDellInc.:rn0Q901G:rvrD02:cvnDellInc.:ct10:cvr:sku0BAA: dmi.product.family: Inspiron dmi.product.name: Inspiron 16 5620 dmi.product.sku: 0BAA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1977815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977815] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1977815/+attachment/5595247/+files/acpidump.txt -- 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/1977815 Title: ADLP AX211 iwlwifi firmware crash after resume Status in linux-firmware package in Ubuntu: New Bug description: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. wifi failed to connect after the below message. [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 [ 5525.555157] iwlwifi :00:14.3: 0x004D960E | interruptlink2 [ 5525.555160] iwlwifi :00:14.3: 0x004C6C34 | data1 [ 5525.555163] iwlwifi :00:14.3: 0x0100 | data2 [ 5525.555167] iwlwifi :00:14.3: 0x | data3 [ 5525.555170] iwlwifi :00:14.3: 0x1AC138AE | beacon time [ 5525.555174] iwlwifi :00:14.3: 0xFA1F775A | tsf low [ 5525.555177] iwlwifi :00:14.3: 0x0002 | tsf hi [ 5525.555181] iwlwifi :00:14.3: 0x | time gp1 [ 5525.555184] iwlwifi :00:14.3: 0x029BB566 | time gp2 [ 5525.555188] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 5525.555191] iwlwifi :00:14.3: 0x0043 | uCode version major [ 5525.555194] iwlwifi :00:14.3: 0x8F59B80B | uCode version minor [ 5525.555198] iwlwifi :00:14.3: 0x0370 | hw version [ 5525.555202] iwlwifi :00:14.3: 0x00489002 | board version --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-qyburn+X170 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. wlp0s20f3 no wireless extensions. enx00e04f8238df no wireless extensions. MachineType: Dell Inc. Inspiron 16 5620 Package: linux-firmware 1.187.31 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1040-oem root=UUID=202d0ced-071f-4d95-a481-17b8e1078844 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1040.44-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1040-oem N/A linux-backports-modules-5.14.0-1040-oem N/A linux-firmware 1.187.31 Tags: focal Uname: Linux 5.14.0-1040-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0Q901G dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd04/21/2022:br1.1:svnDellInc.:pnInspiron165620:pvr:rvnDellInc.:rn0Q901G:rvrD02:cvnDellInc.:ct10:cvr:sku0BAA: dmi.product.family: Inspiron dmi.product.name: Inspiron 16 5620 dmi.product.sku: 0BAA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1977815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977815] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1977815/+attachment/5595240/+files/ProcEnviron.txt -- 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/1977815 Title: ADLP AX211 iwlwifi firmware crash after resume Status in linux-firmware package in Ubuntu: New Bug description: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. wifi failed to connect after the below message. [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 [ 5525.555157] iwlwifi :00:14.3: 0x004D960E | interruptlink2 [ 5525.555160] iwlwifi :00:14.3: 0x004C6C34 | data1 [ 5525.555163] iwlwifi :00:14.3: 0x0100 | data2 [ 5525.555167] iwlwifi :00:14.3: 0x | data3 [ 5525.555170] iwlwifi :00:14.3: 0x1AC138AE | beacon time [ 5525.555174] iwlwifi :00:14.3: 0xFA1F775A | tsf low [ 5525.555177] iwlwifi :00:14.3: 0x0002 | tsf hi [ 5525.555181] iwlwifi :00:14.3: 0x | time gp1 [ 5525.555184] iwlwifi :00:14.3: 0x029BB566 | time gp2 [ 5525.555188] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 5525.555191] iwlwifi :00:14.3: 0x0043 | uCode version major [ 5525.555194] iwlwifi :00:14.3: 0x8F59B80B | uCode version minor [ 5525.555198] iwlwifi :00:14.3: 0x0370 | hw version [ 5525.555202] iwlwifi :00:14.3: 0x00489002 | board version --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-qyburn+X170 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. wlp0s20f3 no wireless extensions. enx00e04f8238df no wireless extensions. MachineType: Dell Inc. Inspiron 16 5620 Package: linux-firmware 1.187.31 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1040-oem root=UUID=202d0ced-071f-4d95-a481-17b8e1078844 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1040.44-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1040-oem N/A linux-backports-modules-5.14.0-1040-oem N/A linux-firmware 1.187.31 Tags: focal Uname: Linux 5.14.0-1040-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0Q901G dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd04/21/2022:br1.1:svnDellInc.:pnInspiron165620:pvr:rvnDellInc.:rn0Q901G:rvrD02:cvnDellInc.:ct10:cvr:sku0BAA: dmi.product.family: Inspiron dmi.product.name: Inspiron 16 5620 dmi.product.sku: 0BAA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1977815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977815] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1977815/+attachment/5595233/+files/Lspci-vt.txt -- 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/1977815 Title: ADLP AX211 iwlwifi firmware crash after resume Status in linux-firmware package in Ubuntu: New Bug description: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. wifi failed to connect after the below message. [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 [ 5525.555157] iwlwifi :00:14.3: 0x004D960E | interruptlink2 [ 5525.555160] iwlwifi :00:14.3: 0x004C6C34 | data1 [ 5525.555163] iwlwifi :00:14.3: 0x0100 | data2 [ 5525.555167] iwlwifi :00:14.3: 0x | data3 [ 5525.555170] iwlwifi :00:14.3: 0x1AC138AE | beacon time [ 5525.555174] iwlwifi :00:14.3: 0xFA1F775A | tsf low [ 5525.555177] iwlwifi :00:14.3: 0x0002 | tsf hi [ 5525.555181] iwlwifi :00:14.3: 0x | time gp1 [ 5525.555184] iwlwifi :00:14.3: 0x029BB566 | time gp2 [ 5525.555188] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 5525.555191] iwlwifi :00:14.3: 0x0043 | uCode version major [ 5525.555194] iwlwifi :00:14.3: 0x8F59B80B | uCode version minor [ 5525.555198] iwlwifi :00:14.3: 0x0370 | hw version [ 5525.555202] iwlwifi :00:14.3: 0x00489002 | board version --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-qyburn+X170 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. wlp0s20f3 no wireless extensions. enx00e04f8238df no wireless extensions. MachineType: Dell Inc. Inspiron 16 5620 Package: linux-firmware 1.187.31 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1040-oem root=UUID=202d0ced-071f-4d95-a481-17b8e1078844 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1040.44-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1040-oem N/A linux-backports-modules-5.14.0-1040-oem N/A linux-firmware 1.187.31 Tags: focal Uname: Linux 5.14.0-1040-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0Q901G dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd04/21/2022:br1.1:svnDellInc.:pnInspiron165620:pvr:rvnDellInc.:rn0Q901G:rvrD02:cvnDellInc.:ct10:cvr:sku0BAA: dmi.product.family: Inspiron dmi.product.name: Inspiron 16 5620 dmi.product.sku: 0BAA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1977815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977815] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1977815/+attachment/5595241/+files/ProcInterrupts.txt -- 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/1977815 Title: ADLP AX211 iwlwifi firmware crash after resume Status in linux-firmware package in Ubuntu: New Bug description: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. wifi failed to connect after the below message. [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 [ 5525.555157] iwlwifi :00:14.3: 0x004D960E | interruptlink2 [ 5525.555160] iwlwifi :00:14.3: 0x004C6C34 | data1 [ 5525.555163] iwlwifi :00:14.3: 0x0100 | data2 [ 5525.555167] iwlwifi :00:14.3: 0x | data3 [ 5525.555170] iwlwifi :00:14.3: 0x1AC138AE | beacon time [ 5525.555174] iwlwifi :00:14.3: 0xFA1F775A | tsf low [ 5525.555177] iwlwifi :00:14.3: 0x0002 | tsf hi [ 5525.555181] iwlwifi :00:14.3: 0x | time gp1 [ 5525.555184] iwlwifi :00:14.3: 0x029BB566 | time gp2 [ 5525.555188] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 5525.555191] iwlwifi :00:14.3: 0x0043 | uCode version major [ 5525.555194] iwlwifi :00:14.3: 0x8F59B80B | uCode version minor [ 5525.555198] iwlwifi :00:14.3: 0x0370 | hw version [ 5525.555202] iwlwifi :00:14.3: 0x00489002 | board version --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-qyburn+X170 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. wlp0s20f3 no wireless extensions. enx00e04f8238df no wireless extensions. MachineType: Dell Inc. Inspiron 16 5620 Package: linux-firmware 1.187.31 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1040-oem root=UUID=202d0ced-071f-4d95-a481-17b8e1078844 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1040.44-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1040-oem N/A linux-backports-modules-5.14.0-1040-oem N/A linux-firmware 1.187.31 Tags: focal Uname: Linux 5.14.0-1040-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0Q901G dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd04/21/2022:br1.1:svnDellInc.:pnInspiron165620:pvr:rvnDellInc.:rn0Q901G:rvrD02:cvnDellInc.:ct10:cvr:sku0BAA: dmi.product.family: Inspiron dmi.product.name: Inspiron 16 5620 dmi.product.sku: 0BAA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1977815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977815] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1977815/+attachment/5595235/+files/Lsusb-t.txt -- 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/1977815 Title: ADLP AX211 iwlwifi firmware crash after resume Status in linux-firmware package in Ubuntu: New Bug description: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. wifi failed to connect after the below message. [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 [ 5525.555157] iwlwifi :00:14.3: 0x004D960E | interruptlink2 [ 5525.555160] iwlwifi :00:14.3: 0x004C6C34 | data1 [ 5525.555163] iwlwifi :00:14.3: 0x0100 | data2 [ 5525.555167] iwlwifi :00:14.3: 0x | data3 [ 5525.555170] iwlwifi :00:14.3: 0x1AC138AE | beacon time [ 5525.555174] iwlwifi :00:14.3: 0xFA1F775A | tsf low [ 5525.555177] iwlwifi :00:14.3: 0x0002 | tsf hi [ 5525.555181] iwlwifi :00:14.3: 0x | time gp1 [ 5525.555184] iwlwifi :00:14.3: 0x029BB566 | time gp2 [ 5525.555188] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 5525.555191] iwlwifi :00:14.3: 0x0043 | uCode version major [ 5525.555194] iwlwifi :00:14.3: 0x8F59B80B | uCode version minor [ 5525.555198] iwlwifi :00:14.3: 0x0370 | hw version [ 5525.555202] iwlwifi :00:14.3: 0x00489002 | board version --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-qyburn+X170 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. wlp0s20f3 no wireless extensions. enx00e04f8238df no wireless extensions. MachineType: Dell Inc. Inspiron 16 5620 Package: linux-firmware 1.187.31 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1040-oem root=UUID=202d0ced-071f-4d95-a481-17b8e1078844 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1040.44-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1040-oem N/A linux-backports-modules-5.14.0-1040-oem N/A linux-firmware 1.187.31 Tags: focal Uname: Linux 5.14.0-1040-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0Q901G dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd04/21/2022:br1.1:svnDellInc.:pnInspiron165620:pvr:rvnDellInc.:rn0Q901G:rvrD02:cvnDellInc.:ct10:cvr:sku0BAA: dmi.product.family: Inspiron dmi.product.name: Inspiron 16 5620 dmi.product.sku: 0BAA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1977815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977815] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1977815/+attachment/5595244/+files/PulseList.txt -- 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/1977815 Title: ADLP AX211 iwlwifi firmware crash after resume Status in linux-firmware package in Ubuntu: New Bug description: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. wifi failed to connect after the below message. [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 [ 5525.555157] iwlwifi :00:14.3: 0x004D960E | interruptlink2 [ 5525.555160] iwlwifi :00:14.3: 0x004C6C34 | data1 [ 5525.555163] iwlwifi :00:14.3: 0x0100 | data2 [ 5525.555167] iwlwifi :00:14.3: 0x | data3 [ 5525.555170] iwlwifi :00:14.3: 0x1AC138AE | beacon time [ 5525.555174] iwlwifi :00:14.3: 0xFA1F775A | tsf low [ 5525.555177] iwlwifi :00:14.3: 0x0002 | tsf hi [ 5525.555181] iwlwifi :00:14.3: 0x | time gp1 [ 5525.555184] iwlwifi :00:14.3: 0x029BB566 | time gp2 [ 5525.555188] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 5525.555191] iwlwifi :00:14.3: 0x0043 | uCode version major [ 5525.555194] iwlwifi :00:14.3: 0x8F59B80B | uCode version minor [ 5525.555198] iwlwifi :00:14.3: 0x0370 | hw version [ 5525.555202] iwlwifi :00:14.3: 0x00489002 | board version --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-qyburn+X170 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. wlp0s20f3 no wireless extensions. enx00e04f8238df no wireless extensions. MachineType: Dell Inc. Inspiron 16 5620 Package: linux-firmware 1.187.31 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1040-oem root=UUID=202d0ced-071f-4d95-a481-17b8e1078844 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1040.44-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1040-oem N/A linux-backports-modules-5.14.0-1040-oem N/A linux-firmware 1.187.31 Tags: focal Uname: Linux 5.14.0-1040-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0Q901G dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd04/21/2022:br1.1:svnDellInc.:pnInspiron165620:pvr:rvnDellInc.:rn0Q901G:rvrD02:cvnDellInc.:ct10:cvr:sku0BAA: dmi.product.family: Inspiron dmi.product.name: Inspiron 16 5620 dmi.product.sku: 0BAA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1977815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977815] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1977815/+attachment/5595238/+files/ProcCpuinfo.txt -- 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/1977815 Title: ADLP AX211 iwlwifi firmware crash after resume Status in linux-firmware package in Ubuntu: New Bug description: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. wifi failed to connect after the below message. [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 [ 5525.555157] iwlwifi :00:14.3: 0x004D960E | interruptlink2 [ 5525.555160] iwlwifi :00:14.3: 0x004C6C34 | data1 [ 5525.555163] iwlwifi :00:14.3: 0x0100 | data2 [ 5525.555167] iwlwifi :00:14.3: 0x | data3 [ 5525.555170] iwlwifi :00:14.3: 0x1AC138AE | beacon time [ 5525.555174] iwlwifi :00:14.3: 0xFA1F775A | tsf low [ 5525.555177] iwlwifi :00:14.3: 0x0002 | tsf hi [ 5525.555181] iwlwifi :00:14.3: 0x | time gp1 [ 5525.555184] iwlwifi :00:14.3: 0x029BB566 | time gp2 [ 5525.555188] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 5525.555191] iwlwifi :00:14.3: 0x0043 | uCode version major [ 5525.555194] iwlwifi :00:14.3: 0x8F59B80B | uCode version minor [ 5525.555198] iwlwifi :00:14.3: 0x0370 | hw version [ 5525.555202] iwlwifi :00:14.3: 0x00489002 | board version --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-qyburn+X170 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. wlp0s20f3 no wireless extensions. enx00e04f8238df no wireless extensions. MachineType: Dell Inc. Inspiron 16 5620 Package: linux-firmware 1.187.31 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1040-oem root=UUID=202d0ced-071f-4d95-a481-17b8e1078844 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1040.44-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1040-oem N/A linux-backports-modules-5.14.0-1040-oem N/A linux-firmware 1.187.31 Tags: focal Uname: Linux 5.14.0-1040-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0Q901G dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd04/21/2022:br1.1:svnDellInc.:pnInspiron165620:pvr:rvnDellInc.:rn0Q901G:rvrD02:cvnDellInc.:ct10:cvr:sku0BAA: dmi.product.family: Inspiron dmi.product.name: Inspiron 16 5620 dmi.product.sku: 0BAA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1977815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
Verified on kinetic with 5.19.0-42-generic, the issue is fixed. With kernel 5.19.0-40-generic: No HDMI audio output device $ cat /proc/asound/cards 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x200ffe31 irq 77 With kernel 5.19.0-42-generic: Sound output device shows "HDMI/DisplayPort3 - Ellesmere H" $ cat /proc/asound/cards 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x200ffe31 irq 77 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0x9e84 irq 78 Kernel: 5.19.0-42-generic Graphic: RX 580 -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977815] Re: ADLP AX211 iwlwifi firmware crash after resume
Invalid this bug due to the issue can not be reproduced after swap wifi module. ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- 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/1977815 Title: ADLP AX211 iwlwifi firmware crash after resume Status in linux-firmware package in Ubuntu: Invalid Bug description: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. wifi failed to connect after the below message. [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 [ 5525.555157] iwlwifi :00:14.3: 0x004D960E | interruptlink2 [ 5525.555160] iwlwifi :00:14.3: 0x004C6C34 | data1 [ 5525.555163] iwlwifi :00:14.3: 0x0100 | data2 [ 5525.555167] iwlwifi :00:14.3: 0x | data3 [ 5525.555170] iwlwifi :00:14.3: 0x1AC138AE | beacon time [ 5525.555174] iwlwifi :00:14.3: 0xFA1F775A | tsf low [ 5525.555177] iwlwifi :00:14.3: 0x0002 | tsf hi [ 5525.555181] iwlwifi :00:14.3: 0x | time gp1 [ 5525.555184] iwlwifi :00:14.3: 0x029BB566 | time gp2 [ 5525.555188] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 5525.555191] iwlwifi :00:14.3: 0x0043 | uCode version major [ 5525.555194] iwlwifi :00:14.3: 0x8F59B80B | uCode version minor [ 5525.555198] iwlwifi :00:14.3: 0x0370 | hw version [ 5525.555202] iwlwifi :00:14.3: 0x00489002 | board version --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-qyburn+X170 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. wlp0s20f3 no wireless extensions. enx00e04f8238df no wireless extensions. MachineType: Dell Inc. Inspiron 16 5620 Package: linux-firmware 1.187.31 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1040-oem root=UUID=202d0ced-071f-4d95-a481-17b8e1078844 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1040.44-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1040-oem N/A linux-backports-modules-5.14.0-1040-oem N/A linux-firmware 1.187.31 Tags: focal Uname: Linux 5.14.0-1040-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0Q901G dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd04/21/2022:br1.1:svnDellInc.:pnInspiron165620:pvr:rvnDellInc.:rn0Q901G:rvrD02:cvnDellInc.:ct10:cvr:sku0BAA: dmi.product.family: Inspiron dmi.product.name: Inspiron 16 5620 dmi.product.sku: 0BAA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1977815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
