[Kernel-packages] [Bug 1967894] 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 1967894 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/1967894 Title: KVM IPI Virtualization support for SPR Status in linux package in Ubuntu: Incomplete Bug description: IPI virtualization targets to make the processor emulate the write to APIC registers that would send IPIs in virtualized system. VMX provide new VM-execution control and VMCS field to support IPI virtualization which can eliminate APIC-Write VM-exit. The processor sets the bit corresponding to the vector in target vCPU's PIR and may send a notification (IPI) specified by NDST and NV fields in target vCPU's PID. It is similar to what IOMMU engine does when dealing with posted interrupt from devices. IPI Virtualization is approved in SPR/EGS CCB and it is supposed to be enabled in C-step or later (perhaps D-step). Subject: Re: [PATCH v7 8/8] KVM: VMX: enable IPI virtualization https://lore.kernel.org/kvm/54df6da8-ad68-cc75-48db-d18fc8743...@intel.com/ Target Linux 5.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967894/+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 1967998] [NEW] Problems with ports Ubuntu 20.04 5.13.0-39-generic - matherboard Gigabyte GA-Z77X-UD3H
Public bug reported: [1.101901] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20210331/psargs-330) [1.101915] No Local Variables are initialized for Method [_GTF] [1.101917] No Arguments are initialized for method [_GTF] [1.101919] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20210331/psparse-529) [1.101988] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20210331/psargs-330) [1.101998] No Local Variables are initialized for Method [_GTF] [1.102001] No Arguments are initialized for method [_GTF] [1.102004] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20210331/psparse-529) [1.102052] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20210331/psargs-330) [1.102060] No Local Variables are initialized for Method [_GTF] [1.102062] No Arguments are initialized for method [_GTF] [1.102064] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT2._GTF due to previous error (AE_NOT_FOUND) (20210331/psparse-529) [1.102130] ata2.00: ATA-10: ADATA SU800, Q0518BS, max UDMA/133 [1.102133] ata2.00: 500118192 sectors, multi 2: LBA48 NCQ (depth 32), AA [1.102263] ata3.00: ATA-8: WDC WD10EZEX-00RKKA0, 80.00A80, max UDMA/133 [1.102266] ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA [1.102480] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20210331/psargs-330) [1.102492] No Local Variables are initialized for Method [_GTF] [1.102494] No Arguments are initialized for method [_GTF] [1.102496] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20210331/psparse-529) [1.102681] ata2.00: configured for UDMA/133 [1.103019] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20210331/psargs-330) [1.103027] No Local Variables are initialized for Method [_GTF] [1.103028] No Arguments are initialized for method [_GTF] [1.103030] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20210331/psparse-529) [1.103072] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20210331/psargs-330) [1.103082] No Local Variables are initialized for Method [_GTF] [1.103084] No Arguments are initialized for method [_GTF] [1.103086] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT2._GTF due to previous error (AE_NOT_FOUND) (20210331/psparse-529) [1.103125] ata5.00: supports DRM functions and may not be fully accessible [1.103253] ata3.00: configured for UDMA/133 [1.103376] ata6.00: NCQ Send/Recv Log not supported [1.103378] ata6.00: ATA-9: Samsung SSD 840 PRO Series, DXM04B0Q, max UDMA/133 [1.103379] ata6.00: 250069680 sectors, multi 16: LBA48 NCQ (depth 32), AA [1.103594] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20210331/psargs-330) [1.103600] No Local Variables are initialized for Method [_GTF] [1.103601] No Arguments are initialized for method [_GTF] [1.103603] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20210331/psparse-529) [1.103706] ata6.00: NCQ Send/Recv Log not supported [1.103768] ata6.00: configured for UDMA/133 [1.103940] ata5.00: disabling queued TRIM support [1.103941] ata5.00: ATA-11: Samsung SSD 860 EVO 250GB, RVT01B6Q, max UDMA/133 [1.103942] ata5.00: 488397168 sectors, multi 1: LBA48 NCQ (depth 32), AA [1.105189] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [1.105494] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20210331/psargs-330) [1.105518] No Local Variables are initialized for Method [_GTF] [1.105520] No Arguments are initialized for method [_GTF] [1.105523] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20210331/psparse-529) [1.105576] ata1.00: ATA-10: ADATA SU800, R0427ANR, max UDMA/133 [1.105579] ata1.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 32), AA [1.106039] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20210331/psargs-330) [1.106059] No Local Variables are initialized for Method [_GTF] [1.106060] No Arguments are initialized for method [_GTF] [1.106062] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20210331/psparse-529) [1.106225] ata1.00: configured for UDMA/133 [1.106350] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20210331/psargs-330) [1.106358] No Local Va
[Kernel-packages] [Bug 1967986] Re: Fix ADL, WD22TB4, Dual monitors display resolution can't reach 4K 60hz
** Description changed: [Impact] SUT attach WD22TB4 dock, plug in two 4K monitor, the monitor resolution can't reach 4K 60Hz [Fix] Fix maximum DP source rate. - For unstable, because the patch set has been landed since 5.16-rc1 on mainline, - https://patchwork.freedesktop.org/series/93622/ this patch should be taken first, https://lore.kernel.org/intel-gfx/20211026104342.198300-2-ankit.k.nauti...@intel.com/ Then, on U/J/OEM-5.14, apply 3fd6afb623ba) drm/i915/intel_combo_phy: Print I/O voltage info, [Test Case] 1. Connect two 4K external monitor to WD22TB4 2. the monitor resolution can reach 4K 60Hz [Where problems could occur] Low -- 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/1967986 Title: Fix ADL, WD22TB4,Dual monitors display resolution can't reach 4K 60hz Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: New Bug description: [Impact] SUT attach WD22TB4 dock, plug in two 4K monitor, the monitor resolution can't reach 4K 60Hz [Fix] Fix maximum DP source rate. this patch should be taken first, https://lore.kernel.org/intel-gfx/20211026104342.198300-2-ankit.k.nauti...@intel.com/ Then, on U/J/OEM-5.14, apply 3fd6afb623ba) drm/i915/intel_combo_phy: Print I/O voltage info, [Test Case] 1. Connect two 4K external monitor to WD22TB4 2. the monitor resolution can reach 4K 60Hz [Where problems could occur] Low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967986/+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 1967998] Re: Problems with ports Ubuntu 20.04 5.13.0-39-generic - matherboard Gigabyte GA-Z77X-UD3H
** Description changed: - [1.101901] ACPI BIOS Error (bug): Could not resolve symbol - [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20210331/psargs-330) + I have several problems with USB ports after installation of Ubuntu + 20.04. All worked fine on Ubuntu 18.04.Problems: + + usb 1-3: 1:1: cannot get freq at ep 0x81 + 1:0: usb_set_interface failed (-71) + usb 1-3: 1:1: cannot get freq at ep 0x81 + ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20210331/psparse-529) + ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20210331/psparse-529) + + I am using also Kingstone HyperX Cloud II headphones and the device is + detected but microphone is deaf. Maybe the problems are related. + + + Below dmesg full response: + + + [1.101901] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20210331/psargs-330) [1.101915] No Local Variables are initialized for Method [_GTF] [1.101917] No Arguments are initialized for method [_GTF] [1.101919] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20210331/psparse-529) [1.101988] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20210331/psargs-330) [1.101998] No Local Variables are initialized for Method [_GTF] [1.102001] No Arguments are initialized for method [_GTF] [1.102004] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20210331/psparse-529) [1.102052] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20210331/psargs-330) [1.102060] No Local Variables are initialized for Method [_GTF] [1.102062] No Arguments are initialized for method [_GTF] [1.102064] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT2._GTF due to previous error (AE_NOT_FOUND) (20210331/psparse-529) [1.102130] ata2.00: ATA-10: ADATA SU800, Q0518BS, max UDMA/133 [1.102133] ata2.00: 500118192 sectors, multi 2: LBA48 NCQ (depth 32), AA [1.102263] ata3.00: ATA-8: WDC WD10EZEX-00RKKA0, 80.00A80, max UDMA/133 [1.102266] ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA [1.102480] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20210331/psargs-330) [1.102492] No Local Variables are initialized for Method [_GTF] [1.102494] No Arguments are initialized for method [_GTF] [1.102496] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20210331/psparse-529) [1.102681] ata2.00: configured for UDMA/133 [1.103019] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20210331/psargs-330) [1.103027] No Local Variables are initialized for Method [_GTF] [1.103028] No Arguments are initialized for method [_GTF] [1.103030] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20210331/psparse-529) [1.103072] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20210331/psargs-330) [1.103082] No Local Variables are initialized for Method [_GTF] [1.103084] No Arguments are initialized for method [_GTF] [1.103086] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT2._GTF due to previous error (AE_NOT_FOUND) (20210331/psparse-529) [1.103125] ata5.00: supports DRM functions and may not be fully accessible [1.103253] ata3.00: configured for UDMA/133 [1.103376] ata6.00: NCQ Send/Recv Log not supported [1.103378] ata6.00: ATA-9: Samsung SSD 840 PRO Series, DXM04B0Q, max UDMA/133 [1.103379] ata6.00: 250069680 sectors, multi 16: LBA48 NCQ (depth 32), AA [1.103594] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20210331/psargs-330) [1.103600] No Local Variables are initialized for Method [_GTF] [1.103601] No Arguments are initialized for method [_GTF] [1.103603] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20210331/psparse-529) [1.103706] ata6.00: NCQ Send/Recv Log not supported [1.103768] ata6.00: configured for UDMA/133 [1.103940] ata5.00: disabling queued TRIM support [1.103941] ata5.00: ATA-11: Samsung SSD 860 EVO 250GB, RVT01B6Q, max UDMA/133 [1.103942] ata5.00: 488397168 sectors, multi 1: LBA48 NCQ (depth 32), AA [1.105189] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [1.105494] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20210331/psargs-330) [1.105518] No Local Variables are initialized for Method [_GTF]
[Kernel-packages] [Bug 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
** Changed in: linux-firmware (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Focal) Status: New => In Progress -- 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/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+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 1967961] Re: jammy failed to deploy to Hisilicon D06 with MAAS
Tried to deploy d06-3 with jammy again today. I was dropped to the root username after the ephemeral environment installation reboot[1]. See the attachment "d06-3-maas-220406-01.log" for the full console log. [1] [ OK ] Finished Availability of block devices. root@d06-3:~# root@d06-3:~# ** Attachment added: "d06-3-maas-220406-01.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967961/+attachment/5577537/+files/d06-3-maas-220406-01.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967961 Title: jammy failed to deploy to Hisilicon D06 with MAAS Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab) Image: Jammy = Steps to Reproduce = 1. Deploy the system with MAAS webUI 2. Wait until everything is ready = Expected Results = After the system is installed at the ephemeral stage of MAAS installation and restarts, the system boots and ready to login and use. = Actual Results = The system is never ready to be at the login prompt stage, and MAAS deployment timeouts. The console log of the system (see the attachment d06-1.log for the full log): [ 366.412548] INFO: task kworker/31:1:624 blocked for more than 241 seconds. [ 366.412566] Tainted: G L5.15.0-25-generic #25-Ubuntu [ 366.412577] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 366.412826] INFO: task kworker/u196:1:1107 blocked for more than 120 seconds. [ 366.412833] Tainted: G L5.15.0-25-generic #25-Ubuntu [ 366.412840] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ** 2167 printk messages dropped ** [ 387.007501] watchdog: BUG: soft lockup - CPU#9 stuck for 272s! [swapper/9:0] [ 387.037902] watchdog: BUG: soft lockup - CPU#7 stuck for 272s! [swapper/7:0] [ 411.004684] watchdog: BUG: soft lockup - CPU#9 stuck for 294s! [swapper/9:0] [ 411.025400] watchdog: BUG: soft lockup - CPU#7 stuck for 294s! [swapper/7:0] [ 435.005493] watchdog: BUG: soft lockup - CPU#7 stuck for 317s! [swapper/7:0] [ 435.019191] watchdog: BUG: soft lockup - CPU#9 stuck for 317s! [swapper/9:0] [*** [ 455.581303] systemd[1]: sysinit.target: Unable to break cycle starting with sysinit.target/start [**] (6 of 7) A start job is running for…d Directories (6min 4s / no limit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967961/+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 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
** Description changed: + SRU template for linux-firmware + [Impact] + we have a Dell ADL laptop which has sdw audio, but there is no camera + and no internal digital mic in this machine, the current asoc driver + can't work on this machine, the speaker and headset couldn't work. + + [Fix] + Backport a tplg file which is specific to this mahcine + + [Test] + Install the patched linux-firmware and boot the latest oem-5.14 kernel + on the machine, check dmesg, it loads the correct tplg, and + test speaker and headset, all work well. + + [Where problems could occur] + This SRU is adding a new tplg file, it has no chance to introduce + a regression. + + SRU template for linux [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. -- 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/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: SRU template for linux-firmware [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current asoc driver can't work on this machine, the speaker and headset couldn't work. [Fix] Backport a tplg file which is specific to this mahcine [Test] Install the patched linux-firmware and boot the latest oem-5.14 kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] This SRU is adding a new tplg file, it has no chance to introduce a regression. SRU template for linux [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+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 1967986] Re: Fix ADL, WD22TB4, Dual monitors display resolution can't reach 4K 60hz
** Description changed: [Impact] SUT attach WD22TB4 dock, plug in two 4K monitor, the monitor resolution can't reach 4K 60Hz [Fix] Fix maximum DP source rate. this patch should be taken first, - https://lore.kernel.org/intel-gfx/20211026104342.198300-2-ankit.k.nauti...@intel.com/ + 73867c8709) drm/i915/display: Remove check for low voltage sku for max dp source rate Then, on U/J/OEM-5.14, apply 3fd6afb623ba) drm/i915/intel_combo_phy: Print I/O voltage info, [Test Case] 1. Connect two 4K external monitor to WD22TB4 2. the monitor resolution can reach 4K 60Hz [Where problems could occur] Low -- 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/1967986 Title: Fix ADL, WD22TB4,Dual monitors display resolution can't reach 4K 60hz Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: New Bug description: [Impact] SUT attach WD22TB4 dock, plug in two 4K monitor, the monitor resolution can't reach 4K 60Hz [Fix] Fix maximum DP source rate. this patch should be taken first, 73867c8709) drm/i915/display: Remove check for low voltage sku for max dp source rate Then, on U/J/OEM-5.14, apply 3fd6afb623ba) drm/i915/intel_combo_phy: Print I/O voltage info, [Test Case] 1. Connect two 4K external monitor to WD22TB4 2. the monitor resolution can reach 4K 60Hz [Where problems could occur] Low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967986/+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 1967562] Re: jammy beta (220330) arm iso kernel panic on Ampere Mt. Jade during pxe boot
Redo with the same iso but different downloading url: http://cdimage.ubuntu.com/releases/22.04/beta/ubuntu-22.04-beta-live- server-arm64.iso I can still reproduce the issue. The grub entry looks good (no duplicate ---)[1]. The attachment bizzy-maas-220406-01.log is the corresponding console log. setparams 'Ubuntu Server' set gfxpayload=keep linux/casper/vmlinuz quiet root=/dev/ram0 ramdisk_size=150 ip=dhcp url=http://cdimage.ubuntu.com/releases/22.04/beta/ubuntu-22.04-beta-live-server-arm64.iso autoinstall "ds=nocloud-net;s=http://10.229.56.0/"; --- initrd/casper/initrd ** Attachment added: "bizzy-maas-220406-01.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+attachment/5577564/+files/bizzy-maas-220406-01.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic on Ampere Mt. Jade during pxe boot Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Incomplete Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+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 1968013] [NEW] Boot stall on non-azure systems due to linux-cloud-tools-common
Public bug reported: I see a boot stall on a normal qemu/libvirt based KVM guest using an almost fresh cloud image a stall on boot: While live on the console I see: [ OK ] Reached target System Time Set. [ OK ] Finished Load AppArmor pro…s managed internally by snapd. [* ] A start job is running for /sys/dev…misc/vmbus!hv_kvp (41s / 1min 30s) Afterwards in the console I see: [ TIME ] Timed out waiting for device es/virtual/misc/vmbus!hv_kvp. [DEPEND] Dependency failed for Hyper-V KVP Protocol Daemon. Note: Found after wondering why my system isn't available for ssh after start In the journal this bonus minute can be seen for example here: Apr 06 05:48:42 login-jammy systemd[1]: systemd-fsckd.service: Deactivated successfully. Apr 06 05:49:41 login-jammy systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start timed out. Apr 06 05:49:41 login-jammy systemd[1]: Timed out waiting for device /sys/devices/virtual/misc/vmbus!hv_kvp. Apr 06 05:49:41 login-jammy systemd[1]: Dependency failed for Hyper-V KVP Protocol Daemon. Apr 06 05:49:41 login-jammy systemd[1]: hv-kvp-daemon.service: Job hv-kvp-daemon.service/start failed with result 'dependency'. Apr 06 05:49:41 login-jammy systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start failed with result 'timeout'. Apr 06 05:49:41 login-jammy systemd[1]: Starting Initial cloud-init job (pre-networking)... This behavior is from: /usr/lib/systemd/system/hv-kvp-daemon.service $ dpkg -S hv-kvp-daemon.service linux-cloud-tools-common: /lib/systemd/system/hv-kvp-daemon.service It has the expected "should not matter elsewhere": ConditionVirtualization=microsoft ConditionKernelCommandLine=!snapd_recovery_mode But it also has: BindsTo=sys-devices-virtual-misc-vmbus\x21hv_kvp.device Right now it seems the latter overrules the former (in an obvious non microsoft environment it does run and wait) and thereby makes it stall boot until it gives up on it. This is on my system since I wanted to do performance checks for something completely else and is part of linux-cloud-tools-common which I had installed for perf. Repro: 1. get jammy system 2. install linux-cloud-tools-common 3. reboot and see the delay I'd expect this stalls boot everywhere except when on azure, but I still need to try that to confirm it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-cloud-tools-common 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 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 6 05:48 seq crw-rw 1 root audio 116, 33 Apr 6 05:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu80 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: unknown Date: Wed Apr 6 09:04:02 2022 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) PackageArchitecture: all PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=16484d8a-587c-4c41-9201-e6079b9c6938 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.14.0-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-impish dmi.modalias: dmi:bvnSeaBIOS:bvr1.14.0-2:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-impish:cvnQEMU:ct1:cvrpc-q35-impish:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-impish dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy uec-images ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968013 Title: Boot stall on non-azure systems due to linux-cloud-tools-common Status in linux package in Ubuntu: Confirmed Bug description: I see a boot stall on a normal qemu/libvirt based
[Kernel-packages] [Bug 1968013] Re: Boot stall on non-azure systems due to linux-cloud-tools-common
On a fresh AWS instance I already see it stalling on package install, I do not even need to reboot :-/ ubuntu@ip-172-31-16-15:~$ sudo apt install linux-cloud-tools-common Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: linux-cloud-tools-common 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. Need to get 72.4 kB of archives. After this operation, 342 kB of additional disk space will be used. Get:1 http://eu-south-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 linux-cloud-tools-common all 5.15.0-25.25 [72.4 kB] Fetched 72.4 kB in 0s (632 kB/s) Selecting previously unselected package linux-cloud-tools-common. (Reading database ... 63666 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_5.15.0-25.25_all.deb ... Unpacking linux-cloud-tools-common (5.15.0-25.25) ... Setting up linux-cloud-tools-common (5.15.0-25.25) ... Created symlink /etc/systemd/system/multi-user.target.wants/hv-fcopy-daemon.service → /lib/systemd/system/hv-fcopy-daemon.service. Created symlink /etc/systemd/system/multi-user.target.wants/hv-kvp-daemon.service → /lib/systemd/system/hv-kvp-daemon.service. Created symlink /etc/systemd/system/multi-user.target.wants/hv-vss-daemon.service → /lib/systemd/system/hv-vss-daemon.service. Progress: [ 60%] [###..] < here it is hanging ~1 minute > Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. Processing triggers for man-db (2.10.2-1) ... Scanning processes... Scanning linux images... It is interesting that it even hits: Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. That is the try to start it from: /var/lib/dpkg/info/linux-cloud-tools-common.postinst :63 Which has: deb-systemd-invoke $_dh_action 'hv-fcopy-daemon.service' 'hv-kvp-daemon.service' 'hv-vss-daemon.service' >/dev/null || true In Journal we can see the exact same time-out Apr 06 09:12:36 ip-172-31-16-15 systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start timed out. Apr 06 09:12:36 ip-172-31-16-15 systemd[1]: Timed out waiting for device /sys/devices/virtual/misc/vmbus!hv_kvp. Apr 06 09:12:36 ip-172-31-16-15 systemd[1]: Dependency failed for Hyper-V KVP Protocol Daemon. Apr 06 09:12:36 ip-172-31-16-15 systemd[1]: hv-kvp-daemon.service: Job hv-kvp-daemon.service/start failed with result 'dependency'. Apr 06 09:12:36 ip-172-31-16-15 systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start failed with result 'timeout'. ** Summary changed: - Boot stall on non-azure systems due to linux-cloud-tools-common + Boot and package install/update stalled due to linux-cloud-tools-common (hv-kvp-daemon.service) -- 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/1968013 Title: Boot and package install/update stalled due to linux-cloud-tools- common (hv-kvp-daemon.service) Status in linux package in Ubuntu: Confirmed Bug description: I see a boot stall on a normal qemu/libvirt based KVM guest using an almost fresh cloud image a stall on boot: While live on the console I see: [ OK ] Reached target System Time Set. [ OK ] Finished Load AppArmor pro…s managed internally by snapd. [* ] A start job is running for /sys/dev…misc/vmbus!hv_kvp (41s / 1min 30s) Afterwards in the console I see: [ TIME ] Timed out waiting for device es/virtual/misc/vmbus!hv_kvp. [DEPEND] Dependency failed for Hyper-V KVP Protocol Daemon. Note: Found after wondering why my system isn't available for ssh after start In the journal this bonus minute can be seen for example here: Apr 06 05:48:42 login-jammy systemd[1]: systemd-fsckd.service: Deactivated successfully. Apr 06 05:49:41 login-jammy systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start timed out. Apr 06 05:49:41 login-jammy systemd[1]: Timed out waiting for device /sys/devices/virtual/misc/vmbus!hv_kvp. Apr 06 05:49:41 login-jammy systemd[1]: Dependency failed for Hyper-V KVP Protocol Daemon. Apr 06 05:49:41 login-jammy systemd[1]: hv-kvp-daemon.service: Job hv-kvp-daemon.service/start failed with result 'dependency'. Apr 06 05:49:41 login-jammy systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start failed with result 'timeout'. Apr 06 0
[Kernel-packages] [Bug 1968013] Re: Boot and package install/update stalled due to linux-cloud-tools-common (hv-kvp-daemon.service)
For easier debugging this can be reproduced on any affected system (Tried KVM and EC2) by just running: $ sudo systemctl start hv-kvp-daemon.service ^^ This will stall while one would assume it should quick-exit due to the ConditionVirtualization not being met. A full cycle (90 second stall) of this start-try in the journal will look like: Apr 06 09:17:01 ip-172-31-16-15 sudo[2290]: ubuntu : TTY=pts/1 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/systemctl start hv-kvp-daemon.service Apr 06 09:17:01 ip-172-31-16-15 sudo[2290]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1000) Apr 06 09:17:01 ip-172-31-16-15 CRON[2294]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Apr 06 09:17:01 ip-172-31-16-15 CRON[2295]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 06 09:17:01 ip-172-31-16-15 CRON[2294]: pam_unix(cron:session): session closed for user root Apr 06 09:18:31 ip-172-31-16-15 systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start timed out. Apr 06 09:18:31 ip-172-31-16-15 systemd[1]: Timed out waiting for device /sys/devices/virtual/misc/vmbus!hv_kvp. Apr 06 09:18:31 ip-172-31-16-15 sudo[2290]: pam_unix(sudo:session): session closed for user root Apr 06 09:18:31 ip-172-31-16-15 systemd[1]: Dependency failed for Hyper-V KVP Protocol Daemon. Apr 06 09:18:31 ip-172-31-16-15 systemd[1]: hv-kvp-daemon.service: Job hv-kvp-daemon.service/start failed with result 'dependency'. Apr 06 09:18:31 ip-172-31-16-15 systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start failed with result 'timeout'. -- 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/1968013 Title: Boot and package install/update stalled due to linux-cloud-tools- common (hv-kvp-daemon.service) Status in linux package in Ubuntu: Confirmed Bug description: I see a boot stall on a normal qemu/libvirt based KVM guest using an almost fresh cloud image a stall on boot: While live on the console I see: [ OK ] Reached target System Time Set. [ OK ] Finished Load AppArmor pro…s managed internally by snapd. [* ] A start job is running for /sys/dev…misc/vmbus!hv_kvp (41s / 1min 30s) Afterwards in the console I see: [ TIME ] Timed out waiting for device es/virtual/misc/vmbus!hv_kvp. [DEPEND] Dependency failed for Hyper-V KVP Protocol Daemon. Note: Found after wondering why my system isn't available for ssh after start In the journal this bonus minute can be seen for example here: Apr 06 05:48:42 login-jammy systemd[1]: systemd-fsckd.service: Deactivated successfully. Apr 06 05:49:41 login-jammy systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start timed out. Apr 06 05:49:41 login-jammy systemd[1]: Timed out waiting for device /sys/devices/virtual/misc/vmbus!hv_kvp. Apr 06 05:49:41 login-jammy systemd[1]: Dependency failed for Hyper-V KVP Protocol Daemon. Apr 06 05:49:41 login-jammy systemd[1]: hv-kvp-daemon.service: Job hv-kvp-daemon.service/start failed with result 'dependency'. Apr 06 05:49:41 login-jammy systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start failed with result 'timeout'. Apr 06 05:49:41 login-jammy systemd[1]: Starting Initial cloud-init job (pre-networking)... This behavior is from: /usr/lib/systemd/system/hv-kvp-daemon.service $ dpkg -S hv-kvp-daemon.service linux-cloud-tools-common: /lib/systemd/system/hv-kvp-daemon.service It has the expected "should not matter elsewhere": ConditionVirtualization=microsoft ConditionKernelCommandLine=!snapd_recovery_mode But it also has: BindsTo=sys-devices-virtual-misc-vmbus\x21hv_kvp.device Right now it seems the latter overrules the former (in an obvious non microsoft environment it does run and wait) and thereby makes it stall boot until it gives up on it. This is on my system since I wanted to do performance checks for something completely else and is part of linux-cloud-tools-common which I had installed for perf. Repro: 1. get jammy system 2. install linux-cloud-tools-common 3. reboot and see the delay I'd expect this stalls boot everywhere except when on azure, but I still need to try that to confirm it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-cloud-tools-common 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 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 6 05:48 seq crw-rw 1 root audio 116, 33 Apr 6 05:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0u
[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso kernel panic on Ampere Mt. Jade during pxe boot
log snippet from the attachment "bizzy-maas-220406-01.log" of comment#8 [1.354637] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu [1.362195] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26 [1.374876] Call trace: [1.377310] dump_backtrace+0x0/0x1ec [1.380968] show_stack+0x24/0x30 [1.384272] dump_stack_lvl+0x68/0x84 [1.387929] dump_stack+0x18/0x34 [1.391232] panic+0x18c/0x39c [1.394275] mount_block_root+0x160/0x210 [1.398281] mount_root+0x12c/0x14c [1.401757] prepare_namespace+0x140/0x1a0 [1.405842] kernel_init_freeable+0x1c8/0x214 [1.410187] kernel_init+0x30/0x160 [1.413667] ret_from_fork+0x10/0x20 [1.417235] SMP: stopping secondary CPUs [1.421957] Kernel Offset: 0x34a8864c from 0x8800 [1.428038] PHYS_OFFSET: 0x8000 [1.431514] CPU features: 0x85c1,a3302e42 [1.435859] Memory Limit: none [1.438905] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]--- -- 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/1967562 Title: jammy beta (220330) arm iso kernel panic on Ampere Mt. Jade during pxe boot Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Incomplete Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+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 1968013] Re: Boot and package install/update stalled due to linux-cloud-tools-common (hv-kvp-daemon.service)
** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968013 Title: Boot and package install/update stalled due to linux-cloud-tools- common (hv-kvp-daemon.service) Status in linux package in Ubuntu: Confirmed Bug description: I see a boot stall on a normal qemu/libvirt based KVM guest using an almost fresh cloud image a stall on boot: While live on the console I see: [ OK ] Reached target System Time Set. [ OK ] Finished Load AppArmor pro…s managed internally by snapd. [* ] A start job is running for /sys/dev…misc/vmbus!hv_kvp (41s / 1min 30s) Afterwards in the console I see: [ TIME ] Timed out waiting for device es/virtual/misc/vmbus!hv_kvp. [DEPEND] Dependency failed for Hyper-V KVP Protocol Daemon. Note: Found after wondering why my system isn't available for ssh after start In the journal this bonus minute can be seen for example here: Apr 06 05:48:42 login-jammy systemd[1]: systemd-fsckd.service: Deactivated successfully. Apr 06 05:49:41 login-jammy systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start timed out. Apr 06 05:49:41 login-jammy systemd[1]: Timed out waiting for device /sys/devices/virtual/misc/vmbus!hv_kvp. Apr 06 05:49:41 login-jammy systemd[1]: Dependency failed for Hyper-V KVP Protocol Daemon. Apr 06 05:49:41 login-jammy systemd[1]: hv-kvp-daemon.service: Job hv-kvp-daemon.service/start failed with result 'dependency'. Apr 06 05:49:41 login-jammy systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start failed with result 'timeout'. Apr 06 05:49:41 login-jammy systemd[1]: Starting Initial cloud-init job (pre-networking)... This behavior is from: /usr/lib/systemd/system/hv-kvp-daemon.service $ dpkg -S hv-kvp-daemon.service linux-cloud-tools-common: /lib/systemd/system/hv-kvp-daemon.service It has the expected "should not matter elsewhere": ConditionVirtualization=microsoft ConditionKernelCommandLine=!snapd_recovery_mode But it also has: BindsTo=sys-devices-virtual-misc-vmbus\x21hv_kvp.device Right now it seems the latter overrules the former (in an obvious non microsoft environment it does run and wait) and thereby makes it stall boot until it gives up on it. This is on my system since I wanted to do performance checks for something completely else and is part of linux-cloud-tools-common which I had installed for perf. Repro: 1. get jammy system 2. install linux-cloud-tools-common 3. reboot and see the delay I'd expect this stalls boot everywhere except when on azure, but I still need to try that to confirm it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-cloud-tools-common 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 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 6 05:48 seq crw-rw 1 root audio 116, 33 Apr 6 05:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu80 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: unknown Date: Wed Apr 6 09:04:02 2022 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) PackageArchitecture: all PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=16484d8a-587c-4c41-9201-e6079b9c6938 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.14.0-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-impish dmi.modalias: dmi:bvnSeaBIOS:bvr1.14.0-2:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-impish:cvnQEMU:ct1:cvrpc-q35-impish:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-impish dmi.s
[Kernel-packages] [Bug 1967957] Re: jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06 with virtual CD
Redo with d06 (d06-1). This time we have the log of kernel trace. See
d06-1-cd-220406-01.log for the full console log.
[ 652.568681] pstate: 004000c9 (nzcv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 652.575630] pc : irq_work_queue_on+0xa4/0xb0
[ 652.579888] lr : rcu_implicit_dynticks_qs+0x1b8/0x350
[ 652.584928] sp : 8b223c50
[ 652.588229] x29: 8b223c50 x28: 8aa30e00 x27:
[ 652.595354] x26: 003f7fb44025 x25: 0019 x24: 8aa30e00
[ 652.602478] x23: 803f759d9000 x22: 8a906000 x21: 8a16b025
[ 652.609602] x20: x19: 003f7fb43f00 x18: 0102
[ 652.616727] x17: 3330643830383030 x16: 30303820 x15: 3a20307820303030
[ 652.623850] x14: 8a94b760 x13: 8a94b1e8 x12: 0002
[ 652.630974] x11: x10: 0b50 x9 : 882158e4
[ 652.638097] x8 : 002084b42b30 x7 : x6 : 003f7fb44058
[ 652.645221] x5 : x4 : x3 : 003f7fb43140
[ 652.652344] x2 : x1 : 8a90da28 x0 : 0004
[ 652.659469] Call trace:
[ 652.661903] irq_work_queue_on+0xa4/0xb0
[ 652.665813] rcu_implicit_dynticks_qs+0x1b8/0x350
[ 652.670504] force_qs_rnp+0x184/0x340
[ 652.674154] rcu_gp_fqs_loop+0x224/0x394
[ 652.678064] rcu_gp_kthread+0x120/0x164
[ 652.681888] kthread+0x114/0x120
[ 652.685105] ret_from_fork+0x10/0x20
[ 652.688669] ---[ end trace da56ec070b45e740 ]---
** Attachment added: "d06-1-cd-220406-01.log"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1967957/+attachment/5577595/+files/d06-1-cd-220406-01.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967957
Title:
jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06
with virtual CD
Status in linux package in Ubuntu:
Incomplete
Status in subiquity package in Ubuntu:
New
Bug description:
= Description =
Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab)
Image: Jammy Beta (220330)
= Steps to Reproduce =
1. Boot the system with the iso from d06's virtual CD of BMC
2. Launch the kernel via the default grub entry
= Expected Results =
The kernel and image are loaded via the virtual CD, and then subiquity is
launched.
= Actual Results =
After the grub stage, when loading the kernel we see (check d06-3.log for the
full log details):
[ 1149.949752] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1149.949796] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1180.107036] watchdog: BUG: soft lockup - CPU#6 stuck for 26s!
[swapper/6:0]^M
[ 1204.107091] watchdog: BUG: soft lockup - CPU#6 stuck for 48s!
[swapper/6:0]^M
[ 1213.237720] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:^M
[ 1213.243639] rcu: 15-: (2 GPs behind) idle=87d/1/0x4004
softirq=854/855 fqs=7501 ^M
[ 1213.441723] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1213.441764] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1228.108161] watchdog: BUG: soft lockup - CPU#6 stuck for 70s!
[swapper/6:0]^M
[ 1252.106613] watchdog: BUG: soft lockup - CPU#6 stuck for 93s!
[swapper/6:0]^M
[ 1276.106317] watchdog: BUG: soft lockup - CPU#6 stuck for 115s!
[swapper/6:0]^M
[ 1300.106639] watchdog: BUG: soft lockup - CPU#6 stuck for 137s!
[swapper/6:0]^M
[ 1324.114455] watchdog: BUG: soft lockup - CPU#6 stuck for 160s!
[swapper/6:0]^M
[ 1330.178015] INFO: task (imesyncd):2464 blocked for more than 120 seconds.^M
[ 1330.184819] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.184836] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185017] INFO: task unshare:2502 blocked for more than 120 seconds.^M
[ 1330.185027] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.185037] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185325] INFO: task unshare:2507 blocked for more than 120 seconds.^M
** 1238 printk messages dropped **^M
[ 1333.632679] systemd[1]: Failed to start Journal Service.^M
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967957/+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 1967957] Re: jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06 with virtual CD
Next from my side: there are new daily build. I may try them as well.
--
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/1967957
Title:
jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06
with virtual CD
Status in linux package in Ubuntu:
Incomplete
Status in subiquity package in Ubuntu:
New
Bug description:
= Description =
Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab)
Image: Jammy Beta (220330)
= Steps to Reproduce =
1. Boot the system with the iso from d06's virtual CD of BMC
2. Launch the kernel via the default grub entry
= Expected Results =
The kernel and image are loaded via the virtual CD, and then subiquity is
launched.
= Actual Results =
After the grub stage, when loading the kernel we see (check d06-3.log for the
full log details):
[ 1149.949752] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1149.949796] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1180.107036] watchdog: BUG: soft lockup - CPU#6 stuck for 26s!
[swapper/6:0]^M
[ 1204.107091] watchdog: BUG: soft lockup - CPU#6 stuck for 48s!
[swapper/6:0]^M
[ 1213.237720] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:^M
[ 1213.243639] rcu: 15-: (2 GPs behind) idle=87d/1/0x4004
softirq=854/855 fqs=7501 ^M
[ 1213.441723] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1213.441764] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1228.108161] watchdog: BUG: soft lockup - CPU#6 stuck for 70s!
[swapper/6:0]^M
[ 1252.106613] watchdog: BUG: soft lockup - CPU#6 stuck for 93s!
[swapper/6:0]^M
[ 1276.106317] watchdog: BUG: soft lockup - CPU#6 stuck for 115s!
[swapper/6:0]^M
[ 1300.106639] watchdog: BUG: soft lockup - CPU#6 stuck for 137s!
[swapper/6:0]^M
[ 1324.114455] watchdog: BUG: soft lockup - CPU#6 stuck for 160s!
[swapper/6:0]^M
[ 1330.178015] INFO: task (imesyncd):2464 blocked for more than 120 seconds.^M
[ 1330.184819] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.184836] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185017] INFO: task unshare:2502 blocked for more than 120 seconds.^M
[ 1330.185027] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.185037] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185325] INFO: task unshare:2507 blocked for more than 120 seconds.^M
** 1238 printk messages dropped **^M
[ 1333.632679] systemd[1]: Failed to start Journal Service.^M
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967957/+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 1967961] Re: jammy failed to deploy to Hisilicon D06 with MAAS
d06-3-maas-220406-02.log is the console log for maas deployment timeout with d06-3. ** Attachment added: "d06-3-maas-220406-02.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967961/+attachment/5577604/+files/d06-3-maas-220406-02.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967961 Title: jammy failed to deploy to Hisilicon D06 with MAAS Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab) Image: Jammy = Steps to Reproduce = 1. Deploy the system with MAAS webUI 2. Wait until everything is ready = Expected Results = After the system is installed at the ephemeral stage of MAAS installation and restarts, the system boots and ready to login and use. = Actual Results = The system is never ready to be at the login prompt stage, and MAAS deployment timeouts. The console log of the system (see the attachment d06-1.log for the full log): [ 366.412548] INFO: task kworker/31:1:624 blocked for more than 241 seconds. [ 366.412566] Tainted: G L5.15.0-25-generic #25-Ubuntu [ 366.412577] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 366.412826] INFO: task kworker/u196:1:1107 blocked for more than 120 seconds. [ 366.412833] Tainted: G L5.15.0-25-generic #25-Ubuntu [ 366.412840] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ** 2167 printk messages dropped ** [ 387.007501] watchdog: BUG: soft lockup - CPU#9 stuck for 272s! [swapper/9:0] [ 387.037902] watchdog: BUG: soft lockup - CPU#7 stuck for 272s! [swapper/7:0] [ 411.004684] watchdog: BUG: soft lockup - CPU#9 stuck for 294s! [swapper/9:0] [ 411.025400] watchdog: BUG: soft lockup - CPU#7 stuck for 294s! [swapper/7:0] [ 435.005493] watchdog: BUG: soft lockup - CPU#7 stuck for 317s! [swapper/7:0] [ 435.019191] watchdog: BUG: soft lockup - CPU#9 stuck for 317s! [swapper/9:0] [*** [ 455.581303] systemd[1]: sysinit.target: Unable to break cycle starting with sysinit.target/start [**] (6 of 7) A start job is running for…d Directories (6min 4s / no limit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967961/+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 1959547] Comment bridged from LTC Bugzilla
--- Comment From fre...@de.ibm.com 2022-04-06 05:34 EDT--- Hm, I am not an expert in this -proposed thing... I am currently using an Ubuntu 20.04 and added these lines to /etc/apt/source.list: deb http://us.ports.ubuntu.com/ubuntu-ports/ focal-proposed main deb http://us.ports.ubuntu.com/ubuntu-ports/ jammy-proposed main then I run an apt update and then I do a apt list --upgradable | grep proposed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. dpkg-dev/focal-proposed 1.19.7ubuntu3.1 all [upgradable from: 1.19.7ubuntu3] dpkg/focal-proposed 1.19.7ubuntu3.1 s390x [upgradable from: 1.19.7ubuntu3] kmod/focal-proposed 27-1ubuntu2.1 s390x [upgradable from: 27-1ubuntu2] libc-bin/focal-proposed 2.31-0ubuntu9.8 s390x [upgradable from: 2.31-0ubuntu9.2] libc-dev-bin/focal-proposed 2.31-0ubuntu9.8 s390x [upgradable from: 2.31-0ubuntu9.2] libc6-dev/focal-proposed 2.31-0ubuntu9.8 s390x [upgradable from: 2.31-0ubuntu9.2] libc6/focal-proposed 2.31-0ubuntu9.8 s390x [upgradable from: 2.31-0ubuntu9.2] libcurl4/focal-proposed 7.68.0-1ubuntu2.8 s390x [upgradable from: 7.68.0-1ubuntu2.7] libdpkg-perl/focal-proposed 1.19.7ubuntu3.1 all [upgradable from: 1.19.7ubuntu3] libgstreamer1.0-0/focal-proposed 1.16.3-0ubuntu1 s390x [upgradable from: 1.16.2-2] libjpeg8/jammy-proposed 8c-2ubuntu9 s390x [upgradable from: 8c-2ubuntu8] libkmod2/focal-proposed 27-1ubuntu2.1 s390x [upgradable from: 27-1ubuntu2] liblzma5/jammy-proposed 5.2.5-2build2 s390x [upgradable from: 5.2.4-1ubuntu1] libnss-systemd/focal-proposed 245.4-4ubuntu3.16 s390x [upgradable from: 245.4-4ubuntu3.15] libpam-systemd/focal-proposed 245.4-4ubuntu3.16 s390x [upgradable from: 245.4-4ubuntu3.15] libsystemd0/focal-proposed 245.4-4ubuntu3.16 s390x [upgradable from: 245.4-4ubuntu3.15] libudev1/focal-proposed 245.4-4ubuntu3.16 s390x [upgradable from: 245.4-4ubuntu3.15] libx11-6/jammy-proposed 2:1.7.5-1 s390x [upgradable from: 2:1.6.9-2ubuntu1.2] libx11-data/jammy-proposed 2:1.7.5-1 all [upgradable from: 2:1.6.9-2ubuntu1.2] libzstd1/jammy-proposed 1.4.8+dfsg-3build1 s390x [upgradable from: 1.4.4+dfsg-3ubuntu0.1] linux-generic/focal-proposed 5.4.0.108.112 s390x [upgradable from: 5.4.0.97.101] linux-headers-generic/focal-proposed 5.4.0.108.112 s390x [upgradable from: 5.4.0.97.101] linux-image-generic/focal-proposed 5.4.0.108.112 s390x [upgradable from: 5.4.0.97.101] linux-libc-dev/focal-proposed 5.4.0-108.122 s390x [upgradable from: 5.4.0-94.106] linux-source-5.4.0/focal-proposed 5.4.0-108.122 all [upgradable from: 5.4.0-94.106] locales/focal-proposed 2.31-0ubuntu9.8 all [upgradable from: 2.31-0ubuntu9.2] login/focal-proposed 1:4.8.1-1ubuntu5.20.04.2 s390x [upgradable from: 1:4.8.1-1ubuntu5.20.04.1] ltrace/jammy-proposed 0.7.3-6.1ubuntu5 s390x [upgradable from: 0.7.3-6.1ubuntu1] passwd/focal-proposed 1:4.8.1-1ubuntu5.20.04.2 s390x [upgradable from: 1:4.8.1-1ubuntu5.20.04.1] python3-gdbm/jammy-proposed 3.10.4-0ubuntu1 s390x [upgradable from: 3.8.10-0ubuntu1~20.04] systemd-sysv/focal-proposed 245.4-4ubuntu3.16 s390x [upgradable from: 245.4-4ubuntu3.15] systemd-timesyncd/focal-proposed 245.4-4ubuntu3.16 s390x [upgradable from: 245.4-4ubuntu3.15] systemd/focal-proposed 245.4-4ubuntu3.16 s390x [upgradable from: 245.4-4ubuntu3.15] udev/focal-proposed 245.4-4ubuntu3.16 s390x [upgradable from: 245.4-4ubuntu3.15] xz-utils/jammy-proposed 5.2.5-2build2 s390x [upgradable from: 5.2.4-1ubuntu1] and there is no such thing like a kernel package 5.15 to see. So what else do I need to do to fetch this kernel package ? -- 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/1959547 Title: [22.04 FEAT] zcrypt DD: Exploitation Support of new IBM Z Crypto Hardware (kernel part) Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: zcrypt DD: Exploitation Support of new IBM Z Crypto Hardware - kernel part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959547/+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 1967961] Re: jammy failed to deploy to Hisilicon D06 with MAAS
In our lab, a production level taishan2280v2 (scobee) and x6000 (saenger) could be deployed by MAAS successfully. -- 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/1967961 Title: jammy failed to deploy to Hisilicon D06 with MAAS Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab) Image: Jammy = Steps to Reproduce = 1. Deploy the system with MAAS webUI 2. Wait until everything is ready = Expected Results = After the system is installed at the ephemeral stage of MAAS installation and restarts, the system boots and ready to login and use. = Actual Results = The system is never ready to be at the login prompt stage, and MAAS deployment timeouts. The console log of the system (see the attachment d06-1.log for the full log): [ 366.412548] INFO: task kworker/31:1:624 blocked for more than 241 seconds. [ 366.412566] Tainted: G L5.15.0-25-generic #25-Ubuntu [ 366.412577] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 366.412826] INFO: task kworker/u196:1:1107 blocked for more than 120 seconds. [ 366.412833] Tainted: G L5.15.0-25-generic #25-Ubuntu [ 366.412840] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ** 2167 printk messages dropped ** [ 387.007501] watchdog: BUG: soft lockup - CPU#9 stuck for 272s! [swapper/9:0] [ 387.037902] watchdog: BUG: soft lockup - CPU#7 stuck for 272s! [swapper/7:0] [ 411.004684] watchdog: BUG: soft lockup - CPU#9 stuck for 294s! [swapper/9:0] [ 411.025400] watchdog: BUG: soft lockup - CPU#7 stuck for 294s! [swapper/7:0] [ 435.005493] watchdog: BUG: soft lockup - CPU#7 stuck for 317s! [swapper/7:0] [ 435.019191] watchdog: BUG: soft lockup - CPU#9 stuck for 317s! [swapper/9:0] [*** [ 455.581303] systemd[1]: sysinit.target: Unable to break cycle starting with sysinit.target/start [**] (6 of 7) A start job is running for…d Directories (6min 4s / no limit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967961/+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 1968027] [NEW] shiftfs breaks paths in /proc/*/maps
Public bug reported: When enabling shiftfs for LXD we get incorrect paths in /proc/*/maps within a container: root@anbox0:~# cat /proc/self/maps 55930e60-55930e608000 r-xp 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930e807000-55930e808000 r--p 7000 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930e808000-55930e809000 rw-p 8000 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930fd3c000-55930fd5d000 rw-p 00:00 0 [heap] 7fe736be2000-7fe736dc9000 r-xp 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736dc9000-7fe736fc9000 ---p 001e7000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fc9000-7fe736fcd000 r--p 001e7000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fcd000-7fe736fcf000 rw-p 001eb000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fcf000-7fe736fd3000 rw-p 00:00 0 7fe736fd3000-7fe736ffc000 r-xp 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so 7fe7371ba000-7fe7371de000 rw-p 00:00 0 7fe7371fc000-7fe7371fd000 r--p 00029000 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so 7fe7371fd000-7fe7371fe000 rw-p 0002a000 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so 7fe7371fe000-7fe7371ff000 rw-p 00:00 0 7ffcd50a-7ffcd50c1000 rw-p 00:00 0 [stack] 7ffcd51d2000-7ffcd51d6000 r--p 00:00 0 [vvar] 7ffcd51d6000-7ffcd51d8000 r-xp 00:00 0 [vdso] ff60-ff601000 --xp 00:00 0 [vsyscall] When shiftfs is disabled the paths look all correct and are relative to the root of the container root@anbox0:~# cat /proc/self/maps 557aaa20-557aaa208000 r-xp 00:48 14509 /bin/cat 557aaa407000-557aaa408000 r--p 7000 00:48 14509 /bin/cat 557aaa408000-557aaa409000 rw-p 8000 00:48 14509 /bin/cat 557aabaa5000-557aabac6000 rw-p 00:00 0 [heap] 7f4820526000-7f482070d000 r-xp 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f482070d000-7f482090d000 ---p 001e7000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f482090d000-7f4820911000 r--p 001e7000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f4820911000-7f4820913000 rw-p 001eb000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f4820913000-7f4820917000 rw-p 00:00 0 7f4820917000-7f482094 r-xp 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so 7f4820afe000-7f4820b22000 rw-p 00:00 0 7f4820b4-7f4820b41000 r--p 00029000 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so 7f4820b41000-7f4820b42000 rw-p 0002a000 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so 7f4820b42000-7f4820b43000 rw-p 00:00 0 7ffd12ead000-7ffd12ece000 rw-p 00:00 0 [stack] 7ffd12fd8000-7ffd12fdc000 r--p 00:00 0 [vvar] 7ffd12fdc000-7ffd12fde000 r-xp 00:00 0 [vdso] ff60-ff601000 --xp 00:00 0 [vsyscall] To reproduce: 1. Use Ubuntu 20.04 or newer inluding shiftfs 2. Install LXD (4.0.x is good enough) and enable shiftfs support $ snap install lxd $ snap set lxd shiftfs.enable=true $ snap restart lxd $ lxd init --auto 3. Start a container and check /proc/self/maps $ lxc launch ubuntu:f test0 $ lxc exec test0 -- cat /proc/self/maps 4. Turn shiftfs back off $ snap set lxd shiftfs.enable=false $ snap restart lxd 5. Check /proc/self/maps again inside the container $ lxc exec test0 -- cat /proc/self/maps ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968027 Title: shiftfs breaks paths in /proc/*/maps Status in linux package in Ubuntu: New Bug description: When enabling shiftfs for L
[Kernel-packages] [Bug 1934293] Re: Add l2tp.sh in net from ubuntu_kernel_selftests back
** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1934293 Title: Add l2tp.sh in net from ubuntu_kernel_selftests back Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Groovy: Invalid Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.13 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] We have this test disabled intentionally in the past because of the lack of commit 27d53323664c54 "l2tp: remove skb_dst_set() from l2tp_xmit_skb()" in our kernels. The way we disable it is to override the executable bit with our autotest-client-tests suite [1], but this makes the test suite complain about script is not executable. Henceforth we further disable it by removing it from the Makefile in the patch "UBUNTU: SAUCE: selftests/net -- disable timeout" Now with commit 27d53323664c54 landed and l2tp.sh test re-enabled in our test suite [2], we still need to revert that SAUCE patch to get it tested. [1] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=05d7eebf32c6872ebce6c9e5275b1ff9d91ecd16 [2] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=7dea7776ce431e5a1c550dc73b1d9ac0ba49698d [Fix] Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test" This test only exists in our tree since Focal. [Test] Run the net test suite in kselftest with patched source tree: sudo make -C linux/tools/testing/selftests TARGETS=net run_tests The l2tp.sh test will be executed. [Where problems could occur] This is only for testing tools, however if commit 27d53323664c54 "l2tp: remove skb_dst_set() from l2tp_xmit_skb()" didn't land properly we might crash our testing node like in bug 1854968. Also, we might see new failures caused by this test in the test report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934293/+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 1968027] 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 1968027 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/1968027 Title: shiftfs breaks paths in /proc/*/maps Status in linux package in Ubuntu: Incomplete Bug description: When enabling shiftfs for LXD we get incorrect paths in /proc/*/maps within a container: root@anbox0:~# cat /proc/self/maps 55930e60-55930e608000 r-xp 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930e807000-55930e808000 r--p 7000 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930e808000-55930e809000 rw-p 8000 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930fd3c000-55930fd5d000 rw-p 00:00 0 [heap] 7fe736be2000-7fe736dc9000 r-xp 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736dc9000-7fe736fc9000 ---p 001e7000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fc9000-7fe736fcd000 r--p 001e7000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fcd000-7fe736fcf000 rw-p 001eb000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fcf000-7fe736fd3000 rw-p 00:00 0 7fe736fd3000-7fe736ffc000 r-xp 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so 7fe7371ba000-7fe7371de000 rw-p 00:00 0 7fe7371fc000-7fe7371fd000 r--p 00029000 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so 7fe7371fd000-7fe7371fe000 rw-p 0002a000 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so 7fe7371fe000-7fe7371ff000 rw-p 00:00 0 7ffcd50a-7ffcd50c1000 rw-p 00:00 0 [stack] 7ffcd51d2000-7ffcd51d6000 r--p 00:00 0 [vvar] 7ffcd51d6000-7ffcd51d8000 r-xp 00:00 0 [vdso] ff60-ff601000 --xp 00:00 0 [vsyscall] When shiftfs is disabled the paths look all correct and are relative to the root of the container root@anbox0:~# cat /proc/self/maps 557aaa20-557aaa208000 r-xp 00:48 14509 /bin/cat 557aaa407000-557aaa408000 r--p 7000 00:48 14509 /bin/cat 557aaa408000-557aaa409000 rw-p 8000 00:48 14509 /bin/cat 557aabaa5000-557aabac6000 rw-p 00:00 0 [heap] 7f4820526000-7f482070d000 r-xp 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f482070d000-7f482090d000 ---p 001e7000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f482090d000-7f4820911000 r--p 001e7000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f4820911000-7f4820913000 rw-p 001eb000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f4820913000-7f4820917000 rw-p 00:00 0 7f4820917000-7f482094 r-xp 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so 7f4820afe000-7f4820b22000 rw-p 00:00 0 7f4820b4-7f4820b41000 r--p 00029000 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so 7f4820b41000-7f4820b42000 rw-p 0002a000 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so 7f4820b42000-7f4820b43000 rw-p 00:00 0 7ffd12ead000-7ffd12ece000 rw-p 00:00 0 [stack] 7ffd12fd8000-7ffd12fdc000 r--p 00:00 0 [vvar] 7ffd12fdc000-7ffd12fde000 r-xp 00:00 0 [vdso] ff60-fff
[Kernel-packages] [Bug 1967957] Re: jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06 with virtual CD
Additional info: in our lab, a taishan2280v2 could install the 220330
iso. (tested by ike)
--
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/1967957
Title:
jammy beta (220330) live server arm64 iso failed to boot Hisilicon D06
with virtual CD
Status in linux package in Ubuntu:
Incomplete
Status in subiquity package in Ubuntu:
New
Bug description:
= Description =
Platforms: Hisilicon D06 (d06-1 and d06-3 in our lab)
Image: Jammy Beta (220330)
= Steps to Reproduce =
1. Boot the system with the iso from d06's virtual CD of BMC
2. Launch the kernel via the default grub entry
= Expected Results =
The kernel and image are loaded via the virtual CD, and then subiquity is
launched.
= Actual Results =
After the grub stage, when loading the kernel we see (check d06-3.log for the
full log details):
[ 1149.949752] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1149.949796] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1180.107036] watchdog: BUG: soft lockup - CPU#6 stuck for 26s!
[swapper/6:0]^M
[ 1204.107091] watchdog: BUG: soft lockup - CPU#6 stuck for 48s!
[swapper/6:0]^M
[ 1213.237720] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:^M
[ 1213.243639] rcu: 15-: (2 GPs behind) idle=87d/1/0x4004
softirq=854/855 fqs=7501 ^M
[ 1213.441723] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks:
{^M
[ 1213.441764] rcu: blocking rcu_node structures (internal RCU debug):^M
[ 1228.108161] watchdog: BUG: soft lockup - CPU#6 stuck for 70s!
[swapper/6:0]^M
[ 1252.106613] watchdog: BUG: soft lockup - CPU#6 stuck for 93s!
[swapper/6:0]^M
[ 1276.106317] watchdog: BUG: soft lockup - CPU#6 stuck for 115s!
[swapper/6:0]^M
[ 1300.106639] watchdog: BUG: soft lockup - CPU#6 stuck for 137s!
[swapper/6:0]^M
[ 1324.114455] watchdog: BUG: soft lockup - CPU#6 stuck for 160s!
[swapper/6:0]^M
[ 1330.178015] INFO: task (imesyncd):2464 blocked for more than 120 seconds.^M
[ 1330.184819] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.184836] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185017] INFO: task unshare:2502 blocked for more than 120 seconds.^M
[ 1330.185027] Tainted: G L5.15.0-23-generic
#23-Ubuntu^M
[ 1330.185037] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.^M
[ 1330.185325] INFO: task unshare:2507 blocked for more than 120 seconds.^M
** 1238 printk messages dropped **^M
[ 1333.632679] systemd[1]: Failed to start Journal Service.^M
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967957/+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 1966819] Re: System will not suspend using HWE kernel.
[ removing comment, wrong kernel version. I'm seeing issue on .107, not .105 ] -- 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/1966819 Title: System will not suspend using HWE kernel. Status in linux package in Ubuntu: Confirmed Bug description: I am unable to suspend with the HWE kernel with my hp elitebook 745 g3. It works without issue on the 5.4.0-105 kernel. I'm not really sure how to troubleshoot these issue either but am interested in helping to solve the problem. I can take direction and am not entirely useless. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-105-generic 5.4.0-105.119 ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174 Uname: Linux 5.4.0-105-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sterling 1510 F pulseaudio /dev/snd/controlC0: sterling 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Mar 28 19:56:33 2022 InstallationDate: Installed on 2022-03-27 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: HP HP EliteBook 745 G3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-105-generic root=UUID=74ef52ad-94d0-4c4f-a7aa-c2f4df7128ad ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-105-generic N/A linux-backports-modules-5.4.0-105-generic N/A linux-firmware 1.187.29 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2020 dmi.bios.vendor: HP dmi.bios.version: N73 Ver. 01.51 dmi.board.name: 807E dmi.board.vendor: HP dmi.board.version: KBC Version 75.71 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN73Ver.01.51:bd10/17/2020:svnHP:pnHPEliteBook745G3:pvr:rvnHP:rn807E:rvrKBCVersion75.71:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 745 G3 dmi.product.sku: N1S71AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966819/+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 1968027] Re: shiftfs breaks paths in /proc/*/maps
Attaching logs fails when `apport-collect 1968027` wants to authorized with my LP with an "Not allowed error". ** Description changed: When enabling shiftfs for LXD we get incorrect paths in /proc/*/maps within a container: root@anbox0:~# cat /proc/self/maps 55930e60-55930e608000 r-xp 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930e807000-55930e808000 r--p 7000 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930e808000-55930e809000 rw-p 8000 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930fd3c000-55930fd5d000 rw-p 00:00 0 [heap] 7fe736be2000-7fe736dc9000 r-xp 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736dc9000-7fe736fc9000 ---p 001e7000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fc9000-7fe736fcd000 r--p 001e7000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fcd000-7fe736fcf000 rw-p 001eb000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so - 7fe736fcf000-7fe736fd3000 rw-p 00:00 0 + 7fe736fcf000-7fe736fd3000 rw-p 00:00 0 7fe736fd3000-7fe736ffc000 r-xp 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so - 7fe7371ba000-7fe7371de000 rw-p 00:00 0 + 7fe7371ba000-7fe7371de000 rw-p 00:00 0 7fe7371fc000-7fe7371fd000 r--p 00029000 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so 7fe7371fd000-7fe7371fe000 rw-p 0002a000 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so - 7fe7371fe000-7fe7371ff000 rw-p 00:00 0 + 7fe7371fe000-7fe7371ff000 rw-p 00:00 0 7ffcd50a-7ffcd50c1000 rw-p 00:00 0 [stack] 7ffcd51d2000-7ffcd51d6000 r--p 00:00 0 [vvar] 7ffcd51d6000-7ffcd51d8000 r-xp 00:00 0 [vdso] ff60-ff601000 --xp 00:00 0 [vsyscall] When shiftfs is disabled the paths look all correct and are relative to the root of the container root@anbox0:~# cat /proc/self/maps 557aaa20-557aaa208000 r-xp 00:48 14509 /bin/cat 557aaa407000-557aaa408000 r--p 7000 00:48 14509 /bin/cat 557aaa408000-557aaa409000 rw-p 8000 00:48 14509 /bin/cat 557aabaa5000-557aabac6000 rw-p 00:00 0 [heap] 7f4820526000-7f482070d000 r-xp 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f482070d000-7f482090d000 ---p 001e7000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f482090d000-7f4820911000 r--p 001e7000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f4820911000-7f4820913000 rw-p 001eb000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so - 7f4820913000-7f4820917000 rw-p 00:00 0 + 7f4820913000-7f4820917000 rw-p 00:00 0 7f4820917000-7f482094 r-xp 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so - 7f4820afe000-7f4820b22000 rw-p 00:00 0 + 7f4820afe000-7f4820b22000 rw-p 00:00 0 7f4820b4-7f4820b41000 r--p 00029000 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so 7f4820b41000-7f4820b42000 rw-p 0002a000 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so - 7f4820b42000-7f4820b43000 rw-p 00:00 0 + 7f4820b42000-7f4820b43000 rw-p 00:00 0 7ffd12ead000-7ffd12ece000 rw-p 00:00 0 [stack] 7ffd12fd8000-7ffd12fdc000 r--p 00:00 0 [vvar] 7ffd12fdc000-7ffd12fde000 r-xp 00:00 0 [vdso] ff60-ff601000 --xp 00:00 0 [vsyscall] - To reproduce: 1. Use Ubuntu 20.04 or newer inluding shiftfs 2. Install LXD (4.0.x is good enough) and enable shiftfs support $ snap install lxd $ snap set lxd shiftfs.enable=true $ snap restart lxd $ lxd init --auto 3. Start a container and check /proc/self/maps $ lxc launch ubuntu:f test0 $ lxc exec test0 -- cat /proc/self/maps 4. Tu
[Kernel-packages] [Bug 1966499] Re: Recent 5.13 kernel has broken KVM support
I managed to reproduce this with the hyperv_stimer test in kvm-unit- tests with Impish 5.13.0-39, with the identical output spamming in dmesg. And I can reproduce this with 5.13.0-40 [ 921.874608] [ cut here ] [ 921.874609] WARNING: CPU: 13 PID: 6997 at arch/x86/kvm/vmx/vmx.c:6336 vmx_sync_pir_to_irr+0x9e/0xc0 [kvm_intel] [ 921.874613] ? xfer_to_guest_mode_work+0xe2/0x110 [ 921.874616] Modules linked in: vhost_net vhost vhost_iotlb tap xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables nfnetlink bridge stp llc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm joydev input_leds ioatdma rapl intel_cstate efi_pstore ipmi_si mei_me mei mac_hid acpi_pad [ 921.874616] vcpu_run+0x4d/0x220 [kvm] [ 921.874635] acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid mgag200 i2c_algo_bit drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul sysfillrect sysimgblt ghash_clmulni_intel fb_sys_fops ixgbe cec aesni_intel rc_core crypto_simd xfrm_algo cryptd drm ahci dca i2c_i801 xhci_pci mdio libahci i2c_smbus lpc_ich xhci_pci_renesas wmi [ 921.874664] CPU: 13 PID: 6997 Comm: qemu-system-x86 Tainted: GW I 5.13.0-39-generic #44-Ubuntu [ 921.874665] Hardware name: Intel Corporation S2600WTT/S2600WTT, BIOS SE5C610.86B.01.01.1008.031920151331 03/19/2015 [ 921.874651] kvm_arch_vcpu_ioctl_run+0xc5/0x4f0 [kvm] [ 921.874666] RIP: 0010:vmx_sync_pir_to_irr+0x9e/0xc0 [kvm_intel] [ 921.874671] Code: e8 47 f5 18 00 8b 93 00 03 00 00 89 45 ec 83 e2 20 85 d2 74 dc 48 8b 55 f0 65 48 2b 14 25 28 00 00 00 75 1d 48 8b 5d f8 c9 c3 <0f> 0b eb 87 f0 80 4b 39 40 8b 93 00 03 00 00 8b 45 ec 83 e2 20 eb [ 921.874673] RSP: 0018:ae4d8d107c98 EFLAGS: 00010046 [ 921.874674] RAX: RBX: 99c552942640 RCX: 99c5043a72f0 [ 921.874675] RDX: 99c552942640 RSI: 0001 RDI: 99c552942640 [ 921.874676] RBP: ae4d8d107cb0 R08: 99c86f6a7140 R09: 00027100 [ 921.874677] R10: 4228 R11: 000a R12: 99c552942640 [ 921.874678] R13: R14: ae4d8d1a63e0 R15: 99c552942640 [ 921.874679] FS: 7f6ae9be7640() GS:99c86f68() knlGS: [ 921.874680] CS: 0010 DS: ES: CR0: 80050033 [ 921.874681] CR2: CR3: 00010b8a6006 CR4: 001726e0 [ 921.874683] Call Trace: [ 921.874684] [ 921.874684] kvm_vcpu_ioctl+0x243/0x5e0 [kvm] [ 921.874685] vcpu_enter_guest+0x383/0xf50 [kvm] [ 921.874720] ? xfer_to_guest_mode_work+0xe2/0x110 [ 921.874709] ? kvm_vm_ioctl+0x364/0x730 [kvm] [ 921.874738] ? __fget_files+0x86/0xc0 [ 921.874723] vcpu_run+0x4d/0x220 [kvm] [ 921.874742] __x64_sys_ioctl+0x91/0xc0 [ 921.874744] do_syscall_64+0x61/0xb0 [ 921.874747] ? fput+0x13/0x20 [ 921.874749] ? exit_to_user_mode_prepare+0x37/0xb0 [ 921.874751] ? syscall_exit_to_user_mode+0x27/0x50 [ 921.874752] ? do_syscall_64+0x6e/0xb0 [ 921.874755] ? syscall_exit_to_user_mode+0x27/0x50 [ 921.874756] ? do_syscall_64+0x6e/0xb0 [ 921.874759] ? do_syscall_64+0x6e/0xb0 [ 921.874761] ? do_syscall_64+0x6e/0xb0 [ 921.874764] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 921.874766] RIP: 0033:0x7f6aebce1a2b [ 921.874767] Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 f3 0f 00 f7 d8 64 89 01 48 [ 921.874769] RSP: 002b:7f6ae8ffe3f8 EFLAGS: 0246 ORIG_RAX: 0010 [ 921.874771] RAX: ffda RBX: ae80 RCX: 7f6aebce1a2b [ 921.874772] RDX: RSI: ae80 RDI: 000c [ 921.874774] RBP: 557d3b429b90 R08: 557d3a4ebff0 R09: [ 921.874758] kvm_arch_vcpu_ioctl_run+0xc5/0x4f0 [kvm] [ 921.874776] R10: 0001 R11: 0246 R12: [ 921.874777] R13: 0001 R14: 3000 R15: [ 921.874779] [ 921.874780] ---[ end trace 5b722d71a78069b1 ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966499 Title: Recent 5.13 kernel has broken KVM support Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: Upgrading to 5.13.0-37 or 5.13.0-39 immediately crashes my production servers as they hit: https://lore.kernel.org/all/f1ea22d
[Kernel-packages] [Bug 1959547] Re: [22.04 FEAT] zcrypt DD: Exploitation Support of new IBM Z Crypto Hardware (kernel part)
Hi Harald, well, this is an Ubuntu 22.04 feature (like the Launchpad ticket title indicated), hence need to be used/tested on a Ubuntu 22.04 codename 'jammy' system. (You may upgrade your 20.04 / focal system directly to 22.04 / jammy using 'do-release-upgrade -d' - '-d' because jammy is still in development). Once on a 22.04 / jammy system, things are relatively straight forward - let me go into the details: First of all check what's available in the (jammy) archives, in case of this tickets, it's about the kernel (package called 'linux-generic'): $ rmadison --arch=s390x linux-generic | grep $(lsb_release -cs) linux-generic | 5.15.0.25.27 | jammy | s390x Well, this tells us that there is only one kernel available, and that one is in jammy(-release) and there is no kernel in jammy-proposed right now. Means the kernel is already rolled out and you don't need -proposed anymore. So you can go with the kernel that you get by default if running jammy/22.04. [ If there is another kernel in -proposed for testing, things look like in this mockup: linux-generic | 5.15.0.25.27 | jammy | s390x linux-generic | 5.15.0.26.30 | jammy-proposed | s390x ] ___ Anyway, just for the reason of completeness, here are the steps needed in case a kernel from -proposed should be installed and tested: 1) make sure your system is at the latest level: sudo apt -y -q update && sudo apt -y -q full-upgrade 2) activate '-proposed' with: sudo add-apt-repository -y "deb http://us.ports.ubuntu.com/ubuntu-ports/ $(lsb_release -sc)-proposed main universe" (and update the package index with 'sudo apt -y -q update' if not already triggered automatically) 3) now check for the available versions that can be installed: $ apt-cache policy linux-generic linux-generic: Installed: 5.15.0.25.27 Candidate: 5.15.0.26.30 Version table: ... And the version table shows you where the kernels are coming from (either main, proposed, updates, or security). [Btw. ignore the right-most digit, since it's just the build/meta digit. If there is a request to test 5.15.0-25.25, it usually points to the kernel source package, and the binary kernel is (in this case) 5.15.0.25.27. So it's save to ignore '27'.] 4) update the kernel by either 'installing' the latest one that is available, like: sudo apt install linux-generic or explicitly install a specific version, like: sudo apt install linux-generic=5.15.0.26.30 5) don't forget to reboot afterwards to activate the newly installed kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959547 Title: [22.04 FEAT] zcrypt DD: Exploitation Support of new IBM Z Crypto Hardware (kernel part) Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: zcrypt DD: Exploitation Support of new IBM Z Crypto Hardware - kernel part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959547/+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 1965241] Re: Include DPC Fixes in Ubuntu 22.04 and 20.04
** Also affects: dellserver 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/1965241 Title: Include DPC Fixes in Ubuntu 22.04 and 20.04 Status in dellserver: New Status in linux package in Ubuntu: In Progress Bug description: SRU Justification: Impact: Recovery from DownPort Containment events fail and the NVMe endpoint is not accessible in some scenarios. Fix: These are some of the DPC fixes which help in handling some of the failure cases of DownPort Containment events. Upstream kernel patches to be included into Ubuntu 22.04 and into Ubuntu 20.04.5: Already in Jammy as of Ubuntu-5.15.0-1.1 PCI/portdrv: Enable Bandwidth Notification only if port supports it https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6&id=00823dcbdd415c868390feaca16f0265101efab4 Not yet pulled PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6&id=ea401499e943c307e6d44af6c2b4e068643e7884 Test Case: To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1965241/+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 1968034] [NEW] Ubuntu 22.04 Feature master tracker: Boot from NVMe over TCP
Private bug reported: This is a master feature tracker to track the bits of Boot from NVMe over TCP feature. Feature includes: 1. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626 Update kernel, Add pkgs - libnvme and nvme-stas. 2. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948636 Include libnvme pkg in jammy 3. https://bugs.launchpad.net/ubuntu/+source/dasbus/+bug/1948644 Include python3-dasbus in jammy 4. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625 Include and update nvme-stas pkg 5. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948627 6. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948630 Update dracut 7. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948631 Update efibootmgr 8. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948634 Update subiquity to detect and install os into nvme/tcp lun. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private -- 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/1968034 Title: Ubuntu 22.04 Feature master tracker: Boot from NVMe over TCP Status in linux package in Ubuntu: New Bug description: This is a master feature tracker to track the bits of Boot from NVMe over TCP feature. Feature includes: 1. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626 Update kernel, Add pkgs - libnvme and nvme-stas. 2. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948636 Include libnvme pkg in jammy 3. https://bugs.launchpad.net/ubuntu/+source/dasbus/+bug/1948644 Include python3-dasbus in jammy 4. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625 Include and update nvme-stas pkg 5. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948627 6. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948630 Update dracut 7. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948631 Update efibootmgr 8. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948634 Update subiquity to detect and install os into nvme/tcp lun. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968034/+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 1967901] Re: [qxl] Xorg fails to start with "Screen(s) found, but none have a usable configuration."
this is caused by a build issue, it doesn't detect qxl_drm.h which then means the driver doesn't have support for KMS ** Changed in: xorg-server (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/1967901 Title: [qxl] Xorg fails to start with "Screen(s) found, but none have a usable configuration." Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xserver-xorg-video-qxl package in Ubuntu: New Bug description: Ubuntu Desktop Jammy 20220405 It fails to boot to the live session in virt-manager and gnome-boxes. ubiquity-dm starts fine but the live session does. The graphical session keeps dying. If I switch from QXL to Virtio then it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967901/+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 1958494] Re: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking
Seems fixed in linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958494 Title: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: After screen was blanked (meta-L; lid closed) it wakes up with an erratic pattern, it can't recover from (except power off, power on). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 07:41:10 2022 InstallationDate: Installed on 2021-09-29 (112 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+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 1958494] Re: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking
Good. I just install kernel 5.14.21 one month ago and all works fine for me -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958494 Title: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: After screen was blanked (meta-L; lid closed) it wakes up with an erratic pattern, it can't recover from (except power off, power on). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 07:41:10 2022 InstallationDate: Installed on 2021-09-29 (112 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+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 1967166] Re: Azure: not enough RAM under 4GB for CVM
This bug was fixed in the package linux-azure - 5.15.0-1003.4 --- linux-azure (5.15.0-1003.4) jammy; urgency=medium * jammy/linux-azure: 5.15.0-1003.4 -proposed tracker (LP: #1966481) * Azure: not enough RAM under 4GB for CVM (LP: #1967166) - SAUCE: azure: Swiotlb: Add swiotlb_alloc_from_low_pages switch - SAUCE: azure: x86/hyperv: Make swiotlb bounce buffer allocation not just from low pages * linux-azure: arm64 network performance improvement (LP: #1966098) - SAUCE: azure: ACPI: scan: Export acpi_get_dma_attr() - SAUCE: azure: dma-mapping: Add wrapper function to set dma_coherent - SAUCE: azure: Drivers: hv: vmbus: Propagate VMbus coherence to each VMbus device - SAUCE: azure: PCI: hv: Propagate coherence from VMbus device to PCI device [ Ubuntu: 5.15.0-25.25 ] * jammy/linux: 5.15.0-25.25 -proposed tracker (LP: #1967146) * Miscellaneous Ubuntu changes - SAUCE: Revert "scsi: core: Reallocate device's budget map on queue depth change" [ Ubuntu: 5.15.0-24.24 ] * jammy/linux: 5.15.0-24.24 -proposed tracker (LP: #1966305) * Update OS policy capability handshake (LP: #1966089) - thermal: int340x: Update OS policy capability handshake * Jammy update: v5.15.30 upstream stable release (LP: #1966057) - Revert "xfrm: state and policy should fail if XFRMA_IF_ID 0" - arm64: dts: rockchip: fix rk3399-puma-haikou USB OTG mode - xfrm: Check if_id in xfrm_migrate - xfrm: Fix xfrm migrate issues when address family changes - arm64: dts: rockchip: fix rk3399-puma eMMC HS400 signal integrity - arm64: dts: rockchip: align pl330 node name with dtschema - arm64: dts: rockchip: reorder rk3399 hdmi clocks - arm64: dts: agilex: use the compatible "intel,socfpga-agilex-hsotg" - ARM: dts: rockchip: reorder rk322x hmdi clocks - ARM: dts: rockchip: fix a typo on rk3288 crypto-controller - mac80211: refuse aggregations sessions before authorized - MIPS: smp: fill in sibling and core maps earlier - ARM: 9178/1: fix unmet dependency on BITREVERSE for HAVE_ARCH_BITREVERSE - Bluetooth: hci_core: Fix leaking sent_cmd skb - can: rcar_canfd: rcar_canfd_channel_probe(): register the CAN device when fully ready - atm: firestream: check the return value of ioremap() in fs_init() - iwlwifi: don't advertise TWT support - drm/vrr: Set VRR capable prop only if it is attached to connector - nl80211: Update bss channel on channel switch for P2P_CLIENT - tcp: make tcp_read_sock() more robust - sfc: extend the locking on mcdi->seqno - bnx2: Fix an error message - kselftest/vm: fix tests build with old libc - x86/module: Fix the paravirt vs alternative order - ice: Fix race condition during interface enslave - Linux 5.15.30 * Jammy update: v5.15.29 upstream stable release (LP: #1966056) - arm64: dts: qcom: sm8350: Describe GCC dependency clocks - arm64: dts: qcom: sm8350: Correct UFS symbol clocks - HID: elo: Revert USB reference counting - HID: hid-thrustmaster: fix OOB read in thrustmaster_interrupts - ARM: boot: dts: bcm2711: Fix HVS register range - clk: qcom: gdsc: Add support to update GDSC transition delay - clk: qcom: dispcc: Update the transition delay for MDSS GDSC - HID: vivaldi: fix sysfs attributes leak - arm64: dts: armada-3720-turris-mox: Add missing ethernet0 alias - tipc: fix kernel panic when enabling bearer - vdpa/mlx5: add validation for VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET command - vduse: Fix returning wrong type in vduse_domain_alloc_iova() - net: phy: meson-gxl: fix interrupt handling in forced mode - mISDN: Fix memory leak in dsp_pipeline_build() - vhost: fix hung thread due to erroneous iotlb entries - virtio-blk: Don't use MAX_DISCARD_SEGMENTS if max_discard_seg is zero - vdpa: fix use-after-free on vp_vdpa_remove - isdn: hfcpci: check the return value of dma_set_mask() in setup_hw() - net: qlogic: check the return value of dma_alloc_coherent() in qed_vf_hw_prepare() - esp: Fix possible buffer overflow in ESP transformation - esp: Fix BEET mode inter address family tunneling on GSO - qed: return status of qed_iov_get_link - smsc95xx: Ignore -ENODEV errors when device is unplugged - gpiolib: acpi: Convert ACPI value of debounce to microseconds - drm/sun4i: mixer: Fix P010 and P210 format numbers - net: dsa: mt7530: fix incorrect test in mt753x_phylink_validate() - ARM: dts: aspeed: Fix AST2600 quad spi group - iavf: Fix handling of vlan strip virtual channel messages - i40e: stop disabling VFs due to PF error responses - ice: stop disabling VFs due to PF error responses - ice: Fix error with handling of bonding MTU - ice: Don't use GFP_KERNEL in atomic context - ice: Fix curr_link_speed advertised speed - ethernet: Fix error handling in xemaclite_of_probe - tipc: fix incorrect order of state
[Kernel-packages] [Bug 1966098] Re: linux-azure: arm64 network performance improvement
This bug was fixed in the package linux-azure - 5.15.0-1003.4 --- linux-azure (5.15.0-1003.4) jammy; urgency=medium * jammy/linux-azure: 5.15.0-1003.4 -proposed tracker (LP: #1966481) * Azure: not enough RAM under 4GB for CVM (LP: #1967166) - SAUCE: azure: Swiotlb: Add swiotlb_alloc_from_low_pages switch - SAUCE: azure: x86/hyperv: Make swiotlb bounce buffer allocation not just from low pages * linux-azure: arm64 network performance improvement (LP: #1966098) - SAUCE: azure: ACPI: scan: Export acpi_get_dma_attr() - SAUCE: azure: dma-mapping: Add wrapper function to set dma_coherent - SAUCE: azure: Drivers: hv: vmbus: Propagate VMbus coherence to each VMbus device - SAUCE: azure: PCI: hv: Propagate coherence from VMbus device to PCI device [ Ubuntu: 5.15.0-25.25 ] * jammy/linux: 5.15.0-25.25 -proposed tracker (LP: #1967146) * Miscellaneous Ubuntu changes - SAUCE: Revert "scsi: core: Reallocate device's budget map on queue depth change" [ Ubuntu: 5.15.0-24.24 ] * jammy/linux: 5.15.0-24.24 -proposed tracker (LP: #1966305) * Update OS policy capability handshake (LP: #1966089) - thermal: int340x: Update OS policy capability handshake * Jammy update: v5.15.30 upstream stable release (LP: #1966057) - Revert "xfrm: state and policy should fail if XFRMA_IF_ID 0" - arm64: dts: rockchip: fix rk3399-puma-haikou USB OTG mode - xfrm: Check if_id in xfrm_migrate - xfrm: Fix xfrm migrate issues when address family changes - arm64: dts: rockchip: fix rk3399-puma eMMC HS400 signal integrity - arm64: dts: rockchip: align pl330 node name with dtschema - arm64: dts: rockchip: reorder rk3399 hdmi clocks - arm64: dts: agilex: use the compatible "intel,socfpga-agilex-hsotg" - ARM: dts: rockchip: reorder rk322x hmdi clocks - ARM: dts: rockchip: fix a typo on rk3288 crypto-controller - mac80211: refuse aggregations sessions before authorized - MIPS: smp: fill in sibling and core maps earlier - ARM: 9178/1: fix unmet dependency on BITREVERSE for HAVE_ARCH_BITREVERSE - Bluetooth: hci_core: Fix leaking sent_cmd skb - can: rcar_canfd: rcar_canfd_channel_probe(): register the CAN device when fully ready - atm: firestream: check the return value of ioremap() in fs_init() - iwlwifi: don't advertise TWT support - drm/vrr: Set VRR capable prop only if it is attached to connector - nl80211: Update bss channel on channel switch for P2P_CLIENT - tcp: make tcp_read_sock() more robust - sfc: extend the locking on mcdi->seqno - bnx2: Fix an error message - kselftest/vm: fix tests build with old libc - x86/module: Fix the paravirt vs alternative order - ice: Fix race condition during interface enslave - Linux 5.15.30 * Jammy update: v5.15.29 upstream stable release (LP: #1966056) - arm64: dts: qcom: sm8350: Describe GCC dependency clocks - arm64: dts: qcom: sm8350: Correct UFS symbol clocks - HID: elo: Revert USB reference counting - HID: hid-thrustmaster: fix OOB read in thrustmaster_interrupts - ARM: boot: dts: bcm2711: Fix HVS register range - clk: qcom: gdsc: Add support to update GDSC transition delay - clk: qcom: dispcc: Update the transition delay for MDSS GDSC - HID: vivaldi: fix sysfs attributes leak - arm64: dts: armada-3720-turris-mox: Add missing ethernet0 alias - tipc: fix kernel panic when enabling bearer - vdpa/mlx5: add validation for VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET command - vduse: Fix returning wrong type in vduse_domain_alloc_iova() - net: phy: meson-gxl: fix interrupt handling in forced mode - mISDN: Fix memory leak in dsp_pipeline_build() - vhost: fix hung thread due to erroneous iotlb entries - virtio-blk: Don't use MAX_DISCARD_SEGMENTS if max_discard_seg is zero - vdpa: fix use-after-free on vp_vdpa_remove - isdn: hfcpci: check the return value of dma_set_mask() in setup_hw() - net: qlogic: check the return value of dma_alloc_coherent() in qed_vf_hw_prepare() - esp: Fix possible buffer overflow in ESP transformation - esp: Fix BEET mode inter address family tunneling on GSO - qed: return status of qed_iov_get_link - smsc95xx: Ignore -ENODEV errors when device is unplugged - gpiolib: acpi: Convert ACPI value of debounce to microseconds - drm/sun4i: mixer: Fix P010 and P210 format numbers - net: dsa: mt7530: fix incorrect test in mt753x_phylink_validate() - ARM: dts: aspeed: Fix AST2600 quad spi group - iavf: Fix handling of vlan strip virtual channel messages - i40e: stop disabling VFs due to PF error responses - ice: stop disabling VFs due to PF error responses - ice: Fix error with handling of bonding MTU - ice: Don't use GFP_KERNEL in atomic context - ice: Fix curr_link_speed advertised speed - ethernet: Fix error handling in xemaclite_of_probe - tipc: fix incorrect order of state
[Kernel-packages] [Bug 1958918] Re: dependency on crda obsolete according to Debian
This bug was fixed in the package linux-azure - 5.15.0-1003.4 --- linux-azure (5.15.0-1003.4) jammy; urgency=medium * jammy/linux-azure: 5.15.0-1003.4 -proposed tracker (LP: #1966481) * Azure: not enough RAM under 4GB for CVM (LP: #1967166) - SAUCE: azure: Swiotlb: Add swiotlb_alloc_from_low_pages switch - SAUCE: azure: x86/hyperv: Make swiotlb bounce buffer allocation not just from low pages * linux-azure: arm64 network performance improvement (LP: #1966098) - SAUCE: azure: ACPI: scan: Export acpi_get_dma_attr() - SAUCE: azure: dma-mapping: Add wrapper function to set dma_coherent - SAUCE: azure: Drivers: hv: vmbus: Propagate VMbus coherence to each VMbus device - SAUCE: azure: PCI: hv: Propagate coherence from VMbus device to PCI device [ Ubuntu: 5.15.0-25.25 ] * jammy/linux: 5.15.0-25.25 -proposed tracker (LP: #1967146) * Miscellaneous Ubuntu changes - SAUCE: Revert "scsi: core: Reallocate device's budget map on queue depth change" [ Ubuntu: 5.15.0-24.24 ] * jammy/linux: 5.15.0-24.24 -proposed tracker (LP: #1966305) * Update OS policy capability handshake (LP: #1966089) - thermal: int340x: Update OS policy capability handshake * Jammy update: v5.15.30 upstream stable release (LP: #1966057) - Revert "xfrm: state and policy should fail if XFRMA_IF_ID 0" - arm64: dts: rockchip: fix rk3399-puma-haikou USB OTG mode - xfrm: Check if_id in xfrm_migrate - xfrm: Fix xfrm migrate issues when address family changes - arm64: dts: rockchip: fix rk3399-puma eMMC HS400 signal integrity - arm64: dts: rockchip: align pl330 node name with dtschema - arm64: dts: rockchip: reorder rk3399 hdmi clocks - arm64: dts: agilex: use the compatible "intel,socfpga-agilex-hsotg" - ARM: dts: rockchip: reorder rk322x hmdi clocks - ARM: dts: rockchip: fix a typo on rk3288 crypto-controller - mac80211: refuse aggregations sessions before authorized - MIPS: smp: fill in sibling and core maps earlier - ARM: 9178/1: fix unmet dependency on BITREVERSE for HAVE_ARCH_BITREVERSE - Bluetooth: hci_core: Fix leaking sent_cmd skb - can: rcar_canfd: rcar_canfd_channel_probe(): register the CAN device when fully ready - atm: firestream: check the return value of ioremap() in fs_init() - iwlwifi: don't advertise TWT support - drm/vrr: Set VRR capable prop only if it is attached to connector - nl80211: Update bss channel on channel switch for P2P_CLIENT - tcp: make tcp_read_sock() more robust - sfc: extend the locking on mcdi->seqno - bnx2: Fix an error message - kselftest/vm: fix tests build with old libc - x86/module: Fix the paravirt vs alternative order - ice: Fix race condition during interface enslave - Linux 5.15.30 * Jammy update: v5.15.29 upstream stable release (LP: #1966056) - arm64: dts: qcom: sm8350: Describe GCC dependency clocks - arm64: dts: qcom: sm8350: Correct UFS symbol clocks - HID: elo: Revert USB reference counting - HID: hid-thrustmaster: fix OOB read in thrustmaster_interrupts - ARM: boot: dts: bcm2711: Fix HVS register range - clk: qcom: gdsc: Add support to update GDSC transition delay - clk: qcom: dispcc: Update the transition delay for MDSS GDSC - HID: vivaldi: fix sysfs attributes leak - arm64: dts: armada-3720-turris-mox: Add missing ethernet0 alias - tipc: fix kernel panic when enabling bearer - vdpa/mlx5: add validation for VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET command - vduse: Fix returning wrong type in vduse_domain_alloc_iova() - net: phy: meson-gxl: fix interrupt handling in forced mode - mISDN: Fix memory leak in dsp_pipeline_build() - vhost: fix hung thread due to erroneous iotlb entries - virtio-blk: Don't use MAX_DISCARD_SEGMENTS if max_discard_seg is zero - vdpa: fix use-after-free on vp_vdpa_remove - isdn: hfcpci: check the return value of dma_set_mask() in setup_hw() - net: qlogic: check the return value of dma_alloc_coherent() in qed_vf_hw_prepare() - esp: Fix possible buffer overflow in ESP transformation - esp: Fix BEET mode inter address family tunneling on GSO - qed: return status of qed_iov_get_link - smsc95xx: Ignore -ENODEV errors when device is unplugged - gpiolib: acpi: Convert ACPI value of debounce to microseconds - drm/sun4i: mixer: Fix P010 and P210 format numbers - net: dsa: mt7530: fix incorrect test in mt753x_phylink_validate() - ARM: dts: aspeed: Fix AST2600 quad spi group - iavf: Fix handling of vlan strip virtual channel messages - i40e: stop disabling VFs due to PF error responses - ice: stop disabling VFs due to PF error responses - ice: Fix error with handling of bonding MTU - ice: Don't use GFP_KERNEL in atomic context - ice: Fix curr_link_speed advertised speed - ethernet: Fix error handling in xemaclite_of_probe - tipc: fix incorrect order of state
[Kernel-packages] [Bug 1958918] Re: dependency on crda obsolete according to Debian
This bug was fixed in the package linux-oracle - 5.15.0-1002.4 --- linux-oracle (5.15.0-1002.4) jammy; urgency=medium * jammy/linux-oracle: 5.15.0-1002.4 -proposed tracker (LP: #1966490) * Packaging resync (LP: #1786013) - [Packaging] resync getabis - [Packaging] update Ubuntu.md * dependency on crda obsolete according to Debian (LP: #1958918) - [Packaging] switch dependency from crda to wireless-regdb * Miscellaneous Ubuntu changes - [Config] update configs after rebase [ Ubuntu: 5.15.0-25.25 ] * jammy/linux: 5.15.0-25.25 -proposed tracker (LP: #1967146) * Miscellaneous Ubuntu changes - SAUCE: Revert "scsi: core: Reallocate device's budget map on queue depth change" [ Ubuntu: 5.15.0-24.24 ] * jammy/linux: 5.15.0-24.24 -proposed tracker (LP: #1966305) * Update OS policy capability handshake (LP: #1966089) - thermal: int340x: Update OS policy capability handshake * Jammy update: v5.15.30 upstream stable release (LP: #1966057) - Revert "xfrm: state and policy should fail if XFRMA_IF_ID 0" - arm64: dts: rockchip: fix rk3399-puma-haikou USB OTG mode - xfrm: Check if_id in xfrm_migrate - xfrm: Fix xfrm migrate issues when address family changes - arm64: dts: rockchip: fix rk3399-puma eMMC HS400 signal integrity - arm64: dts: rockchip: align pl330 node name with dtschema - arm64: dts: rockchip: reorder rk3399 hdmi clocks - arm64: dts: agilex: use the compatible "intel,socfpga-agilex-hsotg" - ARM: dts: rockchip: reorder rk322x hmdi clocks - ARM: dts: rockchip: fix a typo on rk3288 crypto-controller - mac80211: refuse aggregations sessions before authorized - MIPS: smp: fill in sibling and core maps earlier - ARM: 9178/1: fix unmet dependency on BITREVERSE for HAVE_ARCH_BITREVERSE - Bluetooth: hci_core: Fix leaking sent_cmd skb - can: rcar_canfd: rcar_canfd_channel_probe(): register the CAN device when fully ready - atm: firestream: check the return value of ioremap() in fs_init() - iwlwifi: don't advertise TWT support - drm/vrr: Set VRR capable prop only if it is attached to connector - nl80211: Update bss channel on channel switch for P2P_CLIENT - tcp: make tcp_read_sock() more robust - sfc: extend the locking on mcdi->seqno - bnx2: Fix an error message - kselftest/vm: fix tests build with old libc - x86/module: Fix the paravirt vs alternative order - ice: Fix race condition during interface enslave - Linux 5.15.30 * Jammy update: v5.15.29 upstream stable release (LP: #1966056) - arm64: dts: qcom: sm8350: Describe GCC dependency clocks - arm64: dts: qcom: sm8350: Correct UFS symbol clocks - HID: elo: Revert USB reference counting - HID: hid-thrustmaster: fix OOB read in thrustmaster_interrupts - ARM: boot: dts: bcm2711: Fix HVS register range - clk: qcom: gdsc: Add support to update GDSC transition delay - clk: qcom: dispcc: Update the transition delay for MDSS GDSC - HID: vivaldi: fix sysfs attributes leak - arm64: dts: armada-3720-turris-mox: Add missing ethernet0 alias - tipc: fix kernel panic when enabling bearer - vdpa/mlx5: add validation for VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET command - vduse: Fix returning wrong type in vduse_domain_alloc_iova() - net: phy: meson-gxl: fix interrupt handling in forced mode - mISDN: Fix memory leak in dsp_pipeline_build() - vhost: fix hung thread due to erroneous iotlb entries - virtio-blk: Don't use MAX_DISCARD_SEGMENTS if max_discard_seg is zero - vdpa: fix use-after-free on vp_vdpa_remove - isdn: hfcpci: check the return value of dma_set_mask() in setup_hw() - net: qlogic: check the return value of dma_alloc_coherent() in qed_vf_hw_prepare() - esp: Fix possible buffer overflow in ESP transformation - esp: Fix BEET mode inter address family tunneling on GSO - qed: return status of qed_iov_get_link - smsc95xx: Ignore -ENODEV errors when device is unplugged - gpiolib: acpi: Convert ACPI value of debounce to microseconds - drm/sun4i: mixer: Fix P010 and P210 format numbers - net: dsa: mt7530: fix incorrect test in mt753x_phylink_validate() - ARM: dts: aspeed: Fix AST2600 quad spi group - iavf: Fix handling of vlan strip virtual channel messages - i40e: stop disabling VFs due to PF error responses - ice: stop disabling VFs due to PF error responses - ice: Fix error with handling of bonding MTU - ice: Don't use GFP_KERNEL in atomic context - ice: Fix curr_link_speed advertised speed - ethernet: Fix error handling in xemaclite_of_probe - tipc: fix incorrect order of state message data sanity check - net: ethernet: ti: cpts: Handle error for clk_enable - net: ethernet: lpc_eth: Handle error for clk_enable - net: marvell: prestera: Add missing of_node_put() in prestera_switch_set_base_mac_addr - ax25: Fix NULL pointer dereference in ax2
[Kernel-packages] [Bug 1958918] Re: dependency on crda obsolete according to Debian
This bug was fixed in the package linux-gcp - 5.15.0-1003.6 --- linux-gcp (5.15.0-1003.6) jammy; urgency=medium * jammy/linux-gcp: 5.15.0-1003.6 -proposed tracker (LP: #1966482) * dependency on crda obsolete according to Debian (LP: #1958918) - [Packaging] switch dependency from crda to wireless-regdb * Miscellaneous Ubuntu changes - [gcp] add arm64 to getabis - [Config] updateconfigs [ Ubuntu: 5.15.0-25.25 ] * jammy/linux: 5.15.0-25.25 -proposed tracker (LP: #1967146) * Miscellaneous Ubuntu changes - SAUCE: Revert "scsi: core: Reallocate device's budget map on queue depth change" [ Ubuntu: 5.15.0-24.24 ] * jammy/linux: 5.15.0-24.24 -proposed tracker (LP: #1966305) * Update OS policy capability handshake (LP: #1966089) - thermal: int340x: Update OS policy capability handshake * Jammy update: v5.15.30 upstream stable release (LP: #1966057) - Revert "xfrm: state and policy should fail if XFRMA_IF_ID 0" - arm64: dts: rockchip: fix rk3399-puma-haikou USB OTG mode - xfrm: Check if_id in xfrm_migrate - xfrm: Fix xfrm migrate issues when address family changes - arm64: dts: rockchip: fix rk3399-puma eMMC HS400 signal integrity - arm64: dts: rockchip: align pl330 node name with dtschema - arm64: dts: rockchip: reorder rk3399 hdmi clocks - arm64: dts: agilex: use the compatible "intel,socfpga-agilex-hsotg" - ARM: dts: rockchip: reorder rk322x hmdi clocks - ARM: dts: rockchip: fix a typo on rk3288 crypto-controller - mac80211: refuse aggregations sessions before authorized - MIPS: smp: fill in sibling and core maps earlier - ARM: 9178/1: fix unmet dependency on BITREVERSE for HAVE_ARCH_BITREVERSE - Bluetooth: hci_core: Fix leaking sent_cmd skb - can: rcar_canfd: rcar_canfd_channel_probe(): register the CAN device when fully ready - atm: firestream: check the return value of ioremap() in fs_init() - iwlwifi: don't advertise TWT support - drm/vrr: Set VRR capable prop only if it is attached to connector - nl80211: Update bss channel on channel switch for P2P_CLIENT - tcp: make tcp_read_sock() more robust - sfc: extend the locking on mcdi->seqno - bnx2: Fix an error message - kselftest/vm: fix tests build with old libc - x86/module: Fix the paravirt vs alternative order - ice: Fix race condition during interface enslave - Linux 5.15.30 * Jammy update: v5.15.29 upstream stable release (LP: #1966056) - arm64: dts: qcom: sm8350: Describe GCC dependency clocks - arm64: dts: qcom: sm8350: Correct UFS symbol clocks - HID: elo: Revert USB reference counting - HID: hid-thrustmaster: fix OOB read in thrustmaster_interrupts - ARM: boot: dts: bcm2711: Fix HVS register range - clk: qcom: gdsc: Add support to update GDSC transition delay - clk: qcom: dispcc: Update the transition delay for MDSS GDSC - HID: vivaldi: fix sysfs attributes leak - arm64: dts: armada-3720-turris-mox: Add missing ethernet0 alias - tipc: fix kernel panic when enabling bearer - vdpa/mlx5: add validation for VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET command - vduse: Fix returning wrong type in vduse_domain_alloc_iova() - net: phy: meson-gxl: fix interrupt handling in forced mode - mISDN: Fix memory leak in dsp_pipeline_build() - vhost: fix hung thread due to erroneous iotlb entries - virtio-blk: Don't use MAX_DISCARD_SEGMENTS if max_discard_seg is zero - vdpa: fix use-after-free on vp_vdpa_remove - isdn: hfcpci: check the return value of dma_set_mask() in setup_hw() - net: qlogic: check the return value of dma_alloc_coherent() in qed_vf_hw_prepare() - esp: Fix possible buffer overflow in ESP transformation - esp: Fix BEET mode inter address family tunneling on GSO - qed: return status of qed_iov_get_link - smsc95xx: Ignore -ENODEV errors when device is unplugged - gpiolib: acpi: Convert ACPI value of debounce to microseconds - drm/sun4i: mixer: Fix P010 and P210 format numbers - net: dsa: mt7530: fix incorrect test in mt753x_phylink_validate() - ARM: dts: aspeed: Fix AST2600 quad spi group - iavf: Fix handling of vlan strip virtual channel messages - i40e: stop disabling VFs due to PF error responses - ice: stop disabling VFs due to PF error responses - ice: Fix error with handling of bonding MTU - ice: Don't use GFP_KERNEL in atomic context - ice: Fix curr_link_speed advertised speed - ethernet: Fix error handling in xemaclite_of_probe - tipc: fix incorrect order of state message data sanity check - net: ethernet: ti: cpts: Handle error for clk_enable - net: ethernet: lpc_eth: Handle error for clk_enable - net: marvell: prestera: Add missing of_node_put() in prestera_switch_set_base_mac_addr - ax25: Fix NULL pointer dereference in ax25_kill_by_device - net/mlx5: Fix size field in bufferx_reg struct - net/mlx5: Fix a rac
[Kernel-packages] [Bug 1953554] Re: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out
I'm seeing this exact same issue with a TP-Link UE300C USB-C adapter, the thing is, I have 2 identical intel NUC's with each one of these adaptors, and on the one machine I see this on average once a month for the last 3 months now, on the other machine this has not happend yet. replugging it and restarting the network seems to fix it, I'm not sure if this is a hardware issue or not Is there any information or debug info I can provide here to help this issue allong? -- 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/1953554 Title: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Bug description: Hi, I am facing this problem in Focal with the USB 3.0 Ethernet Gigabit adapter "ASIX Electronics Corp. AX88179 Gigabit Ethernet" (waneth is the name I assigned to this ethernet connected to the cable modem/router): [ cut here ] [94104.121581] NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out [94104.121606] WARNING: CPU: 2 PID: 217952 at net/sched/sch_generic.c:467 dev_watchdog+0x24f/0x260 [94104.121615] Modules linked in: binfmt_misc xt_recent nfnetlink nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua snd_sof_pci_intel_apl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof soundwire_bus snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core intel_rapl_msr snd_soc_sst_ipc intel_rapl_common 8814au(OE) mei_hdcp snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi intel_pmc_bxt snd_soc_core intel_telemetry_pltdrv intel_punit_ipc snd_compress intel_telemetry_core snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek coretemp snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine kvm_intel snd_hda_intel kvm snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec rapl intel_cstate snd_hda_core snd_hwdep snd_pcm snd_timer ax88179_178a cfg80211 efi_pstore mei_me usbnet ee1004 snd mii soundcore mei mac_hid bridge ip6t_REJECT nf_reject_ipv6 stp llc xt_hl [94104.121696] ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_limit xt_addrtype xt_tcpudp xt_MASQUERADE iptable_nat nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables sch_fq_codel iptable_filter bpfilter msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_bit drm_kms_helper crct10dif_pclmul crc32_pclmul ghash_clmulni_intel syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core aesni_intel crypto_simd i2c_i801 xhci_pci i2c_smbus cryptd r8169 realtek xhci_pci_renesas drm sdhci_pci ahci cqhci sdhci libahci video [94104.121771] CPU: 2 PID: 217952 Comm: PLUGIN[cgroups] Tainted: G OE 5.13.0-22-generic #22~20.04.1-Ubuntu [94104.121775] Hardware name: GIGABYTE MZGLKDP-00/MZGLKDP-00, BIOS F1 12/21/2017 [94104.121777] RIP: 0010:dev_watchdog+0x24f/0x260 [94104.121782] Code: c7 36 fd ff eb ab 4c 89 ff c6 05 60 f1 6e 01 01 e8 86 11 fa ff 44 89 e9 4c 89 fe 48 c7 c7 20 9c ca 89 48 89 c2 e8 38 17 17 00 <0f> 0b eb 8c 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 [94104.121785] RSP: 0018:b515c0138e88 EFLAGS: 00010282 [94104.121788] RAX: RBX: 91214fc45e00 RCX: 0027 [94104.121790] RDX: 0027 RSI: dfff RDI: 9124b05189c8 [94104.121792] RBP: b515c0138eb8 R08: 9124b05189c0 R09: b515c0138c60 [94104.121794] R10: 0001 R11: 0001 R12: 0001 [94104.121795] R13: R14: 912154a7d480 R15: 912154a7d000 [94104.121797] FS: 7f74619e5700() GS:9124b050() knlGS: [94104.121800] CS: 0010 DS: ES: CR0: 80050033 [94104.121802] CR2: 5635dd41b584 CR3: 00020592a000 CR4: 00350ee0 [94104.121805] Call Trace: [94104.121807] [94104.121812] ? pfifo_fast_enqueue+0x150/0x150 [94104.121816] call_timer_fn+0x2c/0x100 [94104.121821] run_timer_softirq+0x3d7/0x480 [94104.121824] ? perf_trace_softirq+0x9d/0xd0 [94104.121829] __do_softirq+0xdd/0x29b [94104.121835] irq_exit_rcu+0xa4/0xb0 [94104.121837] sysvec_apic_timer_interrupt+0x7c/0x90 [94104.121841] [94104.121843] asm_sysvec_apic_timer_interrupt+0x12/0x20 [94104.121846] RIP: 0010:errseq_sample+0x2/0x10 [94104.121850] Code: ff 48 d3 e2 48 f7 d2 48 21 d0 0f 01 ca 48 85 c0 0f 94 c0 0f b6 c0 c3 b8 01 00 00 00 c3 b8 f2 ff ff ff c3 cc cc cc cc cc 8b 07 00 00 00 00 f6 c4 10 0f 44 c2 c3 66 90 8b 17 31 c0 39 16 74 1b [94104.121853] RSP: 0018:b515c29cfb68 EFLAGS: 0286 [94104.121855] RAX:
[Kernel-packages] [Bug 1953554] Re: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out
[335315.982132] [ cut here ] [335315.982172] NETDEV WATCHDOG: enxf8e43ba9c6b7 (ax88179_178a): transmit queue 0 timed out [335315.982195] WARNING: CPU: 6 PID: 0 at net/sched/sch_generic.c:467 dev_watchdog+0x24c/0x250 [335315.982202] Modules linked in: tcp_diag udp_diag inet_diag nfsv3 nfs_acl nfs lockd grace veth rbd ceph libceph fscache netfs ebtable_filter ebtables ip_set ip6table_raw iptable_raw ip6table_filter ip6_tables iptable_filter bpfilter sctp ip6_udp_tunnel udp_tunnel nf_tables bonding tls softdog nfnetlink_log nfnetlink cdc_mbim cdc_wdm cdc_ncm cdc_ether snd_hda_codec_hdmi intel_rapl_msr intel_rapl_common snd_sof_pci_intel_cnl snd_sof_intel_hda_common x86_pkg_temp_thermal soundwire_intel intel_powerclamp soundwire_generic_allocation coretemp soundwire_cadence snd_ctl_led snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek kvm_intel snd_sof_xtensa_dsp snd_hda_codec_generic snd_sof kvm snd_soc_hdac_hda iwlmvm snd_hda_ext_core snd_soc_acpi_intel_match irqbypass snd_soc_acpi soundwire_bus crct10dif_pclmul mac80211 ghash_clmulni_intel ledtrig_audio mei_hdcp libarc4 aesni_intel snd_soc_core crypto_simd snd_compress cryptd ac97_bus snd_pcm_dmaengine snd_hda_intel rapl snd_intel_dspcfg intel_cstate [335315.982343] i915 snd_intel_sdw_acpi snd_hda_codec pcspkr snd_hda_core btusb snd_hwdep btrtl intel_wmi_thunderbolt wmi_bmof efi_pstore btbcm drm_kms_helper btintel snd_pcm cec iwlwifi rc_core bluetooth snd_timer i2c_algo_bit ax88179_178a fb_sys_fops snd syscopyarea ecdh_generic usbnet sysfillrect mii ee1004 soundcore sysimgblt ecc mei_me cfg80211 mei intel_pch_thermal acpi_tad mac_hid acpi_pad zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_net vhost vhost_iotlb tap ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi drm sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c crc32_pclmul nvme sdhci_pci xhci_pci intel_lpss_pci i2c_i801 cqhci xhci_pci_renesas e1000e i2c_smbus sdhci thunderbolt nvme_core ahci intel_lpss libahci xhci_hcd idma64 wmi video pinctrl_cannonlake [335315.982469] CPU: 6 PID: 0 Comm: swapper/6 Tainted: P O 5.13.19-6-pve #1 [335315.982472] Hardware name: Intel(R) Client Systems NUC10i7FNK/NUC10i7FNB, BIOS FNCML357.0038.2020.0131.1422 01/31/2020 [335315.982473] RIP: 0010:dev_watchdog+0x24c/0x250 [335315.982476] Code: fa 25 fd ff eb ab 4c 89 ff c6 05 35 da 4f 01 01 e8 e9 ee f9 ff 44 89 e9 4c 89 fe 48 c7 c7 80 d9 48 ae 48 89 c2 e8 bc 05 1a 00 <0f> 0b eb 8c 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 41 56 4d 89 [335315.982479] RSP: 0018:b0bac029ce80 EFLAGS: 00010282 [335315.982481] RAX: RBX: 9e0d86e98000 RCX: 083f [335315.982483] RDX: RSI: 00f6 RDI: 083f [335315.982484] RBP: b0bac029ceb0 R08: R09: b0bac029cc60 [335315.982485] R10: b0bac029cc58 R11: aeb55428 R12: 9e0d86e98080 [335315.982487] R13: R14: 9e0d92c96480 R15: 9e0d92c96000 [335315.982488] FS: () GS:9e10f0d0() knlGS: [335315.982490] CS: 0010 DS: ES: CR0: 80050033 [335315.982491] CR2: 55faae44be88 CR3: 000256210006 CR4: 003706e0 [335315.982493] Call Trace: [335315.982495] [335315.982498] ? pfifo_fast_enqueue+0x150/0x150 [335315.982500] call_timer_fn+0x2c/0x100 [335315.982503] __run_timers.part.0+0x1d8/0x250 [335315.982505] ? ktime_get+0x3b/0xa0 [335315.982508] ? lapic_next_deadline+0x2c/0x40 [335315.982512] ? clockevents_program_event+0x8f/0xe0 [335315.982516] run_timer_softirq+0x2a/0x50 [335315.982519] __do_softirq+0xcb/0x281 [335315.982523] irq_exit_rcu+0xa2/0xd0 [335315.982527] sysvec_apic_timer_interrupt+0x7c/0x90 [335315.982529] [335315.982530] [335315.982531] asm_sysvec_apic_timer_interrupt+0x12/0x20 [335315.982534] RIP: 0010:cpuidle_enter_state+0xcc/0x360 [335315.982538] Code: 3d f1 92 8d 52 e8 f4 54 7a ff 49 89 c6 0f 1f 44 00 00 31 ff e8 95 60 7a ff 80 7d d7 00 0f 85 01 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 ff 0f 88 0d 01 00 00 49 63 cf 4c 2b 75 c8 48 8d 04 49 48 89 [335315.982540] RSP: 0018:b0bac0137e68 EFLAGS: 0246 [335315.982542] RAX: 9e10f0d34ec0 RBX: 0003 RCX: 001f [335315.982543] RDX: RSI: 4f9a1f43 RDI: [335315.982545] RBP: b0bac0137ea0 R08: 000130f7d6002b01 R09: 0018 [335315.982546] R10: 0001 R11: R12: d0babfb00500 [335315.982547] R13: aec50e00 R14: 000130f7d6002b01 R15: 0003 [335315.982550] ? cpuidle_enter_state+0xbb/0x360 [335315.982553] cpuidle_enter+0x2e/0x40 [335315.982556] do_idle+0x1ff/0x2a0 [335315.982559] cpu_startup_entry+0x20/0x30 [335315.982561] start_secondary+0x1
[Kernel-packages] [Bug 1953554] Re: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out
Jens, I suggest you to buy Tp Link Ue306. I did it, and now is working fine. Weird, because it does have the AX88179 chipset too, same as the one that was failing for me (Ugreen CM209). -- 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/1953554 Title: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Bug description: Hi, I am facing this problem in Focal with the USB 3.0 Ethernet Gigabit adapter "ASIX Electronics Corp. AX88179 Gigabit Ethernet" (waneth is the name I assigned to this ethernet connected to the cable modem/router): [ cut here ] [94104.121581] NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out [94104.121606] WARNING: CPU: 2 PID: 217952 at net/sched/sch_generic.c:467 dev_watchdog+0x24f/0x260 [94104.121615] Modules linked in: binfmt_misc xt_recent nfnetlink nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua snd_sof_pci_intel_apl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof soundwire_bus snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core intel_rapl_msr snd_soc_sst_ipc intel_rapl_common 8814au(OE) mei_hdcp snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi intel_pmc_bxt snd_soc_core intel_telemetry_pltdrv intel_punit_ipc snd_compress intel_telemetry_core snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek coretemp snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine kvm_intel snd_hda_intel kvm snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec rapl intel_cstate snd_hda_core snd_hwdep snd_pcm snd_timer ax88179_178a cfg80211 efi_pstore mei_me usbnet ee1004 snd mii soundcore mei mac_hid bridge ip6t_REJECT nf_reject_ipv6 stp llc xt_hl [94104.121696] ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_limit xt_addrtype xt_tcpudp xt_MASQUERADE iptable_nat nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables sch_fq_codel iptable_filter bpfilter msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_bit drm_kms_helper crct10dif_pclmul crc32_pclmul ghash_clmulni_intel syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core aesni_intel crypto_simd i2c_i801 xhci_pci i2c_smbus cryptd r8169 realtek xhci_pci_renesas drm sdhci_pci ahci cqhci sdhci libahci video [94104.121771] CPU: 2 PID: 217952 Comm: PLUGIN[cgroups] Tainted: G OE 5.13.0-22-generic #22~20.04.1-Ubuntu [94104.121775] Hardware name: GIGABYTE MZGLKDP-00/MZGLKDP-00, BIOS F1 12/21/2017 [94104.121777] RIP: 0010:dev_watchdog+0x24f/0x260 [94104.121782] Code: c7 36 fd ff eb ab 4c 89 ff c6 05 60 f1 6e 01 01 e8 86 11 fa ff 44 89 e9 4c 89 fe 48 c7 c7 20 9c ca 89 48 89 c2 e8 38 17 17 00 <0f> 0b eb 8c 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 [94104.121785] RSP: 0018:b515c0138e88 EFLAGS: 00010282 [94104.121788] RAX: RBX: 91214fc45e00 RCX: 0027 [94104.121790] RDX: 0027 RSI: dfff RDI: 9124b05189c8 [94104.121792] RBP: b515c0138eb8 R08: 9124b05189c0 R09: b515c0138c60 [94104.121794] R10: 0001 R11: 0001 R12: 0001 [94104.121795] R13: R14: 912154a7d480 R15: 912154a7d000 [94104.121797] FS: 7f74619e5700() GS:9124b050() knlGS: [94104.121800] CS: 0010 DS: ES: CR0: 80050033 [94104.121802] CR2: 5635dd41b584 CR3: 00020592a000 CR4: 00350ee0 [94104.121805] Call Trace: [94104.121807] [94104.121812] ? pfifo_fast_enqueue+0x150/0x150 [94104.121816] call_timer_fn+0x2c/0x100 [94104.121821] run_timer_softirq+0x3d7/0x480 [94104.121824] ? perf_trace_softirq+0x9d/0xd0 [94104.121829] __do_softirq+0xdd/0x29b [94104.121835] irq_exit_rcu+0xa4/0xb0 [94104.121837] sysvec_apic_timer_interrupt+0x7c/0x90 [94104.121841] [94104.121843] asm_sysvec_apic_timer_interrupt+0x12/0x20 [94104.121846] RIP: 0010:errseq_sample+0x2/0x10 [94104.121850] Code: ff 48 d3 e2 48 f7 d2 48 21 d0 0f 01 ca 48 85 c0 0f 94 c0 0f b6 c0 c3 b8 01 00 00 00 c3 b8 f2 ff ff ff c3 cc cc cc cc cc 8b 07 00 00 00 00 f6 c4 10 0f 44 c2 c3 66 90 8b 17 31 c0 39 16 74 1b [94104.121853] RSP: 0018:b515c29cfb68 EFLAGS: 0286 [94104.121855] RAX: RBX: 91214298e500 RCX: 0002 [94104.121857] RDX: 0001 RSI: 0002 RDI: 91218c293c88 [94104.121859] RBP: b515c29cfba0 R08: 91221987a160 R09: 9121e1e8c180 [94104.121860] R10: 00746174 R11: 8196e1bd R12:
[Kernel-packages] [Bug 1961955] Re: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream
https://github.com/vcrhonek/hwdata/commit/ae144d896eea90e527a57276accaf0da043c9f83 added the ROR-N100 to upstream hwdata. Request you to pull this as well into Jammy. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1961955 Title: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream Status in hwdata package in Ubuntu: Incomplete Status in hwdata source package in Focal: New Status in hwdata source package in Jammy: Incomplete Bug description: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however new form factors are having new subsystem-ids. BOSS-N1 is planned support in Ubuntu 20.04 onwards. Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET 1b4b: 2241: 1028: 2196 ROR-N100 Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1961955/+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 1940690] Re: amdgpu kernel crash
*** This bug is a duplicate of bug 1956845 *** https://bugs.launchpad.net/bugs/1956845 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940690 Title: amdgpu kernel crash Status in linux package in Ubuntu: Confirmed Bug description: [0.00] Linux version 5.4.0-81-generic (buildd@lgw01-amd64-052) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 (Ubuntu 5.4.0-81.91-generic 5.4.128) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-81-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [ 217.837643] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7499 thread Xorg:cs0 pid 7500) [ 217.837647] amdgpu :09:00.0: in page starting at address 0x80010797e000 from client 27 [ 217.837649] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 217.837651] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 217.837653] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 217.837655] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 217.837657] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 217.837658] amdgpu :09:00.0: RW: 0x0 [ 217.837668] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7499 thread Xorg:cs0 pid 7500) [ 217.837670] amdgpu :09:00.0: in page starting at address 0x8001079a6000 from client 27 [ 217.837672] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 217.837674] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 217.837675] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 217.837677] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 217.837679] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 217.837681] amdgpu :09:00.0: RW: 0x0 [ 217.837698] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7499 thread Xorg:cs0 pid 7500) [ 217.837703] amdgpu :09:00.0: in page starting at address 0x8001079ce000 from client 27 [ 217.837708] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 217.837712] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 217.837716] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 217.837721] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 217.837725] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 217.837729] amdgpu :09:00.0: RW: 0x0 [ 217.838669] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7499 thread Xorg:cs0 pid 7500) [ 217.838673] amdgpu :09:00.0: in page starting at address 0x80010797e000 from client 27 [ 217.838675] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 217.838677] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 217.838679] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 217.838681] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 217.838683] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 217.838684] amdgpu :09:00.0: RW: 0x0 [ 217.838695] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7499 thread Xorg:cs0 pid 7500) [ 217.838697] amdgpu :09:00.0: in page starting at address 0x8001079a6000 from client 27 [ 217.838699] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 217.838701] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 217.838703] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 217.838704] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 217.838706] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 217.838708] amdgpu :09:00.0: RW: 0x0 [ 217.838727] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7499 thread Xorg:cs0 pid 7500) [ 217.838732] amdgpu :09:00.0: in page starting at address 0x8001079ce000 from client 27 [ 217.838736] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 217.838741] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 217.838746] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 217.838750] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 217.838755] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 217.838759] amdgpu :09:00.0: RW: 0x0 [ 217.839694] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7499 thread Xorg:cs0 pid 7500) [ 217.839698] amdgpu :09:00.0: in page starting at address 0x80010797e000 from client 27 [ 217.839700] amdgpu :09:00.0: VM_L2_PROTECTION_FAU
[Kernel-packages] [Bug 1914774] Re: HWE kernels do not ship linux-tools packages
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta-hwe-5.4 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1914774 Title: HWE kernels do not ship linux-tools packages Status in linux-meta-hwe-5.4 package in Ubuntu: Confirmed Bug description: While running kernel 5.4.0-64 today on bionic I noticed that Canonical kernel team does not provide a linux-hwe-5.4-tools package. Is that a deliberate choice? If so, would you please share the reason? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.4/+bug/1914774/+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 1940690] Re: amdgpu kernel crash
*** This bug is a duplicate of bug 1956845 *** https://bugs.launchpad.net/bugs/1956845 Hardware: DP Epyc Milan 7763 node with 2 qty AMD Instinct Mi100 Kernel: ubuntu 18.04.6LTS w/linux-hwe 5.4.0-107-generic ROCm 5.1.0 and AMDGPU version: 5.13.20.5.1 driver Homegrown software developed using ROCm 5.1.0. Might this be related? Logs: [304726.475355] beegfs: enabling unsafe global rkey [304734.912424] amdgpu :23:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32769, for process hyprep pid 122284 thread hyprep pid 122284) [304734.928526] amdgpu :23:00.0: amdgpu: in page starting at address 0x01753000 from IH client 0x1b (UTCL2) [304734.939972] amdgpu :23:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [304734.948130] amdgpu :23:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [304734.955858] amdgpu :23:00.0: amdgpu: MORE_FAULTS: 0x1 [304734.962115] amdgpu :23:00.0: amdgpu: WALKER_ERROR: 0x0 [304734.968441] amdgpu :23:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [304734.975196] amdgpu :23:00.0: amdgpu: MAPPING_ERROR: 0x0 [304734.981580] amdgpu :23:00.0: amdgpu: RW: 0x0 [304735.568400] amdgpu :23:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32769, for process pid 0 thread pid 0) [304735.582318] amdgpu :23:00.0: amdgpu: in page starting at address 0x01753000 from IH client 0x1b (UTCL2) [304735.593722] amdgpu :23:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x [304735.601851] amdgpu :23:00.0: amdgpu: Faulty UTCL2 client ID: CB (0x0) [304735.609465] amdgpu :23:00.0: amdgpu: MORE_FAULTS: 0x0 [304735.615686] amdgpu :23:00.0: amdgpu: WALKER_ERROR: 0x0 [304735.621994] amdgpu :23:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [304735.628737] amdgpu :23:00.0: amdgpu: MAPPING_ERROR: 0x0 [304735.635104] amdgpu :23:00.0: amdgpu: RW: 0x0 [321839.599489] beegfs: enabling unsafe global rkey Driver Apr 02 22:19:59 n004 kernel: [drm] amdgpu kernel modesetting enabled. Apr 02 22:19:59 n004 kernel: [drm] amdgpu version: 5.13.20.5.1 Apr 02 22:19:59 n004 kernel: amdgpu: Ignoring ACPI CRAT on non-APU system Apr 02 22:19:59 n004 kernel: amdgpu: Virtual CRAT table created for CPU Apr 02 22:19:59 n004 kernel: amdgpu: Topology: Add CPU node Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: remove_conflicting_pci_framebuffers: bar 0: 0x678 -> 0x67f Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: remove_conflicting_pci_framebuffers: bar 2: 0x680 -> 0x680001f Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: remove_conflicting_pci_framebuffers: bar 5: 0xeb40 -> 0xeb47 Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: enabling device ( -> 0003) Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: Fetched VBIOS from ROM BAR Apr 02 22:19:59 n004 kernel: amdgpu: ATOM BIOS: 113-D3431401-100 Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: MEM ECC is active. Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: SRAM ECC is active. Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: RAS INFO: ras initialized successfully, hardware ability[7fff] ras_mask[7fff] Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: VRAM: 32752M 0x0080 - 0x0087FEFF (32752M used) Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: GART: 512M 0x - 0x1FFF Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: AGP: 267878400M 0x0088 - 0x Apr 02 22:19:59 n004 kernel: [drm] amdgpu: 32752M of VRAM memory ready Apr 02 22:19:59 n004 kernel: [drm] amdgpu: 2064153M of GTT memory ready. Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: PSP runtime database doesn't exist Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: Will use PSP to load VCN firmware Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: HDCP: optional hdcp ta ucode is not available Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: DTM: optional dtm ta ucode is not available Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: RAP: optional rap ta ucode is not available Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: use vbios provided pptable Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: smc_dpm_info table revision(format.content): 4.6 Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: PMFW based fan control disabled Apr 02 22:19:59 n004 kernel: amdgpu :23:00.0: amdgpu: SMU is initialized successfully! Apr 02 22:19:59 n004 kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart Apr 02 22:19:59 n004 kernel: amdgpu: Virtual CRAT table created for GP
[Kernel-packages] [Bug 1914774] Re: HWE kernels do not ship linux-tools packages
so, this is very weird. We used to install binary "cpupower" from linux-tools via this package for the hwe kernel: linux-tools-generic-hwe-18.04 but this seems to have changed somewhere in between, the file list on packages.ubuntu.com only lists: /usr/share/doc/linux-tools-generic-hwe-18.04/changelog.gz /usr/share/doc/linux-tools-generic-hwe-18.04/copyright see, e.g.: https://packages.ubuntu.com/bionic-updates/amd64/linux-tools-generic-hwe-18.04/filelist linked from: https://packages.ubuntu.com/bionic-updates/linux-tools-generic-hwe-18.04 I believe this is, because it's a meta/virtual package? nevertheless I found how to install "cpupower" it seems it moved to the following package (adjust kernel subversion as needed): https://packages.ubuntu.com/bionic-updates/linux-hwe-5.4-tools-5.4.0-80 but this is also strange for several reasons: first, afaik you need to install the version for your specific installed kernel, but the package name leads to bad sed-magic in install scripts like: apt install linux-hwe-5.4-tools-$(uname -r | sed 's#-generic$##') this is obviously bad, but I could live with that. what is really really weird though, is the installation path of the cpupower binary: root@server:~# /usr/lib/linux-hwe-5.4-tools-5.4.0-104/cpupower --help Usage: cpupower [-d|--debug] [-c|--cpu cpulist ] [] Supported commands are: frequency-info frequency-set idle-info idle-set set info monitor help Not all commands can make use of the -c cpulist option. Use 'cpupower help ' for getting help for above commands. root@server:~# type cpupower -su: type: cpupower: not found it is not installed in $PATH at all, which is really contracdicting the upstream makefile, imho? see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/power/cpupower/Makefile am I holding it wrong? is there another package which installs cpupower in the correct path? why was the packaging changed, mid release? This breaks every workflow around the provided tools. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1914774 Title: HWE kernels do not ship linux-tools packages Status in linux-meta-hwe-5.4 package in Ubuntu: Confirmed Bug description: While running kernel 5.4.0-64 today on bionic I noticed that Canonical kernel team does not provide a linux-hwe-5.4-tools package. Is that a deliberate choice? If so, would you please share the reason? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.4/+bug/1914774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950107] Re: Ubuntu MATE 20.04.3 window-list crashed
*** This bug is a duplicate of bug 1838433 *** https://bugs.launchpad.net/bugs/1838433 ** This bug has been marked a duplicate of bug 1838433 mate-panel crashes when re-ordering the window list applet -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1950107 Title: Ubuntu MATE 20.04.3 window-list crashed Status in linux-signed-hwe-5.11 package in Ubuntu: Invalid Status in mate-panel package in Ubuntu: New Bug description: I got an error pop-up about a program crashing. I did not recognize the name as pertaining to Ubuntu MATE, so I closed it. The list of windows at the bottom of the screen was blank. Google how to reset the Windows List Manager. Dic alt-cntl-F2. Then the display went black (no signal). Had to turn off (without shutting down - blank screen). Had to reboot. Tried to report bug but was told that although it is in the distro, it is not supported (like Caja). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Nov 7 21:11:20 2021 SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1950107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967116] Re: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes
Hi Sumit, could you please verify the test kernel here: https://kernel.ubuntu.com/~kmously/kernel-kmously-2e0820d-jmN7/ -- 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/1967116 Title: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes Status in linux package in Ubuntu: Incomplete Bug description: Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below: 334ae6459aa3 scsi: mpi3mr: Fix flushing !WQ_MEM_RECLAIM events warning 22754f7fbb40 scsi: mpi3mr: Bump driver version to 8.0.0.68.0 d44b5fefb22e scsi: mpi3mr: Fix memory leaks 21401408ddeb scsi: mpi3mr: Update the copyright year 999224612724 scsi: mpi3mr: Fix reporting of actual data transfer size b3911ab3a76e scsi: mpi3mr: Fix cmnd getting marked as in use forever 191a3ef58634 scsi: mpi3mr: Fix hibernation issue 04b27e538d50 scsi: mpi3mr: Update MPI3 headers 6d211f1d2635 scsi: mpi3mr: Fix printing of pending I/O count 580e6742205e scsi: mpi3mr: Fix deadlock while canceling the fw event 3bb3c24e268a scsi: mpi3mr: Fix formatting problems in some kernel-doc comments 5867b8569e64 scsi: mpi3mr: Fix some spelling mistakes c77b1f8a8fae scsi: mpi3mr: Bump driver version to 8.0.0.61.0 a91603a5d504 scsi: mpi3mr: Enhanced Task Management Support Reply handling c86651345ca5 scsi: mpi3mr: Use TM response codes from MPI3 headers afd3a5793fe2 scsi: mpi3mr: Add io_uring interface support in I/O-polled mode 95cca8d5542a scsi: mpi3mr: Print cable mngnt and temp threshold events 78b76a0768ef scsi: mpi3mr: Support Prepare for Reset event c1af985d27da scsi: mpi3mr: Add Event acknowledgment logic c5758fc72b92 scsi: mpi3mr: Gracefully handle online FW update operation b64845a7d403 scsi: mpi3mr: Detect async reset that occurred in firmware c0b00a931e5e scsi: mpi3mr: Add IOC reinit function fe6db6151565 scsi: mpi3mr: Handle offline FW activation in graceful manner 59bd9cfe3fa0 scsi: mpi3mr: Code refactor of IOC init - part2 e3605f65ef69 scsi: mpi3mr: Code refactor of IOC init - part1 a6856cc4507b scsi: mpi3mr: Fault IOC when internal command gets timeout 2ac794baaec9 scsi: mpi3mr: Display IOC firmware package version 13fd7b1555b6 scsi: mpi3mr: Handle unaligned PLL in unmap cmnds 4f08b9637f63 scsi: mpi3mr: Increase internal cmnds timeout to 60s ba68779a518d scsi: mpi3mr: Do access status validation before adding devices 17d6b9cf89cf scsi: mpi3mr: Add support for PCIe Managed Switch SES device ec5ebd2c14a9 scsi: mpi3mr: Update MPI3 headers - part2 d00ff7c31195 scsi: mpi3mr: Update MPI3 headers - part1 fbaa9aa48bb4 scsi: mpi3mr: Don't reset IOC if cmnds flush with reset status a83ec831b24a scsi: mpi3mr: Replace spin_lock() with spin_lock_irqsave() 9cf0666f34b1 scsi: mpi3mr: Add debug APIs based on logging_level bits 30e99f05f8b1 scsi: mpi3mr: Use scnprintf() instead of snprintf() 97e6ea6d7806 scsi: mpi3mr: Fix duplicate device entries when scanning through sysfs 1a30fd18f21b scsi: mpi3mr: Call scsi_done() directly 76a4f7cc5973 scsi: mpi3mr: Clean up mpi3mr_print_ioc_info() 92cc94adfce4 scsi: mpi3mr: Use the proper SCSI midlayer interfaces for PI 69868c3b6939 scsi: mpi3mr: Use scsi_cmd_to_rq() instead of scsi_cmnd.request aa0dc6a73309 scsi: mpi3mr: Fix W=1 compilation warnings 62e528b80d6b scsi: mpi3mr: Fix warnings reported by smatch a254eae30b45 scsi: mpi3mr: Fix error return code in mpi3mr_init_ioc() f9dc034d0402 scsi: mpi3mr: Fix missing unlock on error 2938bedd0efa scsi: mpi3mr: Fix error handling in mpi3mr_setup_isr() d46bdecd9f3c scsi: mpi3mr: Delete unnecessary NULL check d3d61f9c8c2d scsi: mpi3mr: Fix a double free 7b8a49881b01 scsi: mpi3mr: Fix fall-through warning for Clang 9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints Thanks, Sumit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967116/+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 1959547] Comment bridged from LTC Bugzilla
--- Comment From fre...@de.ibm.com 2022-04-06 10:26 EDT--- Ok, thanks. I updated my system to Ubuntu 22.04 and ran my testsuite. Looks fine - all seems to be good and CEX8 exploitation support is available. Kernel used: root@a35lp66:~# uname -a Linux a35lp66 5.15.0-25-generic #25-Ubuntu SMP Wed Mar 30 15:54:59 UTC 2022 s390x s390x s390x GNU/Linux S390-tools: 2.20.0-0ubuntu1 So this is now verified :-) -- 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/1959547 Title: [22.04 FEAT] zcrypt DD: Exploitation Support of new IBM Z Crypto Hardware (kernel part) Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: zcrypt DD: Exploitation Support of new IBM Z Crypto Hardware - kernel part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959547/+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 1959547] Re: [22.04 FEAT] zcrypt DD: Exploitation Support of new IBM Z Crypto Hardware (kernel part)
Fantastic - many thx, Harald! -- 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/1959547 Title: [22.04 FEAT] zcrypt DD: Exploitation Support of new IBM Z Crypto Hardware (kernel part) Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: zcrypt DD: Exploitation Support of new IBM Z Crypto Hardware - kernel part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959547/+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 1968027] Re: shiftfs breaks paths in /proc/*/maps
** Description changed: When enabling shiftfs for LXD we get incorrect paths in /proc/*/maps within a container: root@anbox0:~# cat /proc/self/maps 55930e60-55930e608000 r-xp 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930e807000-55930e808000 r--p 7000 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930e808000-55930e809000 rw-p 8000 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930fd3c000-55930fd5d000 rw-p 00:00 0 [heap] 7fe736be2000-7fe736dc9000 r-xp 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736dc9000-7fe736fc9000 ---p 001e7000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fc9000-7fe736fcd000 r--p 001e7000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fcd000-7fe736fcf000 rw-p 001eb000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fcf000-7fe736fd3000 rw-p 00:00 0 7fe736fd3000-7fe736ffc000 r-xp 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so 7fe7371ba000-7fe7371de000 rw-p 00:00 0 7fe7371fc000-7fe7371fd000 r--p 00029000 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so 7fe7371fd000-7fe7371fe000 rw-p 0002a000 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so 7fe7371fe000-7fe7371ff000 rw-p 00:00 0 7ffcd50a-7ffcd50c1000 rw-p 00:00 0 [stack] 7ffcd51d2000-7ffcd51d6000 r--p 00:00 0 [vvar] 7ffcd51d6000-7ffcd51d8000 r-xp 00:00 0 [vdso] ff60-ff601000 --xp 00:00 0 [vsyscall] When shiftfs is disabled the paths look all correct and are relative to the root of the container root@anbox0:~# cat /proc/self/maps 557aaa20-557aaa208000 r-xp 00:48 14509 /bin/cat 557aaa407000-557aaa408000 r--p 7000 00:48 14509 /bin/cat 557aaa408000-557aaa409000 rw-p 8000 00:48 14509 /bin/cat 557aabaa5000-557aabac6000 rw-p 00:00 0 [heap] 7f4820526000-7f482070d000 r-xp 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f482070d000-7f482090d000 ---p 001e7000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f482090d000-7f4820911000 r--p 001e7000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f4820911000-7f4820913000 rw-p 001eb000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f4820913000-7f4820917000 rw-p 00:00 0 7f4820917000-7f482094 r-xp 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so 7f4820afe000-7f4820b22000 rw-p 00:00 0 7f4820b4-7f4820b41000 r--p 00029000 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so 7f4820b41000-7f4820b42000 rw-p 0002a000 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so 7f4820b42000-7f4820b43000 rw-p 00:00 0 7ffd12ead000-7ffd12ece000 rw-p 00:00 0 [stack] 7ffd12fd8000-7ffd12fdc000 r--p 00:00 0 [vvar] 7ffd12fdc000-7ffd12fde000 r-xp 00:00 0 [vdso] ff60-ff601000 --xp 00:00 0 [vsyscall] To reproduce: 1. Use Ubuntu 20.04 or newer inluding shiftfs 2. Install LXD (4.0.x is good enough) and enable shiftfs support $ snap install lxd $ snap set lxd shiftfs.enable=true $ snap restart lxd $ lxd init --auto 3. Start a container and check /proc/self/maps $ lxc launch ubuntu:f test0 $ lxc exec test0 -- cat /proc/self/maps 4. Turn shiftfs back off $ snap set lxd shiftfs.enable=false $ snap restart lxd 5. Check /proc/self/maps again inside the container $ lxc exec test0 -- cat /proc/self/maps This can be reproduced with both the 5.4 and 5.13 kernels on Ubuntu - 20.04 + 20.04 and also with 5.15 on a fresh jammy installation ** Description changed: + # Overview + When enabling shiftfs for LXD we get incorrect paths in
[Kernel-packages] [Bug 1939638] Re: [regression] USB device is not detected during boot
Sorry, I can't help with that.
All machines on which I have seen the issue so far are production machines
under configuration control where I cannot install an experimental kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1939638
Title:
[regression] USB device is not detected during boot
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-intel package in Ubuntu:
Confirmed
Status in linux-intel-5.13 package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux-intel source package in Focal:
Confirmed
Status in linux-intel-5.13 source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in linux-intel source package in Hirsute:
Invalid
Status in linux-intel-5.13 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
The USB devices (keyboard, storage...) are failed to be detected when
connecting to the problematic root hubs which need longer PowerOn-to-PowerGood
delay than it claims in the hub descriptor. It's caused by the upstream fix
90d28fb53d4a ("usb: core: reduce power-on-good delay time of root hub").
[Fix]
Reverting the upstream fix until a formal fix been placed.
[Test Case]
1. Plug the USB device to the ports of problematic root hub.
2. Power on the machine.
3. Check if the USB device can work or not after boot.
[Regression Potential]
Low. The longer delay is proven safe in old kernels.
== Original Bug Description ==
[Summary]
The USB devices (keyboard, storage...) are failed to be detected during boot
after upgrade to UBUNTU focal kernel 5.4.0-78 and hirsute 5.11.0-26. However,
they will be detected and working ok after re-plugging. The kernel output shows
as down below during boot
[ 39.350435] hub 1-0:1.0: USB hub found
[ 39.398835] hub 1-0:1.0: 12 ports detected
[ 39.622744] usb usb1-port3: couldn't allocate usb_device
And when I plug out then plug in the same device, it shows
[57210.794140] usb 1-3: new low-speed USB device number 4 using xhci_hcd
[57210.951289] usb 1-3: New USB device found, idVendor=17ef, idProduct=6099,
bcdDevice= 1.14
[57210.951293] usb 1-3: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
After doing kernel bisecting, we found the upstream commit
https://github.com/torvalds/linux/commit/90d28fb53d4a51299ff324dede015d5cb11b88a2
makes the difference. It indicates that the delay for the root hub from
power_on to power_good is not long enough. There was no problem if the delay is
100 ms. From the Hub Descriptor of the root hub, the value is 10 * 2
milliseconds. And the XHCI spec also says in section 5.4.8
"""
The host is required to have power stable to the port within 20 milliseconds
of the '0' to '1' transition of PP. If PPC = '1', software is responsible for
waiting 20ms.
"""
The commit seems to follow the SPEC but could cause problems on some
hubs.
[Reproduce Steps]
1. Plug the USB device to the physical port #1 and #4 which belongs to
high-speed hub.
2. Power on the machine.
3. Check if the USB device can work or not after boot.
[Results]
Expected:
All usb devices connect to the hub should work OK.
Actual:
USB devices connects to high-speed hub can not be probed.
[Additional Information]
Kernel Version: focal 5.4.0-78 and hirsute 5.11.0-26
[Upstream bug]
https://bugzilla.kernel.org/show_bug.cgi?id=214021
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1939638/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967336] Re: linux-azure: CONFIG_HIBERNATION=y
This bug is awaiting verification that the linux-azure/5.13.0-1022.26 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish -- 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/1967336 Title: linux-azure: CONFIG_HIBERNATION=y Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Azure arm64 tuned kernels do not support hibernation. [Test Plan] Microsoft tested [Where things could go wrong] Hibernation may fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967336/+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 1967166] Re: Azure: not enough RAM under 4GB for CVM
This bug is awaiting verification that the linux-azure/5.13.0-1022.26 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish -- 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/1967166 Title: Azure: not enough RAM under 4GB for CVM Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Can you please include one more patchset for the "no enough RAM under 4GB" issue for the v5.13 kernel (and v5.15 kernel): https://lwn.net/ml/linux-kernel/20220209122302.213882-2-ltyker...@gmail.com/ https://lwn.net/ml/linux-kernel/20220209122302.213882-3-ltyker...@gmail.com/ Without the two patches, currently the 5.13 kernel (and 5.15 kernel) can't boot as a CVM guest on Azure. :-( The background is: currently an Azure host only provides about 900 MB memory below the 4GB boundary while the swiotlb code (which is required by the CVM patchset) needs to allocate memory of a size of MIN(1GB, 6% of the total memory). There will be an Azure host update, with which the host will provide about 3GB memory below the 4GB boundary, but we still need to wait a few more weeks to know the ETA. Currently the above two patches can work around the issue from the guest side. [Test Case] Microsoft tested [Where things could go wrong] These patches could affect non-CVM instances. [Other Info] SF: #00323683 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967166/+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 1961329] Re: linux-azure: Update HV support to 5.17
This bug is awaiting verification that the linux-azure/5.13.0-1022.26 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish -- 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/1961329 Title: linux-azure: Update HV support to 5.17 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: New Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Microsoft has requested these commits be present in all Azure tuned kernels: ac0f7d42584125dab8039e60ab4ade48cc2db61c Drivers: hv: copy from message page only what's needed a276463b7aeb6186e7e4315cccb032773fb31b5d Drivers: hv: allocate the exact needed memory for messages 5cc415001bca8fe0e3f0ee6d58a953a314dd9751 Drivers: hv: avoid passing opaque pointer to vmbus_onmessage() b0a284dc65b401a508dc2c5ed7d465884220f607 Drivers: hv: make sure that 'struct vmbus_channel_message_header' compiles correctly 52c7803f9bd4b1f0ac6e2e3e6051415198cc06bd Drivers: hv: check VMBus messages lengths 06caa778d8b2fbcb4ac3878751e39d116424ba9b hv_utils: Add validation for untrusted Hyper-V values e99c4afbee07e9323e9191a20b24d74dbf815bdf Drivers: hv: vmbus: Initialize memory to be sent to the host fe8c1b18a27de4d6ca5d99b3ffb3125dc69a5b76 Drivers: hv: vmbus: Copy the hv_message in vmbus_on_msg_dpc() e3fa4b747f085d2cda09bba0533b86fa76038635 Drivers: hv: vmbus: Avoid use-after-free in vmbus_onoffer_rescind() e4d221b42354b2e2ddb9187a806afb651eee2cda Drivers: hv: vmbus: Resolve race condition in vmbus_onoffer_rescind() adae1e931acd8b430d31141a283ea06d4b705417 Drivers: hv: vmbus: Copy packets sent by Hyper-V out of the ring buffer 9d68cd9120e4e3af38f843e165631c323b86b4e4 hv_utils: Set the maximum packet size for VSS driver to the length of the receive buffer f1940d4e9cbe6208e7e77e433c587af108152a17 Drivers: hv: vmbus: Fix kernel crash upon unbinding a device from uio_hv_generic driver 007faec014cb5d26983c1f86fd08c6539b41392e x86/sev: Expose sev_es_ghcb_hv_call() for use by HyperV 0cc4f6d9f0b9f20f3f1e1149bdb6737c0b4e134a x86/hyperv: Initialize GHCB page in Isolation VM af788f355e343373490b7d2e361016e7c24a0ffa x86/hyperv: Initialize shared memory boundary in the Isolation VM. 810a521265023a1d5c6c081ea2d216bc63d422f5 x86/hyperv: Add new hvcall guest address host visibility support d4dccf353db80e209f262e3973c834e6e48ba9a9 Drivers: hv: vmbus: Mark vmbus ring buffer visible to host in Isolation VM faff44069ff538ccdfef187c4d7ec83d22dfb3a4 x86/hyperv: Add Write/Read MSR registers via ghcb page 20c89a559e00dfe352b73e867211a669113ae881 x86/hyperv: Add ghcb hvcall support for SNP VM f2f136c05fb6093818a3b3fefcba46231ac66a62 Drivers: hv: vmbus: Add SNP support for VMbus channel initiate message 9a8797722e4239242d0cb4cc4baa805df6ac979e Drivers: hv: vmbus: Initialize VMbus ring buffer for Isolation VM 1a5e91d8375fc8369207cc0b9894a324f2bbf1d9 swiotlb: Add swiotlb bounce buffer remap function for HV IVM c789b90a69045d1924bc0802ae0dce2bba05a04e x86/hyper-v: Add hyperv Isolation VM check in the cc_platform_has() 062a5c4260cdb734a4727230c58e38accf413315 hyper-v: Enable swiotlb bounce buffer for Isolation VM 743b237c3a7b0f5b44aa704aae8a1058877b6322 scsi: storvsc: Add Isolation VM support for storvsc driver 846da38de0e8224f2f94b885125cf1fd2d7b0d39 net: netvsc: Add Isolation VM support for netvsc driver 2deb55d9f57bb7a877c0d77115cc4077e1e974ff swiotlb: Add CONFIG_HAS_IOMEM check around swiotlb_mem_remap() 6a27e396ebb149fc47baccc1957a7a9dd70049a7 Drivers: hv: vmbus: Initialize request offers message for Isolation VM 4eea5332d67d8ae6ba5717ec0f4e671fdbd222e7 scsi: storvsc: Fix storvsc_queuecommand() memory leak 96d9d1fa5cd505078534113308ced0aa56d8da58 Drivers: hv: balloon: account for vmbus packet header in max_pkt_size [Test Plan] Microsoft tested [Where things could go wrong] Hyper-V guests may not work correctly. [Other Info] SF: #00323683 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1961329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : http
[Kernel-packages] [Bug 1967901] Re: [qxl] Xorg fails to start with "Screen(s) found, but none have a usable configuration."
This bug was fixed in the package xserver-xorg-video-qxl - 0.1.5+git20200331-3 --- xserver-xorg-video-qxl (0.1.5+git20200331-3) unstable; urgency=medium * configure-Simplify-fragile-libdrm-detection.patch: Fix detecting qxl_drm.h. (LP: #1967901) -- Timo Aaltonen Wed, 06 Apr 2022 10:23:41 +0300 ** Changed in: xserver-xorg-video-qxl (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967901 Title: [qxl] Xorg fails to start with "Screen(s) found, but none have a usable configuration." Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xserver-xorg-video-qxl package in Ubuntu: Fix Released Bug description: Ubuntu Desktop Jammy 20220405 It fails to boot to the live session in virt-manager and gnome-boxes. ubiquity-dm starts fine but the live session does. The graphical session keeps dying. If I switch from QXL to Virtio then it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967901/+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 1968062] [NEW] jammy/linux-aws hibernation timeout on xen instances
Public bug reported: Hibernation testing of jammy/linux-aws 5.15.0-1003-aws is failing on all xen instance types (c3/c4/i3/m3/m4/r3/r4/t2). The failure happens while attempting to resume from the first attempt to hibernate. Testing on nitro instances types (c5/m5/r5/t3) all pass. After the resume, the system is inaccessible via ssh. The console screenshot does change, but the console log obtained from `aws ec2 get- console-output` does not. ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Attachment added: "serial console log" https://bugs.launchpad.net/bugs/1968062/+attachment/5577675/+files/aws-jammy-all-c3.8xlarge-9-1.txt -- 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/1968062 Title: jammy/linux-aws hibernation timeout on xen instances Status in linux-aws package in Ubuntu: New Bug description: Hibernation testing of jammy/linux-aws 5.15.0-1003-aws is failing on all xen instance types (c3/c4/i3/m3/m4/r3/r4/t2). The failure happens while attempting to resume from the first attempt to hibernate. Testing on nitro instances types (c5/m5/r5/t3) all pass. After the resume, the system is inaccessible via ssh. The console screenshot does change, but the console log obtained from `aws ec2 get-console-output` does not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062/+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 1968062] Re: jammy/linux-aws hibernation timeout on xen instances
** Attachment added: "First screenshot after resume initiated" https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062/+attachment/5577677/+files/post-hibernate.01.jpg -- 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/1968062 Title: jammy/linux-aws hibernation timeout on xen instances Status in linux-aws package in Ubuntu: New Bug description: Hibernation testing of jammy/linux-aws 5.15.0-1003-aws is failing on all xen instance types (c3/c4/i3/m3/m4/r3/r4/t2). The failure happens while attempting to resume from the first attempt to hibernate. Testing on nitro instances types (c5/m5/r5/t3) all pass. After the resume, the system is inaccessible via ssh. The console screenshot does change, but the console log obtained from `aws ec2 get-console-output` does not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062/+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 1968062] Re: jammy/linux-aws hibernation timeout on xen instances
** Attachment added: "Last screenshot before hibernation" https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062/+attachment/5577676/+files/pre-hibernation.04.jpg -- 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/1968062 Title: jammy/linux-aws hibernation timeout on xen instances Status in linux-aws package in Ubuntu: New Bug description: Hibernation testing of jammy/linux-aws 5.15.0-1003-aws is failing on all xen instance types (c3/c4/i3/m3/m4/r3/r4/t2). The failure happens while attempting to resume from the first attempt to hibernate. Testing on nitro instances types (c5/m5/r5/t3) all pass. After the resume, the system is inaccessible via ssh. The console screenshot does change, but the console log obtained from `aws ec2 get-console-output` does not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062/+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 1968062] Re: jammy/linux-aws hibernation timeout on xen instances
This screenshot was taken a few minutes after the resume attempt. These ssm-amazon-agent messages repeat every 120 seconds with a new set. But this is all the progress we see from either the screenshot or the serial console. There are no new memory consumption messages indicating that the resume was complete. ** Attachment added: "Third screenshot after resume initiated" https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062/+attachment/5577703/+files/post-hibernate.16.jpg -- 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/1968062 Title: jammy/linux-aws hibernation timeout on xen instances Status in linux-aws package in Ubuntu: New Bug description: Hibernation testing of jammy/linux-aws 5.15.0-1003-aws is failing on all xen instance types (c3/c4/i3/m3/m4/r3/r4/t2). The failure happens while attempting to resume from the first attempt to hibernate. Testing on nitro instances types (c5/m5/r5/t3) all pass. After the resume, the system is inaccessible via ssh. The console screenshot does change, but the console log obtained from `aws ec2 get-console-output` does not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062/+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 1968062] Re: jammy/linux-aws hibernation timeout on xen instances
In this screenshot, it appears the system has resumed as the login screen is shown along with the messages from the hibernation memory consumption utility. The first memory message was generated prior to the hibernation (matches the message from the pre-hibernation image). The second message could have been generated before the hibernation or after the resume (there isn't enough data to know for sure). ** Attachment added: "Second screenshot after resume initiated" https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062/+attachment/5577701/+files/post-hibernate.12.jpg -- 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/1968062 Title: jammy/linux-aws hibernation timeout on xen instances Status in linux-aws package in Ubuntu: New Bug description: Hibernation testing of jammy/linux-aws 5.15.0-1003-aws is failing on all xen instance types (c3/c4/i3/m3/m4/r3/r4/t2). The failure happens while attempting to resume from the first attempt to hibernate. Testing on nitro instances types (c5/m5/r5/t3) all pass. After the resume, the system is inaccessible via ssh. The console screenshot does change, but the console log obtained from `aws ec2 get-console-output` does not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062/+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 1967892] Re: Fix flow table lookup failure with no originating ifindex
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1967892 Title: Fix flow table lookup failure with no originating ifindex Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug After the CT ifindex extension feature, flow table entries are populated with ifindex information which was intended to only be used for HW offload. This tuple ifindex is hashed in the flow table key, so it must be filled for lookup to be successful. But tuple ifindex is only relevant for the netfilter flowtables (nft), so it's not filled in act_ct flow table lookup, resulting in lookup failure, and no SW offload and no offload teardown for TCP connection FIN/RST packets. To fix this, add new tc ifindex field to tuple, which will only be used for offloading, not for lookup, as it will not be part of the tuple hash. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Generate traffic at high rate (e.g. using IXIA). The number of offloaded rules exposed in /sys/kernel/debug/mlx5/\:$BUS\:00.0/ct/offloaded should be in synch the number of generated connections. * What it could break. Perhaps nft offload – it is not part of our tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1967892/+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 1966937] Re: RM nvidia-graphics-drivers-495 superseded by 510
Removing packages from jammy: nvidia-graphics-drivers-495 495.46-0ubuntu3 in jammy Comment: Obsolete source package; LP: #1966937 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-495 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-495 in Ubuntu. https://bugs.launchpad.net/bugs/1966937 Title: RM nvidia-graphics-drivers-495 superseded by 510 Status in nvidia-graphics-drivers-495 package in Ubuntu: Fix Released Bug description: RM nvidia-graphics-drivers-495 superseded by 510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-495/+bug/1966937/+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 1951166] Re: nvidia_drm error at the end of kernel ring buffer (dmesg)
Same issue with Jammy 22.04. Linux Jupiter 5.15.0-25-generic #25-Ubuntu SMP Wed Mar 30 15:54:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux libnvidia-cfg1-510:amd64---510.60.02-0ubuntu1 libnvidia-common-510---510.60.02-0ubuntu1 libnvidia-compute-510:amd64---510.60.02-0ubuntu1 libnvidia-compute-510:i386---510.60.02-0ubuntu1 libnvidia-decode-510:amd64---510.60.02-0ubuntu1 libnvidia-decode-510:i386---510.60.02-0ubuntu1 libnvidia-egl-wayland1:amd64---1:1.1.9-1.1 libnvidia-encode-510:amd64---510.60.02-0ubuntu1 libnvidia-encode-510:i386---510.60.02-0ubuntu1 libnvidia-extra-510:amd64---510.60.02-0ubuntu1 libnvidia-fbc1-510:amd64---510.60.02-0ubuntu1 libnvidia-fbc1-510:i386---510.60.02-0ubuntu1 libnvidia-gl-510:amd64---510.60.02-0ubuntu1 libnvidia-gl-510:i386---510.60.02-0ubuntu1 nvidia-compute-utils-510---510.60.02-0ubuntu1 nvidia-dkms-510---510.60.02-0ubuntu1 nvidia-driver-510---510.60.02-0ubuntu1 nvidia-kernel-common-510---510.60.02-0ubuntu1 nvidia-kernel-source-510---510.60.02-0ubuntu1 nvidia-prime---0.8.17.1 nvidia-settings---510.47.03-0ubuntu1 nvidia-utils-510---510.60.02-0ubuntu1 screen-resolution-extra---0.18.2 xserver-xorg-video-nvidia-510---510.60.02-0ubuntu1 libnvidia-egl-wayland1:amd64---1:1.1.9-1.1 libva-wayland2:amd64---2.14.0-1 libwayland-client0:amd64---1.20.0-1 libwayland-client0:i386---1.20.0-1 libwayland-cursor0:amd64---1.20.0-1 libwayland-egl1:amd64---1.20.0-1 libwayland-server0:amd64---1.20.0-1 xwayland---2:22.1.1-1 xorg---1:7.7+23ubuntu2 xorg-docs-core---1:1.7.1-1.2 xserver-xorg---1:7.7+23ubuntu2 xserver-xorg-core---2:21.1.3-2ubuntu2 xserver-xorg-input-all---1:7.7+23ubuntu2 xserver-xorg-input-evdev---1:2.10.6-2build1 xserver-xorg-input-libinput---1.2.1-1 xserver-xorg-input-wacom---1:0.39.0-0ubuntu3 xserver-xorg-legacy---2:21.1.3-2ubuntu2 xserver-xorg-video-all---1:7.7+23ubuntu2 xserver-xorg-video-amdgpu---22.0.0-1build1 xserver-xorg-video-ati---1:19.1.0-2build3 xserver-xorg-video-fbdev---1:0.5.0-2build1 xserver-xorg-video-intel---2:2.99.917+git20210115-1 xserver-xorg-video-nouveau---1:1.0.17-2build1 xserver-xorg-video-nvidia-510---510.60.02-0ubuntu1 xserver-xorg-video-qxl---0.1.5+git20200331-2build1 xserver-xorg-video-radeon---1:19.1.0-2build3 xserver-xorg-video-vesa---1:2.5.0-1build4 xserver-xorg-video-vmware---1:13.3.0-3build1 [mer avr 6 17:53:32 2022] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1951166 Title: nvidia_drm error at the end of kernel ring buffer (dmesg) Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: Recently, I have noticed an error about nvidia_drm logged several times on my kernel ring buffer output occasionally. I am using the Nvidia driver version 470.82 on Ubuntu 20.04.03 LTS with kernel version 5.11.0-40-generic. My graphics card is RTX 2070 Mobile and I am using it via external G-SYNC monitor. Some output log describing the error from dmesg command: [16166.980676] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [19268.970816] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [19268.970930] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-470 470.82.00-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 01:20:13 2021 InstallationDate: Installed on 2021-09-24 (53 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1951166/+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 1966936] Re: RM nvidia-graphics-drivers-460-server superseded by 470-server
Removing packages from jammy: nvidia-graphics-drivers-460-server 460.106.00-0ubuntu2 in jammy Comment: Obsolete source package; LP: #1966936 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1966936 Title: RM nvidia-graphics-drivers-460-server superseded by 470-server Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Bug description: RM nvidia-graphics-drivers-460-server superseded by 470-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1966936/+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 1968077] [NEW] NVIDIA driver crashes with kernel NULL pointer dereference
Public bug reported: After leaving the system for a while and it turning the screen off the kernel crashes in the NVIDIA driver with the following: Apr 06 17:24:56 kore kernel: BUG: kernel NULL pointer dereference, address: 0070 Apr 06 17:24:56 kore kernel: #PF: supervisor read access in kernel mode Apr 06 17:24:56 kore kernel: #PF: error_code(0x) - not-present page Apr 06 17:24:56 kore kernel: PGD 0 P4D 0 Apr 06 17:24:56 kore kernel: Oops: [#1] SMP PTI Apr 06 17:24:56 kore kernel: CPU: 3 PID: 286160 Comm: Xorg Tainted: P C O 5.15.0-25-generic #25-Ubuntu Apr 06 17:24:56 kore kernel: Hardware name: Dell Inc. XPS 8930/0H0P0M, BIOS 1.1.15 07/01/2020 Apr 06 17:24:56 kore kernel: RIP: 0010:_nv002531kms+0x18/0x70 [nvidia_modeset] Apr 06 17:24:56 kore kernel: Code: ff c6 44 24 2f 01 eb af 66 2e 0f 1f 84 00 00 00 00 00 41 54 55 49 89 fc 53 89 d5 41 b8 04 00 00 00 ba 02 01 02 00 48 83 ec 10 <8b> 46 70 8b 3d 6f bb 0b 00 48 8d 4c 24 0c 89 ee 89 44 24 0c e8 6f Apr 06 17:24:56 kore kernel: RSP: 0018:bb9412827c90 EFLAGS: 00010286 Apr 06 17:24:56 kore kernel: RAX: RBX: 2002 RCX: 9ec1417f3980 Apr 06 17:24:56 kore kernel: RDX: 00020102 RSI: RDI: 9ec163d33008 Apr 06 17:24:56 kore kernel: RBP: 00010009 R08: 0004 R09: Apr 06 17:24:56 kore kernel: R10: 9ec5f1bd3000 R11: R12: 9ec163d33008 Apr 06 17:24:56 kore kernel: R13: 9ec163d330a0 R14: 0fff R15: 00010008 Apr 06 17:24:56 kore kernel: FS: 7f560151ea80() GS:9ec8a0ac() knlGS: Apr 06 17:24:56 kore kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 06 17:24:56 kore kernel: CR2: 0070 CR3: 0001ed208001 CR4: 003726e0 Apr 06 17:24:56 kore kernel: Call Trace: Apr 06 17:24:56 kore kernel: Apr 06 17:24:56 kore kernel: ? _nv002530kms+0xb3/0x150 [nvidia_modeset] Apr 06 17:24:56 kore kernel: ? _nv002308kms+0x499/0x680 [nvidia_modeset] Apr 06 17:24:56 kore kernel: ? _nv000453kms+0xa0/0xa0 [nvidia_modeset] Apr 06 17:24:56 kore kernel: ? _copy_from_user+0x2e/0x60 Apr 06 17:24:56 kore kernel: ? _nv000453kms+0xa0/0xa0 [nvidia_modeset] Apr 06 17:24:56 kore kernel: ? _nv000639kms+0x34/0x50 [nvidia_modeset] Apr 06 17:24:56 kore kernel: ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset] Apr 06 17:24:56 kore kernel: ? nvkms_ioctl+0x104/0x170 [nvidia_modeset] Apr 06 17:24:56 kore kernel: ? nvidia_frontend_unlocked_ioctl+0x58/0x90 [nvidia] Apr 06 17:24:56 kore kernel: ? __x64_sys_ioctl+0x91/0xc0 Apr 06 17:24:56 kore kernel: ? do_syscall_64+0x5c/0xc0 Apr 06 17:24:56 kore kernel: ? do_syscall_64+0x69/0xc0 Apr 06 17:24:56 kore kernel: ? syscall_exit_to_user_mode+0x27/0x50 Apr 06 17:24:56 kore kernel: ? do_syscall_64+0x69/0xc0 Apr 06 17:24:56 kore kernel: ? do_syscall_64+0x69/0xc0 Apr 06 17:24:56 kore kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xae I can reliable reproduce this on my current jammy system (proposed enabled, no pending updates) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-510 510.60.02-0ubuntu1 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 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 6 19:47:32 2022 InstallationDate: Installed on 2022-01-02 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: nvidia-graphics-drivers-510 UpgradeStatus: Upgraded to jammy on 2022-03-23 (13 days ago) ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1968077 Title: NVIDIA driver crashes with kernel NULL pointer dereference Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: After leaving the system for a while and it turning the screen off the kernel crashes in the NVIDIA driver with the following: Apr 06 17:24:56 kore kernel: BUG: kernel NULL pointer dereference, address: 0070 Apr 06 17:24:56 kore kernel: #PF: supervisor read access in kernel mode Apr 06 17:24:56 kore kernel: #PF: error_code(0x) - not-present page Apr 06 17:24:56 kore kernel: PGD 0 P4D 0 Apr 06 17:24:56 kore kernel: Oops: [#1] SMP PTI Apr 06 17:24:56 kore kernel: CPU: 3 PID: 286160 Comm: Xorg Tainted: P C O 5.15.0-25-generic #25-Ubuntu Apr 06 17:24:56 kore kernel: Hardware name: Dell Inc. XPS 8930/0H0P0M, BIOS 1.1.15 07/01/2020 Apr 06 17:24:56 kore kernel: RIP: 0010:_nv002531kms+0x18/0x70 [nvidia_modeset] Apr 06 17:24:56 kore kernel: Code: ff c6 44 24 2f 01 eb af
[Kernel-packages] [Bug 1968079] [NEW] impish:linux-azure - VM fails to initialize CX4 VF due to mem fragmentation (v2)
Public bug reported:
SRU Justification
[Impact]
The fix for LP: #1961632 failed to include commit
48f02eef7f764f33e520ed8009d293396ca690cd ("net/mlx5: Allocate individual
capability").
[Test case]
Microsoft tested
[Where things could go wrong]
mlx5 could fail to initialize
[Other Info]
SF: #00327011
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1968079
Title:
impish:linux-azure - VM fails to initialize CX4 VF due to mem
fragmentation (v2)
Status in linux-azure package in Ubuntu:
New
Bug description:
SRU Justification
[Impact]
The fix for LP: #1961632 failed to include commit
48f02eef7f764f33e520ed8009d293396ca690cd ("net/mlx5: Allocate
individual capability").
[Test case]
Microsoft tested
[Where things could go wrong]
mlx5 could fail to initialize
[Other Info]
SF: #00327011
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1968079/+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 1968079] Re: impish:linux-azure - VM fails to initialize CX4 VF due to mem fragmentation (v2)
Patches submitted: https://lists.ubuntu.com/archives/kernel-
team/2022-April/129251.html
** Also affects: linux-azure (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Impish)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Jammy)
Status: New => Fix Released
** Changed in: linux-azure (Ubuntu Impish)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Impish)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Impish)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Tags added: bot-stop-nagging
--
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/1968079
Title:
impish:linux-azure - VM fails to initialize CX4 VF due to mem
fragmentation (v2)
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Impish:
In Progress
Status in linux-azure source package in Jammy:
Fix Released
Bug description:
SRU Justification
[Impact]
The fix for LP: #1961632 failed to include commit
48f02eef7f764f33e520ed8009d293396ca690cd ("net/mlx5: Allocate
individual capability").
[Test case]
Microsoft tested
[Where things could go wrong]
mlx5 could fail to initialize
[Other Info]
SF: #00327011
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1968079/+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 1952933] Re: impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq
Upstream has gone ahead and reverted the problematic patches, and they are flowing into the various stable trees. ** Changed in: linux (Ubuntu Impish) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952933 Title: impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq Status in linux package in Ubuntu: In Progress Status in linux source package in Impish: In Progress Bug description: During MAAS deployment: [ 107.768146] Unable to handle kernel read from unreadable memory at virtual address domain : maas[ 107.943413] Mem abort info: rootserver: 10.229.32.21 rootpath: filename :[ 108.043666] ESR = 0x9604 lpxelinux.0 :: root=squash:http://10.229.32.21:5248/images/ubu[ 108.147045] EC = 0x25: DABT (current EL), IL = 32 bits ntu/arm64/xgene-uboot/impish/stable/squashfs :: mount_squash do[ 108.277541] SET = 0, FnV = 0 wnloading http://10.229.32.21:5248/images/ubuntu/arm64/xgene-ubo[ 108.380921] EA = 0, S1PTW = 0 ot/impish/stable/squashfs to /root.tmp.img Connecting to 10.229[ 108.485351] Data abort info: .32.21:5248 (10.229.32.21:5248) [ 108.586639] ISV = 0, ISS = 0x0004 [ 108.667060] CM = 0, WnR = 0 [ 108.702635] user pgtable: 4k pages, 48-bit VAs, pgdp=00401ce02000 root.tmp.img [ 108.779941] [] pgd=, p4d= 4% [ 108.884372] Internal error: Oops: 9604 [#1] SMP [ 108.948102] Modules linked in: raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx4_ib ib_uverbs ib_core mlx4_en mlx4_core gpio_keys_polled gpio_dwapb crct10dif_ce ahci_xgene gpio_xgene_sb aes_neon_bs aes_neon_blk crypto_simd cryptd [ 109.286243] CPU: 0 PID: 11 Comm: ksoftirqd/0 Not tainted 5.13.0-20-generic #20-Ubuntu [ 109.380233] Hardware name: HP ProLiant m400 Server Cartridge (DT) [ 109.453258] pstate: 6045 (nZCv daif +PAN -UAO -TCO BTYPE=--) [ 109.525342] pc : mlx4_en_poll_rx_cq+0xb4/0x17c [mlx4_en] [ 109.589087] lr : mlx4_en_poll_rx_cq+0x7c/0x17c [mlx4_en] [ 109.652828] sp : 8000129cbc60 [ 109.692470] x29: 8000129cbc60 x28: 012c x27: 000ff7e95fc0 [ 109.778115] x26: x25: 20908508 x24: 21b40940 [ 109.863763] x23: 20908508 x22: 20908400 x21: 21b4 [ 109.949409] x20: 0040 x19: 0040 x18: 0014 [ 110.035056] x17: 1122e350 x16: cb46f8bb x15: e2b6a183 [ 110.120703] x14: 26fff11e x13: 9312ff0b x12: [ 110.206349] x11: 0006 x10: 0040 x9 : 89119320 [ 110.291997] x8 : 08acdc00 x7 : 02c0 x6 : dff8 [ 110.377642] x5 : 0394 x4 : 03960040 x3 : 21c2 [ 110.463289] x2 : x1 : x0 : [ 110.548937] Call trace: [ 110.578147] mlx4_en_poll_rx_cq+0xb4/0x17c [mlx4_en] [ 110.637719] __napi_poll+0x40/0x1e0 [ 110.679551] net_rx_action+0x2d8/0x34c [ 110.724513] __do_softirq+0x128/0x388 [ 110.768432] run_ksoftirqd+0x6c/0x94 [ 110.811308] smpboot_thread_fn+0x15c/0x1a0 [ 110.860443] kthread+0x114/0x120 [ 110.899145] ret_from_fork+0x10/0x18 [ 110.942024] Code: 1100fc41 1a82b021 13067c21 93407c21 (f8617800) [ 111.015158] ---[ end trace b37ae99414884442 ]--- [ 111.070550] Kernel panic - not syncing: Oops: Fatal exception in interrupt [ 111.152964] SMP: stopping secondary CPUs [ 111.200016] Kernel Offset: 0x8 from 0x80001000 [ 111.265837] PHYS_OFFSET: 0x40 [ 111.309651] CPU features: 0x0251,0046 [ 111.361915] Memory Limit: none [ 111.398431] ---[ end Kernel panic - not syncing: Oops: Fatal exception in interrupt ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952933/+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 1967924] Re: One overlayfs fix has not been backported to the 5.13 bracnh
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-azure (Ubuntu)
Status: New => Confirmed
--
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/1967924
Title:
One overlayfs fix has not been backported to the 5.13 bracnh
Status in linux-azure package in Ubuntu:
Confirmed
Bug description:
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
map_files
BugLink: https://bugs.launchpad.net/bugs/1857257
...
Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
But it isn't in the 5.13 branch:
$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967924/+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 1968089] [NEW] Scarlett 2i2 USB DAC (1235:8210) has distorted playback on kernel 5.13.0-39
Public bug reported: After updating to kernel `linux-image-5.13.0-39-generic`, my Scarlett 2i2 began playing back distorted audio (sounds overdriven and slowed down, as if the sample rate is incorrect). To clarify, the device is reported in libusb as: Bus 001 Device 002: ID 1235:8210 Focusrite-Novation Scarlett 2i2 Camera This bug is also present in 5.13.0-37-generic, but is not present in 5.13.0-35-generic; booting the -35 kernel via GRUB resolves the problem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eta2014 F pulseaudio /dev/snd/controlC1: eta2014 F pulseaudio /dev/snd/pcmC1D0p: eta2014 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Apr 6 22:05:29 2022 InstallationDate: Installed on 2022-02-16 (49 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20L6S87J1L ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.13.0-35-generic N/A linux-backports-modules-5.13.0-35-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET66W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S87J1L dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrN24ET66W(1.41):bd10/20/2021:br1.41:efr1.21:svnLENOVO:pn20L6S87J1L:pvrThinkPadT480:rvnLENOVO:rn20L6S87J1L:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L6_BU_Think_FM_ThinkPadT480: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S87J1L dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968089 Title: Scarlett 2i2 USB DAC (1235:8210) has distorted playback on kernel 5.13.0-39 Status in linux package in Ubuntu: New Bug description: After updating to kernel `linux-image-5.13.0-39-generic`, my Scarlett 2i2 began playing back distorted audio (sounds overdriven and slowed down, as if the sample rate is incorrect). To clarify, the device is reported in libusb as: Bus 001 Device 002: ID 1235:8210 Focusrite-Novation Scarlett 2i2 Camera This bug is also present in 5.13.0-37-generic, but is not present in 5.13.0-35-generic; booting the -35 kernel via GRUB resolves the problem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eta2014 F pulseaudio /dev/snd/controlC1: eta2014 F pulseaudio /dev/snd/pcmC1D0p: eta2014 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Apr 6 22:05:29 2022 InstallationDate: Installed on 2022-02-16 (49 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20L6S87J1L ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.13.0-35-generic N/A linux-backports-modules-5.13.0-35-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET66W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S87J1L dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrN24ET66W(1.41):bd10/20/2021:br1.41:efr1.21:svnLENOVO:pn20L6S87J1L:pvrThinkPadT480:rvnLENOVO:rn20L6S87J1L:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L6_BU_Think_FM_ThinkPadT4
[Kernel-packages] [Bug 1968089] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968089 Title: Scarlett 2i2 USB DAC (1235:8210) has distorted playback on kernel 5.13.0-39 Status in linux package in Ubuntu: Confirmed Bug description: After updating to kernel `linux-image-5.13.0-39-generic`, my Scarlett 2i2 began playing back distorted audio (sounds overdriven and slowed down, as if the sample rate is incorrect). To clarify, the device is reported in libusb as: Bus 001 Device 002: ID 1235:8210 Focusrite-Novation Scarlett 2i2 Camera This bug is also present in 5.13.0-37-generic, but is not present in 5.13.0-35-generic; booting the -35 kernel via GRUB resolves the problem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eta2014 F pulseaudio /dev/snd/controlC1: eta2014 F pulseaudio /dev/snd/pcmC1D0p: eta2014 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Apr 6 22:05:29 2022 InstallationDate: Installed on 2022-02-16 (49 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20L6S87J1L ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.13.0-35-generic N/A linux-backports-modules-5.13.0-35-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET66W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S87J1L dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrN24ET66W(1.41):bd10/20/2021:br1.41:efr1.21:svnLENOVO:pn20L6S87J1L:pvrThinkPadT480:rvnLENOVO:rn20L6S87J1L:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L6_BU_Think_FM_ThinkPadT480: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S87J1L dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968089/+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 1968096] [NEW] [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z
You have been subscribed to a public bug: State the component where the Bug is occuring: kernel Indicate the nature of the problem by answering the below questions: - Is this problem reproducible? No No, steps unknown, but we have seen these before - Is the system sitting at a debugger (kdb, or xmon)? No - Is the system hung? No No, dumped and rebooted - Are there any custom patches installed? Yes On base system level (CloudAppliance) we are still running with the zfpc_proc module loaded. But no recent changes in the module and is running absolutely stable in HA (same kernel and userspace, Ubuntu 20.04 LTS) - Is there any special hardware that may be relevant to this problem? Yes We are running with mlx (cloud network adapters) installed. - Is access information for the machine the problem was found on available? Yes - Is the bug occuring in a userspace application? No - Was a stack trace produced? Yes This is what mention in first comment by @Boris Barth - Did the system produce an Oops message on the console?Yes [556585.270902] illegal operation: 0001 ilc:1 [#10] SMP [556585.270905] Modules linked in: vhost_net macvtap macvlan tap rpcsec_gss_krb5 auth_rpcgss nfsv3 nfs_acl nfs lockd grace fscache veth xt_statistic ipt_REJECT nf_reject_ipv4 ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_mangle xt_mark sunrpc nf_log_ipv6 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_set ip_set_hash_net ip_set_hash_ip ip_set tcp_diag inet_diag xt_comment xt_nat cls_cgroup sch_htb act_gact sch_multiq act_mirred act_pedit act_tunnel_key cls_flower act_police cls_u32 vxlan ip6_udp_tunnel udp_tunnel dummy nf_tables ebtable_filter ebtables xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key sch_ingress mlx5_ib ib_uverbs ib_core mlx5_core tls mlxfw ptp pps_core dm_integrity async_xor async_tx dm_bufio bonding xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat br_netfilter bridge vhost_vsock vmw_vsock_virtio_transport_common vhost vsock 8021q garp mrp stp llc xt_multiport xt_tcpudp qeth_l2 lcs ctcm fsm dasd_fba_mod aufs overlay scsi_dh_rdac [556585.270923] scsi_dh_emc s390_trng xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables iptable_filter bpfilter sch_fq_codel zFPC_proc(OE) zFPC_diag(OE) vfio_ap vfio_mdev drm vfio_iommu_type1 drm_panel_orientation_quirks i2c_core ip_tables x_tables scsi_dh_alua pkey zcrypt ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common chsc_sch qeth ccwgroup eadm_sch vfio_ccw mdev vfio btrfs libcrc32c crc32_vx_s390 xor zstd_compress raid6_pq dm_crypt virtio_blk dm_service_time dm_multipath zfcp scsi_transport_fc qdio dasd_eckd_mod dasd_mod zlib_deflate [last unloaded: tls] [556585.270945] CPU: 28 PID: 217741 Comm: worker Kdump: loaded Tainted: G DOE 5.4.0-90-generic #101-Ubuntu [556585.270947] Hardware name: IBM 8562 GT2 A00 (LPAR) [556585.270948] Krnl PSW : 0704d0018000 0002 (0x2) [556585.270951]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3 [556585.270953] Krnl GPRS: 03e010ebbcf8 0071c45e1ec0 [556585.270954] 002816f7b18c 0078dd36a4a0 00713a62f718 [556585.270955] 03e010ebbcf8 0068 0071c45e1ec0 [556585.270957]006090a12200 0c40 03ff80d6fb54 03e010ebbbf0 [556585.270959] Krnl Code:#: illegal >0002: illegal 0004: illegal 0006: illegal 0008: illegal 000a: illegal 000c: illegal 000e: illegal [556585.270967] Call Trace: [556585.270982] ([<03ff80d6fb1a>] rpcauth_lookup_credcache+0x5a/0x300 [sunrpc]) [556585.270993] [<03ff80e1182c>] nfs_ctx_key_to_expire+0xec/0x130 [nfs] [556585.271004] [<03ff80e1189c>] nfs_key_timeout_notify+0x2c/0x70 [nfs] [556585.271014] [<03ff80dfdf7e>] nfs_file_write+0x3e/0x320 [nfs] [556585.271016] [<0028165944a8>] new_sync_write+0x118/0x1b0 [556585.271017] [<002816594ee0>] vfs_write+0xb0/0x1b0 [556585.271019] [<002816596a1e>] ksys_pwrite64+0x7e/0xc0 [556585.271021] [<002816bb26b2>] system_call+0x2a6/0x2c8 - Was a system dump produced ie kdump, netdumpmp, or LKCD? Yes That is the kdump where the stacktrace from. Enter data below to accurately describe the problem: - Problem description: Null Pointer issue in nfs code running Ubuntu Ubuntu 18.04 w
[Kernel-packages] [Bug 1968096] [NEW] [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z
Public bug reported: State the component where the Bug is occuring: kernel Indicate the nature of the problem by answering the below questions: - Is this problem reproducible? No No, steps unknown, but we have seen these before - Is the system sitting at a debugger (kdb, or xmon)? No - Is the system hung? No No, dumped and rebooted - Are there any custom patches installed? Yes On base system level (CloudAppliance) we are still running with the zfpc_proc module loaded. But no recent changes in the module and is running absolutely stable in HA (same kernel and userspace, Ubuntu 20.04 LTS) - Is there any special hardware that may be relevant to this problem? Yes We are running with mlx (cloud network adapters) installed. - Is access information for the machine the problem was found on available? Yes - Is the bug occuring in a userspace application? No - Was a stack trace produced? Yes This is what mention in first comment by @Boris Barth - Did the system produce an Oops message on the console?Yes [556585.270902] illegal operation: 0001 ilc:1 [#10] SMP [556585.270905] Modules linked in: vhost_net macvtap macvlan tap rpcsec_gss_krb5 auth_rpcgss nfsv3 nfs_acl nfs lockd grace fscache veth xt_statistic ipt_REJECT nf_reject_ipv4 ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_mangle xt_mark sunrpc nf_log_ipv6 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_set ip_set_hash_net ip_set_hash_ip ip_set tcp_diag inet_diag xt_comment xt_nat cls_cgroup sch_htb act_gact sch_multiq act_mirred act_pedit act_tunnel_key cls_flower act_police cls_u32 vxlan ip6_udp_tunnel udp_tunnel dummy nf_tables ebtable_filter ebtables xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key sch_ingress mlx5_ib ib_uverbs ib_core mlx5_core tls mlxfw ptp pps_core dm_integrity async_xor async_tx dm_bufio bonding xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat br_netfilter bridge vhost_vsock vmw_vsock_virtio_transport_common vhost vsock 8021q garp mrp stp llc xt_multiport xt_tcpudp qeth_l2 lcs ctcm fsm dasd_fba_mod aufs overlay scsi_dh_rdac [556585.270923] scsi_dh_emc s390_trng xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables iptable_filter bpfilter sch_fq_codel zFPC_proc(OE) zFPC_diag(OE) vfio_ap vfio_mdev drm vfio_iommu_type1 drm_panel_orientation_quirks i2c_core ip_tables x_tables scsi_dh_alua pkey zcrypt ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common chsc_sch qeth ccwgroup eadm_sch vfio_ccw mdev vfio btrfs libcrc32c crc32_vx_s390 xor zstd_compress raid6_pq dm_crypt virtio_blk dm_service_time dm_multipath zfcp scsi_transport_fc qdio dasd_eckd_mod dasd_mod zlib_deflate [last unloaded: tls] [556585.270945] CPU: 28 PID: 217741 Comm: worker Kdump: loaded Tainted: G DOE 5.4.0-90-generic #101-Ubuntu [556585.270947] Hardware name: IBM 8562 GT2 A00 (LPAR) [556585.270948] Krnl PSW : 0704d0018000 0002 (0x2) [556585.270951]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3 [556585.270953] Krnl GPRS: 03e010ebbcf8 0071c45e1ec0 [556585.270954] 002816f7b18c 0078dd36a4a0 00713a62f718 [556585.270955] 03e010ebbcf8 0068 0071c45e1ec0 [556585.270957]006090a12200 0c40 03ff80d6fb54 03e010ebbbf0 [556585.270959] Krnl Code:#: illegal >0002: illegal 0004: illegal 0006: illegal 0008: illegal 000a: illegal 000c: illegal 000e: illegal [556585.270967] Call Trace: [556585.270982] ([<03ff80d6fb1a>] rpcauth_lookup_credcache+0x5a/0x300 [sunrpc]) [556585.270993] [<03ff80e1182c>] nfs_ctx_key_to_expire+0xec/0x130 [nfs] [556585.271004] [<03ff80e1189c>] nfs_key_timeout_notify+0x2c/0x70 [nfs] [556585.271014] [<03ff80dfdf7e>] nfs_file_write+0x3e/0x320 [nfs] [556585.271016] [<0028165944a8>] new_sync_write+0x118/0x1b0 [556585.271017] [<002816594ee0>] vfs_write+0xb0/0x1b0 [556585.271019] [<002816596a1e>] ksys_pwrite64+0x7e/0xc0 [556585.271021] [<002816bb26b2>] system_call+0x2a6/0x2c8 - Was a system dump produced ie kdump, netdumpmp, or LKCD? Yes That is the kdump where the stacktrace from. Enter data below to accurately describe the problem: - Problem description: Null Pointer issue in nfs code running Ubuntu Ubuntu 18.04 with HWE kernel 5.4 o
[Kernel-packages] [Bug 1965241] Re: Include DPC Fixes in Ubuntu 22.04 and 20.04
I found that this additional patch was also needed. Pcie_port_device_iter was added in 5.16 and referenced in the "PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset" patch commit 3134689f98f9e09004a4727370adc46e7635b4be Author: Lukas Wunner Date: Fri Oct 15 13:58:40 2021 -0500 PCI/portdrv: Rename pm_iter() to pcie_port_device_iter() Rename pm_iter() to pcie_port_device_iter() and make it visible outside CONFIG_PM and portdrv_core.c so it can be used for pciehp slot reset recovery. [bhelgaas: split into its own patch] Link: https://lore.kernel.org/linux-pci/08c046b0-c9f2-3489-eeef-7e7aca435...@gmail.com/ Link: https://lore.kernel.org/r/251f4edcc04c14f873ff1c967bc686169cd07d2d.1627638184.git.lu...@wunner.de Signed-off-by: Lukas Wunner Signed-off-by: Bjorn Helgaas -- 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/1965241 Title: Include DPC Fixes in Ubuntu 22.04 and 20.04 Status in dellserver: New Status in linux package in Ubuntu: In Progress Bug description: SRU Justification: Impact: Recovery from DownPort Containment events fail and the NVMe endpoint is not accessible in some scenarios. Fix: These are some of the DPC fixes which help in handling some of the failure cases of DownPort Containment events. Upstream kernel patches to be included into Ubuntu 22.04 and into Ubuntu 20.04.5: Already in Jammy as of Ubuntu-5.15.0-1.1 PCI/portdrv: Enable Bandwidth Notification only if port supports it https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6&id=00823dcbdd415c868390feaca16f0265101efab4 Not yet pulled PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6&id=ea401499e943c307e6d44af6c2b4e068643e7884 Test Case: To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1965241/+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 1965241] Re: Include DPC Fixes in Ubuntu 22.04 and 20.04
I have provided test kernels at the following link: https://people.canonical.com/~mreed/lp_1965241_DPC_Fix/ -- 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/1965241 Title: Include DPC Fixes in Ubuntu 22.04 and 20.04 Status in dellserver: New Status in linux package in Ubuntu: In Progress Bug description: SRU Justification: Impact: Recovery from DownPort Containment events fail and the NVMe endpoint is not accessible in some scenarios. Fix: These are some of the DPC fixes which help in handling some of the failure cases of DownPort Containment events. Upstream kernel patches to be included into Ubuntu 22.04 and into Ubuntu 20.04.5: Already in Jammy as of Ubuntu-5.15.0-1.1 PCI/portdrv: Enable Bandwidth Notification only if port supports it https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6&id=00823dcbdd415c868390feaca16f0265101efab4 Not yet pulled PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6&id=ea401499e943c307e6d44af6c2b4e068643e7884 Test Case: To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1965241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-ibm/5.4.0.1020.20)
All autopkgtests for the newly accepted linux-meta-ibm (5.4.0.1020.20) for focal have finished running. The following regressions have been reported in tests triggered by the package: snapd/2.54.3+20.04.1ubuntu0.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-ibm [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 1966093] Re: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish
Test results for 510 are available at https://docs.google.com/spreadsheets/d/1VjZ1Jx9vuQPFtmTU-r9hJYDWlrA5dyopHQfQ9LWitlg/edit?usp=sharing Test results for 390 are available at https://docs.google.com/spreadsheets/d/1hZrugw1J2oNKFf4ZZzhBE5wmE1HWjZGSOqk6Llt_0ZM/edit?usp=sharing No regression found for both. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1966093 Title: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Committed Status in linux-restricted-modules source package in Bionic: Triaged Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Focal: Triaged Status in nvidia-graphics-drivers-390 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-510 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Impish: Triaged Status in nvidia-graphics-drivers-390 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-510 source package in Impish: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] === 510 impish/focal/bionic === * New upstream release (LP: #1966093): - Added support for the following GPUs: NVIDIA RTX A4000H NVIDIA RTX A5500 - Fixed a bug that could cause displays with HDMI or DisplayPort audio to be deselected as the default audio output device after resuming from suspend. - Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT- switches - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:" in /proc/driver/nvidia/gpus//information to be "Unknown" for some GPUs. === 390 impish/focal/bionic === * New upstream release (LP: #1966093): - Fixed a bug where vkCreateSwapchain could cause the X Server to crash when an invalid imageFormat was provided. - Fixed a driver installation failure on Linux kernel 5.11 release candidates, where the NVIDIA kernel module failed to build with error "fatal error: asm/kmap_types.h: No such file or directory". [ Dimitri John Ledkov ] * debian/dkms_nvidia/patches/buildfix_kernel_5.13_armhf.patch: - Fix armhf builds. * debian/dkms_nvidia/patches/buildfix_kernel_5.17.patch: - Fix build failure with Linux 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1966093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968104] [NEW] [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk
Public bug reported: After installing OS in a SW RAID1 disk (this disk is created in UEFI setup - via Intel VMD/VROC), the dmesg shows the following GPT messages after the installation and booting into the OS. --- [8.715400] GPT:Primary header thinks Alt. header is not at the end of the disk. [8.716425] GPT:419430399 != 7814037167 [8.717422] GPT:Alternate GPT header not at the end of the disk. [8.718224] GPT:419430399 != 7814037167 [8.719007] GPT: Use GNU Parted to correct GPT errors. --- [Note] 1. The issue does not happen when installing OS in a SW RAID0 disk, a SW RAID5 disk or a SW RAID10 disk. 2. Kernel community had the patch submission/discussion about this issue (in 2016): https://lore.kernel.org/lkml/1476699630-127009-1-git-send-email-h...@suse.de/. However, the patch is still pending there due to this feedback: https://lore.kernel.org/lkml/20161018095637.tgdjehscttskq...@ws.net.home/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-bug linux ** Attachment added: "dmesg" https://bugs.launchpad.net/bugs/1968104/+attachment/5577765/+files/dmesg -- 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/1968104 Title: [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk Status in linux package in Ubuntu: New Bug description: After installing OS in a SW RAID1 disk (this disk is created in UEFI setup - via Intel VMD/VROC), the dmesg shows the following GPT messages after the installation and booting into the OS. --- [8.715400] GPT:Primary header thinks Alt. header is not at the end of the disk. [8.716425] GPT:419430399 != 7814037167 [8.717422] GPT:Alternate GPT header not at the end of the disk. [8.718224] GPT:419430399 != 7814037167 [8.719007] GPT: Use GNU Parted to correct GPT errors. --- [Note] 1. The issue does not happen when installing OS in a SW RAID0 disk, a SW RAID5 disk or a SW RAID10 disk. 2. Kernel community had the patch submission/discussion about this issue (in 2016): https://lore.kernel.org/lkml/1476699630-127009-1-git-send-email-h...@suse.de/. However, the patch is still pending there due to this feedback: https://lore.kernel.org/lkml/20161018095637.tgdjehscttskq...@ws.net.home/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968104/+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 1968104] 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 1968104 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/1968104 Title: [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk Status in linux package in Ubuntu: Incomplete Bug description: After installing OS in a SW RAID1 disk (this disk is created in UEFI setup - via Intel VMD/VROC), the dmesg shows the following GPT messages after the installation and booting into the OS. --- [8.715400] GPT:Primary header thinks Alt. header is not at the end of the disk. [8.716425] GPT:419430399 != 7814037167 [8.717422] GPT:Alternate GPT header not at the end of the disk. [8.718224] GPT:419430399 != 7814037167 [8.719007] GPT: Use GNU Parted to correct GPT errors. --- [Note] 1. The issue does not happen when installing OS in a SW RAID0 disk, a SW RAID5 disk or a SW RAID10 disk. 2. Kernel community had the patch submission/discussion about this issue (in 2016): https://lore.kernel.org/lkml/1476699630-127009-1-git-send-email-h...@suse.de/. However, the patch is still pending there due to this feedback: https://lore.kernel.org/lkml/20161018095637.tgdjehscttskq...@ws.net.home/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968104/+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 1958006] Re: multiple UBSAN warnings in Intel IPU6 camera driver at boot
Upstream fix in https://github.com/intel/ipu6-drivers/commit/8dcb7d8df28fd311a72f3d996b02231e38aac8a7 -- 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/1958006 Title: multiple UBSAN warnings in Intel IPU6 camera driver at boot Status in linux package in Ubuntu: Confirmed Bug description: UBSAN is turned on by default in Ubuntu 5.15 kernel. While Intel IPU6 driver is still suffering from bug 1958004, intel_iommu issue, so these are found with intel_iommu=off. [ 51.469485] [ 51.469490] UBSAN: invalid-load in /tmp/kernel-vicamo-8789bd62d725-b752/build/include/linux/dma-buf-map.h:224:9 [ 51.469494] load of value 2 is not a valid value for type '_Bool' [ 51.469497] CPU: 8 PID: 1315 Comm: camerasrc0:src Tainted: G O 5.15.0-2017-generic #17~20.04.1+lp1955383.2 [ 51.469500] Hardware name: Dell Inc. XPS 9320/, BIOS 0.2.7 12/02/2021 [ 51.469501] Call Trace: [ 51.469504] [ 51.469508] dump_stack_lvl+0x4a/0x5f [ 51.469516] dump_stack+0x10/0x12 [ 51.469519] ubsan_epilogue+0x9/0x45 [ 51.469523] __ubsan_handle_load_invalid_value.cold+0x44/0x49 [ 51.469530] dma_buf_vmap.cold+0x38/0x3d [ 51.469537] ipu_psys_mapbuf_locked+0x178/0x450 [intel_ipu6_psys] [ 51.469545] ipu_psys_ioctl+0x148/0x4f0 [intel_ipu6_psys] [ 51.469550] ? __fget_files+0xa7/0xd0 [ 51.469556] __x64_sys_ioctl+0x91/0xc0 [ 51.469560] do_syscall_64+0x59/0xc0 [ 51.469564] ? do_user_addr_fault+0x1dc/0x650 [ 51.469567] ? irqentry_exit_to_user_mode+0x9/0x20 [ 51.469570] ? irqentry_exit+0x19/0x30 [ 51.469573] ? exc_page_fault+0x89/0x160 [ 51.469576] ? asm_exc_page_fault+0x8/0x30 [ 51.469581] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 51.469585] RIP: 0033:0x7fa5e047250b [ 51.469588] Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48 [ 51.469589] RSP: 002b:7fa5debfa298 EFLAGS: 0246 ORIG_RAX: 0010 [ 51.469592] RAX: ffda RBX: 7fa5d0004000 RCX: 7fa5e047250b [ 51.469593] RDX: 001f RSI: c0044102 RDI: 001e [ 51.469595] RBP: 7fa5d4a371e0 R08: R09: 007c [ 51.469596] R10: 7fa5debfa120 R11: 0246 R12: [ 51.469597] R13: 7fa5d4a31bc0 R14: 7fa5debfa36c R15: 7fa5debfa430 [ 51.469598] [ 51.469599] [ 52.050608] [ 52.050620] UBSAN: array-index-out-of-bounds in /tmp/kernel-vicamo-8789bd62d725-b752/build/drivers/media/pci/intel/ipu6/ipu-resources.c:633:30 [ 52.050631] index -1 is out of range for type 'ipu_resource_alloc [128]' [ 52.050637] CPU: 8 PID: 803 Comm: psys_sched_cmd Tainted: G O 5.15.0-2017-generic #17~20.04.1+lp1955383.2 [ 52.050647] Hardware name: Dell Inc. XPS 9320/, BIOS 0.2.7 12/02/2021 [ 52.050651] Call Trace: [ 52.050656] [ 52.050664] dump_stack_lvl+0x4a/0x5f [ 52.050692] dump_stack+0x10/0x12 [ 52.050703] ubsan_epilogue+0x9/0x45 [ 52.050716] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [ 52.050731] ipu_psys_allocate_resources+0x4de/0x670 [intel_ipu6_psys] [ 52.050761] ipu_psys_ppg_start+0xff/0x250 [intel_ipu6_psys] [ 52.050781] ? ipu_psys_scheduler_ppg_start+0x1b6/0x510 [intel_ipu6_psys] [ 52.050801] ipu_psys_scheduler_ppg_start+0x429/0x510 [intel_ipu6_psys] [ 52.050819] ipu_psys_run_next+0x1c4/0x7c0 [intel_ipu6_psys] [ 52.050836] ipu_psys_sched_cmd+0x6d/0x130 [intel_ipu6_psys] [ 52.050850] ? __wake_up_pollfree+0x40/0x40 [ 52.050859] ? psys_isr_threaded+0xc0/0xc0 [intel_ipu6_psys] [ 52.050874] kthread+0x127/0x150 [ 52.050884] ? set_kthread_struct+0x40/0x40 [ 52.050893] ret_from_fork+0x1f/0x30 [ 52.050911] [ 52.050914] [ 52.050924] [ 52.050926] UBSAN: shift-out-of-bounds in /tmp/kernel-vicamo-8789bd62d725-b752/build/drivers/media/pci/intel/ipu6/ipu-resources.c:652:15 [ 52.050932] shift exponent 34 is too large for 32-bit type 'unsigned int' [ 52.050938] CPU: 8 PID: 803 Comm: psys_sched_cmd Tainted: G O 5.15.0-2017-generic #17~20.04.1+lp1955383.2 [ 52.050944] Hardware name: Dell Inc. XPS 9320/, BIOS 0.2.7 12/02/2021 [ 52.050947] Call Trace: [ 52.050949] [ 52.050951] dump_stack_lvl+0x4a/0x5f [ 52.05096
[Kernel-packages] [Bug 1968110] [NEW] can not disable zfs snapshot/pool/filesystem scanning in grub
Public bug reported: I've currently got an issue where encrypted backups on an external pool whose key are unavailable are being scanned during `grub-mkconfig`, causing it to error out during `zfs_mount_at()` because the key is unavailable. I've traced it down to the /etc/grub.d/10_linux_zfs support file which scans pools and filesystems indiscriminately, no options to configure in /etc/default/grub or /etc/default/zfs. Although, /etc/default/zfs has the `ZPOOL_IMPORT_ALL_VISIBLE='no'` that I have set explicitly, and it is ignored during grub-mkconfig only. Even if my zpool isn't imported, it's scanned (I hear the HDD spin up) and erroneously included. Package: grub-common Status: install ok installed Priority: optional Section: admin Installed-Size: 13836 Maintainer: Ubuntu Developers Architecture: amd64 Multi-Arch: foreign Source: grub2 Version: 2.06-2ubuntu6 ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1968110 Title: can not disable zfs snapshot/pool/filesystem scanning in grub Status in zfs-linux package in Ubuntu: New Bug description: I've currently got an issue where encrypted backups on an external pool whose key are unavailable are being scanned during `grub- mkconfig`, causing it to error out during `zfs_mount_at()` because the key is unavailable. I've traced it down to the /etc/grub.d/10_linux_zfs support file which scans pools and filesystems indiscriminately, no options to configure in /etc/default/grub or /etc/default/zfs. Although, /etc/default/zfs has the `ZPOOL_IMPORT_ALL_VISIBLE='no'` that I have set explicitly, and it is ignored during grub-mkconfig only. Even if my zpool isn't imported, it's scanned (I hear the HDD spin up) and erroneously included. Package: grub-common Status: install ok installed Priority: optional Section: admin Installed-Size: 13836 Maintainer: Ubuntu Developers Architecture: amd64 Multi-Arch: foreign Source: grub2 Version: 2.06-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1968110/+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 1967726] Re: Disabled S3 ACPI standby state on DELL Precision M3560
Hi, S3 is no longer required in UEFI for certification, the machine can enter suspend with Suspend-to-idle S0ix. [1] http://certification- static.canonical.com/docs/coverage_by_release/20.04/UbuntuDesktopCoverage2004.pdf ** Changed in: linux-signed-oem-5.14 (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1967726 Title: Disabled S3 ACPI standby state on DELL Precision M3560 Status in linux-signed-oem-5.14 package in Ubuntu: Won't Fix Bug description: Device information for https://answers.launchpad.net/ubuntu- certification/+question/701164 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1031-oem 5.14.0-1031.34 ProcVersionSignature: Ubuntu 5.14.0-1031.34-oem 5.14.21 Uname: Linux 5.14.0-1031-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 4 09:58:28 2022 InstallationDate: Installed on 2021-12-06 (118 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1967726/+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 1968096] Re: [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968096 Title: [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: State the component where the Bug is occuring: kernel Indicate the nature of the problem by answering the below questions: - Is this problem reproducible? No No, steps unknown, but we have seen these before - Is the system sitting at a debugger (kdb, or xmon)? No - Is the system hung? No No, dumped and rebooted - Are there any custom patches installed? Yes On base system level (CloudAppliance) we are still running with the zfpc_proc module loaded. But no recent changes in the module and is running absolutely stable in HA (same kernel and userspace, Ubuntu 20.04 LTS) - Is there any special hardware that may be relevant to this problem? Yes We are running with mlx (cloud network adapters) installed. - Is access information for the machine the problem was found on available? Yes - Is the bug occuring in a userspace application? No - Was a stack trace produced? Yes This is what mention in first comment by @Boris Barth - Did the system produce an Oops message on the console? Yes [556585.270902] illegal operation: 0001 ilc:1 [#10] SMP [556585.270905] Modules linked in: vhost_net macvtap macvlan tap rpcsec_gss_krb5 auth_rpcgss nfsv3 nfs_acl nfs lockd grace fscache veth xt_statistic ipt_REJECT nf_reject_ipv4 ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_mangle xt_mark sunrpc nf_log_ipv6 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_set ip_set_hash_net ip_set_hash_ip ip_set tcp_diag inet_diag xt_comment xt_nat cls_cgroup sch_htb act_gact sch_multiq act_mirred act_pedit act_tunnel_key cls_flower act_police cls_u32 vxlan ip6_udp_tunnel udp_tunnel dummy nf_tables ebtable_filter ebtables xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key sch_ingress mlx5_ib ib_uverbs ib_core mlx5_core tls mlxfw ptp pps_core dm_integrity async_xor async_tx dm_bufio bonding xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat br_netfilter bridge vhost_vsock vmw_vsock_virtio_transport_common vhost vsock 8021q garp mrp stp llc xt_multiport xt_tcpudp qeth_l2 lcs ctcm fsm dasd_fba_mod aufs overlay scsi_dh_rdac [556585.270923] scsi_dh_emc s390_trng xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables iptable_filter bpfilter sch_fq_codel zFPC_proc(OE) zFPC_diag(OE) vfio_ap vfio_mdev drm vfio_iommu_type1 drm_panel_orientation_quirks i2c_core ip_tables x_tables scsi_dh_alua pkey zcrypt ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common chsc_sch qeth ccwgroup eadm_sch vfio_ccw mdev vfio btrfs libcrc32c crc32_vx_s390 xor zstd_compress raid6_pq dm_crypt virtio_blk dm_service_time dm_multipath zfcp scsi_transport_fc qdio dasd_eckd_mod dasd_mod zlib_deflate [last unloaded: tls] [556585.270945] CPU: 28 PID: 217741 Comm: worker Kdump: loaded Tainted: G DOE 5.4.0-90-generic #101-Ubuntu [556585.270947] Hardware name: IBM 8562 GT2 A00 (LPAR) [556585.270948] Krnl PSW : 0704d0018000 0002 (0x2) [556585.270951]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3 [556585.270953] Krnl GPRS: 03e010ebbcf8 0071c45e1ec0 [556585.270954] 002816f7b18c 0078dd36a4a0 00713a62f718 [556585.270955] 03e010ebbcf8 0068 0071c45e1ec0 [556585.270957]006090a12200 0c40 03ff80d6fb54 03e010ebbbf0 [556585.270959] Krnl Code:#: illegal >0002: illegal 0004: illegal 0006: illegal 0008: illegal 000a: illegal 000c: illegal 000e: illegal [556585.270967] Call Trace: [556585.270982] ([<03ff80d6fb1a>] rpcauth_lookup_credcache+0x5a/0x300 [sunrpc]) [556585.270993] [<03ff80e1182c>] nfs_ctx_key_to_expire+0xec/0x130 [nfs] [556585.2710
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.4/5.4.0.108.122~18.04.93)
All autopkgtests for the newly accepted linux-meta-hwe-5.4 (5.4.0.108.122~18.04.93) for bionic have finished running. The following regressions have been reported in tests triggered by the package: acpi-call/1.1.0-4 (s390x, ppc64el) virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (s390x, amd64, ppc64el) asic0x/1.0.1-1 (s390x) virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) v4l2loopback/0.10.0-1ubuntu1.2 (s390x) snapd/2.54.3+18.04.2ubuntu0.2 (arm64, s390x, amd64, ppc64el) kpatch/0.5.0-0ubuntu1.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-hwe-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954926] Re: Focal: CIFS stable updates
Ran several validations on this. The issue for which the fixes were submitted works as advertised. Also ran several xfstests using various mount scenarios (DFS and regular) against various file servers (Azure, Windows, samba). -- 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/1954926 Title: Focal: CIFS stable updates Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux-azure source package in Focal: Fix Released Bug description: SRU Justification [Impact] Backport several stable updates to v5.4 Azure [Test Case] Microsoft tested [Where things could go wrong] Samba connections could fail [Other Info] SF: #00324495 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954926/+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 1968096] Re: [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z
Thanks for raising this. First of all I've noticed that the kernel in use is pretty outdated (package 'linux-meta-hwe-5.4 (5.4.0.90.101~18.04.80', changelog date 22 Oct 2021) and about half a year old - the current one is '5.4.0-107-generic' (package '5.4.0.107.121~18.04.92'). The delta between 5.4.0.107.121 and 5.4.0.90.101 are about 2000 commits and more than 20 are NFS related and also some about vfs. Hence I need to ask to update the system to the latest 'linux-image-generic-hwe-18.04' in 'bionic-updates' (5.4.0-107-generic) to be on the latest (and supported) level. (A test with '5.4.0.108.122~18.04.93' from 'bionic-proposed' would be ideal on top.) It also looks like a kernel dump was created, could you please share this dump (ideally from the current kernel) for further analysis (either via IBM Box or Canonical's anon. ftp 'http://archive.admin.canonical.com/')? ** Changed in: ubuntu-z-systems 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/1968096 Title: [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Bug description: State the component where the Bug is occuring: kernel Indicate the nature of the problem by answering the below questions: - Is this problem reproducible? No No, steps unknown, but we have seen these before - Is the system sitting at a debugger (kdb, or xmon)? No - Is the system hung? No No, dumped and rebooted - Are there any custom patches installed? Yes On base system level (CloudAppliance) we are still running with the zfpc_proc module loaded. But no recent changes in the module and is running absolutely stable in HA (same kernel and userspace, Ubuntu 20.04 LTS) - Is there any special hardware that may be relevant to this problem? Yes We are running with mlx (cloud network adapters) installed. - Is access information for the machine the problem was found on available? Yes - Is the bug occuring in a userspace application? No - Was a stack trace produced? Yes This is what mention in first comment by @Boris Barth - Did the system produce an Oops message on the console? Yes [556585.270902] illegal operation: 0001 ilc:1 [#10] SMP [556585.270905] Modules linked in: vhost_net macvtap macvlan tap rpcsec_gss_krb5 auth_rpcgss nfsv3 nfs_acl nfs lockd grace fscache veth xt_statistic ipt_REJECT nf_reject_ipv4 ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_mangle xt_mark sunrpc nf_log_ipv6 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_set ip_set_hash_net ip_set_hash_ip ip_set tcp_diag inet_diag xt_comment xt_nat cls_cgroup sch_htb act_gact sch_multiq act_mirred act_pedit act_tunnel_key cls_flower act_police cls_u32 vxlan ip6_udp_tunnel udp_tunnel dummy nf_tables ebtable_filter ebtables xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key sch_ingress mlx5_ib ib_uverbs ib_core mlx5_core tls mlxfw ptp pps_core dm_integrity async_xor async_tx dm_bufio bonding xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat br_netfilter bridge vhost_vsock vmw_vsock_virtio_transport_common vhost vsock 8021q garp mrp stp llc xt_multiport xt_tcpudp qeth_l2 lcs ctcm fsm dasd_fba_mod aufs overlay scsi_dh_rdac [556585.270923] scsi_dh_emc s390_trng xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables iptable_filter bpfilter sch_fq_codel zFPC_proc(OE) zFPC_diag(OE) vfio_ap vfio_mdev drm vfio_iommu_type1 drm_panel_orientation_quirks i2c_core ip_tables x_tables scsi_dh_alua pkey zcrypt ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common chsc_sch qeth ccwgroup eadm_sch vfio_ccw mdev vfio btrfs libcrc32c crc32_vx_s390 xor zstd_compress raid6_pq dm_crypt virtio_blk dm_service_time dm_multipath zfcp scsi_transport_fc qdio dasd_eckd_mod dasd_mod zlib_deflate [last unloaded: tls] [556585.270945] CPU: 28 PID: 217741 Comm: worker Kdump: loaded Tainted: G DOE 5.4.0-90-generic #101-Ubuntu [556585.270947] Hardware name: IBM 8562 GT2 A00 (LPAR) [556585.270948] Krnl PSW : 0704d0018000 0002 (0x2) [556585.270951]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3 [556585.270953] Krnl GPRS: 03e010ebbcf8 0071c45e1ec0 [556585.270954] 002816f7b18c 0078dd36a4a0 00713a62f718 [556585.270955] 03e010ebbcf8 0068 0071c45e1ec0 [556585.270957]006090a12200 0c40 03ff80d6fb54 03e010ebbbf0 [556585.270959] Krnl Code:#: illegal
[Kernel-packages] [Bug 1968089] Re: Scarlett 2i2 USB DAC (1235:8210) has distorted playback on kernel 5.13.0-39
*** This bug is a duplicate of bug 1966066 *** https://bugs.launchpad.net/bugs/1966066 ** This bug has been marked a duplicate of bug 1966066 audio from external sound card is distorted -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968089 Title: Scarlett 2i2 USB DAC (1235:8210) has distorted playback on kernel 5.13.0-39 Status in linux package in Ubuntu: Confirmed Bug description: After updating to kernel `linux-image-5.13.0-39-generic`, my Scarlett 2i2 began playing back distorted audio (sounds overdriven and slowed down, as if the sample rate is incorrect). To clarify, the device is reported in libusb as: Bus 001 Device 002: ID 1235:8210 Focusrite-Novation Scarlett 2i2 Camera This bug is also present in 5.13.0-37-generic, but is not present in 5.13.0-35-generic; booting the -35 kernel via GRUB resolves the problem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eta2014 F pulseaudio /dev/snd/controlC1: eta2014 F pulseaudio /dev/snd/pcmC1D0p: eta2014 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Apr 6 22:05:29 2022 InstallationDate: Installed on 2022-02-16 (49 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20L6S87J1L ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.13.0-35-generic N/A linux-backports-modules-5.13.0-35-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET66W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S87J1L dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrN24ET66W(1.41):bd10/20/2021:br1.41:efr1.21:svnLENOVO:pn20L6S87J1L:pvrThinkPadT480:rvnLENOVO:rn20L6S87J1L:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L6_BU_Think_FM_ThinkPadT480: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S87J1L dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968089/+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 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
** Attachment added: "Windows Installer" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950282/+attachment/5577808/+files/TelephonyToolM2_5G_branch_V5.0.29.msi -- 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/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+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 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
Hi Canonical Team, Please request Fibocom team to share the latest modem firmware for FM350, as they would be able to share it. Thanks and Best Regards, Murali -- 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/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+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 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
Hi Canonical Team, For FM350 5G 5000 on Windows, please use the attached Telephony tool for 5G. For Linux, we are still waiting for Canonical team to help on the clarifications for creating the snap package for Firmware Update and Switching tool. Thanks and Best Regards, Murali -- 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/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+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
