[Kernel-packages] [Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
Updated to 5.15.0-18-generic and now the network adapter doesn't work at all. -- 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/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot Status in linux package in Ubuntu: Confirmed Bug description: The undefined behaviour sanitiser picks up an array-index-out-of- bounds in the aquantia atlantic driver. The NIC is (I think) built into my gigabyte motherboard (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME- rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to 22.04 (or at least dmesg didn't previously complain). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 13:02:10 2022 InstallationDate: Installed on 2019-08-07 (899 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS XTREME-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS XTREME dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+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 1959073] Re: kernel unable to detect disks on ASMedia Technology Inc. ASM1062 controller
Still not working with latest kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959073 Title: kernel unable to detect disks on ASMedia Technology Inc. ASM1062 controller Status in linux package in Ubuntu: New Bug description: Upgraded from 21.10 to 22.04. Kernel is no longer able to detect speed of disks on "ASMedia Technology Inc. ASM1062" controller: [1.262159] ata5: SATA max UDMA/133 abar m512@0xdf81 port 0xdf810100 irq 166 [1.945237] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [1.945242] ata5.00: link online but device misclassified [1.945243] ata5: link online but 1 devices misclassified, retrying [1.945244] ata5: reset failed (errno=-11), retrying in 10 secs [ 11.941338] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 11.941436] ata5.00: link online but device misclassified [ 11.941586] ata5: link online but 1 devices misclassified, retrying [ 11.941759] ata5: reset failed (errno=-11), retrying in 10 secs [ 22.181347] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 22.181443] ata5.00: link online but device misclassified [ 22.181594] ata5: link online but 1 devices misclassified, retrying [ 22.181740] ata5: reset failed (errno=-11), retrying in 35 secs [ 58.569320] ata5: limiting SATA link speed to 1.5 Gbps [ 59.045347] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 59.045359] ata5.00: link online but device misclassified [ 59.045519] ata5: link online but 1 devices misclassified, device detection might fail ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CustomUdevRuleFiles: md126.rules md127.rules 60-vboxdrv.rules 70-snap.core.rules Date: Wed Jan 26 08:44:00 2022 InstallationDate: Installed on 2020-04-10 (655 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c317 Logitech, Inc. Wave Corded Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=d2123ad2-32ac-4a77-abf1-468ac80f097c ro SourcePackage: udisks2 Symptom: storage Title: Internal hard disk partition cannot be mounted manually UpgradeStatus: Upgraded to jammy on 2022-01-26 (0 days ago) dmi.bios.date: 03/14/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3801 dmi.board.asset.tag: Default string dmi.board.name: Z170-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-PRO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959073/+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 1821152] Re: lxc-test-no-new-privs failed with Temporary failure resolving 'archive.ubuntu.com'
Still visible on Impish, we should probably use newer container image for the test. ** Tags added: sru-20220103 ** Tags added: 5.13 impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1821152 Title: lxc-test-no-new-privs failed with Temporary failure resolving 'archive.ubuntu.com' Status in ubuntu-kernel-tests: Triaged Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Bug description: It seems this failure only exist in KVM instances. FAIL: lxc-tests: lxc-test-no-new-privs (37s) --- + DONE=0 + trap cleanup EXIT SIGHUP SIGINT SIGTERM + mkdir -p /etc/lxc/ + cat + ARCH=i386 + type dpkg ++ dpkg --print-architecture + ARCH=amd64 + lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64 Setting up the GPG keyring Downloading the image index Downloading the rootfs Downloading the metadata The image cache is now ready Unpacking the rootfs --- You just created an Ubuntu xenial amd64 (20190320_07:42) container. To enable SSH, run: apt install openssh-server No default root or user password are set by LXC. + echo 'lxc.no_new_privs = 1' + lxc-start -n c1 ++ lxc-info -n c1 -p -H + p1=8818 + '[' 8818 '!=' -1 ']' + sleep 5s + lxc-attach -n c1 --clear-env -- apt update -y WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Err:1 http://archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'archive.ubuntu.com' Reading package lists... Building dependency tree... Reading state information... All packages are up to date. W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. + lxc-attach -n c1 --clear-env -- apt install -y gcc make WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: binutils cpp cpp-5 gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev libcc1-0 libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 libmpc3 libmpfr4 libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev manpages manpages-dev Suggested packages: binutils-doc cpp-doc gcc-5-locales gcc-multilib autoconf automake libtool flex bison gdb gcc-doc gcc-5-multilib gcc-5-doc libgcc1-dbg libgomp1-dbg libitm1-dbg libatomic1-dbg libasan2-dbg liblsan0-dbg libtsan0-dbg libubsan0-dbg libcilkrts5-dbg libmpx0-dbg libquadmath0-dbg glibc-doc make-doc man-browser The following NEW packages will be installed: binutils cpp cpp-5 gcc gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev libcc1-0 libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 libmpc3 libmpfr4 libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev make manpages manpages-dev 0 upgraded, 26 newly installed, 0 to remove and 0 not upgraded. Need to get 28.7 MB of archives. After this operation, 102 MB of additional disk space will be used. Err:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpfr4 amd64 3.1.4-1 Temporary failure resolving 'archive.ubuntu.com' Err:2 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpc3 amd64 1.0.3-1 Temporary failure resolving 'archive.ubuntu.com' Err:3 http://archive.ubuntu.com/ubuntu xenial/main amd64 manpages all 4.04-2 Temporary failure resolving 'archive.ubuntu.com' Err:4 http://security.ubuntu.com/ubuntu xenial-security/main amd64 binutils amd64 2.26.1-1ubuntu1~16.04.8 Temporary failure resolving 'archive.ubuntu.com' Err:5 http://archive.ubuntu.com/ubuntu xenial/main amd64 libisl15 amd64 0.16.1-1 Temporary failure resolving 'archive.ubuntu.com' It's a bit weird that if I run the command manually, it looks OK lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64 lxc-start -n c1 lxc-attach -n c1 --clear-env -- apt update -y Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease Get:2 http://archive.ubuntu.com/ubuntu
[Kernel-packages] [Bug 1954938] Re: Include the QCA WCN 6856 v2.1 support
** Summary changed: - Include the QCA WCN 6856 v2.1 support - WIFI 6 + Include the QCA WCN 6856 v2.1 support -- 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/1954938 Title: Include the QCA WCN 6856 v2.1 support Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: Incomplete Status in linux-firmware source package in Impish: New Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Incomplete Status in linux-firmware source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954938/+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 1947999] Re: Ubuntu on Wayland stutters, runs at half frame rate for Nvidia Ampere cards
Won't Fix. Mutter 41.2 and later uses the new GBM backend that avoids this bug. It requires NVIDIA 495 though. ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1947999 Title: Ubuntu on Wayland stutters, runs at half frame rate for Nvidia Ampere cards Status in Mutter: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Won't Fix Bug description: GNOME on Wayland stutters, runs at half frame rate for Nvidia Ampere cards. https://forums.developer.nvidia.com/t/eglstreamconsumeracquireattribnv- function-execution-became-significantly-slower-in-470-42-01-driver- release/182746/6 Workaround: Use a Xorg session instead. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1947999/+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 1958952] Re: ARM64 node dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9"
** Also affects: ubuntu-kernel-tests 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/1958952 Title: ARM64 node dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9" Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Bug description: While investigating the SRU deployment failure, I noticed the dmesg will be spammed with: Jan 25 07:48:36 appleton-kernel kernel: [ 22.885627] mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9 Jan 25 07:48:36 appleton-kernel kernel: [ 22.885628] mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1218): Completion event for bogus CQ 0x5a5aa9 Jan 25 07:48:36 appleton-kernel kernel: [ 22.885629] mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9 Jan 25 07:48:36 appleton-kernel kernel: [ 22.885631] mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9 Issue found with Focal 5.4.0-96-generic Please find attachment for the syslog. Not sure if this is cause of our deployment issue, but it seems odd to me. And here is our deployment issue: 1. System successfully deployed with Focal 2. Deployment process hangs with "Enabling PPA" stage 3. I cannot connect to this system manually, ssh hangs (soft lockup maybe?) after: Warning: Permanently added '10.229.50.13' (ECDSA) to the list of known hosts. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-96-generic 5.4.0-96.109 ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157 Uname: Linux 5.4.0-96-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 25 07:48 seq crw-rw 1 root audio 116, 33 Jan 25 07:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Tue Jan 25 07:53:33 2022 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 004: ID 12d1:0003 Huawei Technologies Co., Ltd. Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 1: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Hisilicon D05 PciMultimedia: ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-96-generic root=UUID=3abb8e5a-2f46-4221-b664-cb02a273a249 ro sysrq_always_enabled RelatedPackageVersions: linux-restricted-modules-5.4.0-96-generic N/A linux-backports-modules-5.4.0-96-generic N/A linux-firmware1.187.25 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.50 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC11SPCD dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Hisilicon dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.50:bd06/01/2018:svnHisilicon:pnD05:pvrV100R001C00:rvnHuawei:rnBC11SPCD:rvrVER.A:cvnHisilicon:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: D05 dmi.product.sku: To be filled by O.E.M. dmi.product.version: V100R001C00 dmi.sys.vendor: Hisilicon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1958952/+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 1958850] Re: USB port lost function after unplugging usb drive
SRUed on this, (U/OEM-5.14) https://lists.ubuntu.com/archives/kernel-team/2022-January/127554.html ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) -- 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/1958850 Title: USB port lost function after unplugging usb drive Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Test the proposed 5.14 oem kernel, and get a failure symptom. Unplug a usb drive from WD19TB docking and a BUG reported in kernel, then the other embedded usb port can't detect usb drive anymore after a while. kernel: usb 5-2.3.3: USB disconnect, device number 5 kernel: BUG: kernel NULL pointer dereference, address: 0030 kernel: #PF: supervisor read access in kernel mode kernel: #PF: error_code(0x) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: [#1] SMP NOPTI [Fix] 2a19b28f7929) blk-mq: cancel blk-mq dispatch work... is the first regression and it lands mainline since v5.16-rc2. After applied https://lore.kernel.org/all/20210816134624.ga24...@lst.de/#r, issue is gone. the patches has beend landed since v5.15-rc1. [Test Case] 1. plug usb driver on the machine. 2. unplug usb driver. 3. check the dmesg if the oops would be shown [Where problems could occur] Medium ~~~ Test the proposed 5.14 oem kernel, and get a failure symptom. Unplug a usb drive from WD19TB docking and a BUG reported in kernel, then the other embedded usb port can't detect usb drive anymore after a while. kernel: usb 5-2.3.3: USB disconnect, device number 5 kernel: BUG: kernel NULL pointer dereference, address: 0030 kernel: #PF: supervisor read access in kernel mode kernel: #PF: error_code(0x) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: [#1] SMP NOPTI --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 2205 F pulseaudio /dev/snd/controlC0: u 2205 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-04-29 (270 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. Precision 5750 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1021-oem N/A linux-backports-modules-5.14.0-1021-oem N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.14.0-1021-oem x86_64 UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990: dmi.product.family: Precision dmi.product.name: Precision 5750 dmi.product.sku: 0990 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1958850/+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 1958850] Re: USB port lost function after unplugging usb drive
** Description changed: + [Impact] Test the proposed 5.14 oem kernel, and get a failure symptom. Unplug a usb drive from WD19TB docking and a BUG reported in kernel, then the other embedded usb port can't detect usb drive anymore after a while. kernel: usb 5-2.3.3: USB disconnect, device number 5 kernel: BUG: kernel NULL pointer dereference, address: 0030 kernel: #PF: supervisor read access in kernel mode kernel: #PF: error_code(0x) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: [#1] SMP NOPTI - --- + + [Fix] + After applied https://lore.kernel.org/all/20210816134624.ga24...@lst.de/#r, issue is gone. + the patches has beend landed since v5.15-rc1. + + [Test Case] + 1. plug usb driver on the machine. + 2. unplug usb driver. + 3. check the dmesg if the oops would be shown + + [Where problems could occur] + Medium + ~~~ + Test the proposed 5.14 oem kernel, and get a failure symptom. + + Unplug a usb drive from WD19TB docking and a BUG reported in kernel, + then the other embedded usb port can't detect usb drive anymore after a + while. + + kernel: usb 5-2.3.3: USB disconnect, device number 5 + kernel: BUG: kernel NULL pointer dereference, address: 0030 + kernel: #PF: supervisor read access in kernel mode + kernel: #PF: error_code(0x) - not-present page + kernel: PGD 0 P4D 0 + kernel: Oops: [#1] SMP NOPTI + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: u 2205 F pulseaudio - /dev/snd/controlC0: u 2205 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: u 2205 F pulseaudio + /dev/snd/controlC0: u 2205 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-04-29 (270 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. Precision 5750 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21 RelatedPackageVersions: - linux-restricted-modules-5.14.0-1021-oem N/A - linux-backports-modules-5.14.0-1021-oem N/A - linux-firmware 1.201.3 + linux-restricted-modules-5.14.0-1021-oem N/A + linux-backports-modules-5.14.0-1021-oem N/A + linux-firmware 1.201.3 Tags: impish Uname: Linux 5.14.0-1021-oem x86_64 UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990: dmi.product.family: Precision dmi.product.name: Precision 5750 dmi.product.sku: 0990 dmi.sys.vendor: Dell Inc. ** Description changed: [Impact] Test the proposed 5.14 oem kernel, and get a failure symptom. Unplug a usb drive from WD19TB docking and a BUG reported in kernel, then the other embedded usb port can't detect usb drive anymore after a while. kernel: usb 5-2.3.3: USB disconnect, device number 5 kernel: BUG: kernel NULL pointer dereference, address: 0030 kernel: #PF: supervisor read access in kernel mode kernel: #PF: error_code(0x) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: [#1] SMP NOPTI [Fix] + 2a19b28f7929) blk-mq: cancel blk-mq dispatch work... is the first regression and it lands mainline since v5.16-rc2. + After applied https://lore.kernel.org/all/20210816134624.ga24...@lst.de/#r, issue is gone. the patches has beend landed since v5.15-rc1. [Test Case] 1. plug usb driver on the machine. 2. unplug usb driver. 3. check the dmesg if the oops would be shown [Where problems could occur] Medium ~~~ Test the proposed 5.14 oem kernel, and get a failure symptom. Unplug a usb drive from WD19TB docking and a BUG reported in kernel, then the other embedded usb port can't detect usb drive anymore after a while. kernel: usb 5-2.3.3: USB disconnect, device number 5 kernel: BUG: kernel NULL pointer dereference, address: 0030 kernel: #PF: supervisor read access in kernel mode kernel: #PF: error_code(0x) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: [#1] SMP NOPTI --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USER
[Kernel-packages] [Bug 1958850] Re: USB port lost function after unplugging usb drive
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Incomplete => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) -- 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/1958850 Title: USB port lost function after unplugging usb drive Status in OEM Priority Project: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Bug description: [Impact] Test the proposed 5.14 oem kernel, and get a failure symptom. Unplug a usb drive from WD19TB docking and a BUG reported in kernel, then the other embedded usb port can't detect usb drive anymore after a while. kernel: usb 5-2.3.3: USB disconnect, device number 5 kernel: BUG: kernel NULL pointer dereference, address: 0030 kernel: #PF: supervisor read access in kernel mode kernel: #PF: error_code(0x) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: [#1] SMP NOPTI [Fix] After applied https://lore.kernel.org/all/20210816134624.ga24...@lst.de/#r, issue is gone. the patches has beend landed since v5.15-rc1. [Test Case] 1. plug usb driver on the machine. 2. unplug usb driver. 3. check the dmesg if the oops would be shown [Where problems could occur] Medium ~~~ Test the proposed 5.14 oem kernel, and get a failure symptom. Unplug a usb drive from WD19TB docking and a BUG reported in kernel, then the other embedded usb port can't detect usb drive anymore after a while. kernel: usb 5-2.3.3: USB disconnect, device number 5 kernel: BUG: kernel NULL pointer dereference, address: 0030 kernel: #PF: supervisor read access in kernel mode kernel: #PF: error_code(0x) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: [#1] SMP NOPTI --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 2205 F pulseaudio /dev/snd/controlC0: u 2205 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-04-29 (270 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. Precision 5750 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1021-oem N/A linux-backports-modules-5.14.0-1021-oem N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.14.0-1021-oem x86_64 UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990: dmi.product.family: Precision dmi.product.name: Precision 5750 dmi.product.sku: 0990 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958850/+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 1958248] Re: [amdgpu] Screen garbled on login and freezes on resume from suspend (kernel 5.13.0-25.26~20.04.1-generic)
*** This bug is a duplicate of bug 1958591 *** https://bugs.launchpad.net/bugs/1958591 ** This bug is no longer a duplicate of bug 1958412 [amdgpu] Flickering/noise on screen started in kernel 5.13 ** This bug has been marked a duplicate of bug 1958591 [amdgpu] Random noise 'static' display after internal display turned off/on -- 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/1958248 Title: [amdgpu] Screen garbled on login and freezes on resume from suspend (kernel 5.13.0-25.26~20.04.1-generic) Status in linux package in Ubuntu: Confirmed Bug description: 1. The login manager works but as soon as I log in, the screen is filled with colored vertical stripes and is unusable. I found that if I change the screen resolution to the maximum (1920x1080), then the screen is ok. Any other resolution that I've tried (eg (1440x900 used to be my preference) causes the unreadable display and it does not revert back, requiring a reboot. 2. Coming out of suspend, the password entry screen is displayed, but there is no response to keyboard or mouse, requiring a reboot. HP Envy x360 laptop with AMD Ryzen 7 with Radeon graphics Last known kernel that worked is 5.11.0-46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958248/+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 1958631] Re: [amdgpu] Flickering internal monitor
*** This bug is a duplicate of bug 1958591 *** https://bugs.launchpad.net/bugs/1958591 ** This bug is no longer a duplicate of bug 1958412 [amdgpu] Flickering/noise on screen started in kernel 5.13 ** This bug has been marked a duplicate of bug 1958591 [amdgpu] Random noise 'static' display after internal display turned off/on -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958631 Title: [amdgpu] Flickering internal monitor Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: Hello everybody, Recently my internal monitor on my laptop (HP Pavilion Gaming 15) starts flickering after boot. On my laptop I have Geforce 1660 Ti beside AMD Renoir. Formerly I had the problem of not detecting the external monitor but solved it. Now this problem has arisen. I have also updated the kernel to 5.13 recently. I would appreciate any solution to the problem. Thank you ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.86 Tue Oct 26 21:55:45 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 09:24:58 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.86, 5.13.0-25-generic, x86_64: installed nvidia, 470.86, 5.13.0-27-generic, x86_64: installed virtualbox, 6.1.26, 5.13.0-25-generic, x86_64: installed virtualbox, 6.1.26, 5.13.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:87b3] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87b3] InstallationDate: Installed on 2021-02-01 (353 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP Pavilion Gaming Laptop 15-ec1xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=a852eab7-471e-4804-9ed4-2517ad4e6218 ro quiet splash amdgpu.exp_hw_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2021 dmi.bios.release: 15.25 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87B3 dmi.board.vendor: HP dmi.board.version: 31.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 31.23 dmi.modalias: dmi:bvnAMI:bvrF.25:bd08/18/2021:br15.25:efr31.23:svnHP:pnHPPavilionGamingLaptop15-ec1xxx:pvr:rvnHP:rn87B3:rvr31.23:cvnHP:ct10:cvrChassisVersion:sku1B2E2EA#ABD: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-ec1xxx dmi.product.sku: 1B2E2EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1958823] Re: Screen Keeps Blinking/Flickering after waking up from lock
*** This bug is a duplicate of bug 1958591 *** https://bugs.launchpad.net/bugs/1958591 ** This bug is no longer a duplicate of bug 1958412 [amdgpu] Flickering/noise on screen started in kernel 5.13 ** This bug has been marked a duplicate of bug 1958591 [amdgpu] Random noise 'static' display after internal display turned off/on -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958823 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Screen Keeps Blinking/Flickering after waking up from lock ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 24 10:44:54 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164c] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3f95] InstallationDate: Installed on 2022-01-11 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 82KT ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=7e63c3e2-afff-4841-8da3-9dad122a8352 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: GLCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55726WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 14ALC6 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrGLCN40WW:bd07/23/2021:br1.40:efr1.40:svnLENOVO:pn82KT:pvrIdeaPad314ALC6:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrIdeaPad314ALC6:skuLENOVO_MT_82KT_BU_idea_FM_IdeaPad314ALC6: dmi.product.family: IdeaPad 3 14ALC6 dmi.product.name: 82KT dmi.product.sku: LENOVO_MT_82KT_BU_idea_FM_IdeaPad 3 14ALC6 dmi.product.version: IdeaPad 3 14ALC6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958823/+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 1958890] Re: [amdgpu] the screen is flickering after waking up from sleep
*** This bug is a duplicate of bug 1958591 *** https://bugs.launchpad.net/bugs/1958591 ** This bug is no longer a duplicate of bug 1958412 [amdgpu] Flickering/noise on screen started in kernel 5.13 ** This bug has been marked a duplicate of bug 1958591 [amdgpu] Random noise 'static' display after internal display turned off/on -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958890 Title: [amdgpu] the screen is flickering after waking up from sleep Status in linux-hwe-5.13 package in Ubuntu: New Bug description: the screen is flcikering after waking up from sleep ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 24 23:04:53 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 5.6.0.15-1098277: added ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164c] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3f95] InstallationDate: Installed on 2022-01-11 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 82KT ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=7e63c3e2-afff-4841-8da3-9dad122a8352 ro nouveau.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 07/23/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: GLCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55726WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 14ALC6 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrGLCN40WW:bd07/23/2021:br1.40:efr1.40:svnLENOVO:pn82KT:pvrIdeaPad314ALC6:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrIdeaPad314ALC6:skuLENOVO_MT_82KT_BU_idea_FM_IdeaPad314ALC6: dmi.product.family: IdeaPad 3 14ALC6 dmi.product.name: 82KT dmi.product.sku: LENOVO_MT_82KT_BU_idea_FM_IdeaPad 3 14ALC6 dmi.product.version: IdeaPad 3 14ALC6 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958890/+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 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on
** Changed in: linux-hwe-5.13 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958591 Title: [amdgpu] Random noise 'static' display after internal display turned off/on Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: Laptop internal display shows random looking 'static' after it's turned off and then on again. e.g. on suspend/resume, or when plugging/unplugging an external monitor. This appeared to come after a `dist-upgrade` took the kernel from 5.11.0-44 to 5.13.0-25 (hwe). Others are seeing this with both NVidia and AMD graphics hardware: - https://www.reddit.com/r/Ubuntu/comments/s8c83w/laptop_shows_static_screen_after_going_into_lock/ - https://www.reddit.com/r/Ubuntu/comments/s8fit0/please_help_static_noise_display_on_ubuntu_2004/ I use i3 under gnome-flashback, but tried using default Ubuntu/Gnome both X and Wayland, and gnome-flashback/metacity. All showed the same problem. Also tried an `apt install --reinstall xserver-xorg-video-radeon libdrm-radeon1` for luck - no joy. Running a 20.04.3 live stick the problem does *not* occur. System: Thinkpad X13 Gen1 Processor: AMD Ryzen 7 PRO 4750U System Firmware: 1.35 $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 Happy to assist with investigations. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: i3-GNOME-Flashback:GNOME-Flashback:GNOME Date: Thu Jan 20 19:37:09 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5082] InstallationDate: Installed on 2021-06-24 (210 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20UF0014US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=5db0269f-fa23-487e-ace8-ba99bca814a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET67W(1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UF0014US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnLENOVO:bvrR1CET67W(1.36):bd10/20/2021:br1.36:efr1.36:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UF0014US dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958591/+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 1958412] Re: [amdgpu] Flickering/noise on screen started in kernel 5.13
*** This bug is a duplicate of bug 1958591 *** https://bugs.launchpad.net/bugs/1958591 Bug 1958591 seems to be more active and they are resisting being marked as a duplicate of this. So I'll take the unusual step of making this a duplicate of that newer bug. ** Changed in: linux-hwe-5.13 (Ubuntu) Importance: Undecided => High ** This bug has been marked a duplicate of bug 1958591 [amdgpu] Random noise 'static' display after internal display turned off/on -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958412 Title: [amdgpu] Flickering/noise on screen started in kernel 5.13 Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: After the kernel release 5.13.0-27-generic was installed today, the startup and shutdown processes finish with white noise screens. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Wed Jan 19 16:17:35 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164c] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:18b2] InstallationDate: Installed on 2022-01-19 (0 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP420UA_TM420UA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=c4ec4ae8-c14c-4c0b-9922-9142270cef97 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: TP420UA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP420UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.2 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrTP420UA.302:bd09/06/2021:br5.19:efr3.2:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP420UA_TM420UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP420UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: VivoBook Flip dmi.product.name: VivoBook_ASUSLaptop TP420UA_TM420UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958412/+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 1958523] Re: [amdgpu] Static-noise-like effect
*** This bug is a duplicate of bug 1958591 *** https://bugs.launchpad.net/bugs/1958591 ** This bug is no longer a duplicate of bug 1958412 [amdgpu] Flickering/noise on screen started in kernel 5.13 ** This bug has been marked a duplicate of bug 1958591 [amdgpu] Random noise 'static' display after internal display turned off/on -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958523 Title: [amdgpu] Static-noise-like effect Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: Hello, I have encountered a bug in Ubuntu. When I turn on my laptop and log in (I can see the login screen) I see static-noise-like effect. I was able to make a screenshot and it depicts my desktop as if the problem didn't exist. Switching to stable (non-HWE) kernel solves the issue. My desktop environment is GNOME. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958523/+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 1959340] Re: frequent color snowing on screen after resuming from suspend
*** This bug is a duplicate of bug 1958591 *** https://bugs.launchpad.net/bugs/1958591 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1958412, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** This bug has been marked a duplicate of bug 1958412 [amdgpu] Flickering/noise on screen started in kernel 5.13 ** This bug is no longer a duplicate of bug 1958412 [amdgpu] Flickering/noise on screen started in kernel 5.13 ** This bug has been marked a duplicate of bug 1958591 [amdgpu] Random noise 'static' display after internal display turned off/on -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1959340 Title: frequent color snowing on screen after resuming from suspend Status in linux-hwe-5.13 package in Ubuntu: New Bug description: For the last 2 days my Thinkpad X13 laptop frequently opens with snowing pixels across the whole screen. The only way to stop it seems to be to hard-reset my laptop. $ uname -a Linux X13 5.13.0-27-generic #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 27 13:56:42 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5082] InstallationDate: Installed on 2021-09-23 (126 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20UF0014US ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=8e981ab2-e4f0-4607-b2c4-587a6db04c7d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UF0014US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrR1CET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UF0014US dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1959340/+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 1959340] [NEW] frequent color snowing on screen after resuming from suspend
You have been subscribed to a public bug: For the last 2 days my Thinkpad X13 laptop frequently opens with snowing pixels across the whole screen. The only way to stop it seems to be to hard-reset my laptop. $ uname -a Linux X13 5.13.0-27-generic #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 27 13:56:42 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5082] InstallationDate: Installed on 2021-09-23 (126 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20UF0014US ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=8e981ab2-e4f0-4607-b2c4-587a6db04c7d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UF0014US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrR1CET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UF0014US dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu -- frequent color snowing on screen after resuming from suspend https://bugs.launchpad.net/bugs/1959340 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959348] [NEW] Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27 Induce Laptop Screen Crash
Public bug reported: Please accept my apologies up front for any inefficiencies this format may induce, as I'm a very casual user who has just started to scratch the surface of Linux distro usage. I have read the instructions on the report submission page and I believe I am following the guidance, but if I'm not it's because of unfamiliarity and general ignorance. I beg for your patience and understanding. For the listed kernels in the summary line (kernels 5.13.0-21, -22, -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to snow/white noise immediately whenever the following conditions are met: 1) Any video peripheral is connected to the laptop via the HDMI port directly or through a USB-C hub with HDMI input AND 2) The "Mirror" selection is toggled in the Display Manager GUI OR 3) The HDMI cable is removed from the HDMI port/USB-C hub I can confirm that: 1) The HDMI cable is not the culprit because this issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2) running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest any of the described screen crash issues listed above. That is to say, the laptop and peripheral HDMI display run stably/without issue while running Linux Mint 20.3 kernel 5.11.0-46 For your diagnostic consideration: System Info: [code] System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.2.7 wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal Machine: Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: Mobo: RO model: Kona_RN v: V1.10 serial: UEFI: Insyde v: 1.10 date: 05/13/2021 Battery: ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 10.9/11.2 model: LGC AP18C8K serial: status: Discharging CPU: Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics bits: 64 type: MCP arch: Zen rev: 1 L2 cache: 4096 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 31938 Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 2: 1397 3: 1396 4: 1397 5: 1908 6: 1761 7: 1736 8: 2286 Graphics: Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu v: kernel bus ID: 03:00.0 chip ID: 1002:1636 Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz, 1920x1080~60Hz OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 21.0.3 compat-v: 3.1 direct render: Yes Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel bus ID: 03:00.1 chip ID: 1002:1637 Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel bus ID: 03:00.5 chip ID: 1022:15e2 Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel bus ID: 03:00.6 chip ID: 1022:15e3 Sound Server: ALSA v: k5.11.0-46-generic Network: Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 01:00.0 chip ID: 8086:2723 IF: wlp1s0 state: up mac: Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%) ID-1: /dev/nvme0n1 vendor: Western Digital model: WDBRPG0010BNC-WRSN size: 931.51 GiB speed: 31.6 Gb/s lanes: 4 serial: Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: /dev/nvme0n1p5 USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip ID: 1d6b:0002 Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 chip ID: 8087:0029 Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip ID: 1d6b:0003 Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip ID: 1d6b:0002 Device-2: 3-1:2 info: LighTuning EgisTec EH575 type: driver: N/A rev: 2.0 chip ID: 1c7a:0575 Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt Wheel type: Mouse driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2 Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip ID: 1d6b:0003 Sensors: System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu temp: 40 C Fan Speeds (RPM): N/A Repos: No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg arch=amd64] https: //brave-browser-apt-release.s3.brave.com/ stable main Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 1: deb [arch=amd64] https: //dl.google.com/linux/chrome/deb/ stable main Active apt repos in:
[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
This bug is awaiting verification that the linux-
gcp-5.13/5.13.0-1013.16~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956401
Title:
amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22
works
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification
Impact:
This does not occur with linux-image-5.13.0-22-generic, but does with
linux-image-5.13.0-23-generic.
On startup, I get about a 60 second hang, with the following in the kernel
dmesg:
Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0:
amdgp : failed to write reg 28b4 wait reg 28c6
Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0:
amdgp : failed to write reg 1a6f4 wait reg 1a706
Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0:
amdgp : failed to write reg 28b4 wait reg 28c6
Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0:
amdgp : failed to write reg 1a6f4 wait reg 1a706
I have the following GPU:
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Picass
o (rev c2) (prog-if 00 [VGA controller])
04:00.0 0300: 1002:15d8 (rev c2)
(This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.)
I get a similar hang if I start firefox (when it's probing OpenGL
contexts), and even with glxgears and glxinfo. Seems like anything
that'd kick on a OpenGL context does it. I had a freeze as well when
I tried running firefox and glxgears both. Along with odd BUG:
messages logged (I have some in the attached log.)
I was running with "iommu=pt", but did try with this removed, still
got the errors (I think amdgpu driver uses the IOMMU even when it's
set to IOMMU=pt though.). See the attached log for some very odd
"[Hardware Error]" messages that were logged on one test run. I think
this was when I tried to run firestorm (second life viewer) -- that
had a large pause then opened to a black window.
Per Google, I see there was a bug like this that turned up in kernel
5.14.15 but fixed in 5.14.17. See
https://gitlab.freedesktop.org/drm/amd/-/issues/1770
Thanks!
--Henry
Fix:
upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is
disabled in Picasso.")
Patch was included in the Impish kernel in -proposed (5.13.0.24.24)
from an upstream patch set. multiple confirmations the problem is
resolved with the kernel in -proposed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+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 1956585] Re: OOB write on BPF_RINGBUF
This bug is awaiting verification that the linux- gcp-5.13/5.13.0-1013.16~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956585 Title: OOB write on BPF_RINGBUF Status in linux package in Ubuntu: Fix Released Bug description: tr3e wang discovered that an OOB write existed in the eBPF subsystem in the Linux kernel on BPF_RINGBUF. Mitigation commit: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/impish/commit/?id=53fb7741ff9d546174dbb585957b4f8b6afbdb83 Mitigation: Disable unprivileged ebpf with: $ sudo sysctl kernel.unprivileged_bpf_disabled=1 Unprivileged ebpf is disabled by default in Ubuntu 21.10 and newer. See https://www.kernel.org/doc/html/latest/admin- guide/sysctl/kernel.html#unprivileged-bpf-disabled for details on the configuration setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956585/+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 1959345] [NEW] vulkaninfo reports error
Public bug reported: Tracker says mesa-vulkan-drivers is not in Ubuntu!? mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed] Ubuntu 18.04.6 LTS AMD Ryzen 7 2700x eight-core processor x 16 AMD Radeon rx 5700 xt apt-cache show says that vulkan-mesa-drivers provides vulkan-icd. find / -name vulkan-icd finds nothing vulkaninfo reports: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in /usr/share/vulkan/icd.d/ Either the error is a false positive or I should have amd_icd64.json - and then maybe all the other problems with the GPU would go away! ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959345 Title: vulkaninfo reports error Status in linux package in Ubuntu: New Bug description: Tracker says mesa-vulkan-drivers is not in Ubuntu!? mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed] Ubuntu 18.04.6 LTS AMD Ryzen 7 2700x eight-core processor x 16 AMD Radeon rx 5700 xt apt-cache show says that vulkan-mesa-drivers provides vulkan-icd. find / -name vulkan-icd finds nothing vulkaninfo reports: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in /usr/share/vulkan/icd.d/ Either the error is a false positive or I should have amd_icd64.json - and then maybe all the other problems with the GPU would go away! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959345/+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 1959335] [NEW] Bionic update: upstream stable patchset 2022-01-27
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: upstream stable patchset 2022-01-27 Ported from the following upstream stable releases: v4.14.261, v4.19.224 from git://git.kernel.org/ HID: asus: Add depends on USB_HID to HID_ASUS Kconfig option tee: handle lookup of shm with reference count 0 platform/x86: apple-gmux: use resource_size() with res recordmcount.pl: fix typo in s390 mcount regex selinux: initialize proto variable in selinux_ip_postroute_compat() scsi: lpfc: Terminate string in lpfc_debugfs_nvmeio_trc_write() net: usb: pegasus: Do not drop long Ethernet frames NFC: st21nfca: Fix memory leak in device probe and remove fsl/fman: Fix missing put_device() call in fman_port_probe nfc: uapi: use kernel size_t to fix user-space builds uapi: fix linux/nfc.h userspace compilation errors xhci: Fresco FL1100 controller should not have BROKEN_MSI quirk set. usb: gadget: f_fs: Clear ffs_eventfd in ffs_data_clear. binder: fix async_free_space accounting for empty parcels scsi: vmw_pvscsi: Set residual data length conditionally Input: appletouch - initialize work before device registration Input: spaceball - fix parsing of movement data packets net: fix use-after-free in tw_timer_handler sctp: use call_rcu to free endpoint Input: i8042 - add deferred probe support Input: i8042 - enable deferred probe quirk for ASUS UM325UA i2c: validate user data in compat ioctl usb: mtu3: set interval of FS intr and isoc endpoint UBUNTU: upstream stable to v4.14.261, v4.19.224 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) 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 Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu) Status: Won't Fix => 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: + upstream stable patchset 2022-01-27 -upstream stable patchset 2022-01-27 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v4.14.261, v4.19.224 + + from git://git.kernel.org/ + + HID: asus: Add depends on USB_HID to HID_ASUS Kconfig option + tee: handle lookup of shm with reference count 0 + platform/x86: apple-gmux: use resource_size() with res + recordmcount.pl: fix typo in s390 mcount regex + selinux: initialize proto variable in selinux_ip_postroute_compat() + scsi: lpfc: Terminate string in lpfc_debugfs_nvmeio_trc_write() + net: usb: pegasus: Do not drop long Ethernet frames + NFC: st21nfca: Fix memory leak in device probe and remove + fsl/fman: Fix missing put_device() call in fman_port_probe + nfc: uapi: use kernel size_t to fix user-space builds + uapi: fix linux/nfc.h userspace compilation errors + xhci: Fresco FL1100 controller should not have BROKEN_MSI quirk set. + usb: gadget: f_fs: Clear ffs_eventfd in ffs_data_clear. + binder: fix async_free_space accounting for empty parcels + scsi: vmw_pvscsi: Set residual data length conditionally + Input: appletouch - initialize work before device registration + Input: spaceball
[Kernel-packages] [Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
uname logfile ** Attachment added: "uname logfile" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+attachment/5557858/+files/uname-a.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/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot Status in linux package in Ubuntu: Confirmed Bug description: The undefined behaviour sanitiser picks up an array-index-out-of- bounds in the aquantia atlantic driver. The NIC is (I think) built into my gigabyte motherboard (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME- rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to 22.04 (or at least dmesg didn't previously complain). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 13:02:10 2022 InstallationDate: Installed on 2019-08-07 (899 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS XTREME-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS XTREME dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+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 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
lspci logfile ** Attachment added: "lspci logfile" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+attachment/5557857/+files/lspci-vvnn.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/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot Status in linux package in Ubuntu: Confirmed Bug description: The undefined behaviour sanitiser picks up an array-index-out-of- bounds in the aquantia atlantic driver. The NIC is (I think) built into my gigabyte motherboard (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME- rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to 22.04 (or at least dmesg didn't previously complain). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 13:02:10 2022 InstallationDate: Installed on 2019-08-07 (899 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS XTREME-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS XTREME dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+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 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
dmesg logfile ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+attachment/5557856/+files/dmesg.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/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot Status in linux package in Ubuntu: Confirmed Bug description: The undefined behaviour sanitiser picks up an array-index-out-of- bounds in the aquantia atlantic driver. The NIC is (I think) built into my gigabyte motherboard (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME- rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to 22.04 (or at least dmesg didn't previously complain). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 13:02:10 2022 InstallationDate: Installed on 2019-08-07 (899 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS XTREME-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS XTREME dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+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 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
Same in my system: [ 294.432996] UBSAN: array-index-out-of-bounds in /build/linux-Qow4fL/linux-5.15.0/drivers/net/ethernet/aquantia/atlantic/aq_nic.c:484:48 [ 294.433695] index 8 is out of range for type 'aq_vec_s *[8]' [ 294.434372] CPU: 5 PID: 1341 Comm: systemd-network Tainted: P O 5.15.0-17-generic #17-Ubuntu [ 294.434374] Hardware name: System manufacturer System Product Name/Z170-PRO, BIOS 3801 03/14/2018 [ 294.434374] Call Trace: [ 294.434376] [ 294.434377] show_stack+0x52/0x58 [ 294.434380] dump_stack_lvl+0x4a/0x5f [ 294.434383] dump_stack+0x10/0x12 [ 294.434384] ubsan_epilogue+0x9/0x45 [ 294.434385] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [ 294.434386] ? aq_nic_get_link_ksettings+0x58/0x380 [atlantic] [ 294.434393] ? aq_vec_start+0x94/0xb0 [atlantic] [ 294.434398] aq_nic_start+0x3af/0x3d0 [atlantic] [ 294.434402] aq_ndev_open+0x49/0x70 [atlantic] [ 294.434405] __dev_open+0xf3/0x1c0 [ 294.434408] __dev_change_flags+0x1a3/0x220 [ 294.434410] dev_change_flags+0x26/0x60 [ 294.434411] do_setlink+0x28a/0xc50 [ 294.434414] ? __nla_validate_parse+0x4c/0x1a0 [ 294.434416] rtnl_setlink+0xf6/0x170 [ 294.434419] rtnetlink_rcv_msg+0x15d/0x400 [ 294.434421] ? rtnl_calcit.isra.0+0x130/0x130 [ 294.434422] netlink_rcv_skb+0x55/0x100 [ 294.434424] rtnetlink_rcv+0x15/0x20 [ 294.434426] netlink_unicast+0x21d/0x330 [ 294.434427] netlink_sendmsg+0x24c/0x4c0 [ 294.434428] sock_sendmsg+0x65/0x70 [ 294.434430] __sys_sendto+0x113/0x190 [ 294.434433] __x64_sys_sendto+0x24/0x30 [ 294.434435] do_syscall_64+0x5c/0xc0 [ 294.434437] ? syscall_exit_to_user_mode+0x27/0x50 [ 294.434439] ? do_syscall_64+0x69/0xc0 [ 294.434440] ? __secure_computing+0x42/0xe0 [ 294.434442] ? syscall_trace_enter.constprop.0+0xa3/0x1c0 [ 294.43] ? exit_to_user_mode_prepare+0x37/0xb0 [ 294.434446] ? syscall_exit_to_user_mode+0x27/0x50 [ 294.434447] ? __do_sys_gettid+0x1b/0x20 [ 294.434449] ? do_syscall_64+0x69/0xc0 [ 294.434450] ? do_syscall_64+0x69/0xc0 [ 294.434451] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 294.434453] RIP: 0033:0x7feeaf99146a [ 294.434455] Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb b8 0f 1f 00 f3 0f 1e fa 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 15 b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 7e c3 0f 1f 44 00 00 41 54 48 83 ec 30 44 89 [ 294.434456] RSP: 002b:7ffc9cf72cf8 EFLAGS: 0246 ORIG_RAX: 002c [ 294.434458] RAX: ffda RBX: 55afe2a315e8 RCX: 7feeaf99146a [ 294.434458] RDX: 0020 RSI: 55afe2a30290 RDI: 0003 [ 294.434459] RBP: 55afe2a11900 R08: 7ffc9cf72d00 R09: 0080 [ 294.434460] R10: R11: 0246 R12: 55afe2a32bf0 [ 294.434461] R13: 053d R14: 55afe2a315a0 R15: 55afe13b0e40 [ 294.434462] -- 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/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot Status in linux package in Ubuntu: Confirmed Bug description: The undefined behaviour sanitiser picks up an array-index-out-of- bounds in the aquantia atlantic driver. The NIC is (I think) built into my gigabyte motherboard (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME- rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to 22.04 (or at least dmesg didn't previously complain). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 13:02:10 2022 InstallationDate: Installed on 2019-08-07 (899 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS XTREME-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default
[Kernel-packages] [Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot Status in linux package in Ubuntu: Confirmed Bug description: The undefined behaviour sanitiser picks up an array-index-out-of- bounds in the aquantia atlantic driver. The NIC is (I think) built into my gigabyte motherboard (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME- rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to 22.04 (or at least dmesg didn't previously complain). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 13:02:10 2022 InstallationDate: Installed on 2019-08-07 (899 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS XTREME-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS XTREME dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+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 1959061] Re: The display output on type-c hub doesn't work on ADL platform
Intel comments: The fix is merged to drm-tip -- 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/1959061 Title: The display output on type-c hub doesn't work on ADL platform Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] The display output(DP/HDMI) on the USB type-c hub doesn't work. No display output device could be found after the monitor is plugged into the hub. [Fix] Intel provide a new patch to fix this issue on ADL platforms. [Test] Verified on ADL platform with different type-c hubs, the display output works. [Where problems could occur] The TCSS_DDI_STATUS register is indexed by tc_port not by the FIA port index. So, this patch is more like a fix and only affect ADL platforms. And as the commit log describes, the value is wrong on TC#3/4 ports, so it won't affect the origin working ports. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1959061/+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 1954692] Re: Reconsider compressed kernels on arm64
** Tags added: patch -- 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/1954692 Title: Reconsider compressed kernels on arm64 Status in maas-images: New Status in flash-kernel package in Ubuntu: In Progress Status in linux package in Ubuntu: Triaged Bug description: Compressed kernel images were introduced in bug 1384955 to work around some limits on old u-boot systems. This in turn broke grub-check- signatures, meaning that while cloud images booted in secure boot, you could not upgrade grub or install new kernels on secure systems as that would trigger a "you have unsigned kernels" message. grub 2.06 also fails to boot the images, as it verifies before decompressing. Work to fix grub to handle such images on arm64 for backward compatibility is tracked in bug 1954683. This bug is to reconsider whether the change is still necessary or could be removed in 22.04 such that we can have proper UEFI executables again. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/1954692/+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 1959216] Re: linux-azure: CONFIG_FB_EFI=y
** Also affects: linux-azure-4.15 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-azure-4.15 (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-azure-4.15 (Ubuntu Bionic) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure-4.15 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-azure-4.15 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-azure-4.15 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed ** Also affects: linux-azure-5.13 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-azure-5.13 (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-azure-5.13 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-azure-5.13 (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure-4.15 (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux-azure-5.13 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-azure-5.13 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-azure-5.13 (Ubuntu Jammy) Status: New => Invalid ** Also affects: linux-azure-5.11 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-azure-5.11 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-azure-5.11 (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-azure-5.11 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-azure-5.11 (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure-5.11 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-azure-5.11 (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-4.15 in Ubuntu. https://bugs.launchpad.net/bugs/1959216 Title: linux-azure: CONFIG_FB_EFI=y Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-azure-5.11 package in Ubuntu: Invalid Status in linux-azure-5.13 package in Ubuntu: Invalid Status in linux-azure source package in Bionic: In Progress Status in linux-azure-4.15 source package in Bionic: In Progress Status in linux-azure-5.11 source package in Bionic: Invalid Status in linux-azure-5.13 source package in Bionic: Invalid Status in linux-azure source package in Focal: In Progress Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-azure-5.11 source package in Focal: In Progress Status in linux-azure-5.13 source package in Focal: In Progress Status in linux-azure source package in Impish: In Progress Status in linux-azure-4.15 source package in Impish: Invalid Status in linux-azure-5.11 source package in Impish: Invalid Status in linux-azure-5.13 source package in Impish: Invalid Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure-4.15 source package in Jammy: Invalid Status in linux-azure-5.11 source package in Jammy: Invalid Status in linux-azure-5.13 source package in Jammy: Invalid Bug description: SRU Justification [Impact] Secure boot instances of linux-azure require an EFI framebuffer in some cases in order for the VM to boot. [Test Case] Microsoft tested. This config is also enabled on the master branch. [Where things could go wrong] VMs on certain instance types could fail to boot. [Other Info] SF: #00327005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1959216/+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 1954676] Re: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x
Yes, the commit has cc:stable and fixes: tags, so it should be picked up for v4.19 and later. -- 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/1954676 Title: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x Status in Ubuntu on IBM z Systems: Confirmed Status in gcc-11 package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: New Status in gcc-11 source package in Jammy: Fix Released Status in zfs-linux source package in Jammy: New Bug description: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. This seems to happen only when zfs is compile with gcc >= 11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show the problem and zfs is working just fine. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Temporary workaround is to build zfs with gcc-10 on s390x. [Regression potential] Building a kernel module with a different compiler is never 100% safe, we may experience potential crashes / panics if the ABI is not compatible. Moreover, if we build zfs with gcc-10 we are going to lose some of the performance benefits provided by gcc-11. However these regressions are limited to zfs on s390x and without this change zfs is broken anyway on this architecture. [Further analysis] @IBM Issue report to zfs upstream at https://github.com/openzfs/zfs/issues/12942 Reverting https://gcc.gnu.org/git/?p=gcc.git;a=patch;h=2335aa8771acd06b082d3e15d9f21ae0a802afd7 appears to make everything work, the compiled kernel and zfs.ko are loadable/unloadable once again. Please bring this issue to the attention of Ilya Leoshkevich Potentially this means we may have missbuilt userspace binaries in the archive for s390x. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1954676/+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 1954692] Re: Reconsider compressed kernels on arm64
@juliank my assumption is that nothing prevents it, other than someone writing that code. Attached is a patch for flash-kernel that will handle the compression, if needed, of kernel images for the m400. One alternate solution might be to try and copy the firmware-provided device tree data into a different memory location before loading the kernel in the boot.scr script. On one hand, that would limit the changes to code that only runs on these devices. But on the other hand, the generated uImage/uInitrd files wouldn't be usable for netbooting, as I don't think there's a way to inject memory copy commands into a config file for u-boot's pxelinux emulation. Note that we'll need to update the MAAS image generation code as well to keep that working. ** Patch added: "0001-Introduce-Boot-Kernel-Max-Size-and-support-for-compr.patch" https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1954692/+attachment/5557834/+files/0001-Introduce-Boot-Kernel-Max-Size-and-support-for-compr.patch ** Also affects: maas-images Importance: Undecided Status: New ** Changed in: flash-kernel (Ubuntu) Status: New => In Progress ** Changed in: flash-kernel (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) -- 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/1954692 Title: Reconsider compressed kernels on arm64 Status in maas-images: New Status in flash-kernel package in Ubuntu: In Progress Status in linux package in Ubuntu: Triaged Bug description: Compressed kernel images were introduced in bug 1384955 to work around some limits on old u-boot systems. This in turn broke grub-check- signatures, meaning that while cloud images booted in secure boot, you could not upgrade grub or install new kernels on secure systems as that would trigger a "you have unsigned kernels" message. grub 2.06 also fails to boot the images, as it verifies before decompressing. Work to fix grub to handle such images on arm64 for backward compatibility is tracked in bug 1954683. This bug is to reconsider whether the change is still necessary or could be removed in 22.04 such that we can have proper UEFI executables again. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/1954692/+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 1959216] Re: linux-azure: CONFIG_FB_EFI=y
https://lists.ubuntu.com/archives/kernel-team/2022-January/127528.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1959216 Title: linux-azure: CONFIG_FB_EFI=y Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-azure-5.13 package in Ubuntu: Invalid Status in linux-azure source package in Bionic: In Progress Status in linux-azure-4.15 source package in Bionic: In Progress Status in linux-azure-5.13 source package in Bionic: Invalid Status in linux-azure source package in Focal: In Progress Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-azure-5.13 source package in Focal: In Progress Status in linux-azure source package in Impish: In Progress Status in linux-azure-4.15 source package in Impish: Invalid Status in linux-azure-5.13 source package in Impish: Invalid Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure-4.15 source package in Jammy: Invalid Status in linux-azure-5.13 source package in Jammy: Invalid Bug description: SRU Justification [Impact] Secure boot instances of linux-azure require an EFI framebuffer in some cases in order for the VM to boot. [Test Case] Microsoft tested. This config is also enabled on the master branch. [Where things could go wrong] VMs on certain instance types could fail to boot. [Other Info] SF: #00327005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1959216/+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 1938531] Re: support signed v4l2loopback dkms build
verified linux-oem-5.14 version 5.14.0-1021-oem from focal-proposed. v4l2loopback prebuilt and signed: filename: /lib/modules/5.14.0-1021-oem/kernel/v4l2loopback/v4l2loopback.ko license:GPL author: Vasily Levin, IOhannes m zmoelnig ,Stefan Diewald,Anton Novikovet al. description:V4L2 loopback video device srcversion: 594E0DE21110E9D51B89C6B depends:videodev retpoline: Y name: v4l2loopback vermagic: 5.14.0-1021-oem SMP mod_unload modversions sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:6C:35:3A:49:55:DE:E5:56:21:AF:39:94:1F:E9:02:C3:2E:29:81:39 sig_hashalgo: sha512 signature: B9:3B:A0:FD:54:81:5A:F6:76:B2:C0:52:FE:C4:B0:7D:3D:8F:D7:BC: ... ** 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/1938531 Title: support signed v4l2loopback dkms build Status in OEM Priority Project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [SRU Justification] [Impact] v4l2loopback is used as a critical role on Intel IPU6 camera platforms, which takes userspace middleware involvements to correctly configure hardware sensors. While all the legacy camera applications are not yet learned how to support libcamera, v4l2loopback and a v4l2-relayd step in as a video streaming proxy for backward compatibility. To preinstall v4l2loopback kernel module on secureboot systems, signed modules should be used. [Fix] All Ubuntu specific changes to enable signed v4l2loopback dkms builds. [Test Case] Install signed modules package and check `modinfo v4l2loopback`. [Where problems could occur] N/A. [Other Info] This adds current revision of v4l2loopback in the ubuntu archive. While some other fixes are also needed for v4l2loopback/focal, expects version bumps recently. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1938531/+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 1954692] Re: Reconsider compressed kernels on arm64
** Also affects: flash-kernel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954692 Title: Reconsider compressed kernels on arm64 Status in flash-kernel package in Ubuntu: New Status in linux package in Ubuntu: Triaged Bug description: Compressed kernel images were introduced in bug 1384955 to work around some limits on old u-boot systems. This in turn broke grub-check- signatures, meaning that while cloud images booted in secure boot, you could not upgrade grub or install new kernels on secure systems as that would trigger a "you have unsigned kernels" message. grub 2.06 also fails to boot the images, as it verifies before decompressing. Work to fix grub to handle such images on arm64 for backward compatibility is tracked in bug 1954683. This bug is to reconsider whether the change is still necessary or could be removed in 22.04 such that we can have proper UEFI executables again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1954692/+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 1959239] [NEW] Touchscreen only works on every second boot
Public bug reported: On first boot, the touchscreen works. After reboot it doesn't. Reboot again and it works. Reboot again and it doesn't work. And so on. I have discovered a workaround, which is to run "echo 1 > /sys/bus/pci/devices/\:00\:15.1/remove" before rebooting. With a script containing this command added to /usr/lib/systemd/system- shutdown/, the touchscreen works on every boot. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-27-generic 5.13.0-27.29 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: darrell1621 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 27 15:25:45 2022 HibernationDevice: resume=UUID=00f963ec-ecf7-4ac6-accc-c541e719329d InstallationDate: Installed on 2022-01-05 (22 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: GEO GeoFlex 340 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=ad5fd920-af96-4db8-8cb2-c91d9f0c8dc3 ro quiet splash resume=UUID=00f963ec-ecf7-4ac6-accc-c541e719329d vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-27-generic N/A linux-backports-modules-5.13.0-27-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/16/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: IN5DV05 dmi.board.asset.tag: Default string dmi.board.name: ZHL dmi.board.vendor: GeoFlex 340 dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: GeoFlex 340 dmi.chassis.version: Default string dmi.ec.firmware.release: 2.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrIN5DV05:bd03/16/2021:br1.5:efr2.13:svnGEO:pnGeoFlex340:pvrDefaultstring:rvnGeoFlex340:rnZHL:rvrDefaultstring:cvnGeoFlex340:ct31:cvrDefaultstring:skuGE132-UK-2: dmi.product.family: Flex dmi.product.name: GeoFlex 340 dmi.product.sku: GE132-UK-2 dmi.product.version: Default string dmi.sys.vendor: GEO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- 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/1959239 Title: Touchscreen only works on every second boot Status in linux package in Ubuntu: New Bug description: On first boot, the touchscreen works. After reboot it doesn't. Reboot again and it works. Reboot again and it doesn't work. And so on. I have discovered a workaround, which is to run "echo 1 > /sys/bus/pci/devices/\:00\:15.1/remove" before rebooting. With a script containing this command added to /usr/lib/systemd/system- shutdown/, the touchscreen works on every boot. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-27-generic 5.13.0-27.29 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: darrell1621 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 27 15:25:45 2022 HibernationDevice: resume=UUID=00f963ec-ecf7-4ac6-accc-c541e719329d InstallationDate: Installed on 2022-01-05 (22 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: GEO GeoFlex 340 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=ad5fd920-af96-4db8-8cb2-c91d9f0c8dc3 ro quiet splash resume=UUID=00f963ec-ecf7-4ac6-accc-c541e719329d vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-27-generic N/A linux-backports-modules-5.13.0-27-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/16/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: IN5DV05 dmi.board.asset.tag: Default string dmi.board.name: ZHL dmi.board.vendor: GeoFlex 340 dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: GeoFlex 340 dmi.chassis.version: Default string dmi.ec.firmware.release: 2.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrIN5DV05:bd03/16/2021:br1.5:efr2.13:svnGEO:pnGeoFlex340:pvrDefaultstring:rvnGeoFlex340:rnZHL:rvrDefaultstring:cvnGeoFlex340:ct31:cvrDefaultstring:skuGE132-UK-2: dmi.product.family: Flex dmi.product.name: GeoFlex 340 dmi.product.sku: GE132-UK-2 dmi.product.version: Default
[Kernel-packages] [Bug 1958412] Re: [amdgpu] Flickering/noise on screen started in kernel 5.13
Me too (like Mariusz), I can boot with "Ubuntu, with Linux 5.11.0-46-generic" but not correctly with 5.13.0.27. But - normaly, I work with a second screen, connected over HDMI. In this case, ubuntu 5.13.0.27 starts with a white noise screen on the machines screen, but normaly on the second screen. I can't explain this, but its always the same. My last question is, how it is going on? Is there a kernel-update? Is it possible, to update an base of 5.11.0-46? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958412 Title: [amdgpu] Flickering/noise on screen started in kernel 5.13 Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: After the kernel release 5.13.0-27-generic was installed today, the startup and shutdown processes finish with white noise screens. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Wed Jan 19 16:17:35 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164c] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:18b2] InstallationDate: Installed on 2022-01-19 (0 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP420UA_TM420UA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=c4ec4ae8-c14c-4c0b-9922-9142270cef97 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: TP420UA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP420UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.2 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrTP420UA.302:bd09/06/2021:br5.19:efr3.2:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP420UA_TM420UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP420UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: VivoBook Flip dmi.product.name: VivoBook_ASUSLaptop TP420UA_TM420UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958412/+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 1959033] Re: Bionic update: upstream stable patchset 2022-01-25
** 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/1959033 Title: Bionic update: upstream stable patchset 2022-01-25 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed 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: upstream stable patchset 2022-01-25 Ported from the following upstream stable releases: v4.14.260, v4.19.223 from git://git.kernel.org/ IB/qib: Use struct_size() helper IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields net: usb: lan78xx: add Allied Telesis AT29M2-AF can: kvaser_usb: get CAN clock frequency from device HID: holtek: fix mouse probing spi: change clk_disable_unprepare to clk_unprepare IB/qib: Fix memory leak in qib_user_sdma_queue_pkts() netfilter: fix regression in looped (broad|multi)cast's MAC handling qlcnic: potential dereference null pointer of rx_queue->page_ring net: accept UFOv6 packages in virtio_net_hdr_to_skb net: skip virtio_net_hdr_set_proto if protocol already set bonding: fix ad_actor_system option setting to default fjes: Check for error irq drivers: net: smc911x: Check for error irq sfc: falcon: Check null pointer of rx_queue->page_ring hwmon: (lm90) Fix usage of CONFIG2 register in detect function ALSA: jack: Check the return value of kstrdup() ALSA: drivers: opl3: Fix incorrect use of vp->state Input: atmel_mxt_ts - fix double free in mxt_read_info_block x86/pkey: Fix undefined behaviour with PKRU_WD_BIT pinctrl: stm32: consider the GPIO offset to expose all the GPIO lines ARM: 9169/1: entry: fix Thumb2 bug in iWMMXt exception handling f2fs: fix to do sanity check on last xattr entry in __f2fs_setxattr() usb: gadget: u_ether: fix race in setting MAC address in setup phase KVM: VMX: Fix stale docs for kvm-intel.emulate_invalid_guest_state hwmon: (lm90) Do not report 'busy' status bit as alarm ax25: NPD bug when detaching AX25 device hamradio: defer ax25 kfree after unregister_netdev hamradio: improve the incomplete fix to avoid NPD phonet/pep: refuse to enable an unbound pipe parisc: Correct completer in lws start UBUNTU: upstream stable to v4.14.260, v4.19.223 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959033/+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 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
** Description changed: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. + Workaround: + Unbind "usb" driver from the device manually before suspending. That can be done to work automatically by a special script in /lib/systemd/system-sleep. + ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: jarnos 1175 F pulseaudio - /dev/snd/controlC0: jarnos 1175 F pulseaudio - /dev/snd/controlC1: jarnos 1175 F pulseaudio - /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: jarnos 1175 F pulseaudio + /dev/snd/controlC0: jarnos 1175 F pulseaudio + /dev/snd/controlC1: jarnos 1175 F pulseaudio + /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: - lono wireless extensions. - - eno1 no wireless extensions. + lono wireless extensions. + + eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.3.0-24-generic N/A - linux-backports-modules-5.3.0-24-generic N/A - linux-firmware1.183.2 + linux-restricted-modules-5.3.0-24-generic N/A + linux-backports-modules-5.3.0-24-generic N/A + linux-firmware1.183.2 RfKill: - 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- 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/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected Status in linux package in Ubuntu: Confirmed Bug description: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. Workaround: Unbind "usb" driver from the device manually before suspending. That can be done to work automatically by a special script in /lib/systemd/system-sleep. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1175 F pulseaudio /dev/snd/controlC0: jarnos 1175 F pulseaudio /dev/snd/controlC1: jarnos 1175 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018
[Kernel-packages] [Bug 1957113] Re: Bionic update: upstream stable patchset 2022-01-11
** 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/1957113 Title: Bionic update: upstream stable patchset 2022-01-11 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed 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: upstream stable patchset 2022-01-11 Ported from the following upstream stable releases: v4.14.258, v4.19.221 from git://git.kernel.org/ HID: add hid_is_usb() function to make it simpler for USB detection HID: add USB_HID dependancy to hid-prodikeys HID: add USB_HID dependancy to hid-chicony HID: add USB_HID dependancy on some USB HID drivers HID: wacom: fix problems when device is not a valid USB device HID: check for valid USB device for many HID drivers can: sja1000: fix use after free in ems_pcmcia_add_card() nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done bpf: Fix the off-by-two error in range markings nfp: Fix memory leak in nfp_cpp_area_cache_add() seg6: fix the iif in the IPv6 socket control block IB/hfi1: Correct guard on eager buffer deallocation mm: bdi: initialize bdi_min_ratio when bdi is unregistered ALSA: ctl: Fix copy of updated id with element read/write ALSA: pcm: oss: Fix negative period/buffer sizes ALSA: pcm: oss: Limit the period size to 16MB ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*() tracefs: Have new files inherit the ownership of their parent can: pch_can: pch_can_rx_normal: fix use after free can: m_can: Disable and ignore ELO interrupt libata: add horkage for ASMedia 1092 wait: add wake_up_pollfree() binder: use wake_up_pollfree() signalfd: use wake_up_pollfree() tracefs: Set all files to the same group ownership as the mount option block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2) qede: validate non LSO skb length net: cdc_ncm: Allow for dwNtbOutMaxSize to be unset or zero net: altera: set a couple error code in probe() net: fec: only clear interrupt of handling queue in fec_enet_rx_queue() net, neigh: clear whole pneigh_entry at alloc time net/qla3xxx: fix an error code in ql_adapter_up() USB: gadget: detect too-big endpoint 0 requests USB: gadget: zero allocate endpoint 0 buffers usb: core: config: fix validation of wMaxPacketValue entries xhci: Remove CONFIG_USB_DEFAULT_PERSIST to prevent xHCI from runtime suspending usb: core: config: using bit mask instead of individual bits iio: trigger: Fix reference counting iio: trigger: stm32-timer: fix MODULE_ALIAS iio: stk3310: Don't return error code in interrupt handler iio: mma8452: Fix trigger reference couting iio: ltr501: Don't return error code in trigger handler iio: kxsd9: Don't return error code in trigger handler iio: itg3200: Call iio_trigger_notify_done() on error iio: dln2-adc: Fix lockdep complaint iio: dln2: Check return value of devm_iio_trigger_register() iio: adc: axp20x_adc: fix charging current reporting on AXP22x iio: accel: kxcjk-1013: Fix possible memory leak in probe and remove irqchip/armada-370-xp: Fix return value of armada_370_xp_msi_alloc() irqchip/armada-370-xp: Fix support for Multi-MSI interrupts irqchip/irq-gic-v3-its.c: Force synchronisation when issuing INVALL irqchip: nvic: Fix offset for Interrupt Priority Offsets bonding: make tx_rebalance_counter an atomic UBUNTU: upstream stable to v4.14.258, v4.19.221 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957113/+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 1957957] Re: Bionic update: upstream stable patchset 2022-01-14
** 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/1957957 Title: Bionic update: upstream stable patchset 2022-01-14 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed 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: upstream stable patchset 2022-01-14 Ported from the following upstream stable releases: v4.14.259, v4.19.222 from git://git.kernel.org/ nfc: fix segfault in nfc_genl_dump_devices_done drm/msm/dsi: set default num_data_lanes net/mlx4_en: Update reported link modes for 1/10G parisc/agp: Annotate parisc agp init functions with __init i2c: rk3x: Handle a spurious start completion interrupt flag net: netlink: af_netlink: Prevent empty skb by adding a check on len. tracing: Fix a kmemleak false positive in tracing_map bpf: fix panic due to oob in bpf_prog_test_run_skb hwmon: (dell-smm) Fix warning on /proc/i8k creation error mac80211: send ADDBA requests using the tid/queue of the aggregation session recordmcount.pl: look for jgnop instruction as well as bcrl on s390 dm btree remove: fix use after free in rebalance_children() audit: improve robustness of the audit queue handling nfsd: fix use-after-free due to delegation race x86: Make ARCH_USE_MEMREMAP_PROT a generic Kconfig symbol x86/sme: Explicitly map new EFI memmap table as encrypted ARM: socfpga: dts: fix qspi node compatible dmaengine: st_fdma: fix MODULE_ALIAS soc/tegra: fuse: Fix bitwise vs. logical OR warning igbvf: fix double free in `igbvf_probe` ixgbe: set X550 MDIO speed before talking to PHY net/packet: rx_owner_map depends on pg_vec sit: do not call ipip6_dev_free() from sit_init_net() USB: gadget: bRequestType is a bitfield, not a enum PCI/MSI: Clear PCI_MSIX_FLAGS_MASKALL on error PCI/MSI: Mask MSI-X vectors only on success USB: serial: option: add Telit FN990 compositions timekeeping: Really make sure wall_to_monotonic isn't positive libata: if T_LENGTH is zero, dma direction should be DMA_NONE net: systemport: Add global locking for descriptor lifecycle firmware: arm_scpi: Fix string overflow in SCPI genpd driver ARM: dts: imx6ull-pinfunc: Fix CSI_DATA07__ESAI_TX0 pad name fuse: annotate lock in fuse_reverse_inval_entry() scsi: scsi_debug: Sanity check block descriptor length in resp_mode_select() net: lan78xx: Avoid unnecessary self assignment ARM: 8805/2: remove unneeded naked function usage mwifiex: Remove unnecessary braces from HostCmd_SET_SEQ_NO_BSS_INFO ARM: 8800/1: use choice for kernel unwinders UBUNTU: [Config] updateconfigs for UNWINDER_ARM Input: touchscreen - avoid bitwise vs logical OR warning xen/blkfront: harden blkfront against event channel storms xen/netfront: harden netfront against event channel storms xen/console: harden hvc_xen against event channel storms xen/netback: fix rx queue stall detection xen/netback: don't queue unlimited number of packages mac80211: track only QoS data frames for admission control UBUNTU: upstream stable to v4.14.259, v4.19.222 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957957/+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 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
Still present in 5.13.0-27-generic. -- 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/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected Status in linux package in Ubuntu: Confirmed Bug description: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. Workaround: Unbind "usb" driver from the device manually before suspending. That can be done to work automatically by a special script in /lib/systemd/system-sleep. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1175 F pulseaudio /dev/snd/controlC0: jarnos 1175 F pulseaudio /dev/snd/controlC1: jarnos 1175 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+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 1956614] Re: Bionic update: upstream stable patchset 2022-01-06
Skipped as already applied for security: fs: add fget_many() and fput_many() fget: check that the fd still exists after getting a ref to it ** 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/1956614 Title: Bionic update: upstream stable patchset 2022-01-06 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed 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: upstream stable patchset 2022-01-06 Ported from the following upstream stable releases: v4.14.257, v4.19.219, v4.19.220 from git://git.kernel.org/ USB: serial: option: add Telit LE910S1 0x9200 composition USB: serial: option: add Fibocom FM101-GL variants usb: hub: Fix usb enumeration issue due to address0 race usb: hub: Fix locking issues with address0_mutex binder: fix test regression due to sender_euid change ALSA: ctxfi: Fix out-of-range access media: cec: copy sequence field for the reply HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect() fuse: fix page stealing xen: don't continue xenstore initialization in case of errors xen: detect uninitialized xenbus in xenbus_init tracing: Fix pid filtering when triggers are attached netfilter: ipvs: Fix reuse connection if RS weight is 0 ARM: dts: BCM5301X: Fix I2C controller interrupt ARM: dts: BCM5301X: Add interrupt properties to GPIO node ASoC: topology: Add missing rwsem around snd_ctl_remove() calls net: ieee802154: handle iftypes as u32 NFSv42: Don't fail clone() unless the OP_CLONE operation failed ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE scsi: mpt3sas: Fix kernel panic during drive powercycle test drm/vc4: fix error code in vc4_create_object() ipv6: fix typos in __ip6_finish_output() net/smc: Ensure the active closing peer first closes clcsock PM: hibernate: use correct mode for swsusp_close() tcp_cubic: fix spurious Hystart ACK train detections for not-cwnd-limited flows MIPS: use 3-level pgtable for 64KB page size on MIPS_VA_BITS_48 net/smc: Don't call clcsock shutdown twice when smc shutdown vhost/vsock: fix incorrect used length reported to the guest tracing: Check pid filtering when creating events s390/mm: validate VMA in PGSTE manipulation functions PCI: aardvark: Fix a leaked reference by adding missing of_node_put() PCI: aardvark: Wait for endpoint to be ready before training link PCI: aardvark: Train link immediately after enabling training PCI: aardvark: Improve link training PCI: aardvark: Issue PERST via GPIO PCI: aardvark: Replace custom macros by standard linux/pci_regs.h macros PCI: aardvark: Indicate error in 'val' when config read fails PCI: aardvark: Introduce an advk_pcie_valid_device() helper PCI: aardvark: Don't touch PCIe registers if no card connected PCI: aardvark: Fix compilation on s390 PCI: aardvark: Move PCIe reset card code to advk_pcie_train_link() PCI: aardvark: Update comment about disabling link training PCI: aardvark: Remove PCIe outbound window configuration PCI: aardvark: Configure PCIe resources from 'ranges' DT property PCI: aardvark: Fix PCIe Max Payload Size setting PCI: Add PCI_EXP_LNKCTL2_TLS* macros PCI: aardvark: Fix link training PCI: aardvark: Fix checking for link up via LTSSM state pinctrl: armada-37xx: Correct mpp definitions pinctrl: armada-37xx: add missing pin: PCIe1 Wakeup pinctrl: armada-37xx: Correct PWM pins definitions arm64: dts: marvell: armada-37xx: declare PCIe reset pin arm64: dts: marvell: armada-37xx: Set pcie_reset_pin to gpio function proc/vmcore: fix clearing user buffer by properly using clear_user() NFC: add NCI_UNREG flag to eliminate the race fuse: release pipe buf after last use xen: sync include/xen/interface/io/ring.h with Xen's newest version xen/blkfront: read response from backend only once xen/blkfront: don't take local copy of a request from the ring page xen/blkfront: don't trust the backend response data blindly xen/netfront: read response from backend only once xen/netfront: don't read data from request on the ring page xen/netfront: disentangle tx_skb_freelist xen/netfront: don't trust the backend response data blindly tty: hvc: replace BUG_ON() with negative return
[Kernel-packages] [Bug 1959216] [NEW] linux-azure: CONFIG_FB_EFI=y
Public bug reported: SRU Justification [Impact] Secure boot instances of linux-azure require an EFI framebuffer in some cases in order for the VM to boot. [Test Case] Microsoft tested. This config is also enabled on the master branch. [Where things could go wrong] VMs on certain instance types could fail to boot. [Other Info] SF: #00327005 ** Affects: linux-azure (Ubuntu) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Bionic) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Focal) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Impish) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Jammy) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Tags: bot-stop-nagging ** Tags added: bot-stop-nagging ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Impish) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Bionic) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Impish) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1959216 Title: linux-azure: CONFIG_FB_EFI=y Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Bionic: In Progress Status in linux-azure source package in Focal: In Progress Status in linux-azure source package in Impish: In Progress Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification [Impact] Secure boot instances of linux-azure require an EFI framebuffer in some cases in order for the VM to boot. [Test Case] Microsoft tested. This config is also enabled on the master branch. [Where things could go wrong] VMs on certain instance types could fail to boot. [Other Info] SF: #00327005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1959216/+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 1957007] Re: Focal update: v5.4.165 upstream stable release
** Changed in: linux (Ubuntu Focal)
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/1957007
Title:
Focal update: v5.4.165 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Committed
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.165 upstream stable release
from git://git.kernel.org/
serial: tegra: Change lower tolerance baud rate limit for tegra20 and tegra30
ntfs: fix ntfs_test_inode and ntfs_init_locked_inode function type
HID: quirks: Add quirk for the Microsoft Surface 3 type-cover
HID: google: add eel USB id
HID: add hid_is_usb() function to make it simpler for USB detection
HID: add USB_HID dependancy to hid-prodikeys
HID: add USB_HID dependancy to hid-chicony
HID: add USB_HID dependancy on some USB HID drivers
HID: bigbenff: prevent null pointer dereference
HID: wacom: fix problems when device is not a valid USB device
HID: check for valid USB device for many HID drivers
can: kvaser_usb: get CAN clock frequency from device
can: kvaser_pciefd: kvaser_pciefd_rx_error_frame(): increase correct
stats->{rx,tx}_errors counter
can: sja1000: fix use after free in ems_pcmcia_add_card()
nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
selftests: netfilter: add a vrf+conntrack testcase
vrf: don't run conntrack on vrf with !dflt qdisc
bpf: Fix the off-by-two error in range markings
ice: ignore dropped packets during init
bonding: make tx_rebalance_counter an atomic
nfp: Fix memory leak in nfp_cpp_area_cache_add()
seg6: fix the iif in the IPv6 socket control block
udp: using datalen to cap max gso segments
iavf: restore MSI state on reset
iavf: Fix reporting when setting descriptor count
IB/hfi1: Correct guard on eager buffer deallocation
mm: bdi: initialize bdi_min_ratio when bdi is unregistered
ALSA: ctl: Fix copy of updated id with element read/write
ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
ALSA: pcm: oss: Fix negative period/buffer sizes
ALSA: pcm: oss: Limit the period size to 16MB
ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*()
btrfs: clear extent buffer uptodate when we fail to write it
btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
nfsd: Fix nsfd startup race (again)
tracefs: Have new files inherit the ownership of their parent
clk: qcom: regmap-mux: fix parent clock lookup
drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.
can: pch_can: pch_can_rx_normal: fix use after free
can: m_can: Disable and ignore ELO interrupt
x86/sme: Explicitly map new EFI memmap table as encrypted
libata: add horkage for ASMedia 1092
wait: add wake_up_pollfree()
UBUNTU: SAUCE: binder: export __wake_up_pollfree for binder module
binder: use wake_up_pollfree()
signalfd: use wake_up_pollfree()
aio: keep poll requests on waitqueue until completed
aio: fix use-after-free due to missing POLLFREE handling
tracefs: Set all files to the same group ownership as the mount option
block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2)
qede: validate non LSO skb length
ASoC: qdsp6: q6routing: Fix return value from msm_routing_put_audio_mixer
i40e: Fix failed opcode appearing if handling messages from VF
i40e: Fix pre-set max number of queues for VF
mtd: rawnand: fsmc: Take instruction delay into account
mtd: rawnand: fsmc: Fix timing computation
dt-bindings: net: Reintroduce PHY no lane swap binding
tools build: Remove needless libpython-version feature check that breaks
test-all fast path
net: cdc_ncm: Allow for dwNtbOutMaxSize to be unset or zero
net: altera: set a couple error code in probe()
net: fec: only clear interrupt of handling queue in fec_enet_rx_queue()
net, neigh: clear whole pneigh_entry at alloc time
net/qla3xxx: fix an error code in ql_adapter_up()
Revert "UBUNTU: SAUCE: selftests: fib_tests: assign address to dummy1 for
rp_filter tests"
selftests/fib_tests: Rework fib_rp_filter_test()
USB: gadget: detect too-big endpoint 0 requests
USB: gadget: zero allocate endpoint 0 buffers
usb: core: config: fix validation of wMaxPacketValue entries
xhci: Remove CONFIG_USB_DEFAULT_PERSIST to prevent xHCI from runtime
suspending
usb: core: config: using bit mask instead of individual bits
xhci: avoid race between
[Kernel-packages] [Bug 1957008] Re: Focal update: v5.4.166 upstream stable release
Additional patches pulled into this update: 6dedcff6738b net/packet: rx_owner_map depends on pg_vec 4ce2761acc86 USB: gadget: bRequestType is a bitfield, not a enum b20f9579cfb1 HID: holtek: fix mouse probing 712c922bd079 udp: using datalen to cap ipv6 udp max gso segments bd7bd9edb090 selftests: Calculate udpgso segment count without header adjustment ** Changed in: linux (Ubuntu Focal) 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/1957008 Title: Focal update: v5.4.166 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed 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.166 upstream stable release from git://git.kernel.org/ netfilter: selftest: conntrack_vrf.sh: fix file permission Linux 5.4.166 UBUNTU: upstream stable to v5.4.166 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957008/+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 1959215] Re: unshare test in ubuntu_stress_smoke_tests triggers "BUG: unable to handle page fault for address: 0000000000001cc8" on Impish with node vought
Here is the test log: ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Description changed: Issue found on Intel node "vought" with: - * 5.13.0-28.31 - * 5.13.0-27 - * And possibly the 5.13.0-23 from the last cycle (this test didn't finish properly back then). For more earlier Impish kernels, this system was not tested with this test on them. + * 5.13.0-28.31 + * 5.13.0-27 + * And possibly the 5.13.0-23 from the last cycle (this test didn't finish properly and marked as "Incomplete" back then, just like this cycle). For more earlier Impish kernels, this system was not tested with this test on them. The test will hang with unshare test in ubuntu_stress_smoke_tests: 12:39:39 DEBUG| [stdout] udp RETURNED 0 12:39:39 DEBUG| [stdout] udp PASSED 12:39:39 DEBUG| [stdout] udp-flood STARTING 12:39:41 DEBUG| [stdout] udp-flood RETURNED 0 12:39:41 DEBUG| [stdout] udp-flood PASSED 12:39:41 DEBUG| [stdout] unshare STARTING (hangs here) And stop responding. Error can be found in dmesg: [ 2371.109961] BUG: unable to handle page fault for address: 1cc8 [ 2371.110074] #PF: supervisor read access in kernel mode [ 2371.114323] #PF: error_code(0x) - not-present page - [ 2371.119931] PGD 0 P4D 0 + [ 2371.119931] PGD 0 P4D 0 [ 2371.125257] Oops: [#1] SMP NOPTI [ 2371.129247] CPU: 51 PID: 207256 Comm: stress-ng Tainted: P O 5.13.0-27-generic #29-Ubuntu [ 2371.133203] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS SE5C620.86B.0D.01.0395.022720191340 02/27/2019 [ 2371.135887] RIP: 0010:__next_zones_zonelist+0x6/0x50 [ 2371.138525] Code: d0 0f 4e d0 3d ff 03 00 00 7f 0d 48 63 d2 5d 48 8b 04 d5 60 e5 35 af c3 31 c0 5d c3 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 <8b> 4f 08 48 89 f8 48 89 e5 48 85 d2 75 10 eb 1d 48 63 49 50 48 0f [ 2371.143813] RSP: 0018:a9c8b399fac0 EFLAGS: 00010282 [ 2371.146078] RAX: RBX: RCX: [ 2371.148293] RDX: 9c98e894ea98 RSI: 0002 RDI: 1cc0 [ 2371.150477] RBP: a9c8b399fb28 R08: R09: [ 2371.152650] R10: 0002 R11: d9bfbfcc5600 R12: 00052cc0 [ 2371.154778] R13: 0002 R14: 0001 R15: 00152cc0 [ 2371.156876] FS: 7fcbd141d740() GS:9cc14ccc() knlGS: [ 2371.158936] CS: 0010 DS: ES: CR0: 80050033 [ 2371.160958] CR2: 1cc8 CR3: 00059f292001 CR4: 007706e0 [ 2371.162950] DR0: DR1: DR2: [ 2371.164888] DR3: DR6: fffe0ff0 DR7: 0400 [ 2371.166811] PKRU: 5554 [ 2371.168694] Call Trace: [ 2371.170544] ? __alloc_pages+0x2f1/0x330 [ 2371.172386] kmalloc_large_node+0x45/0xb0 [ 2371.174222] __kmalloc_node+0x276/0x300 [ 2371.176036] ? queue_delayed_work_on+0x39/0x60 [ 2371.177853] kvmalloc_node+0x5a/0x90 [ 2371.179622] expand_one_shrinker_info+0x82/0x190 [ 2371.181382] prealloc_shrinker+0x175/0x1d0 [ 2371.183091] alloc_super+0x2bf/0x330 [ 2371.184764] ? __fput_sync+0x30/0x30 [ 2371.186384] sget_fc+0x74/0x2e0 [ 2371.187951] ? set_anon_super+0x50/0x50 [ 2371.189473] ? mqueue_create+0x20/0x20 [ 2371.190944] get_tree_keyed+0x34/0xd0 [ 2371.192363] mqueue_get_tree+0x1c/0x20 [ 2371.193734] vfs_get_tree+0x2a/0xc0 [ 2371.195105] fc_mount+0x13/0x50 [ 2371.196409] mq_init_ns+0x10a/0x1b0 [ 2371.197667] copy_ipcs+0x130/0x220 [ 2371.198899] create_new_namespaces+0xa6/0x2e0 [ 2371.200113] unshare_nsproxy_namespaces+0x5a/0xb0 [ 2371.201303] ksys_unshare+0x1db/0x3c0 [ 2371.202480] __x64_sys_unshare+0x12/0x20 [ 2371.203649] do_syscall_64+0x61/0xb0 [ 2371.204804] ? exit_to_user_mode_loop+0xec/0x160 [ 2371.205966] ? exit_to_user_mode_prepare+0x37/0xb0 [ 2371.207102] ? syscall_exit_to_user_mode+0x27/0x50 [ 2371.208222] ? __x64_sys_close+0x11/0x40 [ 2371.209336] ? do_syscall_64+0x6e/0xb0 [ 2371.210438] ? asm_exc_page_fault+0x8/0x30 [ 2371.211545] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 2371.212641] RIP: 0033:0x7fcbd1562c4b [ 2371.213698] Code: 73 01 c3 48 8b 0d e5 e1 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 10 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 e1 0e 00 f7 d8 64 89 01 48 [ 2371.215851] RSP: 002b:7ffc5d8eb878 EFLAGS: 0246 ORIG_RAX: 0110 [ 2371.216846] RAX: ffda RBX: 7ffc5d8eba20 RCX: 7fcbd1562c4b [ 2371.217830] RDX: 560296049862 RSI: 0800 RDI: 0800 [ 2371.218886] RBP: 7ffc5d8eb8d0 R08: 5602960234a2 R09: 7fcbd141d740 [ 2371.219908] R10: R11: 0246 R12:
[Kernel-packages] [Bug 1953334] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part
This bug was fixed in the package linux - 5.15.0-18.18
---
linux (5.15.0-18.18) jammy; urgency=medium
* jammy/linux: 5.15.0-18.18 -proposed tracker (LP: #1958638)
* CVE-2021-4155
- xfs: map unwritten blocks in XFS_IOC_{ALLOC, FREE}SP just like fallocate
* CVE-2022-0185
- SAUCE: vfs: test that one given mount param is not larger than PAGE_SIZE
* [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel -
kernel part (LP: #1953334)
- KVM: s390: add debug statement for diag 318 CPNC data
* OOB write on BPF_RINGBUF (LP: #1956585)
- SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other
than 0
* Miscellaneous Ubuntu changes
- [Config] re-enable shiftfs
- [SAUCE] shiftfs: support kernel 5.15
- [Config] update toolchain versions
* Miscellaneous upstream changes
- vfs: fs_context: fix up param length parsing in legacy_parse_param
-- Andrea Righi Fri, 21 Jan 2022 13:32:27
+0100
** Changed in: linux (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-4155
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0185
--
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/1953334
Title:
[UBUNTU 20.04] KVM hardware diagnose data improvements for guest
kernel - kernel part
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* Hardware diagnose data (diag 318) of KVM guest kernel cannot be
handled.
* A fix is needed to enhance problem determination of guest kernel
under KVM using DIAG 0x318 instruction execution.
* The s390x diagnose 318 instruction sets the control program name
code (CPNC) and control program version code (CPVC) to provide useful
information regarding the OS during debugging.
* The CPNC is explicitly set to 4 to indicate a Linux/KVM environment.
[Fix]
* In general the following 4 commits are needed:
* 3fd8417f2c728d810a3b26d7e2008012ffb7fd01 3fd8417f2c72 "KVM: s390: add debug
statement for diag 318 CPNC data"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545726/+files/0004-KVM-s390-add-debug-statement-for-diag-318-CPNC-data.patch
* 6cbf1e960fa52e4c63a6dfa4cda8736375b34ccc 6cbf1e960fa5 "KVM: s390: remove
diag318 reset code"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545725/+files/0003-KVM-s390-remove-diag318-reset-code.patch
* 23a60f834406c8e3805328b630d09d5546b460c1 23a60f834406 "s390/kvm: diagnose
0x318 sync and reset"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545724/+files/0002-s390-kvm-diagnose-0x318-sync-and-reset.patch
* a23816f3cdcbffe5dc6e8c331914b3f51b87c2f3 a23816f3cdcb "s390/setup: diag
318: refactor struct"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545723/+files/0001-s390-setup-diag-318-refactor-struct.patch
* For jammy, hirsute and impish only the first commit is needed, the
others are already in.
* For focal all 4 commits are needed, but since they do not apply
cleanly on focal, the attached backports need to be used instead.
[Test Case]
* Setup an IBM Z or LinuxONE LPAR with Ubuntu Server as KVM host.
* And setup an Ubuntu KVM virtual machine on top.
* It can then be observed if the CPNC (diag318 data) has been
successfully set by looking at the s390dbf messages for the KVM guest.
* The CPNC will always be 4 (denotes Linux environment).
* Another way to test this is by running the sync_regs_test under
tools/testing/selftests/kvm/s390x/sync_regs_test. Just running the
kernel self test suite can trigger this.
[Where problems could occur]
* The approach here is to provide additional debug and diagnose
information on top.
* Hence even if the diag318 changes are broken, the existing
functionality shouldn't be harmed.
* The changes themselves are relatively discernible and mostly
introduce new structures.
* However, with the functional changes broken code could be introduced
(e.g. due to erroneous pointer arithmetic for example) that does not
compile or causes crashes. But this is what the test builds are for
(https://launchpad.net/~fheimes/+archive/ubuntu/lp1953334).
* On top the diag318 diagnose data might not properly provided - maybe
empty or wrong. Again that is what the test builds and the
verification later is targeted at.
* Since diag318 is s390x specific, all the modifications touch
[Kernel-packages] [Bug 1956381] Re: Focal update: v5.4.164 upstream stable release
Skipped "fget: check that the fd still exists after getting a ref to it" since it was already applied for security. ** Changed in: linux (Ubuntu Focal) 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/1956381 Title: Focal update: v5.4.164 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed 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.164 upstream stable release from git://git.kernel.org/ NFSv42: Fix pagecache invalidation after COPY/CLONE of: clk: Make self-contained arm64: dts: mcbin: support 2W SFP modules can: j1939: j1939_tp_cmd_recv(): check the dst address of TP.CM_BAM gfs2: Fix length of holes reported at end-of-file drm/sun4i: fix unmet dependency on RESET_CONTROLLER for PHY_SUN6I_MIPI_DPHY mac80211: do not access the IV when it was stripped net/smc: Transfer remaining wait queue entries during fallback atlantic: Fix OOB read and write in hw_atl_utils_fw_rpc_wait net: return correct error code platform/x86: thinkpad_acpi: Fix WWAN device disabled issue after S3 deep s390/setup: avoid using memblock_enforce_memory_limit btrfs: check-integrity: fix a warning on write caching disabled disk thermal: core: Reset previous low and high trip during thermal zone init scsi: iscsi: Unblock session then wake up error handler ata: ahci: Add Green Sardine vendor ID as board_ahci_mobile ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port() net: tulip: de4x5: fix the problem that the array 'lp->phy[8]' may be out of bound net: ethernet: dec: tulip: de4x5: fix possible array overflows in type3_infoblock() perf hist: Fix memory leak of a perf_hpp_fmt perf report: Fix memory leaks around perf_tip() net/smc: Avoid warning of possible recursive locking vrf: Reset IPCB/IP6CB when processing outbound pkts in vrf dev xmit kprobes: Limit max data_size of the kretprobe instances rt2x00: do not mark device gone on EPROTO errors during start cpufreq: Fix get_cpu_device() failure in add_cpu_dev_symlink() s390/pci: move pseudo-MMIO to prevent MIO overlap fget: check that the fd still exists after getting a ref to it sata_fsl: fix UAF in sata_fsl_port_stop when rmmod sata_fsl sata_fsl: fix warning in remove_proc_entry when rmmod sata_fsl i2c: stm32f7: flush TX FIFO upon transfer errors i2c: stm32f7: recover the bus on access timeout i2c: stm32f7: stop dma transfer in case of NACK i2c: cbus-gpio: set atomic transfer callback natsemi: xtensa: fix section mismatch warnings net: qlogic: qlcnic: Fix a NULL pointer dereference in qlcnic_83xx_add_rings() net: mpls: Fix notifications when deleting a device siphash: use _unaligned version by default net/mlx4_en: Fix an use-after-free bug in mlx4_en_try_alloc_resources() selftests: net: Correct case name rxrpc: Fix rxrpc_local leak in rxrpc_lookup_peer() net: usb: lan78xx: lan78xx_phy_init(): use PHY_POLL instead of "0" if no IRQ is available net: marvell: mvpp2: Fix the computation of shared CPUs net: annotate data-races on txq->xmit_lock_owner ipv4: convert fib_num_tclassid_users to atomic_t net/rds: correct socket tunable error in rds_tcp_tune() net/smc: Keep smc_close_final rc during active close drm/msm: Do hw_init() before capturing GPU state ipv6: fix memory leak in fib6_rule_suppress KVM: x86/pmu: Fix reserved bits for AMD PerfEvtSeln register sched/uclamp: Fix rq->uclamp_max not set on first enqueue parisc: Fix KBUILD_IMAGE for self-extracting kernel parisc: Fix "make install" on newer debian releases vgacon: Propagate console boot parameters before calling `vc_resize' xhci: Fix commad ring abort, write all 64 bits to CRCR register. USB: NO_LPM quirk Lenovo Powered USB-C Travel Hub usb: typec: tcpm: Wait in SNK_DEBOUNCED until disconnect x86/tsc: Add a timer to make sure TSC_adjust is always checked x86/tsc: Disable clocksource watchdog for TSC on qualified platorms x86/64/mm: Map all kernel memory into trampoline_pgd tty: serial: msm_serial: Deactivate RX DMA for polling support serial: pl011: Add ACPI SBSA UART match id serial: core: fix transmit-buffer reset and memleak serial: 8250_pci: Fix ACCES entries in pci_serial_quirks array serial: 8250_pci: rewrite pericom_do_set_divisor() iwlwifi: mvm: retry init flow if
[Kernel-packages] [Bug 1956380] Re: Focal update: v5.4.163 upstream stable release
** Changed in: linux (Ubuntu Focal) 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/1956380 Title: Focal update: v5.4.163 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed 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.163 upstream stable release from git://git.kernel.org/ USB: serial: option: add Telit LE910S1 0x9200 composition USB: serial: option: add Fibocom FM101-GL variants usb: dwc2: gadget: Fix ISOC flow for elapsed frames usb: dwc2: hcd_queue: Fix use of floating point literal net: nexthop: fix null pointer dereference when IPv6 is not enabled usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts usb: hub: Fix usb enumeration issue due to address0 race usb: hub: Fix locking issues with address0_mutex binder: fix test regression due to sender_euid change ALSA: ctxfi: Fix out-of-range access media: cec: copy sequence field for the reply HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts staging/fbtft: Fix backlight staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect() xen: don't continue xenstore initialization in case of errors xen: detect uninitialized xenbus in xenbus_init KVM: PPC: Book3S HV: Prevent POWER7/8 TLB flush flushing SLB tracing/uprobe: Fix uprobe_perf_open probes iteration tracing: Fix pid filtering when triggers are attached mmc: sdhci: Fix ADMA for PAGE_SIZE >= 64KiB mdio: aspeed: Fix "Link is Down" issue PCI: aardvark: Deduplicate code in advk_pcie_rd_conf() PCI: aardvark: Wait for endpoint to be ready before training link PCI: aardvark: Fix big endian support PCI: aardvark: Train link immediately after enabling training PCI: aardvark: Improve link training PCI: aardvark: Issue PERST via GPIO PCI: aardvark: Replace custom macros by standard linux/pci_regs.h macros PCI: aardvark: Don't touch PCIe registers if no card connected PCI: aardvark: Fix compilation on s390 PCI: aardvark: Move PCIe reset card code to advk_pcie_train_link() PCI: aardvark: Update comment about disabling link training PCI: pci-bridge-emul: Fix array overruns, improve safety PCI: aardvark: Configure PCIe resources from 'ranges' DT property PCI: aardvark: Fix PCIe Max Payload Size setting PCI: aardvark: Implement re-issuing config requests on CRS response PCI: aardvark: Simplify initialization of rootcap on virtual bridge PCI: aardvark: Fix link training PCI: aardvark: Fix support for bus mastering and PCI_COMMAND on emulated bridge PCI: aardvark: Set PCI Bridge Class Code to PCI Bridge PCI: aardvark: Fix support for PCI_BRIDGE_CTL_BUS_RESET on emulated bridge pinctrl: armada-37xx: Correct PWM pins definitions arm64: dts: marvell: armada-37xx: Set pcie_reset_pin to gpio function proc/vmcore: fix clearing user buffer by properly using clear_user() netfilter: ipvs: Fix reuse connection if RS weight is 0 ARM: dts: BCM5301X: Fix I2C controller interrupt ARM: dts: BCM5301X: Add interrupt properties to GPIO node ASoC: qdsp6: q6routing: Conditionally reset FrontEnd Mixer ASoC: topology: Add missing rwsem around snd_ctl_remove() calls net: ieee802154: handle iftypes as u32 firmware: arm_scmi: pm: Propagate return value to caller NFSv42: Don't fail clone() unless the OP_CLONE operation failed ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE scsi: mpt3sas: Fix kernel panic during drive powercycle test drm/vc4: fix error code in vc4_create_object() iavf: Prevent changing static ITR values if adaptive moderation is on ipv6: fix typos in __ip6_finish_output() nfp: checking parameter process for rx-usecs/tx-usecs is invalid net: ipv6: add fib6_nh_release_dsts stub net: nexthop: release IPv6 per-cpu dsts when replacing a nexthop group scsi: core: sysfs: Fix setting device state to SDEV_RUNNING net/smc: Ensure the active closing peer first closes clcsock nvmet-tcp: fix incomplete data digest send net/ncsi : Add payload to be 32-bit aligned to fix dropped packets PM: hibernate: use correct mode for swsusp_close() tcp_cubic: fix spurious Hystart ACK train detections for not-cwnd-limited flows nvmet: use IOCB_NOWAIT only if the filesystem supports it igb: fix netpoll exit with traffic MIPS: use 3-level pgtable for 64KB page size on MIPS_VA_BITS_48 net: vlan: fix
[Kernel-packages] [Bug 1956849] Re: Almost all USB ports suddenly stopped working; unbootable
This problem seems to occur very randomly for me on 20.04 with the 5.13 HWE kernel (5.13.0-27-generic). Here's the relevant dmesg from after the problem occurs: [1.751416] wacom 0003:056A:00EC.0002: hidraw0: USB HID v1.10 Mouse [Tablet ISD-V4] on usb-:00:1d.0-1.8/input0 [6.738809] usb 3-3: device descriptor read/8, error -110 [6.846682] usb 3-3: new SuperSpeed USB device number 2 using xhci_hcd [ 12.114819] usb 3-3: device descriptor read/8, error -110 [ 12.358687] usb 2-4: new full-speed USB device number 3 using xhci_hcd [ 12.508071] usb 2-4: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01 [ 12.508086] usb 2-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 12.598690] usb 2-3.2: new high-speed USB device number 4 using xhci_hcd [ 12.711168] usb 2-3.2: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.00 [ 12.711184] usb 2-3.2: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 12.711190] usb 2-3.2: Product: USB 2.0 Hub [MTT] [ 12.712162] hub 2-3.2:1.0: USB hub found [ 12.712243] hub 2-3.2:1.0: 4 ports detected [ 23.002688] xhci_hcd :00:14.0: Abort failed to stop command ring: -110 [ 23.002707] xhci_hcd :00:14.0: xHCI host controller not responding, assume dead [ 23.002744] xhci_hcd :00:14.0: HC died; cleaning up [ 23.002767] clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large: [ 23.002771] clocksource: 'acpi_pm' wd_now: af831a wd_last: a565c0 mask: ff [ 23.002775] clocksource: 'tsc' cs_now: 10bdde5e61 cs_last: e237c090a mask: [ 23.002778] tsc: Marking TSC unstable due to clocksource watchdog [ 23.002791] xhci_hcd :00:14.0: Timeout while waiting for setup device command [ 23.002798] xhci_hcd :00:14.0: Error while assigning device slot ID [ 23.002801] xhci_hcd :00:14.0: Max number of devices this xHCI host supports is 32. [ 23.002805] usb 2-3.2-port1: couldn't allocate usb_device [ 23.003022] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. [ 23.003024] sched_clock: Marking unstable (23002093033, 928871)<-(23061485899, -58464196) [ 23.003286] clocksource: Checking clocksource tsc synchronization from CPU 2. [ 23.003348] clocksource: Switched to clocksource acpi_pm [ 23.418688] usb 3-3: device not accepting address 3, error -108 [ 23.418792] usb usb3-port3: attempt power cycle [ 23.418799] usb usb3-port3: failed to disable port power [ 23.418804] usb usb3-port3: couldn't allocate usb_device [ 23.418855] usb usb2-port5: couldn't allocate usb_device [ 23.418902] usb 2-3: USB disconnect, device number 2 [ 23.418909] usb 2-3.2: USB disconnect, device number 4 [ 23.419931] usb 2-4: USB disconnect, device number 3 -- 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/1956849 Title: Almost all USB ports suddenly stopped working; unbootable Status in linux package in Ubuntu: Incomplete Bug description: This package needs to be pulled NOW. It disables almost all USB-3.0 and USB-C ports completely. Even though I had automatic software updates turned OFF (or so I thought), my Mac Pro suddenly got a new kernel when I rebooted it this morning: Linux macpro-obs 5.11.0-44-generic #48~20.04.2-Ubuntu SMP Tue Dec 14 15:36:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux and it contains a P0 showstopper bug. Upon rebooting, I got dropped into the initrd prompt because Linux could not see the external USB drive that I'm booting from (WDBAGF5000AGY-WESN). I wasted an entire day figuring out what was wrong, and even went so far as to order a replacement SSD, planning to rebuild everything from scratch, because the drive failed to appear in every single USB port I tried. Then I discovered that a different SSD didn't work, either. At that point, I realized that something else was wrong, and I kept trying until I found one other port that worked. I was then able to boot and get dmesg and lsusb output. This kernel update broke not only the built-in ports, but also the ports on a generic USB-C PCIe card (Amazon B08PF8XR73). Mac Pro built-in USB-3.0(A) ports (2x): working Mac Pro built-in USB-C ports (4x): dead USB-C PCIe card USB-C ports (2x): dead USB-C PCIe card USB-3.0(A) ports (5x): dead All devices fail to appear in lsusb when attached to the port, including an Apple USB keyboard, an Anker USB-C Ethernet adapter, a WD SSD, and a Sandisk SSD. I'm going to roll back my kernel to a working kernel, but this package needs to be pulled NOW before it affects too many people. This is too catastrophic a bug to wait even a day. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1959215] [NEW] unshare test in ubuntu_stress_smoke_tests triggers "BUG: unable to handle page fault for address: 0000000000001cc8" on Impish with node vought
Public bug reported: Issue found on Intel node "vought" with: * 5.13.0-28.31 * 5.13.0-27 * And possibly the 5.13.0-23 from the last cycle (this test didn't finish properly and marked as "Incomplete" back then, just like this cycle). For more earlier Impish kernels, this system was not tested with this test on them. The test will hang with unshare test in ubuntu_stress_smoke_tests: 12:39:39 DEBUG| [stdout] udp RETURNED 0 12:39:39 DEBUG| [stdout] udp PASSED 12:39:39 DEBUG| [stdout] udp-flood STARTING 12:39:41 DEBUG| [stdout] udp-flood RETURNED 0 12:39:41 DEBUG| [stdout] udp-flood PASSED 12:39:41 DEBUG| [stdout] unshare STARTING (hangs here) And stop responding. Error can be found in dmesg: [ 2371.109961] BUG: unable to handle page fault for address: 1cc8 [ 2371.110074] #PF: supervisor read access in kernel mode [ 2371.114323] #PF: error_code(0x) - not-present page [ 2371.119931] PGD 0 P4D 0 [ 2371.125257] Oops: [#1] SMP NOPTI [ 2371.129247] CPU: 51 PID: 207256 Comm: stress-ng Tainted: P O 5.13.0-27-generic #29-Ubuntu [ 2371.133203] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS SE5C620.86B.0D.01.0395.022720191340 02/27/2019 [ 2371.135887] RIP: 0010:__next_zones_zonelist+0x6/0x50 [ 2371.138525] Code: d0 0f 4e d0 3d ff 03 00 00 7f 0d 48 63 d2 5d 48 8b 04 d5 60 e5 35 af c3 31 c0 5d c3 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 <8b> 4f 08 48 89 f8 48 89 e5 48 85 d2 75 10 eb 1d 48 63 49 50 48 0f [ 2371.143813] RSP: 0018:a9c8b399fac0 EFLAGS: 00010282 [ 2371.146078] RAX: RBX: RCX: [ 2371.148293] RDX: 9c98e894ea98 RSI: 0002 RDI: 1cc0 [ 2371.150477] RBP: a9c8b399fb28 R08: R09: [ 2371.152650] R10: 0002 R11: d9bfbfcc5600 R12: 00052cc0 [ 2371.154778] R13: 0002 R14: 0001 R15: 00152cc0 [ 2371.156876] FS: 7fcbd141d740() GS:9cc14ccc() knlGS: [ 2371.158936] CS: 0010 DS: ES: CR0: 80050033 [ 2371.160958] CR2: 1cc8 CR3: 00059f292001 CR4: 007706e0 [ 2371.162950] DR0: DR1: DR2: [ 2371.164888] DR3: DR6: fffe0ff0 DR7: 0400 [ 2371.166811] PKRU: 5554 [ 2371.168694] Call Trace: [ 2371.170544] ? __alloc_pages+0x2f1/0x330 [ 2371.172386] kmalloc_large_node+0x45/0xb0 [ 2371.174222] __kmalloc_node+0x276/0x300 [ 2371.176036] ? queue_delayed_work_on+0x39/0x60 [ 2371.177853] kvmalloc_node+0x5a/0x90 [ 2371.179622] expand_one_shrinker_info+0x82/0x190 [ 2371.181382] prealloc_shrinker+0x175/0x1d0 [ 2371.183091] alloc_super+0x2bf/0x330 [ 2371.184764] ? __fput_sync+0x30/0x30 [ 2371.186384] sget_fc+0x74/0x2e0 [ 2371.187951] ? set_anon_super+0x50/0x50 [ 2371.189473] ? mqueue_create+0x20/0x20 [ 2371.190944] get_tree_keyed+0x34/0xd0 [ 2371.192363] mqueue_get_tree+0x1c/0x20 [ 2371.193734] vfs_get_tree+0x2a/0xc0 [ 2371.195105] fc_mount+0x13/0x50 [ 2371.196409] mq_init_ns+0x10a/0x1b0 [ 2371.197667] copy_ipcs+0x130/0x220 [ 2371.198899] create_new_namespaces+0xa6/0x2e0 [ 2371.200113] unshare_nsproxy_namespaces+0x5a/0xb0 [ 2371.201303] ksys_unshare+0x1db/0x3c0 [ 2371.202480] __x64_sys_unshare+0x12/0x20 [ 2371.203649] do_syscall_64+0x61/0xb0 [ 2371.204804] ? exit_to_user_mode_loop+0xec/0x160 [ 2371.205966] ? exit_to_user_mode_prepare+0x37/0xb0 [ 2371.207102] ? syscall_exit_to_user_mode+0x27/0x50 [ 2371.208222] ? __x64_sys_close+0x11/0x40 [ 2371.209336] ? do_syscall_64+0x6e/0xb0 [ 2371.210438] ? asm_exc_page_fault+0x8/0x30 [ 2371.211545] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 2371.212641] RIP: 0033:0x7fcbd1562c4b [ 2371.213698] Code: 73 01 c3 48 8b 0d e5 e1 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 10 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 e1 0e 00 f7 d8 64 89 01 48 [ 2371.215851] RSP: 002b:7ffc5d8eb878 EFLAGS: 0246 ORIG_RAX: 0110 [ 2371.216846] RAX: ffda RBX: 7ffc5d8eba20 RCX: 7fcbd1562c4b [ 2371.217830] RDX: 560296049862 RSI: 0800 RDI: 0800 [ 2371.218886] RBP: 7ffc5d8eb8d0 R08: 5602960234a2 R09: 7fcbd141d740 [ 2371.219908] R10: R11: 0246 R12: 560296049862 [ 2371.220904] R13: 7ffc5d8eba20 R14: 00032980 R15: 5602960397d5 [ 2371.221896] Modules linked in: unix_diag binfmt_misc uhid userio hci_vhci bluetooth ecdh_generic ecc vhost_net tap vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) dccp_ipv4 dccp atm wp512 streebog_generic sm3_generic sha3_generic rmd160 poly1305_generic poly1305_x86_64 nhpoly1305_avx2 nhpoly1305_sse2 nhpoly1305 libpoly1305 michael_mic md4 cmac ccm algif_rng twofish_generic twofish_avx_x86_64
[Kernel-packages] [Bug 1956508] Re: Impish update: upstream stable patchset 2022-01-05
** Changed in: linux (Ubuntu Impish) 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/1956508 Title: Impish update: upstream stable patchset 2022-01-05 Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: Fix Committed 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: upstream stable patchset 2022-01-05 Ported from the following upstream stable releases: v5.10.83, v5.15.6 from git://git.kernel.org/ ACPI: Get acpi_device's parent from the parent field USB: serial: option: add Telit LE910S1 0x9200 composition USB: serial: option: add Fibocom FM101-GL variants usb: dwc2: gadget: Fix ISOC flow for elapsed frames usb: dwc2: hcd_queue: Fix use of floating point literal usb: dwc3: gadget: Ignore NoStream after End Transfer usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer usb: dwc3: gadget: Fix null pointer exception net: nexthop: fix null pointer dereference when IPv6 is not enabled usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in probe usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts usb: hub: Fix usb enumeration issue due to address0 race usb: hub: Fix locking issues with address0_mutex binder: fix test regression due to sender_euid change ALSA: ctxfi: Fix out-of-range access ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100 ALSA: hda/realtek: Fix LED on HP ProBook 435 G7 media: cec: copy sequence field for the reply Revert "parisc: Fix backtrace to always include init funtion names" HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts staging/fbtft: Fix backlight staging: greybus: Add missing rwsem around snd_ctl_remove() calls staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect() fuse: release pipe buf after last use xen: don't continue xenstore initialization in case of errors xen: detect uninitialized xenbus in xenbus_init KVM: PPC: Book3S HV: Prevent POWER7/8 TLB flush flushing SLB tracing/uprobe: Fix uprobe_perf_open probes iteration tracing: Fix pid filtering when triggers are attached mmc: sdhci-esdhc-imx: disable CMDQ support mmc: sdhci: Fix ADMA for PAGE_SIZE >= 64KiB mdio: aspeed: Fix "Link is Down" issue powerpc/32: Fix hardlockup on vmap stack overflow PCI: aardvark: Deduplicate code in advk_pcie_rd_conf() PCI: aardvark: Implement re-issuing config requests on CRS response PCI: aardvark: Simplify initialization of rootcap on virtual bridge PCI: aardvark: Fix link training proc/vmcore: fix clearing user buffer by properly using clear_user() netfilter: ctnetlink: fix filtering with CTA_TUPLE_REPLY netfilter: ctnetlink: do not erase error code with EINVAL netfilter: ipvs: Fix reuse connection if RS weight is 0 netfilter: flowtable: fix IPv6 tunnel addr match ARM: dts: BCM5301X: Fix I2C controller interrupt ARM: dts: BCM5301X: Add interrupt properties to GPIO node ARM: dts: bcm2711: Fix PCIe interrupts ASoC: qdsp6: q6routing: Conditionally reset FrontEnd Mixer ASoC: qdsp6: q6asm: fix q6asm_dai_prepare error handling ASoC: topology: Add missing rwsem around snd_ctl_remove() calls ASoC: codecs: wcd934x: return error code correctly from hw_params net: ieee802154: handle iftypes as u32 firmware: arm_scmi: pm: Propagate return value to caller NFSv42: Don't fail clone() unless the OP_CLONE operation failed ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE drm/nouveau/acr: fix a couple NULL vs IS_ERR() checks scsi: mpt3sas: Fix kernel panic during drive powercycle test drm/vc4: fix error code in vc4_create_object() net: marvell: prestera: fix double free issue on err path iavf: Prevent changing static ITR values if adaptive moderation is on ALSA: intel-dsp-config: add quirk for JSL devices based on ES8336 codec mptcp: fix delack timer firmware: smccc: Fix check for ARCH_SOC_ID not implemented ipv6: fix typos in __ip6_finish_output() nfp: checking parameter process for rx-usecs/tx-usecs is invalid net: stmmac: retain PTP clock time during SIOCSHWTSTAMP ioctls net: ipv6: add fib6_nh_release_dsts stub net: nexthop: release IPv6 per-cpu dsts when replacing a nexthop group ice: fix vsi->txq_map sizing ice: avoid bpf_prog refcount underflow scsi: core: sysfs: Fix setting device state to SDEV_RUNNING scsi: scsi_debug:
[Kernel-packages] [Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
#55 kapper1224 fixed it for me. Didn't create or modify any .conf file(think thats for arch only) Just added the kernel mod param: GRUB_CMDLINE_LINUX="i915.enable_guc=2" then sudo update-grub and reboot -- 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/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: Since the last kernel update 5.11.0-25-generic, the system freezes in a few seconds or minutes, sometimes even on the login screen. The machine is a recent dell latitude 7490. The graphics card is Intel Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the previous kernel 5.8.0-63. I had the same problem with fedora a few months ago, which forced me to switch to ubuntu without any problems so far. Thanks for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: plawrence 1996 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-21 (414 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+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 1956508] Re: Impish update: upstream stable patchset 2022-01-05
And as a late addition also (from 2022-01-18v3): 255441c89d01 net/packet: rx_owner_map depends on pg_vec -- 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/1956508 Title: Impish update: upstream stable patchset 2022-01-05 Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: 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: upstream stable patchset 2022-01-05 Ported from the following upstream stable releases: v5.10.83, v5.15.6 from git://git.kernel.org/ ACPI: Get acpi_device's parent from the parent field USB: serial: option: add Telit LE910S1 0x9200 composition USB: serial: option: add Fibocom FM101-GL variants usb: dwc2: gadget: Fix ISOC flow for elapsed frames usb: dwc2: hcd_queue: Fix use of floating point literal usb: dwc3: gadget: Ignore NoStream after End Transfer usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer usb: dwc3: gadget: Fix null pointer exception net: nexthop: fix null pointer dereference when IPv6 is not enabled usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in probe usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts usb: hub: Fix usb enumeration issue due to address0 race usb: hub: Fix locking issues with address0_mutex binder: fix test regression due to sender_euid change ALSA: ctxfi: Fix out-of-range access ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100 ALSA: hda/realtek: Fix LED on HP ProBook 435 G7 media: cec: copy sequence field for the reply Revert "parisc: Fix backtrace to always include init funtion names" HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts staging/fbtft: Fix backlight staging: greybus: Add missing rwsem around snd_ctl_remove() calls staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect() fuse: release pipe buf after last use xen: don't continue xenstore initialization in case of errors xen: detect uninitialized xenbus in xenbus_init KVM: PPC: Book3S HV: Prevent POWER7/8 TLB flush flushing SLB tracing/uprobe: Fix uprobe_perf_open probes iteration tracing: Fix pid filtering when triggers are attached mmc: sdhci-esdhc-imx: disable CMDQ support mmc: sdhci: Fix ADMA for PAGE_SIZE >= 64KiB mdio: aspeed: Fix "Link is Down" issue powerpc/32: Fix hardlockup on vmap stack overflow PCI: aardvark: Deduplicate code in advk_pcie_rd_conf() PCI: aardvark: Implement re-issuing config requests on CRS response PCI: aardvark: Simplify initialization of rootcap on virtual bridge PCI: aardvark: Fix link training proc/vmcore: fix clearing user buffer by properly using clear_user() netfilter: ctnetlink: fix filtering with CTA_TUPLE_REPLY netfilter: ctnetlink: do not erase error code with EINVAL netfilter: ipvs: Fix reuse connection if RS weight is 0 netfilter: flowtable: fix IPv6 tunnel addr match ARM: dts: BCM5301X: Fix I2C controller interrupt ARM: dts: BCM5301X: Add interrupt properties to GPIO node ARM: dts: bcm2711: Fix PCIe interrupts ASoC: qdsp6: q6routing: Conditionally reset FrontEnd Mixer ASoC: qdsp6: q6asm: fix q6asm_dai_prepare error handling ASoC: topology: Add missing rwsem around snd_ctl_remove() calls ASoC: codecs: wcd934x: return error code correctly from hw_params net: ieee802154: handle iftypes as u32 firmware: arm_scmi: pm: Propagate return value to caller NFSv42: Don't fail clone() unless the OP_CLONE operation failed ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE drm/nouveau/acr: fix a couple NULL vs IS_ERR() checks scsi: mpt3sas: Fix kernel panic during drive powercycle test drm/vc4: fix error code in vc4_create_object() net: marvell: prestera: fix double free issue on err path iavf: Prevent changing static ITR values if adaptive moderation is on ALSA: intel-dsp-config: add quirk for JSL devices based on ES8336 codec mptcp: fix delack timer firmware: smccc: Fix check for ARCH_SOC_ID not implemented ipv6: fix typos in __ip6_finish_output() nfp: checking parameter process for rx-usecs/tx-usecs is invalid net: stmmac: retain PTP clock time during SIOCSHWTSTAMP ioctls net: ipv6: add fib6_nh_release_dsts stub net: nexthop: release IPv6 per-cpu dsts when replacing a nexthop group ice: fix vsi->txq_map sizing ice: avoid bpf_prog refcount underflow scsi: core: sysfs: Fix setting device state to
[Kernel-packages] [Bug 1806396] Re: lis3lv02d: unknown sensor type 0x0 in HP x360 machines
Yes, sorry, that was a typo. -- 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/1806396 Title: lis3lv02d: unknown sensor type 0x0 in HP x360 machines Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 15.684425] lis3lv02d: unknown sensor type 0x0 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2647 F pulseaudio /dev/snd/pcmC0D0p: caravena 2647 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 10:22:33 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806396/+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 1956508] Re: Impish update: upstream stable patchset 2022-01-05
After double checking I added the following patches on top (fixups to the patches included in this set, some come from later stable set submissions): 9ece25545ff2 net/smc: Keep smc_close_final rc during active close 40ac3bc4d46d net/sched: sch_ets: don't remove idle classes from the round-robin list 5d5e274867ef HID: wacom: Reset expected and received contact counts at the same time 8fcdc82a361b HID: wacom: Ignore the confidence flag when a touch is removed 189c345f2937 net: usb: Correct reset handling of smsc95xx 640ca19230e1 cifs: nosharesock should be set on new server -- 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/1956508 Title: Impish update: upstream stable patchset 2022-01-05 Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: 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: upstream stable patchset 2022-01-05 Ported from the following upstream stable releases: v5.10.83, v5.15.6 from git://git.kernel.org/ ACPI: Get acpi_device's parent from the parent field USB: serial: option: add Telit LE910S1 0x9200 composition USB: serial: option: add Fibocom FM101-GL variants usb: dwc2: gadget: Fix ISOC flow for elapsed frames usb: dwc2: hcd_queue: Fix use of floating point literal usb: dwc3: gadget: Ignore NoStream after End Transfer usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer usb: dwc3: gadget: Fix null pointer exception net: nexthop: fix null pointer dereference when IPv6 is not enabled usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in probe usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts usb: hub: Fix usb enumeration issue due to address0 race usb: hub: Fix locking issues with address0_mutex binder: fix test regression due to sender_euid change ALSA: ctxfi: Fix out-of-range access ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100 ALSA: hda/realtek: Fix LED on HP ProBook 435 G7 media: cec: copy sequence field for the reply Revert "parisc: Fix backtrace to always include init funtion names" HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts staging/fbtft: Fix backlight staging: greybus: Add missing rwsem around snd_ctl_remove() calls staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect() fuse: release pipe buf after last use xen: don't continue xenstore initialization in case of errors xen: detect uninitialized xenbus in xenbus_init KVM: PPC: Book3S HV: Prevent POWER7/8 TLB flush flushing SLB tracing/uprobe: Fix uprobe_perf_open probes iteration tracing: Fix pid filtering when triggers are attached mmc: sdhci-esdhc-imx: disable CMDQ support mmc: sdhci: Fix ADMA for PAGE_SIZE >= 64KiB mdio: aspeed: Fix "Link is Down" issue powerpc/32: Fix hardlockup on vmap stack overflow PCI: aardvark: Deduplicate code in advk_pcie_rd_conf() PCI: aardvark: Implement re-issuing config requests on CRS response PCI: aardvark: Simplify initialization of rootcap on virtual bridge PCI: aardvark: Fix link training proc/vmcore: fix clearing user buffer by properly using clear_user() netfilter: ctnetlink: fix filtering with CTA_TUPLE_REPLY netfilter: ctnetlink: do not erase error code with EINVAL netfilter: ipvs: Fix reuse connection if RS weight is 0 netfilter: flowtable: fix IPv6 tunnel addr match ARM: dts: BCM5301X: Fix I2C controller interrupt ARM: dts: BCM5301X: Add interrupt properties to GPIO node ARM: dts: bcm2711: Fix PCIe interrupts ASoC: qdsp6: q6routing: Conditionally reset FrontEnd Mixer ASoC: qdsp6: q6asm: fix q6asm_dai_prepare error handling ASoC: topology: Add missing rwsem around snd_ctl_remove() calls ASoC: codecs: wcd934x: return error code correctly from hw_params net: ieee802154: handle iftypes as u32 firmware: arm_scmi: pm: Propagate return value to caller NFSv42: Don't fail clone() unless the OP_CLONE operation failed ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE drm/nouveau/acr: fix a couple NULL vs IS_ERR() checks scsi: mpt3sas: Fix kernel panic during drive powercycle test drm/vc4: fix error code in vc4_create_object() net: marvell: prestera: fix double free issue on err path iavf: Prevent changing static ITR values if adaptive moderation is on ALSA: intel-dsp-config: add quirk for JSL devices based on ES8336 codec mptcp: fix delack timer
[Kernel-packages] [Bug 1959194] [NEW] zfs mount is error free but no directory is present
Public bug reported: Hello In a 22.04 version installed in an EXT4 partition, I am trying to watch the contents of a 22.04 version installed in a ZFS partition. I can't. However, I can easily access the "duplicate" of this partition which was created under ZFS. I think it certainly needs an additional option that I can't find. But maybe this is a bug??? Can you help me. Thank you. sudo blkid | grep zfs_member /dev/sdb4: LABEL="rpool" UUID="3705767347231228268" UUID_SUB="17088151264315178202" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="4c7ee6a4-46e4-a244-83ad-744047de9184" /dev/sdb3: LABEL="bpool" UUID="2280493683547443963" UUID_SUB="6738067129089399524" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="ab89c3ca-8125-dc40-83f9-2d1050c1251c" /dev/sdc6: LABEL="poolSORTIE" UUID="10752972542097428173" UUID_SUB="3388036065267144189" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="2be01f36-25c3-463c-9ba2-fbbe0b0b9a45" On a duplicate partition of rpool all is good sudo zpool import -f -N poolSORTIE Sortie; zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT Sortie 19.5G 10.1G 9.36G- - 0%51% 1.00xONLINE - sudo zfs set mountpoint=/mnt/Sortie Sortie sudo zfs set canmount=on Sortie sudo zfs mount Sortie ls /mnt/Sortie bin boot cdrom dev etc home lib lib32 lib64 libx32 media mnt opt proc sudo zpool export Sortie ; zpool list no pools available ls /mnt/Sortie -- On the rpool partition, No directory is visible. sudo zpool import -f -N rpool Root; zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT Root 920G 5.00G 915G- - 0% 0% 1.00xONLINE - sudo zfs set mountpoint=/mnt/Root Root sudo zfs set canmount=on Root sudo zfs mount Root ls /mnt/Root However no error on the mount action janv. 27 09:43:51 b sudo[8050]:a : TTY=pts/1 ; PWD=/home/a ; USER=root ; COMMAND=/usr/sbin/zpool import -f -N rpool Root janv. 27 09:43:51 b sudo[8050]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) janv. 27 09:43:55 b zed[8214]: eid=37 class=config_sync pool='Root' janv. 27 09:43:55 b zed[8216]: eid=38 class=pool_import pool='Root' janv. 27 09:43:55 b zed[8238]: eid=40 class=config_sync pool='Root' janv. 27 09:43:55 b sudo[8050]: pam_unix(sudo:session): session closed for user root janv. 27 09:44:59 b sudo[8360]:a : TTY=pts/1 ; PWD=/home/a ; USER=root ; COMMAND=/usr/sbin/zfs set mountpoint=/mnt/Root Root janv. 27 09:44:59 b sudo[8360]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) janv. 27 09:45:00 b sudo[8360]: pam_unix(sudo:session): session closed for user root janv. 27 09:45:00 b sudo[8376]:a : TTY=pts/1 ; PWD=/home/a ; USER=root ; COMMAND=/usr/sbin/zfs set canmount=on Root janv. 27 09:45:00 b sudo[8376]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) janv. 27 09:45:00 b sudo[8376]: pam_unix(sudo:session): session closed for user root janv. 27 09:45:00 b sudo[8387]:a : TTY=pts/1 ; PWD=/home/a ; USER=root ; COMMAND=/usr/sbin/zfs mount Root janv. 27 09:45:00 b sudo[8387]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) janv. 27 09:45:00 b sudo[8387]: pam_unix(sudo:session): session closed for user root sudo zpool export Root ; zpool list ls /mnt/Root ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfsutils-linux 2.1.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 27 10:33:07 2022 InstallationDate: Installed on 2021-11-01 (86 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211031) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission non accordée: '/etc/sudoers.d/zfs'] ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1959194 Title: zfs mount is error free but no directory is present Status in zfs-linux package in Ubuntu: New Bug description: Hello In a 22.04 version installed in an EXT4 partition, I am trying to watch the contents of a 22.04 version installed in a ZFS partition. I can't. However, I can easily access the "duplicate" of this partition which was created under ZFS. I think it certainly needs an additional option that I can't find. But maybe this is a bug??? Can you help me. Thank you. sudo blkid | grep zfs_member
[Kernel-packages] [Bug 1954938] Re: Include the QCA WCN 6856 v2.1 support - WIFI 6
PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1954938 -- 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/1954938 Title: Include the QCA WCN 6856 v2.1 support - WIFI 6 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: Incomplete Status in linux-firmware source package in Impish: New Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Incomplete Status in linux-firmware source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954938/+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 1958774] Re: Black screen after suspending and closing LID
** Description changed: These bugs occur after I upgrade the linux-generic package from 5.11 (not sure) to 5.13 today. After that, I have met two similar bugs: 1. Every time I suspend my computer and re-activate it, I will get a black screen with a bleaking cursor. 2. Every time I close my laptop's LID and reopen it, I will get an empty black screen (without anything). These bugs really trouble me. It will be very helpful if you fix it. UPDATE on 2022/01/25: After I upgraded the "core" package using "snap refresh", the first bug has been fixed. However, the second bug related to laptop devices is still there. UPDATE on 2022/01/26: The first bug is still there. It seems that the bug just occasionally disappeared when I tried it yesterday, but actually it is still there since today I enter the bleaking-cursor- black-screen situation again. UPDATE on 2022/01/27: With respect to the suspend bug: I followed Thomas's guide and suspended my computer for several times. I have the following observation: 1. When I use the commandline to put my PC into STR or STI (I cannot put it into Hibernation, not sure whether this is because I don't allocate a swap partition for it) by commands like "echo mem | sudo tee /sys/power/state", it never encounters any problem. 2. The problem occurs only when I use the suspend button in the menu at the right end of the GNOME status bar. After that, the PC will get into a black screen, and then immediately and automatically revoke itself. After that, it shows the logging screen. I enter the password and punch the enter key. Then, it prints a long error message as follows: > [ 121.509899] gdm3[11143]: segfault at 0 ip 558aaf0a912a sp 7fff1cd7cf10 error 4 in gdm3[558aaf093000+32000] > [ 121.509926] Code: 95 c7 40 0f b6 ff e8 d5 8a 01 00 8b 54 24 08 be 80 00 00 00 48 89 df 49 89 c7 4c 8d 05 04 ea 01 00 48 8d 05 1b 51 02 00 85 d2 <49> 8b 0f 48 8d 15 6c 02 02 00 4c 0f 44 c0 31 c0 e8 d1 dd fe ff 45 It gets stuck there and I have to use the power button to force reboot. With respect to the LID bug: I still cannot get any information. After I close the LID and reopen it, my PC gets stuck at a pure black screen without anything, even a cursor. Moreover, it's not totally black, but with a bit LED light, which means that the LID has power supply. I'm not sure whether I describe this clearly. You can imagine closing your iPhone. It will first get into a status where the screen still has power and some light before completely shutting down. My LID is a bit like this. - I'll try to ssh my computer in this status and look for more info. + I'll try to ssh to my computer in this status and look for more info. + + UPDATE #2 on 2022/01/27: It seems that I've found the reason for the LID + bug. I close and reopen my laptop's LID to put it into the black screen + status, and then I ssh to it. I then enter "systemctl list-units" and + find that there are two units failing to load. The info of these two + units got by "systemctl status" is as follows: + + > modprobe@drm.service - Load Kernel Module drm + > Loaded: loaded (/lib/systemd/system/modprobe@.service; static) + > Active: failed (Result: start-limit-hit) since Thu 2022-01-27 17:12:07 CST; 43s ago + >Docs: man:modprobe(8) + > Process: 8387 ExecStart=/sbin/modprobe -abq drm (code=exited, status=0/SUCCESS) + >Main PID: 8387 (code=exited, status=0/SUCCESS) + > CPU: 2ms + > + > Jan 27 17:12:07 lenovopc systemd[1]: Finished Load Kernel Module drm. + > Jan 27 17:12:07 lenovopc systemd[1]: modprobe@drm.service: Start request repeated too quickly. + > Jan 27 17:12:07 lenovopc systemd[1]: modprobe@drm.service: Failed with result 'start-limit-hit'. + > Jan 27 17:12:07 lenovopc systemd[1]: Failed to start Load Kernel Module drm. + > Jan 27 17:12:07 lenovopc systemd[1]: modprobe@drm.service: Start request repeated too quickly. + > Jan 27 17:12:07 lenovopc systemd[1]: modprobe@drm.service: Failed with result 'start-limit-hit'. + > Jan 27 17:12:07 lenovopc systemd[1]: Failed to start Load Kernel Module drm. + > Jan 27 17:12:07 lenovopc systemd[1]: modprobe@drm.service: Start request repeated too quickly. + > Jan 27 17:12:07 lenovopc systemd[1]: modprobe@drm.service: Failed with result 'start-limit-hit'. + > Jan 27 17:12:07 lenovopc systemd[1]: Failed to start Load Kernel Module drm. + + and + + > systemd-logind.service - User Login Management + > Loaded: loaded (/lib/systemd/system/systemd-logind.service; static) + > Active: failed (Result: exit-code) since Thu 2022-01-27 17:12:07 CST; 1min 7s ago + >Docs: man:sd-login(3) + > man:systemd-logind.service(8) + > man:logind.conf(5) + > man:org.freedesktop.login1(5) + > Process: 8417 ExecStart=/lib/systemd/systemd-logind (code=exited, status=1/FAILURE) + >Main PID: 8417 (code=exited,
[Kernel-packages] [Bug 1959193] [NEW] symlink loop in libnvpair1linux
Public bug reported: I got this e-mail that debsums found a symlink loop and am filing a bug as instructed: /etc/cron.daily/debsums: debsums: Error: symlink loop detected in path 'usr/share/doc/libnvpair1linux/COPYRIGHT'. Please file a bug again libnvpair1linux. Additional info: ~$ apt-cache policy libnvpair1linux libnvpair1linux: Installed: 0.7.5-1ubuntu16.12 Candidate: 0.7.5-1ubuntu16.12 Version table: *** 0.7.5-1ubuntu16.12 500 500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.7.5-1ubuntu15 500 500 http://dk.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ~$ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- 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/1959193 Title: symlink loop in libnvpair1linux Status in zfs-linux package in Ubuntu: New Bug description: I got this e-mail that debsums found a symlink loop and am filing a bug as instructed: /etc/cron.daily/debsums: debsums: Error: symlink loop detected in path 'usr/share/doc/libnvpair1linux/COPYRIGHT'. Please file a bug again libnvpair1linux. Additional info: ~$ apt-cache policy libnvpair1linux libnvpair1linux: Installed: 0.7.5-1ubuntu16.12 Candidate: 0.7.5-1ubuntu16.12 Version table: *** 0.7.5-1ubuntu16.12 500 500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.7.5-1ubuntu15 500 500 http://dk.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ~$ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1959193/+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 1827980] Re: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3
Found also on: d2021.10.26/jammy/linux/5.15.0-17.17 (node: akis.amd64) d2021.10.26/jammy/linux-realtime/5.15.0-1004.4 (node: lagalla.amd64) ** Tags added: 5.15 jammy realtime ** Tags added: hinted -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1827980 Title: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3 Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Bug description: Test timeout. # TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev # -initrd /tmp/tmp.LeYhxJZmHV qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic ncpus = 2 prepare qemu-system-x86_64: terminating on signal 15 from pid 1658 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:36:32 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827980/+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 1827982] Re: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3 / B-Oracle-5.4
15:45:12 DEBUG| [stdout] PASS: Hyper-V SynIC periodic timers test vcpu 1 15:45:12 DEBUG| [stdout] PASS: Hyper-V SynIC periodic timers test vcpu 0 15:45:12 DEBUG| [stdout] PASS: Hyper-V SynIC one-shot test vcpu 1 15:45:12 DEBUG| [stdout] PASS: Hyper-V SynIC one-shot test vcpu 0 15:45:12 DEBUG| [stdout] PASS: Hyper-V SynIC auto-enable one-shot timer test vcpu 1 15:45:12 DEBUG| [stdout] PASS: Hyper-V SynIC auto-enable one-shot timer test vcpu 0 15:45:13 DEBUG| [stdout] PASS: Hyper-V SynIC auto-enable periodic timer test vcpu 1 15:45:13 DEBUG| [stdout] PASS: Hyper-V SynIC auto-enable periodic timer test vcpu 0 15:45:13 DEBUG| [stdout] PASS: no timer fired while msg slot busy: vcpu 1 15:45:13 DEBUG| [stdout] PASS: timer resumed when msg slot released: vcpu 1 15:45:13 DEBUG| [stdout] PASS: no timer fired while msg slot busy: vcpu 0 15:45:13 DEBUG| [stdout] PASS: timer resumed when msg slot released: vcpu 0 15:46:40 DEBUG| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 18030 (timeout) 15:46:41 DEBUG| [stdout] FAIL hyperv_stimer (timeout; duration=90s) Found also on: d2021.10.26/jammy/linux/5.15.0-17.17 (node: akis.amd64) d2021.10.26/jammy/linux-realtime/5.15.0-1004.4 (node: lagalla.amd64) ** Tags added: 5.15 hinted jammy realtime -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1827982 Title: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3 / B-Oracle-5.4 Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Bug description: Test timeouted. # TESTNAME=hyperv_stimer TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev # -initrd /tmp/tmp.ouYfwUEdq5 qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic cpus = 2 qemu-system-x86_64: terminating on signal 15 from pid 2224 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:39:16 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827982/+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 1827980] Re: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oracle (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1827980 Title: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3 Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Bug description: Test timeout. # TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev # -initrd /tmp/tmp.LeYhxJZmHV qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic ncpus = 2 prepare qemu-system-x86_64: terminating on signal 15 from pid 1658 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:36:32 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827980/+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 1827980] Re: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-kvm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1827980 Title: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3 Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Bug description: Test timeout. # TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev # -initrd /tmp/tmp.LeYhxJZmHV qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic ncpus = 2 prepare qemu-system-x86_64: terminating on signal 15 from pid 1658 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:36:32 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827980/+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 1956561] Re: 5.15 kernel selftest srv6_end_dt46_l3vpn_test.sh failure
Found on: d2021.10.26/jammy/linux-realtime/5.15.0-1004.4 (appleton- kernel.arm64) ** Tags added: 5.15 arm64 jammy realtime ubuntu-kernel-selftests -- 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/1956561 Title: 5.15 kernel selftest srv6_end_dt46_l3vpn_test.sh failure Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Kernel selftest srv6_end_dt46_l3vpn_test.sh reports the following error (it seems to be an upstream issue): 15187 19:34:40 DEBUG| [stdout] # 15188 19:34:40 DEBUG| [stdout] # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant 15189 19:34:40 DEBUG| [stdout] # 15190 19:34:41 DEBUG| [stdout] # 15191 19:34:41 DEBUG| [stdout] # TEST: IPv6 Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [ OK ] 15192 19:34:45 DEBUG| [stdout] # 15193 19:34:45 DEBUG| [stdout] # TEST: IPv4 Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [FAIL] 15194 19:34:45 DEBUG| [stdout] # 15195 19:34:45 DEBUG| [stdout] # TEST: IPv6 Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [ OK ] 15196 19:34:49 DEBUG| [stdout] # 15197 19:34:49 DEBUG| [stdout] # TEST: IPv4 Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [FAIL] 15198 19:34:50 DEBUG| [stdout] # 15199 19:34:50 DEBUG| [stdout] # TEST: IPv6 Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [ OK ] 15200 19:34:54 DEBUG| [stdout] # 15201 19:34:54 DEBUG| [stdout] # TEST: IPv4 Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [FAIL] 15202 19:34:54 DEBUG| [stdout] # 15203 19:34:54 DEBUG| [stdout] # TEST: IPv6 Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [ OK ] 15204 19:34:58 DEBUG| [stdout] # 15205 19:34:58 DEBUG| [stdout] # TEST: IPv4 Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956561/+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 1956562] Re: 5.15 kernel selftest srv6_end_dt4_l3vpn_test.sh failure
Found on: d2021.10.26/jammy/linux-realtime/5.15.0-1004.4 (appleton- kernel.arm64) ** Tags added: 5.15 arm64 jammy realtime ubuntu-kernel-selftests -- 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/1956562 Title: 5.15 kernel selftest srv6_end_dt4_l3vpn_test.sh failure Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Script srv6_end_dt4_l3vpn_test.sh reports the following failure (upstream issue): 15321 19:35:52 DEBUG| [stdout] # 15322 19:35:52 DEBUG| [stdout] # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant 15323 19:35:52 DEBUG| [stdout] # 15324 19:35:56 DEBUG| [stdout] # 15325 19:35:56 DEBUG| [stdout] # TEST: Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [FAIL] 15326 19:36:00 DEBUG| [stdout] # 15327 19:36:00 DEBUG| [stdout] # TEST: Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [FAIL] 15328 19:36:04 DEBUG| [stdout] # 15329 19:36:04 DEBUG| [stdout] # TEST: Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [FAIL] 15330 19:36:08 DEBUG| [stdout] # 15331 19:36:08 DEBUG| [stdout] # TEST: Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [FAIL] 15332 19:36:08 DEBUG| [stdout] # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956562/+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 1959173] Re: Vulnerability in af_packet handling
** Changed in: linux-gke (Ubuntu) Status: New => Invalid ** Changed in: linux-gke (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-gke (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-gke (Ubuntu Focal) Assignee: (unassigned) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/1959173 Title: Vulnerability in af_packet handling Status in linux-gke package in Ubuntu: Invalid Status in linux-gke source package in Focal: In Progress Bug description: CVE-2021-22600 A vulnerability, which was classified as critical, was found in Linux Kernel. Affected is the function packet_set_ring of the file net/packet/af_packet.c. The manipulation with an unknown input leads to a memory corruption vulnerability. This is going to have an impact on confidentiality, integrity, and availability. The weakness was released 01/26/2022. The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2021-22600 since 01/05/2021. The exploitability is told to be easy. It is possible to launch the attack remotely. A authentication is required for exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 01/26/2022). Applying a patch is able to eliminate this problem. The fix is https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=ec6af094ea28f0f2dda1a6a33b14cd57e36a9755 More information at: https://partnerissuetracker.corp.google.com/issues/215427453 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1959173/+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 1958121] Re: test_bpf.sh unreliable on ppc64el and arm64
*** This bug is a duplicate of bug 1955011 *** https://bugs.launchpad.net/bugs/1955011 This was earlier reported as lp:1955011 ** This bug has been marked a duplicate of bug 1955011 ubuntu_kernel_selftests:net:test_bpf BPF_ATOMIC FAIL to select_runtime err=-524 -- 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/1958121 Title: test_bpf.sh unreliable on ppc64el and arm64 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: kernel selftest net:test_bpf.sh can return the following error on ppc64el and arm64: 10664 02:12:25 DEBUG| [stdout] [ 1001.533842] test_bpf: #313 BPF_ATOMIC | BPF_W, BPF_ADD | BPF_FETCH: Test: 0x12 + 0xab = 0xbd 10665 02:12:25 DEBUG| [stdout] [ 1001.533855] bpf_jit: unknown atomic op code 01 10666 02:12:25 DEBUG| [stdout] [ 1001.538305] FAIL to select_runtime err=-524 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1958121/+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 1959119] Re: Fix sprintf usage that may lead to buffer overflow
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-bluefield (Ubuntu Focal) Assignee: (unassigned) => Jitendra Lanka (jlankanvidia) ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid -- 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/1959119 Title: Fix sprintf usage that may lead to buffer overflow Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: In Progress Bug description: SRU Justification: [Impact] Fix references to sprintf that have a possibility for buffer overflow [Fix] Replace sprintf with snprintf containing a defined boundary of PAGE_SIZE for sysfs store/show functions and max array size defined otherwise. [Test Case] Existing testcases should work as is as no functional change has been introduced by this patch. [Regression Potential] Regression potential can be considered minimal since the patch does not change any function of the driver other than limiting the upper bound of sprintf where the usual lengths parsed are < PAGE_SIZE and requests > PAGE_SIZE are limited. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1959119/+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 1958774] Re: Black screen after suspending and closing LID
** Description changed: These bugs occur after I upgrade the linux-generic package from 5.11 (not sure) to 5.13 today. After that, I have met two similar bugs: 1. Every time I suspend my computer and re-activate it, I will get a black screen with a bleaking cursor. 2. Every time I close my laptop's LID and reopen it, I will get an empty black screen (without anything). These bugs really trouble me. It will be very helpful if you fix it. - UPDATE on 2022/01/25: After I upgraded the "core" package using "snap - refresh", the first bug has been fixed. However, the second bug related - to laptop devices is still there. - UPDATE on 2022/01/26: The first bug is still there. It seems that the - bug just occasionally disappeared when I tried it yesterday, but - actually it is still there since today I enter the bleaking-cursor- - black-screen situation again. + UPDATE on 2022/01/25: After I upgraded the "core" package using "snap refresh", the first bug has been fixed. However, the second bug related to laptop devices is still there. + + + UPDATE on 2022/01/26: The first bug is still there. It seems that the bug just occasionally disappeared when I tried it yesterday, but actually it is still there since today I enter the bleaking-cursor-black-screen situation again. + + + UPDATE on 2022/01/27: + + With respect to Bug #1: + + I followed Thomas's guide and suspended my computer for several times. I have the following observation: + 1. When I use the commandline to put my PC into STR or STI (I cannot put it into Hibernation, not sure whether this is because I don't allocate a swap partition for it) by commands like "echo mem | sudo tee /sys/power/state", it never encounters any problem. + 2. The problem occurs only when I use the suspend button in the menu at the right end of the status bar. After that, the PC will get into a black screen, and then immediately and automatically revoke itself. After that, it shows the logging screen. I enter the password and punch the enter key. Then, it prints a long error message as follows: + + > [ 121.509899] gdm3[11143]: segfault at 0 ip 558aaf0a912a sp 7fff1cd7cf10 error 4 in gdm3[558aaf093000+32000] + > [ 121.509926] Code: 95 c7 40 0f b6 ff e8 d5 8a 01 00 8b 54 24 08 be 80 00 00 00 48 89 df 49 89 c7 4c 8d 05 04 ea 01 00 48 8d 05 1b 51 02 00 85 d2 <49> 8b 0f 48 8d 15 6c 02 02 00 4c 0f 44 c0 31 c0 e8 d1 dd fe ff 45 + + It gets stuck there and I have to use the power button to force reboot. + + With respect to Bug #2: + + I still cannot get any information. After I close the LID and reopen it, + my PC gets stuck at a pure black screen without anything, even a cursor. + Moreover, it's not totally black, but with a bit LED light, which means + that the LID has power supply. I'm not sure whether I describe this + clearly. You can imagine closing your iPhone. It will first get into a + status where the screen still has power and some light before completely + shutting down. My LID is a bit like this. + + I'll try to ssh my computer in this status and look for more info. + ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-generic 5.13.0.27.37 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nomanous 5648 F pulseaudio /dev/snd/controlC1: nomanous 5648 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 23:02:24 2022 InstallationDate: Installed on 2021-06-29 (208 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HASEE Computer NH5x_7xDCx_DDx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=018344b7-14eb-4d4a-b012-cf2577a7bc6a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-27-generic N/A linux-backports-modules-5.13.0-27-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-15 (100 days ago) dmi.bios.date: 04/18/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03THZX dmi.board.asset.tag: Tag 12345 dmi.board.name: NH5x_7xDCx_DDx dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.1 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03THZX:bd04/18/2020:br7.3:efr7.1:svnHASEEComputer:pnNH5x_7xDCx_DDx:pvrNotApplicable:rvnNotebook:rnNH5x_7xDCx_DDx:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NH5x_7xDCx_DDx dmi.product.sku: Not
[Kernel-packages] [Bug 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
** Changed in: linux-firmware (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] So far all the patches can be cleanly applied, and they're being progressively proposed to linux-stable. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1951422] Re: Ucore kernel snap size: netronome smartnic fw
** Changed in: linux-raspi (Ubuntu) Status: New => Invalid ** Changed in: linux-raspi (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-raspi (Ubuntu Focal) 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/1951422 Title: Ucore kernel snap size: netronome smartnic fw Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Focal: In Progress Bug description: [ Impact ] Pi kernel snaps are big in part due to included firmware binaries. A lot of these binaries are not needed/required by the Pi kernel. The size of the snap has a negative impact on boot speed. [ Fix ] Parse modinfo data from all modules to determine the list of required firmware files and remove the ones that are not necessary during snap build time. [ Test Case ] On core20 before: $ du -sh /lib/firmware/ 602M /lib/firmware/ And after: $ du -sh /lib/firmware/ 58M /lib/firmware/ [ Where Problems Could Occur ] We might accidentally drop needed firmware which might render the relevant HW unusable. Firmware load failures should be visible in the kernel log though. [ Original Description ] The size of the pi-kernel snap for UC20 is 254Mbytes (compressed) and 794Mbytes (uncompressed). 569Mbyte of this is caused by FW 140Mbyte -> Netronome SmartNIC Removing unreferenced FW and/or reducing number of drivers & their FW has exponential reduction of disk space usage. Additionally, downloaded image will be smaller; and storing 3x kernel snaps for upgrades will be smaller. Even more, snap seeding will be faster, so boot time will be faster. So it will be a nice gain in multiple aspects: download image, boot image, upgrade image, reboot image, start using image. stulluk ~/tmp $ ls -lah pi-kernel_353.snap -rw--- 1 stulluk stulluk 254M Kas 8 13:57 pi-kernel_353.snap stulluk ~/tmp $ cd pikern/ stulluk ~/tmp/pikern $ du -sh 794M . stulluk ~/tmp/pikern $ cd firmware/ stulluk ~/tmp/pikern/firmware $ du --block-size=MiB --max-depth=1 . | sort -rn 569MiB. 140MiB./netronome 40MiB ./amdgpu 34MiB ./intel 25MiB ./liquidio 24MiB ./qcom 20MiB ./qed 19MiB ./brcm 12MiB ./mellanox 12MiB ./dpaa2 12MiB ./ath10k ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1951422/+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 1951423] Re: Ucore kernel snap size: amd gpu fw
** Also affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu) Status: New => Invalid ** Changed in: linux-raspi (Ubuntu Focal) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux-raspi (Ubuntu Focal) Status: New => In Progress -- 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/1951423 Title: Ucore kernel snap size: amd gpu fw Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Focal: In Progress Bug description: The size of the kernel snap for UC20 is 254Mbytes (compressed) and 794Mbytes (uncompressed). 569Mbyte of this is caused by FW 40Mbyte -> amdgpu IMO, removing unreferenced FW and/or reducing number of drivers & their FW has exponential reduction of disk space usage. Additionally, downloaded image will be smaller; and storing 3x kernel snaps for upgrades will be smaller. Even more, snap seeding will be faster, so boot time will be faster. So it will be a nice gain in multiple aspects: download image, boot image, upgrade image, reboot image, start using image. stulluk ~/tmp $ ls -lah pi-kernel_353.snap -rw--- 1 stulluk stulluk 254M Kas 8 13:57 pi-kernel_353.snap stulluk ~/tmp $ cd pikern/ stulluk ~/tmp/pikern $ du -sh 794M . stulluk ~/tmp/pikern $ cd firmware/ stulluk ~/tmp/pikern/firmware $ du --block-size=MiB --max-depth=1 . | sort -rn 569MiB. 140MiB./netronome 40MiB ./amdgpu 34MiB ./intel 25MiB ./liquidio 24MiB ./qcom 20MiB ./qed 19MiB ./brcm 12MiB ./mellanox 12MiB ./dpaa2 12MiB ./ath10k ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1951423/+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 1959064] Re: [SRU][F] Add mt8183 SCP firmware
** Tags added: kern-2069 -- 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/1959064 Title: [SRU][F] Add mt8183 SCP firmware Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Committed Bug description: [Impact] No driver is loaded for scp firmware on the mt8183 platform, and fw is missing too. [Fix] Add mt8183 SCP firmware [Test] Verified on the mt8183 platform, it can be loaded and powered up. [Where problems could occur] This firmware is specific for mt8183, it should be low risk. The firmware is already in impish and jammy, only SRU fw for focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1959064/+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 1959102] Re: Kernel fails to boot in ScalingStack
** Tags added: kern-2070 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1959102 Title: Kernel fails to boot in ScalingStack Status in linux-raspi package in Ubuntu: New Status in linux-raspi-5.4 package in Ubuntu: Invalid Status in linux-raspi-5.4 source package in Bionic: New Status in linux-raspi source package in Focal: New Status in linux-raspi source package in Impish: New Status in linux-raspi source package in Jammy: New Bug description: [ Impact ] The raspi kernel fails to boot in ScalingStack which is our OpenStack cluster for running ADT/autopkgtest tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1959102/+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
