[Kernel-packages] [Bug 1953058] Re: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion even
appleton with 5.4.0-135.152~18.04.2-generic passes 1000 reboot without any soft lockup. I will try 5.4.0-92.103~18.04.2. d05-3 with 5.4.0-135.152~18.04.2-generic passes 669 reboot without any error. ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Ike Panhc (ikepanhc) -- 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/1953058 Title: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9") Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Confirmed Bug description: The regression boot test running with bionic:linux-hwe-5.4 5.4.0-92.103~18.04.2 failed because of the following hung task: Dec 2 12:17:12 appleton-kernel kernel: [ 64.281447] watchdog: BUG: soft lockup - CPU#16 stuck for 22s! [swapper/16:0] Dec 2 12:17:12 appleton-kernel kernel: [ 64.288573] Modules linked in: ipmi_ssif nls_iso8859_1 joydev input_leds ipmi_si ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib hid_generic ses usbhid enclosure hid ib_uverbs ib_core marvell hibmc_drm drm_vram_helper ttm drm_kms_helper crct10dif_ce ghash_ce syscopyarea sysfillrect sha2_ce mlx5_core sysimgblt sha256_arm64 ixgbe hisi_sas_v2_hw fb_sys_fops nvme sha1_ce hisi_sas_main tls xfrm_algo drm megaraid_sas nvme_core mdio mlxfw libsas ehci_platform scsi_transport_sas hns_dsaf hns_enet_drv hns_mdio hnae aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher Dec 2 12:17:12 appleton-kernel kernel: [ 64.288629] CPU: 16 PID: 0 Comm: swapper/16 Not tainted 5.4.0-91-generic #102~18.04.1-Ubuntu Dec 2 12:17:12 appleton-kernel kernel: [ 64.288630] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288632] pstate: 4045 (nZcv daif +PAN -UAO) Dec 2 12:17:12 appleton-kernel kernel: [ 64.288640] pc : __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288644] lr : irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288645] sp : 800011ee3ef0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288646] x29: 800011ee3ef0 x28: 002fb71a2d00 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288649] x27: x26: 800011ee4000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288650] x25: 800011ee x24: 001fba073600 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288652] x23: 80001234bdb0 x22: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288654] x21: 0282 x20: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288656] x19: 8000116b3000 x18: 800011267510 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288658] x17: x16: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288659] x15: 0001 x14: 002fbb9f21c8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288661] x13: 0004 x12: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288663] x11: x10: 0040 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288665] x9 : 800011bbf228 x8 : 800011bbf220 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288666] x7 : 001fb9002270 x6 : 0002c07fa07f Dec 2 12:17:12 appleton-kernel kernel: [ 64.288668] x5 : 00c1 x4 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288670] x3 : 8000116b3780 x2 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288672] x1 : 00e0 x0 : 8000116b3780 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288675] Call trace: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288677] __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288679] irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288683] __handle_domain_irq+0x6c/0xc0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288685] gic_handle_irq+0x84/0x2c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288687] el1_irq+0x104/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288690] arch_cpu_idle+0x34/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288694] default_idle_call+0x24/0x60 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288696] do_idle+0x1d8/0x2b8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288699] cpu_startup_entry+0x28/0xb0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288702]
[Kernel-packages] [Bug 1992823] Re: package nvidia-dkms-515 515.65.01-0ubuntu0.22.04.1 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-515 script post-installation devolvió el c
[Expired for nvidia-graphics-drivers-515 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-515 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu. https://bugs.launchpad.net/bugs/1992823 Title: package nvidia-dkms-515 515.65.01-0ubuntu0.22.04.1 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-515 script post-installation devolvió el código de salida de error 10 Status in nvidia-graphics-drivers-515 package in Ubuntu: Expired Bug description: i can't detect my 2 monitors ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-515 515.65.01-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Oct 13 17:24:41 2022 ErrorMessage: el subproceso instalado paquete nvidia-dkms-515 script post-installation devolvió el código de salida de error 10 InstallationDate: Installed on 2021-12-05 (311 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: nvidia-graphics-drivers-515 Title: package nvidia-dkms-515 515.65.01-0ubuntu0.22.04.1 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-515 script post-installation devolvió el código de salida de error 10 UpgradeStatus: Upgraded to jammy on 2022-09-18 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/1992823/+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 1930921] Re: Apache 2.4.41 corrupts files from samba share
** Changed in: debian Status: Confirmed => 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/1930921 Title: Apache 2.4.41 corrupts files from samba share Status in apache2 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in samba package in Ubuntu: Incomplete Status in Debian: Fix Released Bug description: Wenn I serve a samba share with apache 2.4.41 on Ubuntu 20.04 then some files have a corrupt header during transmission. It seems that the first few bytes of the headers are truncated and sometimes other bytes of the download are not belonging to the file. A workaround I found that works is to set "EnableMMAP Off" in the apache config. See other bug reports like this: https://serverfault.com/questions/1044724/apache2-sends-corrupt-responses-when-using-a-cifs-share https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900821 This is most probably not a bug in Ubuntu itself but I am reporting it here since I assume that a data corruption bug is seen as critical. I am also marking it as a security vulnerability since it seems that wrong parts of memory get exposed during file download. I don't know how random the exposed memory is and if it potentially could expose e.g. secrets. Please feel free to remove the security vulnerability flag if your assessment leads to a different conclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1930921/+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 2000030] 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 230 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/230 Title: Soundwire support for the Intel RPL Gen platforms -- follow-ups Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: New Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: New Status in firmware-sof source package in Lunar: New Status in linux source package in Lunar: Incomplete Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: This is a follow-up to bug 1997944 that supports more RPL gen platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/230/+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 2000030] [NEW] Soundwire support for the Intel RPL Gen platforms -- follow-ups
Public bug reported: This is a follow-up to bug 1997944 that supports more RPL gen platforms. ** Affects: firmware-sof (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: firmware-sof (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: firmware-sof (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: linux-oem-6.0 (Ubuntu Lunar) Status: New => Invalid ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Also affects: firmware-sof (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-firmware (Ubuntu) ** No longer affects: linux-firmware (Ubuntu Jammy) ** No longer affects: linux-firmware (Ubuntu Lunar) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/230 Title: Soundwire support for the Intel RPL Gen platforms -- follow-ups Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: New Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: New Status in firmware-sof source package in Lunar: New Status in linux source package in Lunar: New Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: This is a follow-up to bug 1997944 that supports more RPL gen platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/230/+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-restricted-modules-azure/5.19.0-1015.16)
All autopkgtests for the newly accepted linux-restricted-modules-azure (5.19.0-1015.16) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-515-server/unknown (arm64) nvidia-graphics-drivers-525/525.60.11-0ubuntu0.22.10.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#linux-restricted-modules-azure [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 1998351] Re: Azure: MANA New Feature MANA XDP_Redirect Action
This bug is awaiting verification that the linux-azure/5.19.0-1016.17
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-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.
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: kernel-spammed-kinetic-linux-azure verification-needed-kinetic
--
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/1998351
Title:
Azure: MANA New Feature MANA XDP_Redirect Action
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Jammy:
Fix Committed
Status in linux-azure source package in Kinetic:
Fix Committed
Bug description:
SRU Justification
[Impact]
XDP Redirection is not implemented in 5.15 Azure tuned kernels.
Microsoft has requested the addition of this feature:
commit 7a8938cd024d383c12bb1e08025db6ea3d551103 ("net: mana: Add
support of XDP_REDIRECT action")
[Test Plan]
Microsoft tested with positive results.
[Where things could go wrong]
Network skb routing could go awry.
[Other info]
SF: #00340222
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1998351/+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 1998838] Re: Azure: Jammy fio test hangs, swiotlb buffers exhausted
This bug is awaiting verification that the linux-azure/5.19.0-1016.17 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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: kernel-spammed-kinetic-linux-azure verification-needed-kinetic -- 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/1998838 Title: Azure: Jammy fio test hangs, swiotlb buffers exhausted Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Jammy: Fix Released Status in linux-azure source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] Hello Canonical Team, This issue was found while doing the validation on CPC's Jammy CVM image. We are up against a tight timeline to deliver this to a partner on 10/5. Would appreciate prioritizing this. While running fio, the command fails to exit after 2 minutes. I watched `top` as the command hung and I saw kworkers getting blocked. sudo fio --ioengine=libaio --bs=4K --filename=/dev/sdc1:/dev/sdd1:/dev/sde1:/dev/sdf1:/dev/sdg1:/dev/sdh1:/dev/sdi1:/dev/sdj1:/dev/sdk1:/dev/sdl1:/dev/sdm1:/dev/sdn1:/dev/sdo1:/dev/sdp1:/dev/sdq1:/dev/sdr1 --readwrite=randwrite --runtime=120 --iodepth=1 --numjob=96 --name=iteration9 --direct=1 --size=8192M --group_reporting --overwrite=1 Example system logs: --- [ 1096.297641] INFO: task kworker/u192:0:8 blocked for more than 120 seconds. [ 1096.302785] Tainted: G W 5.15.0-1024-azure #30-Ubuntu [ 1096.306312] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1096.310489] INFO: task jbd2/sda1-8:1113 blocked for more than 120 seconds. [ 1096.313900] Tainted: G W 5.15.0-1024-azure #30-Ubuntu [ 1096.317481] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1096.324117] INFO: task systemd-journal:1191 blocked for more than 120 seconds. [ 1096.331219] Tainted: G W 5.15.0-1024-azure #30-Ubuntu [ 1096.335332] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. --- --- [ 3241.013230] systemd-udevd[1221]: sdl1: Worker [6686] processing SEQNUM=13323 killed [ 3261.492691] systemd-udevd[1221]: sdl1: Worker [6686] failed --- TOP report: --- PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 417 root 20 0 0 0 0 R 66.2 0.0 0:34.61 ksoftirqd/59 435 root 20 0 0 0 0 I 24.5 0.0 0:09.03 kworker/59:1-mm_percpu_wq 416 root rt 0 0 0 0 S 23.5 0.0 0:01.86 migration/59 366 root 0 -20 0 0 0 I 19.2 0.0 0:16.64 kworker/49:1H-kblockd 378 root 0 -20 0 0 0 I 17.9 0.0 0:15.71 kworker/51:1H-kblockd 455 root 0 -20 0 0 0 I 17.9 0.0 0:14.76 kworker/62:1H-kblockd 135 root 0 -20 0 0 0 I 17.5 0.0 0:13.08 kworker/17:1H-kblockd 420 root 0 -20 0 0 0 I 16.9 0.0 0:14.63 kworker/58:1H-kblockd ... --- LISAv3 Testcase: perf_premium_datadisks_4k Image : "canonical-test 0001-com-ubuntu-confidential-vm-jammy-preview 22_04-lts-cvm latest" VMSize : "Standard_DC96ads_v5" For repro-ability, I am seeing this every time I run the storage perf tests. It always seems to happen on iteration 9 or 10. When running manually, I had to run the command three or four times to reproduce the issue. [Test Case] Microsoft tested, requires lots of cores (96) and disks (16) [Where things could go wrong] swiotlb buffers could be double freed. [Other Info] SF: #00349781 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1998838/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
This bug was fixed in the package grub2-unsigned - 2.06-2ubuntu16 --- grub2-unsigned (2.06-2ubuntu16) lunar; urgency=medium * Cherry-pick all memory patches from rhboot - Allocate initrd > 4 GB (LP: #1842320) - Allocate kernels as code, not data (needed for newer firmware) * ubuntu: Fix casts on i386-efi target * Cherry-pick all the 2.12 memory management changes (LP: #1842320) * Allocate executables as CODE, not DATA in chainloader and arm64 * Source package generated from src:grub2 using make -f ./debian/rules generate-grub2-unsigned -- Julian Andres Klode Fri, 09 Dec 2022 17:11:44 +0100 ** Changed in: grub2-unsigned (Ubuntu) Status: Fix Committed => 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/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Fix Committed Status in grub2-unsigned package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: [Workaround] Some workarounds have been suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125 [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory region starvation in <1G addresses: Type StartEnd # Pages Attributes Available -00086FFF 0087 000F BS_Data00087000-00087FFF 0001 000F Available 00088000-0009EFFF 0017 000F Reserved 0009F000-0009 0001 000F Available 0010-00FF 0F00 000F LoaderCode 0100-01021FFF 0022 000F Available 01022000-238A7FFF 00022886 000F BS_Data238A8000-23927FFF 0080 000F Available 23928000-28860FFF 4F39 000F BS_Data28861000-2AB09FFF 22A9 000F LoaderCode 2AB0A000-2ACF8FFF 01EF 000F BS_Data2ACF9000-2B2FAFFF 0602 000F Available 2B2FB000-2B611FFF 0317 000F BS_Data2B612000-2B630FFF 001F 000F Available 2B631000-2B632FFF 0002 000F BS_Data2B633000-2B63CFFF 000A 000F Available 2B63D000-2B649FFF 000D 000F BS_Data2B64A000-2B64EFFF 0005 000F Available 2B64F000-2B666FFF 0018 000F BS_Data2B667000-2D8D5FFF 226F 000F LoaderCode 2D8D6000-2D8E9FFF 0014 000F BS_Data2D8EA000-2D925FFF 003C 000F LoaderCode 2D926000-2D932FFF 000D 000F BS_Data2D933000-2D969FFF 0037 000F BS_Code2D96A000-2D973FFF 000A 000F BS_Data2D974000-2E377FFF 0A04 000F Available 2E378000-2E37AFFF 0003
[Kernel-packages] [Bug 1997472] Re: Touchpad problem detecting working area on Dell XPS
Checked the input devices list, the touchpad is on i2c bus 2. Please use the command to dump the firmware version: $ sudo i2ctransfer -f -y 2 w2@0x2c 0x20 0x00 r26 I'll ask Dell what is the latest firmware version for your machine. Thanks, -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997472 Title: Touchpad problem detecting working area on Dell XPS Status in linux package in Ubuntu: Confirmed Bug description: I am using a new Dell XPS 17 with the latest Ubuntu (22.10). One bug I could see is the touchpad sensitivity. Sometimes, randomly, the upper part of the touchpad is the only one working, most of its surface does not work. If the movement starts in the working area, then you can use the whole touchpad until you lift the finger. After a while it seems to recover by itself. My feeling is that this is somehow related to the sensitivity of the touchpad (some instability) or related to the system that disables the touchpad while writing (again, some buggy detection). While writing this text I experienced the bug twice, for instance, intermittently. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: florin 1581 F pipewire florin 1584 F wireplumber /dev/snd/controlC0: florin 1584 F wireplumber /dev/snd/seq:florin 1581 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 22 17:25:52 2022 InstallationDate: Installed on 2022-10-24 (29 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Dell Inc. XPS 17 9720 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=99833626-9acf-4145-9fee-2cbbe47e4d33 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2022 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0KNF8J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd09/08/2022:br1.11:svnDellInc.:pnXPS179720:pvr:rvnDellInc.:rn0KNF8J:rvrA00:cvnDellInc.:ct10:cvr:sku0AFF: dmi.product.family: XPS dmi.product.name: XPS 17 9720 dmi.product.sku: 0AFF dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997472/+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
