[Kernel-packages] [Bug 1955174] Re: Unkillable process pegging CPU
[Expired for linux-raspi (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-raspi (Ubuntu) Status: Incomplete => Expired -- 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/1955174 Title: Unkillable process pegging CPU Status in linux-raspi package in Ubuntu: Expired Bug description: The following very simple bash script results in an unkillable process topping the CPU. ``` #!/bin/bash while true; do echo -n "." if echo "hw-tc-offload: off [fixed]" 2>&1 | grep 'x-checksumming' ; then echo "should never get here" fi done ``` I can reproduce the issue by starting a few (8) concurrent executions and wait a few minutes. The system used is: ``` > cat /etc/os-release PRETTY_NAME="Ubuntu 21.10" NAME="Ubuntu" VERSION_ID="21.10" VERSION="21.10 (Impish Indri)" VERSION_CODENAME=impish ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=impish ``` With kernel: ``` > uname -a Linux ubuntu 5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux ``` The issue reported over at [1] and it seems to not be present on debian [2]. At the time the issue is triggered top shows the script using one of the CPUs: ``` top - 16:39:24 up 21 min, 10 users, load average: 1.86, 3.00, 3.52 Tasks: 194 total, 3 running, 191 sleeping, 0 stopped, 0 zombie %Cpu(s): 11.1 us, 32.1 sy, 0.0 ni, 56.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 7808.5 total, 5194.8 free,873.9 used, 1739.7 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 6682.4 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 78617 ubuntu20 08836408 0 R 99.7 0.0 9:09.02 repro.sh ``` The stack of the CPU as reported by sysrq with the "l" option: ``` [ 876.197594] sysrq: Show backtrace of all active CPUs [ 876.202717] sysrq: CPU1: [ 876.202724] Call trace: [ 876.202727] dump_backtrace+0x0/0x1ec [ 876.202738] show_stack+0x24/0x30 [ 876.202743] showacpu+0x84/0x94 [ 876.202751] flush_smp_call_function_queue+0xd8/0x260 [ 876.202757] generic_smp_call_function_single_interrupt+0x20/0x2c [ 876.202762] do_handle_IPI+0x1d8/0x310 [ 876.202769] ipi_handler+0x28/0x40 [ 876.202774] handle_percpu_devid_irq+0x94/0x270 [ 876.202780] __handle_domain_irq+0x88/0xec [ 876.202787] gic_handle_irq+0x5c/0xf0 [ 876.202791] el1_irq+0xc0/0x15c [ 876.202795] schedule_tail+0x12c/0x1fc [ 876.202802] ret_from_fork+0x4/0x3c ``` The stack of the stuck: ``` > cat /proc/78617/stack [<0>] __switch_to+0x138/0x190 [<0>] exit_to_kernel_mode+0x28/0x80 ``` This is causing MicroK8s to fail after a few days. Thank you for your help. [1] https://github.com/ubuntu/microk8s/issues/2280#issuecomment-866912974 [2] https://github.com/ubuntu/microk8s/issues/2280#issuecomment-931306599 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1955174/+subscriptions -- Mailing list: https://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 1977638] Re: screen become black after few minutes
[Expired for linux-raspi (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-raspi (Ubuntu) Status: Incomplete => Expired -- 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/1977638 Title: screen become black after few minutes Status in linux-raspi package in Ubuntu: Expired Bug description: After a few minutes the screen become black, but the system continues to run. After I remove the HDMI screen cable, the system restarts. System: Ubuntu 22.04 LTS ( Release 22.04 ) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 4 09:20:15 2022 ImageMediaBuild: 20201022 SourcePackage: linux-raspi UpgradeStatus: Upgraded to jammy on 2022-05-13 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1977638/+subscriptions -- Mailing list: https://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 1987232] Re: WARN in trace_event_dyn_put_ref
Should this also get nominated as affecting Focal? I hit this on the 5.15 kernel that was attached to linux-aws for 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/1987232 Title: WARN in trace_event_dyn_put_ref Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Confirmed Bug description: I have systems that are regularly hitting a WARN in trace_event_dyn_put_ref. The exact message is: WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46 +trace_event_dyn_put_ref+0x15/0x20 With the following stacktrace: perf_trace_init+0x8f/0xd0 perf_tp_event_init+0x1f/0x40 perf_try_init_event+0x4a/0x130 perf_event_alloc+0x497/0xf40 __do_sys_perf_event_open+0x1d4/0xf70 __x64_sys_perf_event_open+0x20/0x30 do_syscall_64+0x5c/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae I've debugged this and worked with upstream to get a fix into Linux. It was recently merged in 6.0-rc2. See here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2=7249921d94ff64f67b733eca0b68853a62032b3d The problem started appearing as soon as our systems picked up the linux-aws-5.15 branch for Focal. (That was 5.15.0-1015-aws, if memory serves). Could you please cherry pick this fix and pull it back to the the linux and linux-aws kernels for Focal? There's test here: https://lore.kernel.org/all/cover.1660347763.git.k...@templeofstupid.com/ that reproduces the problem very reliably for me. With the patch applied, I no longer get the WARNs. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 22 17:32 seq crw-rw 1 root audio 116, 33 Aug 22 17:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 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: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Amazon EC2 c5d.12xlarge Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1015-aws root=PARTUUID=4986e35b-1bd5-45d3-b528-fa2edb861a38 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 ProcVersionSignature: Ubuntu 5.15.0-1015.19~20.04.1-aws 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-1015-aws N/A linux-backports-modules-5.15.0-1015-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.15.0-1015-aws x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 10/16/2017 dmi.bios.release: 1.0 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-03f5d8581c7ad94aa dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:br1.0:svnAmazonEC2:pnc5d.12xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:sku: dmi.product.name: c5d.12xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987232/+subscriptions -- Mailing list: https://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 1976184] Re: Linux PV device frontends vulnerable to attacks by backends
I am using this bug to track 7 security vulnerabilities in Ubuntu kernels. ** Changed in: linux-aws-5.15 (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released ** Changed in: linux-gcp (Ubuntu) Status: New => Fix Released ** Changed in: linux-gcp-5.4 (Ubuntu) Status: New => Fix Released ** Changed in: linux-gke (Ubuntu) Status: New => Fix Released ** Changed in: linux-gkeop-5.4 (Ubuntu) Status: New => Fix Released ** No longer affects: linux-hwe-5.13 (Ubuntu) ** Changed in: linux-intel-iotg-5.15 (Ubuntu) Status: New => Fix Released ** Changed in: linux-raspi (Ubuntu) Status: New => Fix Released ** No longer affects: linux-riscv (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1976184 Title: Linux PV device frontends vulnerable to attacks by backends Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-aws-5.15 package in Ubuntu: Fix Released Status in linux-aws-5.4 package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure-5.4 package in Ubuntu: Fix Released Status in linux-bluefield package in Ubuntu: Fix Released Status in linux-dell300x package in Ubuntu: New Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gcp-4.15 package in Ubuntu: New Status in linux-gcp-5.4 package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Fix Released Status in linux-gke-5.4 package in Ubuntu: Fix Released Status in linux-gkeop package in Ubuntu: Fix Released Status in linux-gkeop-5.4 package in Ubuntu: Fix Released Status in linux-hwe-5.4 package in Ubuntu: Fix Released Status in linux-ibm package in Ubuntu: Fix Released Status in linux-ibm-5.4 package in Ubuntu: Fix Released Status in linux-intel-iotg-5.15 package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: Won't Fix Status in linux-oracle package in Ubuntu: New Status in linux-oracle-5.4 package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi-5.4 package in Ubuntu: Fix Released Status in linux-snapdragon package in Ubuntu: New Bug description: The packages listed above are vulnerable to the CVEs below in at least one Ubuntu release, as stated in the Ubuntu CVE Tracker, except for linux-azure-4.15, linux-dell300x, linux-gcp-4.15 and linux-snapdragon, that are only vulnerable to CVE-2022-23041. Please release fixed packages. Xen released a security advisory on March 10. (I was informed by the security team that it does not track security issues via Launchpad bugs, but in the Ubuntu CVE Tracker. However, the issue is unpatched for over 2.5 months and marked as needed for these combinations of source package and Ubuntu version in the Tracker, and therefore I am filing this bug.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976184/+subscriptions -- Mailing list: https://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 1976184] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1976184 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1976184 Title: Linux PV device frontends vulnerable to attacks by backends Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-aws-5.15 package in Ubuntu: Fix Released Status in linux-aws-5.4 package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure-5.4 package in Ubuntu: Fix Released Status in linux-bluefield package in Ubuntu: Fix Released Status in linux-dell300x package in Ubuntu: New Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gcp-4.15 package in Ubuntu: New Status in linux-gcp-5.4 package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Fix Released Status in linux-gke-5.4 package in Ubuntu: Fix Released Status in linux-gkeop package in Ubuntu: Fix Released Status in linux-gkeop-5.4 package in Ubuntu: Fix Released Status in linux-hwe-5.4 package in Ubuntu: Fix Released Status in linux-ibm package in Ubuntu: Fix Released Status in linux-ibm-5.4 package in Ubuntu: Fix Released Status in linux-intel-iotg-5.15 package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: Won't Fix Status in linux-oracle package in Ubuntu: New Status in linux-oracle-5.4 package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: New Status in linux-raspi-5.4 package in Ubuntu: Fix Released Status in linux-riscv package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Bug description: The packages listed above are vulnerable to the CVEs below in at least one Ubuntu release, as stated in the Ubuntu CVE Tracker, except for linux-azure-4.15, linux-dell300x, linux-gcp-4.15 and linux-snapdragon, that are only vulnerable to CVE-2022-23041. Please release fixed packages. Xen released a security advisory on March 10. (I was informed by the security team that it does not track security issues via Launchpad bugs, but in the Ubuntu CVE Tracker. However, the issue is unpatched for over 2.5 months and marked as needed for these combinations of source package and Ubuntu version in the Tracker, and therefore I am filing this bug.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976184/+subscriptions -- Mailing list: https://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 1976184] Re: Linux PV device frontends vulnerable to attacks by backends
** Changed in: linux-aws-5.4 (Ubuntu) Status: New => Fix Released ** Changed in: linux-ibm-5.4 (Ubuntu) Status: New => Fix Released ** Changed in: linux-ibm (Ubuntu) Status: New => Fix Released ** Changed in: linux-hwe-5.4 (Ubuntu) Status: New => Fix Released ** Changed in: linux-gke-5.4 (Ubuntu) Status: New => Fix Released ** Changed in: linux-gkeop (Ubuntu) Status: New => Fix Released ** Changed in: linux-azure-5.4 (Ubuntu) Status: New => Fix Released ** Changed in: linux-bluefield (Ubuntu) Status: New => Fix Released ** Changed in: linux-raspi-5.4 (Ubuntu) Status: New => Fix Released ** Changed in: linux-oracle-5.4 (Ubuntu) Status: New => Fix Released ** No longer affects: linux-aws-5.13 (Ubuntu) ** No longer affects: linux-oracle-5.13 (Ubuntu) ** No longer affects: linux-gcp-5.13 (Ubuntu) ** No longer affects: linux-azure-5.13 (Ubuntu) ** Also affects: linux-intel-iotg-5.15 (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/1976184 Title: Linux PV device frontends vulnerable to attacks by backends Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-aws-5.15 package in Ubuntu: Fix Released Status in linux-aws-5.4 package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure-5.4 package in Ubuntu: Fix Released Status in linux-bluefield package in Ubuntu: Fix Released Status in linux-dell300x package in Ubuntu: New Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gcp-4.15 package in Ubuntu: New Status in linux-gcp-5.4 package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Fix Released Status in linux-gke-5.4 package in Ubuntu: Fix Released Status in linux-gkeop package in Ubuntu: Fix Released Status in linux-gkeop-5.4 package in Ubuntu: Fix Released Status in linux-hwe-5.4 package in Ubuntu: Fix Released Status in linux-ibm package in Ubuntu: Fix Released Status in linux-ibm-5.4 package in Ubuntu: Fix Released Status in linux-intel-iotg-5.15 package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: Won't Fix Status in linux-oracle package in Ubuntu: New Status in linux-oracle-5.4 package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: New Status in linux-raspi-5.4 package in Ubuntu: Fix Released Status in linux-riscv package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Bug description: The packages listed above are vulnerable to the CVEs below in at least one Ubuntu release, as stated in the Ubuntu CVE Tracker, except for linux-azure-4.15, linux-dell300x, linux-gcp-4.15 and linux-snapdragon, that are only vulnerable to CVE-2022-23041. Please release fixed packages. Xen released a security advisory on March 10. (I was informed by the security team that it does not track security issues via Launchpad bugs, but in the Ubuntu CVE Tracker. However, the issue is unpatched for over 2.5 months and marked as needed for these combinations of source package and Ubuntu version in the Tracker, and therefore I am filing this bug.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976184/+subscriptions -- Mailing list: https://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 1976184] Re: Linux PV device frontends vulnerable to attacks by backends
** Also affects: linux-aws-5.15 (Ubuntu) Importance: Undecided Status: New ** Also 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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1976184 Title: Linux PV device frontends vulnerable to attacks by backends Status in linux package in Ubuntu: New Status in linux-aws package in Ubuntu: New Status in linux-aws-5.13 package in Ubuntu: New Status in linux-aws-5.15 package in Ubuntu: New Status in linux-aws-5.4 package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: New Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure-5.13 package in Ubuntu: New Status in linux-azure-5.4 package in Ubuntu: New Status in linux-bluefield package in Ubuntu: New Status in linux-dell300x package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-gcp-4.15 package in Ubuntu: New Status in linux-gcp-5.13 package in Ubuntu: New Status in linux-gcp-5.4 package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux-gke-5.4 package in Ubuntu: New Status in linux-gkeop package in Ubuntu: New Status in linux-gkeop-5.4 package in Ubuntu: New Status in linux-hwe-5.13 package in Ubuntu: New Status in linux-hwe-5.4 package in Ubuntu: New Status in linux-ibm package in Ubuntu: New Status in linux-ibm-5.4 package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: Won't Fix Status in linux-oracle package in Ubuntu: New Status in linux-oracle-5.13 package in Ubuntu: New Status in linux-oracle-5.4 package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Status in linux-raspi-5.4 package in Ubuntu: New Status in linux-riscv package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Bug description: The packages listed above are vulnerable to the CVEs below in at least one Ubuntu release, as stated in the Ubuntu CVE Tracker, except for linux-azure-4.15, linux-dell300x, linux-gcp-4.15 and linux-snapdragon, that are only vulnerable to CVE-2022-23041. Please release fixed packages. Xen released a security advisory on March 10. (I was informed by the security team that it does not track security issues via Launchpad bugs, but in the Ubuntu CVE Tracker. However, the issue is unpatched for over 2.5 months and marked as needed for these combinations of source package and Ubuntu version in the Tracker, and therefore I am filing this bug.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976184/+subscriptions -- Mailing list: https://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 1988073] [NEW] package linux-firmware 20220329.git681281e4-0ubuntu1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './lib/firmware/ath10k/WCN3990/hw1.0/
Public bug reported: no idea ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: braisoncrece 1211 F pulseaudio /dev/snd/controlC1: braisoncrece 1211 F pulseaudio /dev/snd/controlC2: braisoncrece 1211 F pulseaudio /dev/snd/controlC0: braisoncrece 1211 F pulseaudio CRDA: N/A CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: fail Date: Mon Aug 29 19:18:48 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu3 ErrorMessage: no se pudieron copiar los datos extraídos de './lib/firmware/ath10k/WCN3990/hw1.0/wlanmdsp.mbn' a '/lib/firmware/ath10k/WCN3990/hw1.0/wlanmdsp.mbn.dpkg-new': fin de fichero o de flujo inesperado InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=82c4ebe7-2e57-4b67-a5f5-e1b1c5a31b63 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: linux-firmware Title: package linux-firmware 20220329.git681281e4-0ubuntu1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './lib/firmware/ath10k/WCN3990/hw1.0/wlanmdsp.mbn' a '/lib/firmware/ath10k/WCN3990/hw1.0/wlanmdsp.mbn.dpkg-new': fin de fichero o de flujo inesperado UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F30 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO 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.:bvrF30:bd09/15/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPRO:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS PRO dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/1988073 Title: package linux-firmware 20220329.git681281e4-0ubuntu1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './lib/firmware/ath10k/WCN3990/hw1.0/wlanmdsp.mbn' a '/lib/firmware/ath10k/WCN3990/hw1.0/wlanmdsp.mbn.dpkg-new': fin de fichero o de flujo inesperado Status in linux-firmware package in Ubuntu: New Bug description: no idea ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: braisoncrece 1211 F pulseaudio /dev/snd/controlC1: braisoncrece 1211 F pulseaudio /dev/snd/controlC2: braisoncrece 1211 F pulseaudio /dev/snd/controlC0: braisoncrece 1211 F pulseaudio CRDA: N/A CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: fail Date: Mon Aug 29 19:18:48 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu3 ErrorMessage: no se pudieron copiar los datos extraídos de './lib/firmware/ath10k/WCN3990/hw1.0/wlanmdsp.mbn' a '/lib/firmware/ath10k/WCN3990/hw1.0/wlanmdsp.mbn.dpkg-new': fin de fichero o de flujo inesperado InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=82c4ebe7-2e57-4b67-a5f5-e1b1c5a31b63 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oem-5.17/5.17.0.1016.15)
All autopkgtests for the newly accepted linux-meta-oem-5.17 (5.17.0.1016.15) for jammy have finished running. The following regressions have been reported in tests triggered by the package: dahdi-linux/1:2.11.1~dfsg-1ubuntu11 (amd64) r8168/8.049.02-1ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-oem-5.17 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914881] Re: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245,
** Information type changed from Public to Public Security -- 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/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Status in linux package in Ubuntu: Confirmed Bug description: There is no sound output from the laptop internal speakers when running Ubuntu 20.10. This is a dual-boot system; - Booting Windows first and then rebooting to Ubuntu -> sound works fine - Booting Ubuntu first and then rebooting to Windows -> Windows identifies sound as not enables and runs its troubleshooter to enable it The card seems to be recognised OK (system sound settings report output device as Speaker - Tiger Lake-LP Smart Sound technology Audio Controller. VU meters etc all appear as if sound is playing, but no sound. Headphone socket works perfectly. Similar bug reports for different laptops in the HP x360 series suggest this is a pinning problem and that the extract below from the boot logs may support this. lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 aplay -l List of PLAYBACK Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 extract from journalctl -b kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC245: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:> kernel: snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 kernel: snd_hda_codec_realtek ehdaudio0D0:inputs: kernel: snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1460 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 6 20:48:52 2021 InstallationDate: Installed on 2021-02-04 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1460 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1481 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-04 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=0a15de41-a7a7-4152-a5dc-e7e69f45fccb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A
[Kernel-packages] [Bug 1922910] Re: Unable to deploy HWE kernel with sub-arch set to xgene-uboot
Well, yes and no. xgene-uboot *is* required. But xgene-uboot *is* the generic kernel - it just has a u-boot wrapper prepended. So what I meant by comment #10, is that I wonder should allow xgene-uboot in the same cases where we allow -generic for HWE kernels, such as this code from src/maasserver/utils/osystems.py: if subarch != "generic" and ( (hwe_kernel and validate_kernel_str(hwe_kernel)) or (min_hwe_kernel and validate_kernel_str(min_hwe_kernel)) ): raise ValidationError( "Subarchitecture(%s) must be generic when setting hwe_kernel." % subarch ) ** Changed in: maas Status: Incomplete => 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/1922910 Title: Unable to deploy HWE kernel with sub-arch set to xgene-uboot Status in MAAS: New Status in linux package in Ubuntu: Expired Bug description: When trying to deploy Moonshot nodes, the sub-arch must be set to xgene-uboot for it to be deployed with GA kernel. However, when trying to deploy it with the HWE kernel it will complain that: Subarchitecture(xgene-uboot) must be generic when setting hwe_kernel. [ deleted the bit about how generic/hwe fails, because that is expected. this machine requires xgene-uboot/hwe ] To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1922910/+subscriptions -- Mailing list: https://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 1987996] Re: boot is failing shows error ACPI BIOS error (bug): could not resolve symbol [\_SB.PR00._CPC] I tried reinstalling ubuntu and erase the current files however the ins
Unfortunately I'm unable to access terminal at this point when I boot I can only access the GNU GRUB menu is there any other way I can get those files? ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987996 Title: boot is failing shows error ACPI BIOS error (bug): could not resolve symbol [\_SB.PR00._CPC] I tried reinstalling ubuntu and erase the current files however the installer crashed. Status in linux package in Ubuntu: Confirmed Bug description: I have read this is a kernel issue, however I don't know how to resolve it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.15 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 17:17:31 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987996/+subscriptions -- Mailing list: https://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 1968526] Re: e1000e reports that reset is blocked by ME
I can confirm this on a Dell Precision 3570, and also add that Ethernet stops working (due to this problem?) after a suspend/resume cycle. -- 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/1968526 Title: e1000e reports that reset is blocked by ME Status in linux package in Ubuntu: Confirmed Bug description: Boot into Ubuntu without ethernet connected, do suspend/resume, the e1000e reports that the reset is blocked by ME. e1000e :00:1f.6 enp0s31f6: DPG_EXIT_DONE took 2510 msec. This is a firmware bug e1000e :00:1f.6 enp0s31f6: Reset blocked by ME ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1100 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 11 14:42:55 2022 InstallationDate: Installed on 2022-03-29 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Dell Inc. Precision 3571 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=d8676815-7d4e-4d79-8ba8-66c3cfae6575 ro intel_iommu=on quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.2 dmi.board.name: 0PY010 dmi.board.vendor: Dell Inc. dmi.board.version: D00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.2:bd02/25/2022:br1.1:svnDellInc.:pnPrecision3571:pvr:rvnDellInc.:rn0PY010:rvrD00:cvnDellInc.:ct10:cvr:sku0B10: dmi.product.family: Precision dmi.product.name: Precision 3571 dmi.product.sku: 0B10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968526/+subscriptions -- Mailing list: https://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 1978333] Re: Remove "ata_piix.prefer_ms_hyperv=0" parameter
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1978333 Title: Remove "ata_piix.prefer_ms_hyperv=0" parameter Status in kdump-tools package in Ubuntu: Fix Committed Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: Fix Committed Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: Fix Committed Status in kdump-tools source package in Impish: Invalid Status in makedumpfile source package in Impish: Invalid Status in kdump-tools source package in Jammy: Fix Committed Status in makedumpfile source package in Jammy: Invalid Status in kdump-tools source package in Kinetic: Fix Committed Status in makedumpfile source package in Kinetic: Invalid Bug description: [Impact] Azure VM instances hit I/O error on boot causing kernel crash [Test Plan] Create Ubuntu Marketplace VM on Azure ``` ssh -i .ssh/id_rsa ubuntu@ipaddr ``` Install crash dump utilities (from guide: https://ubuntu.com/server/docs/kernel-crash-dump) apt-get install kdump-tools Say (y) to all questions during install kdump-config show *shows the vm is not yet ready to kdump root@bionic3: kdump-config show * no crashkernel= parameter in the kernel cmdline DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz kdump initrd: /var/lib/kdump/initrd.img current state:Not ready to kdump kexec command: no kexec command recorded Reboot the VM sudo su As root on the VM after reboot: kdump-config show kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x3200 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1086-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #verify kdump is on cat /proc/cmdline ... crashkernel=512M-:192M dmesg | grep -i crash [0.071660] kexec: Reserving the low 1M of memory for crashkernel [0.269823] Reserving 192MB of memory at 640MB for crashkernel (System RAM: 4095MB) cat /proc/sys/kernel/sysrq # make sure this value is greater than 0 #set it to 1 sudo sysctl -w kernel.sysrq=1 the directory of /var/crash should have no crashes yet as well. Outcome with "ata_piix.prefer_ms_hyperv=0" in kexec command: # perform crash sudo su echo c > /proc/sysrq-trigger After a couple of minuties Open new terminal and try to ssh to azure VM, It does not succeed Force a reboot of the VM through the portal or serial console #kdump doesnt work and hangs indefinitely #force reboot VM from Azure console # verify package version of kdump-tool # verify parameter is not listed in the kdump-config show output kdump-config unload kdump-config load kdump-config show kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x3200 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1086-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #trigger another crash echo c > /proc/sysrq-trigger # open new terminal and ssh back into vm cd /var/crash #verify a dump was created linux-image-5.4.0-1086-azure-202208041658.crash [Where Problems Could Occur] This change modifies the debian/rules. The package could fail to build properly if mistyped. [Other] Back-porting a fix from upstream to remove "ata_piix.prefer_ms_hyperv=0" parameter. target series - Bionic, Focal, Jammy upstream patch https://salsa.debian.org/debian/kdump- tools/-/commit/b1bac9396ddbbce3817c34be3161630698e4a503
[Kernel-packages] [Bug 1980730] Re: OVS internal port Hardware Offload implementation is missing in Jammy kernel
Hey Itai, The PR I filed for the feature inclusion above has been approved and will ship with the kernel released in the SRU cycle that just started today. The cycle should be done around 9/19. -Zack -- 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/1980730 Title: OVS internal port Hardware Offload implementation is missing in Jammy kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: In Progress Bug description: Platform: OpenStack Yoga, Ubuntu 22.04 Jammy, Kernel 5.15.0-37-generic When deploying Charmed Openstack deployment with HW Offload over Jammy series, some of the traffic workloads (mainly those related to Floating IP and NAT) will not be properly offloaded. In order to solve it, "OVS internal port offload" feature was introduced and pushed to upstream kernel. These are the main base patches for the feature we call "OVS internal port offload": b16eb3c81fe27978afdb2c111908d4d627a88d99 net/mlx5: Support internal port as decap route device 5e9942721749fc96b9df4b0545474153316c0571 net/mlx5e: Term table handling of internal port rules 166f431ec6beaf472bc2e116a202a127b64779e4 net/mlx5e: Add indirect tc offload of ovs internal port 100ad4e2d75837c9b42f49b3814b4b42ec9ebe46 net/mlx5e: Offload internal port as encap route device 27484f7170edabbda7b53650cd24d38295cffe60 net/mlx5e: Offload tc rules that redirect to ovs internal port dbac71f22954276633e525f958994f84a7bd303f net/mlx5e: Accept action skbedit in the tc actions list 4f4edcc2b84fecec66748ecbb90a84b981ecdaae net/mlx5: E-Switch, Add ovs internal port mapping to metadata support 189ce08ebf876df2b51f625877731055475352df net/mlx5e: Use generic name for the forwarding dev pointer 28e7606fa8f106cdc0355e0548396c037443e063 net/mlx5e: Refactor rx handler of represetor device Please make sure to take as well all patches the came later on top of those base patches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980730/+subscriptions -- Mailing list: https://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 1922910] Re: Unable to deploy HWE kernel with sub-arch set to xgene-uboot
From the comments above, it seems the generic kernel does not work on this machine, and the xgene-uboot is required? ** Changed in: maas Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922910 Title: Unable to deploy HWE kernel with sub-arch set to xgene-uboot Status in MAAS: Incomplete Status in linux package in Ubuntu: Expired Bug description: When trying to deploy Moonshot nodes, the sub-arch must be set to xgene-uboot for it to be deployed with GA kernel. However, when trying to deploy it with the HWE kernel it will complain that: Subarchitecture(xgene-uboot) must be generic when setting hwe_kernel. [ deleted the bit about how generic/hwe fails, because that is expected. this machine requires xgene-uboot/hwe ] To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1922910/+subscriptions -- Mailing list: https://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 1987711] Re: [i915] Ubuntu display get shifted after some time.
Yes I suspect RDP under Wayland is still buggy -- it's very new and hardly anyone knows about it or uses it that I can tell. Since this sounds like a kernel bug you don't really need to stick to Wayland. You can go back to using Xorg. Just make sure your log contains the correct driver: "modeset(0)" and not "intel(0)" As for other ways to possibly solve the shifting problem, I think the next step is to try the latest upstream graphics kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm- tip/2022-08-27/amd64/ But beware that test kernels require Secure Boot is disabled in your BIOS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987711 Title: [i915] Ubuntu display get shifted after some time. Status in linux package in Ubuntu: Incomplete Bug description: It is continuation of this bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1986583 where advised fix was applied. Summay: After ubuntu is turned on, after some time screen gets shifted to side. (and starts to overlap) I setup webcamera to record screen, and video below shows what it looked like. after fix were applied. www.ms.mff.cuni.cz/~krasicei/capture-0231.bug.crop.slow.mp4 (video was cropped, and slowed down 2x) before fix was applied shift looked somehow like this: www.ms.mff.cuni.cz/~krasicei/bug17-50-18-8-2022.c.mp4 (video is also cropped, and slowed down 2x) During shift no one was present on computer. Is there any idea how to enable some more detailed log or something? I probably can pinpoint exact moment in time when shift happened. i tried to read log journalctl, but I found nothing interesting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown Date: Fri Aug 26 02:31:10 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (189 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-08-02 (23 days ago) dmi.bios.date: 10/07/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GSKU0504.V54 dmi.board.asset.tag: Default string dmi.board.name: SKYBAY dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987711/+subscriptions -- Mailing list: https://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 1987711] Re: [i915] Ubuntu display get shifted after some time.
I had a really bad luck making RDP work under wayland (but I need some remote desktop management), so I want to ask, is there some alike adjustment for Xorg? I would like make it work under Xorg, than wayland. Since bug is presented in both cases, i hope it is possible. -- 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/1987711 Title: [i915] Ubuntu display get shifted after some time. Status in linux package in Ubuntu: Incomplete Bug description: It is continuation of this bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1986583 where advised fix was applied. Summay: After ubuntu is turned on, after some time screen gets shifted to side. (and starts to overlap) I setup webcamera to record screen, and video below shows what it looked like. after fix were applied. www.ms.mff.cuni.cz/~krasicei/capture-0231.bug.crop.slow.mp4 (video was cropped, and slowed down 2x) before fix was applied shift looked somehow like this: www.ms.mff.cuni.cz/~krasicei/bug17-50-18-8-2022.c.mp4 (video is also cropped, and slowed down 2x) During shift no one was present on computer. Is there any idea how to enable some more detailed log or something? I probably can pinpoint exact moment in time when shift happened. i tried to read log journalctl, but I found nothing interesting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown Date: Fri Aug 26 02:31:10 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (189 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-08-02 (23 days ago) dmi.bios.date: 10/07/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GSKU0504.V54 dmi.board.asset.tag: Default string dmi.board.name: SKYBAY dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987711/+subscriptions -- Mailing list: https://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 1987869] Re: Remove linux-oem-5.17 from kinetic
According to excuses[1], linux is blocked on nvidia-* drivers, and nvidia-* are blocked on linux-oem-5.17 and linux-iotg[2] - we first need to "unblock" oem-5.17 and iotg if we want oem-22.04 metapackages to promote. 1: https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#nvidia-graphics-drivers-510 2: https://bugs.launchpad.net/ubuntu/+source/linux-restricted- signatures-intel-iotg/+bug/1987870 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1987869 Title: Remove linux-oem-5.17 from kinetic Status in linux-meta-oem-5.17 package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: Triaged Status in linux-restricted-modules-oem-5.17 package in Ubuntu: Triaged Status in linux-restricted-signatures-oem-5.17 package in Ubuntu: Triaged Status in linux-signed-oem-5.17 package in Ubuntu: Triaged Bug description: Remove linux-oem-5.17 from kinetic this kernel should not exist in kinetic-release, as it is jammy-only thing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-5.17/+bug/1987869/+subscriptions -- Mailing list: https://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 1988023] Re: Could not switch uppercase/lowercase by using keyboard of laptop
** Package changed: linux (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Status: Incomplete => 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in systemd package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988023/+subscriptions -- Mailing list: https://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 1988023] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1988023 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in systemd package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988023/+subscriptions -- Mailing list: https://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 1988023] [NEW] Could not switch uppercase/lowercase by using keyboard of laptop
Public bug reported: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. ** Affects: systemd (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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in systemd package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988023/+subscriptions -- Mailing list: https://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 1987232] Re: WARN in trace_event_dyn_put_ref
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987232 Title: WARN in trace_event_dyn_put_ref Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Confirmed Bug description: I have systems that are regularly hitting a WARN in trace_event_dyn_put_ref. The exact message is: WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46 +trace_event_dyn_put_ref+0x15/0x20 With the following stacktrace: perf_trace_init+0x8f/0xd0 perf_tp_event_init+0x1f/0x40 perf_try_init_event+0x4a/0x130 perf_event_alloc+0x497/0xf40 __do_sys_perf_event_open+0x1d4/0xf70 __x64_sys_perf_event_open+0x20/0x30 do_syscall_64+0x5c/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae I've debugged this and worked with upstream to get a fix into Linux. It was recently merged in 6.0-rc2. See here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2=7249921d94ff64f67b733eca0b68853a62032b3d The problem started appearing as soon as our systems picked up the linux-aws-5.15 branch for Focal. (That was 5.15.0-1015-aws, if memory serves). Could you please cherry pick this fix and pull it back to the the linux and linux-aws kernels for Focal? There's test here: https://lore.kernel.org/all/cover.1660347763.git.k...@templeofstupid.com/ that reproduces the problem very reliably for me. With the patch applied, I no longer get the WARNs. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 22 17:32 seq crw-rw 1 root audio 116, 33 Aug 22 17:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 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: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Amazon EC2 c5d.12xlarge Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1015-aws root=PARTUUID=4986e35b-1bd5-45d3-b528-fa2edb861a38 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 ProcVersionSignature: Ubuntu 5.15.0-1015.19~20.04.1-aws 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-1015-aws N/A linux-backports-modules-5.15.0-1015-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.15.0-1015-aws x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 10/16/2017 dmi.bios.release: 1.0 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-03f5d8581c7ad94aa dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:br1.0:svnAmazonEC2:pnc5d.12xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:sku: dmi.product.name: c5d.12xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987232/+subscriptions -- Mailing list: https://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 1976228] Re: [Ubuntu 22.04 LTS]The host OS becomes read-only after the 'rescan-scsi-bus.sh -r' command is executed
Hello Jeff, The reproducible on Dell PowerEdge R630.The test system is initialized system(OS info:Ubuntu 22.04 LTS kernel:5.15.0-33-generic) without any special configiration. -- 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/1976228 Title: [Ubuntu 22.04 LTS]The host OS becomes read-only after the 'rescan- scsi-bus.sh -r' command is executed Status in linux package in Ubuntu: Confirmed Bug description: OS:Ubuntu 22.04 LTS kernel:5.15.0-33-generic host model:Dell PowerEdge R630 issue description: After I mapped luns from array to my host, I ran 'rescan-scsi-bus.sh -r' to scan for luns, my host crashed and became read-only.After the KVM forcibly restarts the host, the host is restored to normal. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 30 08:33 seq crw-rw 1 root audio 116, 33 May 30 08:33 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 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: CRDA: N/A DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-26 (4 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 05/14/2021 dmi.bios.release: 2.13 dmi.bios.version: 2.13.0 dmi.board.name: 02C2CP dmi.board.version: A01 dmi.chassis.type: 23 dmi.modalias: dmi:bvn:bvr2.13.0:bd05/14/2021:br2.13:svn:pn:pvr:rvn:rn02C2CP:rvrA01:cvn:ct23:cvr:skuSKU=NotProvided;ModelName=: dmi.product.sku: SKU=NotProvided;ModelName= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976228/+subscriptions -- Mailing list: https://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 1980829] Re: System freeze after resuming from suspend due to PCI ASPM settings
** Tags added: originate-from-1985043 -- 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/1980829 Title: System freeze after resuming from suspend due to PCI ASPM settings Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: For Jammy/Kinetic SRU [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ So, I created a DMI quirk to make the patches only affects on listed platforms. [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The patches only affects on the listed platforms, and won't affect other platforms. == [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The 2 patches look pretty safe to me, they try to preserve the ASPM state of devices. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980829/+subscriptions -- Mailing list: https://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 1987711] Re: Ubuntu display get shifted after some time.
Thanks. It sounds like the problem is now happening in Wayland sessions. Since essentially the same bug was first reported in Xorg that would make this a kernel bug. Please try adding this line to /etc/environment: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 and then reboot. It will change the way the screen is rendered in Wayland sessions. ** Package changed: xorg-server (Ubuntu) => linux (Ubuntu) ** Summary changed: - Ubuntu display get shifted after some time. + [i915] Ubuntu display get shifted after some time. ** Tags added: i915 -- 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/1987711 Title: [i915] Ubuntu display get shifted after some time. Status in linux package in Ubuntu: Incomplete Bug description: It is continuation of this bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1986583 where advised fix was applied. Summay: After ubuntu is turned on, after some time screen gets shifted to side. (and starts to overlap) I setup webcamera to record screen, and video below shows what it looked like. after fix were applied. www.ms.mff.cuni.cz/~krasicei/capture-0231.bug.crop.slow.mp4 (video was cropped, and slowed down 2x) before fix was applied shift looked somehow like this: www.ms.mff.cuni.cz/~krasicei/bug17-50-18-8-2022.c.mp4 (video is also cropped, and slowed down 2x) During shift no one was present on computer. Is there any idea how to enable some more detailed log or something? I probably can pinpoint exact moment in time when shift happened. i tried to read log journalctl, but I found nothing interesting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown Date: Fri Aug 26 02:31:10 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (189 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-08-02 (23 days ago) dmi.bios.date: 10/07/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GSKU0504.V54 dmi.board.asset.tag: Default string dmi.board.name: SKYBAY dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987711/+subscriptions -- Mailing list: https://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 1987711] [NEW] Ubuntu display get shifted after some time.
You have been subscribed to a public bug: It is continuation of this bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1986583 where advised fix was applied. Summay: After ubuntu is turned on, after some time screen gets shifted to side. (and starts to overlap) I setup webcamera to record screen, and video below shows what it looked like. after fix were applied. www.ms.mff.cuni.cz/~krasicei/capture-0231.bug.crop.slow.mp4 (video was cropped, and slowed down 2x) before fix was applied shift looked somehow like this: www.ms.mff.cuni.cz/~krasicei/bug17-50-18-8-2022.c.mp4 (video is also cropped, and slowed down 2x) During shift no one was present on computer. Is there any idea how to enable some more detailed log or something? I probably can pinpoint exact moment in time when shift happened. i tried to read log journalctl, but I found nothing interesting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown Date: Fri Aug 26 02:31:10 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (189 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-08-02 (23 days ago) dmi.bios.date: 10/07/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GSKU0504.V54 dmi.board.asset.tag: Default string dmi.board.name: SKYBAY dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy ubuntu -- Ubuntu display get shifted after some time. https://bugs.launchpad.net/bugs/1987711 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987134] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver
OK this sounds like an Nvidia kernel driver bug, or some other kernel driver bug. P.S. If you have TLP installed then please remove it as it is known to also cause bugs like this. ** No longer affects: mutter (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu. https://bugs.launchpad.net/bugs/1987134 Title: Black screen after wake from S3 suspend on Nvidia proprietary driver Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: An Nvidia driver upgrade in Ubuntu 20.04 caused waking from S3 suspend to lead to a black screen. Upgrading to Ubuntu 22.04 using latest stable Nvidia driver 515.65.01 did not resolve the issue. There are several Nvidia sleep tickets that at first seem related, but mention dmesg entries that I am not seeing which makes me suspect I have a different issue: * https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1970088 * https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303 Workaround dhenry mentions in 1970088 of disabling the nvidia suspend and hibernate systemd services makes no difference for me. Currrently running Ubuntu 22.04, Nvidia GTX 970 on driver 515.65.01, AMD Ryzen 7 5800X. Here are journalctl excerpts during the reboot process, with and without nvidia systemd suspend services. dmesg and /var/log/kern.log show no errors as are mentioned in the above tickets. With disabled nvidia suspend systemd services: Aug 19 12:42:37 uf-panacea ModemManager[2731]: [sleep-monitor] system is about to suspend Aug 19 12:42:37 uf-panacea NetworkManager[2617]: [1660938157.8491] manager: NetworkManager state> Aug 19 12:42:37 uf-panacea systemd[1]: Reached target Sleep. Aug 19 12:42:37 uf-panacea systemd[1]: Starting Record successful boot for GRUB... Aug 19 12:42:37 uf-panacea systemd[1]: Starting System Suspend... Aug 19 12:42:37 uf-panacea systemd-sleep[13048]: Entering sleep state 'suspend'... Aug 19 12:42:37 uf-panacea systemd[1]: grub-common.service: Deactivated successfully. Aug 19 12:42:37 uf-panacea systemd[1]: Finished Record successful boot for GRUB. With enabled nvidia suspend systemd services: Aug 19 12:12:25 uf-panacea systemd[1]: Starting NVIDIA system suspend actions... Aug 19 12:12:25 uf-panacea suspend[15998]: nvidia-suspend.service Aug 19 12:12:25 uf-panacea logger[15998]: <13>Aug 19 12:12:25 suspend: nvidia-suspend.service Aug 19 12:12:25 uf-panacea systemd[1]: grub-common.service: Deactivated successfully. Aug 19 12:12:25 uf-panacea systemd[1]: Finished Record successful boot for GRUB. Aug 19 12:12:25 uf-panacea systemd[1]: Starting GRUB failed boot detection... Aug 19 12:12:25 uf-panacea systemd[1]: grub-initrd-fallback.service: Deactivated successfully. Aug 19 12:12:25 uf-panacea systemd[1]: Finished GRUB failed boot detection. Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "40" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event1 - Power Button: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "43" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event0 - Power Button: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "44" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event4 - USB Mouse OKLIC: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "45" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event5 - USB Mouse OKLIC Mouse: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "46" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event6 - USB Mouse OKLIC System Control: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "47" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event7 - USB Mouse OKLIC Consumer Control: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "53" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "53" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event11 - Valve Software Steam Controller: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "50" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "50" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event9 - Logitech G305: device removed Aug 19 12:12:25 uf-panacea rtkit-daemon[3286]: Supervising 10 threads of 4 processes of 1 users. Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "51" Aug 19 12:12:25
[Kernel-packages] [Bug 1988018] [NEW] [mlx5] Intermittent VF-LAG activation failure
Public bug reported: During system initialization there is a specific sequence that must be followed to enable the use of hardware offload and VF-LAG. Intermittently one may see that VF-LAG initialization fails: [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: lag map port 1:1 port 2:2 shared_fdb:1 [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_cmd_check:782:(pid 9): CREATE_LAG(0x840) op_mod(0x0) failed, status bad parameter(0x3), syndrome (0x7d49cb) [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_create_lag:248:(pid 9): Failed to create LAG (-22) [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_activate_lag:288:(pid 9): Failed to activate VF LAG Make sure all VFs are unbound prior to VF LAG activation or deactivation This is caused by rebinding the driver prior to the VF lag being ready. A sysfs knob has recently been added to the driver [0] and we should monitor it before attempting to rebind the driver: $ cat /sys/kernel/debug/mlx5/\:08\:00.0/lag/state The kernel feature is available in the upcoming Kinetic 5.19 kernel and we should probably backport it to the Jammy 5.15 kernel. 0: https://github.com/torvalds/linux/commit/7f46a0b7327ae261f9981888708dbca22c283900 ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Committed ** Affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: netplan.io (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Fix Committed ** Affects: netplan.io (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Kinetic) Status: New => Fix Committed ** Also affects: netplan.io (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/1988018 Title: [mlx5] Intermittent VF-LAG activation failure Status in linux package in Ubuntu: Fix Committed Status in netplan.io package in Ubuntu: New Status in linux source package in Jammy: New Status in netplan.io source package in Jammy: New Status in linux source package in Kinetic: Fix Committed Status in netplan.io source package in Kinetic: New Bug description: During system initialization there is a specific sequence that must be followed to enable the use of hardware offload and VF-LAG. Intermittently one may see that VF-LAG initialization fails: [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: lag map port 1:1 port 2:2 shared_fdb:1 [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_cmd_check:782:(pid 9): CREATE_LAG(0x840) op_mod(0x0) failed, status bad parameter(0x3), syndrome (0x7d49cb) [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_create_lag:248:(pid 9): Failed to create LAG (-22) [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_activate_lag:288:(pid 9): Failed to activate VF LAG Make sure all VFs are unbound prior to VF LAG activation or deactivation This is caused by rebinding the driver prior to the VF lag being ready. A sysfs knob has recently been added to the driver [0] and we should monitor it before attempting to rebind the driver: $ cat /sys/kernel/debug/mlx5/\:08\:00.0/lag/state The kernel feature is available in the upcoming Kinetic 5.19 kernel and we should probably backport it to the Jammy 5.15 kernel. 0: https://github.com/torvalds/linux/commit/7f46a0b7327ae261f9981888708dbca22c283900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp