[Kernel-packages] [Bug 1958620] Re: Flickering white/black screen once KMS comes up
Further investigation: Affects: 1) 5.13.19 does not suffer from this bug 2) The Ubuntu 5.15 kernels, and mainline 5.16 and 5.17 kernels *do* suffer from this bug. Also of note: this only occurs the *first* time KMS tries to come up on the panel, and *only* if there is not a second monitor plugged in. Having a second monitor plugged in at boot results in a successful boot, *plugging in* a second monitor after triggering this bug results in *both* displays working fine, and *removing* a second monitor leaves the laptop panel working. It looks like maybe a bug has been introduced in framebuffer allocation? -- 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/1958620 Title: Flickering white/black screen once KMS comes up Status in linux package in Ubuntu: Confirmed Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+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 1965968] Re: [Dell XPS 15 9575] Black screen on boot in kernels 5.14 and 5.15 (but 5.13.19 works)
*** This bug is a duplicate of bug 1958620 *** https://bugs.launchpad.net/bugs/1958620 ** This bug has been marked a duplicate of bug 1958620 Flickering white/black screen once KMS comes up -- 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/1965968 Title: [Dell XPS 15 9575] Black screen on boot in kernels 5.14 and 5.15 (but 5.13.19 works) Status in linux package in Ubuntu: Confirmed Bug description: After initial jammy upgrade things were working fine, but after a recent update the machine boots to a blank screen. There are occasional purplish flickers that seem to correspond with keypresses, but even blindly typing the encrypted disk password doesn't appear to advance the boot process to gdm. Plugging in an external monitor does fix the issue and allow boot to proceed, but obviously doesn't help if not near an external monitor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth 0.9.5+git20211018-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 22 09:22:26 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-08-17 (948 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) MachineType: Dell Inc. XPS 15 9575 ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965968/+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 1958620] Re: Flickering white/black screen once KMS comes up
Ah! I was looking for this bug yesterday when duplicate bug 1965968 was reported. ** Summary changed: - Flickering white/black screen once KMS comes up + [Dell XPS 15 9575] Flickering white/black screen once KMS comes up -- 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/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in linux package in Ubuntu: Confirmed Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+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 1966215] Re: USB audio on Focusrite scarlett 2i2 (2nd Gen) is distorted
*** This bug is a duplicate of bug 1966066 *** https://bugs.launchpad.net/bugs/1966066 Possible dup of bug #1966066, please feel free to remove dup if you think this is incorrect. Thanks. ** This bug has been marked a duplicate of bug 1966066 audio from external sound card is distorted -- 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/1966215 Title: USB audio on Focusrite scarlett 2i2 (2nd Gen) is distorted Status in linux package in Ubuntu: Incomplete Bug description: issues is with `Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19` audio is distorted, not sure how to describe it but there is somewhat of an electronic noise with a small delay tested with `Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19` and problem does not occur Seems to be only happening on usb audio, normal audio seems fine Hardware in question: Focusrite scarlett 2i2 (2nd Gen) is distorted --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: floris 1998 F pulseaudio /dev/snd/controlC1: floris 1998 F pulseaudio /dev/snd/controlC0: floris 1998 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-10-19 (156 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 81YQ Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-37-generic root=UUID=66316bb3-7a4a-4fb0-b54f-41b37af8f9bf ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.187.29 Tags: uma Uname: Linux 5.13.0-37-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo tty uucp _MarkForUpload: False dmi.bios.date: 10/12/2020 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrE7CN34WW:bd10/12/2020:br1.34:efr1.34:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515ARE05:skuLENOVO_MT_81YQ_BU_idea_FM_IdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: floris 1998 F pulseaudio /dev/snd/controlC1: floris 1998 F pulseaudio /dev/snd/pcmC1D0p: floris 1998 F...m pulseaudio /dev/snd/controlC0: floris 1998 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2021-10-19 (156 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 81YQ Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-37-generic root=UUID=66316bb3-7a4a-4fb0-b54f-41b37af8f9bf ro quiet splash ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.187.29 Tags: uma Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo tty uucp _MarkForUpload: True dmi.bios.date: 10/12/2020 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrE7CN34WW:bd10/12/2020:br1.34:efr1.34:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515ARE05:skuLENOVO_MT_81YQ_BU_idea_FM_IdeaPad515ARE05:
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
The other bug mentions that the flickering seems unrelated to the blackness. Fixing the flickering needed i915.enable_psr=0 Fixing the blackness needed kernel <= 5.13.19 (or generally < 5.14) ** Tags added: i915 regression regression-release ** Changed in: linux (Ubuntu) Importance: Undecided => High -- 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/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in linux package in Ubuntu: Confirmed Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+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 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
I feel like the OEM team would have encountered and fixed this already. Can you try an OEM kernel? -- 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/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in linux package in Ubuntu: Confirmed Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+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 1939638] Re: [regression] USB device is not detected during boot
Broken again on Ubuntu 20.04LTS after updating to kernel 5.4.0-105-generic.
USB2 devices not detected on USB3 ports after reboot, but appearing after:
$ echo ':00:14.0' | sudo tee /sys/bus/pci/drivers/xhci_hcd/unbind
$ sleep 1
$ echo ':00:14.0' | sudo tee /sys/bus/pci/drivers/xhci_hcd
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1939638
Title:
[regression] USB device is not detected during boot
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-intel package in Ubuntu:
Confirmed
Status in linux-intel-5.13 package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux-intel source package in Focal:
Confirmed
Status in linux-intel-5.13 source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in linux-intel source package in Hirsute:
Invalid
Status in linux-intel-5.13 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
The USB devices (keyboard, storage...) are failed to be detected when
connecting to the problematic root hubs which need longer PowerOn-to-PowerGood
delay than it claims in the hub descriptor. It's caused by the upstream fix
90d28fb53d4a ("usb: core: reduce power-on-good delay time of root hub").
[Fix]
Reverting the upstream fix until a formal fix been placed.
[Test Case]
1. Plug the USB device to the ports of problematic root hub.
2. Power on the machine.
3. Check if the USB device can work or not after boot.
[Regression Potential]
Low. The longer delay is proven safe in old kernels.
== Original Bug Description ==
[Summary]
The USB devices (keyboard, storage...) are failed to be detected during boot
after upgrade to UBUNTU focal kernel 5.4.0-78 and hirsute 5.11.0-26. However,
they will be detected and working ok after re-plugging. The kernel output shows
as down below during boot
[ 39.350435] hub 1-0:1.0: USB hub found
[ 39.398835] hub 1-0:1.0: 12 ports detected
[ 39.622744] usb usb1-port3: couldn't allocate usb_device
And when I plug out then plug in the same device, it shows
[57210.794140] usb 1-3: new low-speed USB device number 4 using xhci_hcd
[57210.951289] usb 1-3: New USB device found, idVendor=17ef, idProduct=6099,
bcdDevice= 1.14
[57210.951293] usb 1-3: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
After doing kernel bisecting, we found the upstream commit
https://github.com/torvalds/linux/commit/90d28fb53d4a51299ff324dede015d5cb11b88a2
makes the difference. It indicates that the delay for the root hub from
power_on to power_good is not long enough. There was no problem if the delay is
100 ms. From the Hub Descriptor of the root hub, the value is 10 * 2
milliseconds. And the XHCI spec also says in section 5.4.8
"""
The host is required to have power stable to the port within 20 milliseconds
of the '0' to '1' transition of PP. If PPC = '1', software is responsible for
waiting 20ms.
"""
The commit seems to follow the SPEC but could cause problems on some
hubs.
[Reproduce Steps]
1. Plug the USB device to the physical port #1 and #4 which belongs to
high-speed hub.
2. Power on the machine.
3. Check if the USB device can work or not after boot.
[Results]
Expected:
All usb devices connect to the hub should work OK.
Actual:
USB devices connects to high-speed hub can not be probed.
[Additional Information]
Kernel Version: focal 5.4.0-78 and hirsute 5.11.0-26
[Upstream bug]
https://bugzilla.kernel.org/show_bug.cgi?id=214021
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1939638/+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 1966066] Re: audio from external sound card is distorted
I also confirm this with my soundcard. how do you set default-sample-rate = 48000 ?? i don't have permission? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1966066 Title: audio from external sound card is distorted Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: The sound card is a Focusrite Scarlett 2i2. The sound is distorted everywhere. Sound via HDMI works. Seen others having the same problem: (Edit because of previously wrong link here) https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card ubuntu release: Ubuntu 20.04.4 LTS package name involved in bug: linux-image-5.13.0-37-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 12:56:02 2022 InstallationDate: Installed on 2020-12-18 (459 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966066/+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 1962349] Re: Bolt doesn't work with native USB4 hosts
jammy has 0.9.2-1 since last month, any reason not to backport that instead? -- 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/1962349 Title: Bolt doesn't work with native USB4 hosts Status in OEM Priority Project: New Status in bolt package in Ubuntu: Fix Released 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 bolt source package in Focal: In Progress Status in linux source package in Focal: Won't Fix 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 bolt source package in Impish: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released 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] * AMD Yellow Carp provides integrated USB4 host controllers * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] AMD Yellow Carp Host (issue this bug is about) -- * Plug in USB4 device or TBT3 to AMD Yellow Carp host * Ensure that PCI topology has populated * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" * Try to run `boltctl enroll $UUID` Alpine Ridge / Titan Ridge host (discrete controller) -- Start out on a host with discrete controller (Alpine Ridge or Titan Ridge) 1. sudo boltctl forget -a 2. Plug in dock 3. Make sure 'boltctl list' enumerates dock. 4. Check /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection (value dependent upon host) - If 0; try to manually enroll using 'boltctl enroll $UUID' - If 1; ensure that device automatically enrolled with bolt. GUI Check - Ensure that devices show up in the Settings GUI and are now able to authorize. Note: for AMD platforms enumerating PCIe devices is a separate problem from BOLT handled by kernel tasks. GUI check is only about "authorization". [Where problems could occur] * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. * There haven't been any significant bugs reported upstream or in Ubuntu since 0.9.1 release. [Other Info] * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. * It is fixed in bolt 0.9.1 or later release. * To solve the SRU, will backport 0.9.1 release from Impish. * I did look into backporting just the commit(s) for fixing this, but it's not a trivial backport. Quoting the changelog (https://gitlab.freedesktop.org/bolt/bolt/-/blob/master/CHANGELOG.md): "Additionally the unique_id of said host controller changes with every boot, which breaks one of the fundamental assumptions in boltd". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962349/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
** Description changed: - After backporting following patches from PA and alsa-ucm-conf and then - it works. + == SRU Justification == + [Impact] + On P620, only single port can work on rear panel. For example, when the Line-Out is plugged, the Mic won't work anymore. + + [Fix] + Use upstream version of UCM to handle port priority correctly, instead of separate ports into different profiles. + + [Test] + Once the UCM is in place, all three ports of rear panel work correctly. + + [Where problems could occur] + UCM is not a static thing - it's actually interpreted differently at higher level. So any change in userspace daemons other than PulseAudio may not like the change and can interpret the UCM in another way. + + == Original Bug Report == + After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: == SRU Justification == [Impact] On P620, only single port can work on rear panel. For example, when the Line-Out is plugged, the Mic won't work anymore. [Fix] Use upstream version of UCM to handle port priority correctly, instead of separate ports into different profiles. [Test] Once the UCM is in place, all three ports of rear panel work correctly. [Where problems could occur] UCM is not a static thing - it's actually interpreted differently at higher level. So any change in userspace daemons other than PulseAudio may not like the change and can interpret the UCM in another way. == Original Bug Report == After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
Hello jeremyszu, or anyone else affected, Accepted alsa-ucm-conf into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.2-1ubuntu0.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: == SRU Justification == [Impact] On P620, only single port can work on rear panel. For example, when the Line-Out is plugged, the Mic won't work anymore. [Fix] Use upstream version of UCM to handle port priority correctly, instead of separate ports into different profiles. [Test] Once the UCM is in place, all three ports of rear panel work correctly. [Where problems could occur] UCM is not a static thing - it's actually interpreted differently at higher level. So any change in userspace daemons other than PulseAudio may not like the change and can interpret the UCM in another way. == Original Bug Report == After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
Turns out that Ubuntu never certified the XPS 9575 so no we don't have a kernel fix prepared and hiding anywhere. -- 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/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in linux package in Ubuntu: Confirmed Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+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 1966417] [NEW] memcontrol04 in ubuntu_ltp_controllers failed on J-azure (Low events in F)
Public bug reported: Issue found on I-azure 5.15.0-1002.3 Test failed with: memcontrol04.c:214: TFAIL: Expect: (F low events=419) == 0 HINT: You _MAY_ be hit by known kernel failures: Low events in F: https://bugzilla.suse.com/show_bug.cgi?id=1196298 Test log: INFO: Test start time: Fri Mar 25 10:03:44 UTC 2022 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 119719 -n 119719 -f /tmp/ltp-mFNzOrxoBY/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_device.c:88: TINFO: Found free device 3 '/dev/loop3' tst_supported_fs_types.c:88: TINFO: Kernel supports ext2 tst_supported_fs_types.c:50: TINFO: mkfs.ext2 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext3 tst_supported_fs_types.c:50: TINFO: mkfs.ext3 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext4 tst_supported_fs_types.c:50: TINFO: mkfs.ext4 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports xfs tst_supported_fs_types.c:50: TINFO: mkfs.xfs does exist tst_supported_fs_types.c:88: TINFO: Kernel supports btrfs tst_supported_fs_types.c:50: TINFO: mkfs.btrfs does exist tst_supported_fs_types.c:155: TINFO: Skipping vfat as requested by the test tst_supported_fs_types.c:155: TINFO: Skipping exfat as requested by the test tst_supported_fs_types.c:155: TINFO: Skipping tmpfs as requested by the test tst_test.c:1528: TINFO: Testing on ext2 tst_test.c:996: TINFO: Formatting /dev/loop3 with ext2 opts='' extra opts='' mke2fs 1.46.5 (30-Dec-2021) tst_test.c:1456: TINFO: Timeout per run is 0h 05m 00s memcontrol04.c:118: TINFO: Child 119783 in leaf_C: Allocating pagecache: 52428800 memcontrol04.c:118: TINFO: Child 119785 in leaf_D: Allocating pagecache: 52428800 memcontrol04.c:118: TINFO: Child 119786 in leaf_F: Allocating pagecache: 52428800 memcontrol04.c:99: TINFO: Child 119787 in trunk_G: Allocating anon: 155189248 memcontrol04.c:170: TPASS: Expect: (A/B memory.current=54177792) ~= 52428800 memcontrol04.c:176: TPASS: Expect: (A/B/C memory.current=30691328) ~= 34603008 memcontrol04.c:178: TPASS: Expect: (A/B/D memory.current=22523904) ~= 17825792 memcontrol04.c:180: TPASS: Expect: (A/B/E memory.current=0) ~= 0 memcontrol04.c:182: TINFO: A/B/F memory.current=950272 memcontrol04.c:99: TINFO: Child 119788 in trunk_G: Allocating anon: 174063616 memcontrol04.c:195: TINFO: A: low events=1645, oom events=0 memcontrol04.c:195: TINFO: B: low events=1645, oom events=0 memcontrol04.c:195: TINFO: G: low events=0, oom events=0 memcontrol04.c:208: TPASS: Expect: (C oom events=0) == 0 memcontrol04.c:211: TPASS: Expect: (C low events=413) > 0 memcontrol04.c:208: TPASS: Expect: (D oom events=0) == 0 memcontrol04.c:211: TPASS: Expect: (D low events=413) > 0 memcontrol04.c:208: TPASS: Expect: (E oom events=0) == 0 memcontrol04.c:214: TPASS: Expect: (E low events=0) == 0 memcontrol04.c:208: TPASS: Expect: (F oom events=0) == 0 memcontrol04.c:214: TFAIL: Expect: (F low events=410) == 0 tst_test.c:1528: TINFO: Testing on ext3 tst_test.c:996: TINFO: Formatting /dev/loop3 with ext3 opts='' extra opts='' mke2fs 1.46.5 (30-Dec-2021) tst_test.c:1456: TINFO: Timeout per run is 0h 05m 00s memcontrol04.c:118: TINFO: Child 119798 in leaf_C: Allocating pagecache: 52428800 memcontrol04.c:118: TINFO: Child 119800 in leaf_D: Allocating pagecache: 52428800 memcontrol04.c:118: TINFO: Child 119801 in leaf_F: Allocating pagecache: 52428800 memcontrol04.c:99: TINFO: Child 119802 in trunk_G: Allocating anon: 155189248 memcontrol04.c:170: TPASS: Expect: (A/B memory.current=54173696) ~= 52428800 memcontrol04.c:176: TPASS: Expect: (A/B/C memory.current=30658560) ~= 34603008 memcontrol04.c:178: TPASS: Expect: (A/B/D memory.current=22560768) ~= 17825792 memcontrol04.c:180: TPASS: Expect: (A/B/E memory.current=0) ~= 0 memcontrol04.c:182: TINFO: A/B/F memory.current=942080 memcontrol04.c:99: TINFO: Child 119803 in trunk_G: Allocating anon: 174063616 memcontrol04.c:195: TINFO: A: low events=1617, oom events=0 memcontrol04.c:195: TINFO: B: low events=1617, oom events=0 memcontrol04.c:195: TINFO: G: low events=0, oom events=0 memcontrol04.c:208: TPASS: Expect: (C oom events=0) == 0 memcontrol04.c:211: TPASS: Expect: (C low events=406) > 0 memcontrol04.c:208: TPASS: Expect: (D oom events=0) == 0 memcontrol04.c:211: TPASS: Expect: (D low events=406) > 0 memcontrol04.c:208: TPASS: Expect: (E oom events=0) == 0 memcontrol04.c:214: TPASS: Expect: (E low events=0) == 0 memcontrol04.c:208: TPASS: Expect: (F oom events=0) == 0 memcontrol04.c:214: TFAIL: Expect: (F low events=403) == 0 tst_test.c:1528: TINFO: Testing on ext4 tst_test.c:996: TINFO: Formatting /dev/loop3 with ext4 opts='' extra opts='' mke2fs 1.46.5 (30-Dec-2021) tst_test.c:1456: TINFO: Timeout per run is 0h 05m 00s memcontrol04.c:118: TINFO: Child 119814 in leaf_C: Allocating pagecache: 52428800 memcontrol04.c:118: TINFO: Child 119815 in leaf_D: Allocating pagecache: 52428800 memcontrol04.c:1
[Kernel-packages] [Bug 1966422] [NEW] FTBFS during archive rebuild due to lack of singing tarballs
Public bug reported: We have stopped accepting singing tarballs into the archive, because we don't want to use wrong signing keys or produce duplicate/tripplicate signatures. (in the signing PPA, in -proposed, and in -updates/-security/-release as well potentially). This results in inability to rebuild linux-signed-* packages during full archive rebuilds. Opening this bug report to highlight this fact. ** Affects: linux-signed-aws (Ubuntu) Importance: Undecided Status: Triaged ** Affects: linux-signed-azure (Ubuntu) Importance: Undecided Status: Triaged ** Affects: linux-signed-gcp (Ubuntu) Importance: Undecided Status: Triaged ** Affects: linux-signed-kvm (Ubuntu) Importance: Undecided Status: Triaged ** Affects: linux-signed-lowlatency (Ubuntu) Importance: Undecided Status: Triaged ** Affects: linux-signed-oracle (Ubuntu) Importance: Undecided Status: Triaged ** Tags: ftbfs ** Also affects: linux-signed-azure (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-signed-gcp (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-signed-kvm (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-signed-lowlatency (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-signed-oracle (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-signed-aws (Ubuntu) Status: New => Triaged ** Changed in: linux-signed-azure (Ubuntu) Status: New => Triaged ** Changed in: linux-signed-gcp (Ubuntu) Status: New => Triaged ** Changed in: linux-signed-kvm (Ubuntu) Status: New => Triaged ** Changed in: linux-signed-lowlatency (Ubuntu) Status: New => Triaged ** Changed in: linux-signed-oracle (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-aws in Ubuntu. https://bugs.launchpad.net/bugs/1966422 Title: FTBFS during archive rebuild due to lack of singing tarballs Status in linux-signed-aws package in Ubuntu: Triaged Status in linux-signed-azure package in Ubuntu: Triaged Status in linux-signed-gcp package in Ubuntu: Triaged Status in linux-signed-kvm package in Ubuntu: Triaged Status in linux-signed-lowlatency package in Ubuntu: Triaged Status in linux-signed-oracle package in Ubuntu: Triaged Bug description: We have stopped accepting singing tarballs into the archive, because we don't want to use wrong signing keys or produce duplicate/tripplicate signatures. (in the signing PPA, in -proposed, and in -updates/-security/-release as well potentially). This results in inability to rebuild linux-signed-* packages during full archive rebuilds. Opening this bug report to highlight this fact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws/+bug/1966422/+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 1966417] 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 1966417 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/1966417 Title: memcontrol04 in ubuntu_ltp_controllers failed on J-azure (Low events in F) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on I-azure 5.15.0-1002.3 Test failed with: memcontrol04.c:214: TFAIL: Expect: (F low events=419) == 0 HINT: You _MAY_ be hit by known kernel failures: Low events in F: https://bugzilla.suse.com/show_bug.cgi?id=1196298 Test log: INFO: Test start time: Fri Mar 25 10:03:44 UTC 2022 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 119719 -n 119719 -f /tmp/ltp-mFNzOrxoBY/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_device.c:88: TINFO: Found free device 3 '/dev/loop3' tst_supported_fs_types.c:88: TINFO: Kernel supports ext2 tst_supported_fs_types.c:50: TINFO: mkfs.ext2 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext3 tst_supported_fs_types.c:50: TINFO: mkfs.ext3 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext4 tst_supported_fs_types.c:50: TINFO: mkfs.ext4 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports xfs tst_supported_fs_types.c:50: TINFO: mkfs.xfs does exist tst_supported_fs_types.c:88: TINFO: Kernel supports btrfs tst_supported_fs_types.c:50: TINFO: mkfs.btrfs does exist tst_supported_fs_types.c:155: TINFO: Skipping vfat as requested by the test tst_supported_fs_types.c:155: TINFO: Skipping exfat as requested by the test tst_supported_fs_types.c:155: TINFO: Skipping tmpfs as requested by the test tst_test.c:1528: TINFO: Testing on ext2 tst_test.c:996: TINFO: Formatting /dev/loop3 with ext2 opts='' extra opts='' mke2fs 1.46.5 (30-Dec-2021) tst_test.c:1456: TINFO: Timeout per run is 0h 05m 00s memcontrol04.c:118: TINFO: Child 119783 in leaf_C: Allocating pagecache: 52428800 memcontrol04.c:118: TINFO: Child 119785 in leaf_D: Allocating pagecache: 52428800 memcontrol04.c:118: TINFO: Child 119786 in leaf_F: Allocating pagecache: 52428800 memcontrol04.c:99: TINFO: Child 119787 in trunk_G: Allocating anon: 155189248 memcontrol04.c:170: TPASS: Expect: (A/B memory.current=54177792) ~= 52428800 memcontrol04.c:176: TPASS: Expect: (A/B/C memory.current=30691328) ~= 34603008 memcontrol04.c:178: TPASS: Expect: (A/B/D memory.current=22523904) ~= 17825792 memcontrol04.c:180: TPASS: Expect: (A/B/E memory.current=0) ~= 0 memcontrol04.c:182: TINFO: A/B/F memory.current=950272 memcontrol04.c:99: TINFO: Child 119788 in trunk_G: Allocating anon: 174063616 memcontrol04.c:195: TINFO: A: low events=1645, oom events=0 memcontrol04.c:195: TINFO: B: low events=1645, oom events=0 memcontrol04.c:195: TINFO: G: low events=0, oom events=0 memcontrol04.c:208: TPASS: Expect: (C oom events=0) == 0 memcontrol04.c:211: TPASS: Expect: (C low events=413) > 0 memcontrol04.c:208: TPASS: Expect: (D oom events=0) == 0 memcontrol04.c:211: TPASS: Expect: (D low events=413) > 0 memcontrol04.c:208: TPASS: Expect: (E oom events=0) == 0 memcontrol04.c:214: TPASS: Expect: (E low events=0) == 0 memcontrol04.c:208: TPASS: Expect: (F oom events=0) == 0 memcontrol04.c:214: TFAIL: Expect: (F low events=410) == 0 tst_test.c:1528: TINFO: Testing on ext3 tst_test.c:996: TINFO: Formatting /dev/loop3 with ext3 opts='' extra opts='' mke2fs 1.46.5 (30-Dec-2021) tst_test.c:1456: TINFO: Timeout per run is 0h 05m 00s memcontrol04.c:118: TINFO: Child 119798 in leaf_C: Allocating pagecache: 52428800 memcontrol04.c:118: TINFO: Child 119800 in leaf_D: Allocating pagecache: 52428800 memcontrol04.c:118: TINFO: Child 119801 in leaf_F: Allocating pagecache: 52428800 memcontrol04.c:99: TINFO: Child 119802 in trunk_G: Allocating anon: 155189248 memcontrol04.c:170: TPASS: Expect: (A/B memory.current=54173696) ~= 52428800 memcontrol04.c:176: TPASS: Expect: (A/B/C memory.current=30658560) ~= 34603008 memcontrol04.c:178: TPASS: Expect: (A/B/D memory.current=22560768) ~= 17825792 memcontrol04.c:180: TPASS: Expect: (A/B/E memory.current=0) ~= 0 memcontrol04.c:182: TINFO: A/B/F memory.current=942080 memcontrol04.c:99: TINFO: C
[Kernel-packages] [Bug 1966327] Re: external audio interface cracking sound
Hello, apart from upload more info with apport-collect mentioned above. Can you check if workaround in comment #9 of bug #1966066 works for you? Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966147] Re: 5.13.0-37.42 terrible sound via usb
Hello, apart from upload more info with apport-collect mentioned above (please do it with your USB sound card connected). Can you check if workaround in comment #9 of bug #1966066 works for you? Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966147 Title: 5.13.0-37.42 terrible sound via usb Status in linux package in Ubuntu: Incomplete Bug description: updated yesterday to kernel 5.13.0-37.42 and sound from usb is awfully distorted, while from bluetooth and hdmi is unaltered. reverted to 5.13.0-35.40 via grub and sound via usb is back to normal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966147/+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 1962349] Re: Bolt doesn't work with native USB4 hosts
Only reason was to avoid having to backport to both impish and focal when the version in impish is enough. -- 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/1962349 Title: Bolt doesn't work with native USB4 hosts Status in OEM Priority Project: New Status in bolt package in Ubuntu: Fix Released 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 bolt source package in Focal: In Progress Status in linux source package in Focal: Won't Fix 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 bolt source package in Impish: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released 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] * AMD Yellow Carp provides integrated USB4 host controllers * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] AMD Yellow Carp Host (issue this bug is about) -- * Plug in USB4 device or TBT3 to AMD Yellow Carp host * Ensure that PCI topology has populated * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" * Try to run `boltctl enroll $UUID` Alpine Ridge / Titan Ridge host (discrete controller) -- Start out on a host with discrete controller (Alpine Ridge or Titan Ridge) 1. sudo boltctl forget -a 2. Plug in dock 3. Make sure 'boltctl list' enumerates dock. 4. Check /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection (value dependent upon host) - If 0; try to manually enroll using 'boltctl enroll $UUID' - If 1; ensure that device automatically enrolled with bolt. GUI Check - Ensure that devices show up in the Settings GUI and are now able to authorize. Note: for AMD platforms enumerating PCIe devices is a separate problem from BOLT handled by kernel tasks. GUI check is only about "authorization". [Where problems could occur] * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. * There haven't been any significant bugs reported upstream or in Ubuntu since 0.9.1 release. [Other Info] * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. * It is fixed in bolt 0.9.1 or later release. * To solve the SRU, will backport 0.9.1 release from Impish. * I did look into backporting just the commit(s) for fixing this, but it's not a trivial backport. Quoting the changelog (https://gitlab.freedesktop.org/bolt/bolt/-/blob/master/CHANGELOG.md): "Additionally the unique_id of said host controller changes with every boot, which breaks one of the fundamental assumptions in boltd". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962349/+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 1966327] Re: external audio interface cracking sound
ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-11-20 (124 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Micro-Star International Co., Ltd. MS-7C37 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-37-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.187.29 Tags: focal Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker kismet lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/03/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.D1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MPG X570 GAMING PLUS (MS-7C37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.D1:bd03/03/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C37:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570GAMINGPLUS(MS-7C37):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C37 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Tags added: apport-collected 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/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1966327/+attachment/5572870/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1966327/+attachment/5572871/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1966327/+attachment/5572873/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1966327/+attachment/5572872/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1966327/+attachment/5572874/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1966327/+attachment/5572877/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1966327/+attachment/5572875/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1966327/+attachment/5572876/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1966327/+attachment/5572880/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1966327/+attachment/5572878/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1966327/+attachment/5572879/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1966327/+attachment/5572887/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1966327/+attachment/5572881/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1966327/+attachment/5572888/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1966327/+attachment/5572882/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] Re: external audio interface cracking sound
@Po-Hsu Lin (cypressyew) the workaround in bug #1966066 worked for me, symptoms are the same I think this is a duplicate. I changed at /etc/pulse/daemon.conf ``` default-sample-rate = 48000 alternate-sample-rate = 48000 ``` -- 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/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1966327/+attachment/5572889/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1966327/+attachment/5572883/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1966327/+attachment/5572884/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1966327/+attachment/5572886/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966327] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1966327/+attachment/5572885/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966327 Title: external audio interface cracking sound Status in linux package in Ubuntu: Incomplete Bug description: after a recent kernel update, my KRK Rokit 5 speakers connected to the Behringer U-PHORIA UMC22 started to emit strange clicking sound artifacts. nothing like this happened before the last update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966327/+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 1966143] Re: Periodic glitch in LogiTech H390 headphone audio
Hello, Can you attach the "lsusb -v" output with your headset connected? Also, can you check if workaround in comment #9 of bug #1966066 works for you? Thanks. ** Changed in: linux-signed-hwe-5.13 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1966143 Title: Periodic glitch in LogiTech H390 headphone audio Status in linux-signed-hwe-5.13 package in Ubuntu: Incomplete Bug description: When running kernel version 5.13.0-37-generic the audio output through my Logitech H390 headphones has a periodic "glitch" every few seconds - noticable in Google Meetings and Youtube - its very distracting, its not exactly a scratch or pop; it's more like a really bad reception mobile phone call "robot voice" noise but lasts only for a moment, then maybe 30 seconds later occurs again, seems to be regularly periodic. The problem isn't present on 5.13.0-35-generic and doesn't effect my external speaker audio output just the headphones so it's not a network issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Mar 24 10:26:12 2022 InstallationDate: Installed on 2018-02-17 (1495 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: Upgraded to focal on 2020-05-08 (684 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966143/+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 1966147] Re: 5.13.0-37.42 terrible sound via usb
Hi Po-Hsu Lin, Thank you for your direction. I'll do it this evening after work (I need to restart my pc to load the affected kernel). Would it be useful at all to have apport-collect from both kernels (good sound vs bad sound)? -- 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/1966147 Title: 5.13.0-37.42 terrible sound via usb Status in linux package in Ubuntu: Incomplete Bug description: updated yesterday to kernel 5.13.0-37.42 and sound from usb is awfully distorted, while from bluetooth and hdmi is unaltered. reverted to 5.13.0-35.40 via grub and sound via usb is back to normal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966147/+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 1966066] Re: audio from external sound card is distorted
Workaround fixed it for me, same symptoms rolling back to 5.13.0-35 is fine, 5.13.0-37 has the issue. @~magen you need to use sudo to elevate your access sudo nano /etc/pulse/daemon.conf Find the line with default-sample-rate Remove the ; and change the value to 48000, do the same for alternate- sample-rate so it will look like: default-sample-rate = 48000 alternate-sample-rate = 48000 Press CTRL + X to save and exit. Then run pulseaudio -k to restart your audio. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1966066 Title: audio from external sound card is distorted Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: The sound card is a Focusrite Scarlett 2i2. The sound is distorted everywhere. Sound via HDMI works. Seen others having the same problem: (Edit because of previously wrong link here) https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card ubuntu release: Ubuntu 20.04.4 LTS package name involved in bug: linux-image-5.13.0-37-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 12:56:02 2022 InstallationDate: Installed on 2020-12-18 (459 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966066/+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 1786013] Autopkgtest regression report (linux-meta-hwe-5.4/5.4.0.106.120~18.04.91)
All autopkgtests for the newly accepted linux-meta-hwe-5.4 (5.4.0.106.120~18.04.91) for bionic have finished running. The following regressions have been reported in tests triggered by the package: acpi-call/1.1.0-4 (ppc64el, s390x) v4l2loopback/0.10.0-1ubuntu1.2 (s390x) asic0x/1.0.1-1 (s390x) lxc/3.0.3-0ubuntu1~18.04.1 (ppc64el, s390x, amd64) virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) glibc/2.27-3ubuntu1.5 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-hwe-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966436] [NEW] Bluetooth fails to connect "br-connection-profile-unavailable"
Public bug reported: How to reproduce: > bluetoothctl scan on Discovery started ... > bluetoothctl connect 94:DB:56:8E:0B:96 Attempting to connect to 94:DB:56:8E:0B:96 Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable > systemctl status bluetooth bluetooth.service - Bluetooth service Loaded: loaded ... mars 25 12:39:08 ncelrnd2375 bluetoothd[1282]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 94:DB:56:8E:0B:96: Protocol not available Notes: kernel-5.15, bluez-5.64 Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth Dell Precision 3560 Unfortunately I did not test before upgrade to 22.04. Tried installing pipewire-pulse, blueman, but this is lower-level. There are reports of similar errors popping up in Arch and Manjaro recently: https://bbs.archlinux.org/viewtopic.php?id=270465 https://forum.manjaro.org/t/bluetooth-ko-with-kernel-5-16/99913 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Mar 25 12:56:34 2022 InstallationDate: Installed on 2022-03-04 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision 3560 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/AmadeUbuntu20-root ro audit=1 acpi_rev_override load_nvme=YES nouveau.modeset=0 dis_ucode_ldr quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-03-22 (3 days ago) dmi.bios.date: 09/13/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.2 dmi.board.name: 095HH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.2:bd09/13/2021:br1.12:svnDellInc.:pnPrecision3560:pvr:rvnDellInc.:rn095HH7:rvrA00:cvnDellInc.:ct10:cvr:sku0A22: dmi.product.family: Precision dmi.product.name: Precision 3560 dmi.product.sku: 0A22 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 44:E5:17:BC:00:DD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:24189 acl:41 sco:0 events:519 errors:0 TX bytes:8252 acl:33 sco:0 commands:239 errors:0 modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1966436 Title: Bluetooth fails to connect "br-connection-profile-unavailable" Status in bluez package in Ubuntu: New Bug description: How to reproduce: > bluetoothctl scan on Discovery started ... > bluetoothctl connect 94:DB:56:8E:0B:96 Attempting to connect to 94:DB:56:8E:0B:96 Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable > systemctl status bluetooth bluetooth.service - Bluetooth service Loaded: loaded ... mars 25 12:39:08 ncelrnd2375 bluetoothd[1282]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 94:DB:56:8E:0B:96: Protocol not available Notes: kernel-5.15, bluez-5.64 Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth Dell Precision 3560 Unfortunately I did not test before upgrade to 22.04. Tried installing pipewire-pulse, blueman, but this is lower-level. There are reports of similar errors popping up in Arch and Manjaro recently: https://bbs.archlinux.org/viewtopic.php?id=270465 https://forum.manjaro.org/t/bluetooth-ko-with-kernel-5-16/99913 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Mar 25 12:56:34 2022 InstallationDate: Installed on 2022-03-04 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision 3560 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/AmadeUbuntu20-root ro audit=1 acpi_rev_override load_nvme=YES nouveau.modeset=0 dis_ucode_ldr quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-03-22 (3 days ago) dmi.bios.date: 09/13/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.2 dmi.board.name: 095HH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1966436] Re: Bluetooth fails to connect "br-connection-profile-unavailable"
I found recent bugs but: * this is not the same adapter as #1960448 * not same adapter as #1960377 and I'm running 5.15.0-23-generic which is supposed to have the fix mentioned. -- 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/1966436 Title: Bluetooth fails to connect "br-connection-profile-unavailable" Status in bluez package in Ubuntu: New Bug description: How to reproduce: > bluetoothctl scan on Discovery started ... > bluetoothctl connect 94:DB:56:8E:0B:96 Attempting to connect to 94:DB:56:8E:0B:96 Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable > systemctl status bluetooth bluetooth.service - Bluetooth service Loaded: loaded ... mars 25 12:39:08 ncelrnd2375 bluetoothd[1282]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 94:DB:56:8E:0B:96: Protocol not available Notes: kernel-5.15, bluez-5.64 Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth Dell Precision 3560 Unfortunately I did not test before upgrade to 22.04. Tried installing pipewire-pulse, blueman, but this is lower-level. There are reports of similar errors popping up in Arch and Manjaro recently: https://bbs.archlinux.org/viewtopic.php?id=270465 https://forum.manjaro.org/t/bluetooth-ko-with-kernel-5-16/99913 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Mar 25 12:56:34 2022 InstallationDate: Installed on 2022-03-04 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision 3560 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/AmadeUbuntu20-root ro audit=1 acpi_rev_override load_nvme=YES nouveau.modeset=0 dis_ucode_ldr quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-03-22 (3 days ago) dmi.bios.date: 09/13/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.2 dmi.board.name: 095HH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.2:bd09/13/2021:br1.12:svnDellInc.:pnPrecision3560:pvr:rvnDellInc.:rn095HH7:rvrA00:cvnDellInc.:ct10:cvr:sku0A22: dmi.product.family: Precision dmi.product.name: Precision 3560 dmi.product.sku: 0A22 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 44:E5:17:BC:00:DD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:24189 acl:41 sco:0 events:519 errors:0 TX bytes:8252 acl:33 sco:0 commands:239 errors:0 modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1966436/+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 1966093] Re: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-510 into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-510/510.60.02-0ubuntu0.21.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-510 (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1966093 Title: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Committed Status in linux-restricted-modules source package in Bionic: Triaged Status in nvidia-graphics-drivers-390 source package in Bionic: In Progress Status in nvidia-graphics-drivers-510 source package in Bionic: In Progress Status in linux-restricted-modules source package in Focal: Triaged Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-510 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Impish: Triaged Status in nvidia-graphics-drivers-390 source package in Impish: In Progress Status in nvidia-graphics-drivers-510 source package in Impish: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] === 510 impish/focal/bionic === * New upstream release (LP: #1966093): - Added support for the following GPUs: NVIDIA RTX A4000H NVIDIA RTX A5500 - Fixed a bug that could cause displays with HDMI or DisplayPort audio to be deselected as the default audio output device after resuming from suspend. - Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT- switches - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:" in /proc/driver/nvidia/gpus//information to be "Unknown" for some GPUs. === 390 impish/focal/bionic === * New upstream release (LP: #1966093): - Fixed a bug where vkCreateSwapchain could cause the X Server to crash when an invalid imageFormat was provided. - Fixed a driver installation failure on Linux kernel 5.11 release candidates, where the NVIDIA kernel module failed to build with error "fatal error: asm/kmap_types.h: No such file or directory". [ Dimitri John Ledkov ] * debian/dkms_nvidia/patches/buildfix_kernel_5.13_armhf.patch: - Fix armhf builds. * debian/dkms_nvidia/patches/buildfix_kernel_5.17.patch: - Fix build failure with Linux 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restrict
[Kernel-packages] [Bug 1960633] Re: Move virtual graphics drivers from linux-modules-extra to linux-modules
This bug is awaiting verification that the linux-
hwe-5.4/5.4.0-107.121~18.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-bionic' to
'verification-done-bionic'. If the problem still exists, change the tag
'verification-needed-bionic' to 'verification-failed-bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-bionic
--
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/1960633
Title:
Move virtual graphics drivers from linux-modules-extra to linux-
modules
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
Fix Released
Bug description:
[SRU justification]
Impact: We split the drivers into linux-modules and linux-modules-extra. The
latter is only included for setups geared towards real hardware (desktops,
laptops). For VM guests the recommended setup is to use linux-virtual which
does not include linux-modules-extra but also does not depend on other
packages, like linux-firmware.
We already include most VM related drivers in the linux-modules package and
vboxvideo (since 21.10/Impish). So it makes sense to include the missing ones.
Fix: Move the following modules from linux-modules-extra into linux-modules:
- bochs-drm (though a bit aged, this was the predecessor of qemu)
- cirrus (this is a standard emulated gfx card, might not give the best
performance but better than nothing)
- virtio-gpu (KVM)
- vmwgfx (VMWare)
- drm-xen-front (Xen)
Testcase: Check linux-modules for the mentioned modules.
Regression Potential: There should be no change noticeable. Users with
linux-modules-extra installed will see no difference and those without
have additional drivers. Maybe this shows as moving from low-
resolution graphics to higher ones which maybe perform less.
--- Original Description ---
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains
kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko, so at the moment I need to
keep it installed and updated. The only way to do so conveniently is
to install linux-image-generic, which also pulls in linux-firmware,
which is ~760MB installed.
If vmwgfx was moved from linux-modules-extra to linux-modules, I could
use linux-image-virtual instead of linux-image-generic, remove linux-
firmware, linux-modules-extra, and the microcode packages, saving
substantial disk space and bandwidth.
Other virtual graphics drivers in linux-modules-extra that might be
worth moving are:
kernel/drivers/gpu/drm/bochs/bochs-drm.ko
kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
kernel/drivers/gpu/drm/xen/drm_xen_front.ko
Thank you for your consideration.
Note: Edited significantly in response to
https://lists.ubuntu.com/archives/kernel-
team/2022-February/128103.html and
https://lists.ubuntu.com/archives/kernel-
team/2022-February/128104.html to better reflect the underlying
problem and solution.
P.S. There are three other drivers in linux-modules-extra that seem
VMWare-related, but they are not in use in my VM and I don't know
whether they are in common enough use to justify moving them to linux-
modules. I have listed them here for completeness.
kernel/drivers/net/vsockmon.ko
kernel/drivers/ptp/ptp_vmw.ko
kernel/drivers/infiniband/hw/vmw_pvrdma/vmw_pvrdma.ko
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Por
[Kernel-packages] [Bug 1943301] Re: 【sec-0911】 fail to reset sec module
This bug is awaiting verification that the linux- hwe-5.4/5.4.0-107.121~18.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1943301 Title: 【sec-0911】 fail to reset sec module Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [Impact] The crypto accelerator in Hi1620 SoC can not be reset. [Test Plan] 1) echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.1/reset 2) echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.0/reset 3) busybox devmem 0x200141B01018 32 0x1 4) dmesg | grep "FLR resetting" [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] [Steps to Reproduce] 1、echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.1/reset 2、echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.0/reset 3、busybox devmem 0x200141B01018 32 0x1, [Actual Results] root@root:~# busybox devmem 0x200141B01018 32 0x1 root@root:~# dmesg root@root:~# [Expected Results] reset ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): OS: ubuntu 20.04.2 DRV（driver version）: vermagic: 5.8.0-59-generic SMP mod_unload aarch64 [Resolution] [v2,3/5] crypto: hisilicon/sec2 - update SEC initialization and reset 此patch未合入 https://patchwork.kernel.org/project/linux-crypto/patch/1594084541-22177-4-git-send-email-liulongf...@huawei.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1943301/+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 1966093] Re: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-510 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-510/510.60.02-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-510 (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal ** Changed in: nvidia-graphics-drivers-510 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1966093 Title: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Committed Status in linux-restricted-modules source package in Bionic: Triaged Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Focal: Triaged Status in nvidia-graphics-drivers-390 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-510 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Impish: Triaged Status in nvidia-graphics-drivers-390 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-510 source package in Impish: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] === 510 impish/focal/bionic === * New upstream release (LP: #1966093): - Added support for the following GPUs: NVIDIA RTX A4000H NVIDIA RTX A5500 - Fixed a bug that could cause displays with HDMI or DisplayPort audio to be deselected as the default audio output device after resuming from suspend. - Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT- switches - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:" in /proc/driver/nvidia/gpus//information to be "Unknown" for some GPUs. === 390 impish/focal/bionic === * New upstream release (LP: #1966093): - Fixed a bug where vkCreateSwapchain could cause the X Server to crash when an invalid imageFormat was provided. - Fixed a driver installation failure on Linux kernel 5.11 release candidates, where the NVIDIA kernel module failed to build with error "fatal error: asm/kmap_types.h: No such file or directory". [ Dimitri John Ledkov ] * debian/dkms_nvidia/patches/buildfix_kernel_5.13_armhf.patch: - Fix armhf builds. * debian/dkms_nvidia/patches/buildfix_kernel_5.17.patch: - Fix build
[Kernel-packages] [Bug 1962578] Re: [UBUNTU 20.04] Fix SIGP processing on KVM/s390
This bug is awaiting verification that the linux- hwe-5.4/5.4.0-107.121~18.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1962578 Title: [UBUNTU 20.04] Fix SIGP processing on KVM/s390 Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification: == [Impact] * The SIGP processing on KVM/s390x is incorrect and not fully conform to the 'Principles of Operations', the IBM Z architecture definition and documentation. * KVM: SIGP RESTART is reporting a CPU state 'stopped' after SIGP RESTART was issued, while it should report a 'busy' condition until the CPU is really started. * The fix for this consists of three patches: 812de04661c4 "KVM: s390: Clarify SIGP orders versus STOP/RESTART" 435d17955519 "KVM: s390: Add a routine for setting userspace CPU state" 4563bcad46bf "KVM: s390: Simplify SIGP Set Arch handling" whereas 812de04661c4 already landed via upstream stable, hence only two are left and need to be cherry-picked: [Fix] * 67cf68b6a5ccac8bc7dfef0a220b59af4c83fd2c 67cf68b6a5cc "KVM: s390: Add a routine for setting userspace CPU state" * 8eeba194a32e0f50329354a696baaa2e3d9accc5 8eeba194a32e "KVM: s390: Simplify SIGP Set Arch handling" [Test Case] * Install an LPAR on IBM Z (z13+) or LinuxONE (Emperor / Rockhopper) with Ubuntu Server 20.04 using kernel standard kernel 5.4. * Setup this LPAR as QEMU/KVM host and a focal VM as guest. * The test itself is the following unit test: https://lore.kernel.org/r/20220303210425.1693486-1-far...@linux.ibm.com/ * The test and verification will be done by the IBM Z team. [Where problems could occur] * A broken patch could harm KVM ioctl on s390x or the (virtual) CPU state control in general. * The SIGP handing (on s390x) can become broken, which could lead to incorrect (virtual) CPU states. * In worst case KVM can become broken on s390x entirely. * The modified code is all s390x specific QEMU/KVM code, no common code is touched. [Other] * The two remaining patches are upstream since 5.16, the first one already landed in 5.4 via upstream stable bug LP#1959701 and in 5.13 via upstream stable bug LP#1960861. * The patches already landed in jammy (master-next) based on LP#1959735, hence only SRU to impish and focal is needed. * This patches got discussed here: https://lore.kernel.org/all/20211008203112.1979843-2-far...@linux.ibm.com/ * This not only fixes the SIGP processing, but is also important in terms of long term maintainability. __ Description: KVM: SIGP RESTART is reporting a CPU state 'stopped' after SIGP RESTART was issued, while it should report a 'busy' condition until the CPU is really started. The patches to fix this have already been picked for jammy/master- next: 812de04661c4 "KVM: s390: Clarify SIGP orders versus STOP/RESTART" 435d17955519 "KVM: s390: Add a routine for setting userspace CPU state" 4563bcad46bf "KVM: s390: Simplify SIGP Set Arch handling" For Ubuntu 20.04 the focal/master-next already contains: d74b0d2d38d3 KVM: s390: Clarify SIGP orders versus STOP/RESTART so we additionally need the following two upstream commits in focal 67cf68b6a5cc KVM: s390: Add a routine for setting userspace CPU state 8eeba194a32e KVM: s390: Simplify SIGP Set Arch handling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1962578/+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 1966093] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-510 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-510/510.60.02-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1966093 Title: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Committed Status in linux-restricted-modules source package in Bionic: Triaged Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Focal: Triaged Status in nvidia-graphics-drivers-390 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-510 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Impish: Triaged Status in nvidia-graphics-drivers-390 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-510 source package in Impish: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] === 510 impish/focal/bionic === * New upstream release (LP: #1966093): - Added support for the following GPUs: NVIDIA RTX A4000H NVIDIA RTX A5500 - Fixed a bug that could cause displays with HDMI or DisplayPort audio to be deselected as the default audio output device after resuming from suspend. - Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT- switches - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:" in /proc/driver/nvidia/gpus//information to be "Unknown" for some GPUs. === 390 impish/focal/bionic === * New upstream release (LP: #1966093): - Fixed a bug where vkCreateSwapchain could cause the X Server to crash when an invalid imageFormat was provided. - Fixed a driver installation failure on Linux kernel 5.11 release candidates, where the NVIDIA kernel module failed to build with error "fatal error: asm/kmap_types.h: No such file or directory". [ Dimitri John Ledkov ] * debian/dkms_nvidia/patches/buildfix_kernel_5.13_armhf.patch: - Fix armhf builds. * debian/dkms_nvidia/patches/buildfix_kernel_5.17.patch: - Fix build failure with Linux 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1966093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe
[Kernel-packages] [Bug 1966093] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-390 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-390/390.147-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1966093 Title: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Committed Status in linux-restricted-modules source package in Bionic: Triaged Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Focal: Triaged Status in nvidia-graphics-drivers-390 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-510 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Impish: Triaged Status in nvidia-graphics-drivers-390 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-510 source package in Impish: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] === 510 impish/focal/bionic === * New upstream release (LP: #1966093): - Added support for the following GPUs: NVIDIA RTX A4000H NVIDIA RTX A5500 - Fixed a bug that could cause displays with HDMI or DisplayPort audio to be deselected as the default audio output device after resuming from suspend. - Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT- switches - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:" in /proc/driver/nvidia/gpus//information to be "Unknown" for some GPUs. === 390 impish/focal/bionic === * New upstream release (LP: #1966093): - Fixed a bug where vkCreateSwapchain could cause the X Server to crash when an invalid imageFormat was provided. - Fixed a driver installation failure on Linux kernel 5.11 release candidates, where the NVIDIA kernel module failed to build with error "fatal error: asm/kmap_types.h: No such file or directory". [ Dimitri John Ledkov ] * debian/dkms_nvidia/patches/buildfix_kernel_5.13_armhf.patch: - Fix armhf builds. * debian/dkms_nvidia/patches/buildfix_kernel_5.17.patch: - Fix build failure with Linux 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1966093/+subscriptions -- Mailing list: ht
[Kernel-packages] [Bug 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
This bug is awaiting verification that the linux- hwe-5.4/5.4.0-107.121~18.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Impact] hisi_qm does not clean up kernel process after calculation is done. Many zombie processes slow down system. After checkbox cpu stress test, it takes more then 2min to ssh in. [Test Plan] 1) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 2) ps aux | grep hisi_qm | wc -l Expected result is less then 100 [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+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 1966093] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-390 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-390/390.147-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1966093 Title: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Committed Status in linux-restricted-modules source package in Bionic: Triaged Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Focal: Triaged Status in nvidia-graphics-drivers-390 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-510 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Impish: Triaged Status in nvidia-graphics-drivers-390 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-510 source package in Impish: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] === 510 impish/focal/bionic === * New upstream release (LP: #1966093): - Added support for the following GPUs: NVIDIA RTX A4000H NVIDIA RTX A5500 - Fixed a bug that could cause displays with HDMI or DisplayPort audio to be deselected as the default audio output device after resuming from suspend. - Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT- switches - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:" in /proc/driver/nvidia/gpus//information to be "Unknown" for some GPUs. === 390 impish/focal/bionic === * New upstream release (LP: #1966093): - Fixed a bug where vkCreateSwapchain could cause the X Server to crash when an invalid imageFormat was provided. - Fixed a driver installation failure on Linux kernel 5.11 release candidates, where the NVIDIA kernel module failed to build with error "fatal error: asm/kmap_types.h: No such file or directory". [ Dimitri John Ledkov ] * debian/dkms_nvidia/patches/buildfix_kernel_5.13_armhf.patch: - Fix armhf builds. * debian/dkms_nvidia/patches/buildfix_kernel_5.17.patch: - Fix build failure with Linux 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1966093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1964512] Re: Low RX performance for 40G Solarflare NICs
This bug is awaiting verification that the linux- hwe-5.4/5.4.0-107.121~18.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1964512 Title: Low RX performance for 40G Solarflare NICs Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] * Some 40G Solarflare NICs have low RX performance in some cases, due low RX recycle ring size * RX recycle ring size is either 4096 for IOMMU, 16 for NOIOMMU * The low fixed sizes can cause a high number of calls to alloc_pages, tanking performance for higher link speeds [Test Plan] * Users report that iperf3 is sufficient to showcase the bad RX performance * For some setups, RX performance was around 15Gbps while TX stayed consistently above 30Gbps [Fix] * This patch sets the RX recycle ring size according to an adapter's maximum link speed * Fix was introduced by commit: 000fe940e51f "sfc: The size of the RX recycle ring should be more flexible" * --!-- Commit is from net-next --!-- [Regression Potential] * Regressions would show primarily as performance issues, as we're effectively changing ring sizes for all RX traffic * It's possible to see increased calls to alloc_pages if ring sizes aren't being set correctly * We should look out for excessive memory usage in the sfc driver due to the increased ring sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964512/+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 1962831] Re: [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
This bug was opened for focal, bionic was not really requested and is not marked as affected, so I'm setting the verification-done-bionic tag to unblock further SRU processing. ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1962831 Title: [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: SRU Justification: == [Impact] * KVM uses lazy storage key enablement as Linux does no longer make use of the storage keys. When the guest enters keyed mode, then KVM will save/restore the key during paging, provide change/reference tracking for guest and host and for all interpreted instructions will do key protection. * If an instruction is intercepted and passed along to userspace (like QEMU) no storage key protection is checked, though. * But this is in violation of the architecture and it can result in misbehaving guests that rely on key protection for all instructions. * This item will improve the MEMOP ioctl to also add key checking. In case of a key protection the right fault is injected in the guest. [Fix] * The following changes since commit dbdbd581976f9dfcc9e21a777273b55bdb9bf138: UBUNTU: Ubuntu-5.4.0-102.115 (2022-02-23 15:32:05 +0100) are available in the Git repository at: https://git.launchpad.net/~fheimes/+git/lp1962831/ 16c0809cf1012e68279a8936a482c1d63cc4d14c for you to fetch changes up to 16c0809cf1012e68279a8936a482c1d63cc4d14c: KVM: s390: Add missing vm MEM_OP size check (2022-03-03 22:45:50 +0100) * Patches are upstream accepted (but some are as of today still in linux-next). * Notes on why the backports are needed are included in the provenance of the corresponding commit. [Test Case] * An IBM z13 or LinuxONE system is needed running Ubuntu Server 20.04 with QEMU/KVM setup. * These modification here are covered by the following three tests: * [kvm-unit-tests,v2] s390x: Test effect of storage keys on some instructions https://patchwork.kernel.org/project/kvm/patch/20220301095059.3026178-1-s...@linux.ibm.com/ * [PATCH v2 0/5] memop selftest for storage key checking https://lore.kernel.org/kvm/20220225155311.3540514-1-s...@linux.ibm.com/ * c7ef9ebbed20 "KVM: s390: selftests: Test TEST PROTECTION emulation" * The tests and the verification will be done by the IBM Z team. * On top a test build is available (see below). [Where problems could occur] * Issues with vm ioctl may occur due to the introduction of _vm_ioctl. * Tests may fail or may report wrong states due to the new TEST_FAIL macro in tests/utilities or due to new variants of GUEST_ASSERT in selftests. * Problems on gaccess might be caused due to the refactoring of gpa, length calculation, access address range check and the new access_guest_page helper function. * In uaccess issues may occur due to the introduction of the bit field for OAC specifier, that causes lot's but relatively straight forward changes or due to the new storage key checking functions copy_from/to_user_key functions. * Compile issues may happen if the changes in uaccess.h bout z10 features are erroneous. * Instructions that are emulated by KVM might be impacted due to the expanded storage key checking, that now covers intercepted instructions, too. This is the most significant modification in terms of size and complexity and therefore carries the highest risk. * MEM_OP IOCTL could be harmed due to the additional, but optional, storage key extension and checking, or the new size check and I/O emulation can be impacted due to the new vm IOCTL for key checked guest memory access. * Some tests were added to mitigate this, like the selftests TEST PROTECTION. * The renaming of the existing vcpu memop functions shouldn't be very harmful, since issues will already occur test build. * The rest are API documentation updates and clarifications. * Except two include/header changes and changes in tools/testing all other modifications are s390x specific [Other] * It was ensured that these changes are in jammy based on LP#1933179. __ Description: KVM uses lazy storage key enablement as Linux does no longer make use of the storage keys. When the guest enters keyed mode, then KVM will save/restore the key during paging, provide change/reference tracking for guest and host and for all interpreted instructions will do key protection. If an instruction is intercepted and passed along to userspace (like QEMU) no storage key protection is checked, thou
[Kernel-packages] [Bug 1962578] Re: [UBUNTU 20.04] Fix SIGP processing on KVM/s390
This bug was opened for focal and impish, bionic was not really requested and is not marked as affected, so I'm setting the verification-done-bionic tag to unblock further SRU processing. ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1962578 Title: [UBUNTU 20.04] Fix SIGP processing on KVM/s390 Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification: == [Impact] * The SIGP processing on KVM/s390x is incorrect and not fully conform to the 'Principles of Operations', the IBM Z architecture definition and documentation. * KVM: SIGP RESTART is reporting a CPU state 'stopped' after SIGP RESTART was issued, while it should report a 'busy' condition until the CPU is really started. * The fix for this consists of three patches: 812de04661c4 "KVM: s390: Clarify SIGP orders versus STOP/RESTART" 435d17955519 "KVM: s390: Add a routine for setting userspace CPU state" 4563bcad46bf "KVM: s390: Simplify SIGP Set Arch handling" whereas 812de04661c4 already landed via upstream stable, hence only two are left and need to be cherry-picked: [Fix] * 67cf68b6a5ccac8bc7dfef0a220b59af4c83fd2c 67cf68b6a5cc "KVM: s390: Add a routine for setting userspace CPU state" * 8eeba194a32e0f50329354a696baaa2e3d9accc5 8eeba194a32e "KVM: s390: Simplify SIGP Set Arch handling" [Test Case] * Install an LPAR on IBM Z (z13+) or LinuxONE (Emperor / Rockhopper) with Ubuntu Server 20.04 using kernel standard kernel 5.4. * Setup this LPAR as QEMU/KVM host and a focal VM as guest. * The test itself is the following unit test: https://lore.kernel.org/r/20220303210425.1693486-1-far...@linux.ibm.com/ * The test and verification will be done by the IBM Z team. [Where problems could occur] * A broken patch could harm KVM ioctl on s390x or the (virtual) CPU state control in general. * The SIGP handing (on s390x) can become broken, which could lead to incorrect (virtual) CPU states. * In worst case KVM can become broken on s390x entirely. * The modified code is all s390x specific QEMU/KVM code, no common code is touched. [Other] * The two remaining patches are upstream since 5.16, the first one already landed in 5.4 via upstream stable bug LP#1959701 and in 5.13 via upstream stable bug LP#1960861. * The patches already landed in jammy (master-next) based on LP#1959735, hence only SRU to impish and focal is needed. * This patches got discussed here: https://lore.kernel.org/all/20211008203112.1979843-2-far...@linux.ibm.com/ * This not only fixes the SIGP processing, but is also important in terms of long term maintainability. __ Description: KVM: SIGP RESTART is reporting a CPU state 'stopped' after SIGP RESTART was issued, while it should report a 'busy' condition until the CPU is really started. The patches to fix this have already been picked for jammy/master- next: 812de04661c4 "KVM: s390: Clarify SIGP orders versus STOP/RESTART" 435d17955519 "KVM: s390: Add a routine for setting userspace CPU state" 4563bcad46bf "KVM: s390: Simplify SIGP Set Arch handling" For Ubuntu 20.04 the focal/master-next already contains: d74b0d2d38d3 KVM: s390: Clarify SIGP orders versus STOP/RESTART so we additionally need the following two upstream commits in focal 67cf68b6a5cc KVM: s390: Add a routine for setting userspace CPU state 8eeba194a32e KVM: s390: Simplify SIGP Set Arch handling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1962578/+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 1956760] Re: xHCI (xhci_hcd) host controller not working after unattended kernel upgrade
I can confirm that now, with the latest updates, I cannot reproduce the problem. -- 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/1956760 Title: xHCI (xhci_hcd) host controller not working after unattended kernel upgrade Status in linux package in Ubuntu: Confirmed Bug description: After the unattended-upgrade on January 5th (i.e. 5.4.0-92.103~18.04.2, automatic), the xHCI (xhci_hcd) host controller stopped working (i.e. no USB device is working): ===>dmesg log: linux1804 kernel: xhci_hcd :00:14.0: Abort failed to stop command ring: -110 linux1804 kernel: xhci_hcd :00:14.0: xHCI host controller not responding, assume dead linux1804 kernel: xhci_hcd :00:14.0: HC died; cleaning up linux1804 kernel: xhci_hcd :00:14.0: Timeout while waiting for setup device command linux1804 kernel: usb 4-1: device not accepting address 2, error -108 linux1804 kernel: usb usb4-port1: couldn't allocate usb_device linux1804 kernel: usb usb3-port1: couldn't allocate usb_device ===>unattended-upgrade info: Start-Date: 2022-01-05 11:08:54 Commandline: /usr/bin/unattended-upgrade Install: linux-image-5.4.0-92-generic:amd64 (5.4.0-92.103~18.04.2, automatic), linux-modules- extra-5.4.0-92-generic:amd64 (5.4.0-92.103~18.04.2, automatic), linux-headers-5.4.0-92 -generic:amd64 (5.4.0-92.103~18.04.2, automatic), linux-hwe-5.4-headers-5.4.0-92:amd64 (5.4.0-92.103~18.04.2, automatic), linux-modules-5.4.0-92-generic:amd64 (5.4.0-92.103~18.04.2, automatic) Upgrade: linux-headers-generic-hwe-18.04:amd64 (5.4.0.91.102~18.04.81, 5.4.0.92.103~18.04.82), linux-image-generic-hwe-18.04:amd64 (5.4.0.91.102~18.04.81, 5.4.0.92.103~18.04.82), linux-generic-hwe-18.04:amd64 (5.4.0.91.102~18.04.81, 5.4.0.92.103~18.04.82) End-Date: 2022-01-05 11:09:29 ===>lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 ===>Workaround: This happens on any boot after power off. If I restart the computer, the problem is not reproducible. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2060 F pulseaudio igoretov 8697 F pulseaudio /dev/snd/controlC0: gdm2060 F pulseaudio igoretov 8697 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-15 (913 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. N551JW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=446babcc-3c36-4899-ac47-f721db732d2a ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-92.103~18.04.2-generic 5.4.157 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.173.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.4.0-92-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N551JW.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N551JW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN551JW.202:bd01/16/2015:svnASUSTeKCOMPUTERINC.:pnN551JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N551JW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956760/+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 1966125] Re: Suspend (to ram) fails after upgrade from 5.13.0-35-generic to 5.13.0-37-generic
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.13 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1966125 Title: Suspend (to ram) fails after upgrade from 5.13.0-35-generic to 5.13.0-37-generic Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: As stated in the summary, my PC can't suspend anymore after kernel upgrade. When I click suspend from desktop: - The screen gets blank - (sometimes) Screen then shows up for a short time, then gets blank again - Now PC ist "dead", no reaction an keyboard, mouse and so on. - Even a CTR-ALT-DEL didn't show any reaction. - There is still some activity (HD-Led flashing) - The PC is "reachable" via network, but trying to ssh into it will not work (no response after entering password) - I have to reboot, either by power the PC off by pressing the power button longer or by using "Magic SysRq" keyboard sequence When I rollback (I use systemback) to Kernel 5.13.0-35-generic suspend works! # Information needed as directed by https://wiki.ubuntu.com/DebuggingKernelSuspend) # = $cat /proc/acpi/wakeup DeviceS-state Status Sysfs node GPP0S4*enabled pci::00:01.1 GP12S4*enabled pci::00:07.1 GP13S4*enabled pci::00:08.1 XHC0S4*enabled pci::0e:00.3 GP30S4*disabled GP31S4*disabled PS2KS3*disabled GPP2S4*disabled GPP3S4*disabled GPP8S4*enabled pci::00:03.1 SWUSS4*enabled pci::0a:00.0 SWDSS4*enabled pci::0b:00.0 GPP1S4*enabled pci::00:01.2 = sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" ... after power up again ... dmesg | grep -e "Magic number" -e "hash matches" [3.141067] PM: Magic number: 0:247:389 [3.145394] PM: hash matches drivers/base/power/main.c:982 [3.149741] thermal cooling_device4: hash matches = sudo su echo freezer > /sys/power/pm_test exit sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" ... promt is back after a few seconds again ... dmesg | grep -e "Magic number" -e "hash matches" [3.142991] PM: Magic number: 14:995:344 [3.147383] tty tty61: hash matches [3.151721] acpi ACPI0007:06: hash matches = sudo su echo devices > /sys/power/pm_test exit sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" ... after power up again ... dmesg | grep -e "Magic number" -e "hash matches" [3.141229] PM: Magic number: 0:247:394 [3.145558] PM: hash matches drivers/base/power/main.c:982 [3.149905] thermal cooling_device9: hash matches = sudo su echo platform > /sys/power/pm_test exit sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" ... after power up again ... dmesg | grep -e "Magic number" -e "hash matches" [3.142816] PM: Magic number: 0:247:394 [3.147180] PM: hash matches drivers/base/power/main.c:982 [3.151573] thermal cooling_device9: hash matches = sudo su echo processors > /sys/power/pm_test exit sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" ... after power up again ... dmesg | grep -e "Magic number" -e "hash matches" [3.141830] PM: Magic number: 0:247:394 [3.146148] PM: hash matches drivers/base/power/main.c:982 [3.150488] thermal cooling_device9: hash matches = sudo su echo core > /sys/power/pm_test exit sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" ... after power up again ... dmesg | grep -e "Magic number" -e "hash matches" [3.140971] PM: Magic number: 0:247:394 [3.145294] PM: hash matches drivers/base/power/main.c:982 [3.149639] thermal cooling_device9: hash matches = sudo su echo none > /sys/power/pm_test exit sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" ... after power up again ... dmesg | grep -e "Magic number" -e "hash matches" [3.143489] PM: Magic number: 0:247:394 [3.147856] PM: hash matches drivers/base/power/main.c:982 [3.152244] thermal cooling_device9: hash matches = $ sudo cat /sys/kernel/debug/suspend_stats success: 0 fail: 0 failed_freeze: 0 failed_prepare: 0 failed_suspend: 0 failed_suspend_late: 0 failed_suspend_noirq: 0 failed
[Kernel-packages] [Bug 1966093] Re: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-390 into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-390/390.147-0ubuntu0.21.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Impish) Status: In Progress => Fix Committed ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1966093 Title: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Committed Status in linux-restricted-modules source package in Bionic: Triaged Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Focal: Triaged Status in nvidia-graphics-drivers-390 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-510 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Impish: Triaged Status in nvidia-graphics-drivers-390 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-510 source package in Impish: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] === 510 impish/focal/bionic === * New upstream release (LP: #1966093): - Added support for the following GPUs: NVIDIA RTX A4000H NVIDIA RTX A5500 - Fixed a bug that could cause displays with HDMI or DisplayPort audio to be deselected as the default audio output device after resuming from suspend. - Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT- switches - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:" in /proc/driver/nvidia/gpus//information to be "Unknown" for some GPUs. === 390 impish/focal/bionic === * New upstream release (LP: #1966093): - Fixed a bug where vkCreateSwapchain could cause the X Server to crash when an invalid imageFormat was provided. - Fixed a driver installation failure on Linux kernel 5.11 release candidates, where the NVIDIA kernel module failed to build with error "fatal error: asm/kmap_types.h: No such file or directory". [ Dimitri John Ledkov ] * debian/dkms_nvidia/patches/buildfix_kernel_5.13_armhf.patch: - Fix armhf builds. * debian/dkms_nvidia/patches/buildfix_kernel_5.17.patch: - Fix build failure with Linux 5.17. To manage notifications about this bug go to: https://bu
[Kernel-packages] [Bug 1960633] Re: Move virtual graphics drivers from linux-modules-extra to linux-modules
Bionic (HWE) verification *failure*:
root@bionic-vm:~# uname -a
Linux bionic-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
root@bionic-vm:~# dpkg -l| grep linux-modules
ii linux-modules-5.4.0-105-generic 5.4.0-105.119~18.04.1
amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
ii linux-modules-5.4.0-107-generic 5.4.0-107.121~18.04.1
amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
No linux-modules-extra package is installed but virtio_gpu cannot be
loaded:
root@bionic-vm:~# modprobe virtio_gpu
modprobe: FATAL: Module virtio_gpu not found in directory
/lib/modules/5.4.0-107-generic
Same for vmwgfx:
root@bionic-vm:~# modprobe vmwgfx
modprobe: FATAL: Module vmwgfx not found in directory
/lib/modules/5.4.0-107-generic
The modules are NOT provided by the linux-modules packages:
root@bionic-vm:~# grep -E '(virtio-gpu|vmwgfx)\.ko'
/var/lib/dpkg/info/linux-modules-5.4.0-10{5,7}-generic.list
root@bionic-vm:~#
The relevant kernel modules are still shipped in the linux-modules-extra
package:
root@bionic-vm:~# apt-get install linux-modules-extra-5.4.0-107-generic
root@bionic-vm:~# grep -E '(virtio-gpu|vmwgfx)\.ko'
/var/lib/dpkg/info/linux-modules-extra-5.4.0-107-generic.list
/var/lib/dpkg/info/linux-modules-extra-5.4.0-107-generic.list:/lib/modules/5.4.0-107-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
/var/lib/dpkg/info/linux-modules-extra-5.4.0-107-generic.list:/lib/modules/5.4.0-107-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
** Tags removed: verification-needed-bionic
** Tags added: verification-failed-bionic
--
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/1960633
Title:
Move virtual graphics drivers from linux-modules-extra to linux-
modules
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
Fix Released
Bug description:
[SRU justification]
Impact: We split the drivers into linux-modules and linux-modules-extra. The
latter is only included for setups geared towards real hardware (desktops,
laptops). For VM guests the recommended setup is to use linux-virtual which
does not include linux-modules-extra but also does not depend on other
packages, like linux-firmware.
We already include most VM related drivers in the linux-modules package and
vboxvideo (since 21.10/Impish). So it makes sense to include the missing ones.
Fix: Move the following modules from linux-modules-extra into linux-modules:
- bochs-drm (though a bit aged, this was the predecessor of qemu)
- cirrus (this is a standard emulated gfx card, might not give the best
performance but better than nothing)
- virtio-gpu (KVM)
- vmwgfx (VMWare)
- drm-xen-front (Xen)
Testcase: Check linux-modules for the mentioned modules.
Regression Potential: There should be no change noticeable. Users with
linux-modules-extra installed will see no difference and those without
have additional drivers. Maybe this shows as moving from low-
resolution graphics to higher ones which maybe perform less.
--- Original Description ---
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains
kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko, so at the moment I need to
keep it installed and updated. The only way to do so conveniently is
to install linux-image-generic, which also pulls in linux-firmware,
which is ~760MB installed.
If vmwgfx was moved from linux-modules-extra to linux-modules, I could
use linux-image-virtual instead of linux-image-generic, remove linux-
firmware, linux-modules-extra, and the microcode packages, saving
substantial disk space and bandwidth.
Other virtual graphics drivers in linux-modules-extra that might be
worth moving are:
kernel/drivers/gpu/drm/bochs/bochs-drm.ko
kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
kernel/drivers/gpu/drm/xen/drm_xen_front.ko
Thank you for your consideration.
Note: Edited significantly in response to
https://lists.ubuntu.com/archives/kernel-
team/2022-February/128103.html and
https://lists.ubuntu.com/archives/kernel-
team/2022-February/128104.html to better reflect the underlying
problem and solution.
P.S. There are three other drivers in linux-modules-extra that seem
VMWare-related, but they are not in use in my VM and I don't know
whether they are in common enough use to justify moving them to linux-
modules. I have listed them here for completeness.
kernel/drivers/net/vsockmon.ko
kernel/drivers/ptp/ptp_vmw.ko
kernel/drivers/infi
[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted
The same here. Distorted sound every ~7 seconds. Kernel 5.13.0-35 is fine, kernel 5.13.0-37 is buggy. External card: Thinkpad USB-C Dock Gen2, 40AS, 0090EU. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1966066 Title: audio from external sound card is distorted Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: The sound card is a Focusrite Scarlett 2i2. The sound is distorted everywhere. Sound via HDMI works. Seen others having the same problem: (Edit because of previously wrong link here) https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card ubuntu release: Ubuntu 20.04.4 LTS package name involved in bug: linux-image-5.13.0-37-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 12:56:02 2022 InstallationDate: Installed on 2020-12-18 (459 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966066/+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 1966125] Re: Suspend (to ram) fails after upgrade from 5.13.0-35-generic to 5.13.0-37-generic
Same issue for me on an AMD system after booting into 5.13.0-37-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1966125 Title: Suspend (to ram) fails after upgrade from 5.13.0-35-generic to 5.13.0-37-generic Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: As stated in the summary, my PC can't suspend anymore after kernel upgrade. When I click suspend from desktop: - The screen gets blank - (sometimes) Screen then shows up for a short time, then gets blank again - Now PC ist "dead", no reaction an keyboard, mouse and so on. - Even a CTR-ALT-DEL didn't show any reaction. - There is still some activity (HD-Led flashing) - The PC is "reachable" via network, but trying to ssh into it will not work (no response after entering password) - I have to reboot, either by power the PC off by pressing the power button longer or by using "Magic SysRq" keyboard sequence When I rollback (I use systemback) to Kernel 5.13.0-35-generic suspend works! # Information needed as directed by https://wiki.ubuntu.com/DebuggingKernelSuspend) # = $cat /proc/acpi/wakeup DeviceS-state Status Sysfs node GPP0S4*enabled pci::00:01.1 GP12S4*enabled pci::00:07.1 GP13S4*enabled pci::00:08.1 XHC0S4*enabled pci::0e:00.3 GP30S4*disabled GP31S4*disabled PS2KS3*disabled GPP2S4*disabled GPP3S4*disabled GPP8S4*enabled pci::00:03.1 SWUSS4*enabled pci::0a:00.0 SWDSS4*enabled pci::0b:00.0 GPP1S4*enabled pci::00:01.2 = sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" ... after power up again ... dmesg | grep -e "Magic number" -e "hash matches" [3.141067] PM: Magic number: 0:247:389 [3.145394] PM: hash matches drivers/base/power/main.c:982 [3.149741] thermal cooling_device4: hash matches = sudo su echo freezer > /sys/power/pm_test exit sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" ... promt is back after a few seconds again ... dmesg | grep -e "Magic number" -e "hash matches" [3.142991] PM: Magic number: 14:995:344 [3.147383] tty tty61: hash matches [3.151721] acpi ACPI0007:06: hash matches = sudo su echo devices > /sys/power/pm_test exit sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" ... after power up again ... dmesg | grep -e "Magic number" -e "hash matches" [3.141229] PM: Magic number: 0:247:394 [3.145558] PM: hash matches drivers/base/power/main.c:982 [3.149905] thermal cooling_device9: hash matches = sudo su echo platform > /sys/power/pm_test exit sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" ... after power up again ... dmesg | grep -e "Magic number" -e "hash matches" [3.142816] PM: Magic number: 0:247:394 [3.147180] PM: hash matches drivers/base/power/main.c:982 [3.151573] thermal cooling_device9: hash matches = sudo su echo processors > /sys/power/pm_test exit sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" ... after power up again ... dmesg | grep -e "Magic number" -e "hash matches" [3.141830] PM: Magic number: 0:247:394 [3.146148] PM: hash matches drivers/base/power/main.c:982 [3.150488] thermal cooling_device9: hash matches = sudo su echo core > /sys/power/pm_test exit sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" ... after power up again ... dmesg | grep -e "Magic number" -e "hash matches" [3.140971] PM: Magic number: 0:247:394 [3.145294] PM: hash matches drivers/base/power/main.c:982 [3.149639] thermal cooling_device9: hash matches = sudo su echo none > /sys/power/pm_test exit sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" ... after power up again ... dmesg | grep -e "Magic number" -e "hash matches" [3.143489] PM: Magic number: 0:247:394 [3.147856] PM: hash matches drivers/base/power/main.c:982 [3.152244] thermal cooling_device9: hash matches = $ sudo cat /sys/kernel/debug/suspend_stats success: 0 fail: 0 failed_freeze: 0 failed_prepare: 0 failed_suspend: 0 failed_suspend_late: 0 failed_suspend_noirq: 0 failed_resume: 0 failed_resume_early: 0 failed_resume_noirq: 0 failures:
[Kernel-packages] [Bug 1966472] [NEW] nvidia-drivers-510 HDMI output not working
Public bug reported: With nvidia-graphics-drivers 510 version HDMI output is not working. Changing the screen setup causes a crash. With 470 version HDMI output works well only with extend screen setup, not if single screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-driver-510 (not installed) ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 15:19:08 2022 InstallationDate: Installed on 2022-03-21 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-510 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1966472 Title: nvidia-drivers-510 HDMI output not working Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: With nvidia-graphics-drivers 510 version HDMI output is not working. Changing the screen setup causes a crash. With 470 version HDMI output works well only with extend screen setup, not if single screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-driver-510 (not installed) ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 15:19:08 2022 InstallationDate: Installed on 2022-03-21 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-510 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/+bug/1966472/+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 1962349] Please test proposed package
Hello Mario, or anyone else affected, Accepted bolt into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bolt/0.9.1-2~ubuntu20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1962349 Title: Bolt doesn't work with native USB4 hosts Status in OEM Priority Project: New Status in bolt package in Ubuntu: Fix Released 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 bolt source package in Focal: Fix Committed Status in linux source package in Focal: Won't Fix 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 bolt source package in Impish: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released 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] * AMD Yellow Carp provides integrated USB4 host controllers * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] AMD Yellow Carp Host (issue this bug is about) -- * Plug in USB4 device or TBT3 to AMD Yellow Carp host * Ensure that PCI topology has populated * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" * Try to run `boltctl enroll $UUID` Alpine Ridge / Titan Ridge host (discrete controller) -- Start out on a host with discrete controller (Alpine Ridge or Titan Ridge) 1. sudo boltctl forget -a 2. Plug in dock 3. Make sure 'boltctl list' enumerates dock. 4. Check /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection (value dependent upon host) - If 0; try to manually enroll using 'boltctl enroll $UUID' - If 1; ensure that device automatically enrolled with bolt. GUI Check - Ensure that devices show up in the Settings GUI and are now able to authorize. Note: for AMD platforms enumerating PCIe devices is a separate problem from BOLT handled by kernel tasks. GUI check is only about "authorization". [Where problems could occur] * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. * There haven't been any significant bugs reported upstream or in Ubuntu since 0.9.1 release. [Other Info] * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. * It is fixed in bolt 0.9.1 or later release. * To solve the SRU, will backport 0.9.1 release from Impish. * I did look into backporting just the commit(s) for fixing this, but it's not a trivial backport. Quoting the changelog (https://gitlab.freedesktop.org/bolt/bolt/-/blob/master/CHANGELOG.md): "Additionally the unique_id of said host controller changes with every boot, which breaks one of the fundamental assumptions in boltd". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962349/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@
[Kernel-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts
fair point, and the upstream fixes in .2 don't seem that important after a quick look ** Changed in: bolt (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- 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/1962349 Title: Bolt doesn't work with native USB4 hosts Status in OEM Priority Project: New Status in bolt package in Ubuntu: Fix Released 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 bolt source package in Focal: Fix Committed Status in linux source package in Focal: Won't Fix 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 bolt source package in Impish: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released 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] * AMD Yellow Carp provides integrated USB4 host controllers * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] AMD Yellow Carp Host (issue this bug is about) -- * Plug in USB4 device or TBT3 to AMD Yellow Carp host * Ensure that PCI topology has populated * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" * Try to run `boltctl enroll $UUID` Alpine Ridge / Titan Ridge host (discrete controller) -- Start out on a host with discrete controller (Alpine Ridge or Titan Ridge) 1. sudo boltctl forget -a 2. Plug in dock 3. Make sure 'boltctl list' enumerates dock. 4. Check /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection (value dependent upon host) - If 0; try to manually enroll using 'boltctl enroll $UUID' - If 1; ensure that device automatically enrolled with bolt. GUI Check - Ensure that devices show up in the Settings GUI and are now able to authorize. Note: for AMD platforms enumerating PCIe devices is a separate problem from BOLT handled by kernel tasks. GUI check is only about "authorization". [Where problems could occur] * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. * There haven't been any significant bugs reported upstream or in Ubuntu since 0.9.1 release. [Other Info] * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. * It is fixed in bolt 0.9.1 or later release. * To solve the SRU, will backport 0.9.1 release from Impish. * I did look into backporting just the commit(s) for fixing this, but it's not a trivial backport. Quoting the changelog (https://gitlab.freedesktop.org/bolt/bolt/-/blob/master/CHANGELOG.md): "Additionally the unique_id of said host controller changes with every boot, which breaks one of the fundamental assumptions in boltd". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962349/+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 1966093] Autopkgtest regression report (nvidia-graphics-drivers-390/390.147-0ubuntu0.18.04.1)
All autopkgtests for the newly accepted nvidia-graphics-drivers-390 (390.147-0ubuntu0.18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.147-0ubuntu0.18.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#nvidia-graphics-drivers-390 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1966093 Title: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Committed Status in linux-restricted-modules source package in Bionic: Triaged Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Focal: Triaged Status in nvidia-graphics-drivers-390 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-510 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Impish: Triaged Status in nvidia-graphics-drivers-390 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-510 source package in Impish: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] === 510 impish/focal/bionic === * New upstream release (LP: #1966093): - Added support for the following GPUs: NVIDIA RTX A4000H NVIDIA RTX A5500 - Fixed a bug that could cause displays with HDMI or DisplayPort audio to be deselected as the default audio output device after resuming from suspend. - Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT- switches - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:" in /proc/driver/nvidia/gpus//information to be "Unknown" for some GPUs. === 390 impish/focal/bionic === * New upstream release (LP: #1966093): - Fixed a bug where vkCreateSwapchain could cause the X Server to crash when an invalid imageFormat was provided. - Fixed a driver installation failure on Linux kernel 5.11 release candidates, where the NVIDIA kernel module failed to build with error "fatal error: asm/kmap_types.h: No such file or directory". [ Dimitri John Ledkov ] * debian/dkms_nvidia/patches/buildfix_kernel_5.13_armhf.patch: - Fix armhf builds. * debian/dkms_nvidia/patches/buildfix_kernel_5.17.patch: - Fix build failure with Linux 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1966093/+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 1962831] Re: [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
This bug is awaiting verification that the linux- hwe-5.4/5.4.0-107.121~18.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1962831 Title: [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: SRU Justification: == [Impact] * KVM uses lazy storage key enablement as Linux does no longer make use of the storage keys. When the guest enters keyed mode, then KVM will save/restore the key during paging, provide change/reference tracking for guest and host and for all interpreted instructions will do key protection. * If an instruction is intercepted and passed along to userspace (like QEMU) no storage key protection is checked, though. * But this is in violation of the architecture and it can result in misbehaving guests that rely on key protection for all instructions. * This item will improve the MEMOP ioctl to also add key checking. In case of a key protection the right fault is injected in the guest. [Fix] * The following changes since commit dbdbd581976f9dfcc9e21a777273b55bdb9bf138: UBUNTU: Ubuntu-5.4.0-102.115 (2022-02-23 15:32:05 +0100) are available in the Git repository at: https://git.launchpad.net/~fheimes/+git/lp1962831/ 16c0809cf1012e68279a8936a482c1d63cc4d14c for you to fetch changes up to 16c0809cf1012e68279a8936a482c1d63cc4d14c: KVM: s390: Add missing vm MEM_OP size check (2022-03-03 22:45:50 +0100) * Patches are upstream accepted (but some are as of today still in linux-next). * Notes on why the backports are needed are included in the provenance of the corresponding commit. [Test Case] * An IBM z13 or LinuxONE system is needed running Ubuntu Server 20.04 with QEMU/KVM setup. * These modification here are covered by the following three tests: * [kvm-unit-tests,v2] s390x: Test effect of storage keys on some instructions https://patchwork.kernel.org/project/kvm/patch/20220301095059.3026178-1-s...@linux.ibm.com/ * [PATCH v2 0/5] memop selftest for storage key checking https://lore.kernel.org/kvm/20220225155311.3540514-1-s...@linux.ibm.com/ * c7ef9ebbed20 "KVM: s390: selftests: Test TEST PROTECTION emulation" * The tests and the verification will be done by the IBM Z team. * On top a test build is available (see below). [Where problems could occur] * Issues with vm ioctl may occur due to the introduction of _vm_ioctl. * Tests may fail or may report wrong states due to the new TEST_FAIL macro in tests/utilities or due to new variants of GUEST_ASSERT in selftests. * Problems on gaccess might be caused due to the refactoring of gpa, length calculation, access address range check and the new access_guest_page helper function. * In uaccess issues may occur due to the introduction of the bit field for OAC specifier, that causes lot's but relatively straight forward changes or due to the new storage key checking functions copy_from/to_user_key functions. * Compile issues may happen if the changes in uaccess.h bout z10 features are erroneous. * Instructions that are emulated by KVM might be impacted due to the expanded storage key checking, that now covers intercepted instructions, too. This is the most significant modification in terms of size and complexity and therefore carries the highest risk. * MEM_OP IOCTL could be harmed due to the additional, but optional, storage key extension and checking, or the new size check and I/O emulation can be impacted due to the new vm IOCTL for key checked guest memory access. * Some tests were added to mitigate this, like the selftests TEST PROTECTION. * The renaming of the existing vcpu memop functions shouldn't be very harmful, since issues will already occur test build. * The rest are API documentation updates and clarifications. * Except two include/header changes and changes in tools/testing all other modifications are s390x specific [Other] * It was ensured that these changes are in jammy based on LP#1933179. __ Descriptio
[Kernel-packages] [Bug 1966125] Re: Suspend (to ram) fails after upgrade from 5.13.0-35-generic to 5.13.0-37-generic
I had already found the reason for this behavior! The only change in the "drivers/base/power/" Subdirectory is inside main.c line 192. There is a "while loop" that loops over a list (dpm_list). The (principal) task of this loop is to call "device_prepare" on every list-element. Every element that is processed (without error) is then removed from the list and placed into a "prepared" list (I leave out the special case of EAGAIN here, because its not necessary to understood the bug). In the prev. version this loop is terminated when the list is empty OR when there is an error. In the newer revision the second condition was removed. Removing the second condition will result in an endless loop whenever an error occurs! Right now I am not sure what will be the correct way to handle an error (on device_prepare)... I guess that the correct way should be to "skip/mark" this element, continue to process the rest of the elements and do special handling later on the marked elements. But, because the prev. revision simply ignores the failed element AND all remaining (I believe that the second part is definitely wrong) , this should work here too. I am currently trying to generate a kernel with this line reverted to prev. version and check if this works.. I will report (again) if my checks are done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1966125 Title: Suspend (to ram) fails after upgrade from 5.13.0-35-generic to 5.13.0-37-generic Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: As stated in the summary, my PC can't suspend anymore after kernel upgrade. When I click suspend from desktop: - The screen gets blank - (sometimes) Screen then shows up for a short time, then gets blank again - Now PC ist "dead", no reaction an keyboard, mouse and so on. - Even a CTR-ALT-DEL didn't show any reaction. - There is still some activity (HD-Led flashing) - The PC is "reachable" via network, but trying to ssh into it will not work (no response after entering password) - I have to reboot, either by power the PC off by pressing the power button longer or by using "Magic SysRq" keyboard sequence When I rollback (I use systemback) to Kernel 5.13.0-35-generic suspend works! # Information needed as directed by https://wiki.ubuntu.com/DebuggingKernelSuspend) # = $cat /proc/acpi/wakeup DeviceS-state Status Sysfs node GPP0S4*enabled pci::00:01.1 GP12S4*enabled pci::00:07.1 GP13S4*enabled pci::00:08.1 XHC0S4*enabled pci::0e:00.3 GP30S4*disabled GP31S4*disabled PS2KS3*disabled GPP2S4*disabled GPP3S4*disabled GPP8S4*enabled pci::00:03.1 SWUSS4*enabled pci::0a:00.0 SWDSS4*enabled pci::0b:00.0 GPP1S4*enabled pci::00:01.2 = sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" ... after power up again ... dmesg | grep -e "Magic number" -e "hash matches" [3.141067] PM: Magic number: 0:247:389 [3.145394] PM: hash matches drivers/base/power/main.c:982 [3.149741] thermal cooling_device4: hash matches = sudo su echo freezer > /sys/power/pm_test exit sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" ... promt is back after a few seconds again ... dmesg | grep -e "Magic number" -e "hash matches" [3.142991] PM: Magic number: 14:995:344 [3.147383] tty tty61: hash matches [3.151721] acpi ACPI0007:06: hash matches = sudo su echo devices > /sys/power/pm_test exit sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" ... after power up again ... dmesg | grep -e "Magic number" -e "hash matches" [3.141229] PM: Magic number: 0:247:394 [3.145558] PM: hash matches drivers/base/power/main.c:982 [3.149905] thermal cooling_device9: hash matches = sudo su echo platform > /sys/power/pm_test exit sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" ... after power up again ... dmesg | grep -e "Magic number" -e "hash matches" [3.142816] PM: Magic number: 0:247:394 [3.147180] PM: hash matches drivers/base/power/main.c:982 [3.151573] thermal cooling_device9: hash matches = sudo su echo processors > /sys/power/pm_test exit sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" ... after power up again ... dmesg | grep -e "Magic number" -e "hash matches" [3.141
[Kernel-packages] [Bug 1958786] Re: CRASH - [drm:amd gpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
It is ABSOLUTLY INACCEPTABLE that watching video can CRASH the whole system! -- 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/1958786 Title: CRASH - [drm:amd gpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Status in linux package in Ubuntu: Confirmed Bug description: While watching a video from hard drive with vlc i got this complete crash of my machine! I wasn't able to do anything in the GUI with keyboard and/or mouse , all input where gone Going to TTY1 and killing vlc did not change anything. I had to reboot hard. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-27-generic 5.13.0-27.29 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: frank 2973 F pulseaudio /dev/snd/controlC0: frank 2973 F pulseaudio CasperMD5CheckResult: unknown Date: Sun Jan 23 20:31:47 2022 InstallationDate: Installed on 2020-12-28 (391 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp4s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_DE TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=b9069cfc-c55b-4b7e-ab02-17ebf1727f41 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-27-generic N/A linux-backports-modules-5.13.0-27-generic N/A linux-firmware 1.201.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-11-28 (56 days ago) dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X570-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX570-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958786/+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 1950107] Re: Ubuntu MATE 20.04.3 window-list crashed
** Changed in: linux-signed-hwe-5.11 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1950107 Title: Ubuntu MATE 20.04.3 window-list crashed Status in linux-signed-hwe-5.11 package in Ubuntu: Invalid Status in mate-panel package in Ubuntu: New Bug description: I got an error pop-up about a program crashing. I did not recognize the name as pertaining to Ubuntu MATE, so I closed it. The list of windows at the bottom of the screen was blank. Google how to reset the Windows List Manager. Dic alt-cntl-F2. Then the display went black (no signal). Had to turn off (without shutting down - blank screen). Had to reboot. Tried to report bug but was told that although it is in the distro, it is not supported (like Caja). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Nov 7 21:11:20 2021 SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1950107/+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 1939638] Re: [regression] USB device is not detected during boot
Confirmed, this seems to be broken again on Ubuntu Core 20 devices using
the latest pc-kernel Snap on the 20/stable channel (5.4.0-104.118.1).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1939638
Title:
[regression] USB device is not detected during boot
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-intel package in Ubuntu:
Confirmed
Status in linux-intel-5.13 package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux-intel source package in Focal:
Confirmed
Status in linux-intel-5.13 source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in linux-intel source package in Hirsute:
Invalid
Status in linux-intel-5.13 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
The USB devices (keyboard, storage...) are failed to be detected when
connecting to the problematic root hubs which need longer PowerOn-to-PowerGood
delay than it claims in the hub descriptor. It's caused by the upstream fix
90d28fb53d4a ("usb: core: reduce power-on-good delay time of root hub").
[Fix]
Reverting the upstream fix until a formal fix been placed.
[Test Case]
1. Plug the USB device to the ports of problematic root hub.
2. Power on the machine.
3. Check if the USB device can work or not after boot.
[Regression Potential]
Low. The longer delay is proven safe in old kernels.
== Original Bug Description ==
[Summary]
The USB devices (keyboard, storage...) are failed to be detected during boot
after upgrade to UBUNTU focal kernel 5.4.0-78 and hirsute 5.11.0-26. However,
they will be detected and working ok after re-plugging. The kernel output shows
as down below during boot
[ 39.350435] hub 1-0:1.0: USB hub found
[ 39.398835] hub 1-0:1.0: 12 ports detected
[ 39.622744] usb usb1-port3: couldn't allocate usb_device
And when I plug out then plug in the same device, it shows
[57210.794140] usb 1-3: new low-speed USB device number 4 using xhci_hcd
[57210.951289] usb 1-3: New USB device found, idVendor=17ef, idProduct=6099,
bcdDevice= 1.14
[57210.951293] usb 1-3: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
After doing kernel bisecting, we found the upstream commit
https://github.com/torvalds/linux/commit/90d28fb53d4a51299ff324dede015d5cb11b88a2
makes the difference. It indicates that the delay for the root hub from
power_on to power_good is not long enough. There was no problem if the delay is
100 ms. From the Hub Descriptor of the root hub, the value is 10 * 2
milliseconds. And the XHCI spec also says in section 5.4.8
"""
The host is required to have power stable to the port within 20 milliseconds
of the '0' to '1' transition of PP. If PPC = '1', software is responsible for
waiting 20ms.
"""
The commit seems to follow the SPEC but could cause problems on some
hubs.
[Reproduce Steps]
1. Plug the USB device to the physical port #1 and #4 which belongs to
high-speed hub.
2. Power on the machine.
3. Check if the USB device can work or not after boot.
[Results]
Expected:
All usb devices connect to the hub should work OK.
Actual:
USB devices connects to high-speed hub can not be probed.
[Additional Information]
Kernel Version: focal 5.4.0-78 and hirsute 5.11.0-26
[Upstream bug]
https://bugzilla.kernel.org/show_bug.cgi?id=214021
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1939638/+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 1966432] [NEW] audio crackling on usb sound card
You have been subscribed to a public bug: After the regular updates (on 20.04 and 21.10) audio had crackling noise on the USB audio interface, while it was normal on the internal audio. Tried with different sound cards (presonus audiobox, behringer xenyx q802) and three different machines. Might be in the kernel 5.13.0-37 Reverting to that kernel removed the problem: linux- image-5.13.0-35-generic ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- audio crackling on usb sound card https://bugs.launchpad.net/bugs/1966432 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux 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 1966432] Re: audio crackling on usb sound card
** Package changed: ubuntu => linux (Ubuntu) -- 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/1966432 Title: audio crackling on usb sound card Status in linux package in Ubuntu: New Bug description: After the regular updates (on 20.04 and 21.10) audio had crackling noise on the USB audio interface, while it was normal on the internal audio. Tried with different sound cards (presonus audiobox, behringer xenyx q802) and three different machines. Might be in the kernel 5.13.0-37 Reverting to that kernel removed the problem: linux- image-5.13.0-35-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966432/+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 1966498] [NEW] kernel:[ 7548.242662] watchdog: BUG: soft lockup - CPU#2 stuck for 3203s! [kauditd:110]
Public bug reported: When updated to kernel 5.13.0-37-generic we get this error and the server became unresponsive. I've updated four different servers and all have the same problem. On kernel 5.13.0-35-generic everything is fine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Mar 25 15:49:18 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1966498 Title: kernel:[ 7548.242662] watchdog: BUG: soft lockup - CPU#2 stuck for 3203s! [kauditd:110] Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: When updated to kernel 5.13.0-37-generic we get this error and the server became unresponsive. I've updated four different servers and all have the same problem. On kernel 5.13.0-35-generic everything is fine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Mar 25 15:49:18 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966498/+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 1966497] [NEW] Fix non-working MT7921 BT after reboot
Public bug reported: [Impact] There's a high chance that MT7921 BT may go out to lunch after reboot. Worse, there's no way to recover the controller unless the power cord is unplugged. [Fix] In addition to SRU "Need to reset MT7921 BT when the firmware hang or command no response", enable MSFT extension can magically solve the issue. [Test] With the patch applied, the MT7921 BT continues to work after 100 times reboots. [Where problems could occur] This fix is specific to MTK BT controllers, so the change is limited. I totally don't understand why this patch can fix the issue, other than it just does the trick. So I guess we have to accept the reality that hardwares can have their own quirks. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Medium Status: Confirmed ** Tags: oem-priority originate-from-1961591 sutton ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Invalid ** Tags added: oem-priority originate-from-1961591 sutton -- 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/1966497 Title: Fix non-working MT7921 BT after reboot Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: [Impact] There's a high chance that MT7921 BT may go out to lunch after reboot. Worse, there's no way to recover the controller unless the power cord is unplugged. [Fix] In addition to SRU "Need to reset MT7921 BT when the firmware hang or command no response", enable MSFT extension can magically solve the issue. [Test] With the patch applied, the MT7921 BT continues to work after 100 times reboots. [Where problems could occur] This fix is specific to MTK BT controllers, so the change is limited. I totally don't understand why this patch can fix the issue, other than it just does the trick. So I guess we have to accept the reality that hardwares can have their own quirks. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966497/+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 1966432] 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 1966432 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/1966432 Title: audio crackling on usb sound card Status in linux package in Ubuntu: Incomplete Bug description: After the regular updates (on 20.04 and 21.10) audio had crackling noise on the USB audio interface, while it was normal on the internal audio. Tried with different sound cards (presonus audiobox, behringer xenyx q802) and three different machines. Might be in the kernel 5.13.0-37 Reverting to that kernel removed the problem: linux- image-5.13.0-35-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966432/+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 1962349] Re: Bolt doesn't work with native USB4 hosts
verified bolt(0.9.1-2~ubuntu20.04.1) + PPA(5.14.0-9029.32+exp.60) + BIOS(Bootleg-97.20.31) on HP-Lockheed, where shows positive result on hotplug(S0)/Reboot/ColdBoot with TBT storage connected -- 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/1962349 Title: Bolt doesn't work with native USB4 hosts Status in OEM Priority Project: New Status in bolt package in Ubuntu: Fix Released 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 bolt source package in Focal: Fix Committed Status in linux source package in Focal: Won't Fix 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 bolt source package in Impish: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released 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] * AMD Yellow Carp provides integrated USB4 host controllers * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] AMD Yellow Carp Host (issue this bug is about) -- * Plug in USB4 device or TBT3 to AMD Yellow Carp host * Ensure that PCI topology has populated * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" * Try to run `boltctl enroll $UUID` Alpine Ridge / Titan Ridge host (discrete controller) -- Start out on a host with discrete controller (Alpine Ridge or Titan Ridge) 1. sudo boltctl forget -a 2. Plug in dock 3. Make sure 'boltctl list' enumerates dock. 4. Check /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection (value dependent upon host) - If 0; try to manually enroll using 'boltctl enroll $UUID' - If 1; ensure that device automatically enrolled with bolt. GUI Check - Ensure that devices show up in the Settings GUI and are now able to authorize. Note: for AMD platforms enumerating PCIe devices is a separate problem from BOLT handled by kernel tasks. GUI check is only about "authorization". [Where problems could occur] * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. * There haven't been any significant bugs reported upstream or in Ubuntu since 0.9.1 release. [Other Info] * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. * It is fixed in bolt 0.9.1 or later release. * To solve the SRU, will backport 0.9.1 release from Impish. * I did look into backporting just the commit(s) for fixing this, but it's not a trivial backport. Quoting the changelog (https://gitlab.freedesktop.org/bolt/bolt/-/blob/master/CHANGELOG.md): "Additionally the unique_id of said host controller changes with every boot, which breaks one of the fundamental assumptions in boltd". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962349/+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 1962349] Re: Bolt doesn't work with native USB4 hosts
** Tags removed: verification-needed ** Tags added: verification-done -- 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/1962349 Title: Bolt doesn't work with native USB4 hosts Status in OEM Priority Project: New Status in bolt package in Ubuntu: Fix Released 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 bolt source package in Focal: Fix Committed Status in linux source package in Focal: Won't Fix 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 bolt source package in Impish: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released 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] * AMD Yellow Carp provides integrated USB4 host controllers * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] AMD Yellow Carp Host (issue this bug is about) -- * Plug in USB4 device or TBT3 to AMD Yellow Carp host * Ensure that PCI topology has populated * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" * Try to run `boltctl enroll $UUID` Alpine Ridge / Titan Ridge host (discrete controller) -- Start out on a host with discrete controller (Alpine Ridge or Titan Ridge) 1. sudo boltctl forget -a 2. Plug in dock 3. Make sure 'boltctl list' enumerates dock. 4. Check /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection (value dependent upon host) - If 0; try to manually enroll using 'boltctl enroll $UUID' - If 1; ensure that device automatically enrolled with bolt. GUI Check - Ensure that devices show up in the Settings GUI and are now able to authorize. Note: for AMD platforms enumerating PCIe devices is a separate problem from BOLT handled by kernel tasks. GUI check is only about "authorization". [Where problems could occur] * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. * There haven't been any significant bugs reported upstream or in Ubuntu since 0.9.1 release. [Other Info] * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. * It is fixed in bolt 0.9.1 or later release. * To solve the SRU, will backport 0.9.1 release from Impish. * I did look into backporting just the commit(s) for fixing this, but it's not a trivial backport. Quoting the changelog (https://gitlab.freedesktop.org/bolt/bolt/-/blob/master/CHANGELOG.md): "Additionally the unique_id of said host controller changes with every boot, which breaks one of the fundamental assumptions in boltd". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962349/+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 1966498] Re: kernel:[ 7548.242662] watchdog: BUG: soft lockup - CPU#2 stuck for 3203s! [kauditd:110]
I've tested (accidentaly) on 4 different servers. Three of them have the same CPU of the bug report. The fourth one has the cpu attached to this comment. ** Attachment added: "cpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966498/+attachment/5572956/+files/cpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1966498 Title: kernel:[ 7548.242662] watchdog: BUG: soft lockup - CPU#2 stuck for 3203s! [kauditd:110] Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: When updated to kernel 5.13.0-37-generic we get this error and the server became unresponsive. I've updated four different servers and all have the same problem. On kernel 5.13.0-35-generic everything is fine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Mar 25 15:49:18 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966498/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
I enabled proposed and upgrade alsa-ucm-conf, then reboot the system. I plugged a microphone to the rear panel, made sure it works, then I plugged a speaker to line-out, and made sure both speaker and mic are working. So the original issue is solved by this SRU. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: == SRU Justification == [Impact] On P620, only single port can work on rear panel. For example, when the Line-Out is plugged, the Mic won't work anymore. [Fix] Use upstream version of UCM to handle port priority correctly, instead of separate ports into different profiles. [Test] Once the UCM is in place, all three ports of rear panel work correctly. [Where problems could occur] UCM is not a static thing - it's actually interpreted differently at higher level. So any change in userspace daemons other than PulseAudio may not like the change and can interpret the UCM in another way. == Original Bug Report == After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1966499] [NEW] Recent 5.13 kernel has broken KVM support
Public bug reported: Upgrading to 5.13.0-37 or 5.13.0-39 immediately crashes my production servers as they hit: https://lore.kernel.org/all/f1ea22d3-cff8-406a-ad6a-cb8e0124a...@leemhuis.info/T/#md1f5c8c4aa01130a449a47f3e7559f06b0372f55 It looks like we need to get e90e51d5f01d included in those kernels. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966499 Title: Recent 5.13 kernel has broken KVM support Status in linux package in Ubuntu: Confirmed Bug description: Upgrading to 5.13.0-37 or 5.13.0-39 immediately crashes my production servers as they hit: https://lore.kernel.org/all/f1ea22d3-cff8-406a-ad6a-cb8e0124a...@leemhuis.info/T/#md1f5c8c4aa01130a449a47f3e7559f06b0372f55 It looks like we need to get e90e51d5f01d included in those kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966499/+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 1966499] Re: Recent 5.13 kernel has broken KVM support
Mar 25 16:18:30 abydos kernel: [ 1319.549186] [ cut here ] Mar 25 16:18:30 abydos kernel: [ 1319.549191] WARNING: CPU: 12 PID: 15052 at arch/x86/kvm/vmx/vmx.c:6336 vmx_sync_pir_to_irr+0x9f/0xc0 [kvm_intel] Mar 25 16:18:30 abydos kernel: [ 1319.549213] Modules linked in: wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libblake2s blake2s_x86_64 libcurve25519_generic libchacha libblake2s_generic xt_HL xt_MASQUERADE xt_TCPMSS xt_tcpudp binfmt_misc rbd unix_diag nf_conntrack_netlink veth ceph libceph fscache netfs zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_raw iptable_mangle iptable_nat iptable_filter bpfilter nf_tables vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock shiftfs sch_ingress geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 8021q garp mrp nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm rapl intel_cstate Mar 25 16:18:30 abydos kernel: [ 1319.549305] efi_pstore joydev input_leds cdc_acm mei_me mei ioatdma bridge stp llc bonding acpi_ipmi tls ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter acpi_pad mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid ast drm_vram_helper drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul fb_sys_fops crc32_pclmul ghash_clmulni_intel cec nvme rc_core aesni_intel crypto_simd ixgbe igb i2c_i801 xfrm_algo nvme_core drm i2c_smbus ahci i2c_algo_bit cryptd lpc_ich dca xhci_pci mdio libahci xhci_pci_renesas wmi Mar 25 16:18:30 abydos kernel: [ 1319.549394] CPU: 12 PID: 15052 Comm: qemu-system-x86 Tainted: P O 5.13.0-39-generic #44~20.04.1-Ubuntu Mar 25 16:18:30 abydos kernel: [ 1319.549399] Hardware name: Supermicro PIO-618U-T4T+-ST031/X10DRU-i+, BIOS 3.2a 11/19/2019 Mar 25 16:18:30 abydos kernel: [ 1319.549402] RIP: 0010:vmx_sync_pir_to_irr+0x9f/0xc0 [kvm_intel] Mar 25 16:18:30 abydos kernel: [ 1319.549415] Code: 83 c4 10 5b 5d c3 48 89 df e8 5d dc eb fd 8b 93 00 03 00 00 89 45 ec 83 e2 20 85 d2 75 d2 89 c7 e8 f6 fd ff ff 8b 45 ec eb c6 <0f> 0b eb 86 f0 80 4b 39 40 8b 93 00 03 00 00 8b 45 ec 83 e2 20 eb Mar 25 16:18:30 abydos kernel: [ 1319.549419] RSP: 0018:aed30c577cd8 EFLAGS: 00010246 Mar 25 16:18:30 abydos kernel: [ 1319.549423] RAX: RBX: 98162a4f8000 RCX: Mar 25 16:18:30 abydos kernel: [ 1319.549425] RDX: 0400 RSI: c0c38509 RDI: 98162a4f8000 Mar 25 16:18:30 abydos kernel: [ 1319.549428] RBP: aed30c577cf0 R08: 0400 R09: 98161e73fc00 Mar 25 16:18:30 abydos kernel: [ 1319.549430] R10: R11: R12: 98162a4f8000 Mar 25 16:18:30 abydos kernel: [ 1319.549433] R13: 7f272bff9dd0 R14: 98161e73fc00 R15: 98162a4f8000 Mar 25 16:18:30 abydos kernel: [ 1319.549435] FS: 7f272bffe700() GS:981c9f80() knlGS: Mar 25 16:18:30 abydos kernel: [ 1319.549439] CS: 0010 DS: ES: CR0: 80050033 Mar 25 16:18:30 abydos kernel: [ 1319.549442] CR2: 7f2a31708001 CR3: 0009ea4ac001 CR4: 001726e0 Mar 25 16:18:30 abydos kernel: [ 1319.549445] Call Trace: Mar 25 16:18:30 abydos kernel: [ 1319.549447] Mar 25 16:18:30 abydos kernel: [ 1319.549450] kvm_arch_vcpu_ioctl+0x8fd/0x1260 [kvm] Mar 25 16:18:30 abydos kernel: [ 1319.549590] ? kvm_arch_vcpu_ioctl+0xc1/0x1260 [kvm] Mar 25 16:18:30 abydos kernel: [ 1319.549659] ? kfree+0xd8/0x2a0 Mar 25 16:18:30 abydos kernel: [ 1319.549669] kvm_vcpu_ioctl+0x3a7/0x5f0 [kvm] Mar 25 16:18:30 abydos kernel: [ 1319.549720] ? __fget_light+0xce/0xf0 Mar 25 16:18:30 abydos kernel: [ 1319.549728] __x64_sys_ioctl+0x91/0xc0 Mar 25 16:18:30 abydos kernel: [ 1319.549734] do_syscall_64+0x61/0xb0 Mar 25 16:18:30 abydos kernel: [ 1319.549739] ? do_syscall_64+0x6e/0xb0 Mar 25 16:18:30 abydos kernel: [ 1319.549742] ? syscall_exit_to_user_mode+0x27/0x50 Mar 25 16:18:30 abydos kernel: [ 1319.549747] ? do_syscall_64+0x6e/0xb0 Mar 25 16:18:30 abydos kernel: [ 1319.549750] ? syscall_exit_to_user_mode+0x27/0x50 Mar 25 16:18:30 abydos kernel: [ 1319.549755] ? do_syscall_64+0x6e/0xb0 Mar 25 16:18:30 abydos kernel: [ 1319.549758] entry_SYSCALL_64_after_hwframe+0x44/0xae Mar 25 16:18:30 abydos kernel: [ 1319.549771] RIP: 0033:0x7f2a3b2b33db Mar 25 16:18:30 abydos kernel: [ 1319.549775] Code: 0f 1e fa 48 8b 05 b5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 0
[Kernel-packages] [Bug 1966499] Re: Recent 5.13 kernel has broken KVM support
This repeats in a loop and fills tens of GBs of space with kernel logs in just a few minutes before crashing the entire system. -- 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/1966499 Title: Recent 5.13 kernel has broken KVM support Status in linux package in Ubuntu: Confirmed Bug description: Upgrading to 5.13.0-37 or 5.13.0-39 immediately crashes my production servers as they hit: https://lore.kernel.org/all/f1ea22d3-cff8-406a-ad6a-cb8e0124a...@leemhuis.info/T/#md1f5c8c4aa01130a449a47f3e7559f06b0372f55 It looks like we need to get e90e51d5f01d included in those kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966499/+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 1966499] Re: Recent 5.13 kernel has broken KVM support
5.13.0-38.43 has the fix but 5.13.0-39.44 doesn't, presumably because -39 includes urgent security fixes. -- 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/1966499 Title: Recent 5.13 kernel has broken KVM support Status in linux package in Ubuntu: Confirmed Bug description: Upgrading to 5.13.0-37 or 5.13.0-39 immediately crashes my production servers as they hit: https://lore.kernel.org/all/f1ea22d3-cff8-406a-ad6a-cb8e0124a...@leemhuis.info/T/#md1f5c8c4aa01130a449a47f3e7559f06b0372f55 It looks like we need to get e90e51d5f01d included in those kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966499/+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 1966499] Re: Recent 5.13 kernel has broken KVM support
Ah yeah, that could be. I figured I'd test what's in -proposed but if -proposed is a security only fix on top of -37, that wouldn't help much. It's a bit frustrating because users would have gotten the busted kernel as part of -37 which includes a security fix but then the only real option to get a booting system back now is to go to pre-security-fix. Unfortunately this is a production server and I already spent half of the week dealing with this mess so don't have more time to play kernel bingo. Server is now running a clean upstream build. -- 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/1966499 Title: Recent 5.13 kernel has broken KVM support Status in linux package in Ubuntu: Confirmed Bug description: Upgrading to 5.13.0-37 or 5.13.0-39 immediately crashes my production servers as they hit: https://lore.kernel.org/all/f1ea22d3-cff8-406a-ad6a-cb8e0124a...@leemhuis.info/T/#md1f5c8c4aa01130a449a47f3e7559f06b0372f55 It looks like we need to get e90e51d5f01d included in those kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966499/+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 1966432] Re: audio crackling on usb sound card
I'm having similar issues on my Linux Mint 20.3. My onboard sound card (detected as USB Audio) is now broken. The sound coming out is just popping in and out and crackling. My Mainboard is the Z590 AORUS ULTRA. According to the spec sheet, this board used the "Realtek® ALC4080 codec", whatever that means. Hope this helps. I reverted back to 5.13.0-35 and my audio is working again. FYI SPDIF and 5.1 Surround also did never work with this sound chip / mainboard. -- 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/1966432 Title: audio crackling on usb sound card Status in linux package in Ubuntu: Incomplete Bug description: After the regular updates (on 20.04 and 21.10) audio had crackling noise on the USB audio interface, while it was normal on the internal audio. Tried with different sound cards (presonus audiobox, behringer xenyx q802) and three different machines. Might be in the kernel 5.13.0-37 Reverting to that kernel removed the problem: linux- image-5.13.0-35-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966432/+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 1966066] Re: audio from external sound card is distorted
I have this issue too. Hardware is a different external USB DAC (not Focusrite): $ lsusb | grep DAC Bus 005 Device 004: ID 08bb:2704 Texas Instruments PCM2704 16-bit stereo audio DAC Symptoms: Clicking sounds. Irregular but pretty frequent, up to once a second. It happens on kernel 5.13.0-37, but it goes away if I revert to 5.13.0-35. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1966066 Title: audio from external sound card is distorted Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: The sound card is a Focusrite Scarlett 2i2. The sound is distorted everywhere. Sound via HDMI works. Seen others having the same problem: (Edit because of previously wrong link here) https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card ubuntu release: Ubuntu 20.04.4 LTS package name involved in bug: linux-image-5.13.0-37-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 12:56:02 2022 InstallationDate: Installed on 2020-12-18 (459 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966066/+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 1960633] Re: Move virtual graphics drivers from linux-modules-extra to linux-modules
It turns out the Bionic verification failed because the required changes
went into 5.4.0-106.120~18.04.1 but were dropped from
5.4.0-107.121~18.04.1. Presumably because the later address multiple
CVEs.
--
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/1960633
Title:
Move virtual graphics drivers from linux-modules-extra to linux-
modules
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
Fix Released
Bug description:
[SRU justification]
Impact: We split the drivers into linux-modules and linux-modules-extra. The
latter is only included for setups geared towards real hardware (desktops,
laptops). For VM guests the recommended setup is to use linux-virtual which
does not include linux-modules-extra but also does not depend on other
packages, like linux-firmware.
We already include most VM related drivers in the linux-modules package and
vboxvideo (since 21.10/Impish). So it makes sense to include the missing ones.
Fix: Move the following modules from linux-modules-extra into linux-modules:
- bochs-drm (though a bit aged, this was the predecessor of qemu)
- cirrus (this is a standard emulated gfx card, might not give the best
performance but better than nothing)
- virtio-gpu (KVM)
- vmwgfx (VMWare)
- drm-xen-front (Xen)
Testcase: Check linux-modules for the mentioned modules.
Regression Potential: There should be no change noticeable. Users with
linux-modules-extra installed will see no difference and those without
have additional drivers. Maybe this shows as moving from low-
resolution graphics to higher ones which maybe perform less.
--- Original Description ---
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains
kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko, so at the moment I need to
keep it installed and updated. The only way to do so conveniently is
to install linux-image-generic, which also pulls in linux-firmware,
which is ~760MB installed.
If vmwgfx was moved from linux-modules-extra to linux-modules, I could
use linux-image-virtual instead of linux-image-generic, remove linux-
firmware, linux-modules-extra, and the microcode packages, saving
substantial disk space and bandwidth.
Other virtual graphics drivers in linux-modules-extra that might be
worth moving are:
kernel/drivers/gpu/drm/bochs/bochs-drm.ko
kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
kernel/drivers/gpu/drm/xen/drm_xen_front.ko
Thank you for your consideration.
Note: Edited significantly in response to
https://lists.ubuntu.com/archives/kernel-
team/2022-February/128103.html and
https://lists.ubuntu.com/archives/kernel-
team/2022-February/128104.html to better reflect the underlying
problem and solution.
P.S. There are three other drivers in linux-modules-extra that seem
VMWare-related, but they are not in use in my VM and I don't know
whether they are in common enough use to justify moving them to linux-
modules. I have listed them here for completeness.
kernel/drivers/net/vsockmon.ko
kernel/drivers/ptp/ptp_vmw.ko
kernel/drivers/infiniband/hw/vmw_pvrdma/vmw_pvrdma.ko
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/p
[Kernel-packages] [Bug 1960213] Re: Kernel Panic on linux-image-5.15.0-18-generic
Have the same on 5.15.0-23-generic
** Attachment added: "IMG_20220320_095041.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960213/+attachment/5573000/+files/IMG_20220320_095041.jpg
--
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/1960213
Title:
Kernel Panic on linux-image-5.15.0-18-generic
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hello. Get a Kernel Panic on linux-image-5.15.0-18-generic
The same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957012
On 5.13.0-29-generic boot successfully.
Laptop: Lenovo
Model: 20RA002SRT
Stack trace in attached images.
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.13.0-29-generic.
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: CX8070 Analog [CX8070 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: grid 2375 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xb131c000 irq 149'
Mixer name : 'Conexant CX8070'
Components : 'HDA:14f11f86,17aa5079,00100100
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 14
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Ubuntu 20.04
MachineType: LENOVO 20RA002SRT
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-29-generic
root=/dev/mapper/vg_core-sys ro ipv6.disable=1 quiet splash iommu=soft
resume=/dev/vg_core/sys resume_offset=34816 crashkernel=512M-:192M vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-29.32~20.04.1-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-29-generic N/A
linux-backports-modules-5.13.0-29-generic N/A
linux-firmware 1.187.26
Tags: focal
Uname: Linux 5.13.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: dialout docker plugdev tty uucp vboxusers wireshark
WifiSyslog:
_MarkForUpload: True
dmi.bios.date: 09/15/2021
dmi.bios.release: 1.19
dmi.bios.vendor: LENOVO
dmi.bios.version: R16ET33W (1.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20RA002SRT
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrR16ET33W(1.19):bd09/15/2021:br1.19:efr1.13:svnLENOVO:pn20RA002SRT:pvrThinkPadE14:rvnLENOVO:rn20RA002SRT:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20RA_BU_SMB_FM_ThinkPadE14:
dmi.product.family: ThinkPad E14
dmi.product.name: 20RA002SRT
dmi.product.sku: LENOVO_MT_20RA_BU_SMB_FM_ThinkPad E14
dmi.product.version: ThinkPad E14
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960213/+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 1960213] Re: Kernel Panic on linux-image-5.15.0-18-generic
** Attachment added: "IMG_20220320_095120.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960213/+attachment/5573001/+files/IMG_20220320_095120.jpg
--
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/1960213
Title:
Kernel Panic on linux-image-5.15.0-18-generic
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hello. Get a Kernel Panic on linux-image-5.15.0-18-generic
The same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957012
On 5.13.0-29-generic boot successfully.
Laptop: Lenovo
Model: 20RA002SRT
Stack trace in attached images.
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.13.0-29-generic.
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: CX8070 Analog [CX8070 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: grid 2375 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xb131c000 irq 149'
Mixer name : 'Conexant CX8070'
Components : 'HDA:14f11f86,17aa5079,00100100
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 14
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Ubuntu 20.04
MachineType: LENOVO 20RA002SRT
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-29-generic
root=/dev/mapper/vg_core-sys ro ipv6.disable=1 quiet splash iommu=soft
resume=/dev/vg_core/sys resume_offset=34816 crashkernel=512M-:192M vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-29.32~20.04.1-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-29-generic N/A
linux-backports-modules-5.13.0-29-generic N/A
linux-firmware 1.187.26
Tags: focal
Uname: Linux 5.13.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: dialout docker plugdev tty uucp vboxusers wireshark
WifiSyslog:
_MarkForUpload: True
dmi.bios.date: 09/15/2021
dmi.bios.release: 1.19
dmi.bios.vendor: LENOVO
dmi.bios.version: R16ET33W (1.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20RA002SRT
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrR16ET33W(1.19):bd09/15/2021:br1.19:efr1.13:svnLENOVO:pn20RA002SRT:pvrThinkPadE14:rvnLENOVO:rn20RA002SRT:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20RA_BU_SMB_FM_ThinkPadE14:
dmi.product.family: ThinkPad E14
dmi.product.name: 20RA002SRT
dmi.product.sku: LENOVO_MT_20RA_BU_SMB_FM_ThinkPad E14
dmi.product.version: ThinkPad E14
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960213/+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 1786013] Autopkgtest regression report (linux-meta-oracle-5.4/5.4.0.1068.73~18.04.47)
All autopkgtests for the newly accepted linux-meta-oracle-5.4 (5.4.0.1068.73~18.04.47) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxc/3.0.3-0ubuntu1~18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.4.0.1061.60)
All autopkgtests for the newly accepted linux-meta-kvm (5.4.0.1061.60) for focal have finished running. The following regressions have been reported in tests triggered by the package: lttng-modules/2.12.5-1ubuntu2~20.04.1 (amd64) rtl8821ce/5.5.2.1-0ubuntu4~20.04.4 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.3 (amd64) oss4/4.2-build2010-5ubuntu6~20.04.3 (amd64) v4l2loopback/0.12.3-1ubuntu0.4 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64) virtualbox/6.1.32-dfsg-1~ubuntu1.20.04.1 (amd64) sl-modem/2.9.11~20110321-16ubuntu1 (amd64) evdi/1.9.1-1ubuntu4~20.04.1 (amd64) glibc/2.31-0ubuntu9.7 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-kvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902748] Re: ubuntu-seed / ubuntu-boot partition detection could be improved
** Changed in: snapd Assignee: Ian Johnson (anonymouse67) => (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/1902748 Title: ubuntu-seed / ubuntu-boot partition detection could be improved Status in snapd: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: ubuntu-seed / ubuntu-boot partition detection could be improved Currently in the initrd, snapd-bootstrap searches for ubuntu-boot / ubuntu-seed partition by label or by UEFI variable that was set by sd- boot. sdboot uses devicepath UEFI protocol to establish MEDIA_DEVICE_PATH, HARDDRIVE_DEVICEPATH, GUID, Signature aka partuuid that was used to boot. https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Protocol/DevicePath.h This is nice, but not unique enough. It would be nice if we were able to modify sd-boot stub to export something more specific that ideally maps to a sysfs path. For example PCI_DEVICE_PATH, SCSI_DEVICE_PATH, SATA_DEVICE_PATH, USB_DEVICE_PATH, NVME_NAMESPACE_DEVICE_PATH, SD_DEVICE_PATH, UFS_DEVICE_PATH, EMMC_DEVICE_PATH or some such. That way initrd would be able to resolve better which block device to key off. Given that EFI device handle is passed to the kernel, doesn't kernel also know where it came from? or not? To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1902748/+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 1962414] Re: screen white line coming at bottom
Hi I have tried it but i think this is not the issue of laptop display as i noticed whenever i hover my mouse at top bar little of the mouse pointer is seen in the bottom pannel . And when i use to move the mouse from left to right or vice - versa at top bar the half mouse pointer is showing at bottom pannel(dash-to-dock) . i dont know may be next update of LTS version of ubuntu may solve it . but its coming in jammy jellyfish version also . ** Attachment added: "Screenshot from 2022-03-26 03-46-05.png" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1962414/+attachment/5573047/+files/Screenshot%20from%202022-03-26%2003-46-05.png -- 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/1962414 Title: screen white line coming at bottom Status in linux-hwe-5.13 package in Ubuntu: Incomplete Bug description: white line coming at the bottom of the screen ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 28 02:37:14 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:225a] InstallationDate: Installed on 2021-07-01 (241 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard HP EliteBook 820 G2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=3a425ccf-6b17-4740-a951-62415983b2e2 ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.release: 1.4 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M71 Ver. 01.04 dmi.board.name: 225A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 96.54 dmi.chassis.asset.tag: 5CG5172BFZ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 150.84 dmi.modalias: dmi:bvnHewlett-Packard:bvrM71Ver.01.04:bd02/24/2015:br1.4:efr150.84:svnHewlett-Packard:pnHPEliteBook820G2:pvrA3009C510203:rvnHewlett-Packard:rn225A:rvrKBCVersion96.54:cvnHewlett-Packard:ct10:cvr:skuN3F11EC#AB4: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 820 G2 dmi.product.sku: N3F11EC#AB4 dmi.product.version: A3009C510203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 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 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1962414/+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 1786013] Autopkgtest regression report (linux-meta-oracle/5.13.0.1024.24)
All autopkgtests for the newly accepted linux-meta-oracle (5.13.0.1024.24) for impish have finished running. The following regressions have been reported in tests triggered by the package: systemd/248.3-1ubuntu8.2 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/impish/update_excuses.html#linux-meta-oracle [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.4.0.107.111)
All autopkgtests for the newly accepted linux-meta (5.4.0.107.111) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.15 (amd64) snapd/2.54.3+20.04.1ubuntu0.2 (arm64) lxc/1:4.0.6-0ubuntu1~20.04.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964827] Re: zfs-linux upstream at 2.1.3, jammy has 2.1.2
Yes, would be really important to still get the fixes in zfs-2.1.3 into jammy. I'd love to see that too! -- 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/1964827 Title: zfs-linux upstream at 2.1.3, jammy has 2.1.2 Status in zfs-linux package in Ubuntu: Confirmed Bug description: I know Jammy is in freeze zfs upstream is now at 2.1.3, which has a lovely set of fixes for issues I have noticed (such as zfs complaining when waking for sleep, and also patches to support 5.16 better and also for the support of 5.17.) Please peruse the large number of important patches, which will make supporting this in LTS much easier: https://github.com/openzfs/zfs/pull/13063 I'm running a version of https://launchpad.net/~jonathonf/+archive/ubuntu/zfs built for 2.1.3 on Ubuntu mainline kernel 5.17-rc8 on multiple Jammy-dev systems, and it works beautifully. I have attached the debian dir I put on top of the 2.1.3 source release which I used to generate debs for this release, which I have tested on a server and client desktop x86_64 machine running Ubuntu Jammy 22.04 (as of March 14, 2022). I am having no zfs related issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964827/+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 1940724] Re: 20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2
apport information ** Tags added: apport-collected ** Description changed: I am trying Ubuntu MATE 20.04.2 to see what works and what is broken. My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS A88XM-A motherboard via USB2 cable. With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it cannot find my scanner at all. I tried the bundled Document Scanner app. It finds the scanner but cannot connect to it to actually scan. Apparently, something is wrong with connecting a scanner with a USB cable. If you need more information, please tell me how to get it and send it to you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.35 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: MATE Date: Fri Aug 20 18:56:53 2021 InstallationDate: Installed on 2021-04-17 (125 days ago) InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: robert 1572 F pulseaudio + /dev/snd/controlC0: robert 1572 F pulseaudio + /dev/snd/pcmC0D3p: robert 1572 F...m pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: MATE + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2022-03-05 (21 days ago) + InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) + MachineType: System manufacturer System Product Name + Package: linux (not installed) + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash + ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-35-generic N/A + linux-backports-modules-5.13.0-35-generic N/A + linux-firmware 1.187.29 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: focal + Uname: Linux 5.13.0-35-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: 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 ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1940724/+attachment/5573081/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940724 Title: 20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2 Status in linux package in Ubuntu: Expired Bug description: I am trying Ubuntu MATE 20.04.2 to see what works and what is broken. My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS A88XM-A motherboard via USB2 cable. With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it cannot find my scanner at all. I tried the bundled Document Scanner app. It finds the scanner but cannot connect to it to actually scan. Apparently, something is wrong with connecting a scanner with a USB cable. If you need more information, please tell me how to get it and send it to you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.35 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: MATE Date: Fri Aug 20 18:56:53 2021 InstallationDate: Installed on 2021-04-17 (125 days ago) InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all
