[Kernel-packages] [Bug 1950029] [NEW] Suspend "Wait until snapd is fully seeded"
Public bug reported: Using Lenovo IdeaPad 3i Gaming, I got a software update this morning, and since that time, impossible to complete a power suspend. It is always blocked after the message "Finished Wait until snapd is fully seeded". Power Down is working well. Logout is working well. Only the Suspend action is blocked on this message mentioned above. - It is a regression bug, it was not happening before the latest update. - Reproduced by following ways to suspend the computer : - systemctl suspend - Via Ubuntu down arrow on top left menu bar, Power Down / Logout --> Suspend. - Closing the lid Bug reported with 'ubuntu-bug linux' cf picture in attachment on all messages seen before the system gets hanged with the final "Finished Wait until snapd is fully seeded" message. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 5 17:50:25 2021 InstallationDate: Installed on 2021-04-26 (193 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Terminal messages on Suspend action" https://bugs.launchpad.net/bugs/1950029/+attachment/5538501/+files/IMG_20211105_143122.jpg -- 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/1950029 Title: Suspend "Wait until snapd is fully seeded" Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Using Lenovo IdeaPad 3i Gaming, I got a software update this morning, and since that time, impossible to complete a power suspend. It is always blocked after the message "Finished Wait until snapd is fully seeded". Power Down is working well. Logout is working well. Only the Suspend action is blocked on this message mentioned above. - It is a regression bug, it was not happening before the latest update. - Reproduced by following ways to suspend the computer : - systemctl suspend - Via Ubuntu down arrow on top left menu bar, Power Down / Logout --> Suspend. - Closing the lid Bug reported with 'ubuntu-bug linux' cf picture in attachment on all messages seen before the system gets hanged with the final "Finished Wait until snapd is fully seeded" message. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 5 17:50:25 2021 InstallationDate: Installed on 2021-04-26 (193 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1950029/+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 1668105]
On Fri, Nov 05, 2021 at 10:54:24AM +, bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=115741 > > --- Comment #19 from Tobias Bachmann (tobachm...@gmx.de) --- > Starting with kernel 5.14.14 I can't boot anymore. XHCI dies early on and > won't > allow me to decrypt my LUKS encrypted root partition. Different issue, should be fixed in the next 5.14.y release: https://lore.kernel.org/r/42bcbea6-5eb8-16c7-336a-2cb72e71b...@redhat.com -- 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/1668105 Title: xhci_hcd module turns off usb host controller on boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: So we know this xhci_kcd was always shit in that it turns off the console usb keyboard for long running computers and that it on abrupt termination of Linux puts usb in a 12x slower mode. It is buggy, it was always buggy, and its getting worse. With Linux 4.8.0-37, this crappy software decides to halt the host controller on boot, ie. turn off the console keyboard preventing any boot. I cannot think of any situation where anyone would want their host controller halted. This is MacBook Pro 2015. So, it's already broken in UEFI-grub as it always was, ie. every key press takes 8 seconds, but you only need two, so you can boot in 16 s. I tried to disable the xhci_kcd crap by using kernel parameter noxhci_port_switch or modprobe.blacklist=xhci_hcd neither which works. Because it has crap in UEFI, the computer will not boot any external hard drive or usb fob. The only thing that works is Apple rescue that gets rid of the xhci garbage, and the boot os x immediately after that. So the log output xhci_hcd :00:14.0: Timeout while waiting for setup device command xhci_hcd :00:14.0: xHCI host not responding to stop endpoint command. - and a bit later: xhci_hcd :00:14.0: Assuming host is dying, halting host. xhci_hcd :00:14.0: HC died; cleaning up This clown programming of Linux has to stop. Why would anyone ever want their host controller halted? --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: foxyboy5662 F pulseaudio /dev/snd/controlC0: foxyboy5662 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=/dev/mapper/C89-SWAP MachineType: Apple Inc. MacBookPro12,1 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic root=/dev/mapper/C89-RFS ro i915.enable_rc6=0 ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-39-generic N/A linux-backports-modules-4.8.0-39-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.8.0-39-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-11-16 (108 days ago) UserGroups: adm docker libvirt libvirtd sudo _MarkForUpload: True dmi.bios.date: 10/26/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B15.1510261437 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B15.1510261437:bd10/26/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1668105/+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 1668105]
Starting with kernel 5.14.14 I can't boot anymore. XHCI dies early on and won't allow me to decrypt my LUKS encrypted root partition. -- 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/1668105 Title: xhci_hcd module turns off usb host controller on boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: So we know this xhci_kcd was always shit in that it turns off the console usb keyboard for long running computers and that it on abrupt termination of Linux puts usb in a 12x slower mode. It is buggy, it was always buggy, and its getting worse. With Linux 4.8.0-37, this crappy software decides to halt the host controller on boot, ie. turn off the console keyboard preventing any boot. I cannot think of any situation where anyone would want their host controller halted. This is MacBook Pro 2015. So, it's already broken in UEFI-grub as it always was, ie. every key press takes 8 seconds, but you only need two, so you can boot in 16 s. I tried to disable the xhci_kcd crap by using kernel parameter noxhci_port_switch or modprobe.blacklist=xhci_hcd neither which works. Because it has crap in UEFI, the computer will not boot any external hard drive or usb fob. The only thing that works is Apple rescue that gets rid of the xhci garbage, and the boot os x immediately after that. So the log output xhci_hcd :00:14.0: Timeout while waiting for setup device command xhci_hcd :00:14.0: xHCI host not responding to stop endpoint command. - and a bit later: xhci_hcd :00:14.0: Assuming host is dying, halting host. xhci_hcd :00:14.0: HC died; cleaning up This clown programming of Linux has to stop. Why would anyone ever want their host controller halted? --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: foxyboy5662 F pulseaudio /dev/snd/controlC0: foxyboy5662 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=/dev/mapper/C89-SWAP MachineType: Apple Inc. MacBookPro12,1 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic root=/dev/mapper/C89-RFS ro i915.enable_rc6=0 ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-39-generic N/A linux-backports-modules-4.8.0-39-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.8.0-39-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-11-16 (108 days ago) UserGroups: adm docker libvirt libvirtd sudo _MarkForUpload: True dmi.bios.date: 10/26/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B15.1510261437 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B15.1510261437:bd10/26/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1668105/+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 1950014] Re: Focal update: v5.4.153 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.153 upstream stable release + from git://git.kernel.org/ -v5.4.153 upstream stable release -from git://git.kernel.org/ + Partially revert "usb: Kconfig: using select for USB_COMMON dependency" + USB: cdc-acm: fix racy tty buffer accesses + USB: cdc-acm: fix break reporting + usb: typec: tcpm: handle SRC_STARTUP state if cc changes + xen/privcmd: fix error handling in mmap-resource processing + mmc: meson-gx: do not use memcpy_to/fromio for dram-access-quirk + ovl: fix missing negative dentry check in ovl_rename() + nfsd: fix error handling of register_pernet_subsys() in init_nfsd() + nfsd4: Handle the NFSv4 READDIR 'dircount' hint being zero + xen/balloon: fix cancelled balloon action + ARM: dts: omap3430-sdp: Fix NAND device node + ARM: dts: qcom: apq8064: use compatible which contains chipid + MIPS: BPF: Restore MIPS32 cBPF JIT + bpf, mips: Validate conditional branch offsets + soc: qcom: socinfo: Fixed argument passed to platform_set_data() + ARM: dts: qcom: apq8064: Use 27MHz PXO clock as DSI PLL reference + soc: qcom: mdt_loader: Drop PT_LOAD check on hash segment + ARM: dts: imx: Add missing pinctrl-names for panel on M53Menlo + ARM: dts: imx: Fix USB host power regulator polarity on M53Menlo + arm64: dts: qcom: pm8150: use qcom,pm8998-pon binding + xtensa: move XCHAL_KIO_* definitions to kmem_layout.h + xtensa: use CONFIG_USE_OF instead of CONFIG_OF + xtensa: call irqchip_init only when CONFIG_USE_OF is selected + bpf, arm: Fix register clobbering in div/mod implementation + bpf: Fix integer overflow in prealloc_elems_and_freelist() + phy: mdio: fix memory leak + net_sched: fix NULL deref in fifo_set_limit() + powerpc/fsl/dts: Fix phy-connection-type for fm1mac3 + ptp_pch: Load module automatically if ID matches + arm64: dts: freescale: Fix SP805 clock-names + arm64: dts: ls1028a: add missing CAN nodes + ARM: imx6: disable the GIC CPU interface before calling stby-poweroff sequence + net: bridge: use nla_total_size_64bit() in br_get_linkxstats_size() + net/sched: sch_taprio: properly cancel timer from taprio_destroy() + net: sfp: Fix typo in state machine debug string + netlink: annotate data races around nlk->bound + bus: ti-sysc: Use CLKDM_NOAUTO for dra7 dcan1 for errata i893 + video: fbdev: gbefb: Only instantiate device when built for IP32 + drm/nouveau/debugfs: fix file release memory leak + gve: Correct available tx qpl check + rtnetlink: fix if_nlmsg_stats_size() under estimation + gve: fix gve_get_stats() + i40e: fix endless loop under rtnl + i40e: Fix freeing of uninitialized misc IRQ vector + net: prefer socket bound to interface when not in VRF + i2c: acpi: fix resource leak in reconfiguration device addition + bpf, s390: Fix potential memory leak about jit_data + RISC-V: Include clone3() on rv32 + x86/platform/olpc: Correct ifdef symbol to intended CONFIG_OLPC_XO15_SCI + x86/hpet: Use another crystalball to evaluate HPET usability + x86/Kconfig: Correct reference to MWINCHIP3D + Linux 5.4.153 + UBUNTU: upstream stable to v5.4.153 -- 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/1950014 Title: Focal update: v5.4.153 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backpor
[Kernel-packages] [Bug 1942759] Re: No touchpad detected on 'HP ZBook Firefly G8 (1G3U1AV)' after fresh install
@aseligmann Installing Ubuntu 20.04 LTS does solve the trackpad issue together with the GPU driver and audio. Unfortunately for compatibility reasons I have to use 18.04 so I guess I'm stuck with a mouse for now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1942759 Title: No touchpad detected on 'HP ZBook Firefly G8 (1G3U1AV)' after fresh install Status in linux-signed-hwe-5.4 package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.5 LTS The touchpad is not detected with or without the Logitech M705 mouse plugged in. cat /proc/bus/input/devices Outputs: I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=20 0 0 1500f0210 43803078f900d401 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=046d Product=101b Version=0111 N: Name="Logitech M705" P: Phys=usb-:00:14.0-4/input2:1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.2/0003:046D:C52B.0004/0003:046D:101B.0005/input/input14 U: Uniq=101b-fc-92-33-df H: Handlers=mouse0 event5 B: PROP=0 B: EV=17 B: KEY= 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="HP Wireless hotkeys" P: Phys=hpq6001/input0 S: Sysfs=/devices/virtual/input/input15 U: Uniq= H: Handlers=rfkill kbd event6 B: PROP=0 B: EV=3 B: KEY=80 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID events" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input16 U: Uniq= H: Handlers=rfkill kbd event7 B: PROP=0 B: EV=13 B: KEY=810003 504000 1e29400020 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID 5 button array" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input17 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=13 B: KEY=2 0 0 0 0 1 0 201c 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="HP WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input18 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=33 B: KEY=40 0 10007 2102400 0 0 B: MSC=10 B: SW=0 I: Bus=0003 Vendor=04f2 Product=b6bf Version=0013 N: Name="HP HD Camera: HP HD Camera" P: Phys=usb-:00:14.0-2/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-2/3-2:1.0/input/input19 U: Uniq= H: Handlers=kbd event10 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0003 Vendor=04f2 Product=b6bf Version=0013 N: Name="HP HD Camera: HP IR Camera" P: Phys=usb-:00:14.0-2/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-2/3-2:1.2/input/input20 U: Uniq= H: Handlers=kbd event11 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-81-generic 5.4.0-81.91~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 6 11:37:52 2021 InstallationDate: Installed on 2021-09-06 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) SourcePackage: linux-signed-hwe-5.4 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.4/+bug/1942759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1950014] [NEW] Focal update: v5.4.153 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.153 upstream stable release from git://git.kernel.org/ Partially revert "usb: Kconfig: using select for USB_COMMON dependency" USB: cdc-acm: fix racy tty buffer accesses USB: cdc-acm: fix break reporting usb: typec: tcpm: handle SRC_STARTUP state if cc changes xen/privcmd: fix error handling in mmap-resource processing mmc: meson-gx: do not use memcpy_to/fromio for dram-access-quirk ovl: fix missing negative dentry check in ovl_rename() nfsd: fix error handling of register_pernet_subsys() in init_nfsd() nfsd4: Handle the NFSv4 READDIR 'dircount' hint being zero xen/balloon: fix cancelled balloon action ARM: dts: omap3430-sdp: Fix NAND device node ARM: dts: qcom: apq8064: use compatible which contains chipid MIPS: BPF: Restore MIPS32 cBPF JIT bpf, mips: Validate conditional branch offsets soc: qcom: socinfo: Fixed argument passed to platform_set_data() ARM: dts: qcom: apq8064: Use 27MHz PXO clock as DSI PLL reference soc: qcom: mdt_loader: Drop PT_LOAD check on hash segment ARM: dts: imx: Add missing pinctrl-names for panel on M53Menlo ARM: dts: imx: Fix USB host power regulator polarity on M53Menlo arm64: dts: qcom: pm8150: use qcom,pm8998-pon binding xtensa: move XCHAL_KIO_* definitions to kmem_layout.h xtensa: use CONFIG_USE_OF instead of CONFIG_OF xtensa: call irqchip_init only when CONFIG_USE_OF is selected bpf, arm: Fix register clobbering in div/mod implementation bpf: Fix integer overflow in prealloc_elems_and_freelist() phy: mdio: fix memory leak net_sched: fix NULL deref in fifo_set_limit() powerpc/fsl/dts: Fix phy-connection-type for fm1mac3 ptp_pch: Load module automatically if ID matches arm64: dts: freescale: Fix SP805 clock-names arm64: dts: ls1028a: add missing CAN nodes ARM: imx6: disable the GIC CPU interface before calling stby-poweroff sequence net: bridge: use nla_total_size_64bit() in br_get_linkxstats_size() net/sched: sch_taprio: properly cancel timer from taprio_destroy() net: sfp: Fix typo in state machine debug string netlink: annotate data races around nlk->bound bus: ti-sysc: Use CLKDM_NOAUTO for dra7 dcan1 for errata i893 video: fbdev: gbefb: Only instantiate device when built for IP32 drm/nouveau/debugfs: fix file release memory leak gve: Correct available tx qpl check rtnetlink: fix if_nlmsg_stats_size() under estimation gve: fix gve_get_stats() i40e: fix endless loop under rtnl i40e: Fix freeing of uninitialized misc IRQ vector net: prefer socket bound to interface when not in VRF i2c: acpi: fix resource leak in reconfiguration device addition bpf, s390: Fix potential memory leak about jit_data RISC-V: Include clone3() on rv32 x86/platform/olpc: Correct ifdef symbol to intended CONFIG_OLPC_XO15_SCI x86/hpet: Use another crystalball to evaluate HPET usability x86/Kconfig: Correct reference to MWINCHIP3D Linux 5.4.153 UBUNTU: upstream stable to v5.4.153 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950014 Title: Focal update: v5.4.153 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.153 upstream stable release from git://git.kernel.org/ Partially revert "usb: Kconfig: using select for USB_COMMON dependency" USB: cdc-acm: fix racy tty buffer accesses USB: cdc-acm: fix break reporting usb: typec: tcpm: handle SRC_STARTUP state if cc changes xen/privcmd: fix error handling in mmap-resource processing mmc: meson-gx: do not use memcpy_to/fromio for dram-access-quirk ovl: fix m
[Kernel-packages] [Bug 1950013] Re: Add s0i3 RTC wake up for AMD systems
https://lists.ubuntu.com/archives/kernel-team/2021-November/125521.html -- 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/1950013 Title: Add s0i3 RTC wake up for AMD systems Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] RTC based wakeup is not supported natively by the hardware for s0i3. [Fix] A firmware and driver updates were implemented. The driver passes wakeup time to SMU to to enable RTC from S0i3. Note this s0i3 RTC wake up also requires new firmware. The first patch is the prerequisite actual fix (patch 2 and 3). [Test] This is requested by AMD and tested by an AMD developer as below: Testing a suspend run with RTC for 15 seconds and then 30 seconds: ``` $ sudo rtcwake --seconds 15 -m mem rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:31:45 2021 $ sudo rtcwake --seconds 30 -m mem rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:33:13 2021 $ sudo cat /sys/kernel/debug/amd_pmc/s0ix_stats === S0ix statistics === S0ix Entry Time: 4793618285 S0ix Exit Time: 6209036738 Residency Time: 29487884 ``` Residency divided by 100 is 29.4 seconds. Reading idle mask works fine too. [Where problems could occur] Low risk. First patch only exports Idlemask value. The actual fix only affects a specific AMD CPU (CZN). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950013/+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 1870597]
Was this patch sent to the maintainers? If so, was it applied? -- 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/1870597 Title: libinput says "your system is too slow" Status in GNOME Shell: Unknown Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm- x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Inspiron 5570 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed quiet splash --- ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870597/+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 1950013] [NEW] Add s0i3 RTC wake up for AMD systems
Public bug reported: [Impact] RTC based wakeup is not supported natively by the hardware for s0i3. [Fix] A firmware and driver updates were implemented. The driver passes wakeup time to SMU to to enable RTC from S0i3. Note this s0i3 RTC wake up also requires new firmware. The first patch is the prerequisite actual fix (patch 2 and 3). [Test] This is requested by AMD and tested by an AMD developer as below: Testing a suspend run with RTC for 15 seconds and then 30 seconds: ``` $ sudo rtcwake --seconds 15 -m mem rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:31:45 2021 $ sudo rtcwake --seconds 30 -m mem rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:33:13 2021 $ sudo cat /sys/kernel/debug/amd_pmc/s0ix_stats === S0ix statistics === S0ix Entry Time: 4793618285 S0ix Exit Time: 6209036738 Residency Time: 29487884 ``` Residency divided by 100 is 29.4 seconds. Reading idle mask works fine too. [Where problems could occur] Low risk. First patch only exports Idlemask value. The actual fix only affects a specific AMD CPU (CZN). ** Affects: hwe-next Importance: Undecided Assignee: Alex Hung (alexhung) Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Tags: amd oem-priority originate-from-1947889 ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Description changed: [Impact] - RTC based wakeup is not supported natively by the hardware for s0i3. + RTC based wakeup is not supported natively by the hardware for s0i3. [Fix] - A firmware and driver updates were implemented. The driver passes + A firmware and driver updates were implemented. The driver passes wakeup time to SMU to to enable RTC from S0i3. - Note this s0i3 RTC wake up also requires new firmware. + Note this s0i3 RTC wake up also requires new firmware. - The first patch is the prerequisite actual fix (patch 2 and 3). + The first patch is the prerequisite actual fix (patch 2 and 3). [Test] - This is requested by AMD and tested by an AMD developer as below: + This is requested by AMD and tested by an AMD developer as below: - Testing a suspend run with RTC for 15 seconds and then 30 seconds: - ``` - $ sudo rtcwake --seconds 15 -m mem - rtcwake: assuming RTC uses UTC ... - rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:31:45 2021 - $ sudo rtcwake --seconds 30 -m mem - rtcwake: assuming RTC uses UTC ... - rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:33:13 2021 - $ sudo cat /sys/kernel/debug/amd_pmc/s0ix_stats - === S0ix statistics === - S0ix Entry Time: 4793618285 - S0ix Exit Time: 6209036738 - Residency Time: 29487884 - ``` - Residency divided by 100 is 29.4 seconds. + Testing a suspend run with RTC for 15 seconds and then 30 seconds: + ``` + $ sudo rtcwake --seconds 15 -m mem + rtcwake: assuming RTC uses UTC ... + rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:31:45 2021 + $ sudo rtcwake --seconds 30 -m mem + rtcwake: assuming RTC uses UTC ... + rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:33:13 2021 + $ sudo cat /sys/kernel/debug/amd_pmc/s0ix_stats + === S0ix statistics === + S0ix Entry Time: 4793618285 + S0ix Exit Time: 6209036738 + Residency Time: 29487884 + ``` + Residency divided by 100 is 29.4 seconds. - Reading idle mask works fine too. + Reading idle mask works fine too. [Where problems could occur] - Low risk. + Low risk. - First patch only exports Idlemask value. - The actual fix only affects a specific AMD CPU (CZN). + First patch only exports Idlemask value. + The actual fix only affects a specific AMD CPU (CZN). ** Tags added: amd oem-priority originate-from-1947889 ** Changed in: hwe-next Assignee: (unassigned) => Alex Hung (alexhung) -- 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/1950013 Title: Add s0i3 RTC wake up for AMD systems Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] RTC based wakeup is not supported natively by the hardware for s0i3. [Fix] A firmware and driver updates were implemented. The driver passes wakeup time to SMU to to enable RTC from S0i3. Note this s0i3 RTC wake up also requires new firmware. The first patch is the prerequisite actual fix (patc
[Kernel-packages] [Bug 1950010] [NEW] Upgrading to 1.187.20 results in missing firmware, Nvidia 1650 MaxQ
Public bug reported: On a fresh install of Kubuntu 20.04, I ran sudo apt upgrade, which results in the the following warnings: Setting up linux-firmware (1.187.20) ... update-initramfs: Generating /boot/initrd.img-5.11.0-38-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 update-initramfs: Generating /boot/initrd.img-5.11.0-27-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 Booting to the last installed kernel, 5.11.0-27-generic will allow me to boot into the desktop - however if I were to use a Nvidia driver (460 and 470, non-server), I will have issues getting the computer to sleep, and on one boot I the shutdown greeter kept crashing The following packages were part of the upgrade: esme@Esme-Prestige-14:~$ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: libatomic1:i386 libbsd0:i386 libdpkg-perl libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi7:i386 libfile-fcntllock-perl libglvnd0:i386 libllvm12:i386 libnvidia-cfg1-470 libnvidia-common-470 libnvidia-compute-470:i386 libnvidia-decode-470 libnvidia-decode-470:i386 libnvidia-encode-470 libnvidia-encode-470:i386 libnvidia-extra-470 libnvidia-fbc1-470 libnvidia-gl-470 libnvidia-gl-470:i386 libnvidia-ifr1-470 libpciaccess0:i386 libsensors5:i386 libstdc++6:i386 libvulkan1:i386 libwayland-client0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-randr0:i386 libxcb-shm0:i386 libxcb-sync1:i386 libxcb-xfixes0:i386 libxcb1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 mesa-vulkan-drivers:i386 nvidia-compute-utils-470 nvidia-kernel-source-470 nvidia-prime nvidia-settings nvidia-utils-470 pkg-config screen-resolution-extra xserver-xorg-video-nvidia-470 Use 'sudo apt autoremove' to remove them. The following packages have been kept back: linux-modules-nvidia-470-generic-hwe-20.04 nvidia-kernel-common-470 The following packages will be upgraded: alsa-ucm-conf apport apport-kde bind9-dnsutils bind9-host bind9-libs binutils binutils-common binutils-x86-64-linux-gnu ca-certificates cpio distro-info-data firefox ghostscript ghostscript-x gir1.2-udisks-2.0 libbinutils libcaca0 libctf-nobfd0 libctf0 libcurl3-gnutls libcurl4 libegl-mesa0 libgbm
[Kernel-packages] [Bug 1950009] [NEW] Focal update: v5.4.152 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.152 upstream stable release from git://git.kernel.org/ net: mdio: introduce a shutdown method to mdio device drivers xen-netback: correct success/error reporting for the SKB-with-fraglist case sparc64: fix pci_iounmap() when CONFIG_PCI is not set ext2: fix sleeping in atomic bugs on error scsi: sd: Free scsi_disk device via put_device() usb: testusb: Fix for showing the connection speed usb: dwc2: check return value after calling platform_get_resource() selftests: be sure to make khdr before other targets selftests:kvm: fix get_warnings_count() ignoring fscanf() return warn scsi: ses: Retry failed Send/Receive Diagnostic commands tools/vm/page-types: remove dependency on opt_file for idle page tracking KVM: do not shrink halt_poll_ns below grow_start kvm: x86: Add AMD PMU MSRs to msrs_to_save_all[] perf/x86: Reset destroy callback on event init failure silence nfscache allocation warnings with kvzalloc libata: Add ATA_HORKAGE_NO_NCQ_ON_ATI for Samsung 860 and 870 SSD. Linux 5.4.152 UBUNTU: upstream stable to v5.4.152 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.152 upstream stable release + from git://git.kernel.org/ -v5.4.152 upstream stable release -from git://git.kernel.org/ + net: mdio: introduce a shutdown method to mdio device drivers + xen-netback: correct success/error reporting for the SKB-with-fraglist case + sparc64: fix pci_iounmap() when CONFIG_PCI is not set + ext2: fix sleeping in atomic bugs on error + scsi: sd: Free scsi_disk device via put_device() + usb: testusb: Fix for showing the connection speed + usb: dwc2: check return value after calling platform_get_resource() + selftests: be sure to make khdr before other targets + selftests:kvm: fix get_warnings_count() ignoring fscanf() return warn + scsi: ses: Retry failed Send/Receive Diagnostic commands + tools/vm/page-types: remove dependency on opt_file for idle page tracking + KVM: do not shrink halt_poll_ns below grow_start + kvm: x86: Add AMD PMU MSRs to msrs_to_save_all[] + perf/x86: Reset destroy callback on event init failure + silence nfscache allocation warnings with kvzalloc + libata: Add ATA_HORKAGE_NO_NCQ_ON_ATI for Samsung 860 and 870 SSD. + Linux 5.4.152 + UBUNTU: upstream stable to v5.4.152 -- 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/1950009 Title: Focal update: v5.4.152 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by ori
[Kernel-packages] [Bug 1940860] Re: Mellanox NIC interface names change between 5.4 and 5.8
This also affects the ubuntu-installer when the `d-i base- installer/kernel/override-image string linux-generic-hwe-20.04` flag is added to preseed. The installer loads 5.4 kernel and configure NICs using the 5.4 naming convention, then once the 5.11 kernel is loaded and the host reboots the network config fails. -- 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/1940860 Title: Mellanox NIC interface names change between 5.4 and 5.8 Status in subiquity: New Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Invalid Bug description: I noticed on a couple of systems that my network interface names change when upgrading from the focal LTS (5.4) kernel to the focal HWE (both 5.8 & 5.11) kernels. Both systems have Mellanox Connect-X 5 NICs. dannf@bizzy:~$ uname -a Linux bizzy 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 19:10:30 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux dannf@bizzy:~$ ls /sys/class/net enp1s0f0 enp1s0f1 enx3e8734bc294f lo dannf@bizzy:~$ uname -a Linux bizzy 5.8.0-63-generic #71~20.04.1-Ubuntu SMP Thu Jul 15 17:46:44 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux dannf@bizzy:~$ ls /sys/class/net enp1s0f0np0 enp1s0f1np1 enx3e8734bc294f lo dannf@bizzy:~$ uname -a Linux bizzy 5.11.0-27-generic #29~20.04.1-Ubuntu SMP Wed Aug 11 15:58:08 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux dannf@bizzy:~$ ls /sys/class/net enp1s0f0np0 enp1s0f1np1 enx3e8734bc294f lo I bisected this down to a kernel change: # first bad commit: [c6acd629eec754a9679f922d51f90e44c769b80c] net/mlx5e: Add support for devlink-port in non-representors mode The impact is that your network can fail to come up after transitioning from the LTS kernel to the HWE kernel. Now, this isn't a huge problem for MAAS installs because MAAS configures netplan to always use the same names as were used at commissioning. It does impact subiquity based installs however, which do not. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1940860/+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 1949875] Re: Touchpad not working on Lenovo Flex-5 Ryzen
** Attachment added: "dim6003_devices" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1949875/+attachment/5538466/+files/dim6003_devices -- 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/1949875 Title: Touchpad not working on Lenovo Flex-5 Ryzen Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: Model = IdeaPad Flex 5 14ARE05 Model Name = 81X2 MO: R9N0B112200U 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: ubuntu:GNOME Date: Thu Nov 4 16:36:18 2021 InstallationDate: Installed on 2021-10-29 (6 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) 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/1949875/+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 1949875] Re: Touchpad not working on Lenovo Flex-5 Ryzen
See also attachments dim6003_lspci-vvnn.log and dim6003_dmesg.log -- 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/1949875 Title: Touchpad not working on Lenovo Flex-5 Ryzen Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: Model = IdeaPad Flex 5 14ARE05 Model Name = 81X2 MO: R9N0B112200U 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: ubuntu:GNOME Date: Thu Nov 4 16:36:18 2021 InstallationDate: Installed on 2021-10-29 (6 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) 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/1949875/+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 1949875] Re: Touchpad not working on Lenovo Flex-5 Ryzen
** Attachment added: "dim6003_dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1949875/+attachment/5538465/+files/dim6003_dmesg.log -- 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/1949875 Title: Touchpad not working on Lenovo Flex-5 Ryzen Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: Model = IdeaPad Flex 5 14ARE05 Model Name = 81X2 MO: R9N0B112200U 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: ubuntu:GNOME Date: Thu Nov 4 16:36:18 2021 InstallationDate: Installed on 2021-10-29 (6 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) 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/1949875/+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 1949875] Re: Touchpad not working on Lenovo Flex-5 Ryzen
** Attachment added: "dim6003_lspci-vvnn.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1949875/+attachment/5538464/+files/dim6003_lspci-vvnn.log -- 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/1949875 Title: Touchpad not working on Lenovo Flex-5 Ryzen Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: Model = IdeaPad Flex 5 14ARE05 Model Name = 81X2 MO: R9N0B112200U 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: ubuntu:GNOME Date: Thu Nov 4 16:36:18 2021 InstallationDate: Installed on 2021-10-29 (6 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) 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/1949875/+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 1949875] Re: Touchpad not working on Lenovo Flex-5 Ryzen
Lenovo T580 here. kernel updated yesterday, and touchpad fails since. Some additionnal info : didier@T580:~$ uname -a Linux T580 5.4.0-89-generic #100-Ubuntu SMP Fri Sep 24 14:50:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux didier@T580:~$ cat /proc/version_signature Ubuntu 5.4.0-89.100-generic 5.4.143 -- 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/1949875 Title: Touchpad not working on Lenovo Flex-5 Ryzen Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: Model = IdeaPad Flex 5 14ARE05 Model Name = 81X2 MO: R9N0B112200U 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: ubuntu:GNOME Date: Thu Nov 4 16:36:18 2021 InstallationDate: Installed on 2021-10-29 (6 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) 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/1949875/+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 1949875] Re: Touchpad not working on Lenovo Flex-5 Ryzen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.11 (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.11 in Ubuntu. https://bugs.launchpad.net/bugs/1949875 Title: Touchpad not working on Lenovo Flex-5 Ryzen Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: Model = IdeaPad Flex 5 14ARE05 Model Name = 81X2 MO: R9N0B112200U 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: ubuntu:GNOME Date: Thu Nov 4 16:36:18 2021 InstallationDate: Installed on 2021-10-29 (6 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) 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/1949875/+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 1948436] Re: Add RevID field to VPD info in EEPROM
** Changed in: linux-bluefield (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1948436 Title: Add RevID field to VPD info in EEPROM Status in linux-bluefield package in Ubuntu: Fix Committed Bug description: SRU Justification: [Impact] Currently, the VPD info stored in the EEPROM does not include a Rev ID. This field is incremented when a PN goes through minor HW changes. Sometimes, SW needs to differentiate the two versions of the card. Hence, this field should be supported in the EEPROM MFG partition. [Fix] EC (Engineering Changes) field is used to denote the HW Revision of a PN. Add it to the EEPROM MFG and provide a sysfs entry to access the same via mlx-bootctl. [Test Case] This field is typically programmed at the manufacturing step using the bfcfg tool which uses the write mechanism in the driver and then the MFG partition is locked. Reading the "rev" sysfs will show the current value. [Regression Potential] Can be considered minimum. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1948436/+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 1942759] Re: No touchpad detected on 'HP ZBook Firefly G8 (1G3U1AV)' after fresh install
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.4 (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.4 in Ubuntu. https://bugs.launchpad.net/bugs/1942759 Title: No touchpad detected on 'HP ZBook Firefly G8 (1G3U1AV)' after fresh install Status in linux-signed-hwe-5.4 package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.5 LTS The touchpad is not detected with or without the Logitech M705 mouse plugged in. cat /proc/bus/input/devices Outputs: I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=20 0 0 1500f0210 43803078f900d401 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=046d Product=101b Version=0111 N: Name="Logitech M705" P: Phys=usb-:00:14.0-4/input2:1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.2/0003:046D:C52B.0004/0003:046D:101B.0005/input/input14 U: Uniq=101b-fc-92-33-df H: Handlers=mouse0 event5 B: PROP=0 B: EV=17 B: KEY= 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="HP Wireless hotkeys" P: Phys=hpq6001/input0 S: Sysfs=/devices/virtual/input/input15 U: Uniq= H: Handlers=rfkill kbd event6 B: PROP=0 B: EV=3 B: KEY=80 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID events" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input16 U: Uniq= H: Handlers=rfkill kbd event7 B: PROP=0 B: EV=13 B: KEY=810003 504000 1e29400020 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID 5 button array" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input17 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=13 B: KEY=2 0 0 0 0 1 0 201c 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="HP WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input18 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=33 B: KEY=40 0 10007 2102400 0 0 B: MSC=10 B: SW=0 I: Bus=0003 Vendor=04f2 Product=b6bf Version=0013 N: Name="HP HD Camera: HP HD Camera" P: Phys=usb-:00:14.0-2/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-2/3-2:1.0/input/input19 U: Uniq= H: Handlers=kbd event10 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0003 Vendor=04f2 Product=b6bf Version=0013 N: Name="HP HD Camera: HP IR Camera" P: Phys=usb-:00:14.0-2/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-2/3-2:1.2/input/input20 U: Uniq= H: Handlers=kbd event11 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-81-generic 5.4.0-81.91~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 6 11:37:52 2021 InstallationDate: Installed on 2021-09-06 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) SourcePackage: linux-signed-hwe-5.4 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.4/+bug/1942759/+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 1942759] Re: No touchpad detected on 'HP ZBook Firefly G8 (1G3U1AV)' after fresh install
I am experiencing the same issue. @herwich Have you found a workaround for getting the touchpad to function? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1942759 Title: No touchpad detected on 'HP ZBook Firefly G8 (1G3U1AV)' after fresh install Status in linux-signed-hwe-5.4 package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.5 LTS The touchpad is not detected with or without the Logitech M705 mouse plugged in. cat /proc/bus/input/devices Outputs: I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=20 0 0 1500f0210 43803078f900d401 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=046d Product=101b Version=0111 N: Name="Logitech M705" P: Phys=usb-:00:14.0-4/input2:1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.2/0003:046D:C52B.0004/0003:046D:101B.0005/input/input14 U: Uniq=101b-fc-92-33-df H: Handlers=mouse0 event5 B: PROP=0 B: EV=17 B: KEY= 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="HP Wireless hotkeys" P: Phys=hpq6001/input0 S: Sysfs=/devices/virtual/input/input15 U: Uniq= H: Handlers=rfkill kbd event6 B: PROP=0 B: EV=3 B: KEY=80 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID events" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input16 U: Uniq= H: Handlers=rfkill kbd event7 B: PROP=0 B: EV=13 B: KEY=810003 504000 1e29400020 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID 5 button array" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input17 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=13 B: KEY=2 0 0 0 0 1 0 201c 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="HP WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input18 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=33 B: KEY=40 0 10007 2102400 0 0 B: MSC=10 B: SW=0 I: Bus=0003 Vendor=04f2 Product=b6bf Version=0013 N: Name="HP HD Camera: HP HD Camera" P: Phys=usb-:00:14.0-2/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-2/3-2:1.0/input/input19 U: Uniq= H: Handlers=kbd event10 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0003 Vendor=04f2 Product=b6bf Version=0013 N: Name="HP HD Camera: HP IR Camera" P: Phys=usb-:00:14.0-2/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-2/3-2:1.2/input/input20 U: Uniq= H: Handlers=kbd event11 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-81-generic 5.4.0-81.91~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 6 11:37:52 2021 InstallationDate: Installed on 2021-09-06 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) SourcePackage: linux-signed-hwe-5.4 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.4/+bug/1942759/+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 1947568] Re: cannot promote clone: "not a cloned filesystem"
What can we do to address these types of issues, without relying on 3rd party PPAs? https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939210 -- 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/1947568 Title: cannot promote clone: "not a cloned filesystem" Status in zfs-linux package in Ubuntu: Confirmed Bug description: I have a zvol containing a Windows image for a virtual machine. After restarting the system a node under /dev/zvol/... was not created for the virtual disk and no amount of prompting by `udevadm trigger` helped. Instead I created a snapshot from the most recent hourly backup: # zfs clone rpool/vm/windows/windows10/hda@hourly07 rpool/vm/windows/windows10/hda-new # zfs promote rpool/vm/windows/windows10/hda-new cannot promote 'rpool/vm/windows/windows10/hda-new': not a cloned filesystem (didn't work here but carried on assuming something can be sorted later) # zfs rename rpool/vm/windows/windows10/hda rpool/vm/windows/windows10/hda-old # zfs rename rpool/vm/windows/windows10/hda-new rpool/vm/windows/windows10/hda Entries in /dev appeared and I could start the virtual machine. Trying to promote the clone gives 'not a cloned filesystem' message. I later renamed the old zvol and tried to cleanup: # zfs rename rpool/vm/windows/windows10/hda-old rpool/to-be-deleted # zfs destroy rpool/to-be-deleted@hourly07 cannot destroy 'rpool/to-be-deleted@hourly07': snapshot has dependent clones use '-R' to destroy the following datasets: rpool/vm/windows/windows10/hda@hourly09 rpool/vm/windows/windows10/hda@hourly10 rpool/vm/windows/windows10/hda # zfs promote rpool/vm/windows/windows10/hda cannot promote 'rpool/vm/windows/windows10/hda': not a cloned filesystem # zfs get origin rpool/vm/windows/windows10/hda NAMEPROPERTY VALUE SOURCE rpool/vm/windows/windows10/hda originrpool/to-be-deleted@hourly07 - # zfs get clones rpool/to-be-deleted@hourly07 NAME PROPERTY VALUE SOURCE rpool/to-be-deleted@hourly07 clonesrpool/vm/windows/windows10/hda - The dependency between seems to be as expected. This small test fails in the same way: # zfs create -V1G rpool/vm/test # zfs snapshot rpool/vm/test@test2 # zfs clone rpool/vm/test@test2 rpool/vm/test3 # zfs promote rpool/vm/test3 cannot promote 'rpool/vm/test3': not a cloned filesystem # zfs get origin rpool/vm/test3 NAMEPROPERTY VALUESOURCE rpool/vm/test3 originrpool/vm/test@test2 - # zfs get clones rpool/vm/test@test2 NAME PROPERTY VALUE SOURCE rpool/vm/test@test2 clonesrpool/vm/test3 - All the zpool members are ONLINE and no errors are reported. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal # uname -r 5.11.0-37-generic # modinfo zfs | grep -i version version:2.0.2-1ubuntu5.1 srcversion: F267DF7B3FFB43AFE76257D vermagic: 5.11.0-37-generic SMP mod_unload modversions # apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.12 Candidate: 0.8.3-1ubuntu12.13 Version table: 0.8.3-1ubuntu12.13 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 0.8.3-1ubuntu12.12 100 100 /var/lib/dpkg/status 0.8.3-1ubuntu12.9 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 0.8.3-1ubuntu12 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1947568/+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 1948025] Re: Update the NVIDIA drivers October 2021
This bug was fixed in the package libnvidia-nscq-460 -
460.106.00-0ubuntu1
---
libnvidia-nscq-460 (460.106.00-0ubuntu1) jammy; urgency=medium
* New upstream release (LP: #1948025).
* debian/rules{.defs}:
- Switch to new tarball format.
- Change path to extract soname.
* debian/templates/libnvidia-nscq-BRANCH.install.in:
- Change source paths.
-- Alberto Milone Fri, 22 Oct 2021
17:41:56 +0200
** Changed in: libnvidia-nscq-460 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1948025
Title:
Update the NVIDIA drivers October 2021
Status in fabric-manager-450 package in Ubuntu:
Fix Released
Status in fabric-manager-460 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-460 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-470 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-495 package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
Fix Committed
Status in fabric-manager-460 source package in Bionic:
Fix Committed
Status in libnvidia-nscq-450 source package in Bionic:
Fix Committed
Status in libnvidia-nscq-460 source package in Bionic:
Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Committed
Status in nvidia-graphics-drivers-470 source package in Bionic:
Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Bionic:
Fix Committed
Status in nvidia-graphics-drivers-495 source package in Bionic:
Fix Committed
Status in fabric-manager-450 source package in Focal:
Fix Committed
Status in fabric-manager-460 source package in Focal:
Fix Committed
Status in libnvidia-nscq-450 source package in Focal:
Fix Committed
Status in libnvidia-nscq-460 source package in Focal:
Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Focal:
Fix Committed
Status in nvidia-graphics-drivers-495 source package in Focal:
Fix Committed
Status in fabric-manager-450 source package in Hirsute:
Fix Committed
Status in fabric-manager-460 source package in Hirsute:
Fix Committed
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Committed
Status in libnvidia-nscq-460 source package in Hirsute:
Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
Fix Committed
Status in nvidia-graphics-drivers-495 source package in Hirsute:
Fix Committed
Status in fabric-manager-450 source package in Impish:
Fix Committed
Status in fabric-manager-460 source package in Impish:
Fix Committed
Status in libnvidia-nscq-450 source package in Impish:
Fix Committed
Status in libnvidia-nscq-460 source package in Impish:
Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Impish:
Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Impish:
Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Impish:
Fix Committed
Status in nvidia-graphics-drivers-470 source package in Impish:
Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Impish:
Fix Committed
Bug description:
Update the NVIDIA series and introduce the new 495 series in Bionic,
Focal, Hirsute, and Impish.
[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/NVid
[Kernel-packages] [Bug 1934424] Re: kernel NULL pointer dereference during xen hibernation
We already ship lib/systemd/system-sleep/hibinit-agent that does post things in hibinit-resume to workaround things. Including stuff about networking, due to previous issues with xen-netfront. Given we already restart systemd-networkd, I wonder if we should do better and not keep xen-netfront loaded in the kernel across suspend and resume. as in 1) extend hibinit-agent.system-sleep to also have pre command 2) in the pre step unload xen-netfront 3) in the post step only load xen-netfront 4) potentially still stop systemd-networkd in pre; which will be restarted after loading xen-netfront in post Since xen-netfront is causing us issues; and we are already unloading and reloading it; it makes sense to unload it before suspending altogether. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1934424 Title: kernel NULL pointer dereference during xen hibernation Status in linux-aws package in Ubuntu: Confirmed Bug description: SRU Justification [Impact] Encountered the following panic while doing hibernation/resume testing with linux-aws 5.8 on Focal on an m3.xlarge (xen) instance type: [ 594.291317] ACPI: Hardware changed while hibernated, success doubtful! [ 594.411609] BUG: kernel NULL pointer dereference, address: 01f4 [ 594.424658] #PF: supervisor write access in kernel mode [ 594.424660] #PF: error_code(0x0002) - not-present page [ 594.424661] PGD 0 P4D 0 [ 594.424665] Oops: 0002 [#1] SMP PTI [ 594.424668] CPU: 3 PID: 362 Comm: systemd-timesyn Not tainted 5.8.0-1036-aws #38~20.04.1-Ubuntu [ 594.424669] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 594.424675] RIP: 0010:_raw_spin_lock_irqsave+0x23/0x40 [ 594.424678] Code: 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 9c 58 0f 1f 44 00 00 49 89 c4 fa 66 0f 1f 44 00 00 31 c0 ba 01 00 00 00 0f b1 17 75 07 4c 89 e0 41 5c 5d c3 89 c6 e8 e9 d1 56 ff 66 90 [ 594.424679] RSP: 0018:c94e3848 EFLAGS: 00010046 [ 594.424680] RAX: RBX: 8883bcc0d000 RCX: 0e02 [ 594.424681] RDX: 0001 RSI: RDI: 01f4 [ 594.424682] RBP: c94e3850 R08: 8883b90b5ec0 R09: 005a [ 594.424683] R10: c94e3910 R11: R12: 0206 [ 594.424684] R13: ea000ee42d40 R14: R15: 0001 [ 594.424686] FS: 7f65ba055980() GS:8883c0ac() knlGS: [ 594.424687] CS: 0010 DS: ES: CR0: 80050033 [ 594.424688] CR2: 01f4 CR3: 0003b99f0001 CR4: 001606e0 [ 594.424692] Call Trace: [ 594.424699] xennet_start_xmit+0x158/0x570 [ 594.424704] dev_hard_start_xmit+0x91/0x1f0 [ 594.424706] ? validate_xmit_skb+0x300/0x340 [ 594.424710] sch_direct_xmit+0x113/0x340 [ 594.424712] __dev_queue_xmit+0x57c/0x8e0 [ 594.424714] ? neigh_add_timer+0x37/0x60 [ 594.424716] dev_queue_xmit+0x10/0x20 [ 594.424717] neigh_resolve_output+0x112/0x1c0 [ 594.424721] ip_finish_output2+0x19b/0x590 [ 594.424723] __ip_finish_output+0xc8/0x1e0 [ 594.424725] ip_finish_output+0x2d/0xb0 [ 594.424728] ip_output+0x7a/0xf0 [ 594.424730] ? __ip_finish_output+0x1e0/0x1e0 [ 594.424732] ip_local_out+0x3d/0x50 [ 594.424734] ip_send_skb+0x19/0x40 [ 594.424737] udp_send_skb.isra.0+0x165/0x390 [ 594.424739] udp_sendmsg+0xb0e/0xd50 [ 594.424742] ? ip_reply_glue_bits+0x50/0x50 [ 594.424747] ? delete_from_swap_cache+0x6a/0x90 [ 594.424750] ? _cond_resched+0x19/0x30 [ 594.424754] ? aa_sk_perm+0x43/0x1b0 [ 594.424757] inet_sendmsg+0x65/0x70 [ 594.424759] ? security_socket_sendmsg+0x35/0x50 [ 594.424760] ? inet_sendmsg+0x65/0x70 [ 594.424764] sock_sendmsg+0x5e/0x70 [ 594.424766] __sys_sendto+0x113/0x190 [ 594.424770] ? __secure_computing+0x42/0xe0 [ 594.424774] ? syscall_trace_enter+0x10d/0x280 [ 594.424777] __x64_sys_sendto+0x29/0x30 [ 594.424781] do_syscall_64+0x49/0xc0 [ 594.424783] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 594.424785] RIP: 0033:0x7f65baee4844 [ 594.424788] Code: 42 3f f7 ff 44 8b 4c 24 2c 4c 8b 44 24 20 89 c5 44 8b 54 24 28 48 8b 54 24 18 b8 2c 00 00 00 48 8b 74 24 10 8b 7c 24 08 0f 05 <48> 3d 00 f0 ff ff 77 30 89 ef 48 89 44 24 08 e8 68 3f f7 ff 48 8b [ 594.424789] RSP: 002b:7ffe9b5fd3a0 EFLAGS: 0293 ORIG_RAX: 002c [ 594.424790] RAX: ffda RBX: 7ffe9b5fd4e0 RCX: 7f65baee4844 [ 594.424791] RDX: 0030 RSI: 7ffe9b5fd3f0 RDI: 0010 [ 594.424792] RBP: R08: 560426541678 R09: 0010 [ 594.424793] R10: 0040 R11: 0293 R12: [ 594.424794] R13: 7ffe9b5fd3e4 R14: 0068 R15: [
[Kernel-packages] [Bug 1947568] Re: cannot promote clone: "not a cloned filesystem"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zfs-linux (Ubuntu) Status: New => Confirmed -- 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/1947568 Title: cannot promote clone: "not a cloned filesystem" Status in zfs-linux package in Ubuntu: Confirmed Bug description: I have a zvol containing a Windows image for a virtual machine. After restarting the system a node under /dev/zvol/... was not created for the virtual disk and no amount of prompting by `udevadm trigger` helped. Instead I created a snapshot from the most recent hourly backup: # zfs clone rpool/vm/windows/windows10/hda@hourly07 rpool/vm/windows/windows10/hda-new # zfs promote rpool/vm/windows/windows10/hda-new cannot promote 'rpool/vm/windows/windows10/hda-new': not a cloned filesystem (didn't work here but carried on assuming something can be sorted later) # zfs rename rpool/vm/windows/windows10/hda rpool/vm/windows/windows10/hda-old # zfs rename rpool/vm/windows/windows10/hda-new rpool/vm/windows/windows10/hda Entries in /dev appeared and I could start the virtual machine. Trying to promote the clone gives 'not a cloned filesystem' message. I later renamed the old zvol and tried to cleanup: # zfs rename rpool/vm/windows/windows10/hda-old rpool/to-be-deleted # zfs destroy rpool/to-be-deleted@hourly07 cannot destroy 'rpool/to-be-deleted@hourly07': snapshot has dependent clones use '-R' to destroy the following datasets: rpool/vm/windows/windows10/hda@hourly09 rpool/vm/windows/windows10/hda@hourly10 rpool/vm/windows/windows10/hda # zfs promote rpool/vm/windows/windows10/hda cannot promote 'rpool/vm/windows/windows10/hda': not a cloned filesystem # zfs get origin rpool/vm/windows/windows10/hda NAMEPROPERTY VALUE SOURCE rpool/vm/windows/windows10/hda originrpool/to-be-deleted@hourly07 - # zfs get clones rpool/to-be-deleted@hourly07 NAME PROPERTY VALUE SOURCE rpool/to-be-deleted@hourly07 clonesrpool/vm/windows/windows10/hda - The dependency between seems to be as expected. This small test fails in the same way: # zfs create -V1G rpool/vm/test # zfs snapshot rpool/vm/test@test2 # zfs clone rpool/vm/test@test2 rpool/vm/test3 # zfs promote rpool/vm/test3 cannot promote 'rpool/vm/test3': not a cloned filesystem # zfs get origin rpool/vm/test3 NAMEPROPERTY VALUESOURCE rpool/vm/test3 originrpool/vm/test@test2 - # zfs get clones rpool/vm/test@test2 NAME PROPERTY VALUE SOURCE rpool/vm/test@test2 clonesrpool/vm/test3 - All the zpool members are ONLINE and no errors are reported. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal # uname -r 5.11.0-37-generic # modinfo zfs | grep -i version version:2.0.2-1ubuntu5.1 srcversion: F267DF7B3FFB43AFE76257D vermagic: 5.11.0-37-generic SMP mod_unload modversions # apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.12 Candidate: 0.8.3-1ubuntu12.13 Version table: 0.8.3-1ubuntu12.13 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 0.8.3-1ubuntu12.12 100 100 /var/lib/dpkg/status 0.8.3-1ubuntu12.9 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 0.8.3-1ubuntu12 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1947568/+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 1939210] Re: When using HWE, zfs-kmod and zfs user tools versions must match
The version mismatch was the cause of a problem I had with `zfs promote`: https://bugs.launchpad.net/ubuntu/+source/zfs- linux/+bug/1947568 In the end I'm using a 3rd party PPA to get updated user space tools but I don't see that as the ideal solution. -- 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/1939210 Title: When using HWE, zfs-kmod and zfs user tools versions must match Status in zfs-linux package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.2 LTS I ran into a problem recently (https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177) due to mismatched versions when HWE upgraded the kernel from 5.8 to 5.11 where the userspace tools don't match the zfs-kmod version. After the update the system ended up with zfs-0.8.3-1ubuntu12.12 and zfs- kmod-2.0.2-1ubuntu5 My understanding from asking in the OpenZFS github is that the two versions must match. This bug is to figure out what to do for those of us who use HWE and zfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939210/+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 1949977] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949977 Title: Laptop doesn't return from sleep Status in linux package in Ubuntu: Confirmed Bug description: I have an HP Pavilion 15-eh0050wm laptop running Kubuntu 21.10 and when I wake it up from sleep, the screen flashes rainbow colours, and the laptop freezes. It doesn't matter if I suspend it with 'systemctl suspend', close the lid or through the desktop. The problem only occurs with kernel version 5.11 and 5.13. I tested it on kernel 5.8 and as far as I can tell, it wakes up normally. I also tried booting a live 21.10 live USB, but the problem still occurs. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: hristos_joia 5029 F pulseaudio /dev/snd/controlC1: hristos_joia 5029 F pulseaudio /dev/snd/controlC0: hristos_joia 5029 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Nov 5 15:54:47 2021 InstallationDate: Installed on 2021-03-11 (239 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Laptop 15-eh0xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=82a2f784-953e-4903-98a7-b49423372c8b ro nouveau.modeset=0 quiet splash acpi=force vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 10/16/2020 dmi.bios.release: 15.5 dmi.bios.vendor: AMI dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87C5 dmi.board.vendor: HP dmi.board.version: 35.24 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 35.24 dmi.modalias: dmi:bvnAMI:bvrF.05:bd10/16/2020:br15.5:efr35.24:svnHP:pnHPPavilionLaptop15-eh0xxx:pvr:sku183G1UA#ABA:rvnHP:rn87C5:rvr35.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eh0xxx dmi.product.sku: 183G1UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949977/+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 1949977] [NEW] Laptop doesn't return from sleep
Public bug reported: I have an HP Pavilion 15-eh0050wm laptop running Kubuntu 21.10 and when I wake it up from sleep, the screen flashes rainbow colours, and the laptop freezes. It doesn't matter if I suspend it with 'systemctl suspend', close the lid or through the desktop. The problem only occurs with kernel version 5.11 and 5.13. I tested it on kernel 5.8 and as far as I can tell, it wakes up normally. I also tried booting a live 21.10 live USB, but the problem still occurs. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: hristos_joia 5029 F pulseaudio /dev/snd/controlC1: hristos_joia 5029 F pulseaudio /dev/snd/controlC0: hristos_joia 5029 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Nov 5 15:54:47 2021 InstallationDate: Installed on 2021-03-11 (239 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Laptop 15-eh0xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=82a2f784-953e-4903-98a7-b49423372c8b ro nouveau.modeset=0 quiet splash acpi=force vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 10/16/2020 dmi.bios.release: 15.5 dmi.bios.vendor: AMI dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87C5 dmi.board.vendor: HP dmi.board.version: 35.24 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 35.24 dmi.modalias: dmi:bvnAMI:bvrF.05:bd10/16/2020:br15.5:efr35.24:svnHP:pnHPPavilionLaptop15-eh0xxx:pvr:sku183G1UA#ABA:rvnHP:rn87C5:rvr35.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eh0xxx dmi.product.sku: 183G1UA#ABA dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish suspend-resume ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1949977/+attachment/5538426/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949977 Title: Laptop doesn't return from sleep Status in linux package in Ubuntu: New Bug description: I have an HP Pavilion 15-eh0050wm laptop running Kubuntu 21.10 and when I wake it up from sleep, the screen flashes rainbow colours, and the laptop freezes. It doesn't matter if I suspend it with 'systemctl suspend', close the lid or through the desktop. The problem only occurs with kernel version 5.11 and 5.13. I tested it on kernel 5.8 and as far as I can tell, it wakes up normally. I also tried booting a live 21.10 live USB, but the problem still occurs. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: hristos_joia 5029 F pulseaudio /dev/snd/controlC1: hristos_joia 5029 F pulseaudio /dev/snd/controlC0: hristos_joia 5029 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Nov 5 15:54:47 2021 InstallationDate: Installed on 2021-03-11 (239 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Laptop 15-eh0xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=82a2f784-953e-4903-98a7-b49423372c8b ro nouveau.modeset=0 quiet splash acpi=force vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 10/16/2020 dmi.bios.release: 15.5 dmi.bios.vendor: AMI dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87C5 dmi.board.vendor: HP dmi.board.version: 35.24 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 35.24 dmi.modalias: dmi:bvnAMI:bvrF.05:bd10/16/2020:br15.5:efr35.24:svnHP:pnHPPavilionLaptop15-eh0xxx:pvr:sku183G1UA
[Kernel-packages] [Bug 1903288] Re: Power guest secure boot with static keys: kernel portion
Added my own review https://lore.kernel.org/linux- integrity/8d7e1609-f77e-834e-cf40-05e19bbc3...@canonical.com/ A few optional comments; and one required change needed to add one more ifdef. -- 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/1903288 Title: Power guest secure boot with static keys: kernel portion Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Incomplete Bug description: == Comment: #2 - Daniel John Axtens - 2020-11-05 20:15:10 == This is the kernel side of changes needed for LPAR/guest secure boot. Because Ubuntu keeps its kernels so wonderfully up to date, I don't think there are any extra patches you need to pick up. (I'll double- check against the 21.04 tree once my git pulls finish!) However, we potentially need some configuration changes to make sure kexec-ing into a crashdump kernel still works. Because Lockdown requires that kexec kernels are signed by a key trusted by IMA, the public key for used for signing the kdump kernel needs to be in the IMA keyring or the platform keyring. For host secure boot (and in the UEFI case), it's loaded into the platform keyring. But in the case of guest secure boot with static keys, it's not loaded into the platform keyring so it needs to be loaded into the IMA keyring. This is easy enough to do. Firstly, load the Secure Boot CA into the .primary_trusted_keys keyring via the CONFIG_SYSTEM_TRUSTED_KEYS property. We assume the key used to sign the kernel is signed by this CA. Then, enable IMA_LOAD_X509, which allows certificates signed by a key on the .primary_trusted_keys keyring to be loaded into the IMA keyring. Then set IMA_X509_PATH to provide a path to the signing key on installed file system. (It may also be possible to do this step in userspace, so long as the CA is trusted by the kernel.) Then that key will be loaded into the .ima keyring at boot and be used to appraise the kexec kernel for crashdumps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+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 1948025] Re: Update the NVIDIA drivers October 2021
Hello Alberto, or anyone else affected, Accepted fabric-manager-450 into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fabric- manager-450/450.156.00-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: fabric-manager-450 (Ubuntu Impish) Status: New => Fix Committed ** Changed in: fabric-manager-450 (Ubuntu Hirsute) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Committed Status in fabric-manager-460 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in fabric-manager-450 source package in Focal: Fix Committed Status in fabric-manager-460 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in fabric-manager-450 source package in Hirsute: Fix Committed Status in fabric-manager-460 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in fabric-manager-450 source package in Impish: Fix Committed Status in fabric-manager-460 source package in Impish: Fix Committed Status in libnvidia-nscq-450 source package in Impish: Fix Co
[Kernel-packages] [Bug 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted fabric-manager-450 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fabric- manager-450/450.156.00-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-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Committed Status in fabric-manager-460 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in fabric-manager-450 source package in Focal: Fix Committed Status in fabric-manager-460 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in fabric-manager-450 source package in Hirsute: Fix Committed Status in fabric-manager-460 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in fabric-manager-450 source package in Impish: Fix Committed Status in fabric-manager-460 source package in Impish: Fix Committed Status in libnvidia-nscq-450 source package in Impish: Fix Committed Status in libnvidia-nscq-460 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in
[Kernel-packages] [Bug 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted fabric-manager-450 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fabric- manager-450/450.156.00-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: fabric-manager-450 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Committed Status in fabric-manager-460 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in fabric-manager-450 source package in Focal: Fix Committed Status in fabric-manager-460 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in fabric-manager-450 source package in Hirsute: Fix Committed Status in fabric-manager-460 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in fabric-manager-450 source package in Impish: Fix Committed Status in fabric-manager-460 source package in Impish: Fix Committed Status in libnvidia-nscq-450 source package in Impish: Fix Committed Status in libnvidia-nscq-460 source package in Impish: Fix Committed Status in nvi
[Kernel-packages] [Bug 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted fabric-manager-450 into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fabric- manager-450/450.156.00-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- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. 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: fabric-manager-450 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Committed Status in fabric-manager-460 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in fabric-manager-450 source package in Focal: Fix Committed Status in fabric-manager-460 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in fabric-manager-450 source package in Hirsute: Fix Committed Status in fabric-manager-460 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in fabric-manager-450 source package in Impish: Fix Committed Status in fabric-manager-460 source package in Impish: Fix Committed Status in libnvidia-nscq-450 source package in Impish: Fix Committed Status in libnvidia-nscq-460 source package in Impish: Fix Committed Status
[Kernel-packages] [Bug 1947601] Re: Cannot start docker container on ubuntu 21.10 server for raspberry pi
As Dave mentioned, it's a new package in Impish and is certainly not perfect. I have no problems moving that module to linux-modules. FWIW, I missed this bug report because it was initially logged against the linux package instead of linux-raspi. ** Also affects: linux-raspi (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Impish) Status: New => Confirmed ** Changed in: linux-raspi (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-raspi (Ubuntu Impish) Importance: Undecided => High ** Changed in: linux-raspi (Ubuntu Impish) Assignee: (unassigned) => Juerg Haefliger (juergh) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1947601 Title: Cannot start docker container on ubuntu 21.10 server for raspberry pi Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Impish: Confirmed Bug description: Using the Ubuntu image for Raspberry Pi from here: https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled- server-arm64+raspi.img.xz After installing the docker.io package, I cannot start a docker container. Example: $ sudo docker run --rm hello-world docker: Error response from daemon: failed to create endpoint pensive_greider on network bridge: failed to add the host (veth2102512) <=> sandbox (veth4fb66df) pair interfaces: operation not supported. Update for everyone searching for a workaround and finding this bug: sudo apt install linux-modules-extra-raspi You may want to indicate above that you are affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1947601/+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 1930868] Re: Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firm
Debian now has firmware-sof 1.9-1 and Ubuntu Impish has 1.7-1. So I think you can remove sof from linux-firmware now (and maybe add a Recommends on firmware-sof instead). Thanks and greets jre -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1930868 Title: Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 Status in firmware-sof package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Triaged Bug description: (Reading database ... 220533 files and directories currently installed.) Preparing to unpack .../firmware-sof-signed_1.6.1-2_all.deb ... Unpacking firmware-sof-signed (1.6.1-2) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb Is there a work around? ProblemType: Package DistroRelease: Ubuntu 21.04 Package: firmware-sof-signed (not installed) ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 AptOrdering: firmware-sof-signed:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 4 17:22:54 2021 DpkgTerminalLog: Preparing to unpack .../firmware-sof-signed_1.6.1-2_all.deb ... Unpacking firmware-sof-signed (1.6.1-2) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 DuplicateSignature: package:firmware-sof-signed:(not installed) Unpacking firmware-sof-signed (1.6.1-2) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 ErrorMessage: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 InstallationDate: Installed on 2021-06-02 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: firmware-sof Title: package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1930868/+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 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted fabric-manager-460 into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fabric- manager-460/460.106.00-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- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. 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: fabric-manager-460 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in fabric-manager-460 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in fabric-manager-460 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in fabric-manager-460 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in fabric-manager-460 source package in Impish: Fix Committed Status in libnvidia-nscq-450 source package in Impish: Fix Committed Status in libnvidia-nscq-460 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-driv
[Kernel-packages] [Bug 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted fabric-manager-460 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fabric- manager-460/460.106.00-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: fabric-manager-460 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in fabric-manager-460 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in fabric-manager-460 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in fabric-manager-460 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in fabric-manager-460 source package in Impish: Fix Committed Status in libnvidia-nscq-450 source package in Impish: Fix Committed Status in libnvidia-nscq-460 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-47
[Kernel-packages] [Bug 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted fabric-manager-460 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fabric- manager-460/460.106.00-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-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in fabric-manager-460 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in fabric-manager-460 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in fabric-manager-460 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in fabric-manager-460 source package in Impish: Fix Committed Status in libnvidia-nscq-450 source package in Impish: Fix Committed Status in libnvidia-nscq-460 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-s
[Kernel-packages] [Bug 1903288] Re: Power guest secure boot with static keys: kernel portion
Hi @Nayna even if it looks like your patch (v3) is still under discussion on the mailing list (https://lore.kernel.org/linux-integrity/beedd453a1ec674d3986f7c3851f30df516d2fbb.ca...@linux.ibm.com/) we've built a test kernel that allows to try and test what you already have (v3) in an Ubuntu kernel (5.15.0-9.9) context: https://launchpad.net/~fheimes/+archive/ubuntu/lp1903288/ Not sure if your focus is still on this v3 or if you already proceeded ... -- 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/1903288 Title: Power guest secure boot with static keys: kernel portion Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Incomplete Bug description: == Comment: #2 - Daniel John Axtens - 2020-11-05 20:15:10 == This is the kernel side of changes needed for LPAR/guest secure boot. Because Ubuntu keeps its kernels so wonderfully up to date, I don't think there are any extra patches you need to pick up. (I'll double- check against the 21.04 tree once my git pulls finish!) However, we potentially need some configuration changes to make sure kexec-ing into a crashdump kernel still works. Because Lockdown requires that kexec kernels are signed by a key trusted by IMA, the public key for used for signing the kdump kernel needs to be in the IMA keyring or the platform keyring. For host secure boot (and in the UEFI case), it's loaded into the platform keyring. But in the case of guest secure boot with static keys, it's not loaded into the platform keyring so it needs to be loaded into the IMA keyring. This is easy enough to do. Firstly, load the Secure Boot CA into the .primary_trusted_keys keyring via the CONFIG_SYSTEM_TRUSTED_KEYS property. We assume the key used to sign the kernel is signed by this CA. Then, enable IMA_LOAD_X509, which allows certificates signed by a key on the .primary_trusted_keys keyring to be loaded into the IMA keyring. Then set IMA_X509_PATH to provide a path to the signing key on installed file system. (It may also be possible to do this step in userspace, so long as the CA is trusted by the kernel.) Then that key will be loaded into the .ima keyring at boot and be used to appraise the kexec kernel for crashdumps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+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 1948025] Re: Update the NVIDIA drivers October 2021
Hello Alberto, or anyone else affected, Accepted fabric-manager-460 into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fabric- manager-460/460.106.00-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: fabric-manager-460 (Ubuntu Impish) Status: New => Fix Committed ** Changed in: fabric-manager-460 (Ubuntu Hirsute) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in fabric-manager-460 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in fabric-manager-460 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in fabric-manager-460 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in fabric-manager-460 source package in Impish: Fix Committed Status in libnvidia-nscq-450 source package in Impish: Fix Committed Status in libnvidia-nscq-460 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drive
[Kernel-packages] [Bug 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted fabric-manager-470 into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fabric- manager-470/470.82.01-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- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. 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-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Impish: Fix Committed Status in libnvidia-nscq-460 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our u
[Kernel-packages] [Bug 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted fabric-manager-470 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fabric- manager-470/470.82.01-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-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Impish: Fix Committed Status in libnvidia-nscq-460 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our user
[Kernel-packages] [Bug 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted fabric-manager-470 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fabric- manager-470/470.82.01-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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Impish: Fix Committed Status in libnvidia-nscq-460 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users ha
[Kernel-packages] [Bug 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted fabric-manager-470 into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fabric- manager-470/470.82.01-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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Impish: Fix Committed Status in libnvidia-nscq-460 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our user
[Kernel-packages] [Bug 1947723] Re: /dev/ttyUSB? port lost on upgrading to 21.10
** Also affects: linux-raspi (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Impish) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1947723 Title: /dev/ttyUSB? port lost on upgrading to 21.10 Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Impish: Confirmed Bug description: No more /dev/ttyUSB? device for RS485 USB dongle after upgrading lsusb -t #after upgrading /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 2: Dev 3, If 0, Class=Mass Storage, Driver=uas, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 3: Dev 5, If 0, Class=Communications, Driver=, 12M |__ Port 3: Dev 5, If 1, Class=CDC Data, Driver=, 12M |__ Port 4: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 12M should see something like /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=ch341, 12M ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-1008-raspi 5.13.0-1008.9 ProcVersionSignature: Ubuntu 5.13.0-1008.9-raspi 5.13.14 Uname: Linux 5.13.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu70 Architecture: arm64 CasperMD5CheckResult: unknown Date: Tue Oct 19 07:13:27 2021 ImageMediaBuild: 20210421 SourcePackage: linux-raspi UpgradeStatus: Upgraded to impish on 2021-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1947723/+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 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted libnvidia-nscq-450 into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnvidia- nscq-450/450.156.00-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- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. 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: libnvidia-nscq-450 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Impish: Fix Committed Status in libnvidia-nscq-460 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [Impact] These releases
[Kernel-packages] [Bug 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted libnvidia-nscq-450 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnvidia- nscq-450/450.156.00-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: libnvidia-nscq-450 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Impish: Fix Committed Status in libnvidia-nscq-460 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [Impact] These releases provi
[Kernel-packages] [Bug 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted libnvidia-nscq-450 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnvidia- nscq-450/450.156.00-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-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Impish: Fix Committed Status in libnvidia-nscq-460 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our use
[Kernel-packages] [Bug 1948025] Re: Update the NVIDIA drivers October 2021
Hello Alberto, or anyone else affected, Accepted libnvidia-nscq-450 into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnvidia- nscq-450/450.156.00-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: libnvidia-nscq-450 (Ubuntu Impish) Status: New => Fix Committed ** Changed in: libnvidia-nscq-450 (Ubuntu Hirsute) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Impish: Fix Committed Status in libnvidia-nscq-460 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce th
[Kernel-packages] [Bug 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted libnvidia-nscq-460 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnvidia- nscq-460/460.106.00-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-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [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:
[Kernel-packages] [Bug 1948025] Re: Update the NVIDIA drivers October 2021
Hello Alberto, or anyone else affected, Accepted libnvidia-nscq-460 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnvidia- nscq-460/460.106.00-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: libnvidia-nscq-460 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: libnvidia-nscq-460 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [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. [Tes
[Kernel-packages] [Bug 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted libnvidia-nscq-460 into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnvidia- nscq-460/460.106.00-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- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. 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-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [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
[Kernel-packages] [Bug 1948025] Re: Update the NVIDIA drivers October 2021
Hello Alberto, or anyone else affected, Accepted libnvidia-nscq-460 into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnvidia- nscq-460/460.106.00-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: libnvidia-nscq-460 (Ubuntu Impish) Status: New => Fix Committed ** Changed in: libnvidia-nscq-460 (Ubuntu Hirsute) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [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 m
[Kernel-packages] [Bug 1949889] Re: Unable to build net/reuseport_bpf and other tests in ubuntu_kernel_selftests on Bionic with make command
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949889 Title: Unable to build net/reuseport_bpf and other tests in ubuntu_kernel_selftests on Bionic with make command Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] With 4.15 kernel, not all binary files inside a subtest directory in tools/testing/selftests of a kernel tree can be built with command: make TARGETS=$subtest For example, the following binaries in net directory won't be built: * reuseport_bpf * reuseport_bpf_cpu * reuseport_dualstack * reuseaddr_conflict * reuseport_bpf_numa They can only be build with: make TARGETS=net run_tests However, this will also start all of the tests in this subset and it's is not ideal for the granularity improvement, in which we will want to run tests one-by-one. [Fix] 1. 14f1889f selftests: Fix loss of test output in run_kselftests.sh 2. 44f01352 selftests: Makefile set KSFT_TAP_LEVEL to prevent nested TAP headers 3. 8ce72dc3 selftests: fix headers_install circular dependency 4. 27d79a2b selftests: fix bpf build/test workflow regression when KBUILD_OUTPUT is set 5. e2e88325 selftests: vm: Fix test build failure when built by itself The 1st and 5th patch can be cherry-picked. The 2nd needs to be backported with some context adjustment (can be applied with git -cp but not git am -C2). The 3rd and 4th patch would need to be applied with -C2. The third patch (8ce72dc3) is the fix for this issue. To get it applied more easily we will need the first two. The 4th (27d79a2b) and the 5th (e2e88325) patches are included here as they have been marked as a fix for 8ce72dc3. Since we don't use KBUILD_OUTPUT and the vm test, I think the risk of adding these two is pretty low. [Test] Tested on a baremetal node "glameow" with 4.15.0-159-generic, the test cases number and results are identical before and after applying this change (compared side-by-side). Please find attachment in the bug report for the test result. [Where problems could occur] As this is just tested with generic Bionic 4.15 kernel on a bare-metal system, it's is possible to see other issues on different variants. If this change is incorrect it will cause issue to our automated-testing and regression-testing, but it won't affect the real kernel functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949889/+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 1949889] Re: Unable to build net/reuseport_bpf and other tests in ubuntu_kernel_selftests on Bionic with make command
** Description changed: [Impact] With 4.15 kernel, not all binary files inside a subtest directory in tools/testing/selftests of a kernel tree can be built with command: - make TARGETS=$subtest + make TARGETS=$subtest For example, the following binaries in net directory won't be built: - * reuseport_bpf - * reuseport_bpf_cpu - * reuseport_dualstack - * reuseaddr_conflict - * reuseport_bpf_numa + * reuseport_bpf + * reuseport_bpf_cpu + * reuseport_dualstack + * reuseaddr_conflict + * reuseport_bpf_numa They can only be build with: - make TARGETS=net run_tests + make TARGETS=net run_tests However, this will also start all of the tests in this subset and it's is not ideal for the granularity improvement, in which we will want to run tests one-by-one. [Fix] 1. 14f1889f selftests: Fix loss of test output in run_kselftests.sh 2. 44f01352 selftests: Makefile set KSFT_TAP_LEVEL to prevent nested TAP headers 3. 8ce72dc3 selftests: fix headers_install circular dependency 4. 27d79a2b selftests: fix bpf build/test workflow regression when KBUILD_OUTPUT is set 5. e2e88325 selftests: vm: Fix test build failure when built by itself - The 2nd needs to be backported with some context adjustment. - The 3rd and 4th patch would need to be applied with -C2, the other two - can be cherry-picked for Bionic. + The 1st and 5th patch can be cherry-picked. The 2nd needs to be + backported with some context adjustment (can be applied with git -cp + but not git am -C2). The 3rd and 4th patch would need to be applied + with -C2. - The third patch (8ce72dc3) is the fix for this issue. The 4th - (27d79a2b) and the 5th (e2e88325) patches are included here as they - have been marked as a fix for 8ce72dc3. + The third patch (8ce72dc3) is the fix for this issue. To get it + applied more easily we will need the first two. + + The 4th (27d79a2b) and the 5th (e2e88325) patches are included here as + they have been marked as a fix for 8ce72dc3. Since we don't use + KBUILD_OUTPUT and the vm test, I think the risk of adding these two is + pretty low. [Test] Tested on a baremetal node "glameow" with 4.15.0-159-generic, the test cases number and results are identical before and after applying this change (compared side-by-side). Please find attachment in the bug report for the test result. [Where problems could occur] As this is just tested with generic Bionic 4.15 kernel on a bare-metal system, it's is possible to see other issues on different variants. If this change is incorrect it will cause issue to our automated-testing and regression-testing, but it won't affect the real kernel functionality. ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: ubuntu-kernel-tests Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949889 Title: Unable to build net/reuseport_bpf and other tests in ubuntu_kernel_selftests on Bionic with make command Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: [Impact] With 4.15 kernel, not all binary files inside a subtest directory in tools/testing/selftests of a kernel tree can be built with command: make TARGETS=$subtest For example, the following binaries in net directory won't be built: * reuseport_bpf * reuseport_bpf_cpu * reuseport_dualstack * reuseaddr_conflict * reuseport_bpf_numa They can only be build with: make TARGETS=net run_tests However, this will also start all of the tests in this subset and it's is not ideal for the granularity improvement, in which we will want to run tests one-by-one. [Fix] 1. 14f1889f selftests: Fix loss of test output in run_kselftests.sh 2. 44f01352 selftests: Makefile set KSFT_TAP_LEVEL to prevent nested TAP headers 3. 8ce72dc3 selftests: fix headers_install circular dependency 4. 27d79a2b selftests: fix bpf build/test workflow regression when KBUILD_OUTPUT is set 5. e2e88325 selftests: vm: Fix test build failure when built by itself The 1st and 5th patch can be cherry-picked. The 2nd needs to be backported with some context adjustment (can be applied with git -cp but not git am -C2). The 3rd and 4th patch would need to be applied with -C2. The third patch (8ce72dc3) is the fix for this issue. To get it applied more easily we will need the first two. The 4th (27d79a2b) and the 5th (e2e88325) patches are included here as they have been marked as a fix for 8ce72dc3. Since we don't use KBUILD_OUTPUT and the vm test
[Kernel-packages] [Bug 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted libnvidia-nscq-470 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnvidia- nscq-470/470.82.01-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-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [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 thi
[Kernel-packages] [Bug 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted libnvidia-nscq-470 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnvidia- nscq-470/470.82.01-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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [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
[Kernel-packages] [Bug 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted libnvidia-nscq-470 into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnvidia- nscq-470/470.82.01-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- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. 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-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [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
[Kernel-packages] [Bug 1948807] Re: Boot time from snap in 20/stable increases boot time on 3.5 seconds
** Also affects: linux-raspi (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Impish) Status: New => Confirmed ** Changed in: linux-raspi (Ubuntu Impish) Importance: Undecided => High ** Changed in: linux-raspi (Ubuntu Impish) Assignee: (unassigned) => Juerg Haefliger (juergh) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1948807 Title: Boot time from snap in 20/stable increases boot time on 3.5 seconds Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Focal: Confirmed Status in linux-raspi source package in Hirsute: Confirmed Status in linux-raspi source package in Impish: Confirmed Bug description: I am seeing what looks as a regression in pi-kernel snap for UC20: there are around 3.5 additional seconds spent in boot time. In the image from cdimage (2021-06-30), I see: [1.856540] random: crng init done [1.871798] loop: module loaded (see https://paste.ubuntu.com/p/CkfWXY5Vgf/) while if I build an image from latest snaps in the 20/stable channel, I get: [1.855481] random: crng init done [5.349491] loop: module loaded (see https://paste.ubuntu.com/p/CNt42gdDcZ/) The pi-kernel snap revision is 353. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1948807/+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 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted libnvidia-nscq-470 into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnvidia- nscq-470/470.82.01-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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [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 thi
[Kernel-packages] [Bug 1949889] Re: Unable to build net/reuseport_bpf and other tests in ubuntu_kernel_selftests on Bionic with make command
** Description changed: [Impact] - With 4.15 kernel, not all binary files inside a subtest directory in tools/testing/selftests of a kernel tree can be built with command: - make TARGETS=$subtest + With 4.15 kernel, not all binary files inside a subtest directory in + tools/testing/selftests of a kernel tree can be built with command: - For example, the following tests in net directory won't be built: - * reuseport_bpf - * reuseport_bpf_cpu - * reuseport_dualstack - * reuseaddr_conflict - * reuseport_bpf_numa + make TARGETS=$subtest - They can be build with: - make TARGETS=net run_tests + For example, the following binaries in net directory won't be built: + * reuseport_bpf + * reuseport_bpf_cpu + * reuseport_dualstack + * reuseaddr_conflict + * reuseport_bpf_numa - However, this will also start all of the tests in this subset, which is - not ideal for the granularity improvement. + They can only be build with: + + make TARGETS=net run_tests + + However, this will also start all of the tests in this subset and it's + is not ideal for the granularity improvement, in which we will want to + run tests one-by-one. [Fix] 1. 14f1889f selftests: Fix loss of test output in run_kselftests.sh 2. 44f01352 selftests: Makefile set KSFT_TAP_LEVEL to prevent nested TAP headers 3. 8ce72dc3 selftests: fix headers_install circular dependency 4. 27d79a2b selftests: fix bpf build/test workflow regression when KBUILD_OUTPUT is set 5. e2e88325 selftests: vm: Fix test build failure when built by itself The 2nd needs to be backported with some context adjustment. - The 3rd and 4th patch would need to be applied with -C2, the other two can be cherry-picked for Bionic. + The 3rd and 4th patch would need to be applied with -C2, the other two + can be cherry-picked for Bionic. - The third patch (8ce72dc3) is the fix for this issue. The 4th (27d79a2b) - and the 5th (e2e88325) have been marked as a fix for 8ce72dc3. + The third patch (8ce72dc3) is the fix for this issue. The 4th + (27d79a2b) and the 5th (e2e88325) patches are included here as they + have been marked as a fix for 8ce72dc3. [Test] - Tested on a baremetal node "glameow" with 4.15.0-159-generic, the test cases number and results are identical before and after applying this change (compared side-by-side). + Tested on a baremetal node "glameow" with 4.15.0-159-generic, the test + cases number and results are identical before and after applying this + change (compared side-by-side). Please find attachment in the bug report for the test result. [Where problems could occur] - As this is just tested with generic Bionic 4.15 kernel on a bare-metal system, it's is possible to see other issues on different variants. If this change is incorrect it will cause issue to our automated-testing and regression-testing, but it won't affect the real kernel functionality. + As this is just tested with generic Bionic 4.15 kernel on a bare-metal + system, it's is possible to see other issues on different variants. If + this change is incorrect it will cause issue to our automated-testing + and regression-testing, but it won't affect the real kernel + functionality. -- 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/1949889 Title: Unable to build net/reuseport_bpf and other tests in ubuntu_kernel_selftests on Bionic with make command Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Bug description: [Impact] With 4.15 kernel, not all binary files inside a subtest directory in tools/testing/selftests of a kernel tree can be built with command: make TARGETS=$subtest For example, the following binaries in net directory won't be built: * reuseport_bpf * reuseport_bpf_cpu * reuseport_dualstack * reuseaddr_conflict * reuseport_bpf_numa They can only be build with: make TARGETS=net run_tests However, this will also start all of the tests in this subset and it's is not ideal for the granularity improvement, in which we will want to run tests one-by-one. [Fix] 1. 14f1889f selftests: Fix loss of test output in run_kselftests.sh 2. 44f01352 selftests: Makefile set KSFT_TAP_LEVEL to prevent nested TAP headers 3. 8ce72dc3 selftests: fix headers_install circular dependency 4. 27d79a2b selftests: fix bpf build/test workflow regression when KBUILD_OUTPUT is set 5. e2e88325 selftests: vm: Fix test build failure when built by itself The 2nd needs to be backported with some context adjustment. The 3rd and 4th patch would need to be applied with -C2, the other two can be cherry-picked for Bionic. The third patch (8ce72dc3) is the fix for this issue. The 4th (27d79a2b) and the 5th (e2e88325) patches are included here as they have been marked as a fix for 8ce72dc3.
[Kernel-packages] [Bug 1948807] Re: Boot time from snap in 20/stable increases boot time on 3.5 seconds
** Also affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: linux-raspi (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: linux-raspi (Ubuntu Hirsute) Assignee: (unassigned) => Juerg Haefliger (juergh) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1948807 Title: Boot time from snap in 20/stable increases boot time on 3.5 seconds Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Focal: Confirmed Status in linux-raspi source package in Hirsute: Confirmed Bug description: I am seeing what looks as a regression in pi-kernel snap for UC20: there are around 3.5 additional seconds spent in boot time. In the image from cdimage (2021-06-30), I see: [1.856540] random: crng init done [1.871798] loop: module loaded (see https://paste.ubuntu.com/p/CkfWXY5Vgf/) while if I build an image from latest snaps in the 20/stable channel, I get: [1.855481] random: crng init done [5.349491] loop: module loaded (see https://paste.ubuntu.com/p/CNt42gdDcZ/) The pi-kernel snap revision is 353. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1948807/+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 1949889] Re: Unable to build net/reuseport_bpf and other tests in ubuntu_kernel_selftests on Bionic with make command
Test report after applying this patchset. Note that empty lines (or empty lines with "-") has been added to make it easier to run vimdiff. ** Attachment added: "patches-test-report.log" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949889/+attachment/5538395/+files/patches-test-report.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949889 Title: Unable to build net/reuseport_bpf and other tests in ubuntu_kernel_selftests on Bionic with make command Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Bug description: [Impact] With 4.15 kernel, not all binary files inside a subtest directory in tools/testing/selftests of a kernel tree can be built with command: make TARGETS=$subtest For example, the following tests in net directory won't be built: * reuseport_bpf * reuseport_bpf_cpu * reuseport_dualstack * reuseaddr_conflict * reuseport_bpf_numa They can be build with: make TARGETS=net run_tests However, this will also start all of the tests in this subset, which is not ideal for the granularity improvement. [Fix] 1. 14f1889f selftests: Fix loss of test output in run_kselftests.sh 2. 44f01352 selftests: Makefile set KSFT_TAP_LEVEL to prevent nested TAP headers 3. 8ce72dc3 selftests: fix headers_install circular dependency 4. 27d79a2b selftests: fix bpf build/test workflow regression when KBUILD_OUTPUT is set 5. e2e88325 selftests: vm: Fix test build failure when built by itself The 2nd needs to be backported with some context adjustment. The 3rd and 4th patch would need to be applied with -C2, the other two can be cherry-picked for Bionic. The third patch (8ce72dc3) is the fix for this issue. The 4th (27d79a2b) and the 5th (e2e88325) have been marked as a fix for 8ce72dc3. [Test] Tested on a baremetal node "glameow" with 4.15.0-159-generic, the test cases number and results are identical before and after applying this change (compared side-by-side). Please find attachment in the bug report for the test result. [Where problems could occur] As this is just tested with generic Bionic 4.15 kernel on a bare-metal system, it's is possible to see other issues on different variants. If this change is incorrect it will cause issue to our automated-testing and regression-testing, but it won't affect the real kernel functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949889/+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 1949889] Re: Unable to build net/reuseport_bpf and other tests in ubuntu_kernel_selftests on Bionic with make command
Test report before applying this patchset. Note that empty lines (or empty lines with "-") has been added to make it easier to run vimdiff. ** Tags added: 4.15 bionic ** Tags added: ubuntu-kernel-selftests ** Description changed: [Impact] With 4.15 kernel, not all binary files inside a subtest directory in tools/testing/selftests of a kernel tree can be built with command: make TARGETS=$subtest For example, the following tests in net directory won't be built: * reuseport_bpf * reuseport_bpf_cpu * reuseport_dualstack * reuseaddr_conflict * reuseport_bpf_numa They can be build with: make TARGETS=net run_tests However, this will also start all of the tests in this subset, which is not ideal for the granularity improvement. [Fix] 1. 14f1889f selftests: Fix loss of test output in run_kselftests.sh 2. 44f01352 selftests: Makefile set KSFT_TAP_LEVEL to prevent nested TAP headers 3. 8ce72dc3 selftests: fix headers_install circular dependency 4. 27d79a2b selftests: fix bpf build/test workflow regression when KBUILD_OUTPUT is set 5. e2e88325 selftests: vm: Fix test build failure when built by itself The 2nd needs to be backported with some context adjustment. The 3rd and 4th patch would need to be applied with -C2, the other two can be cherry-picked for Bionic. The third patch (8ce72dc3) is the fix for this issue. The 4th (27d79a2b) and the 5th (e2e88325) have been marked as a fix for 8ce72dc3. [Test] - Tested on a baremetal node "glameow" with 4.15.0-159-generic, the test cases number and results are identical before and after applying this change. + Tested on a baremetal node "glameow" with 4.15.0-159-generic, the test cases number and results are identical before and after applying this change (compared side-by-side). + + Please find attachment in the bug report for the test result. [Where problems could occur] As this is just tested with generic Bionic 4.15 kernel on a bare-metal system, it's is possible to see other issues on different variants. If this change is incorrect it will cause issue to our automated-testing and regression-testing, but it won't affect the real kernel functionality. ** Attachment added: "original-test-report.log" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949889/+attachment/5538394/+files/original-test-report.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949889 Title: Unable to build net/reuseport_bpf and other tests in ubuntu_kernel_selftests on Bionic with make command Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Bug description: [Impact] With 4.15 kernel, not all binary files inside a subtest directory in tools/testing/selftests of a kernel tree can be built with command: make TARGETS=$subtest For example, the following tests in net directory won't be built: * reuseport_bpf * reuseport_bpf_cpu * reuseport_dualstack * reuseaddr_conflict * reuseport_bpf_numa They can be build with: make TARGETS=net run_tests However, this will also start all of the tests in this subset, which is not ideal for the granularity improvement. [Fix] 1. 14f1889f selftests: Fix loss of test output in run_kselftests.sh 2. 44f01352 selftests: Makefile set KSFT_TAP_LEVEL to prevent nested TAP headers 3. 8ce72dc3 selftests: fix headers_install circular dependency 4. 27d79a2b selftests: fix bpf build/test workflow regression when KBUILD_OUTPUT is set 5. e2e88325 selftests: vm: Fix test build failure when built by itself The 2nd needs to be backported with some context adjustment. The 3rd and 4th patch would need to be applied with -C2, the other two can be cherry-picked for Bionic. The third patch (8ce72dc3) is the fix for this issue. The 4th (27d79a2b) and the 5th (e2e88325) have been marked as a fix for 8ce72dc3. [Test] Tested on a baremetal node "glameow" with 4.15.0-159-generic, the test cases number and results are identical before and after applying this change (compared side-by-side). Please find attachment in the bug report for the test result. [Where problems could occur] As this is just tested with generic Bionic 4.15 kernel on a bare-metal system, it's is possible to see other issues on different variants. If this change is incorrect it will cause issue to our automated-testing and regression-testing, but it won't affect the real kernel functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949889/+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 1948767] Re: Fail to detect audio output from external monitor
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1948767
Title:
Fail to detect audio output from external monitor
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-5.13 package in Ubuntu:
New
Status in linux-oem-5.14 package in Ubuntu:
New
Status in linux source package in Focal:
Incomplete
Status in linux-oem-5.13 source package in Focal:
Fix Committed
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux-oem-5.14 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Fix Committed
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Few recent AMD systems shows "snd_hda_intel :00:1f.3: azx_get_response
timeout" and fail to detect the HDMI/DP audio output device when connects to
external monitor. It will work magically when re-loading the driver.
[Fix]
Backport the upstream fix c0f1886de7e1 ("Allow repeatedly probing on codec
configuration errors) from 5.15.0 rc. It adds the capability for retrying the
probe upon codec probe errors on the certain AMD platforms.
[Test]
1. Connect the external monitor to particular affected AMD systems with HDMI
or DisplayPort.
2. Go to Audio Settings to check if the HDMI/DP audio output device exist or
not.
[Where problems could occur]
Should be low risk, it adds the chance for retrying codec probe and won't
affect machines which used to work.
== Original Bug Description ==
Can not detect DP audio output
[Steps to reproduce]
1) install dell-bto-focal-fossa-grimer-rkl-X72-20210929-8.iso and boot into OS
2) switch to on-demand mode
3) connect an external monitor via DP Port
4) check sound setting --> Output Device
5) switch to performance mode
6) check sound setting --> Output Device
[Expected result]
System can detect DP audio output when external monitor connected
[Actual result]
Can not detect DP audio output
This issue can be reproduce in on-demand and performance mode.
[Failure rate]
1/1
[Additional information]
CID: 202101-28624
SKU: PRH-DVT-C6
Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-grimer-rkl+X72
system-manufacturer: Dell Inc.
system-product-name: OptiPlex 5490 AIO
bios-version: 1.4.1
CPU: 11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16x)
GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device
[8086:4c8a] (rev 04)
01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1f99] (rev a1)
kernel-version: 5.14.0-2006-oem
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1081 F pulseaudio
u 1592 F pulseaudio
CasperMD5CheckResult: skip
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-proposed-release+X88
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-10-27 (1 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
MachineType: Dell Inc. OptiPlex 5490 AIO
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem
root=UUID=d0e48268-091a-436d-8b79-2420e385c5c8 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25
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.10.0-1020-oem N/A
linux-backports-modules-5.10.0-1020-oem N/A
linux-firmware 1.187.10
Tags: focal
Uname: Linux 5.10.0-1020-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 08/17/2021
dmi.bios.release: 1.4
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.1
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 13
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.4.1:bd08/17/2021:br1.4:svnDellInc.:pnOptiPlex5490AIO:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct13:cvr:
dmi.product.family: OptiPlex
dmi.produ
[Kernel-packages] [Bug 1901266] Re: system sluggish, thermal keep frequency at 400MHz
** Changed in: thermald (Ubuntu) Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1901266 Title: system sluggish, thermal keep frequency at 400MHz Status in thermald package in Ubuntu: Incomplete Bug description: This morning I upgraded to 20.10 from 20.04 The system was quite slow although I have a fast machine. My virtual windows 10 on virtualbox became unusable. When I tried to have the virtual machine open, I could not participate properly in a zoom call (I could still hear the people but they said that my voice was very choppy) On 20.04 I was super-happy with the speed and I could have as many apps running as I want. Based on google I started looking at % journalctl --follow and this shows quite a few errors but not repeating often enough to explain it. Then I googled some more and found that /boot/efi was writing and reading. Then I googled some more and thought I had trouble with gnome. So I reset it to default % dconf reset -f /org/gnome/ and disabled the extensions. This made things slightly better but by far not acceptable. After lots of searching I checked the frequency of the CPUs and it was at the minimum 400Hz (as shown by i7z and also other tools). I tried setting the governor with cpufreqctl and similar methods but this did not change anything. I then found an old bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769236 and tried % sudo systemctl stop thermald this seems to work. After a few seconds the frequency shown in i7z goes to ~4500 MHz and the virtual machine seems to work fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: thermald 2.3-4 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 01:39:40 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+merion+X66 InstallationDate: Installed on 2019-09-27 (392 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: thermald UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago) mtime.conffile..etc.thermald.thermal-conf.xml: 2020-10-24T01:35:59.781865 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1901266/+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 1940485] Re: thermald often limits CPU frequency while on AC
** Changed in: thermald (Ubuntu) Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1940485 Title: thermald often limits CPU frequency while on AC Status in thermald package in Ubuntu: Incomplete Bug description: I'm not entirely sure if this is a thermald issue, but on my laptop (Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC, is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz turbo frequency. Restarting thermald (with `systemctl restart thermald`) will let the system scale up to the expected ~3.8GHz boost frequency. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thermald 2.4.6-1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 19 09:24:56 2021 InstallationDate: Installed on 2021-06-26 (53 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+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 1763144] Re: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows
** Changed in: thermald (Ubuntu) Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1763144 Title: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows Status in linux package in Ubuntu: Invalid Status in thermald package in Ubuntu: Incomplete Bug description: A ThinkPad T480s under windows has a power limit of 44W, both short and long term, with a thermal maximum of about 93C or so. Under Linux, the power limits are 44W and 15W (short) or so, and the thermal limit is 80C, causing a significant performance loss. Looking at MSR and MCHBAR values, we can see that the values are correctly at 44W in the MSR, but the MCHBAR is set to a lower value: $ sudo rdmsr -a 0x610 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0 0x0042816000dd8078 Setting the MCHBAR to the same value as the MSR register solves the problem. At some point intel-rapl seems to reduce overall frequency to 600 MHz, though. The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24 -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting in performance comparative to Windows. Most of the analysis is based on the analysis in https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/ This applies to all bionic kernels I have tested so far, including Ubuntu 4.15.0-13.14-generic 4.15.10 --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: jak5881 F...m pulseaudio /dev/snd/controlC2: jak5881 F pulseaudio /dev/snd/controlC1: jak5881 F pulseaudio /dev/snd/controlC0: jak5881 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-14 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET31W (1.08 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 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.modalias: dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763144/+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 1769236] Re: CPU frequency stuck at minimum value
** Changed in: linux (Ubuntu) Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => koba (kobako) ** Changed in: thermald (Ubuntu) Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Incomplete Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjditchf 1190 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-28 (10 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre Laptop 13-af0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A2 dmi.board.vendor: HP dmi.board.version: 55.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_533
[Kernel-packages] [Bug 1949889] Re: Unable to build net/reuseport_bpf and other tests in ubuntu_kernel_selftests on Bionic with make command
** Description changed: [Impact] With 4.15 kernel, not all binary files inside a subtest directory in tools/testing/selftests of a kernel tree can be built with command: make TARGETS=$subtest For example, the following tests in net directory won't be built: * reuseport_bpf * reuseport_bpf_cpu * reuseport_dualstack * reuseaddr_conflict * reuseport_bpf_numa They can be build with: make TARGETS=net run_tests However, this will also start all of the tests in this subset, which is not ideal for the granularity improvement. [Fix] 1. 14f1889f selftests: Fix loss of test output in run_kselftests.sh 2. 44f01352 selftests: Makefile set KSFT_TAP_LEVEL to prevent nested TAP headers 3. 8ce72dc3 selftests: fix headers_install circular dependency 4. 27d79a2b selftests: fix bpf build/test workflow regression when KBUILD_OUTPUT is set 5. e2e88325 selftests: vm: Fix test build failure when built by itself - The 2nd, 3rd and 4th patch would need to be applied with -C1, the other - two can be cherry-picked for Bionic. + The 2nd needs to be backported with some context adjustment. + The 3rd and 4th patch would need to be applied with -C2, the other two can be cherry-picked for Bionic. The third patch (8ce72dc3) is the fix for this issue. The 4th (27d79a2b) and the 5th (e2e88325) have been marked as a fix for 8ce72dc3. [Test] Tested on a baremetal node "glameow" with 4.15.0-159-generic, the test cases number and results are identical before and after applying this change. [Where problems could occur] As this is just tested with generic Bionic 4.15 kernel on a bare-metal system, it's is possible to see other issues on different variants. If this change is incorrect it will cause issue to our automated-testing and regression-testing, but it won't affect the real kernel functionality. -- 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/1949889 Title: Unable to build net/reuseport_bpf and other tests in ubuntu_kernel_selftests on Bionic with make command Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Bug description: [Impact] With 4.15 kernel, not all binary files inside a subtest directory in tools/testing/selftests of a kernel tree can be built with command: make TARGETS=$subtest For example, the following tests in net directory won't be built: * reuseport_bpf * reuseport_bpf_cpu * reuseport_dualstack * reuseaddr_conflict * reuseport_bpf_numa They can be build with: make TARGETS=net run_tests However, this will also start all of the tests in this subset, which is not ideal for the granularity improvement. [Fix] 1. 14f1889f selftests: Fix loss of test output in run_kselftests.sh 2. 44f01352 selftests: Makefile set KSFT_TAP_LEVEL to prevent nested TAP headers 3. 8ce72dc3 selftests: fix headers_install circular dependency 4. 27d79a2b selftests: fix bpf build/test workflow regression when KBUILD_OUTPUT is set 5. e2e88325 selftests: vm: Fix test build failure when built by itself The 2nd needs to be backported with some context adjustment. The 3rd and 4th patch would need to be applied with -C2, the other two can be cherry-picked for Bionic. The third patch (8ce72dc3) is the fix for this issue. The 4th (27d79a2b) and the 5th (e2e88325) have been marked as a fix for 8ce72dc3. [Test] Tested on a baremetal node "glameow" with 4.15.0-159-generic, the test cases number and results are identical before and after applying this change. [Where problems could occur] As this is just tested with generic Bionic 4.15 kernel on a bare-metal system, it's is possible to see other issues on different variants. If this change is incorrect it will cause issue to our automated-testing and regression-testing, but it won't affect the real kernel functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949889/+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 1949889] Re: Unable to build net/reuseport_bpf and other tests in ubuntu_kernel_selftests on Bionic with make command
** Description changed: [Impact] With 4.15 kernel, not all binary files inside a subtest directory in tools/testing/selftests of a kernel tree can be built with command: make TARGETS=$subtest For example, the following tests in net directory won't be built: * reuseport_bpf * reuseport_bpf_cpu * reuseport_dualstack * reuseaddr_conflict * reuseport_bpf_numa They can be build with: make TARGETS=net run_tests However, this will also start all of the tests in this subset, which is not ideal for the granularity improvement. [Fix] - * 14f1889f selftests: Fix loss of test output in run_kselftests.sh - * 44f01352 selftests: Makefile set KSFT_TAP_LEVEL to prevent nested TAP headers - * 8ce72dc3 selftests: fix headers_install circular dependency - * 27d79a2b selftests: fix bpf build/test workflow regression when KBUILD_OUTPUT is set - * e2e88325 selftests: vm: Fix test build failure when built by itself + 1. 14f1889f selftests: Fix loss of test output in run_kselftests.sh + 2. 44f01352 selftests: Makefile set KSFT_TAP_LEVEL to prevent nested TAP headers + 3. 8ce72dc3 selftests: fix headers_install circular dependency + 4. 27d79a2b selftests: fix bpf build/test workflow regression when KBUILD_OUTPUT is set + 5. e2e88325 selftests: vm: Fix test build failure when built by itself - These patches can be cherry-picked for Bionic. - The third patch (8ce72dc3) is the fix for this issue. The 4th (27d79a2b) and the 5th (e2e88325) have been marked as a fix for 8ce72dc3. + The 2nd, 3rd and 4th patch would need to be applied with -C1, the other + two can be cherry-picked for Bionic. + + The third patch (8ce72dc3) is the fix for this issue. The 4th (27d79a2b) + and the 5th (e2e88325) have been marked as a fix for 8ce72dc3. [Test] - Tested on a baremetal node "glameow" with 4.15.0-159-generic + Tested on a baremetal node "glameow" with 4.15.0-159-generic, the test cases number and results are identical before and after applying this change. [Where problems could occur] - As this is just tested with generic Bionic 4.15 kernel on bare-metal, there is no guarantee this can work flawlessly on variants. + As this is just tested with generic Bionic 4.15 kernel on a bare-metal system, it's is possible to see other issues on different variants. If this change is incorrect it will cause issue to our automated-testing and regression-testing, but it won't affect the real kernel functionality. -- 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/1949889 Title: Unable to build net/reuseport_bpf and other tests in ubuntu_kernel_selftests on Bionic with make command Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Bug description: [Impact] With 4.15 kernel, not all binary files inside a subtest directory in tools/testing/selftests of a kernel tree can be built with command: make TARGETS=$subtest For example, the following tests in net directory won't be built: * reuseport_bpf * reuseport_bpf_cpu * reuseport_dualstack * reuseaddr_conflict * reuseport_bpf_numa They can be build with: make TARGETS=net run_tests However, this will also start all of the tests in this subset, which is not ideal for the granularity improvement. [Fix] 1. 14f1889f selftests: Fix loss of test output in run_kselftests.sh 2. 44f01352 selftests: Makefile set KSFT_TAP_LEVEL to prevent nested TAP headers 3. 8ce72dc3 selftests: fix headers_install circular dependency 4. 27d79a2b selftests: fix bpf build/test workflow regression when KBUILD_OUTPUT is set 5. e2e88325 selftests: vm: Fix test build failure when built by itself The 2nd, 3rd and 4th patch would need to be applied with -C1, the other two can be cherry-picked for Bionic. The third patch (8ce72dc3) is the fix for this issue. The 4th (27d79a2b) and the 5th (e2e88325) have been marked as a fix for 8ce72dc3. [Test] Tested on a baremetal node "glameow" with 4.15.0-159-generic, the test cases number and results are identical before and after applying this change. [Where problems could occur] As this is just tested with generic Bionic 4.15 kernel on a bare-metal system, it's is possible to see other issues on different variants. If this change is incorrect it will cause issue to our automated-testing and regression-testing, but it won't affect the real kernel functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949889/+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 1949889] Re: Unable to build net/reuseport_bpf and other tests in ubuntu_kernel_selftests on Bionic with make command
** Description changed: [Impact] With 4.15 kernel, not all binary files inside a subtest directory in tools/testing/selftests of a kernel tree can be built with command: make TARGETS=$subtest For example, the following tests in net directory won't be built: * reuseport_bpf * reuseport_bpf_cpu * reuseport_dualstack * reuseaddr_conflict * reuseport_bpf_numa They can be build with: make TARGETS=net run_tests However, this will also start all of the tests in this subset, which is not ideal for the granularity improvement. [Fix] * 14f1889f selftests: Fix loss of test output in run_kselftests.sh - * 44f01352 selftests: Makefile set KSFT_TAP_LEVEL to prevent nested TAP headers - * 8ce72dc3 selftests: fix headers_install circular dependency + * 44f01352 selftests: Makefile set KSFT_TAP_LEVEL to prevent nested TAP headers + * 8ce72dc3 selftests: fix headers_install circular dependency + * 27d79a2b selftests: fix bpf build/test workflow regression when KBUILD_OUTPUT is set + * e2e88325 selftests: vm: Fix test build failure when built by itself - These patches can be cherry-picked for Bionic. The third patch + These patches can be cherry-picked for Bionic. + The third patch (8ce72dc3) is the fix for this issue. The 4th (27d79a2b) and the 5th (e2e88325) have been marked as a fix for 8ce72dc3. [Test] Tested on a baremetal node "glameow" with 4.15.0-159-generic [Where problems could occur] + As this is just tested with generic Bionic 4.15 kernel on bare-metal, there is no guarantee this can work flawlessly on variants. -- 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/1949889 Title: Unable to build net/reuseport_bpf and other tests in ubuntu_kernel_selftests on Bionic with make command Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Bug description: [Impact] With 4.15 kernel, not all binary files inside a subtest directory in tools/testing/selftests of a kernel tree can be built with command: make TARGETS=$subtest For example, the following tests in net directory won't be built: * reuseport_bpf * reuseport_bpf_cpu * reuseport_dualstack * reuseaddr_conflict * reuseport_bpf_numa They can be build with: make TARGETS=net run_tests However, this will also start all of the tests in this subset, which is not ideal for the granularity improvement. [Fix] * 14f1889f selftests: Fix loss of test output in run_kselftests.sh * 44f01352 selftests: Makefile set KSFT_TAP_LEVEL to prevent nested TAP headers * 8ce72dc3 selftests: fix headers_install circular dependency * 27d79a2b selftests: fix bpf build/test workflow regression when KBUILD_OUTPUT is set * e2e88325 selftests: vm: Fix test build failure when built by itself These patches can be cherry-picked for Bionic. The third patch (8ce72dc3) is the fix for this issue. The 4th (27d79a2b) and the 5th (e2e88325) have been marked as a fix for 8ce72dc3. [Test] Tested on a baremetal node "glameow" with 4.15.0-159-generic [Where problems could occur] As this is just tested with generic Bionic 4.15 kernel on bare-metal, there is no guarantee this can work flawlessly on variants. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949889/+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
