[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-azure/5.19.0-1021.22)
All autopkgtests for the newly accepted linux-restricted-modules-azure (5.19.0-1021.22) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#linux-restricted-modules-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1988836] Autopkgtest regression report (linux-restricted-modules-azure/5.19.0-1021.22)
All autopkgtests for the newly accepted linux-restricted-modules-azure (5.19.0-1021.22) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#linux-restricted-modules-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 2007004] Re: rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected
Apport data collected on the same machine, running from vanilla Kubuntu 22.10 live USB Booted from live USB Connected mouse via BT - got an error Connected to WiFi Connected mouse via BT - success Disconnected from WiFi - Mouse goes to connect/disconnect loop Run apport-collect Reconnect WiFi Mouse working again ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/2007004 Title: rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. This problem occurs with the rtw88_8821ce driver Workaround was to blacklist rtw88_8821ce and install rtl8821ce When disconnecting from a WiFi network, or turning of WiFi altogether, or booting up at a location where there is no remembered WiFi connection, my bluetooth Logitech MX 2S freezes, then begins to rapidly disconnect/reconnect about 3-4 times a second. root@ithaca:~ # uname -a Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA v: 1.0 serial: Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, then about 10 seconds elapse, then the below messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1:
[Kernel-packages] [Bug 2007004] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2007004/+attachment/5647010/+files/WifiSyslog.txt -- 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/2007004 Title: rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. This problem occurs with the rtw88_8821ce driver Workaround was to blacklist rtw88_8821ce and install rtl8821ce When disconnecting from a WiFi network, or turning of WiFi altogether, or booting up at a location where there is no remembered WiFi connection, my bluetooth Logitech MX 2S freezes, then begins to rapidly disconnect/reconnect about 3-4 times a second. root@ithaca:~ # uname -a Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA v: 1.0 serial: Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, then about 10 seconds elapse, then the below messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2) Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0: sta
[Kernel-packages] [Bug 2007004] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2007004/+attachment/5647011/+files/acpidump.txt -- 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/2007004 Title: rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. This problem occurs with the rtw88_8821ce driver Workaround was to blacklist rtw88_8821ce and install rtl8821ce When disconnecting from a WiFi network, or turning of WiFi altogether, or booting up at a location where there is no remembered WiFi connection, my bluetooth Logitech MX 2S freezes, then begins to rapidly disconnect/reconnect about 3-4 times a second. root@ithaca:~ # uname -a Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA v: 1.0 serial: Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, then about 10 seconds elapse, then the below messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2) Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0: sta
[Kernel-packages] [Bug 2007004] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2007004/+attachment/5647009/+files/UdevDb.txt -- 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/2007004 Title: rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. This problem occurs with the rtw88_8821ce driver Workaround was to blacklist rtw88_8821ce and install rtl8821ce When disconnecting from a WiFi network, or turning of WiFi altogether, or booting up at a location where there is no remembered WiFi connection, my bluetooth Logitech MX 2S freezes, then begins to rapidly disconnect/reconnect about 3-4 times a second. root@ithaca:~ # uname -a Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA v: 1.0 serial: Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, then about 10 seconds elapse, then the below messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2) Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0: sta
[Kernel-packages] [Bug 2007004] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2007004/+attachment/5647008/+files/RfKill.txt -- 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/2007004 Title: rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. This problem occurs with the rtw88_8821ce driver Workaround was to blacklist rtw88_8821ce and install rtl8821ce When disconnecting from a WiFi network, or turning of WiFi altogether, or booting up at a location where there is no remembered WiFi connection, my bluetooth Logitech MX 2S freezes, then begins to rapidly disconnect/reconnect about 3-4 times a second. root@ithaca:~ # uname -a Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA v: 1.0 serial: Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, then about 10 seconds elapse, then the below messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2) Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0: sta
[Kernel-packages] [Bug 2007004] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2007004/+attachment/5647007/+files/ProcModules.txt -- 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/2007004 Title: rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. This problem occurs with the rtw88_8821ce driver Workaround was to blacklist rtw88_8821ce and install rtl8821ce When disconnecting from a WiFi network, or turning of WiFi altogether, or booting up at a location where there is no remembered WiFi connection, my bluetooth Logitech MX 2S freezes, then begins to rapidly disconnect/reconnect about 3-4 times a second. root@ithaca:~ # uname -a Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA v: 1.0 serial: Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, then about 10 seconds elapse, then the below messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2) Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0: sta
[Kernel-packages] [Bug 2007004] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2007004/+attachment/5647006/+files/ProcInterrupts.txt -- 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/2007004 Title: rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. This problem occurs with the rtw88_8821ce driver Workaround was to blacklist rtw88_8821ce and install rtl8821ce When disconnecting from a WiFi network, or turning of WiFi altogether, or booting up at a location where there is no remembered WiFi connection, my bluetooth Logitech MX 2S freezes, then begins to rapidly disconnect/reconnect about 3-4 times a second. root@ithaca:~ # uname -a Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA v: 1.0 serial: Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, then about 10 seconds elapse, then the below messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2) Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce
[Kernel-packages] [Bug 2007004] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2007004/+attachment/5647004/+files/ProcCpuinfoMinimal.txt -- 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/2007004 Title: rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. This problem occurs with the rtw88_8821ce driver Workaround was to blacklist rtw88_8821ce and install rtl8821ce When disconnecting from a WiFi network, or turning of WiFi altogether, or booting up at a location where there is no remembered WiFi connection, my bluetooth Logitech MX 2S freezes, then begins to rapidly disconnect/reconnect about 3-4 times a second. root@ithaca:~ # uname -a Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA v: 1.0 serial: Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, then about 10 seconds elapse, then the below messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2) Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce
[Kernel-packages] [Bug 2007004] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2007004/+attachment/5647002/+files/Lsusb-v.txt -- 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/2007004 Title: rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. This problem occurs with the rtw88_8821ce driver Workaround was to blacklist rtw88_8821ce and install rtl8821ce When disconnecting from a WiFi network, or turning of WiFi altogether, or booting up at a location where there is no remembered WiFi connection, my bluetooth Logitech MX 2S freezes, then begins to rapidly disconnect/reconnect about 3-4 times a second. root@ithaca:~ # uname -a Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA v: 1.0 serial: Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, then about 10 seconds elapse, then the below messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2) Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0: sta
[Kernel-packages] [Bug 2007004] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2007004/+attachment/5647005/+files/ProcEnviron.txt -- 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/2007004 Title: rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. This problem occurs with the rtw88_8821ce driver Workaround was to blacklist rtw88_8821ce and install rtl8821ce When disconnecting from a WiFi network, or turning of WiFi altogether, or booting up at a location where there is no remembered WiFi connection, my bluetooth Logitech MX 2S freezes, then begins to rapidly disconnect/reconnect about 3-4 times a second. root@ithaca:~ # uname -a Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA v: 1.0 serial: Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, then about 10 seconds elapse, then the below messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2) Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0:
[Kernel-packages] [Bug 2007004] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2007004/+attachment/5647003/+files/ProcCpuinfo.txt -- 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/2007004 Title: rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. This problem occurs with the rtw88_8821ce driver Workaround was to blacklist rtw88_8821ce and install rtl8821ce When disconnecting from a WiFi network, or turning of WiFi altogether, or booting up at a location where there is no remembered WiFi connection, my bluetooth Logitech MX 2S freezes, then begins to rapidly disconnect/reconnect about 3-4 times a second. root@ithaca:~ # uname -a Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA v: 1.0 serial: Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, then about 10 seconds elapse, then the below messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2) Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0:
[Kernel-packages] [Bug 2007004] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2007004/+attachment/5647000/+files/Lsusb.txt -- 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/2007004 Title: rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. This problem occurs with the rtw88_8821ce driver Workaround was to blacklist rtw88_8821ce and install rtl8821ce When disconnecting from a WiFi network, or turning of WiFi altogether, or booting up at a location where there is no remembered WiFi connection, my bluetooth Logitech MX 2S freezes, then begins to rapidly disconnect/reconnect about 3-4 times a second. root@ithaca:~ # uname -a Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA v: 1.0 serial: Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, then about 10 seconds elapse, then the below messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2) Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0: sta
[Kernel-packages] [Bug 2007004] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2007004/+attachment/5647001/+files/Lsusb-t.txt -- 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/2007004 Title: rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. This problem occurs with the rtw88_8821ce driver Workaround was to blacklist rtw88_8821ce and install rtl8821ce When disconnecting from a WiFi network, or turning of WiFi altogether, or booting up at a location where there is no remembered WiFi connection, my bluetooth Logitech MX 2S freezes, then begins to rapidly disconnect/reconnect about 3-4 times a second. root@ithaca:~ # uname -a Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA v: 1.0 serial: Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, then about 10 seconds elapse, then the below messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2) Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0: sta
[Kernel-packages] [Bug 2007004] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2007004/+attachment/5646999/+files/Lspci-vt.txt -- 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/2007004 Title: rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. This problem occurs with the rtw88_8821ce driver Workaround was to blacklist rtw88_8821ce and install rtl8821ce When disconnecting from a WiFi network, or turning of WiFi altogether, or booting up at a location where there is no remembered WiFi connection, my bluetooth Logitech MX 2S freezes, then begins to rapidly disconnect/reconnect about 3-4 times a second. root@ithaca:~ # uname -a Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA v: 1.0 serial: Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, then about 10 seconds elapse, then the below messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2) Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0: sta
[Kernel-packages] [Bug 2007004] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2007004/+attachment/5646998/+files/Lspci.txt -- 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/2007004 Title: rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. This problem occurs with the rtw88_8821ce driver Workaround was to blacklist rtw88_8821ce and install rtl8821ce When disconnecting from a WiFi network, or turning of WiFi altogether, or booting up at a location where there is no remembered WiFi connection, my bluetooth Logitech MX 2S freezes, then begins to rapidly disconnect/reconnect about 3-4 times a second. root@ithaca:~ # uname -a Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA v: 1.0 serial: Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, then about 10 seconds elapse, then the below messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2) Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0: sta
[Kernel-packages] [Bug 2007004] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2007004/+attachment/5646997/+files/IwConfig.txt -- 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/2007004 Title: rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. This problem occurs with the rtw88_8821ce driver Workaround was to blacklist rtw88_8821ce and install rtl8821ce When disconnecting from a WiFi network, or turning of WiFi altogether, or booting up at a location where there is no remembered WiFi connection, my bluetooth Logitech MX 2S freezes, then begins to rapidly disconnect/reconnect about 3-4 times a second. root@ithaca:~ # uname -a Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA v: 1.0 serial: Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, then about 10 seconds elapse, then the below messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2) Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0: sta
[Kernel-packages] [Bug 2007004] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2007004/+attachment/5646996/+files/CurrentDmesg.txt -- 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/2007004 Title: rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. This problem occurs with the rtw88_8821ce driver Workaround was to blacklist rtw88_8821ce and install rtl8821ce When disconnecting from a WiFi network, or turning of WiFi altogether, or booting up at a location where there is no remembered WiFi connection, my bluetooth Logitech MX 2S freezes, then begins to rapidly disconnect/reconnect about 3-4 times a second. root@ithaca:~ # uname -a Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA v: 1.0 serial: Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, then about 10 seconds elapse, then the below messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2) Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0:
[Kernel-packages] [Bug 2007004] Re: rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected
apport information ** Tags added: apport-collected kinetic ** Description changed: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. This problem occurs with the rtw88_8821ce driver Workaround was to blacklist rtw88_8821ce and install rtl8821ce When disconnecting from a WiFi network, or turning of WiFi altogether, or booting up at a location where there is no remembered WiFi connection, my bluetooth Logitech MX 2S freezes, then begins to rapidly disconnect/reconnect about 3-4 times a second. root@ithaca:~ # uname -a Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA v: 1.0 serial: Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, then about 10 seconds elapse, then the below messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2) Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx joined with macid 0 Feb 11 20:47:19 ithaca kernel: [ 3449.943789] wlo1: associated Feb 11 20:47:19 ithaca kernel: [ 3449.995269] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready Nothing logged in dmesg After reconnecting WiFi, everything works OK again. + --- + ProblemType: Bug + ApportVersion: 2.23.1-0ubuntu3 + Architecture:
[Kernel-packages] [Bug 1946433] Re: Can only reach PC3 when ethernet is plugged r8169
** Changed in: linux (Ubuntu Kinetic) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: AceLan Kao (acelankao) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1946433 Title: Can only reach PC3 when ethernet is plugged r8169 Status in HWE Next: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.13 source package in Kinetic: Invalid Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.13 source package in Lunar: Invalid Status in linux-oem-5.14 source package in Lunar: Invalid Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] System only can reach PC3, and it affects power consumption alot. [Fix] Kaiheng implemented a dynamic ASPM for r8169, it not only fixes the PC state issue, but also fixes network speed issue. V7: https://patchwork.kernel.org/project/netdevbpf/patch/20211016075442.650311-5-kai.heng.f...@canonical.com/ V6: https://patchwork.ozlabs.org/project/linux-pci/cover/20211007161552.272771-1-kai.heng.f...@canonical.com/ [Test] Verified on 2 different systems which has PC state issue and has network speed issue, these patches fix both issues. [Where problems could occur] It toggles ASPM on and off depends on the network traffic during runtime, I don't think it'll lead to any regressions. Some potential issues have been addressed during the patch submitting. It's v6 now and accepted by upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1946433/+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 2006955] Re: [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 5.15.0-58-generic works)
Also have a look in /etc/modprobe.d/ to see if the proprietary driver has left behind a config file that might be blacklisting the default amdgpu driver to prevent it loading. -- 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/2006955 Title: [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 5.15.0-58-generic works) Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors, but since very recently (yesterday or so), only 1 of them seems to be detected. In the Settings app, under "Screen Display", I used to have a place where I can move my monitors relatively to each other, and adjust each of their settings. Now, I no longer have the monitor drag-and-drop zone, I only have one detected "Unknown display", fixed at 1920x1080 77.00 Hz (physically, it's a 1920x1080 144Hz) and I cannot change any setting except orientation, scaling, and fractional scaling. The bug started happening just when the kernel was auto-updated to 5.15.0-60-generic from 5.15.0-58-generic. `uname -a` reports: `Linux user-desktop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux`. When I reboot with 5.15.0-58-generic, all of my 3 displays are detected and working fine. I also noticed the same problem happened when I installed 5.15.0-58-lowlatency. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 10 11:00:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-57-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-60-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1462:3816] InstallationDate: Installed on 2021-01-27 (743 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B550 Phantom Gaming 4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd08/13/2020:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006955/+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 2006955] Re: [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 5.15.0-58-generic works)
What I've heard from within Canonical is that the free AMD driver performs better than the proprietary one. So unless you have requirements other than performance, sticking to the default driver is best. > Is there a list of drivers that are automatically installed on a fresh Ubuntu install? Yes, but it's too long to be useful. The currently installed list is: find /lib/modules and you can reinstall them with: sudo apt install --reinstall linux-modules-5.15.0-60-generic linux- modules-extra-5.15.0-60-generic so that might resolve the issue after rebooting. -- 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/2006955 Title: [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 5.15.0-58-generic works) Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors, but since very recently (yesterday or so), only 1 of them seems to be detected. In the Settings app, under "Screen Display", I used to have a place where I can move my monitors relatively to each other, and adjust each of their settings. Now, I no longer have the monitor drag-and-drop zone, I only have one detected "Unknown display", fixed at 1920x1080 77.00 Hz (physically, it's a 1920x1080 144Hz) and I cannot change any setting except orientation, scaling, and fractional scaling. The bug started happening just when the kernel was auto-updated to 5.15.0-60-generic from 5.15.0-58-generic. `uname -a` reports: `Linux user-desktop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux`. When I reboot with 5.15.0-58-generic, all of my 3 displays are detected and working fine. I also noticed the same problem happened when I installed 5.15.0-58-lowlatency. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 10 11:00:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-57-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-60-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1462:3816] InstallationDate: Installed on 2021-01-27 (743 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B550 Phantom Gaming 4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd08/13/2020:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 2006955] Re: [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 5.15.0-58-generic works)
I've uninstalled them, ran sudo apt autoremove, and rebooted on 5.15.0-58; the error is unfortunately still here. I've also noted today that SuperTuxKart, which I could run flawlessly at maximum graphics settings prior to the bug, is now barely usable at the lowest settings and hangs within seconds. Is there a list of drivers that are automatically installed on a fresh Ubuntu install? I noticed that some mesa-related packages have been uninstalled in the process, so I'd like to check if it's just a default driver that has been uninstalled when installing the AMD driver. Are there resources on how to use Additional Drivers? I've been wanting to install AMD's drivers but the app always said "No additional drivers available" and I have no idea how to make it find proper drivers for my GPU, and all information I could find online is about installing manually. -- 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/2006955 Title: [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 5.15.0-58-generic works) Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors, but since very recently (yesterday or so), only 1 of them seems to be detected. In the Settings app, under "Screen Display", I used to have a place where I can move my monitors relatively to each other, and adjust each of their settings. Now, I no longer have the monitor drag-and-drop zone, I only have one detected "Unknown display", fixed at 1920x1080 77.00 Hz (physically, it's a 1920x1080 144Hz) and I cannot change any setting except orientation, scaling, and fractional scaling. The bug started happening just when the kernel was auto-updated to 5.15.0-60-generic from 5.15.0-58-generic. `uname -a` reports: `Linux user-desktop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux`. When I reboot with 5.15.0-58-generic, all of my 3 displays are detected and working fine. I also noticed the same problem happened when I installed 5.15.0-58-lowlatency. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 10 11:00:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-57-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-60-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1462:3816] InstallationDate: Installed on 2021-01-27 (743 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B550 Phantom Gaming 4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd08/13/2020:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage
[Kernel-packages] [Bug 2007173] Re: i915: loss of the screen connected in DP to my dockstation
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2007173 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Please note: `ubuntu-bug`, `apport` & bug reporting tools are provided with Ubuntu by default, many require manual addition for some releases of downstream OSes based on Ubuntu (eg. Linux Mint). You should check with your distribution first. (If apport-collect isn't completed; this bug may not be able to be explored until it's encountered on a system where apport tools are used in the bug report, where by this report can provide the confirmation (ie. this reported marked as duplicate of the report thus this is the confirmationl)) -- 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/2007173 Title: i915: loss of the screen connected in DP to my dockstation Status in linux package in Ubuntu: Confirmed Bug description: Since a few versions of the kernel I'm losing the screen connected to my dockstation thinkpad using displayport. My running laptop is a thinkpad T14s I'm currently running "Linux laptop 5.19.0-28-generic #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 15 12:05:40 UTC 2 x86_64 x86_64 x86_64 GNU/Linux" but I had the same issue while running "linux-image-5.15.0-60-generic" and I think with "linux-image-5.15.0-58-generic" too. When losing the screen, I'm getting "i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful" from the kernel. During the last screen loss, I tried to connect the DisplayPort to another screen to eliminate the possibility that it could be a issue with it. Not only did the other screen not work either, but I got the following stacktrace: 17957.541801] CPU: 3 PID: 30705 Comm: kworker/3:1 Tainted: G U 5.19.0-28-generic #29~22.04.1-Ubuntu [17957.541811] Hardware name: LENOVO 20T1S62300/20T1S62300, BIOS N2YET34W (1.23 ) 12/31/2021 [17957.541816] Workqueue: events i915_hotplug_work_func [i915] [17957.542099] RIP: 0010:intel_dp_prep_link_retrain+0x1b0/0x1d0 [i915] [17957.542378] Code: d2 74 32 48 89 55 a8 4c 89 4d b0 e8 1a 86 f3 f5 48 8b 55 a8 48 c7 c1 50 7c b0 c0 48 c7 c7 e6 00 ae c0 48 89 c6 e8 87 5a 41 f6 <0f> 0b 4c 8b 4d b0 e9 36 ff ff ff 48 8b 17 eb c9 e8 ab bc 4d f6 e9 [17957.542385] RSP: 0018:b27bc6677cb0 EFLAGS: 00010246 [17957.542393] RAX: RBX: 9d6da9ef26c0 RCX: [17957.542398] RDX: RSI: RDI: [17957.542401] RBP: b27bc6677d08 R08: R09: [17957.542405] R10: R11: R12: 9d6c99894170 [17957.542409] R13: b27bc6677d27 R14: b27bc6677d70 R15: 9d6ca032c800 [17957.542414] FS: () GS:9d73ad6c() knlGS: [17957.542420] CS: 0010 DS: ES: CR0: 80050033 [17957.542425] CR2: 170804379000 CR3: 000792010005 CR4: 003706e0 [17957.542431] DR0: DR1: DR2: [17957.542434] DR3: DR6: fffe0ff0 DR7: 0400 [17957.542439] Call Trace: [17957.542443] [17957.542453] intel_dp_retrain_link+0xee/0x2f0 [i915] [17957.542773] intel_ddi_hotplug+0xc6/0x1f0 [i915] [17957.543049] i915_hotplug_work_func+0x1f3/0x320 [i915] [17957.543316] process_one_work+0x222/0x400 [17957.543327] worker_thread+0x50/0x3e0 [17957.543334] ? rescuer_thread+0x3c0/0x3c0 [17957.543340] kthread+0xe6/0x110 [17957.543349] ? kthread_complete_and_exit+0x20/0x20 [17957.543359] ret_from_fork+0x1f/0x30 [17957.543374] [17957.543377] ---[ end trace ]--- [17985.975481] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [17991.187501] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful Distrib is : "lsb_release -rd Description: Linux Mint 21 Release: 21" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007173/+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 2007219] [NEW] xfs: Preallocated ioend transactions cause deadlock due to log buffer exhaustion
Public bug reported: BugLink: https://bugs.launchpad.net/bugs/2007219 [Impact] A deadlock exists in the XFS filesystem that occurs when the XFS log buffer becomes completely exhausted. XFS maintains a circular ring buffer for the log, and it is a fixed size. To be able to create a transaction, you need to be able to reserve space on the log buffer. Certain ioend transactions, such as file append, can be preallocated for a negligible performance gain. This takes up space in the log buffer, and these preallocated ioends are placed on a workqueue, behind other ioends that are not preallocated. The deadlock occurs when the XFS log buffer is running low on space, and an ioend append transaction comes in. It is preallocated, consuming nearly all of the remaining XFS log buffer space, and is placed at the very end of the ioend workqueue. The kernel then takes a ioend from the top of the ioend workqeueue, creates a transaction, xfs_trans_alloc(), attempts to allocate space for it, xfs_trans_reserve(), xfs_log_reserve(), and then waits in a while loop checking free space in the log, xlog_grant_head_check(), xlog_grant_head_wait(). Since there is no space, the thread sleeps with schedule(). This happens with all ioend transactions, since the log is exhausted and I/O is not moving. Since I/O never moves, the thread is never woken up, and we get hung task timeouts, with system failure shortly afterward. An example hung task timeout is: INFO: task kworker/60:0:4002982 blocked for more than 360 seconds. Tainted: G OE 5.4.0-137-generic #154-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. kworker/60:0D0 4002982 2 0x90004080 Workqueue: xfs-conv/dm-3 xfs_end_io [xfs] Call Trace: __schedule+0x2e3/0x740 schedule+0x42/0xb0 xlog_grant_head_wait+0xb9/0x1e0 [xfs] xlog_grant_head_check+0xde/0x100 [xfs] xfs_log_reserve+0xc9/0x1e0 [xfs] xfs_trans_reserve+0x17a/0x1e0 [xfs] xfs_trans_alloc+0xda/0x170 [xfs] xfs_iomap_write_unwritten+0x128/0x2f0 [xfs] xfs_end_ioend+0x15b/0x1b0 [xfs] xfs_end_io+0xb1/0xe0 [xfs] process_one_work+0x1eb/0x3b0 worker_thread+0x4d/0x400 kthread+0x104/0x140 ? process_one_work+0x3b0/0x3b0 ? kthread_park+0x90/0x90 ret_from_fork+0x1f/0x40 There is no known workaround, other than to have a larger log buffer at filesystem creation, but even then, it only buys you time until you get high enough load to exhaust the log buffer. [Fix] This was fixed in 5.13-rc1 by the following patch: commit 7cd3099f4925d7c15887d1940ebd65acd66100f5 Author: Brian Foster Date: Fri Apr 9 10:27:43 2021 -0700 Subject: xfs: drop submit side trans alloc for append ioends Link: https://github.com/torvalds/linux/commit/7cd3099f4925d7c15887d1940ebd65acd66100f5 The patch more or less removes all preallocated ioend transactions, and instead, when ioend appends are needed, they go to the standard workqueue like any other ioend, where transactions are allocated when they reach the top of the workqueue. The patch required some backporting for Focal. The changes to the patch itself is minimal and should be straightforward to read, however, the changes to the XFS ioend subsystem between 5.4 and 5.13-rc1 were quite extreme, with a lot of refactoring taking place over very many commits. Additionally, the patch was part of a five part series, the first, fixes the deadlock, and the rest remove all the code to do with transaction preallocation. It is safe to leave the rest of the code in place. It will become dead code, but it will not be reachable, and not cause any risk of regression, due to ioend->io_append_trans always being NULL, and not entering into any of the if statements. [Testcase] There is currently no known testcase for this issue. The issue has only been seen in a customer production environment, running under heavy load. The issue has not been seen in a customer test environment, only production. The production workload is a busy Kubernetes cluster running containers and VMs, with the hosts's filesystem being broken into separate mountpoints over several partitions, all XFS. The kubernetes containers are all backed from a large 4TB disk which is XFS. A test kernel is available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf353709-test This test kernel has been deployed to several production hosts, and the deadlock no longer occurs. [Where problems can occur] We are changing how certain ioend transactions take place in the XFS filesystem. If a regression were to occur, it would impact all XFS users. Users would have to downgrade their kernel, as there are no workarounds for enabling or disabling the behaviour change. The overall risk of the change should be low. ioend append transactions would still be processed in nearly the same way, still being placed at the end of the ioend workqueue like any other transaction, with the only change being it is allocated at the time the transaction is created, at the top
[Kernel-packages] [Bug 2006994] Re: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep
Similar behaivour started recently on my Lenovo V330. Presumably introduced by one of the updates. -- 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/2006994 Title: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep Scenario: Fresh and clean Ubuntu 22.10 install on Latitude 7390, requiring nomodeset kernel boot option to be added in GRUB at boot time when booting from USB stick. This can be achieved by following instructions from here: https://www.dell.com/support/kbdoc/en-uk/000123893/manual- nomodeset-kernel-boot-line-option-for-linux-booting Then, nomodeset needs to be permanently added to /etc/default/grub Followed instructions from https://askubuntu.com/questions/38780/how-do-i-set-nomodeset-after-ive-already-installed-ubuntu If nomodeset is not added, Dell Latitude 7390 will freeze at one point or another, either before reaching the Gnome desktop, either little after. This is the case with both, installing Ubuntu 22.10 from Live USB and running Ubuntu 22.10 after install the install (and having the USB stick disconnected). The issue after having Ubuntu 22.10 installed on Dell Latitude 7390 and having nomodeset permanently added to GRUB for each boot is: If by chance the system goes into sleep, after waking up, there is a totally pitch-black screen; nothing shows up, no screen backlight either. However, caps-lock works and I am able to log in to the system via ssh and can see the system is up an running well. I can even issue a request to send the system to sleep by “sudo systemctl suspend” and then wake the the system up several times without loosing ssh access, however, the screen will remain pitch-black. Other tries to troubleshoot and see if the system can be brought back with a working display (while nomodeset kernel option is being used): 1. sudo systemctl suspend -i >>> this will result in an unusable system after waking up, again, with a pitch-black screen; moreover, the caps-lock would not work, the keyboard backlight won’t work, ssh won’t work; I need a hard reset to get the system back up. 2. start the system in single user mode by inserting “single” in GRUB at boot time; >>> the system will be unusable after waking up, same as in try 1. 3. after a normal boot into the GNOME desktop with kernel nomodeset option and investigating the dmesg for any acpi, no error could be found. Tried to read up on other possible solutions, while stumbled upon the ubuntu wiki page below: https://wiki.ubuntu.com/UnderstandingSuspend Unfortunately, to not much help so far. Other notes: N1. All the above were done by having the latest BIOS v1.30.0 N2. This laptop came with Windows 10 Pro which works fine: goes into suspend and wakes up fine, with working screen and display. N3. Dell Latitude 7390 was released on 15 Feb 2018 ( source: https://www.laptoparena.net/dell/notebook-dell-latitude-7390-n025l739013emea-black-12984 ) and the user manual states it has support for Ubuntu. Therefore, other older and major Ubuntu versions were given a try, along with a new version of Fedora: N3.1 – Ubuntu 22.04 N3.2 – Ubuntu 18.04.6 N3.3 – Ubuntu 16.04.7 N3.4 – Fedora-Workstation-Live-x86_64-37-1.7 Each of the above will freeze at one point or another if nomodeset is not used, except the Ubuntu 18.04.6 and Ubuntu 16.04.7 which will run well and install well from the USB Live stick and will also run fine after the install, until the system goes into sleep, after which, when the system is awake, the screen is black and will have nothing displayed. Any advice will be appreciated. Thank you! ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tuser 2832 F wireplumber /dev/snd/seq:tuser 2829 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 11 13:37:59 2023 InstallationDate: Installed on 2023-01-15 (27 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.15/5.15.0.66.73~20.04.27)
All autopkgtests for the newly accepted linux-meta-hwe-5.15 (5.15.0.66.73~20.04.27) for focal have finished running. The following regressions have been reported in tests triggered by the package: dpdk/19.11.13-0ubuntu0.20.04.1 (amd64) evdi/1.9.1-1ubuntu4~20.04.2 (amd64) lxc/1:4.0.12-0ubuntu1~20.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-hwe-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 2006955] Re: [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 5.15.0-58-generic works)
It sounds like the bug has been caused by those packages. Yes I would remove them. Please be sure to only install 3rd party drivers using the 'Additional Drivers' app. Installing them manually can lead to unique bugs like this one. -- 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/2006955 Title: [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 5.15.0-58-generic works) Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors, but since very recently (yesterday or so), only 1 of them seems to be detected. In the Settings app, under "Screen Display", I used to have a place where I can move my monitors relatively to each other, and adjust each of their settings. Now, I no longer have the monitor drag-and-drop zone, I only have one detected "Unknown display", fixed at 1920x1080 77.00 Hz (physically, it's a 1920x1080 144Hz) and I cannot change any setting except orientation, scaling, and fractional scaling. The bug started happening just when the kernel was auto-updated to 5.15.0-60-generic from 5.15.0-58-generic. `uname -a` reports: `Linux user-desktop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux`. When I reboot with 5.15.0-58-generic, all of my 3 displays are detected and working fine. I also noticed the same problem happened when I installed 5.15.0-58-lowlatency. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 10 11:00:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-57-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-60-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1462:3816] InstallationDate: Installed on 2021-01-27 (743 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B550 Phantom Gaming 4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd08/13/2020:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006955/+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 2001618] Re: BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9
We don't have PowerPC for riscv / azure. ** 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/2001618 Title: BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] The BPF_AND, BPF_OR, BPF_XOR, BPF_FETCH, BPF_XCHG and BPF_CMPXCHG related tests will fail in net:test_bpf test from ubuntu_kernel_selftests as they are not supported. test_bpf: #361 BPF_ATOMIC | BPF_W, BPF_AND: Test: 0x12 & 0xab = 0x02 eBPF filter atomic op code c3 (@3) unsupported FAIL to select_runtime err=-524 ... test_bpf: #365 BPF_ATOMIC | BPF_W, BPF_AND | BPF_FETCH: Test: 0x12 & 0xab = 0x02 eBPF filter atomic op code c3 (@3) unsupported FAIL to select_runtime err=-524 ... test_bpf: #377 BPF_ATOMIC | BPF_W, BPF_OR: Test: 0x12 | 0xab = 0xbb FAIL to select_runtime err=-524 ... test_bpf: #393 BPF_ATOMIC | BPF_W, BPF_XOR: Test: 0x12 ^ 0xab = 0xb9 FAIL to select_runtime err=-524 ... test_bpf: #409 BPF_ATOMIC | BPF_W, BPF_XCHG: Test: 0x12 xchg 0xab = 0xab eBPF filter atomic op code c3 (@3) unsupported FAIL to select_runtime err=-524 ... test_bpf: #417 BPF_ATOMIC | BPF_W, BPF_CMPXCHG: Test successful return eBPF filter atomic op code c3 (@3) unsupported FAIL to select_runtime err=-524 ... test_bpf: Summary: 894 PASSED, 132 FAILED, [882/882 JIT'ed] Please find attachment for the complete test log. [Fix] * 6511270911 powerpc/bpf/64: add support for BPF_ATOMIC bitwise operations * dbe6e2456f powerpc/bpf/64: add support for atomic fetch operations * 1e82dfaa78 powerpc/bpf/64: Add instructions for atomic_[cmp]xchg These patches can be cherry-picked into Kinetic kernel. [Test] Test kernel can be found here: https://people.canonical.com/~phlin/kernel/lp-2001618-ppcbpf/ Steps: 1. Reboot with the patched kernel 2. Run: sudo dmesg -C sudo modprobe test_bpf sudo dmesg Tested with Power9 node baltar, with the patched kernel there will be no failure reported by the test_bpf: test_bpf: Summary: 1026 PASSED, 0 FAILED, [1014/1014 JIT'ed] [Where problems could occur] This patchset just broaden the BPF operations support on ppc64, we might see some new failures when using these instruction somewhere in the future. Cascardo: The existing atomic operations may regress as well, since they now produce different code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2001618/+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 2007193] [NEW] One Dell machine won't auto login after installing nvidia-driver-525.85.05
Public bug reported: During the NV driver SRU testing, I found an issue on one dell machine(https://certification.canonical.com/hardware/202004-27810/). After installing the latest driver(525.85.05) in proposed, the system won't auto login anymore. I tried many times using reboot command. Please check journal log in attachment. ** Affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journal.log.27810" https://bugs.launchpad.net/bugs/2007193/+attachment/5646900/+files/journal.log.27810 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2007193 Title: One Dell machine won't auto login after installing nvidia- driver-525.85.05 Status in nvidia-graphics-drivers-525 package in Ubuntu: New Bug description: During the NV driver SRU testing, I found an issue on one dell machine(https://certification.canonical.com/hardware/202004-27810/). After installing the latest driver(525.85.05) in proposed, the system won't auto login anymore. I tried many times using reboot command. Please check journal log in attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2007193/+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 2006797] Re: MT7922 firmware not working
Sadly this changes nothing. The timeout in dmesg persist. Also tried 6.1 and 6.2 kernel without success. ** Attachment added: "modinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006797/+attachment/5646874/+files/modinfo.txt -- 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/2006797 Title: MT7922 firmware not working Status in linux package in Ubuntu: Confirmed Bug description: Hey I have a "ASUS ROG Strix B650-A Gaming WIFI" (https://rog.asus.com/motherboards/rog-strix/rog-strix-b650-a-gaming- wifi-model/) Motherboard and the WiFi/Bluetooth is not working. On windows, the module is working fine. Using "Kubuntu 22.10" with Kernel "5.19.0-35-generic" lshw -class network: *-network description: Network controller product: MT7922 802.11ax PCI Express Wireless Network Adapter vendor: MEDIATEK Corp. physical id: 0 bus info: pci@:0b:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm bus_master cap_list configuration: driver=mt7921e latency=0 resources: iomemory:fc0-fbf irq:119 memory:fc3030-fc303f memory:fc50-fc507fff #dmesg | grep mt7921e [ 17.001057] mt7921e :0b:00.0: enabling device ( -> 0002) [ 17.001199] mt7921e :0b:00.0: ASIC revision: 79220010 [ 20.247369] mt7921e :0b:00.0: Message 0004008a (seq 1) timeout [ 23.575534] mt7921e :0b:00.0: Message 0004008a (seq 2) timeout [ 26.907372] mt7921e :0b:00.0: Message 0004008a (seq 3) timeout [ 30.231376] mt7921e :0b:00.0: Message 0004008a (seq 4) timeout [ 33.559704] mt7921e :0b:00.0: Message 0004008a (seq 5) timeout [ 36.887365] mt7921e :0b:00.0: Message 0004008a (seq 6) timeout [ 40.215367] mt7921e :0b:00.0: Message 0004008a (seq 7) timeout [ 43.543670] mt7921e :0b:00.0: Message 0004008a (seq 8) timeout [ 46.871378] mt7921e :0b:00.0: Message 0004008a (seq 9) timeout [ 50.199714] mt7921e :0b:00.0: Message 0004008a (seq 10) timeout [ 50.280219] mt7921e :0b:00.0: hardware init failed ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Feb 10 03:33:02 2023 InstallationDate: Installed on 2023-02-09 (0 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: ASUS System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-35-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022 dmi.bios.release: 8.23 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0823 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B650-A GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0823:bd11/21/2022:br8.23:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB650-AGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006797/+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 1968310] Re: arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K
This bug is awaiting verification that the linux-oem-5.17/5.17.0-1028.29 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-5.17 verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1968310 Title: arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-hwe-5.17 source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-hwe-5.17 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In selftests: net: arp_ndisc_evict_nocarrier.sh, even all of the sub-tests from this script have passed, the overall test result is still a fail. # selftests: net: arp_ndisc_evict_nocarrier.sh # run arp_evict_nocarrier=1 test # ok # run arp_evict_nocarrier=0 test # ok # run all.arp_evict_nocarrier=0 test # ok # run ndisc_evict_nocarrier=1 test # ok # run ndisc_evict_nocarrier=0 test # ok # run all.ndisc_evict_nocarrier=0 test # ok not ok 1 selftests: net: arp_ndisc_evict_nocarrier.sh # exit=255 This is caused by the cleanup() in the script, as it's trying to access a non-existing file. [Fix] * 9c4d7f45d6 selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier This patch can be cherry-picked into all affected kernels. [Test] Run the patched test and the test will pass. [Where problems could occur] Change limited to testing tools, no impact to real kernel function or test performances. [Original Bug Report] Issue found on Jammy OEM 5.17.0-1003.3 It looks like all the sub-tests has passed, but the final return value is not 0. Running 'make run_tests -C net TEST_PROGS=arp_ndisc_evict_nocarrier.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' TAP version 13 1..1 # selftests: net: arp_ndisc_evict_nocarrier.sh # run arp_evict_nocarrier=1 test # ok # run arp_evict_nocarrier=0 test # ok # run all.arp_evict_nocarrier=0 test # ok # run ndisc_evict_nocarrier=1 test # ok # run ndisc_evict_nocarrier=0 test # ok # run all.ndisc_evict_nocarrier=0 test # ok not ok 1 selftests: net: arp_ndisc_evict_nocarrier.sh # exit=255 make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968310/+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 2006546] Re: Improve arp_ndisc_evict_nocarrier.sh test result processing
This bug is awaiting verification that the linux-oem-5.17/5.17.0-1028.29 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-5.17 verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2006546 Title: Improve arp_ndisc_evict_nocarrier.sh test result processing Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Bug description: [Impact] The arp_ndisc_evict_nocarrier.sh in selftests/net didn't pass a proper return value for failed test cases. Thus we might get false negatives if the last command runs successfully. [Fix] * 1856628baa selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier This patch can be cherry-picked into affected kernels. Lunar has been patched already. J-hwe-5.17 will be deprecated thus it will be skipped. [Test] Run the patched test, this should not cause any regression as sub tests are good with our kernels (except there is a cleanup issue in bug 1968310) One can deliberately fail a test by hijacking the if statement for the return value check to make sure this patch is working as expected. [Where problems could occur] This patch improves the result interpretation, we might see new failures being reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006546/+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 1914774] Re: Some derivative kernel tools packages don't depend on linux-tools-common
This bug is awaiting verification that the linux-ibm/5.4.0-1045.50 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-ibm verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1914774 Title: Some derivative kernel tools packages don't depend on linux-tools- common Status in linux-hwe-5.4 package in Ubuntu: Invalid Status in linux-ibm package in Ubuntu: Invalid Status in linux-ibm-5.4 package in Ubuntu: Invalid Status in linux-hwe-5.4 source package in Bionic: Fix Committed Status in linux-ibm-5.4 source package in Bionic: Fix Committed Status in linux-ibm source package in Focal: Fix Committed Status in linux-ibm source package in Jammy: Fix Committed Status in linux-ibm source package in Kinetic: Fix Committed Bug description: [Impact] Installing the tools package for some kernels, like linux-tools- generic-hwe-18.04, does not install linux-tools-common because of a missing dependency. This results in missing /usr/bin/* wrapper scripts that call the version dependent binaries (like cpupower). [Test Case] Install like linux-tools-generic-hwe-18.04 on bionic and: $ cpupower cpupower: command not found [Fix] Add linux-tools-common as a dependency. [Regression Potential] The fix results in an additional package being installed. If something goes wrong this would manifest itself as a package installation error. [Original Description] While running kernel 5.4.0-64 today on bionic I noticed that Canonical kernel team does not provide a linux-hwe-5.4-tools package. Is that a deliberate choice? If so, would you please share the reason? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1914774/+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 1987998] Re: LSM: Configuring Too Many LSMs Causes Kernel Panic on Boot
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1012.12 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987998 Title: LSM: Configuring Too Many LSMs Causes Kernel Panic on Boot Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/1987998 [Impact] The Ubuntu kernel carries an out of tree patchet, known as "LSM: Module stacking for AppArmor" upstream, to enable stackable LSMs for containers. The revision the Ubuntu kernel carries is an older one, from 2020, and has some slight divergences from the latest revision in development. One such divergence, is support for Landlock as a stackable LSM. When the stackable LSM patchset was applied, Landlock was still in development and not mainlined yet, and wasn't present in the earlier revision of the "LSM: Module stacking for AppArmor" patchset. Support for this was added by us. There was a minor omission made during enabling support for Landlock. The LSM slot type was marked as LSMBLOB_NEEDED, when it should have been LSMBLOB_NOT_NEEDED. Landlock itself does not provide any of the hooks that use a struct lsmblob, such as secid_to_secctx, secctx_to_secid, inode_getsecid, cred_getsecid, kernel_act_as task_getsecid_subj task_getsecid_obj and ipc_getsecid. When we set .slot = LSMBLOB_NEEDED, this indicates that we need an entry in struct lsmblob, and we need to increment LSMBLOB_ENTRIES by one to fit the entry into the secid array: #define LSMBLOB_ENTRIES ( \ (IS_ENABLED(CONFIG_SECURITY_SELINUX) ? 1 : 0) + \ (IS_ENABLED(CONFIG_SECURITY_SMACK) ? 1 : 0) + \ (IS_ENABLED(CONFIG_SECURITY_APPARMOR) ? 1 : 0) + \ (IS_ENABLED(CONFIG_BPF_LSM) ? 1 : 0)) struct lsmblob { u32 secid[LSMBLOB_ENTRIES]; }; Currently, we don't increment LSMBLOB_ENTRIES by one to make an entry for Landlock, so for the Ubuntu kernel, we can fit a maximum of two entries, one for Apparmor and one for bpf. If you try and configure three LSMs like so and reboot: GRUB_CMDLINE_LINUX_DEFAULT="lsm=landlock,bpf,apparmor" You will receive the following panic: LSM: Security Framework initializing landlock: Up and running. LSM support for eBPF active Kernel panic - not syncing: security_add_hooks Too many LSMs registered. CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-46-generic #49-Ubuntu Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 panic+0x149/0x321 security_add_hooks+0x45/0x13a apparmor_init+0x189/0x1ef initialize_lsm+0x54/0x74 ordered_lsm_init+0x379/0x392 security_init+0x40/0x49 start_kernel+0x466/0x4dc x86_64_start_reservations+0x24/0x2a x86_64_start_kernel+0xe4/0xef secondary_startup_64_no_verify+0xc2/0xcb ---[ end Kernel panic - not syncing: security_add_hooks Too many LSMs registered. ]--- There is a check added in security_add_hooks() that makes sure that you cannot configure too many LSMs: if (lsmid->slot == LSMBLOB_NEEDED) { if (lsm_slot >= LSMBLOB_ENTRIES) panic("%s Too many LSMs registered.\n", __func__); lsmid->slot = lsm_slot++; init_debug("%s assigned lsmblob slot %d\n", lsmid->lsm, lsmid->slot); } A workaround is to enable no more than 2 LSMs until this is fixed. [Fix] If you read the following mailing list thread on linux-security- modules from May 2021: https://lore.kernel.org/selinux/202105141224.942DE93@keescook/T/ It is explained that Landlock does not provide any of the hooks that use a struct lsmblob, such as secid_to_secctx, secctx_to_secid, inode_getsecid, cred_getsecid, kernel_act_as task_getsecid_subj task_getsecid_obj and ipc_getsecid. I verified this with: ubuntu-jammy$ grep -Rin "secid_to_secctx" security/landlock/ ubuntu-jammy$ grep -Rin "secctx_to_secid"
[Kernel-packages] [Bug 1995886] Re: vmxnet3: update to latest ToT
Hello Tim, Team, Can I get an update on this? Thanks, Ronak -- 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/1995886 Title: vmxnet3: update to latest ToT Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: New Status in linux source package in Kinetic: New Bug description: This request is to port vmxnet3 patches to Ubuntu kernel. Below are the commits in order: vmxnet3: prepare for version 7 changes https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=55f0395fcace9e675af2cbb96015ce1ae8856806 vmxnet3: add support for capability registers https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=6f91f4ba046e5de6a6e579620b32b8ecf56873f7 vmxnet3: add support for large passthrough BAR register https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=543fb67405410cc548a72d7a9a4087688d2f56ac vmxnet3: add support for out of order rx completion https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=2c5a5748105a6bb901579d365c6f93e79f282b69 vmxnet3: add command to set ring buffer sizes https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=c7112ebd27ea0dbe4eecd5c96cad93757e34e73d vmxnet3: limit number of TXDs used for TSO packet https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=d2857b99a74b082368ee80f359372faa1d051043 vmxnet3: use ext1 field to indicate encapsulated packet https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=60cafa0395c2bed44d13277ed328317ed16a58c0 vmxnet3: update to version 7 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=acc38e041bd304621d4f59cea4849747d13bba9c vmxnet3: disable overlay offloads if UPT device does not support https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=a56b158a5078b8120d3d72fc9fd44efed5123b12 vmxnet3: do not reschedule napi for rx processing https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/vmxnet3?id=5b91884bf50b21d34bd3daa5c8f8b7e92e0a2c46 This is a request to bring latest Ubuntu LTS releases' vmxnet3 driver up to date with ToT Linux kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995886/+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 1995886] Re: vmxnet3: update to latest ToT
Hello Team, Can I get an update on this? Thanks, Ronak -- 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/1995886 Title: vmxnet3: update to latest ToT Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: New Status in linux source package in Kinetic: New Bug description: This request is to port vmxnet3 patches to Ubuntu kernel. Below are the commits in order: vmxnet3: prepare for version 7 changes https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=55f0395fcace9e675af2cbb96015ce1ae8856806 vmxnet3: add support for capability registers https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=6f91f4ba046e5de6a6e579620b32b8ecf56873f7 vmxnet3: add support for large passthrough BAR register https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=543fb67405410cc548a72d7a9a4087688d2f56ac vmxnet3: add support for out of order rx completion https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=2c5a5748105a6bb901579d365c6f93e79f282b69 vmxnet3: add command to set ring buffer sizes https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=c7112ebd27ea0dbe4eecd5c96cad93757e34e73d vmxnet3: limit number of TXDs used for TSO packet https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=d2857b99a74b082368ee80f359372faa1d051043 vmxnet3: use ext1 field to indicate encapsulated packet https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=60cafa0395c2bed44d13277ed328317ed16a58c0 vmxnet3: update to version 7 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=acc38e041bd304621d4f59cea4849747d13bba9c vmxnet3: disable overlay offloads if UPT device does not support https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/vmxnet3?id=a56b158a5078b8120d3d72fc9fd44efed5123b12 vmxnet3: do not reschedule napi for rx processing https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/vmxnet3?id=5b91884bf50b21d34bd3daa5c8f8b7e92e0a2c46 This is a request to bring latest Ubuntu LTS releases' vmxnet3 driver up to date with ToT Linux kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995886/+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 2007179] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/2007179 Title: touchpad not recognized, touchpad settings missing ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Bug description: ubuntu-bug linux glenn@glenn-IdeaPad-Flex-5-14ALC7:~$ cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=a70210 83803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:10/LNXVIDEO:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:14.3/PNP0C09:00/VPC2004:00/input/input4 U: Uniq= H: Handlers=rfkill kbd event4 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=30c9 Product=0030 Version=0006 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:04:00.3-4/button S: Sysfs=/devices/pci:00/:00:08.1/:04:00.3/usb1/1-4/1-4:1.0/input/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:04:00.1/sound/card0/input6 U: Uniq= H: Handlers=event6 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:04:00.1/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic Headset Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:04:00.6/sound/card1/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:04:00.6/sound/card1/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0003 Vendor=1bcf Product=0007 Version=0110 N: Name="USB Optical Mouse" P: Phys=usb-:04:00.3-2/input0 S: Sysfs=/devices/pci:00/:00:08.1/:04:00.3/usb1/1-2/1-2:1.0/0003:1BCF:0007.0003/input/input12 U: Uniq= H: Handlers=mouse0 event10 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0003 Vendor=1bcf Product=0007 Version=0110 N: Name="USB Optical Mouse" P: Phys=usb-:04:00.3-2/input0 S: Sysfs=/devices/pci:00/:00:08.1/:04:00.3/usb1/1-2/1-2:1.0/0003:1BCF:0007.0003/input/input13 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=9 B: ABS=100 glenn@glenn-IdeaPad-Flex-5-14ALC7:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: glenn 1565 F pulseaudio /dev/snd/controlC0: glenn 1565 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 13 11:47:42 2023 InstallationDate: Installed on 2022-10-24 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 82R9 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=34673e34-d4b4-4d7e-89d6-ed43268cbc25 ro quiet splash vt.handoff=7 RelatedPackageVersions:
[Kernel-packages] [Bug 2007179] [NEW] touchpad not recognized, touchpad settings missing ubuntu 22.04
Public bug reported: ubuntu-bug linux glenn@glenn-IdeaPad-Flex-5-14ALC7:~$ cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=a70210 83803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:10/LNXVIDEO:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:14.3/PNP0C09:00/VPC2004:00/input/input4 U: Uniq= H: Handlers=rfkill kbd event4 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=30c9 Product=0030 Version=0006 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:04:00.3-4/button S: Sysfs=/devices/pci:00/:00:08.1/:04:00.3/usb1/1-4/1-4:1.0/input/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:04:00.1/sound/card0/input6 U: Uniq= H: Handlers=event6 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:04:00.1/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic Headset Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:04:00.6/sound/card1/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:04:00.6/sound/card1/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0003 Vendor=1bcf Product=0007 Version=0110 N: Name="USB Optical Mouse" P: Phys=usb-:04:00.3-2/input0 S: Sysfs=/devices/pci:00/:00:08.1/:04:00.3/usb1/1-2/1-2:1.0/0003:1BCF:0007.0003/input/input12 U: Uniq= H: Handlers=mouse0 event10 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0003 Vendor=1bcf Product=0007 Version=0110 N: Name="USB Optical Mouse" P: Phys=usb-:04:00.3-2/input0 S: Sysfs=/devices/pci:00/:00:08.1/:04:00.3/usb1/1-2/1-2:1.0/0003:1BCF:0007.0003/input/input13 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=9 B: ABS=100 glenn@glenn-IdeaPad-Flex-5-14ALC7:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: glenn 1565 F pulseaudio /dev/snd/controlC0: glenn 1565 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 13 11:47:42 2023 InstallationDate: Installed on 2022-10-24 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 82R9 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=34673e34-d4b4-4d7e-89d6-ed43268cbc25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-60-generic N/A linux-backports-modules-5.15.0-60-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: JCCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14ALC7 dmi.ec.firmware.release: 1.24 dmi.modalias:
[Kernel-packages] [Bug 2007173] Re: i915: loss of the screen connected in DP to my dockstation
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/2007173 Title: i915: loss of the screen connected in DP to my dockstation Status in linux package in Ubuntu: Confirmed Bug description: Since a few versions of the kernel I'm losing the screen connected to my dockstation thinkpad using displayport. My running laptop is a thinkpad T14s I'm currently running "Linux laptop 5.19.0-28-generic #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 15 12:05:40 UTC 2 x86_64 x86_64 x86_64 GNU/Linux" but I had the same issue while running "linux-image-5.15.0-60-generic" and I think with "linux-image-5.15.0-58-generic" too. When losing the screen, I'm getting "i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful" from the kernel. During the last screen loss, I tried to connect the DisplayPort to another screen to eliminate the possibility that it could be a issue with it. Not only did the other screen not work either, but I got the following stacktrace: 17957.541801] CPU: 3 PID: 30705 Comm: kworker/3:1 Tainted: G U 5.19.0-28-generic #29~22.04.1-Ubuntu [17957.541811] Hardware name: LENOVO 20T1S62300/20T1S62300, BIOS N2YET34W (1.23 ) 12/31/2021 [17957.541816] Workqueue: events i915_hotplug_work_func [i915] [17957.542099] RIP: 0010:intel_dp_prep_link_retrain+0x1b0/0x1d0 [i915] [17957.542378] Code: d2 74 32 48 89 55 a8 4c 89 4d b0 e8 1a 86 f3 f5 48 8b 55 a8 48 c7 c1 50 7c b0 c0 48 c7 c7 e6 00 ae c0 48 89 c6 e8 87 5a 41 f6 <0f> 0b 4c 8b 4d b0 e9 36 ff ff ff 48 8b 17 eb c9 e8 ab bc 4d f6 e9 [17957.542385] RSP: 0018:b27bc6677cb0 EFLAGS: 00010246 [17957.542393] RAX: RBX: 9d6da9ef26c0 RCX: [17957.542398] RDX: RSI: RDI: [17957.542401] RBP: b27bc6677d08 R08: R09: [17957.542405] R10: R11: R12: 9d6c99894170 [17957.542409] R13: b27bc6677d27 R14: b27bc6677d70 R15: 9d6ca032c800 [17957.542414] FS: () GS:9d73ad6c() knlGS: [17957.542420] CS: 0010 DS: ES: CR0: 80050033 [17957.542425] CR2: 170804379000 CR3: 000792010005 CR4: 003706e0 [17957.542431] DR0: DR1: DR2: [17957.542434] DR3: DR6: fffe0ff0 DR7: 0400 [17957.542439] Call Trace: [17957.542443] [17957.542453] intel_dp_retrain_link+0xee/0x2f0 [i915] [17957.542773] intel_ddi_hotplug+0xc6/0x1f0 [i915] [17957.543049] i915_hotplug_work_func+0x1f3/0x320 [i915] [17957.543316] process_one_work+0x222/0x400 [17957.543327] worker_thread+0x50/0x3e0 [17957.543334] ? rescuer_thread+0x3c0/0x3c0 [17957.543340] kthread+0xe6/0x110 [17957.543349] ? kthread_complete_and_exit+0x20/0x20 [17957.543359] ret_from_fork+0x1f/0x30 [17957.543374] [17957.543377] ---[ end trace ]--- [17985.975481] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [17991.187501] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful Distrib is : "lsb_release -rd Description: Linux Mint 21 Release: 21" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007173/+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 2007173] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2007173 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/2007173 Title: i915: loss of the screen connected in DP to my dockstation Status in linux package in Ubuntu: Incomplete Bug description: Since a few versions of the kernel I'm losing the screen connected to my dockstation thinkpad using displayport. My running laptop is a thinkpad T14s I'm currently running "Linux laptop 5.19.0-28-generic #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 15 12:05:40 UTC 2 x86_64 x86_64 x86_64 GNU/Linux" but I had the same issue while running "linux-image-5.15.0-60-generic" and I think with "linux-image-5.15.0-58-generic" too. When losing the screen, I'm getting "i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful" from the kernel. During the last screen loss, I tried to connect the DisplayPort to another screen to eliminate the possibility that it could be a issue with it. Not only did the other screen not work either, but I got the following stacktrace: 17957.541801] CPU: 3 PID: 30705 Comm: kworker/3:1 Tainted: G U 5.19.0-28-generic #29~22.04.1-Ubuntu [17957.541811] Hardware name: LENOVO 20T1S62300/20T1S62300, BIOS N2YET34W (1.23 ) 12/31/2021 [17957.541816] Workqueue: events i915_hotplug_work_func [i915] [17957.542099] RIP: 0010:intel_dp_prep_link_retrain+0x1b0/0x1d0 [i915] [17957.542378] Code: d2 74 32 48 89 55 a8 4c 89 4d b0 e8 1a 86 f3 f5 48 8b 55 a8 48 c7 c1 50 7c b0 c0 48 c7 c7 e6 00 ae c0 48 89 c6 e8 87 5a 41 f6 <0f> 0b 4c 8b 4d b0 e9 36 ff ff ff 48 8b 17 eb c9 e8 ab bc 4d f6 e9 [17957.542385] RSP: 0018:b27bc6677cb0 EFLAGS: 00010246 [17957.542393] RAX: RBX: 9d6da9ef26c0 RCX: [17957.542398] RDX: RSI: RDI: [17957.542401] RBP: b27bc6677d08 R08: R09: [17957.542405] R10: R11: R12: 9d6c99894170 [17957.542409] R13: b27bc6677d27 R14: b27bc6677d70 R15: 9d6ca032c800 [17957.542414] FS: () GS:9d73ad6c() knlGS: [17957.542420] CS: 0010 DS: ES: CR0: 80050033 [17957.542425] CR2: 170804379000 CR3: 000792010005 CR4: 003706e0 [17957.542431] DR0: DR1: DR2: [17957.542434] DR3: DR6: fffe0ff0 DR7: 0400 [17957.542439] Call Trace: [17957.542443] [17957.542453] intel_dp_retrain_link+0xee/0x2f0 [i915] [17957.542773] intel_ddi_hotplug+0xc6/0x1f0 [i915] [17957.543049] i915_hotplug_work_func+0x1f3/0x320 [i915] [17957.543316] process_one_work+0x222/0x400 [17957.543327] worker_thread+0x50/0x3e0 [17957.543334] ? rescuer_thread+0x3c0/0x3c0 [17957.543340] kthread+0xe6/0x110 [17957.543349] ? kthread_complete_and_exit+0x20/0x20 [17957.543359] ret_from_fork+0x1f/0x30 [17957.543374] [17957.543377] ---[ end trace ]--- [17985.975481] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [17991.187501] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful Distrib is : "lsb_release -rd Description: Linux Mint 21 Release: 21" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007173/+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 2007173] [NEW] i915: loss of the screen connected in DP to my dockstation
Public bug reported: Since a few versions of the kernel I'm losing the screen connected to my dockstation thinkpad using displayport. My running laptop is a thinkpad T14s I'm currently running "Linux laptop 5.19.0-28-generic #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 15 12:05:40 UTC 2 x86_64 x86_64 x86_64 GNU/Linux" but I had the same issue while running "linux-image-5.15.0-60-generic" and I think with "linux-image-5.15.0-58-generic" too. When losing the screen, I'm getting "i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful" from the kernel. During the last screen loss, I tried to connect the DisplayPort to another screen to eliminate the possibility that it could be a issue with it. Not only did the other screen not work either, but I got the following stacktrace: 17957.541801] CPU: 3 PID: 30705 Comm: kworker/3:1 Tainted: G U 5.19.0-28-generic #29~22.04.1-Ubuntu [17957.541811] Hardware name: LENOVO 20T1S62300/20T1S62300, BIOS N2YET34W (1.23 ) 12/31/2021 [17957.541816] Workqueue: events i915_hotplug_work_func [i915] [17957.542099] RIP: 0010:intel_dp_prep_link_retrain+0x1b0/0x1d0 [i915] [17957.542378] Code: d2 74 32 48 89 55 a8 4c 89 4d b0 e8 1a 86 f3 f5 48 8b 55 a8 48 c7 c1 50 7c b0 c0 48 c7 c7 e6 00 ae c0 48 89 c6 e8 87 5a 41 f6 <0f> 0b 4c 8b 4d b0 e9 36 ff ff ff 48 8b 17 eb c9 e8 ab bc 4d f6 e9 [17957.542385] RSP: 0018:b27bc6677cb0 EFLAGS: 00010246 [17957.542393] RAX: RBX: 9d6da9ef26c0 RCX: [17957.542398] RDX: RSI: RDI: [17957.542401] RBP: b27bc6677d08 R08: R09: [17957.542405] R10: R11: R12: 9d6c99894170 [17957.542409] R13: b27bc6677d27 R14: b27bc6677d70 R15: 9d6ca032c800 [17957.542414] FS: () GS:9d73ad6c() knlGS: [17957.542420] CS: 0010 DS: ES: CR0: 80050033 [17957.542425] CR2: 170804379000 CR3: 000792010005 CR4: 003706e0 [17957.542431] DR0: DR1: DR2: [17957.542434] DR3: DR6: fffe0ff0 DR7: 0400 [17957.542439] Call Trace: [17957.542443] [17957.542453] intel_dp_retrain_link+0xee/0x2f0 [i915] [17957.542773] intel_ddi_hotplug+0xc6/0x1f0 [i915] [17957.543049] i915_hotplug_work_func+0x1f3/0x320 [i915] [17957.543316] process_one_work+0x222/0x400 [17957.543327] worker_thread+0x50/0x3e0 [17957.543334] ? rescuer_thread+0x3c0/0x3c0 [17957.543340] kthread+0xe6/0x110 [17957.543349] ? kthread_complete_and_exit+0x20/0x20 [17957.543359] ret_from_fork+0x1f/0x30 [17957.543374] [17957.543377] ---[ end trace ]--- [17985.975481] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [17991.187501] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful Distrib is : "lsb_release -rd Description:Linux Mint 21 Release:21" ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- 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/2007173 Title: i915: loss of the screen connected in DP to my dockstation Status in linux package in Ubuntu: Incomplete Bug description: Since a few versions of the kernel I'm losing the screen connected to my dockstation thinkpad using displayport. My running laptop is a thinkpad T14s I'm currently running "Linux laptop 5.19.0-28-generic #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 15 12:05:40 UTC 2 x86_64 x86_64 x86_64 GNU/Linux" but I had the same issue while running "linux-image-5.15.0-60-generic" and I think with "linux-image-5.15.0-58-generic" too. When losing the screen, I'm getting "i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful" from the kernel. During the last screen loss, I tried to connect the DisplayPort to another screen to eliminate the possibility that it could be a issue with it. Not only did the other screen not work either, but I got the following stacktrace: 17957.541801] CPU: 3 PID: 30705 Comm: kworker/3:1 Tainted: G U 5.19.0-28-generic #29~22.04.1-Ubuntu [17957.541811] Hardware name: LENOVO 20T1S62300/20T1S62300, BIOS N2YET34W (1.23 ) 12/31/2021 [17957.541816] Workqueue: events i915_hotplug_work_func [i915] [17957.542099] RIP: 0010:intel_dp_prep_link_retrain+0x1b0/0x1d0 [i915] [17957.542378] Code: d2 74 32 48 89 55 a8 4c 89 4d b0 e8 1a 86 f3 f5 48 8b 55 a8 48 c7 c1 50 7c b0 c0 48 c7 c7 e6 00 ae c0 48 89 c6 e8 87 5a 41 f6 <0f> 0b 4c 8b 4d b0 e9 36 ff ff ff 48 8b 17 eb c9 e8 ab bc 4d f6 e9 [17957.542385] RSP: 0018:b27bc6677cb0 EFLAGS: 00010246 [17957.542393] RAX: RBX: 9d6da9ef26c0 RCX: [17957.542398] RDX: RSI: RDI:
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.15.0.1034.30)
All autopkgtests for the newly accepted linux-meta-azure (5.15.0.1034.30) for jammy have finished running. The following regressions have been reported in tests triggered by the package: digimend-dkms/10-4 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 2003174] Re: zfs-dkms fails to build on jammy with linux 5.19
** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2003174 Title: zfs-dkms fails to build on jammy with linux 5.19 Status in zfs-linux package in Ubuntu: Invalid Status in zfs-linux source package in Jammy: Fix Committed Bug description: [Impact] zfs-dkms fails to build on jammy with the latest linux hwe 5.19: *** ZFS Version: zfs-2.1.4-0ubuntu0.1 *** Compatible Kernels: 3.10 - 5.17 [Test case] $ sudo apt install zfs-dkms [Fix] The most reliable fix is probably to move to the same version that is available in kinetic, since there's no significant ABI change in this way we should be able to support both 5.15 and 5.19 kernels. [Regression potential] We may experience zfs regressions if there's a format/ABI incompatibility with volumes created with the previous version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2003174/+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 1945369] Re: memory cgroup disabled on Ubuntu Core 18
Thanks Michaelian - this also worked for me using Ubuntu Core latest. -- 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/1945369 Title: memory cgroup disabled on Ubuntu Core 18 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu Core 18, the memory cgroup is disabled, it seems that it needs to be manually enabled. I was able to enable it by adding `cgroup_enable=memory cgroup_memory=1` to the kernel command line, but on Ubuntu I think the memory cgroup should be enabled by default shouldn't it? $ cat /proc/cgroups #subsys_name hierarchy num_cgroups enabled cpuset2 1 1 cpu 4 100 1 cpuacct 4 100 1 blkio 5 100 1 memory0 109 0 devices 6 100 1 freezer 9 4 1 net_cls 3 1 1 perf_event10 1 1 net_prio 3 1 1 pids 8 107 1 rdma 7 1 1 I see this with Linux localhost 5.4.0-1043-raspi #47~18.04.1-Ubuntu SMP PREEMPT Mon Aug 23 14:39:46 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux on Ubuntu Core 18, but folks have informed me that the same is true on Ubuntu Core 20 as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945369/+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 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
This bug is awaiting verification that the linux-aws/5.15.0-1031.35 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- 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/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Released Bug description: Something wrong with ata driver in dmesg found: [1.980693] kernel: [1.980699] kernel: fbcon: Taking over console [1.980703] kernel: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 [1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]' [1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 5.15.0-25-generic #25-Ubuntu [1.980716] kernel: Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [1.980718] kernel: Call Trace: [1.980721] kernel: [1.980723] kernel: show_stack+0x52/0x58 [1.980729] kernel: dump_stack_lvl+0x4a/0x5f [1.980734] kernel: dump_stack+0x10/0x12 [1.980736] kernel: ubsan_epilogue+0x9/0x45 [1.980739] kernel: __ubsan_handle_out_of_bounds.cold+0x44/0x49 [1.980742] kernel: ahci_qc_issue+0x166/0x170 [libahci] [1.980748] kernel: ata_qc_issue+0x135/0x240 [1.980752] kernel: ata_exec_internal_sg+0x2c4/0x580 [1.980754] kernel: ? vprintk_default+0x1d/0x20 [1.980759] kernel: ata_exec_internal+0x67/0xa0 [1.980762] kernel: sata_pmp_read+0x8d/0xc0 [1.980765] kernel: sata_pmp_read_gscr+0x3c/0x90 [1.980768] kernel: sata_pmp_attach+0x8b/0x310 [1.980771] kernel: ata_eh_revalidate_and_attach+0x28c/0x4b0 [1.980775] kernel: ata_eh_recover+0x6b6/0xb30 [1.980778] kernel: ? ahci_do_hardreset+0x180/0x180 [libahci] [1.980783] kernel: ? ahci_stop_engine+0xb0/0xb0 [libahci] [1.980787] kernel: ? ahci_do_softreset+0x290/0x290 [libahci] [1.980792] kernel: ? trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0 [1.980795] kernel: sata_pmp_eh_recover.isra.0+0x214/0x560 [1.980799] kernel: sata_pmp_error_handler+0x23/0x40 [1.980802] kernel: ahci_error_handler+0x43/0x80 [libahci] [1.980806] kernel: ata_scsi_port_error_handler+0x2b1/0x600 [1.980810] kernel: ata_scsi_error+0x9c/0xd0 [1.980813] kernel: scsi_error_handler+0xa1/0x180 [1.980817] kernel: ? scsi_unjam_host+0x1c0/0x1c0 [1.980820] kernel: kthread+0x12a/0x150 [1.980823] kernel: ? set_kthread_struct+0x50/0x50 [1.980826] kernel: ret_from_fork+0x22/0x30 [1.980831] kernel: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene16798 F pulseaudio /dev/snd/pcmC0D0p: eugene16798 F...m pulseaudio /dev/snd/controlC1: eugene16798 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 24 05:13:34 2022 HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61 InstallationDate: Installed on 2019-04-13 (1106 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp2s0no wireless extensions. virbr0no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on
[Kernel-packages] [Bug 1989944] Re: [22.04/Jammy] Replace SAUCE AMD DP tunneling patch by upstream version
This bug is awaiting verification that the linux-aws/5.15.0-1031.35 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- 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/1989944 Title: [22.04/Jammy] Replace SAUCE AMD DP tunneling patch by upstream version Status in linux package in Ubuntu: Triaged Status in linux source package in Jammy: Fix Released Bug description: [SRU Justification] == Impact == We applied a set of patches early as the upstreaming got delayed. The patch now is in upstream linux. Since it differs somewhat from the patch we carry and in order to get potential security and other updates right, we want to replace the SAUCE patch by its upstream counterpart. == Fix == “UBUNTU: SAUCE: thunderbolt: Add DP out resource when DP tunnel is discovered.” to be replaced by: commit b60e31bf18a7064032dbcb73dcb5b58f8a00a110 linux-next “thunderbolt: Add DP OUT resource when DP tunnel is discovered” == Testcase == Attach external Monitor via Thunderbolt port (AMD GPU) (Reference: bug 1983143) == Regression Potential == Previously working external connections might no longer work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989944/+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 1989990] Re: [SRU] Ubuntu 22.04 - NVMe TCP - Host fails to reconnect to target after link down/link up sequence
This bug is awaiting verification that the linux-aws/5.15.0-1031.35 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- 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/1989990 Title: [SRU] Ubuntu 22.04 - NVMe TCP - Host fails to reconnect to target after link down/link up sequence Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: [Impact] Ubuntu 22.04 host fails to reconnect successfully to the NVMe TCP target after link down event if the number of queues have changed post link down. [Fix] Following upstream patch set helps address the issue. 1. nvmet: Expose max queues to configfs https://git.infradead.org/nvme.git/commit/2c4282742d049e2a5ab874e2b359a2421b9377c2 2. nvme-tcp: Handle number of queue changes https://git.infradead.org/nvme.git/commit/516204e486a19d03962c2757ef49782e6c1cacf4 3. nvme-rdma: Handle number of queue changes https://git.infradead.org/nvme.git/commit/e800278c1dc97518eab1970f8f58a5aad52b0f86 The patch in Point 2 above helps address the failure to reconnect in NVMe TCP scenario. Also, following patch addresses error code parsing issue in the reconnect sequence. nvme-fabrics: parse nvme connect Linux error codes https://git.infradead.org/nvme.git/commit/ec9e96b5230148294c7abcaf3a4c592d3720b62d [Test Plan] 1. Boot into Ubuntu 22.04 kernel without fix. 2. Establish connection to NVMe TCP target. 3. Toggle NIC link and bring link up after 10 seconds. When the NIC link is down, on the target increase the number of queues assigned to the controller. 4. Observe that connection to target is lost and after link comes up, controller from host tries to re-establish connection. 5. With patch, reconnection succeeds with higher number of queues [Where problems could occur] Regression risk is low to medium. [Other Info] Test Kernel Source https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_1989990_nvme_tcp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989990/+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 1990167] Re: cma alloc failure in large 5.15 arm instances
This bug is awaiting verification that the linux-aws/5.15.0-1031.35 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1990167 Title: cma alloc failure in large 5.15 arm instances Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Jammy: Fix Committed Status in linux-aws source package in Kinetic: Fix Committed Bug description: When launching large arm64 instances on the focal or jammy ami, cma allocation errors appear in the dmesg out: [0.063255] cma: cma_alloc: reserved: alloc failed, req-size: 4096 pages, ret: -12 As far as I can tell, this does not impact instance launch in a meaningful way, but I am unsure of the other implications of this. I was able to confirm that these messages are only present in 5.15, as they do not show up in the bionic image, and rolling back focal to linux-aws 5.4 avoids them as well. This was present in at least 2 instance types and only appears to pop up in large sizes (2x4 does not produce them, 64x124 (c6gn.16xlarge) does) This could be as simple as just disabling CMA in the linux-aws pkg, as it appears this is already the case in linux-azure(LP: #1949770). Attaching dmesg out to the report. # Replication + Launch a large arm64 instance (c6gn.16xlarge) + Observe the messages in kern.log / dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1990167/+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 1991951] Re: RCU stalls
This bug is awaiting verification that the linux-aws/5.15.0-1031.35 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- 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/1991951 Title: RCU stalls Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: our RCU Stall Timeouts are different to upstream defaults; with regular one 3x longer; and expedited one 1000x shorter. not sure why. Let's harmonize on 60 & 0, which is 60 for regular ones that are set on most architectures; and upstream default for the expedited ones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991951/+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 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
This bug is awaiting verification that the linux-aws/5.15.0-1031.35 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- 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/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works fine. [Where problems could occur] It may break mt7922 driver. These commits
[Kernel-packages] [Bug 1996112] Re: Virtual GPU driver packaging regression
This bug is awaiting verification that the linux-azure/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- 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/1996112 Title: Virtual GPU driver packaging regression Status in linux package in Ubuntu: Fix Committed Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: Several virtual machine GPU drivers were moved from linux-modules- extra to linux-modules in bug #1960633 so that users running virtualized Linux would not need to install the drivers for real hardware in linux-modules-extra. linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these drivers, but linux-modules-extra-5.19.0-23-generic does. This is a regression. Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was limited to sub-HD resolutions until I installed linux-modules- extra-5.19.0-23-generic. A previous kernel (5.15) had the modules in linux-modules: $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ The current kernel (5.19) has the modules in linux-modules-extra: $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ccherlin 2582 F wireplumber /dev/snd/seq:ccherlin 2580 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-05 (675 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 zswap.compressor=lz4 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware N/A RfKill: Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag:
[Kernel-packages] [Bug 1993563] Re: support for same series backports versioning numbers
This bug is awaiting verification that the linux-aws/5.15.0-1031.35 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- 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/1993563 Title: support for same series backports versioning numbers Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: packaging support for sameport versioning numbers Allow generating kernel packages, that use backports mechanism within the same series. For example linux-lowlatancy linux-riscv. Those kernels already have customized packaging to achieve the above, this is introducing standard support for this in the main kernels for jammy and kinetic series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993563/+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 1995453] Re: Add some ACPI device IDs for Intel HID device
This bug is awaiting verification that the linux-azure/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995453 Title: Add some ACPI device IDs for Intel HID device Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] Add the ACPI devices IDs for Intel JasonLake, MeteorLake and RaptorLake [Fix] ACPI devices IDs are add the the related Intel HID devices on these platforms can work. [Test] Verified the Intel HID events can work such as power button for suspend and wake. [Where problems could occur] Add the ACPI device IDs for support Intel HID devices, so chance of problems should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995453/+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 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
This bug is awaiting verification that the linux-azure/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- 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/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works fine. [Where problems could occur] It may break mt7922 driver.
[Kernel-packages] [Bug 1998115] Re: Fix iosm: WWAN cannot build the connection (DW5823e)
This bug is awaiting verification that the linux-aws/5.15.0-1031.35 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998115 Title: Fix iosm: WWAN cannot build the connection (DW5823e) Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] WWAN(DW5823e) can't build the connection successfully. [Fix] With INTEL_IOMMU disable config or by forcing intel_iommu=off from grub some of the features of IOSM driver like browsing, flashing & coredump collection is not working. When driver calls DMA API - dma_map_single() for tx transfers. It is resulting in dma mapping error. Set the device DMA addressing capabilities using dma_set_mask() and remove the INTEL_IOMMU dependency in kconfig so that driver follows the platform config either INTEL_IOMMU enable or disable. Because the generic jammy(5.15) doesn't contain NET_DEVLINK and RELAY CONFIGs yet on iosm module, the single patch is necessary for Jammy. [Test Case] 1. boot up with kernel applied the FIX. 2. check the status of wwan by "mmcli -m 0" Status| unlock retries: sim-pin (3) | state: ^[32mconnected^[0m |power state: on |access tech: lte | signal quality: 45% (recent) -- 3GPP | imei: ## | enabled locks: sim, fixed-dialing |operator id: 46692 | operator name: Chunghwa Telecom | registration: home | packet service state: attached |pco: | 0: (complete) [Where problems could occur] remove the dependency for intel_iommu, iosm would fit better on other platforms not only Intel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998115/+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 1998115] Re: Fix iosm: WWAN cannot build the connection (DW5823e)
This bug is awaiting verification that the linux-azure/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998115 Title: Fix iosm: WWAN cannot build the connection (DW5823e) Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] WWAN(DW5823e) can't build the connection successfully. [Fix] With INTEL_IOMMU disable config or by forcing intel_iommu=off from grub some of the features of IOSM driver like browsing, flashing & coredump collection is not working. When driver calls DMA API - dma_map_single() for tx transfers. It is resulting in dma mapping error. Set the device DMA addressing capabilities using dma_set_mask() and remove the INTEL_IOMMU dependency in kconfig so that driver follows the platform config either INTEL_IOMMU enable or disable. Because the generic jammy(5.15) doesn't contain NET_DEVLINK and RELAY CONFIGs yet on iosm module, the single patch is necessary for Jammy. [Test Case] 1. boot up with kernel applied the FIX. 2. check the status of wwan by "mmcli -m 0" Status| unlock retries: sim-pin (3) | state: ^[32mconnected^[0m |power state: on |access tech: lte | signal quality: 45% (recent) -- 3GPP | imei: ## | enabled locks: sim, fixed-dialing |operator id: 46692 | operator name: Chunghwa Telecom | registration: home | packet service state: attached |pco: | 0: (complete) [Where problems could occur] remove the dependency for intel_iommu, iosm would fit better on other platforms not only Intel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998115/+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 1998106] Re: Fix AMD-PState driver for Genoa CPU
This bug is awaiting verification that the linux-azure/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1998106 Title: Fix AMD-PState driver for Genoa CPU Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] During AMD Genoa development, the datacenter team identified performance regressions that were root caused in the amd-pstate driver. A first round of fixes already landed upstream (v6.1-rc7) in the amd-pstate driver, and should be backported to all the affected kernels. [Fix] Backport the upstream amd-pstate fixes: https://lore.kernel.org/linux- pm/20221117073541.3350600-1-perry.y...@amd.com/T/#m4616d857ca472937d1e1d31131ddc3261fa17b2a [Regression potential] Clean cherry-picks of already upstream (v6.1-rc7) fixes, impact a single driver (amd-pstate) and the new mode (passive) is disabled by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998106/+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 1998106] Re: Fix AMD-PState driver for Genoa CPU
This bug is awaiting verification that the linux-aws/5.15.0-1031.35 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1998106 Title: Fix AMD-PState driver for Genoa CPU Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] During AMD Genoa development, the datacenter team identified performance regressions that were root caused in the amd-pstate driver. A first round of fixes already landed upstream (v6.1-rc7) in the amd-pstate driver, and should be backported to all the affected kernels. [Fix] Backport the upstream amd-pstate fixes: https://lore.kernel.org/linux- pm/20221117073541.3350600-1-perry.y...@amd.com/T/#m4616d857ca472937d1e1d31131ddc3261fa17b2a [Regression potential] Clean cherry-picks of already upstream (v6.1-rc7) fixes, impact a single driver (amd-pstate) and the new mode (passive) is disabled by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998106/+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 1998883] Re: Micron NVME storage failure [1344, 5407]
This bug is awaiting verification that the linux-aws/5.15.0-1031.35 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1998883 Title: Micron NVME storage failure [1344,5407] Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Micron NVME storage fails to init with below error messages [ 8.965698] nvme nvme1: Duplicate cntlid 0 with nvme0, subsys nqn.2014-08.org.nvmexpress:uuid:834ae34b-0ef0-8a48-ac5a-3006545c2b7f, rejecting [ 8.966111] nvme nvme1: Removing after probe failure status: -22 [Fix] The patch from v5.19 add a quirk for Micron NVME fixes this issue 41f38043f884 nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH [Test] Verified with 5.17 OEM kernel on the reported machine. Didn't verify with 5.15 Jammy kernel, but confirmed the kernel could be compiled. [Where problems could occur] The impact should be low as it adds one device ID into a quirk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998883/+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 1999528] Re: [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later
This bug is awaiting verification that the linux-aws/5.15.0-1031.35 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- 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/1999528 Title: [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [SRU Justification] == Impact == Since we split the lowlatency kernel into its own source package the check in the regression test suite is missing a case and will not run, even though the kernel can be booted in a VM instance. == Fix == Add the missing case to the test script which is used by ADT testing. The test scripts are inherited from the primary/distro kernel. The fix should be made there instead of changing the lowlatency tree. == Test == Inspecting the ADT logs we should start to see tests executed instead of: autopkgtest [19:22:21]: test ubuntu-regression-suite: [- ubuntu-regression-suite is pointless, if one cannot boot the kernel == Regression Potential == There are a couple of flaky tests which will start to show up, rather than only successful runs (which should have been a suspicious thing). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999528/+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 1999528] Re: [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later
This bug is awaiting verification that the linux-azure/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- 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/1999528 Title: [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [SRU Justification] == Impact == Since we split the lowlatency kernel into its own source package the check in the regression test suite is missing a case and will not run, even though the kernel can be booted in a VM instance. == Fix == Add the missing case to the test script which is used by ADT testing. The test scripts are inherited from the primary/distro kernel. The fix should be made there instead of changing the lowlatency tree. == Test == Inspecting the ADT logs we should start to see tests executed instead of: autopkgtest [19:22:21]: test ubuntu-regression-suite: [- ubuntu-regression-suite is pointless, if one cannot boot the kernel == Regression Potential == There are a couple of flaky tests which will start to show up, rather than only successful runs (which should have been a suspicious thing). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999528/+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 2001605] Re: Add support for SEV-SNP
This bug was fixed in the package linux-gcp - 5.15.0-1029.36 --- linux-gcp (5.15.0-1029.36) jammy; urgency=medium * jammy/linux-gcp: 5.15.0-1029.36 -proposed tracker (LP: #2003429) [ Ubuntu: 5.15.0-60.66 ] * jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450) * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux-gcp (5.15.0-1028.35) jammy; urgency=medium * jammy/linux-gcp: 5.15.0-1028.35 -proposed tracker (LP: #2001767) * Add support for SEV-SNP (LP: #2001605) - KVM: SVM: Define sev_features and vmpl field in the VMSA - KVM: SEV: Refactor out sev_es_state struct - KVM: SVM: Create a separate mapping for the SEV-ES save area - KVM: SVM: Create a separate mapping for the GHCB save area - KVM: SVM: Update the SEV-ES save area mapping - x86/boot: Introduce helpers for MSR reads/writes - x86/boot: Use MSR read/write helpers instead of inline assembly - SAUCE: x86/compressed/64: Detect/setup SEV/SME features earlier in boot - x86/sev: Detect/setup SEV/SME features earlier in boot - x86/sev: Use CC_ATTR attribute to generalize string I/O unroll - x86/mm: Extend cc_attr to include AMD SEV-SNP - x86/sev: Shorten GHCB terminate macro names - SAUCE: x86/sev: Define the Linux specific guest termination reasons - x86/sev: Save the negotiated GHCB version - x86/sev: Carve out HV call's return value verification - x86/sev: Expose sev_es_ghcb_hv_call() for use by HyperV - x86/sev: Check SEV-SNP features support - x86/sev: Add a helper for the PVALIDATE instruction - x86/sev: Check the vmpl level - x86/compressed: Add helper for validating pages in the decompression stage - x86/compressed: Register GHCB memory when SEV-SNP is active - x86/sev: Register GHCB memory when SEV-SNP is active - x86/sev: Rename mem_encrypt.c to mem_encrypt_amd.c - x86/sev: Add helper for validating pages in early enc attribute changes - treewide: Replace the use of mem_encrypt_active() with cc_platform_has() - x86/head64: Carve out the guest encryption postprocessing into a helper - SAUCE: x86/kernel: Make the .bss..decrypted section shared in RMP table - x86/kernel: Validate ROM memory before accessing when SEV-SNP is active - SAUCE: x86/mm: Add support to validate memory when changing C-bit - x86/sev: Remove do_early_exception() forward declarations - x86/sev: Use SEV-SNP AP creation to start secondary CPUs - x86/head/64: Re-enable stack protection - x86/compressed/acpi: Move EFI detection to helper - x86/compressed/acpi: Move EFI system table lookup to helper - x86/compressed/acpi: Move EFI config table lookup to helper - x86/compressed/acpi: Move EFI vendor table lookup to helper - x86/compressed/acpi: Move EFI kexec handling into common code - x86/boot: Add Confidential Computing type to setup_data - KVM: x86: Move lookup of indexed CPUID leafs to helper - x86/sev: Move MSR-based VMGEXITs for CPUID to helper - x86/compressed/64: Add support for SEV-SNP CPUID table in #VC handlers - x86/boot: Add a pointer to Confidential Computing blob in bootparams - x86/compressed: Add SEV-SNP feature detection/setup - x86/compressed: Use firmware-validated CPUID leaves for SEV-SNP guests - x86/compressed: Export and rename add_identity_map() - x86/compressed/64: Add identity mapping for Confidential Computing blob - x86/sev: Add SEV-SNP feature detection/setup - x86/sev: Use firmware-validated CPUID for SEV-SNP guests - x86/sev: Provide support for SNP guest request NAEs - x86/sev: Register SEV-SNP guest request platform device - virt: Add SEV-SNP guest driver - virt: sevguest: Add support to derive key - virt: sevguest: Add support to get extended report - virt: sevguest: Add documentation for SEV-SNP CPUID Enforcement - [config] Enable SEV_GUEST [ Ubuntu: 5.15.0-59.65 ] * jammy/linux: 5.15.0-59.65 -proposed tracker (LP: #2001801) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2022-47940 - ksmbd: validate length in smb2_write() * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x * support for same series backports versioning numbers (LP: #1993563) - [Packaging] sameport -- add support for sameport versioning * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Micron NVME storage failure [1344,5407] (LP: #1998883) - nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH * Jammy update: v5.15.78 upstream stable release (LP: #1998843) - scsi: lpfc: Rework MIB Rx Monitor debug info logic - serial: ar933x:
[Kernel-packages] [Bug 2001618] Re: BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9
This bug is awaiting verification that the linux-azure/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- 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/2001618 Title: BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] The BPF_AND, BPF_OR, BPF_XOR, BPF_FETCH, BPF_XCHG and BPF_CMPXCHG related tests will fail in net:test_bpf test from ubuntu_kernel_selftests as they are not supported. test_bpf: #361 BPF_ATOMIC | BPF_W, BPF_AND: Test: 0x12 & 0xab = 0x02 eBPF filter atomic op code c3 (@3) unsupported FAIL to select_runtime err=-524 ... test_bpf: #365 BPF_ATOMIC | BPF_W, BPF_AND | BPF_FETCH: Test: 0x12 & 0xab = 0x02 eBPF filter atomic op code c3 (@3) unsupported FAIL to select_runtime err=-524 ... test_bpf: #377 BPF_ATOMIC | BPF_W, BPF_OR: Test: 0x12 | 0xab = 0xbb FAIL to select_runtime err=-524 ... test_bpf: #393 BPF_ATOMIC | BPF_W, BPF_XOR: Test: 0x12 ^ 0xab = 0xb9 FAIL to select_runtime err=-524 ... test_bpf: #409 BPF_ATOMIC | BPF_W, BPF_XCHG: Test: 0x12 xchg 0xab = 0xab eBPF filter atomic op code c3 (@3) unsupported FAIL to select_runtime err=-524 ... test_bpf: #417 BPF_ATOMIC | BPF_W, BPF_CMPXCHG: Test successful return eBPF filter atomic op code c3 (@3) unsupported FAIL to select_runtime err=-524 ... test_bpf: Summary: 894 PASSED, 132 FAILED, [882/882 JIT'ed] Please find attachment for the complete test log. [Fix] * 6511270911 powerpc/bpf/64: add support for BPF_ATOMIC bitwise operations * dbe6e2456f powerpc/bpf/64: add support for atomic fetch operations * 1e82dfaa78 powerpc/bpf/64: Add instructions for atomic_[cmp]xchg These patches can be cherry-picked into Kinetic kernel. [Test] Test kernel can be found here: https://people.canonical.com/~phlin/kernel/lp-2001618-ppcbpf/ Steps: 1. Reboot with the patched kernel 2. Run: sudo dmesg -C sudo modprobe test_bpf sudo dmesg Tested with Power9 node baltar, with the patched kernel there will be no failure reported by the test_bpf: test_bpf: Summary: 1026 PASSED, 0 FAILED, [1014/1014 JIT'ed] [Where problems could occur] This patchset just broaden the BPF operations support on ppc64, we might see some new failures when using these instruction somewhere in the future. Cascardo: The existing atomic operations may regress as well, since they now produce different code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2001618/+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 2002812] Re: Revoke & rotate to new signing key
This bug is awaiting verification that the linux-aws/5.15.0-1031.35 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- 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/2002812 Title: Revoke & rotate to new signing key Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * Revoke & rotate to new signing key * Update revocations, which match the next Ubuntu shim 15.7 revocations. Specifically - revoke certs that were previously protected with by-hash revocations, revoke lost/unused certificates. * Start using advantage2021v1 and ubuntu2022v1 signing keys. * This is a routine key rotation. [ Test Plan ] * Check that old shim/grub boot this kernel * Check that the upcomming future shim/grub can boot this kernel * Check that these kernels can do signed kexec into itself [ Where problems could occur ] * Kernels with this patch applied should be signed using ubuntu/4 pro/3 core/2 signing streams. [ Other Info ] * TPM PCR values and measurements will change when changing the signing key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002812/+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 2002812] Re: Revoke & rotate to new signing key
This bug is awaiting verification that the linux-azure/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- 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/2002812 Title: Revoke & rotate to new signing key Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * Revoke & rotate to new signing key * Update revocations, which match the next Ubuntu shim 15.7 revocations. Specifically - revoke certs that were previously protected with by-hash revocations, revoke lost/unused certificates. * Start using advantage2021v1 and ubuntu2022v1 signing keys. * This is a routine key rotation. [ Test Plan ] * Check that old shim/grub boot this kernel * Check that the upcomming future shim/grub can boot this kernel * Check that these kernels can do signed kexec into itself [ Where problems could occur ] * Kernels with this patch applied should be signed using ubuntu/4 pro/3 core/2 signing streams. [ Other Info ] * TPM PCR values and measurements will change when changing the signing key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002812/+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 2003353] Re: Azure: Fix race on per-CQ variable napi_iperf panic fix
This bug is awaiting verification that the linux-azure/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2003353 Title: Azure: Fix race on per-CQ variable napi_iperf panic fix Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] This patch [1]1 is requested by MSFT Linux Systems Group to fix a race condition that can cause a panic in napi_iperf(). [1] - https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=18010ff776fa42340efc428b3ea6d19b3e7c7b21 A number of prerequisite patches are required. v5.15.83 contains this patch, however v5.19 stable does not. [Test Case] MSFT tested and approved, "Please merge in both the kernels, LSG finished the validation". [Where things could go wrong] Test results are good. Regression potential seems low. [Other Info] SF: #00350135 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2003353/+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 2004090] Re: Azure: Performance improvement for TDX
This bug is awaiting verification that the linux-azure/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2004090 Title: Azure: Performance improvement for TDX Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] ms_hyperv_init_platform() hides HV_MSR_REFERENCE_TSC_AVAILABLE for TDX guests in favor of Invariant-TSC. In this case, we should also downgrade the rating of hyperv_cs_msr.rating, so Invariant-TSC can be used by default. [Fix] https://github.com/dcui/tdx.git 367f18c06ac999c2822b0c24f50a87994635d4bd [Where things could go wrong] TDX guests may perform worse. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2004090/+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 2003816] Re: Regression in ext4 during online resize
This bug is awaiting verification that the linux-aws/5.15.0-1031.35 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws verification-needed-jammy -- 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/2003816 Title: Regression in ext4 during online resize Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: Issue resize2fs utility is used to resize the filesystem and is idempotent in nature. But in the 5.15 kernel, successive execution of resize2fs is returning error. Reproduction step (on AWS): Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p /mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0 Increase the size of EBS volume. Run sudo resize2fs /dev/xvdb multiple times. The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! When you run the same step on the latest image ami-0a1d6d351894df6cc (Linux 5.15.0-1026-aws). The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. FIX: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003816/+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 2004087] Re: Azure: Fix TDX backport
This bug is awaiting verification that the linux-azure/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2004087 Title: Azure: Fix TDX backport Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Kinetic: Fix Released Bug description: SRU Justification [Impact] A backport caused by a stable updates rebase was not performed correctly. The symptom is a failure to boot on TDX enabled hypervisors. [Fix] Make sure the sources match those of 'https://github.com/dcui/tdx.git decui/upstream-kinetic-22.10/master-next/1209'. [Test Plan] Boot on a TDX enabled hypervisor. Tested by Gauthier Jolly. [Where things could go wrong] This is a new feature isolated to TDX, so there is little chance of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2004087/+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 2003524] Re: amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks
This bug is awaiting verification that the linux-azure/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- 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/2003524 Title: amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks Status in linux package in Ubuntu: Fix Committed Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: [Impact] From "Mario Limonciello mario.limonciello at amd.com" https://lists.ubuntu.com/archives/kernel-team/2023-January/136434.html. There is a problem in amdgpu that if not all of IP blocks are supported or not all of the firmware is present then the framebuffer is destroyed and the screen freezes. In more recent kernels the amdgpu driver loads for all PCI VGA class AMD devices. This effectively means that unless you have all the pieces you need to support a GPU then the installer freezes unless you do nomodeset. This problem is to be fully fixed in kernel 6.3 with a ~47 patch series that is currently in drm-next. This does two basic things: 1) If the IP blocks isn't supported, don't destroy the framebuffer. 2) If firmware for any IP blocks aren't present, don't destroy the framebuffer. The whole patch series still needs more time to back in drm-next, but the most important part of the series is the first patch which accomplishes "1". This patch went out to stable 6.1.y as well: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpu/drm/amd?h=linux-6.1.y=dcfeba477b3e3df526e0f543b58fa71c045dff8b My reasoning is that it will ensure that if someone picks up a newer GPU such as Ryzen 7000 desktop or RDNA3 based they can at least install Ubuntu without needing to use "Safe Graphics Mode" at the installer. Sure; they won't have hardware acceleration without the rest of the kernel and framework, but that's a separate problem to a basic display. [Fix] Cherry-pick/backport commit 1923bc5a56daeeabd7e9093bad2febcd6af2416a "drm/amd: Delay removal of the firmware framebuffer" to Ubuntu Kinetic 5.19 kernel. [Test case] Boot kernel in a system with one of the amdgpu affected adapters. [Where problems can occur] The aforementioned commit could introduce other regressions on the support for AMD GPUs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003524/+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 2004604] Re: Azure: mana: Fix IRQ name - add PCI and queue number
This bug is awaiting verification that the linux-azure/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2004604 Title: Azure: mana: Fix IRQ name - add PCI and queue number Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] The PCI and queue number info is missing in MANA IRQ names. request_irq() will fail if the name is incorrect. [Test Case] Load the MANA module and ascertain if it detected a device. [Where things could go wrong] Existing instances could fail to initialize. [Other Info] SF: #00353708 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2004604/+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 2004807] Re: RDMA Back port DMA buffer fix
This bug is awaiting verification that the linux-aws/5.15.0-1031.35 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2004807 Title: RDMA Back port DMA buffer fix Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Focal: Fix Committed Status in linux-aws source package in Jammy: Fix Committed Status in linux-aws source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] When registering a new DMA MR after selecting the best aligned page size for it, we iterate over the given sglist to split each entry to smaller, aligned to the selected page size, DMA blocks. In given circumstances where the sg entry and page size fit certain sizes and the sg entry is not aligned to the selected page size, the total size of the aligned pages we need to cover the sg entry is >= 4GB. Under this circumstances, while iterating page aligned blocks, the counter responsible for counting how much we advanced from the start of the sg entry is overflowed because its type is u32 and we pass 4GB in size. This can lead to an infinite loop inside the iterator function because the overflow prevents the counter to be larger than the size of the sg entry. Fixes: a808273 ("RDMA/verbs: Add a DMA iterator to return aligned contiguous memory blocks") [Test Plan] AWS tested [Where things could go wrong] What could possibly go wrong with Remote DMA scatter/gather list errors ? [Other Info] SF: #00353710 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2004807/+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 1986623] Re: cryptsetup fails to decrypt root partion during boot
Fresh install worked until I did today's recommended updates, then the problem recurred. Not sure exactly what was updated; I thought /var/log/dpkg.log was supposed to be human-readable, but mine isn't. -- 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/1986623 Title: cryptsetup fails to decrypt root partion during boot Status in cryptsetup package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: During boot, cryptsetup fails to decrypt the root partition in a, seemingly, non-deterministic fashion. I know that the password is correct and that the keymap is not a fault either, because I have specifically chosen the very weak password "123456" for testing purposes. A hardware defect seems also rather unlikely as this behavior does not affect other Linux distributions or FreeBSD. Earlier Ubuntu versions do not seem to be affected either, as this bug appears to have been introduced during a kernel update in 20.04 and persists throughout 20.04-22.04. Unfortunately I cannot pinpoint the exact kernel update that introduced this bug. I have appended the output of cryptsetup when manually called from the initramfs shell. Here the second attempt succeeded in decrypting the root partition, however, it usually takes a lot more attempts to do so. As for some additional information, I can decrypt the same luks partition from a live USB without any problems whatsoever. echo 123456 | cryptsetup open --type luks --debug /dev/nvme0n1p3 nvme0n1p3_crypt # cryptsetup 2.4.3 processing "cryptsetup open --type luks --debug /dev/nvme0n1p3 nvme0n1p3_crypt" # Running command open. # Locking memory. # Installing SIGINT/SIGTERM handler. # Unblocking interruption on signal. # Allocating context for crypt device /dev/nvme0n1p3. # Trying to open and read device /dev/nvme0n1p3 with direct-io. # Initialising device-mapper backend library. # Trying to load any crypt type from device /dev/nvme0n1p3. # Crypto backend (OpenSSL 3.0.2 15 Mar 2022 [default]) initialized in cryptsetup library version 2.4.3. # Detected kernel Linux 5.15.0-46-generic x86_64. # Loading LUKS2 header (repair disabled). # Acquiring read lock for device /dev/nvme0n1p3. # Opening lock resource file /run/cryptsetup/L_259:3 # Verifying lock handle for /dev/nvme0n1p3. # Device /dev/nvme0n1p3 READ lock taken. # Trying to read primary LUKS2 header at offset 0x0. # Opening locked device /dev/nvme0n1p3 # Verifying locked device handle (bdev) # LUKS2 header version 2 of size 16384 bytes, checksum sha256. # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc (on-disk) # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc (in-memory) # Trying to read secondary LUKS2 header at offset 0x4000. # Reusing open ro fd on device /dev/nvme0n1p3 # LUKS2 header version 2 of size 16384 bytes, checksum sha256. # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c (on-disk) # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c (in-memory) # Device size 497776852992, offset 16777216. # Device /dev/nvme0n1p3 READ lock released. # PBKDF argon2id, time_ms 2000 (iterations 0), max_memory_kb 1048576, parallel_threads 4. # Activating volume nvme0n1p3_crypt using token (any type) -1. # dm version [ opencount flush ] [16384] (*1) # dm versions [ opencount flush ] [16384] (*1) # Detected dm-ioctl version 4.45.0. # Detected dm-crypt version 1.23.0. # Device-mapper backend running with UDEV support enabled. # dm status nvme0n1p3_crypt [ opencount noflush ] [16384] (*1) No usable token is available. # STDIN descriptor passphrase entry requested. # Activating volume nvme0n1p3_crypt [keyslot -1] using passphrase. # dm versions [ opencount flush ] [16384] (*1) # dm status nvme0n1p3_crypt [ opencount noflush ] [16384] (*1) # Keyslot 0 priority 1 != 2 (required), skipped. # Keyslot 1 priority 1 != 2 (required), skipped. # Trying to open LUKS2 keyslot 0. # Running keyslot key derivation. # Reading keyslot area [0x8000]. # Acquiring read lock for device /dev/nvme0n1p3. # Opening lock resource file /run/cryptsetup/L_259:3 # Verifying lock handle for /dev/nvme0n1p3. # Device /dev/nvme0n1p3 READ lock taken. # Reusing open ro fd on device /dev/nvme0n1p3 # Device /dev/nvme0n1p3 READ lock released. # Verifying key from keyslot 0, digest 0. # Digest 0 (pbkdf2) verify failed with -1. # Trying to open LUKS2 keyslot 1. # Running keyslot key derivation. # Reading keyslot area [0x47000]. # Acquiring read lock for device /dev/nvme0n1p3. # Opening lock resource file /run/cryptsetup/L_259:3 # Verifying lock handle for /dev/nvme0n1p3. # Device /dev/nvme0n1p3 READ lock taken. # Reusing open ro fd on device
[Kernel-packages] [Bug 2007158] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/2007158 Title: kernel oops with external usb-c hub with ethernet port Status in linux package in Ubuntu: Confirmed Bug description: Using an external USB-C hub with hdmi, usb and ethernet ports, I constantly see the following after ~ a couple of hours of usage: CPU: 7 PID: 137 Comm: irq/122-pciehp Tainted: P OE 5.15.0-60-generic #66-Ubuntu [37914.942824] Hardware name: SCHENKER SCHENKER_SLIM14_SSL14L19/N141CU , BIOS 1.07.04RTR1 10/02/2019 [37914.942825] RIP: 0010:ring_interrupt_active+0x1fe/0x270 [thunderbolt] [37914.942849] Code: 4c 89 4d c8 44 89 45 d4 e8 6f 71 e9 d0 4c 8b 4d c8 44 8b 45 d4 4c 89 e1 48 89 c6 4c 89 f2 48 c7 c7 d8 b8 40 c0 e8 c0 21 32 d1 <0f> 0b e9 0c ff ff ff 41 0f b6 47 78 d3 e0 41 09 c5 e9 cb fe ff ff [37914.942851] RSP: :b4048078ba90 EFLAGS: 00010086 [37914.942853] RAX: RBX: RCX: 0027 [37914.942854] RDX: 8abf707e0588 RSI: 0001 RDI: 8abf707e0580 [37914.942856] RBP: b4048078bad8 R08: 0003 R09: a9a0 [37914.942857] R10: R11: 0001 R12: c040a44b [37914.942858] R13: 00038200 R14: 8abc01b834c0 R15: 8abc038ac3c0 [37914.942859] FS: () GS:8abf707c() knlGS: [37914.942861] CS: 0010 DS: ES: CR0: 80050033 [37914.942862] CR2: 555aaf675f14 CR3: 00014f948004 CR4: 003706e0 [37914.942864] Call Trace: [37914.942865] [37914.942869] tb_ring_start+0x192/0x360 [thunderbolt] [37914.942880] tb_ctl_start+0x1d/0xb0 [thunderbolt] [37914.942892] tb_domain_runtime_resume+0x1a/0x40 [thunderbolt] [37914.942907] nhi_runtime_resume+0x64/0x70 [thunderbolt] [37914.942918] pci_pm_runtime_resume+0xb2/0xd0 [37914.942922] ? pci_pm_freeze_noirq+0x110/0x110 [37914.942924] __rpm_callback+0x4a/0x130 [37914.942928] ? pci_pm_freeze_noirq+0x110/0x110 [37914.942930] rpm_callback+0x67/0x70 [37914.942932] ? pci_pm_freeze_noirq+0x110/0x110 [37914.942933] rpm_resume+0x519/0x7c0 [37914.942936] ? pde_put+0x7c/0xb0 [37914.942939] __pm_runtime_resume+0x52/0x90 [37914.942942] __device_release_driver+0x2f/0x2a0 [37914.942945] device_release_driver+0x29/0x40 [37914.942948] pci_stop_bus_device+0x74/0xa0 [37914.942954] pci_stop_bus_device+0x30/0xa0 [37914.942956] pci_stop_bus_device+0x41/0xa0 [37914.942958] pci_stop_and_remove_bus_device+0x13/0x30 [37914.942960] pciehp_unconfigure_device+0x7e/0x140 [37914.942964] pciehp_disable_slot+0x6c/0x100 [37914.942967] pciehp_handle_presence_or_link_change+0xb7/0x110 [37914.942970] pciehp_ist+0x19a/0x1b0 [37914.942973] ? irq_forced_thread_fn+0x90/0x90 [37914.942977] irq_thread_fn+0x25/0x70 [37914.942980] irq_thread+0xdc/0x1b0 [37914.942983] ? irq_thread_fn+0x70/0x70 [37914.942986] ? irq_thread_check_affinity+0x100/0x100 [37914.942989] kthread+0x127/0x150 [37914.942992] ? set_kthread_struct+0x50/0x50 [37914.942995] ret_from_fork+0x1f/0x30 [37914.942999] [37914.943000] ---[ end trace 3d6e16cc93f67574 ]--- [37914.943004] [ cut here ] [37914.943004] thunderbolt :03:00.0: interrupt for RX ring 0 is already enabled [37914.943030] WARNING: CPU: 7 PID: 137 at drivers/thunderbolt/nhi.c:111 ring_interrupt_active+0x1fe/0x270 [thunderbolt] [37914.943043] Modules linked in: cdc_mbim cdc_wdm cdc_ncm usbhid ax88179_178a snd_seq_dummy hid_generic hidp hid r8153_ecm cdc_ether usbnet r8152 mii ccm veth nft_masq nvme_fabrics nft_chain_nat nf_nat bridge stp llc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) cmac algif_hash algif_skcipher af_alg bnep ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_comment xt_recent xt_multiport nft_limit xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nft_counter snd_hda_codec_hdmi snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_s oc_core [37914.943081] snd_hda_codec_realtek snd_hda_codec_generic snd_compress ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec nf_tables snd_hda_core snd_hwdep nfnetlink binfmt_misc iwlmvm(OE) snd_pcm intel_rapl_msr
[Kernel-packages] [Bug 2007158] [NEW] kernel oops with external usb-c hub with ethernet port
Public bug reported: Using an external USB-C hub with hdmi, usb and ethernet ports, I constantly see the following after ~ a couple of hours of usage: CPU: 7 PID: 137 Comm: irq/122-pciehp Tainted: P OE 5.15.0-60-generic #66-Ubuntu [37914.942824] Hardware name: SCHENKER SCHENKER_SLIM14_SSL14L19/N141CU , BIOS 1.07.04RTR1 10/02/2019 [37914.942825] RIP: 0010:ring_interrupt_active+0x1fe/0x270 [thunderbolt] [37914.942849] Code: 4c 89 4d c8 44 89 45 d4 e8 6f 71 e9 d0 4c 8b 4d c8 44 8b 45 d4 4c 89 e1 48 89 c6 4c 89 f2 48 c7 c7 d8 b8 40 c0 e8 c0 21 32 d1 <0f> 0b e9 0c ff ff ff 41 0f b6 47 78 d3 e0 41 09 c5 e9 cb fe ff ff [37914.942851] RSP: :b4048078ba90 EFLAGS: 00010086 [37914.942853] RAX: RBX: RCX: 0027 [37914.942854] RDX: 8abf707e0588 RSI: 0001 RDI: 8abf707e0580 [37914.942856] RBP: b4048078bad8 R08: 0003 R09: a9a0 [37914.942857] R10: R11: 0001 R12: c040a44b [37914.942858] R13: 00038200 R14: 8abc01b834c0 R15: 8abc038ac3c0 [37914.942859] FS: () GS:8abf707c() knlGS: [37914.942861] CS: 0010 DS: ES: CR0: 80050033 [37914.942862] CR2: 555aaf675f14 CR3: 00014f948004 CR4: 003706e0 [37914.942864] Call Trace: [37914.942865] [37914.942869] tb_ring_start+0x192/0x360 [thunderbolt] [37914.942880] tb_ctl_start+0x1d/0xb0 [thunderbolt] [37914.942892] tb_domain_runtime_resume+0x1a/0x40 [thunderbolt] [37914.942907] nhi_runtime_resume+0x64/0x70 [thunderbolt] [37914.942918] pci_pm_runtime_resume+0xb2/0xd0 [37914.942922] ? pci_pm_freeze_noirq+0x110/0x110 [37914.942924] __rpm_callback+0x4a/0x130 [37914.942928] ? pci_pm_freeze_noirq+0x110/0x110 [37914.942930] rpm_callback+0x67/0x70 [37914.942932] ? pci_pm_freeze_noirq+0x110/0x110 [37914.942933] rpm_resume+0x519/0x7c0 [37914.942936] ? pde_put+0x7c/0xb0 [37914.942939] __pm_runtime_resume+0x52/0x90 [37914.942942] __device_release_driver+0x2f/0x2a0 [37914.942945] device_release_driver+0x29/0x40 [37914.942948] pci_stop_bus_device+0x74/0xa0 [37914.942954] pci_stop_bus_device+0x30/0xa0 [37914.942956] pci_stop_bus_device+0x41/0xa0 [37914.942958] pci_stop_and_remove_bus_device+0x13/0x30 [37914.942960] pciehp_unconfigure_device+0x7e/0x140 [37914.942964] pciehp_disable_slot+0x6c/0x100 [37914.942967] pciehp_handle_presence_or_link_change+0xb7/0x110 [37914.942970] pciehp_ist+0x19a/0x1b0 [37914.942973] ? irq_forced_thread_fn+0x90/0x90 [37914.942977] irq_thread_fn+0x25/0x70 [37914.942980] irq_thread+0xdc/0x1b0 [37914.942983] ? irq_thread_fn+0x70/0x70 [37914.942986] ? irq_thread_check_affinity+0x100/0x100 [37914.942989] kthread+0x127/0x150 [37914.942992] ? set_kthread_struct+0x50/0x50 [37914.942995] ret_from_fork+0x1f/0x30 [37914.942999] [37914.943000] ---[ end trace 3d6e16cc93f67574 ]--- [37914.943004] [ cut here ] [37914.943004] thunderbolt :03:00.0: interrupt for RX ring 0 is already enabled [37914.943030] WARNING: CPU: 7 PID: 137 at drivers/thunderbolt/nhi.c:111 ring_interrupt_active+0x1fe/0x270 [thunderbolt] [37914.943043] Modules linked in: cdc_mbim cdc_wdm cdc_ncm usbhid ax88179_178a snd_seq_dummy hid_generic hidp hid r8153_ecm cdc_ether usbnet r8152 mii ccm veth nft_masq nvme_fabrics nft_chain_nat nf_nat bridge stp llc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) cmac algif_hash algif_skcipher af_alg bnep ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_comment xt_recent xt_multiport nft_limit xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nft_counter snd_hda_codec_hdmi snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc _core [37914.943081] snd_hda_codec_realtek snd_hda_codec_generic snd_compress ac97_bus ledtrig_audio snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec nf_tables snd_hda_core snd_hwdep nfnetlink binfmt_misc iwlmvm(OE) snd_pcm intel_rapl_msr snd_seq_midi intel_rapl_common mac80211(OE) intel_tcc_cooling x86_pkg_temp_thermal snd_seq_midi_event uvcvideo mei_hdcp btusb intel_powerclamp videobuf2_vmalloc libarc4 snd_rawmidi btrtl videobuf2_memops coretemp snd_seq btbcm videobuf2_v4l2 videobuf2_common btintel snd_seq_device iwlwifi(OE) snd_timer nls_iso8859_1 videodev bluetooth snd cfg80211(OE) joydev kvm_intel ecdh_generic mc ecc kvm rapl intel_cstate input_leds serio_raw intel_wmi_thunderbolt soundcore compat(OE) mei_me
[Kernel-packages] [Bug 1995453] Re: Add some ACPI device IDs for Intel HID device
This bug is awaiting verification that the linux-riscv/5.19.0-1013.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-riscv -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995453 Title: Add some ACPI device IDs for Intel HID device Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] Add the ACPI devices IDs for Intel JasonLake, MeteorLake and RaptorLake [Fix] ACPI devices IDs are add the the related Intel HID devices on these platforms can work. [Test] Verified the Intel HID events can work such as power button for suspend and wake. [Where problems could occur] Add the ACPI device IDs for support Intel HID devices, so chance of problems should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995453/+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 1996112] Re: Virtual GPU driver packaging regression
This bug is awaiting verification that the linux-riscv/5.19.0-1013.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-riscv -- 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/1996112 Title: Virtual GPU driver packaging regression Status in linux package in Ubuntu: Fix Committed Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: Several virtual machine GPU drivers were moved from linux-modules- extra to linux-modules in bug #1960633 so that users running virtualized Linux would not need to install the drivers for real hardware in linux-modules-extra. linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these drivers, but linux-modules-extra-5.19.0-23-generic does. This is a regression. Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was limited to sub-HD resolutions until I installed linux-modules- extra-5.19.0-23-generic. A previous kernel (5.15) had the modules in linux-modules: $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ The current kernel (5.19) has the modules in linux-modules-extra: $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ccherlin 2582 F wireplumber /dev/snd/seq:ccherlin 2580 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-05 (675 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 zswap.compressor=lz4 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware N/A RfKill: Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag:
[Kernel-packages] [Bug 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
This bug is awaiting verification that the linux-riscv/5.19.0-1013.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-riscv -- 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/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works fine. [Where problems could occur] It may break mt7922 driver.
[Kernel-packages] [Bug 1998106] Re: Fix AMD-PState driver for Genoa CPU
This bug is awaiting verification that the linux-riscv/5.19.0-1013.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-riscv -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1998106 Title: Fix AMD-PState driver for Genoa CPU Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] During AMD Genoa development, the datacenter team identified performance regressions that were root caused in the amd-pstate driver. A first round of fixes already landed upstream (v6.1-rc7) in the amd-pstate driver, and should be backported to all the affected kernels. [Fix] Backport the upstream amd-pstate fixes: https://lore.kernel.org/linux- pm/20221117073541.3350600-1-perry.y...@amd.com/T/#m4616d857ca472937d1e1d31131ddc3261fa17b2a [Regression potential] Clean cherry-picks of already upstream (v6.1-rc7) fixes, impact a single driver (amd-pstate) and the new mode (passive) is disabled by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998106/+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 1998115] Re: Fix iosm: WWAN cannot build the connection (DW5823e)
This bug is awaiting verification that the linux-riscv/5.19.0-1013.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-riscv -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998115 Title: Fix iosm: WWAN cannot build the connection (DW5823e) Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] WWAN(DW5823e) can't build the connection successfully. [Fix] With INTEL_IOMMU disable config or by forcing intel_iommu=off from grub some of the features of IOSM driver like browsing, flashing & coredump collection is not working. When driver calls DMA API - dma_map_single() for tx transfers. It is resulting in dma mapping error. Set the device DMA addressing capabilities using dma_set_mask() and remove the INTEL_IOMMU dependency in kconfig so that driver follows the platform config either INTEL_IOMMU enable or disable. Because the generic jammy(5.15) doesn't contain NET_DEVLINK and RELAY CONFIGs yet on iosm module, the single patch is necessary for Jammy. [Test Case] 1. boot up with kernel applied the FIX. 2. check the status of wwan by "mmcli -m 0" Status| unlock retries: sim-pin (3) | state: ^[32mconnected^[0m |power state: on |access tech: lte | signal quality: 45% (recent) -- 3GPP | imei: ## | enabled locks: sim, fixed-dialing |operator id: 46692 | operator name: Chunghwa Telecom | registration: home | packet service state: attached |pco: | 0: (complete) [Where problems could occur] remove the dependency for intel_iommu, iosm would fit better on other platforms not only Intel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998115/+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 1999528] Re: [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later
This bug is awaiting verification that the linux-riscv/5.19.0-1013.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-riscv -- 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/1999528 Title: [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [SRU Justification] == Impact == Since we split the lowlatency kernel into its own source package the check in the regression test suite is missing a case and will not run, even though the kernel can be booted in a VM instance. == Fix == Add the missing case to the test script which is used by ADT testing. The test scripts are inherited from the primary/distro kernel. The fix should be made there instead of changing the lowlatency tree. == Test == Inspecting the ADT logs we should start to see tests executed instead of: autopkgtest [19:22:21]: test ubuntu-regression-suite: [- ubuntu-regression-suite is pointless, if one cannot boot the kernel == Regression Potential == There are a couple of flaky tests which will start to show up, rather than only successful runs (which should have been a suspicious thing). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999528/+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 2001618] Re: BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9
This bug is awaiting verification that the linux-riscv/5.19.0-1013.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-kinetic ** Tags added: kernel-spammed-kinetic-linux-riscv verification-needed-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/2001618 Title: BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] The BPF_AND, BPF_OR, BPF_XOR, BPF_FETCH, BPF_XCHG and BPF_CMPXCHG related tests will fail in net:test_bpf test from ubuntu_kernel_selftests as they are not supported. test_bpf: #361 BPF_ATOMIC | BPF_W, BPF_AND: Test: 0x12 & 0xab = 0x02 eBPF filter atomic op code c3 (@3) unsupported FAIL to select_runtime err=-524 ... test_bpf: #365 BPF_ATOMIC | BPF_W, BPF_AND | BPF_FETCH: Test: 0x12 & 0xab = 0x02 eBPF filter atomic op code c3 (@3) unsupported FAIL to select_runtime err=-524 ... test_bpf: #377 BPF_ATOMIC | BPF_W, BPF_OR: Test: 0x12 | 0xab = 0xbb FAIL to select_runtime err=-524 ... test_bpf: #393 BPF_ATOMIC | BPF_W, BPF_XOR: Test: 0x12 ^ 0xab = 0xb9 FAIL to select_runtime err=-524 ... test_bpf: #409 BPF_ATOMIC | BPF_W, BPF_XCHG: Test: 0x12 xchg 0xab = 0xab eBPF filter atomic op code c3 (@3) unsupported FAIL to select_runtime err=-524 ... test_bpf: #417 BPF_ATOMIC | BPF_W, BPF_CMPXCHG: Test successful return eBPF filter atomic op code c3 (@3) unsupported FAIL to select_runtime err=-524 ... test_bpf: Summary: 894 PASSED, 132 FAILED, [882/882 JIT'ed] Please find attachment for the complete test log. [Fix] * 6511270911 powerpc/bpf/64: add support for BPF_ATOMIC bitwise operations * dbe6e2456f powerpc/bpf/64: add support for atomic fetch operations * 1e82dfaa78 powerpc/bpf/64: Add instructions for atomic_[cmp]xchg These patches can be cherry-picked into Kinetic kernel. [Test] Test kernel can be found here: https://people.canonical.com/~phlin/kernel/lp-2001618-ppcbpf/ Steps: 1. Reboot with the patched kernel 2. Run: sudo dmesg -C sudo modprobe test_bpf sudo dmesg Tested with Power9 node baltar, with the patched kernel there will be no failure reported by the test_bpf: test_bpf: Summary: 1026 PASSED, 0 FAILED, [1014/1014 JIT'ed] [Where problems could occur] This patchset just broaden the BPF operations support on ppc64, we might see some new failures when using these instruction somewhere in the future. Cascardo: The existing atomic operations may regress as well, since they now produce different code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2001618/+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 2006038] Re: [Asus ZenBook UX325EA] Can't wake from sleep (when power adapter plugged in)
Is there any way to change the sleep state the os goes into? There's no way to change it in the bios. -- 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/2006038 Title: [Asus ZenBook UX325EA] Can't wake from sleep (when power adapter plugged in) Status in linux package in Ubuntu: Confirmed Bug description: on an Asus zenbook, 2022. When power is plugged in and screen goes to sleep, I can't get back, even with ctrl-alt-f1. I have to do a hard reboot. Here's my uname: Linux sleeky 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 4 17:21:51 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:1452] InstallationDate: Installed on 2023-01-13 (22 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX325EA_UX325EA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=9d28c423-b126-49e5-9092-3ea7e2e68951 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX325EA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX325EA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.8 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX325EA.308:bd07/29/2021:br5.19:efr3.8:svnASUSTeKCOMPUTERINC.:pnZenBookUX325EA_UX325EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX325EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX325EA_UX325EA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006038/+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 2006955] Re: [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 5.15.0-58-generic works)
Update: I rebooted to 5.15.0-58, then 5.15.0-57, and now the same thing happens on all my kernels (only 1 monitor detected). If it helps, a while ago I installed the `amdgpu-install` script from AMD which installed a few packages. I removed `amdgpu-dmks` since it failed to compile with any kernel I could install. I'm not entirely sure if I had a working (3 screens) kernel update since installing those. I tried running `amdgpu-install --uninstall`, but it listed for removal more packages than it installed, and I'm not sure if some base drivers would be wiped away. I can't really afford to have an unusable system for a while. Those packages were listed for removal: ``` The following packages will be REMOVED: amdgpu-core* amdgpu-dkms* amdgpu-dkms-firmware* amdgpu-lib* comgr* gst-omx-amdgpu* hip-runtime-amd* hsa-rocr* hsa-rocr-dev* hsakmt-roct-dev* libdrm-amdgpu-amdgpu1* libdrm-amdgpu-common* libdrm-amdgpu-radeon1* libdrm2-amdgpu* libegl1-amdgpu-mesa* libegl1-amdgpu-mesa-drivers* libgbm1-amdgpu* libgl1-amdgpu-mesa-dri* libgl1-amdgpu-mesa-glx* libglapi-amdgpu-mesa* libllvm14.0.50200-amdgpu* libwayland-amdgpu-client0* libwayland-amdgpu-egl1* libwayland-amdgpu-server0* libxatracker2-amdgpu* mesa-amdgpu-omx-drivers* mesa-amdgpu-va-drivers* mesa-amdgpu-vdpau-drivers* rocm-core* rocm-hip-runtime* rocm-language-runtime* rocm-llvm* rocm-ocl-icd* rocm-opencl* rocm-opencl-runtime* rocminfo* xserver-xorg-amdgpu-video-amdgpu* ``` Should I try removing them anyways? -- 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/2006955 Title: [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 5.15.0-58-generic works) Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors, but since very recently (yesterday or so), only 1 of them seems to be detected. In the Settings app, under "Screen Display", I used to have a place where I can move my monitors relatively to each other, and adjust each of their settings. Now, I no longer have the monitor drag-and-drop zone, I only have one detected "Unknown display", fixed at 1920x1080 77.00 Hz (physically, it's a 1920x1080 144Hz) and I cannot change any setting except orientation, scaling, and fractional scaling. The bug started happening just when the kernel was auto-updated to 5.15.0-60-generic from 5.15.0-58-generic. `uname -a` reports: `Linux user-desktop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux`. When I reboot with 5.15.0-58-generic, all of my 3 displays are detected and working fine. I also noticed the same problem happened when I installed 5.15.0-58-lowlatency. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 10 11:00:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-57-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-60-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1462:3816] InstallationDate: Installed on 2021-01-27 (743 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B550 Phantom Gaming 4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd08/13/2020:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M.
[Kernel-packages] [Bug 2006955] Re: [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 5.15.0-58-generic works)
I ran `sudo apt reinstall linux-modules-extra-5.15.0-60-generic`, which printed: ``` Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 2 not upgraded. Need to get 0 B/64.0 MB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 457278 files and directories currently installed.) Preparing to unpack .../linux-modules-extra-5.15.0-60-generic_5.15.0-60.66_amd64 .deb ... Unpacking linux-modules-extra-5.15.0-60-generic (5.15.0-60.66) over (5.15.0-60.6 6) ... Setting up linux-modules-extra-5.15.0-60-generic (5.15.0-60.66) ... Processing triggers for linux-image-5.15.0-60-generic (5.15.0-60.66) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.15.0-60-generic ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.15.0-60-generic W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vangogh_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. /etc/kernel/postinst.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.0-60-generic Found initrd image: /boot/initrd.img-5.15.0-60-generic Found linux image: /boot/vmlinuz-5.15.0-58-generic Found initrd image: /boot/initrd.img-5.15.0-58-generic Found linux image: /boot/vmlinuz-5.15.0-57-generic Found initrd image: /boot/initrd.img-5.15.0-57-generic Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting Warning: os-prober will not be executed to detect other bootable partitions. Systems on them will not be added to the GRUB boot configuration. Check GRUB_DISABLE_OS_PROBER documentation entry. Adding boot menu entry for UEFI Firmware Settings ... done ``` I rebooted to 5.15.0-60 and ran the command, journal.txt is attached. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006955/+attachment/5646813/+files/journal.txt -- 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/2006955 Title: [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 5.15.0-58-generic works) Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors, but since very recently (yesterday or so), only 1 of them seems to be detected. In the Settings app, under "Screen Display", I used to have a place where I can move my monitors relatively to each other, and adjust each of their settings. Now, I no longer have the monitor drag-and-drop zone, I only have one detected "Unknown display", fixed at 1920x1080 77.00 Hz (physically, it's a 1920x1080 144Hz) and I cannot change any setting except orientation, scaling, and fractional scaling. The bug started happening just when the kernel was auto-updated to 5.15.0-60-generic from 5.15.0-58-generic. `uname -a` reports: `Linux user-desktop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux`. When I reboot with 5.15.0-58-generic, all of my 3 displays are detected and working fine. I also noticed the same problem happened when I installed 5.15.0-58-lowlatency. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 10 11:00:59 2023 DistUpgraded: Fresh install DistroCodename: jammy
[Kernel-packages] [Bug 2006781] Re: 5.19.0-28
Confirmed. Unable to run command. -- 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/2006781 Title: 5.19.0-28 Status in linux package in Ubuntu: Incomplete Bug description: Will not connect to wifi. Unable to establish wifi connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006781/+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 2006458] Re: Frequent wakeups on HP Pro x360 435 13.3 inch G9 using Qualcomm FastConnect 6900
> Anyway, I still don't get why upgrading the wifi-cards firmware to a > more recent version fixes the problem. > Would you mind to elaborate on this a bit more? When the system is in the hardware sleep state it can be woken up from either a GPIO or a GPE. Any of those ACPI events I mentioned will make the EC trigger such a wakeup. When the kernel wakes up it will process the ACPI events and then confirm whether there are any remaining interrupts active. * If no interrupts are active, the system will enter back into hardware sleep state. * If any interrupts are still active then the kernel treats it as a genuine wakeup source that should exit the s2idle loop. What happens with this bug is that the WLAN controller is connected to a design specific GPIO, and when the system leaves hardware sleep state that GPIO is also triggered. This means that two interrupts are active: 1 for that GPIO and 1 for the EC SCI. The firmware update for the WLAN controller fixes it so that the GPIO is not active during resume. -- 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/2006458 Title: Frequent wakeups on HP Pro x360 435 13.3 inch G9 using Qualcomm FastConnect 6900 Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Jammy: New Status in linux-firmware source package in Kinetic: New Status in linux-firmware source package in Lunar: New Bug description: To whom it may concern: I was experiencing frequent wake-ups from s0i3x on a HP Pro 435 G9 convertible [1] using the Qualcomm FastConnect 6900 Soc [2]. The issue is related to FW revision WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9 that comes bundled with Ubuntu 22.10. It appears the SoC increasingly triggering wake-ups after being suspended for approx. 4 hrs. Read the full story at [4]. The solution is to upgrade SoC firmware to rev WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23/ [3] Best regards,Carsten [1] https://support.hp.com/us-en/product/hp-pro-x360-435-13.3-inch-g9-notebook-pc/2101144107/document/ish_6053745-6053789-16 [2] https://www.qualcomm.com/products/technology/wi-fi/fastconnect/fastconnect-6900 [3] https://github.com/kvalo/ath11k-firmware/tree/master/WCN6855/hw2.0/1.1/WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23 [4] https://gitlab.freedesktop.org/drm/amd/-/issues/2377 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2006458/+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 1982479] Re: [Medion Akoya E3223] Latest kernel breaks LCD screen
P.S. See also: https://gitlab.freedesktop.org/drm/intel/-/issues/5569#note_1770070 And maybe try running this to fix the problem temporarily: xrandr --output eDP-1 --off; sleep 3; xrandr --output eDP-1 --auto ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #5569 https://gitlab.freedesktop.org/drm/intel/-/issues/5569 -- 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/1982479 Title: [Medion Akoya E3223] Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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 1982479] Re: [Medion Akoya E3223] Latest kernel breaks LCD screen
Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191#yui_3_10_3_1_1676292775910_1524 Maybe these kernel boot parameters can workaround the problem: intel_idle.max_cstate=2 i915.enable_dc=0 i915.enable_psr=0 (if cstate 2 doesn't help, try limiting cstate to 1 or even 0) -- 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/1982479 Title: [Medion Akoya E3223] Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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 1806488] Re: Support non-strict iommu mode on arm64
This bug was fixed in the package linux-aws - 5.15.0-1030.34 --- linux-aws (5.15.0-1030.34) jammy; urgency=medium * jammy/linux-aws: 5.15.0-1030.34 -proposed tracker (LP: #2003424) [ Ubuntu: 5.15.0-60.66 ] * jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450) * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux-aws (5.15.0-1029.33) jammy; urgency=medium * jammy/linux-aws: 5.15.0-1029.33 -proposed tracker (LP: #2001759) * Jammy update: v5.15.75 upstream stable release (LP: #1996825) // Jammy update: v5.15.76 upstream stable release (LP: #1997113) - [Config] aws: Update configs after rebase * Support non-strict iommu mode on arm64 (LP: #1806488) - [Config] aws: CONFIG_IOMMU_DEFAULT_DMA_LAZY=y for arm64 [ Ubuntu: 5.15.0-59.65 ] * jammy/linux: 5.15.0-59.65 -proposed tracker (LP: #2001801) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2022-47940 - ksmbd: validate length in smb2_write() * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x * support for same series backports versioning numbers (LP: #1993563) - [Packaging] sameport -- add support for sameport versioning * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Micron NVME storage failure [1344,5407] (LP: #1998883) - nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH * Jammy update: v5.15.78 upstream stable release (LP: #1998843) - scsi: lpfc: Rework MIB Rx Monitor debug info logic - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - KVM: x86: Treat #DBs from the emulator as fault-like (code and DR7.GD=1) - drm/amd/display: explicitly disable psr_feature_enable appropriately - mm/hugetlb: fix races when looking up a CONT-PTE/PMD size hugetlb page - HID: playstation: add initial DualSense Edge controller support - KVM: x86: Protect the unused bits in MSR exiting flags - KVM: x86: Copy filter arg outside kvm_vm_ioctl_set_msr_filter() - KVM: x86: Add compat handler for KVM_X86_SET_MSR_FILTER - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Remove magic number - RDMA/hns: Use hr_reg_xxx() instead of remaining roce_set_xxx() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net,
[Kernel-packages] [Bug 2002658] Re: Kinetic linux-azure - Enable TDX guest driver w/MSFT Hyper-v
This bug was fixed in the package linux-azure - 5.19.0-1020.21 --- linux-azure (5.19.0-1020.21) kinetic; urgency=medium * kinetic/linux-azure: 5.19.0-1020.21 -proposed tracker (LP: #2004085) * Azure: Fix TDX backport (LP: #2004087) - SAUCE: TDX: Fixed botched backport linux-azure (5.19.0-1019.20) kinetic; urgency=medium * kinetic/linux-azure: 5.19.0-1019.20 -proposed tracker (LP: #2003415) * Azure: TDX enabled hyper-visors cause segfault (LP: #2003714) - SAUCE: TDX: Work around the segfault issue in glibc 2.35 in Ubuntu 22.04. [ Ubuntu: 5.19.0-31.32 ] * kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423) * amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks (LP: #2003524) - drm/amd: Delay removal of the firmware framebuffer * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux-azure (5.19.0-1018.19) kinetic; urgency=medium * kinetic/linux-azure: 5.19.0-1018.19 -proposed tracker (LP: #2001745) * Kinetic update: upstream stable patchset 2022-11-14 (LP: #1996540) - [Config] azure: updateconfigs after rebase * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.01.02) * Kinetic linux-azure - Enable TDX guest driver w/MSFT Hyper-v (LP: #2002658) - clocksource/drivers/hyperv: add data structure for reference TSC MSR - Revert "UBUNTU: SAUCE: x86/tdx: Add TDX Guest attestation interface driver" - Revert "UBUNTU: SAUCE: selftests: tdx: Test GetReport TDX attestation feature" - Revert "x86/hyper-v: Add hyperv Isolation VM check in the cc_platform_has()" - SAUCE: x86/tdx: Add a wrapper to get TDREPORT0 from the TDX Module - SAUCE: virt: Add TDX guest driver - SAUCE: selftests/tdx: Test TDX attestation GetReport support - SAUCE: tdx: enable DEBUG: tools/testing/selftests/tdx/tdx_guest_test.c - SAUCE: tdx: swiotlb: check set_memory_decrypted()'s return value - SAUCE: tdx: x86/sev: mem_encrypt_free_decrypted_mem(): encrypt the pages for AMD SME only - SAUCE: tdx: x86/hyperv: Do not run swiotlb_update_mem_attributes() in hyperv_init() - SAUCE: tdx: x86/tdx: Retry TDVMCALL_MAP_GPA() when needed - SAUCE: tdx: x86/tdx: Support vmalloc() for tdx_enc_status_changed() - SAUCE: tdx: x86/hyperv: Add hv_isolation_type_tdx() to detect TDX guests - SAUCE: tdx: x86/tdx: Expand __tdx_hypercall() to handle more arguments - SAUCE: tdx: x86/hyperv: Support hypercalls for TDX guests - SAUCE: tdx: Drivers: hv: vmbus: Support TDX guests - SAUCE: tdx: x86/hyperv: Fix serial console interrupts for TDX guests - [Config] azure: Enable TDX guest driver - SAUCE: tdx: Drivers: hv: vmbus:: Fix the ARM64 build caused by recent TDX patches [ Ubuntu: 5.19.0-30.31 ] * kinetic/linux: 5.19.0-30.31 -proposed tracker (LP: #2001756) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/2023.01.02) * Add some ACPI device IDs for Intel HID device (LP: #1995453) - platform/x86/intel/hid: Add some ACPI device IDs * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x riscv64 * BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9 (LP: #2001618) - powerpc/bpf/64: add support for BPF_ATOMIC bitwise operations - powerpc/bpf/64: add support for atomic fetch operations - powerpc/bpf/64: Add instructions for atomic_[cmp]xchg * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Kinetic update: upstream stable patchset 2022-12-15 (LP: #1999828) - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in
[Kernel-packages] [Bug 2004087] Re: Azure: Fix TDX backport
This bug was fixed in the package linux-azure - 5.19.0-1020.21 --- linux-azure (5.19.0-1020.21) kinetic; urgency=medium * kinetic/linux-azure: 5.19.0-1020.21 -proposed tracker (LP: #2004085) * Azure: Fix TDX backport (LP: #2004087) - SAUCE: TDX: Fixed botched backport linux-azure (5.19.0-1019.20) kinetic; urgency=medium * kinetic/linux-azure: 5.19.0-1019.20 -proposed tracker (LP: #2003415) * Azure: TDX enabled hyper-visors cause segfault (LP: #2003714) - SAUCE: TDX: Work around the segfault issue in glibc 2.35 in Ubuntu 22.04. [ Ubuntu: 5.19.0-31.32 ] * kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423) * amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks (LP: #2003524) - drm/amd: Delay removal of the firmware framebuffer * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux-azure (5.19.0-1018.19) kinetic; urgency=medium * kinetic/linux-azure: 5.19.0-1018.19 -proposed tracker (LP: #2001745) * Kinetic update: upstream stable patchset 2022-11-14 (LP: #1996540) - [Config] azure: updateconfigs after rebase * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.01.02) * Kinetic linux-azure - Enable TDX guest driver w/MSFT Hyper-v (LP: #2002658) - clocksource/drivers/hyperv: add data structure for reference TSC MSR - Revert "UBUNTU: SAUCE: x86/tdx: Add TDX Guest attestation interface driver" - Revert "UBUNTU: SAUCE: selftests: tdx: Test GetReport TDX attestation feature" - Revert "x86/hyper-v: Add hyperv Isolation VM check in the cc_platform_has()" - SAUCE: x86/tdx: Add a wrapper to get TDREPORT0 from the TDX Module - SAUCE: virt: Add TDX guest driver - SAUCE: selftests/tdx: Test TDX attestation GetReport support - SAUCE: tdx: enable DEBUG: tools/testing/selftests/tdx/tdx_guest_test.c - SAUCE: tdx: swiotlb: check set_memory_decrypted()'s return value - SAUCE: tdx: x86/sev: mem_encrypt_free_decrypted_mem(): encrypt the pages for AMD SME only - SAUCE: tdx: x86/hyperv: Do not run swiotlb_update_mem_attributes() in hyperv_init() - SAUCE: tdx: x86/tdx: Retry TDVMCALL_MAP_GPA() when needed - SAUCE: tdx: x86/tdx: Support vmalloc() for tdx_enc_status_changed() - SAUCE: tdx: x86/hyperv: Add hv_isolation_type_tdx() to detect TDX guests - SAUCE: tdx: x86/tdx: Expand __tdx_hypercall() to handle more arguments - SAUCE: tdx: x86/hyperv: Support hypercalls for TDX guests - SAUCE: tdx: Drivers: hv: vmbus: Support TDX guests - SAUCE: tdx: x86/hyperv: Fix serial console interrupts for TDX guests - [Config] azure: Enable TDX guest driver - SAUCE: tdx: Drivers: hv: vmbus:: Fix the ARM64 build caused by recent TDX patches [ Ubuntu: 5.19.0-30.31 ] * kinetic/linux: 5.19.0-30.31 -proposed tracker (LP: #2001756) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/2023.01.02) * Add some ACPI device IDs for Intel HID device (LP: #1995453) - platform/x86/intel/hid: Add some ACPI device IDs * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x riscv64 * BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9 (LP: #2001618) - powerpc/bpf/64: add support for BPF_ATOMIC bitwise operations - powerpc/bpf/64: add support for atomic fetch operations - powerpc/bpf/64: Add instructions for atomic_[cmp]xchg * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Kinetic update: upstream stable patchset 2022-12-15 (LP: #1999828) - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in
[Kernel-packages] [Bug 2006797] Re: MT7922 firmware not working
There's new MT79xx firmware available from upstream kernel.org: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/mediatek Copy the following files to /lib/firmware/mediatek on your machine (make backups first): BT_RAM_CODE_MT7922_1_1_hdr.bin BT_RAM_CODE_MT7961_1_2_hdr.bin WIFI_MT7922_patch_mcu_1_1_hdr.bin WIFI_RAM_CODE_MT7922_1.bin WIFI_MT7961_patch_mcu_1_2_hdr.bin WIFI_RAM_CODE_MT7961_1.bin Reboot and check if that makes a difference. -- 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/2006797 Title: MT7922 firmware not working Status in linux package in Ubuntu: Confirmed Bug description: Hey I have a "ASUS ROG Strix B650-A Gaming WIFI" (https://rog.asus.com/motherboards/rog-strix/rog-strix-b650-a-gaming- wifi-model/) Motherboard and the WiFi/Bluetooth is not working. On windows, the module is working fine. Using "Kubuntu 22.10" with Kernel "5.19.0-35-generic" lshw -class network: *-network description: Network controller product: MT7922 802.11ax PCI Express Wireless Network Adapter vendor: MEDIATEK Corp. physical id: 0 bus info: pci@:0b:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm bus_master cap_list configuration: driver=mt7921e latency=0 resources: iomemory:fc0-fbf irq:119 memory:fc3030-fc303f memory:fc50-fc507fff #dmesg | grep mt7921e [ 17.001057] mt7921e :0b:00.0: enabling device ( -> 0002) [ 17.001199] mt7921e :0b:00.0: ASIC revision: 79220010 [ 20.247369] mt7921e :0b:00.0: Message 0004008a (seq 1) timeout [ 23.575534] mt7921e :0b:00.0: Message 0004008a (seq 2) timeout [ 26.907372] mt7921e :0b:00.0: Message 0004008a (seq 3) timeout [ 30.231376] mt7921e :0b:00.0: Message 0004008a (seq 4) timeout [ 33.559704] mt7921e :0b:00.0: Message 0004008a (seq 5) timeout [ 36.887365] mt7921e :0b:00.0: Message 0004008a (seq 6) timeout [ 40.215367] mt7921e :0b:00.0: Message 0004008a (seq 7) timeout [ 43.543670] mt7921e :0b:00.0: Message 0004008a (seq 8) timeout [ 46.871378] mt7921e :0b:00.0: Message 0004008a (seq 9) timeout [ 50.199714] mt7921e :0b:00.0: Message 0004008a (seq 10) timeout [ 50.280219] mt7921e :0b:00.0: hardware init failed ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Feb 10 03:33:02 2023 InstallationDate: Installed on 2023-02-09 (0 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: ASUS System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-35-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022 dmi.bios.release: 8.23 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0823 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B650-A GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0823:bd11/21/2022:br8.23:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB650-AGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006797/+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 2002601] Re: Wireless: Enable RTL8852BE wifi driver
** Tags added: originate-from-2006879 ** Tags added: sutton -- 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/2002601 Title: Wireless: Enable RTL8852BE wifi driver Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Justification] Enable Realtek RLT8852BE WIFI. [Test] 1. put rtw8852b_fw.bin in /lib/firmware/rtw89/ 2. boot-up with kernel enabled RTL8852be. 3. Connect to WIFI-AP and test with ping. * ping -I wlp2s0 8.8.8.8 ~~~ PING 8.8.8.8 (8.8.8.8) from 10.102.137.55 wlp2s0: 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=5.86 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=6.21 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=18.9 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=6.09 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=6.13 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=5.77 ms ~~~ * Connected to AP ~~~ u@ubuntu:~$ nmcli dev DEVICE TYPE STATE CONNECTION enp3s0 ethernet connected Wired connection 1 wlp2s0 wifi connected Canonical p2p-dev-wlp2s0 wifi-p2p disconnected -- lo loopback unmanaged -- ~~~ * lsmod | grep 8852 ~~~ lsmod | grep 8852 rtw89_8852be 16384 0 rtw89_8852b 368640 1 rtw89_8852be rtw89_pci 61440 1 rtw89_8852be rtw89_core 442368 2 rtw89_8852b,rtw89_pci cfg80211 1081344 3 rtw89_8852b,rtw89_core,mac80211 ~~~ 4. cbd's built result, Lunar, ~~~ remote: Resolving deltas: 100% (391/391), completed with 118 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'u_lMstrNxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-lunar-0e58018b43c1-ioeM remote: * 96/480 cores busy (1/5 hosts), 0 builds queued remote: 2023-01-12 03:16:35 kobako-lunar-0e58018b43c1-ioeM/amd64/BUILD-OK remote: 2023-01-12 03:17:47 kobako-lunar-0e58018b43c1-ioeM/arm64/BUILD-OK remote: 2023-01-12 03:11:36 kobako-lunar-0e58018b43c1-ioeM/armhf/BUILD-OK remote: 2023-01-12 03:16:30 kobako-lunar-0e58018b43c1-ioeM/ppc64el/BUILD-OK remote: 2023-01-12 03:10:24 kobako-lunar-0e58018b43c1-ioeM/s390x/BUILD-OK remote: To cbd:lunar.git ~~~ OEM-6.1, remote: Resolving deltas: 100% (399/399), completed with 121 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'oem-6.1-next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-c1002f30ccc3-m65z remote: * 0/192 cores busy (0/2 hosts), 0 builds queued remote: 2023-01-12 05:25:23 kobako-jammy-c1002f30ccc3-m65z/amd64/BUILD-OK remote: To cbd:jammy.git [Where problems could occur] Medium, a new driver so the current driver may have some edge cases didn't consider. [Misc] * For generic Jammy, need more patches to enable RTL8852be so only SRU for OEM-6.1. * firmware, dae5d4603b07) rtw89: 8852b: update fw to v0.27.32.1 has landed on Lunar, so only SRU for Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002601/+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 2002834] Re: Network bridge issue after updating kernel to 5.4.0-137
On Ubuntu 20.04 with new released Kernel 5.4.0-139 also not working. Guest 18.04 connected over Bridge on Host. Currently I stay on kernel < 5.4.0-137 and everything works fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2002834 Title: Network bridge issue after updating kernel to 5.4.0-137 Status in linux-meta package in Ubuntu: Confirmed Bug description: Hello, After updating the kernel from 5.4.0-136 to 5.4.0-137 network bridge are not working any more. I can see the bridge with "ip add show" or "brctl show". Network is up and I can reach the full network from the host through the bridge. VM on the host can not reach network or host and host can not reach the VM through the bridge. We have bonded interface used in the bridge and one bridge without IP and one with an IP. DHCP is off on booth bridge. Downgrading the kernel to 5.4.136 (Ubuntu 5.4.0-136.153-generic 5.4.218) seem to work fine. Thank you for your help. Details Description: Ubuntu 20.04.5 LTS Release: 20.04 Not working version => Ubuntu 5.4.0-137.154-generic 5.4.218 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2002834/+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 2002834] Re: Network bridge issue after updating kernel to 5.4.0-137
I can confirm for Ubuntu 22.04, but also affects Ubuntu 18.04 (all using a dummy bridge for Xen domUs in my case). -> last working: 22.04: - linux-image-5.15.0-57-generic 18.04: - linux-image-4.15.0-201-generic -> broken: 22.04: - linux-image-5.15.0-58-generic - linux-image-5.15.0-60-generic 18.04: - linux-image-4.15.0-202-generic - linux-image-4.15.0-204-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2002834 Title: Network bridge issue after updating kernel to 5.4.0-137 Status in linux-meta package in Ubuntu: Confirmed Bug description: Hello, After updating the kernel from 5.4.0-136 to 5.4.0-137 network bridge are not working any more. I can see the bridge with "ip add show" or "brctl show". Network is up and I can reach the full network from the host through the bridge. VM on the host can not reach network or host and host can not reach the VM through the bridge. We have bonded interface used in the bridge and one bridge without IP and one with an IP. DHCP is off on booth bridge. Downgrading the kernel to 5.4.136 (Ubuntu 5.4.0-136.153-generic 5.4.218) seem to work fine. Thank you for your help. Details Description: Ubuntu 20.04.5 LTS Release: 20.04 Not working version => Ubuntu 5.4.0-137.154-generic 5.4.218 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2002834/+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 2007004] Re: rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected
** Description changed: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. This problem occurs with the rtw88_8821ce driver Workaround was to blacklist rtw88_8821ce and install rtl8821ce + When disconnecting from a WiFi network, or turning of WiFi altogether, + or booting up at a location where there is no remembered WiFi + connection, my bluetooth Logitech MX 2S freezes, then begins to rapidly + disconnect/reconnect about 3-4 times a second. root@ithaca:~ # uname -a - Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 - GNU/Linux + Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC + 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: - Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA - v: 1.0 serial: - Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX - UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 + Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop + E410MA_E410MA v: 1.0 serial: + Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX + UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter - driver: rtw_8821ce + driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb - Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 + Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: + 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered - (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, - then about 10 seconds elapse, then the below messages start) + (At this point I disconnect WiFI. Mouse starts acting up immediately, + responding erratically, then about 10 seconds elapse, then the below + messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no - (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) + (This goes on and on about 3 times a second until + I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated
[Kernel-packages] [Bug 2004534] Re: Lenovo IdeaPad 3 15ABA7 never wakes from sleep
Also, comment #numbers can be found on this page: https://launchpad.net/bugs/2004534 That's probably easier to follow than email. -- 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/2004534 Title: Lenovo IdeaPad 3 15ABA7 never wakes from sleep Status in linux package in Ubuntu: Confirmed Bug description: - on locked screen: the keyboard blocks after a while and I cannot login anymore; - on unlocked screen: = apps do not start (failed to start); = no icon pictures on desktop; = no wallpaper anymore (black background); ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 2 07:15:13 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo [1002:15e7] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] InstallationDate: Installed on 2023-02-01 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 82RN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=b63af605-bd2f-4b16-8bb4-1cc9bb85554c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2022 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: JTCN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ABA7 dmi.ec.firmware.release: 1.38 dmi.modalias: dmi:bvnLENOVO:bvrJTCN38WW:bd08/04/2022:br1.38:efr1.38:svnLENOVO:pn82RN:pvrIdeaPad315ABA7:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315ABA7:skuLENOVO_MT_82RN_BU_idea_FM_IdeaPad315ABA7: dmi.product.family: IdeaPad 3 15ABA7 dmi.product.name: 82RN dmi.product.sku: LENOVO_MT_82RN_BU_idea_FM_IdeaPad 3 15ABA7 dmi.product.version: IdeaPad 3 15ABA7 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004534/+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