[Kernel-packages] [Bug 159356] Re: When DMA is disabled system freeze on high memory usage
** Also affects: gentoo Importance: Undecided Status: New -- 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/159356 Title: When DMA is disabled system freeze on high memory usage Status in linux package in Ubuntu: Incomplete Status in linux package in Arch Linux: New Status in Gentoo Linux: New Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+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 1969874] Re: Bluetooth Mouse and Keyboard drop connections when Laptop using battery
Please try Ubuntu 22.04 which was just released yesterday: https://ubuntu.com/download/desktop ** Tags added: impish ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1969874 Title: Bluetooth Mouse and Keyboard drop connections when Laptop using battery Status in bluez package in Ubuntu: Incomplete Bug description: Bluetooth Mouse and Keyboard drop connections when Laptop using battery (power discconnected). Keyboard and mouse work correctly when laptop is powered by mains power. May be related to suspend/resume. Symptoms: - Mouse and keyboard don't work. - Mouse and keyboard bluetooth association cannot be removed rand e-connected. - Mouse and keyboard are detected (sometimes) with different device names. The following does NOT fix the problem:: - Connect laptop power; - In Bluetooth settings Turn Bluetooth off, then on again Rebooting allows devices to be configured again, and connect correctly. Ubuntu version: Ubuntu 21.10 Kernel: 5.13.0-39-generic Package: bluez 5.60-0ubuntu2.2 When working the keyboard and mouse appear with: root@silver:/home/paul# bluetoothctl devices Device D2:91:D2:B9:6B:9D Logi POP Keys Device D1:8F:A4:4B:1B:F9 Logi POP Mouse When not working, the devices show up as: Device D2:91:D2:B9:6B:9D Logi POP @ Device D1:8F:A4:4B:1B:F9 Logi POP @ This devices are: - https://www.logitech.com/en-au/products/mice/pop-wireless-mouse.910-006515.html - https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-010578.html I know that the devices both work with a Windows 10 desktop. Bluetooth Device Details When working.. root@silver:/home/paul# hciconfig -a hci0: Type: Primary Bus: USB BD Address: 20:68:9D:64:8A:FC ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:1801269 acl:99624 sco:0 events:560 errors:0 TX bytes:8612 acl:173 sco:0 commands:227 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'silver' Class: 0x7c010c Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Laptop HCI Version: 4.0 (0x6) Revision: 0x1000 LMP Version: 4.0 (0x6) Subversion: 0x220e Manufacturer: Broadcom Corporation (15) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1969874/+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 1969771] Re: Fix beacon loss for rtl8821ce on certain platforms
** No longer affects: linux (Ubuntu) ** Description changed: [SRU Justification] [Impact] - On the intel ADL-U platform, the rtl8821ce suffers the beacon loss frequently because the driver doesn't received any beacon from AP. It causes the wpa-supplicant to reconnect again and again. + On the intel ADL-U platform, the rtl8821ce suffers the beacon loss frequently because the driver doesn't received any beacon from AP. It causes the wpa-supplicant to reconnect again and again. Given it's critical to user experience and the urgent schedule, we need to SRU before getting approval. [Fix] Realtek release a fix to disable the PCI completion timeout on rtl8821ce so the PCI bus won't get stuck and can handed the received packets to the driver correctly. [Test Case] 1. Connect the WiFi to internet by selecting a internet connected AP 2. ping 8.8.8.8 to check the internet connectivity for at least 5 minutes. 3. Make sure no 'CTRL-EVENT-BEACON-LOSS' event reported from wpa_supplicant [Where problems could occur] Risk should be Low. It's only applied for RTL8821CE to disable the completion timeout capability. == Original Bug Description == [Summary] Wireless keeps connection and loses connection repeatedly. Below test cases are failed: - wireless/wireless_connection_wpa_n_nm_wlp3s0 - after-suspend-wireless/wireless_connection_wpa_bg_nm_wlp3s0 - after-suspend-wireless/wireless_connection_wpa_ac_nm_wlp3s0 - after-suspend-wireless/wireless_connection_open_n_nm_wlp3s0 - after-suspend-wireless/wireless_connection_open_bg_nm_wlp3s0 - after-suspend-wireless/wireless_connection_open_ac_nm_wlp3s0 Issue is also observed on WVA4-DVT2-C1 [Steps to reproduce] 1. Boot into OS 2. Connect network by wireless 3. Run 'sudo apt update' [Expected result] Wireless connection won't break [Actual result] Wireless loses the connection and then connect network, after a while, issue happens again. [Failure rate] 10/10 [Additional information] CID: 202202-29949, 202202-29947 SKU: WMVA5-DVT2-C1, WVA4-DVT2-C1 Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-olly-adl+X175 system-manufacturer: Dell Inc. system-product-name: Vostro 3520 bios-version: 0.5.4 CPU: 12th Gen Intel(R) Core(TM) i5-1235U (12x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4628] (rev 0c) :01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1f9f] (rev a1) kernel-version: 5.14.0-1024-oem [Stage] Issue reported and logs collected at a later stage -- 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/1969771 Title: Fix beacon loss for rtl8821ce on certain platforms Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.14 source package in Focal: New Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: [SRU Justification] [Impact] On the intel ADL-U platform, the rtl8821ce suffers the beacon loss frequently because the driver doesn't received any beacon from AP. It causes the wpa-supplicant to reconnect again and again. Given it's critical to user experience and the urgent schedule, we need to SRU before getting approval. [Fix] Realtek release a fix to disable the PCI completion timeout on rtl8821ce so the PCI bus won't get stuck and can handed the received packets to the driver correctly. [Test Case] 1. Connect the WiFi to internet by selecting a internet connected AP 2. ping 8.8.8.8 to check the internet connectivity for at least 5 minutes. 3. Make sure no 'CTRL-EVENT-BEACON-LOSS' event reported from wpa_supplicant [Where problems could occur] Risk should be Low. It's only applied for RTL8821CE to disable the completion timeout capability. == Original Bug Description == [Summary] Wireless keeps connection and loses connection repeatedly. Below test cases are failed: - wireless/wireless_connection_wpa_n_nm_wlp3s0 - after-suspend-wireless/wireless_connection_wpa_bg_nm_wlp3s0 - after-suspend-wireless/wireless_connection_wpa_ac_nm_wlp3s0 - after-suspend-wireless/wireless_connection_open_n_nm_wlp3s0 - after-suspend-wireless/wireless_connection_open_bg_nm_wlp3s0 - after-suspend-wireless/wireless_connection_open_ac_nm_wlp3s0 Issue is also observed on WVA4-DVT2-C1 [Steps to reproduce] 1. Boot into OS 2. Connect network by wireless 3. Run 'sudo apt update' [Expected result] Wireless connection won't break [Actual result]
[Kernel-packages] [Bug 1969874] [NEW] Bluetooth Mouse and Keyboard drop connections when Laptop using battery
Public bug reported: Bluetooth Mouse and Keyboard drop connections when Laptop using battery (power discconnected). Keyboard and mouse work correctly when laptop is powered by mains power. May be related to suspend/resume. Symptoms: - Mouse and keyboard don't work. - Mouse and keyboard bluetooth association cannot be removed rand e-connected. - Mouse and keyboard are detected (sometimes) with different device names. The following does NOT fix the problem:: - Connect laptop power; - In Bluetooth settings Turn Bluetooth off, then on again Rebooting allows devices to be configured again, and connect correctly. Ubuntu version: Ubuntu 21.10 Kernel: 5.13.0-39-generic Package: bluez 5.60-0ubuntu2.2 When working the keyboard and mouse appear with: root@silver:/home/paul# bluetoothctl devices Device D2:91:D2:B9:6B:9D Logi POP Keys Device D1:8F:A4:4B:1B:F9 Logi POP Mouse When not working, the devices show up as: Device D2:91:D2:B9:6B:9D Logi POP @ Device D1:8F:A4:4B:1B:F9 Logi POP @ This devices are: - https://www.logitech.com/en-au/products/mice/pop-wireless-mouse.910-006515.html - https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-010578.html I know that the devices both work with a Windows 10 desktop. Bluetooth Device Details When working.. root@silver:/home/paul# hciconfig -a hci0: Type: Primary Bus: USB BD Address: 20:68:9D:64:8A:FC ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:1801269 acl:99624 sco:0 events:560 errors:0 TX bytes:8612 acl:173 sco:0 commands:227 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'silver' Class: 0x7c010c Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Laptop HCI Version: 4.0 (0x6) Revision: 0x1000 LMP Version: 4.0 (0x6) Subversion: 0x220e Manufacturer: Broadcom Corporation (15) ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1969874 Title: Bluetooth Mouse and Keyboard drop connections when Laptop using battery Status in bluez package in Ubuntu: New Bug description: Bluetooth Mouse and Keyboard drop connections when Laptop using battery (power discconnected). Keyboard and mouse work correctly when laptop is powered by mains power. May be related to suspend/resume. Symptoms: - Mouse and keyboard don't work. - Mouse and keyboard bluetooth association cannot be removed rand e-connected. - Mouse and keyboard are detected (sometimes) with different device names. The following does NOT fix the problem:: - Connect laptop power; - In Bluetooth settings Turn Bluetooth off, then on again Rebooting allows devices to be configured again, and connect correctly. Ubuntu version: Ubuntu 21.10 Kernel: 5.13.0-39-generic Package: bluez 5.60-0ubuntu2.2 When working the keyboard and mouse appear with: root@silver:/home/paul# bluetoothctl devices Device D2:91:D2:B9:6B:9D Logi POP Keys Device D1:8F:A4:4B:1B:F9 Logi POP Mouse When not working, the devices show up as: Device D2:91:D2:B9:6B:9D Logi POP @ Device D1:8F:A4:4B:1B:F9 Logi POP @ This devices are: - https://www.logitech.com/en-au/products/mice/pop-wireless-mouse.910-006515.html - https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-010578.html I know that the devices both work with a Windows 10 desktop. Bluetooth Device Details When working.. root@silver:/home/paul# hciconfig -a hci0: Type: Primary Bus: USB BD Address: 20:68:9D:64:8A:FC ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:1801269 acl:99624 sco:0 events:560 errors:0 TX bytes:8612 acl:173 sco:0 commands:227 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'silver' Class: 0x7c010c Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Laptop HCI Version: 4.0 (0x6) Revision: 0x1000 LMP Version: 4.0 (0x6) Subversion: 0x220e Manufacturer: Broadcom Corporation (15) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1969874/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packag
[Kernel-packages] [Bug 1969834] Re: artifacts (many short horizontal lines) on laptop with hybrid graphix
The attached Xorg logs are from March 8th so not recent enough... While the problem is happening please run this command to collect a newer log: journalctl -b0 > journal.txt and attach the resulting text file here. ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Incomplete ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1969834 Title: artifacts (many short horizontal lines) on laptop with hybrid graphix Status in nvidia-graphics-drivers-510 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: artifacts (many short horizontal lines) see https://youtu.be/SQOOp0bd0LE artifacts only on display (screen capture is clear) i have laptop with hybrid graphix (intel nvidia) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.16.13-051613-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Apr 21 22:06:20 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9a68] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb] InstallationDate: Installed on 2022-02-28 (52 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Micro-Star International Co., Ltd. Katana GF76 11UC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.16.13-051613-generic root=UUID=98fc789e-6997-4a4b-b741-da24a1b635ca ro quiet splash modprode.blacklist=nouveau snd_intel_dspcfg.dsp_driver=1 snd_hda_intel.dmic_detect=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2022 dmi.bios.release: 3.16 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E17L2IMS.310 dmi.board.asset.tag: Default string dmi.board.name: MS-17L2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17L2IMS.310:bd01/13/2022:br3.16:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF7611UC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17L2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17L2.3: dmi.product.family: GF dmi.product.name: Katana GF76 11UC dmi.product.sku: 17L2.3 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1969834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-pack
[Kernel-packages] [Bug 1969834] Re: artifacts (many short horizontal lines) on laptop with hybrid graphix
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-510 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1969834 Title: artifacts (many short horizontal lines) on laptop with hybrid graphix Status in nvidia-graphics-drivers-510 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: artifacts (many short horizontal lines) see https://youtu.be/SQOOp0bd0LE artifacts only on display (screen capture is clear) i have laptop with hybrid graphix (intel nvidia) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.16.13-051613-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Apr 21 22:06:20 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9a68] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb] InstallationDate: Installed on 2022-02-28 (52 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Micro-Star International Co., Ltd. Katana GF76 11UC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.16.13-051613-generic root=UUID=98fc789e-6997-4a4b-b741-da24a1b635ca ro quiet splash modprode.blacklist=nouveau snd_intel_dspcfg.dsp_driver=1 snd_hda_intel.dmic_detect=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2022 dmi.bios.release: 3.16 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E17L2IMS.310 dmi.board.asset.tag: Default string dmi.board.name: MS-17L2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17L2IMS.310:bd01/13/2022:br3.16:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF7611UC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17L2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17L2.3: dmi.product.family: GF dmi.product.name: Katana GF76 11UC dmi.product.sku: 17L2.3 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1969834/+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 1969834] [NEW] artifacts (many short horizontal lines) on laptop with hybrid graphix
You have been subscribed to a public bug: artifacts (many short horizontal lines) see https://youtu.be/SQOOp0bd0LE artifacts only on display (screen capture is clear) i have laptop with hybrid graphix (intel nvidia) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.16.13-051613-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Apr 21 22:06:20 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9a68] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb] InstallationDate: Installed on 2022-02-28 (52 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Micro-Star International Co., Ltd. Katana GF76 11UC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.16.13-051613-generic root=UUID=98fc789e-6997-4a4b-b741-da24a1b635ca ro quiet splash modprode.blacklist=nouveau snd_intel_dspcfg.dsp_driver=1 snd_hda_intel.dmic_detect=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2022 dmi.bios.release: 3.16 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E17L2IMS.310 dmi.board.asset.tag: Default string dmi.board.name: MS-17L2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17L2IMS.310:bd01/13/2022:br3.16:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF7611UC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17L2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17L2.3: dmi.product.family: GF dmi.product.name: Katana GF76 11UC dmi.product.sku: 17L2.3 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal kubuntu resolution ubuntu -- artifacts (many short horizontal lines) on laptop with hybrid graphix https://bugs.launchpad.net/bugs/1969834 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. -- 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 1930925] Re: Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but 18.04 does)
** Tags added: 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/1930925 Title: Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but 18.04 does) Status in linux package in Ubuntu: Confirmed Bug description: I have recently acquired a acquired a desktop running ubuntu 20.04. I have several computers and switch between them using this KVM https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 The other machines are either running windows or ubuntu 18.04 or earlier. They are all fine, but the with 20.04 machine neither the keyboard nor the mouse works. On the 18.04 machine I can see lsusb Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub and it is the Logitech, Inc. Unifying Receiver which appears when the USB from the KVM is connected. On the 20.04 machine only this appears lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I have tested installation discs from 19.04 onwards. The failure first appears in 19.10 and is still present in 21.04 I can observe a similar problem with a dual boot laptop running windows 10 and 20.04. With windows 10 I can use it with the KVM for screen and keyboard/mouse, but with ubuntu 20.04 the keyboard and mouse do not work. This issue has also been observed here https://unix.stackexchange.com/questions/646515/using-logitech-mouse- keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed it using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model). I had to report this originally against xorg as this bug reporting system seems not to allow reporting of bugs against unknown packages. I also had to report it through the ubuntu-bug executable as I've been unable to find a way in launchpad of reporting a bug (as opposed to getting a guided tour about reporting bugs). I am happy to supply more info and test fixes if I am asked but as with this type of bug where something fails to happen rather than something wrong happens I don't know what to look at. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Jun 4 20:21:15 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-05-14 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 11: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 13: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 13: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=0c391c11-c570-4e04-a351-4fd128a75369 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2021 dmi.bios.release: 8.20 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0820 dmi.board.asset.tag: Default string dmi.board.name: PRIME H570M-PLUS 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.:bvr0820:bd04/27/2021:br8.20:svnA
[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze
Now at Jammy with kernel 5.15.0-25-generic, I have still observed freezes. Quite infrequent, so not "quick" to reproduce (whereas at Impish were frequent, within minutes of uptime). -- 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/1927808 Title: rtw88_8821ce causes freeze Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Confirmed 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: Confirmed Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DKMS module/driver from https://github.com/tomaspinho/rtl8821ce (having blacklisted rtw88_8821ce), and it seems to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psz1189 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 8 16:58:19 2021 InstallationDate: Installed on 2021-04-23 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protempo Ltd L116HTN6SPW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: L116HTN6SPW dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Protempo Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1927808/+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 1707695] Re: radeon 0000:03:00.0: ring 0 stalled for more than 10000msec
This is still an on going problem. It was working fine on Mint 18.3, then I upgraded(downgraded?) to Mint 20.3 I have been having lockups, freezes, ssh in for a while before it locks up, etc.. Very similar to above mentions of problems. Here is the basic error that happens: [37664.592883] radeon :01:00.0: ring 0 stalled for more than 14948msec [37664.592889] radeon :01:00.0: GPU lockup (current fence id 0x003b1a11 last fence id 0x003b1a26 on ring 0) Here is the system info: System: Kernel: 5.4.0-109-generic x86_64 bits: 64 compiler: gcc v: 9.4.0 Desktop: Cinnamon 5.2.7 wm: muffin dm: LightDM 1.30.0 Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal -- 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/1707695 Title: radeon :03:00.0: ring 0 stalled for more than 1msec Status in Linux: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: My system intermittently locks up every few days. It does not seem to correspond to a particular program or action. When that happens, the screen goes to black, then returns after a few seconds. At that point, the time on the clock is static and indicates that the screen is frozen, but audio continues to play for 30 seconds to a minute. The keyboard and mouse do not affect what's being displayed, but I can Alt - SysRq - REISUB to restart. Every time (7 crashes and counting), /var/log/kern.log indicates that kernel: [353692.378886] radeon :03:00.0: ring 0 stalled for more than 10280msec kernel: [353692.378896] radeon :03:00.0: GPU lockup (current fence id 0x006e96e5 last fence id 0x006e96e9 on ring 0) just before the system locks. Different ring numbers are reported as stalling at different times. As per the instructions, I posted a question about this issue at: https://askubuntu.com/questions/937792/system-lockup-radeon-ring- stalled-for-more-than-10280msec?noredirect=1#comment1486875_937792 but I have not received many responses. I'm running 16.04 LTS. :~$ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 According to the Software Center, I am running Ubuntu Software 3.20.1. I have a Radeon HD graphics card. :~$ lspci | grep VGA 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] :~$ lspci -v -s 03:00.0 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Cedar [Radeon HD 5000/6000/7350/8350 Series] Flags: bus master, fast devsel, latency 0, IRQ 53 Memory at c000 (64-bit, prefetchable) [size=256M] Memory at d3d2 (64-bit, non-prefetchable) [size=128K] I/O ports at 7000 [size=256] Expansion ROM at d3d0 [disabled] [size=128K] Capabilities: Kernel driver in use: radeon Kernel modules: radeon Please let me know if additional information would be useful, and I will be glad to provide it. Thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-87-generic 4.4.0-87.110 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Uname: Linux 4.4.0-87-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: clapp 3889 F pulseaudio /dev/snd/controlC2: clapp 3889 F pulseaudio /dev/snd/controlC1: clapp 3889 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 31 14:02:27 2017 HibernationDevice: RESUME=UUID=1b30dad6-8c48-42cf-ae26-66ab8b0eb446 InstallationDate: Installed on 2013-09-04 (1425 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Dell Inc. Precision T7600 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic root=UUID=33722f76-37fd-4289-b071-d7f48b65dd32 ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-87-generic N/A linux-backports-modules-4.4.0-87-generic N/A linux-firmware1.157.11 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 082WXT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/03/2013:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T7600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notificati
[Kernel-packages] [Bug 1924298] Re: accept returns duplicate endpoints under load
We have been hitting this bug quite often while running Tomcat 8.5 on
Amazon AWS Linux 2 with a kernel of 4.14.268-205.500.amzn2.x86_64
I wanted to see if the bug could be reproduced using an updated kernel
so I attempted to repro it using the server code and methodology
provided by Mark Thomas on Ubuntu Server 21.10 (running on a Raspberry
Pi 4 with 4GB RAM) and was NOT able to repro the bug (kernel
5.13.0-1008-raspi). I then installed Ubuntu Server 20.04 LTS on the same
machine and WAS able to repro the bug (kernel 5.4.0-1052-raspi). The
bug was fairly easy to repro and did not take multiple times to repro.
Since then I have been able to repro the bug using the server code on
AWS Linux 2 with the 4.14.268-205.500.amzn2.x86_64 kernel, but not on
AWS Linux 2 with a 5.10.109-104.500.amzn2.x86_64 kernel.
I think there is a slight problem with the server code used in the
repro, as it is calling `pthread_create` with no thread attributes,
which will create joinable threads instead of detached threads. The
documentation for `pthread_create` says that "Only when a terminated
joinable thread has been joined are the last of its resources released
back to the system." Because the server code never joins the threads I
think this is preventing the OS from releasing the thread resources.
This results in the server eventually running out of memory and the
server program returning a "pthread_create: Cannot allocate memory" as
mentioned by Brooke Hedrick in their comment. I was also not able to
repro the bug on WSL (kernel 4.4.0-19041-Microsoft), but perhaps their
underlying network drivers are different?
I also was running into this issue when running the server code. I made
a slight modification to the server code to set the pthread attribute to
create the new threads in a detached state. This seemed to solve the
memory issue and I was able to repro the bug with this server. I've
attached the code.
Additionally, I found it useful to use `prlimit` to update the maximum
number of open files for the server process, once it was running. This
made the server less likely to run into an EMFILE error when calling
`accept`.
** Attachment added: "Updated server to demonstrate bug"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924298/+attachment/5582247/+files/server.c
--
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/1924298
Title:
accept returns duplicate endpoints under load
Status in Linux:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
When accepting client connections under load, duplicate endpoints may
be returned. These endpoints will have different (usually sequential)
file descriptors but will refer to the same connection (same server
IP, same server port, same client IP, same client port). Both copies
of the endpoint appear to be functional.
Reproduction requires:
- compilation of the attached server.c program
- wrk (https://github.com/wg/wrk) to generate load
The steps to reproduce are:
- run 'server' application in one console window
- run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency
--timeout 1s http://localhost:/post; done' in a second console window
- run the same command in a third window to generate concurrent load
You may need to run additional instance of the wrk command in multiple
windows to trigger the issue.
When the problem occurs the server executable will exit and print some
debugging info. e.g.:
accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient
= 232
This indicates that the sockets with file descriptors 233 and 232 are
duplicates.
The issue has been reproduced on fully patched versions of Ubuntu
20.04 and 18.04. Other versions have not been tested.
This issue was originally observed in Java and was reported against the
Spring Framework:
https://github.com/spring-projects/spring-framework/issues/26434
Investigation from the Spring team and the Apache Tomcat team identified that
it appeared to be a JDK issue:
https://bugs.openjdk.java.net/browse/JDK-8263243
Further research from the JDK team determined that the issue was at
the OS level. Hence this report.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-71-generic 5.4.0-71.79
ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
Uname: Linux 5.4.0-71-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 15 12:52:53 2021
HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d
InstallationDate: Installed on 2017-02-02 (1532 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig:
lono wireless extensions.
docker0 no wireless ex
[Kernel-packages] [Bug 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
** Changed in: zfs Status: New => Fix Released -- 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/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy Status in Native ZFS for Linux: Fix Released Status in mysql-8.0 package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Triaged Bug description: [Summary] When running Jammy on zfs or LXD with a zfs pool on a Jammy host, fallocate creates a zero-sized file. The issue was originally found when installing mysql on LXD, where fallocate would create a zero-sized ib_logfile1 file. The original information in this bug is based on that. [Steps to Reproduce] touch foo.img fallocate -z -l 10M foo.img ls -la foo.img On a non-zfs Jammy system this will show something like: -rw-r--r-- 1 root root 10M ... while on zfs it will show: -rw-rw-r-- 1 root root 0 ... [Original Description] I came across this error when testing various mysql setups in an LXD container and managed to reproduce it consistently. I'm unable to reproduce on Ubuntu desktop or server though since the prerequisites are probably handled properly there. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 15 21:31:09 2022 Dmesg: ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 KernLog: Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic links: '/etc/mysql/my.cnf' MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 'public_key.pem', 'ca.pem', 'server-key.pem'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash mem_sleep_default=deep vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1969247/+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 1969857] [NEW] Jammy update: v5.15.35 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.35 upstream stable release
from git://git.kernel.org/
drm/amd/display: Add pstate verification and recovery for DCN31
drm/amd/display: Fix p-state allow debug index on dcn31
hamradio: defer 6pack kfree after unregister_netdev
hamradio: remove needs_free_netdev to avoid UAF
cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function
ACPI: processor idle: Check for architectural support for LPI
ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
btrfs: remove unused parameter nr_pages in add_ra_bio_pages()
btrfs: remove no longer used counter when reading data page
btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()
soc: qcom: aoss: Expose send for generic usecase
dt-bindings: net: qcom,ipa: add optional qcom,qmp property
net: ipa: request IPA register values be retained
btrfs: release correct delalloc amount in direct IO write path
ALSA: core: Add snd_card_free_on_error() helper
ALSA: sis7019: Fix the missing error handling
ALSA: ali5451: Fix the missing snd_card_free() call at probe error
ALSA: als300: Fix the missing snd_card_free() call at probe error
ALSA: als4000: Fix the missing snd_card_free() call at probe error
ALSA: atiixp: Fix the missing snd_card_free() call at probe error
ALSA: au88x0: Fix the missing snd_card_free() call at probe error
ALSA: aw2: Fix the missing snd_card_free() call at probe error
ALSA: azt3328: Fix the missing snd_card_free() call at probe error
ALSA: bt87x: Fix the missing snd_card_free() call at probe error
ALSA: ca0106: Fix the missing snd_card_free() call at probe error
ALSA: cmipci: Fix the missing snd_card_free() call at probe error
ALSA: cs4281: Fix the missing snd_card_free() call at probe error
ALSA: cs5535audio: Fix the missing snd_card_free() call at probe error
ALSA: echoaudio: Fix the missing snd_card_free() call at probe error
ALSA: emu10k1x: Fix the missing snd_card_free() call at probe error
ALSA: ens137x: Fix the missing snd_card_free() call at probe error
ALSA: es1938: Fix the missing snd_card_free() call at probe error
ALSA: es1968: Fix the missing snd_card_free() call at probe error
ALSA: fm801: Fix the missing snd_card_free() call at probe error
ALSA: galaxy: Fix the missing snd_card_free() call at probe error
ALSA: hdsp: Fix the missing snd_card_free() call at probe error
ALSA: hdspm: Fix the missing snd_card_free() call at probe error
ALSA: ice1724: Fix the missing snd_card_free() call at probe error
ALSA: intel8x0: Fix the missing snd_card_free() call at probe error
ALSA: intel_hdmi: Fix the missing snd_card_free() call at probe error
ALSA: korg1212: Fix the missing snd_card_free() call at probe error
ALSA: lola: Fix the missing snd_card_free() call at probe error
ALSA: lx6464es: Fix the missing snd_card_free() call at probe error
ALSA: maestro3: Fix the missing snd_card_free() call at probe error
ALSA: oxygen: Fix the missing snd_card_free() call at probe error
ALSA: riptide: Fix the missing snd_card_free() call at probe error
ALSA: rme32: Fix the missing snd_card_free() call at probe error
ALSA: rme9652: Fix the missing snd_card_free() call at probe error
ALSA: rme96: Fix the missing snd_card_free() call at probe error
ALSA: sc6000: Fix the missing snd_card_free() call at probe error
ALSA: sonicvibes: Fix the missing snd_card_free() call at probe error
ALSA: via82xx: Fix the missing snd_card_free() call at probe error
ALSA: usb-audio: Cap upper limits of buffer/period bytes for implicit fb
ALSA: nm256: Don't call card private_free at probe error path
drm/msm: Add missing put_task_struct() in debugfs path
firmware: arm_scmi: Remove clear channel call on the TX channel
memory: atmel-ebi: Fix missing of_node_put in atmel_ebi_probe
Revert "ath11k: mesh: add support for 256 bitmap in blockack frames in 11ax"
firmware: arm_scmi: Fix sorting of retrieved clock rates
media: rockchip/rga: do proper error checking in probe
SUNRPC: Fix the svc_deferred_event trace class
net/sched: flower: fix parsing of ethertype following VLAN header
veth: Ensure eth header is in skb's linear part
gpiolib: acpi: use correct format characters
cifs: release cached dentries only if mount is complete
net: mdio: don't defer probe forever if PHY IRQ provider is missing
mlxsw: i2c: Fix initialization error flow
net/sched: fix initialization order when updating chain 0 head
net: dsa: felix: suppress -EPROBE_DEFER errors
net: ethernet: stmmac: fix altr_tse_pcs function when using a fixed-link
net/sched: taprio: Check if socket flags are valid
cfg80211: ho
[Kernel-packages] [Bug 1948626] Re: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010
Hi Sujith, I forgot to apply the latest tag. I have rebuilt the kernel with 5.15 and updated the link. https://people.canonical.com/~mreed/lp_1948626_nvme_tcp/ -- 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/1948626 Title: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [Impact] NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one. TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers. TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis. Here is code that implements TP8009 and TP8010: https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas [Fix] 1. Update kernel with TP8010 kernel patches: a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907 b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0 c. nvme: add CNTRLTYPE definitions for 'identify controller https://lore.kernel.org/all/66fc4f03-ed5c-4727-ba94-c23daf7d6...@oracle.com/ [Test Case] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626/+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 1969841] Re: grub-efi-amd64: grub-efi/install_devices depends on the value of LC_COLLATE/LANG
** Package changed: linux-meta (Ubuntu) => grub2 (Ubuntu) -- 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/1969841 Title: grub-efi-amd64: grub-efi/install_devices depends on the value of LC_COLLATE/LANG Status in grub2 package in Ubuntu: New Bug description: Hi, As discussed with Julian Andres Klode on IRC, there are cases where the value of grub-efi/install_devices is affected by the value of LC_COLLATE. This is caused by this unique sort: https://git.launchpad.net/~ubuntu- core-dev/grub/+git/ubuntu/tree/debian/grub-multi- install?h=debian/2.06-2ubuntu7#n220 # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 From what I see, this can only happen on systems with NVMe drives: # find -L /dev/disk/by-id/ -samefile /dev/nvme0n1p1 /dev/disk/by-id/nvme-eui.e8238fa6bf530001001b444-part1 /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1 Let's assume grub-efi/install_devices has the following value: # debconf-show grub-efi-amd64 | grep grub-efi/install_devices: * grub-efi/install_devices: /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1, /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1 This was obtained with this LANG/LC_COLLATE: # echo $LANG C.UTF-8 # dpkg-reconfigure grub-efi-amd64 │ GRUB EFI system partitions: │ │ │ │[*] /dev/nvme1n1p1 (535 MB; /boot/efi) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000 │ │[*] /dev/nvme0n1p1 (535 MB; ) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000 │ # debconf-show grub-efi-amd64 | grep grub-efi/install_devices: * grub-efi/install_devices: /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1, /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1 We can see that the boxes are properly ticked here. However: # export LANG=en_US.UTF-8; dpkg-reconfigure grub-efi-amd64 │ GRUB EFI system partitions: │ │ │ │[ ] /dev/nvme1n1p1 (535 MB; /boot/efi) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000 │ │[ ] /dev/nvme0n1p1 (535 MB; ) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000│ The boxes are not ticked, if I tick them, I get the following: # debconf-show grub-efi-amd64 | grep grub-efi/install_devices: * grub-efi/install_devices: /dev/disk/by-id/nvme-eui.e8238fa6bf530001001b444-part1, /dev/disk/by-id/nvme-eui.e8238fa6bf530001001b4466-part1 I assume the postinst script for grub-pc exhibits the same bug with the value of grub-pc/install_devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1969841/+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 1969841] [NEW] grub-efi-amd64: grub-efi/install_devices depends on the value of LC_COLLATE/LANG
Public bug reported: Hi, As discussed with Julian Andres Klode on IRC, there are cases where the value of grub-efi/install_devices is affected by the value of LC_COLLATE. This is caused by this unique sort: https://git.launchpad.net/~ubuntu- core-dev/grub/+git/ubuntu/tree/debian/grub-multi- install?h=debian/2.06-2ubuntu7#n220 # lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 From what I see, this can only happen on systems with NVMe drives: # find -L /dev/disk/by-id/ -samefile /dev/nvme0n1p1 /dev/disk/by-id/nvme-eui.e8238fa6bf530001001b444-part1 /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1 Let's assume grub-efi/install_devices has the following value: # debconf-show grub-efi-amd64 | grep grub-efi/install_devices: * grub-efi/install_devices: /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1, /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1 This was obtained with this LANG/LC_COLLATE: # echo $LANG C.UTF-8 # dpkg-reconfigure grub-efi-amd64 │ GRUB EFI system partitions: │ │ │ │[*] /dev/nvme1n1p1 (535 MB; /boot/efi) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000 │ │[*] /dev/nvme0n1p1 (535 MB; ) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000 │ # debconf-show grub-efi-amd64 | grep grub-efi/install_devices: * grub-efi/install_devices: /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1, /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1 We can see that the boxes are properly ticked here. However: # export LANG=en_US.UTF-8; dpkg-reconfigure grub-efi-amd64 │ GRUB EFI system partitions: │ │ │ │[ ] /dev/nvme1n1p1 (535 MB; /boot/efi) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000 │ │[ ] /dev/nvme0n1p1 (535 MB; ) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000 │ The boxes are not ticked, if I tick them, I get the following: # debconf-show grub-efi-amd64 | grep grub-efi/install_devices: * grub-efi/install_devices: /dev/disk/by-id/nvme-eui.e8238fa6bf530001001b444-part1, /dev/disk/by-id/nvme-eui.e8238fa6bf530001001b4466-part1 I assume the postinst script for grub-pc exhibits the same bug with the value of grub-pc/install_devices. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New -- 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/1969841 Title: grub-efi-amd64: grub-efi/install_devices depends on the value of LC_COLLATE/LANG Status in grub2 package in Ubuntu: New Bug description: Hi, As discussed with Julian Andres Klode on IRC, there are cases where the value of grub-efi/install_devices is affected by the value of LC_COLLATE. This is caused by this unique sort: https://git.launchpad.net/~ubuntu- core-dev/grub/+git/ubuntu/tree/debian/grub-multi- install?h=debian/2.06-2ubuntu7#n220 # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 From what I see, this can only happen on systems with NVMe drives: # find -L /dev/disk/by-id/ -samefile /dev/nvme0n1p1 /dev/disk/by-id/nvme-eui.e8238fa6bf530001001b444-part1 /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1 Let's assume grub-efi/install_devices has the following value: # debconf-show grub-efi-amd64 | grep grub-efi/install_devices: * grub-efi/install_devices: /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1, /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1 This was obtained with this LANG/LC_COLLATE: # echo $LANG C.UTF-8 # dpkg-reconfigure grub-efi-amd64 │ GRUB EFI system partitions: │ │ │ │[*] /dev/nvme1n1p1 (535 MB; /boot/efi) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000 │ │[*] /dev/nvme0n1p1 (535 MB; ) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000 │ # debconf-show grub-efi-amd64 | grep grub-efi/install_devices: * grub-efi/install_devices: /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1, /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1 We can see that the boxes are properly ticked here. However: # export LANG=en_US.UTF-8; dpkg-reconfigure grub-efi-amd64 │ GRUB EFI system partitions: │ │ │ │[ ] /dev/nvme1n1p1 (535 MB; /boot/efi) on 512110 MB WDC CL SN720 SDAQNTW-512G-2000 │ │[ ] /dev/nvme0n1p1 (5
[Kernel-packages] [Bug 1969837] 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 1969837 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/1969837 Title: Enable secure boot support Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The linux-realtime kernel should be signed for secure boot. For that add linux-signed-realtime and linux-restricted-modules-realtime packages. [Test Plan] The kernel should be able to boot with secure boot enabled. [Where problems could occur] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969837/+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 1969837] [NEW] Enable secure boot support
Public bug reported: [Impact] The linux-realtime kernel should be signed for secure boot. For that add linux-signed-realtime and linux-restricted-modules-realtime packages. [Test Plan] The kernel should be able to boot with secure boot enabled. [Where problems could occur] N/A ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1969837 Title: Enable secure boot support Status in linux package in Ubuntu: New Bug description: [Impact] The linux-realtime kernel should be signed for secure boot. For that add linux-signed-realtime and linux-restricted-modules-realtime packages. [Test Plan] The kernel should be able to boot with secure boot enabled. [Where problems could occur] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969837/+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 1962481] Re: kubuntu 20.04 LTS didn't startx with dual gfxcard on board
after fresh update: uname -a Linux katana-lin 5.16.13-051613-generic #202203100808-Ubuntu SMP PREEMPT Thu Mar 10 08:16:58 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux i have same changes: after power-on screen didn't freeze with special MSI logo. and I doesn't must switch to tty's, tty1 is active and alive. then i can run "sudo sddm" manually because it didn't start automatically. -- 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/1962481 Title: kubuntu 20.04 LTS didn't startx with dual gfxcard on board Status in linux package in Ubuntu: Confirmed Bug description: didn't startx with dual gfxcard on board after clear installation (i'll try with and without update) Kernel: 5.4.0-102-generic x86_64 bits: 64 Console: N/A Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Micro-Star product: Katana GF76 11UC v: REV:1.0 Mobo: Micro-Star model: MS-17L2 v: REV:1.0 serial: BSS-0123456789 UEFI: American BIOS v: E17L2IMS.310 date: 01/13/2022 CPU: Topology: 6-Core model: 11th Gen Intel Core i5-11400H bits: 64 type: MT MCP L2 cache: ... Graphics: Device-1: Intel driver: N/A my comment : manually i deactivated it "i915" but no happend Device-2: NVIDIA driver: nvidia v: 510.54 my comment :NVIDIA GPU NVIDIA GeForce RTX 3050 Laptop GPU (GA107-A) Display: server: X.org 1.20.8 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa tty: 240x67 Message: Advanced graphics data unavailable in console for root. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-28 (0 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Micro-Star International Co., Ltd. Katana GF76 11UC Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=98fc789e-6997-4a4b-b741-da24a1b635ca ro quiet splash modprode.blacklist=nouveau vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2022 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E17L2IMS.310 dmi.board.asset.tag: Default string dmi.board.name: MS-17L2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17L2IMS.310:bd01/13/2022:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF7611UC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17L2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GF dmi.product.name: Katana GF76 11UC dmi.product.sku: 17L2.3 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962481/+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 1954833] Re: net: ethernet: microchip: lan743x: Increase rx ring size to improve rx performance
Due to lack of hardware, we are unable to verify a backport of this fix, so I'll go ahead and mark this bug "Won't Fix". If you are impacted by this and are able to perform the necessary performance testing to verify a backport, please reopen and we can move forward. ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu Impish) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu Focal) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu Jammy) Assignee: dann frazier (dannf) => (unassigned) ** Changed in: linux (Ubuntu Impish) Assignee: dann frazier (dannf) => (unassigned) ** Changed in: linux (Ubuntu Hirsute) Assignee: dann frazier (dannf) => (unassigned) ** Changed in: linux (Ubuntu Focal) Assignee: dann frazier (dannf) => (unassigned) -- 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/1954833 Title: net: ethernet: microchip: lan743x: Increase rx ring size to improve rx performance Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Won't Fix Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Won't Fix Status in linux source package in Jammy: Won't Fix Bug description: [Impact] rx performance is sub-optimal with EVB-LAN7430 NICs. [Test Case] Use iperf3 to submit TCP or UDP traffic to a host w/ a EVB-LAN7430 NIC. [Fix] Cherry-pick the following upstream commit: a1f1627540cde net: ethernet: microchip: lan743x: Increase rx ring size to improve rx performance [What could go wrong] The patch will slightly increase memory usage, which could possibly add memory pressure to memory-restricted systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954833/+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 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
zfs-dkms ended up working for me using LXD with the following test case: sudo add-apt-repository ppa:ci-train-ppa-service/4831 sudo apt update sudo apt upgrade sudo apt install zfs-dkms lxd init lxc launch images:ubuntu/focal test-mysql lxc exec test-mysql bash # apt update && apt dist-upgrade -y # apt install mysql-server # touch foo.img # fallocate -z -l 10M foo.img # ll foo.img -rw-r--r-- 1 root root 10485760 ... -- 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/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy Status in Native ZFS for Linux: New Status in mysql-8.0 package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Triaged Bug description: [Summary] When running Jammy on zfs or LXD with a zfs pool on a Jammy host, fallocate creates a zero-sized file. The issue was originally found when installing mysql on LXD, where fallocate would create a zero-sized ib_logfile1 file. The original information in this bug is based on that. [Steps to Reproduce] touch foo.img fallocate -z -l 10M foo.img ls -la foo.img On a non-zfs Jammy system this will show something like: -rw-r--r-- 1 root root 10M ... while on zfs it will show: -rw-rw-r-- 1 root root 0 ... [Original Description] I came across this error when testing various mysql setups in an LXD container and managed to reproduce it consistently. I'm unable to reproduce on Ubuntu desktop or server though since the prerequisites are probably handled properly there. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 15 21:31:09 2022 Dmesg: ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 KernLog: Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic links: '/etc/mysql/my.cnf' MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 'public_key.pem', 'ca.pem', 'server-key.pem'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash mem_sleep_default=deep vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1969247/+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 1969807] Re: CONFIG_SND_COMPRESS_OFFLOAD missing in jammy/ppc64el kernel config
Committed to jammy/master-next: c820c49febd6 UBUNTU: [Config] updateconfigs for SND_COMPRESS_OFFLOAD (ppc64el) ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/1969807 Title: CONFIG_SND_COMPRESS_OFFLOAD missing in jammy/ppc64el kernel config Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: CONFIG_SND_COMPRESS_OFFLOAD needs to be configured (as =m ordinarily) for configs that can support it. For the jammy kernel and toolchain, this now includes ppc64el. Add to Jammy: debian.master/config/ppc64el/config.common.ppc64el:CONFIG_SND_COMPRESS_OFFLOAD=m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969807/+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
Re: [Kernel-packages] [Bug 1930925] Re: Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but 18.04 does)
I just tried Ubuntu 22.04. Whilst the installer works correctly with the KVM (so I can for example choose option 1, try or install), the installation doesn't work (at least, not with the mouse, and without that I can't get anything that would be sensitive to the keyboard). By this time next year, there will be no Ubuntu (or Debian I think, given that Rapsbian doesn't work with the KVM either) distribution I can use, as at that point 18.04 will be end of support. I shall then start having to try and learn other distros to see if any of them have fixed/failed to create this bug. Jon Thackray j...@pobox.com 0044 1223 276500 (home) 0044 7803 017991 (mobile) 0033 423354068 (France) -- Original Message -- From: "Launchpad Bug Tracker" <1930...@bugs.launchpad.net> To: j...@pobox.com Sent: 03/08/2021 04:57:57 Subject: [Bug 1930925] Re: Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but 18.04 does) >Status changed to 'Confirmed' because the bug affects multiple users. > >** Changed in: linux (Ubuntu) >Status: New => Confirmed > >-- >You received this bug notification because you are subscribed to the bug >report. >https://bugs.launchpad.net/bugs/1930925 > >Title: > Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but > 18.04 does) > >Status in linux package in Ubuntu: > Confirmed > >Bug description: > I have recently acquired a acquired a desktop running ubuntu 20.04. I > have several computers and switch between them using this KVM >https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 > The other machines are either running windows or ubuntu 18.04 or > earlier. They are all fine, but the with 20.04 machine neither the > keyboard nor the mouse works. On the 18.04 machine I can see > > lsusb > Bus 002 Device 002: ID 8087:8000 Intel Corp. > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 002: ID 8087:8008 Intel Corp. > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > and it is the Logitech, Inc. Unifying Receiver which appears when the > USB from the KVM is connected. On the 20.04 machine only this appears > > lsusb > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller > Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > I have tested installation discs from 19.04 onwards. The failure first > appears in 19.10 and is still present in 21.04 > > I can observe a similar problem with a dual boot laptop running > windows 10 and 20.04. With windows 10 I can use it with the KVM for > screen and keyboard/mouse, but with ubuntu 20.04 the keyboard and > mouse do not work. This issue has also been observed here >https://unix.stackexchange.com/questions/646515/using-logitech-mouse- > keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed > it using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model). > > I had to report this originally against xorg as this bug reporting > system seems not to allow reporting of bugs against unknown packages. > I also had to report it through the ubuntu-bug executable as I've been > unable to find a way in launchpad of reporting a bug (as opposed to > getting a guided tour about reporting bugs). > > I am happy to supply more info and test fixes if I am asked but as > with this type of bug where something fails to happen rather than > something wrong happens I don't know what to look at. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-53-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > Date: Fri Jun 4 20:21:15 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > DpkgLog: > > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) > Subsystem: ASUSTeK Computer Inc. Device [1043:8694] > InstallationDate: Installed on 2021-05-14 (21 days ago) > InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 > (20210209.1) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller >Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub >Bus 001 Device 001: ID 1d6b:0
[Kernel-packages] [Bug 1969807] [NEW] CONFIG_SND_COMPRESS_OFFLOAD missing in jammy/ppc64el kernel config
Public bug reported: CONFIG_SND_COMPRESS_OFFLOAD needs to be configured (as =m ordinarily) for configs that can support it. For the jammy kernel and toolchain, this now includes ppc64el. Add to Jammy: debian.master/config/ppc64el/config.common.ppc64el:CONFIG_SND_COMPRESS_OFFLOAD=m ** Affects: linux (Ubuntu) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Also affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress -- 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/1969807 Title: CONFIG_SND_COMPRESS_OFFLOAD missing in jammy/ppc64el kernel config Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: CONFIG_SND_COMPRESS_OFFLOAD needs to be configured (as =m ordinarily) for configs that can support it. For the jammy kernel and toolchain, this now includes ppc64el. Add to Jammy: debian.master/config/ppc64el/config.common.ppc64el:CONFIG_SND_COMPRESS_OFFLOAD=m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969807/+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 1966519] Re: hard shutdown after close laptop lid
Fixed by upgrade to Ubuntu 22.04 LTS. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- 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/1966519 Title: hard shutdown after close laptop lid Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: shutdown on close screen lid and when i reopen the lid it is completely shutdown and i must press the power button and start boot sequence, i have set in gnome-tweaks action,the after close the lid memory suspend, but evidently it is not working. Sorry for my english. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 20:59:38 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.32, 5.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d3) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Cezanne [103c:8895] InstallationDate: Installed on 2022-03-23 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210502) MachineType: HP HP EliteBook 845 G8 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-37-generic root=UUID=e3adb113-cca4-4316-9c3b-edc124da9ca4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2022 dmi.bios.release: 8.3 dmi.bios.vendor: HP dmi.bios.version: T82 Ver. 01.08.03 dmi.board.name: 8895 dmi.board.vendor: HP dmi.board.version: KBC Version 43.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 67.42 dmi.modalias: dmi:bvnHP:bvrT82Ver.01.08.03:bd02/11/2022:br8.3:efr67.42:svnHP:pnHPEliteBook845G8NotebookPC:pvr:rvnHP:rn8895:rvrKBCVersion43.2A.00:cvnHP:ct10:cvr:sku48R69EA#BCM: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 845 G8 Notebook PC dmi.product.sku: 48R69EA#BCM dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966519/+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 1966632] Re: After every boot my brightness is on the lowest level
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/1966632 Title: After every boot my brightness is on the lowest level Status in linux package in Ubuntu: Fix Released Bug description: i have hp elitebook 845 g8 and i discovered annoying problem with backlight, after grub starts boot sequence before login screen appears backlight level is set right, after one second after login screen appears backlight level is automatically set to lowest. After entering the password backlight level stays unchanged. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-37-generic 5.13.0-37.42 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matej 2133 F pulseaudio /dev/snd/pcmC1D0c: matej 2133 F...m pulseaudio /dev/snd/pcmC1D0p: matej 2133 F...m pulseaudio /dev/snd/controlC0: matej 2133 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 09:17:56 2022 InstallationDate: Installed on 2022-03-23 (4 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210502) MachineType: HP HP EliteBook 845 G8 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-37-generic root=UUID=e3adb113-cca4-4316-9c3b-edc124da9ca4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2022 dmi.bios.release: 8.3 dmi.bios.vendor: HP dmi.bios.version: T82 Ver. 01.08.03 dmi.board.name: 8895 dmi.board.vendor: HP dmi.board.version: KBC Version 43.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 67.42 dmi.modalias: dmi:bvnHP:bvrT82Ver.01.08.03:bd02/11/2022:br8.3:efr67.42:svnHP:pnHPEliteBook845G8NotebookPC:pvr:rvnHP:rn8895:rvrKBCVersion43.2A.00:cvnHP:ct10:cvr:sku48R69EA#BCM: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 845 G8 Notebook PC dmi.product.sku: 48R69EA#BCM dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966632/+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 1966803] Re: xfs: Fix deadlock between AGI and AGF when target_ip exists in xfs_rename()
** Attachment added: "110-xfs.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966803/+attachment/5582132/+files/110-xfs.log ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1966803 Title: xfs: Fix deadlock between AGI and AGF when target_ip exists in xfs_rename() Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] * The xfs filesystem suffers from a deadlock issue in kernels < 5.5. This hangs IO to/from the affected filesystem. Sample backtraces added as a comment. [Fix] * 93597ae8dac0149b5c00b787cba6bf7ba213e666 93597ae8dac0 "xfs: Fix deadlock between AGI and AGF when target_ip exists in xfs_rename()" * This is from the upstream 5.5 kernel. [Test Plan] * Set up an Ubuntu Bionic/Focal installation using kernel 5.4. * Create and mount an XFS filesystem on a block device. * Exercise the filesystem to verify that IO does not hang. [Where problems could occur] * This patch could cause locking issues on XFS filesystems, requiring a system restart to correct. [Other Info] * Bug is difficult to reproduce, a test kernel on affected systems with the above patch prevented the issue. * Backports to earlier (4.15 and earlier) kernels have been omitted as the upstream patch does not apply cleanly and the issue has not been reproduced on them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966803/+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 1966803] Re: xfs: Fix deadlock between AGI and AGF when target_ip exists in xfs_rename()
Verification for Focal Ran the xfstests (https://git.kernel.org/pub/scm/fs/xfs/xfstests- dev.git) on the current 5.4.0-109-generic #123-Ubuntu kernel and the -proposed kernel 5.4.0-110-generic #124-Ubuntu in a VM to exercise the XFS filesystem thoroughly. Detailed log files of the tests are attached. The tests completed successfully on both kernels, with the -110 kernel failing 2 fewer tests than the -109 kernel. 109 (-updates) - Failed 76 of 373 tests 110 (-proposed) - Failed 74 of 373 tests The tests indicate no regressions on the test failures. ** Attachment added: "109-xfs.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966803/+attachment/5582131/+files/109-xfs.log -- 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/1966803 Title: xfs: Fix deadlock between AGI and AGF when target_ip exists in xfs_rename() Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] * The xfs filesystem suffers from a deadlock issue in kernels < 5.5. This hangs IO to/from the affected filesystem. Sample backtraces added as a comment. [Fix] * 93597ae8dac0149b5c00b787cba6bf7ba213e666 93597ae8dac0 "xfs: Fix deadlock between AGI and AGF when target_ip exists in xfs_rename()" * This is from the upstream 5.5 kernel. [Test Plan] * Set up an Ubuntu Bionic/Focal installation using kernel 5.4. * Create and mount an XFS filesystem on a block device. * Exercise the filesystem to verify that IO does not hang. [Where problems could occur] * This patch could cause locking issues on XFS filesystems, requiring a system restart to correct. [Other Info] * Bug is difficult to reproduce, a test kernel on affected systems with the above patch prevented the issue. * Backports to earlier (4.15 and earlier) kernels have been omitted as the upstream patch does not apply cleanly and the issue has not been reproduced on them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966803/+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 1969771] Re: Fix beacon loss for rtl8821ce on certain platforms
** Tags added: oem-priority originate-from-1962681 somerville ** Description changed: [SRU Justification] [Impact] On the intel ADL-U platform, the rtl8821ce suffers the beacon loss frequently because the driver doesn't received any beacon from AP. It causes the wpa-supplicant to reconnect again and again. [Fix] Realtek release a fix to disable the PCI completion timeout on rtl8821ce so the PCI bus won't get stuck and can handed the received packets to the driver correctly. [Test Case] 1. Connect the WiFi to internet by selecting a internet connected AP 2. ping 8.8.8.8 to check the internet connectivity for at least 5 minutes. 3. Make sure no 'CTRL-EVENT-BEACON-LOSS' event reported from wpa_supplicant [Where problems could occur] Risk should be Low. It's only applied for RTL8821CE to disable the completion timeout capability. + + == Original Bug Description == + + [Summary] + Wireless keeps connection and loses connection repeatedly. + + Below test cases are failed: + - wireless/wireless_connection_wpa_n_nm_wlp3s0 + - after-suspend-wireless/wireless_connection_wpa_bg_nm_wlp3s0 + - after-suspend-wireless/wireless_connection_wpa_ac_nm_wlp3s0 + - after-suspend-wireless/wireless_connection_open_n_nm_wlp3s0 + - after-suspend-wireless/wireless_connection_open_bg_nm_wlp3s0 + - after-suspend-wireless/wireless_connection_open_ac_nm_wlp3s0 + + Issue is also observed on WVA4-DVT2-C1 + + [Steps to reproduce] + 1. Boot into OS + 2. Connect network by wireless + 3. Run 'sudo apt update' + + [Expected result] + Wireless connection won't break + + [Actual result] + Wireless loses the connection and then connect network, after a while, issue happens again. + + [Failure rate] + 10/10 + + [Additional information] + CID: 202202-29949, 202202-29947 + SKU: WMVA5-DVT2-C1, WVA4-DVT2-C1 + Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-olly-adl+X175 + system-manufacturer: Dell Inc. + system-product-name: Vostro 3520 + bios-version: 0.5.4 + CPU: 12th Gen Intel(R) Core(TM) i5-1235U (12x) + GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4628] (rev 0c) + :01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1f9f] (rev a1) + kernel-version: 5.14.0-1024-oem + + [Stage] + Issue reported and logs collected at a later stage -- 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/1969771 Title: Fix beacon loss for rtl8821ce on certain platforms Status in HWE Next: New 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: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.14 source package in Focal: New Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: [SRU Justification] [Impact] On the intel ADL-U platform, the rtl8821ce suffers the beacon loss frequently because the driver doesn't received any beacon from AP. It causes the wpa-supplicant to reconnect again and again. [Fix] Realtek release a fix to disable the PCI completion timeout on rtl8821ce so the PCI bus won't get stuck and can handed the received packets to the driver correctly. [Test Case] 1. Connect the WiFi to internet by selecting a internet connected AP 2. ping 8.8.8.8 to check the internet connectivity for at least 5 minutes. 3. Make sure no 'CTRL-EVENT-BEACON-LOSS' event reported from wpa_supplicant [Where problems could occur] Risk should be Low. It's only applied for RTL8821CE to disable the completion timeout capability. == Original Bug Description == [Summary] Wireless keeps connection and loses connection repeatedly. Below test cases are failed: - wireless/wireless_connection_wpa_n_nm_wlp3s0 - after-suspend-wireless/wireless_connection_wpa_bg_nm_wlp3s0 - after-suspend-wireless/wireless_connection_wpa_ac_nm_wlp3s0 - after-suspend-wireless/wireless_connection_open_n_nm_wlp3s0 - after-suspend-wireless/wireless_connection_open_bg_nm_wlp3s0 - after-suspend-wireless/wireless_connection_open_ac_nm_wlp3s0 Issue is also observed on WVA4-DVT2-C1 [Steps to reproduce] 1. Boot into OS 2. Connect network by wireless 3. Run 'sudo apt update' [Expected result] Wireless connection won't break [Actual result] Wireless loses the connection and then connect network, after a while, issue happens again. [Failure rate] 10/10 [Additional information] CID: 202202-29949, 202202-29947 SKU: WMVA5-DVT2-C1, WVA4-DVT2-C1 Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-olly-adl+X175 system-manufacturer: Dell Inc. syste
[Kernel-packages] [Bug 1946828] Re: ntfsresize hang and call traces in syslog
for issue #1966544 I can recreate it 100% of the time with secure boot on, unable to recreate at all with secure boot disabled. also unable to recreate at all with Jammy builds dated 29 mar 2022 and 19 apr 2022... -- 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/1946828 Title: ntfsresize hang and call traces in syslog Status in linux package in Ubuntu: Confirmed Status in ntfs-3g package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in ntfs-3g source package in Jammy: Confirmed Status in ubiquity source package in Jammy: Confirmed Bug description: Attempting to boot the impish final iso on my kvm VM setup with a windows 10 install on the virtual disk. The install process hangs at the "updates and other software" screen, apparently on a ntfsresize call. Mind you, this is before I have chosen disks to partition - I'm at the step where I can choose a Normal or Minimal installation. While this is not a 100% reproduction rate issue, the rate seems high - above 50% I would guess. If I try to quickly click thru the installer on boot it might be a little more likely. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-19-generic 5.13.0-19.19 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4609 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 13 02:40:56 2021 IwConfig: lono wireless extensions. enp1s0no wireless extensions. LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.201 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-5.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.2:sku:cvnQEMU:ct1:cvrpc-q35-5.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-5.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946828/+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 1969776] [NEW] package nvidia-dkms-510-server 510.47.03-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-510-server package post-installation script subprocess
Public bug reported: It would install on kernel 5.17.3 but then that version wouldn't be able to access the boot drive ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-510-server 510.47.03-0ubuntu0.20.04.1 Uname: Linux 5.17.4-051704-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 21 08:45:38 2022 ErrorMessage: installed nvidia-dkms-510-server package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-04-08 (12 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-510-server Title: package nvidia-dkms-510-server 510.47.03-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-510-server package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-510-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510-server in Ubuntu. https://bugs.launchpad.net/bugs/1969776 Title: package nvidia-dkms-510-server 510.47.03-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-510-server package post- installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-510-server package in Ubuntu: New Bug description: It would install on kernel 5.17.3 but then that version wouldn't be able to access the boot drive ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-510-server 510.47.03-0ubuntu0.20.04.1 Uname: Linux 5.17.4-051704-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 21 08:45:38 2022 ErrorMessage: installed nvidia-dkms-510-server package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-04-08 (12 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-510-server Title: package nvidia-dkms-510-server 510.47.03-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-510-server package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510-server/+bug/1969776/+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 1969771] 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 1969771 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 ** Changed in: linux (Ubuntu Focal) 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/1969771 Title: Fix beacon loss for rtl8821ce on certain platforms 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: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.14 source package in Focal: New Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: [SRU Justification] [Impact] On the intel ADL-U platform, the rtl8821ce suffers the beacon loss frequently because the driver doesn't received any beacon from AP. It causes the wpa-supplicant to reconnect again and again. [Fix] Realtek release a fix to disable the PCI completion timeout on rtl8821ce so the PCI bus won't get stuck and can handed the received packets to the driver correctly. [Test Case] 1. Connect the WiFi to internet by selecting a internet connected AP 2. ping 8.8.8.8 to check the internet connectivity for at least 5 minutes. 3. Make sure no 'CTRL-EVENT-BEACON-LOSS' event reported from wpa_supplicant [Where problems could occur] Risk should be Low. It's only applied for RTL8821CE to disable the completion timeout capability. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969771/+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 1969771] [NEW] Fix beacon loss for rtl8821ce on certain platforms
Public bug reported: [SRU Justification] [Impact] On the intel ADL-U platform, the rtl8821ce suffers the beacon loss frequently because the driver doesn't received any beacon from AP. It causes the wpa-supplicant to reconnect again and again. [Fix] Realtek release a fix to disable the PCI completion timeout on rtl8821ce so the PCI bus won't get stuck and can handed the received packets to the driver correctly. [Test Case] 1. Connect the WiFi to internet by selecting a internet connected AP 2. ping 8.8.8.8 to check the internet connectivity for at least 5 minutes. 3. Make sure no 'CTRL-EVENT-BEACON-LOSS' event reported from wpa_supplicant [Where problems could occur] Risk should be Low. It's only applied for RTL8821CE to disable the completion timeout capability. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.17 (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid -- 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/1969771 Title: Fix beacon loss for rtl8821ce on certain platforms Status in linux package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Bug description: [SRU Justification] [Impact] On the intel ADL-U platform, the rtl8821ce suffers the beacon loss frequently because the driver doesn't received any beacon from AP. It causes the wpa-supplicant to reconnect again and again. [Fix] Realtek release a fix to disable the PCI completion timeout on rtl8821ce so the PCI bus won't get stuck and can handed the received packets to the driver correctly. [Test Case] 1. Connect the WiFi to internet by selecting a internet connected AP 2. ping 8.8.8.8 to check the internet connectivity for at least 5 minutes. 3. Make sure no 'CTRL-EVENT-BEACON-LOSS' event reported from wpa_supplicant [Where problems could occur] Risk should be Low. It's only applied for RTL8821CE to disable the completion timeout capability. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969771/+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 1968681] Re: rdpru in ubuntu_kvm_unit_tests failed on B-4.15 node riccioli with FAIL: RDPRU raises #UD
This hardware is an AMD system, codename Rome, Second generation Epyc Fix: https://github.com/torvalds/linux/commit/9d40b85bb46a99bc95dad3a07787da93b0a018e9 https://github.com/torvalds/linux/commit/0cb8410b90e78948984f35f2c4d50c2c0b7ee675 With patched kernel, the rdpru flag will be available in cpuinfo: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 invpcid_single hw_pstate ssbd ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold v_vmsave_vmload vgif umip pku ospke vaes vpclmulqdq rdpid overflow_recov succor smca bugs: sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass $ sudo ./rdpru BUILD_HEAD=16647354 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.syc17ecDpN -smp 1 -cpu max # -initrd /tmp/tmp.poLG53JqrJ enabling apic PASS: RDPRU raises #UD SUMMARY: 1 tests PASS rdpru (1 tests) -- 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/1968681 Title: rdpru in ubuntu_kvm_unit_tests failed on B-4.15 node riccioli with FAIL: RDPRU raises #UD Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Bug description: Issue found on B-ibm-gt-4.15.0-1116.127 This can be reproduced with B-4.15.0-175 as well. This failure is only visible on this node. Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/rdpru' BUILD_HEAD=16647354 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.qGIR5tvTw1 -smp 1 -cpu max # -initrd /tmp/tmp.8JuYRCFRUi enabling apic FAIL: RDPRU raises #UD SUMMARY: 1 tests, 1 unexpected failures FAIL rdpru (1 tests, 1 unexpected failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968681/+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 1968681] Re: rdpru in ubuntu_kvm_unit_tests failed on B-4.15 node riccioli with FAIL: RDPRU raises #UD
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Bionic) 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/1968681 Title: rdpru in ubuntu_kvm_unit_tests failed on B-4.15 node riccioli with FAIL: RDPRU raises #UD Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Bug description: Issue found on B-ibm-gt-4.15.0-1116.127 This can be reproduced with B-4.15.0-175 as well. This failure is only visible on this node. Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/rdpru' BUILD_HEAD=16647354 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.qGIR5tvTw1 -smp 1 -cpu max # -initrd /tmp/tmp.8JuYRCFRUi enabling apic FAIL: RDPRU raises #UD SUMMARY: 1 tests, 1 unexpected failures FAIL rdpru (1 tests, 1 unexpected failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968681/+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 1968016] Re: Use kernel-testing repo from launchpad for ADT tests
ADT started correctly on Bionic as well. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1968016 Title: Use kernel-testing repo from launchpad for ADT tests Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Status in linux-oem-5.14 source package in Trusty: Invalid Status in linux-oem-5.17 source package in Trusty: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-oem-5.14 source package in Xenial: Invalid Status in linux-oem-5.17 source package in Xenial: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux-oem-5.17 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: In Progress Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: In ADT tests, we are still using the kernel-testing repo from kernel.ubuntu.com, it should be migrated to launchpad instead to align with our other testing repos. For autotest-client-tests repo change, it will needs to be handled in the kernel-testing repo directly, see bug 1968257. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968016/+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 1969755] Re: ADLP AX211 iwlwifi firmware crash when running connect/disconnect stress
The highest firmware version for the kernel is -66. it seems there is no -66 for the module in upstream [1]. [1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/ ** Description changed: On Intel ADL-P platform with AX211 Wi-Fi, runs connect/disconnect stress, encounter firmware crash. + + A stress script can be obtained by + $ sudo add-apt-repository ppa:checkbox-dev/ppa + $ sudo apt install checkbox-ng plainbox-provider-checkbox + $ checkbox-cli run com.canonical.certification::stress/wireless_bluetooth_coex_connect_stress + The stress test will be failed when it encounters the firmware crash. Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: SecBoot CPU1 Status: 0x71ea, CPU2 Status: 0xb03 Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: UMAC PC: 0xc00817f8 Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: LMAC PC: 0x1541c Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired (delay=0ms). Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: Loaded firmware version: 64.97bbee0a.0 so-a0-gf-a0-64.ucode - Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: 0x | ADVANCED_SYSASSERT + Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: 0x | ADVANCED_SYSASSERT Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: 0x | trm_hw_status0 Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: 0x | trm_hw_status1 Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: 0x | branchlink2 Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: 0x | interruptlink1 Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: 0x | interruptlink2 .. Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: 0x9061 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: 0x0061 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: Failed to start RT ucode: -110 Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired (delay=0ms). Apr 21 17:34:23 SPM5-C3 kernel: iwlwifi :00:14.3: Failed to run INIT ucode: -110 Apr 21 17:34:23 SPM5-C3 kernel: iwlwifi :00:14.3: retry init count 0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-28.29-generic 5.15.34 Uname: Linux 5.15.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: kchsieh1094 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: kchsieh1094 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 17:35:07 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-04-21 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Latitude 5530 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-28-generic root=UUID=bd255754-12cc-49d1-9566-f0ecd882e202 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.15.0-28-generic N/A - linux-backports-modules-5.15.0-28-generic N/A - linux-firmware 20220329.git681281e4-0ubuntu1 + linux-restricted-modules-5.15.0-28-generic N/A + linux-backports-modules-5.15.0-28-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/28/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd03/28/2022:br1.1:svnDellInc.:pnLatitude5530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0B06: dmi.product.family: Latitude dmi.product.name: Latitude 5530 dmi.product.sku: 0B06 dmi.sys.vendor: Dell Inc. -- 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/1969755 Title: ADLP AX211 iwlwifi firmware crash when running connect/disconnect stress Status in linux-firmware package in Ubuntu: New Bug description: On Intel ADL-P platform with AX211 Wi-Fi, runs connect/disconnect stress, encounter firmware crash. A stress script can be obtained by $ sudo add-apt-repository ppa:checkbox-dev/ppa $ sudo apt install checkbox-ng plainbox-provider-checkbox $ checkbox-cli run com.canonical.certification::stress/wireless_bluetooth_coex_connect_stress The stress test will be failed when it encounters the firmware crash. Apr 21 17:3
[Kernel-packages] [Bug 1969755] [NEW] ADLP AX211 iwlwifi firmware crash when running connect/disconnect stress
Public bug reported: On Intel ADL-P platform with AX211 Wi-Fi, runs connect/disconnect stress, encounter firmware crash. A stress script can be obtained by $ sudo add-apt-repository ppa:checkbox-dev/ppa $ sudo apt install checkbox-ng plainbox-provider-checkbox $ checkbox-cli run com.canonical.certification::stress/wireless_bluetooth_coex_connect_stress The stress test will be failed when it encounters the firmware crash. Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: SecBoot CPU1 Status: 0x71ea, CPU2 Status: 0xb03 Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: UMAC PC: 0xc00817f8 Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: LMAC PC: 0x1541c Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired (delay=0ms). Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: Loaded firmware version: 64.97bbee0a.0 so-a0-gf-a0-64.ucode Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: 0x | ADVANCED_SYSASSERT Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: 0x | trm_hw_status0 Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: 0x | trm_hw_status1 Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: 0x | branchlink2 Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: 0x | interruptlink1 Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: 0x | interruptlink2 .. Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: 0x9061 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: 0x0061 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: Failed to start RT ucode: -110 Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired (delay=0ms). Apr 21 17:34:23 SPM5-C3 kernel: iwlwifi :00:14.3: Failed to run INIT ucode: -110 Apr 21 17:34:23 SPM5-C3 kernel: iwlwifi :00:14.3: retry init count 0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-28.29-generic 5.15.34 Uname: Linux 5.15.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kchsieh1094 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 17:35:07 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-04-21 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Latitude 5530 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-28-generic root=UUID=bd255754-12cc-49d1-9566-f0ecd882e202 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-28-generic N/A linux-backports-modules-5.15.0-28-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/28/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd03/28/2022:br1.1:svnDellInc.:pnLatitude5530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0B06: dmi.product.family: Latitude dmi.product.name: Latitude 5530 dmi.product.sku: 0B06 dmi.sys.vendor: Dell Inc. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy oem-priority wayland-session ** Attachment added: "kernel.log" https://bugs.launchpad.net/bugs/1969755/+attachment/5582031/+files/kernel.log ** Summary changed: - Encounter iwlwifi firmware crash when running connect/disconnect stress + ADLP AX211 iwlwifi firmware crash when running connect/disconnect stress ** Tags added: oem-priority -- 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/1969755 Title: ADLP AX211 iwlwifi firmware crash when running connect/disconnect stress Status in linux-firmware package in Ubuntu: New Bug description: On Intel ADL-P platform with AX211 Wi-Fi, runs connect/disconnect stress, encounter firmware crash. A stress script can be obtained by $ sudo add-apt-repository ppa:checkbox-dev/ppa $ sudo apt install checkbox-ng plainbox-provider-checkbox $ checkbox-cli run com.canonical.certification::stress/wireless_bluetooth_coex_connect_stress The stress test will be failed when it encounters the firmware crash. Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: SecBoot CPU1 Status: 0x71ea, CPU2 Status: 0xb03 Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: UMAC PC: 0xc00817f8 Apr 21 17:34:22 SPM5-C3 kernel: iwlwifi :00:14.3: LMAC PC:
[Kernel-packages] [Bug 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
> [Impact]
> The backlight power won't come back after the meta + l to turn off the
> display on ADL machines.
Judging by drminfo.txt, there is no backlight because it's OLED. Only
the OLED variant of XPS 9320 is 3456x2160 pixels.
--
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/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in mutter package in Ubuntu:
Fix Committed
Status in linux source package in Jammy:
In Progress
Status in mutter source package in Jammy:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
==
SRU Justification
[Impact]
The backlight power won't come back after the meta + l to turn off the
display on ADL machines.
[Fix]
Below series of commits from v5.17 fix this issue
1c7ab5affa5e drm/i915/xelpd: Add Pipe Color Lut caps to platform config
17815f624a90 drm/i915/xelpd: Enable Pipe Degamma
e83c18cffaed drm/i915/xelpd: Enable Pipe color support for D13 platform
[Test]
Verified on at least 2 different machines, the backlight is on after the
screen dimmed with touchpad movement or key stroke.
[Where problems could occcur]
The patches only affect ADL-P and up.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1969633] Re: Continuous Bluetooth timeouts [Broadcom BCM20702A]
We have been notified already, but most kernel fixes don't come from Canonical. It appears the problem is the 'btbcm' kernel driver. I suggest your best option is to try a newer kernel, and the best way to do that is to wait until Ubuntu 22.04 is released this weekend. Alternatively you can try newer kernel versions from https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D Probably the quickest solution however is to change to a different brand of USB Bluetooth dongle. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1969633 Title: Continuous Bluetooth timeouts [Broadcom BCM20702A] Status in linux-hwe-5.13 package in Ubuntu: New Bug description: My computer is an ASUS A88XM-A with AMD A8-7600 Radeon R7. Pluggable USB 2 Bluetooth dongle. Logitech K480 Bluetooth keyboard and Keychron K7 Bluetooth "keyboard". The Bluetooth manager finds the K480 but pairing always fails. The keyboard flashes blue but dongle steady blue. The K7 does not even show up. (But then the "keyboard" does not even work using a USB cable.) Bought dongle and K480 4 years ago, never got them to work at all, gave up as a bad investment. I ordered a K7 wireless keyboard. What I received was a Bluetooth keyboard. Bluetooth does not work. Plugging it in with a USB cable partially works (function keys and End key do not work). Got the K480 working with my Samsung Galaxy 5 Android tablet, but not with my computer. I want Bluetooth but do not know how to get it to work. It still does not work after 4 years of cold boots and the replacement of the power supply. I went to the Keychron Facebook Linux group. They were complaining that Ubuntu does not support Bluetooth and that the Keychron function keys do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Apr 20 10:45:57 2022 InstallationDate: Installed on 2022-03-05 (46 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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: System manufacturer hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1969633/+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 1948626] Re: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010
Michael, The test kernel listed here is 5.13 kernel, but jammy is of v5.15 kernel. Is this going to be for Jammy? https://people.canonical.com/~mreed/lp_1948626_nvme_tcp/ -- 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/1948626 Title: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [Impact] NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one. TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers. TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis. Here is code that implements TP8009 and TP8010: https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas [Fix] 1. Update kernel with TP8010 kernel patches: a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907 b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0 c. nvme: add CNTRLTYPE definitions for 'identify controller https://lore.kernel.org/all/66fc4f03-ed5c-4727-ba94-c23daf7d6...@oracle.com/ [Test Case] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626/+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 1936903] Re: CDTS Network (Ethernet) failures
** Changed in: intel/lookout-canyon Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1936903 Title: CDTS Network (Ethernet) failures Status in intel: New Status in intel lookout-canyon series: Invalid Status in Ubuntu: Incomplete Status in linux-intel package in Ubuntu: New Bug description: [Summary]Some networking tests fail [Steps to reproduce]Run Manual Non-Device Networking Tests $ sudo snap install checkbox20 $ sudo snap install cdts --classic --channel=20.04/stable $ cdts.checkbox-cli (X) Networking tests (manual) [X] + Non-device specific networking tests [Expected result]100% pass [Actual result] networking/info_device1_enp0s30f4 - skipped by tester (no second ethernet port on this board) networking/info_device2_UNKNOWN - failed by tester (should not have UNKNOWN devices) [Failure rate]100% [Additional information] CID: 202106-28175 SKU: system-manufacturer: Intel Corporation system-product-name: Tiger Lake Client Platform bios-version: TGLIFUI1.R00.3455.A03.2011281547 CPU: Genuine Intel(R) CPU @ 2.60GHz (16x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9a60] kernel-version: 5.11.0-1009-intel [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1936903/+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 1967889] Re: Raise CONFIG_NR_CPUS
The following patch sets reasonable values for CONFIG_NR_CPUS on RISC-V: [PATCH v3] RISC-V: Increase range and default value of NR_CPUS https://lore.kernel.org/all/20220420112408.155561-1-apa...@ventanamicro.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1967889 Title: Raise CONFIG_NR_CPUS Status in linux-riscv package in Ubuntu: New Bug description: The QEMU 7.0 virt machine offers up to 32 virtual harts. This matches the number of hardware threads on a typical desktop CPU (AMD Ryzen 5950X). Our Linux kernel should support this number of harts. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967889/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
SRU sent
https://lists.ubuntu.com/archives/kernel-team/2022-April/129627.html
--
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/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in mutter package in Ubuntu:
Fix Committed
Status in linux source package in Jammy:
In Progress
Status in mutter source package in Jammy:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
==
SRU Justification
[Impact]
The backlight power won't come back after the meta + l to turn off the
display on ADL machines.
[Fix]
Below series of commits from v5.17 fix this issue
1c7ab5affa5e drm/i915/xelpd: Add Pipe Color Lut caps to platform config
17815f624a90 drm/i915/xelpd: Enable Pipe Degamma
e83c18cffaed drm/i915/xelpd: Enable Pipe color support for D13 platform
[Test]
Verified on at least 2 different machines, the backlight is on after the
screen dimmed with touchpad movement or key stroke.
[Where problems could occcur]
The patches only affect ADL-P and up.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1969326] Re: Enable hotspot feature for Realtek 8821CE
** Description changed: [Impact] The wifi hotspot doesn't work without the fix. [Fix] Realtek provides us the patches to add this feature which are still in linux-next. https://patchwork.kernel.org/project/linux-wireless/cover/20220407095858.46807-1-pks...@realtek.com/ [Test] Verified on the Realtek 8821CE card. [Where problems could occur] + The patches are introducing new interfaces, I think it only has minimal impact to the origin behaviors. ** Description changed: [Impact] The wifi hotspot doesn't work without the fix. [Fix] Realtek provides us the patches to add this feature which are still in linux-next. https://patchwork.kernel.org/project/linux-wireless/cover/20220407095858.46807-1-pks...@realtek.com/ + ece31c93d4d6 rtw88: 8821c: fix debugfs rssi value + f5207c122102 rtw88: do PHY calibration while starting AP + f1c4dabfe68d rtw88: 8821c: Enable TX report for management frames + f2217968ffda rtw88: Add update beacon flow for AP mode + 6723c0cde84f rtw88: fix incorrect frequency reported + c1edc86472fc rtw88: add ieee80211:sta_rc_update ops + + Realtek provides us another series of patches for 5.14, and it contains + 5 commits, we'd verified this series of patches. [Test] Verified on the Realtek 8821CE card. [Where problems could occur] The patches are introducing new interfaces, I think it only has minimal impact to the origin behaviors. -- 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/1969326 Title: Enable hotspot feature for Realtek 8821CE Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] The wifi hotspot doesn't work without the fix. [Fix] Realtek provides us the patches to add this feature which are still in linux-next. https://patchwork.kernel.org/project/linux-wireless/cover/20220407095858.46807-1-pks...@realtek.com/ ece31c93d4d6 rtw88: 8821c: fix debugfs rssi value f5207c122102 rtw88: do PHY calibration while starting AP f1c4dabfe68d rtw88: 8821c: Enable TX report for management frames f2217968ffda rtw88: Add update beacon flow for AP mode 6723c0cde84f rtw88: fix incorrect frequency reported c1edc86472fc rtw88: add ieee80211:sta_rc_update ops Realtek provides us another series of patches for 5.14, and it contains 5 commits, we'd verified this series of patches. [Test] Verified on the Realtek 8821CE card. [Where problems could occur] The patches are introducing new interfaces, I think it only has minimal impact to the origin behaviors. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969326/+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
