[Kernel-packages] [Bug 1984004] Re: Linux Firmware drops AMD RX6650 XT Performance
Here the dmesg from a boot with only the 12 dimgrey amdgpu firmware files. The ACPI error messages are normal and appear also with the full firmware installation. ** Attachment removed: "dmesg from failed boot" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1984004/+attachment/5611300/+files/dmesg.0 ** Attachment added: "dmesg log" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1984004/+attachment/5611530/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1984004 Title: Linux Firmware drops AMD RX6650 XT Performance Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Triaged Bug description: Kernel: 5.15.0-43-generic linux-firmware: 20220329.git681281e4-0ubuntu3.3 Tested with: Mint 21 Cinnamon (Ubuntu 22.04 based) In e.g. the Unigine benchmark, the linux-firmware packages drops the performance of my AMD RX 6650 XT GPU from 98 FPS in 1080p-high down to 23 FPS. That wasn't a problem in Mint 20.3 with kernel 5.15 (Ubuntu 20.04 based). Getting the firmware directly from git brings the performance back to about 100 FPS: git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git cd linux-firmware sudo make install sudo update-initramfs -c -k all Re-installing the linux-firmware package causes the performance to drop again. So there is a problem with the linux firmware at least for the RX 6650 XT, maybe for the whole RX 6000 series. The linux-firmware package in Ubuntu 22.04 should be updated. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: daelach1352 F pulseaudio /dev/snd/controlC0: daelach1352 F pulseaudio /dev/snd/controlC1: daelach1352 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Dependencies: firmware-sof-signed 2.0-1ubuntu3 [origin: Ubuntu] DistroRelease: Linux Mint 21 InstallationDate: Installed on 2020-08-24 (714 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: lono wireless extensions. enp6s0no wireless extensions. MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=UUID=a4b18dd9-4989-4bf5-8107-e55b8f8f6df4 ro amd_iommu=on iommu=pt quiet loglevel=3 splash ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Tags: vanessa third-party-packages Uname: Linux 5.15.0-43-generic x86_64 UnreportableReason: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4901 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4901:bd07/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1984004/+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 1964983] Re: IPU6 camera has no function on Andrews MLK
For linux-oem-5.17 or newer, see bug 1987595. -- 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/1964983 Title: IPU6 camera has no function on Andrews MLK Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] New Andrews MLK equips yet another new I2C sensor and takes a few driver updates to function normally. [Fix] Upstream driver commit: https://github.com/intel/ipu6-drivers/commit/778819bef3d8ac8d6b24342372e006b7b43e381e [Test Case] To verify by following steps: 1. disable secure boot 2. $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel 3. $ sudo add-apt-repository ppa:kchsieh/ipu6 4. $ sudo apt install linux-oem-5.14 version 5.14.0-9029-oem or newer 6. $ sudo apt install libipu6ep 7. $ sudo apt install libcamhal-ipu6ep-common 8. $ sudo apt install libcamhal-ipu6ep0 9. $ sudo apt install libgsticamerainterface-1.0-1 10. $ sudo apt install gstreamer1.0-icamera 11. $ sudo vim /etc/v4l2-relayd -FORMAT=YUY2 +FORMAT=NV12 12. $ sudo reboot [Where problems could occur] Intel IPU6 platform is still under development and is not capable of advanced power management features and may still suffer from stability issues. [Other Info] Nomination for 5.15 is necessary for oem-5.14 to hwe-5.15 migration and will depend on previous SRU proposal in bug 1955383 (https://lists.ubuntu.com/archives/kernel-team/2022-March/128922.html). Nomination for generic-5.17 and oem-5.17 is still under planning. == original bug description == The new platform uses yet another ov sensor OV02C10. Prerequisites: * kernel fix: https://github.com/intel/ipu6-drivers/commit/778819bef3d8ac8d6b24342372e006b7b43e381e * ipu6-camera-bins: https://github.com/intel/ipu6-camera-bins/commit/7cc1dc2d9ab2b0766e034edf808d751bd25b42cc * ipu6-camera-hal: https://github.com/intel/ipu6-camera-hal/commit/b9b56de11de70b7c4520595176e4831bacf4a7fe * icamerasrc: https://github.com/intel/icamerasrc/commit/a35978264002acaad72bb9956238ccaef3743932 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1964983/+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 1987595] [NEW] Support Intel IPU6 MIPI camera
Public bug reported: This is a follow-up for bug 1964983 but on different platforms that runs linux-oem-5.17 or newer. ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1987595 Title: Support Intel IPU6 MIPI camera Status in linux-oem-5.17 package in Ubuntu: New Bug description: This is a follow-up for bug 1964983 but on different platforms that runs linux-oem-5.17 or newer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1987595/+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
Re: [Kernel-packages] [Bug 1971193] Re: Server Crash while running IO and switch port bounce test with 2K login session
Checking On Wed, Aug 24, 2022 at 7:50 PM Jeff Lane <1971...@bugs.launchpad.net> wrote: > So this is actually in 5.19, and has been pulled into 22.04 via our 5.15 > kernel. Is there anything more to do here? > > commit eb2f403f098fedb4c58283e9532df2ff0d2a36e9 > Author: James Smart > Date: Tue Apr 12 15:19:44 2022 -0700 > > scsi: lpfc: Move cfg_log_verbose check before calling lpfc_dmp_dbg() > > BugLink: https://bugs.launchpad.net/bugs/1981864 > > [ Upstream commit e294647b1aed4247fe52851f3a3b2b19ae906228 ] > > In an attempt to log message 0126 with LOG_TRACE_EVENT, the following > hard > lockup call trace hangs the system. > > Call Trace: > _raw_spin_lock_irqsave+0x32/0x40 > lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc] > lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc] > lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc] > lpfc_els_flush_cmd+0x43c/0x670 [lpfc] > lpfc_els_flush_all_cmd+0x37/0x60 [lpfc] > lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc] > lpfc_do_work+0x1485/0x1d70 [lpfc] > kthread+0x112/0x130 > ret_from_fork+0x1f/0x40 > Kernel panic - not syncing: Hard LOCKUP > > The same CPU tries to claim the phba->port_list_lock twice. > > Move the cfg_log_verbose checks as part of the lpfc_printf_vlog() and > lpfc_printf_log() macros before calling lpfc_dmp_dbg(). There is no > need > to take the phba->port_list_lock within lpfc_dmp_dbg(). > > Link: > https://lore.kernel.org/r/2022041008.126521-3-jsmart2...@gmail.com > Co-developed-by: Justin Tee > Signed-off-by: Justin Tee > Signed-off-by: James Smart > Signed-off-by: Martin K. Petersen > Signed-off-by: Sasha Levin > Signed-off-by: Kamal Mostafa > Signed-off-by: Stefan Bader > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1971193 > > Title: > Server Crash while running IO and switch port bounce test with 2K > login session > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > [Impact] > Server crash and Call trace reported on one of the servers running IO and > switch port bounce test from the 2K login session configuration. > > Call Trace: > [56048.470488] Call Trace: > [56048.470489] _raw_spin_lock_irqsave+0x32/0x40 > [56048.470489] lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc] > [56048.470490] lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc] > [56048.470490] lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc] > [56048.470490] lpfc_els_flush_cmd+0x43c/0x670 [lpfc] > [56048.470491] lpfc_els_flush_all_cmd+0x37/0x60 [lpfc] > [56048.470491] lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc] > [56048.470492] lpfc_do_work+0x1485/0x1d70 [lpfc] > [56048.470492] ? __schedule+0x280/0x700 > [56048.470492] ? finish_wait+0x80/0x80 > [56048.470493] ? lpfc_unregister_unused_fcf+0x80/0x80 [lpfc] > [56048.470493] kthread+0x112/0x130 > [56048.470493] ? kthread_flush_work_fn+0x10/0x10 > [56048.470494] ret_from_fork+0x1f/0x40 > [56048.470494] Kernel panic - not syncing: Hard LOCKUP > [56048.470495] CPU: 0 PID: 682 Comm: lpfc_worker_0 Kdump: loaded > Tainted: G >IOE- - - 4.18.0-240.el8.x86_64 #1 > [56048.470496] Hardware name: Dell Inc. PowerEdge R740/0DY2X0, BIOS > 2.11.2 > 004/21/2021 > [56048.470496] Call Trace: > [56048.470496] > [56048.470496] dump_stack+0x5c/0x80 > [56048.470497] panic+0xe7/0x2a9 > [56048.470497] ? __switch_to_asm+0x51/0x70 > [56048.470497] nmi_panic.cold.9+0xc/0xc > [56048.470498] watchdog_overflow_callback.cold.7+0x5c/0x70 > [56048.470498] __perf_event_overflow+0x52/0xf0 > [56048.470499] handle_pmi_common+0x1db/0x270 > [56048.470499] ? __set_pte_vaddr+0x32/0x50 > [56048.470499] ? __native_set_fixmap+0x24/0x30 > [56048.470500] ? ghes_copy_tofrom_phys+0xd3/0x1c0 > [56048.470500] ? __ghes_peek_estatus.isra.12+0x49/0xa0 > [56048.470500] intel_pmu_handle_irq+0xbf/0x160 > [56048.470501] perf_event_nmi_handler+0x2d/0x50 > [56048.470501] nmi_handle+0x63/0x110 > [56048.470501] default_do_nmi+0x4e/0x100 > [56048.470502] do_nmi+0x128/0x190 > [56048.470502] end_repeat_nmi+0x16/0x6a > [56048.470503] RIP: 0010:native_queued_spin_lock_slowpath+0x5d/0x1d0 > [56048.470504] Code: 0f ba 2f 08 0f 92 c0 0f b6 c0 c1 e0 08 89 c2 8b 07 > 30 e4 > 09 d0 a9 00 01 ff ff 75 47 85 c0 74 0e 8b 07 84 c0 74 08 f3 90 8b 07 > <84> c0 75 > f8 b8 01 00 00 00 66 89 07 c3 8b 37 81 fe 00 01 00 00 75 > [56048.470504] RSP: 0018:acebc7877ca8 EFLAGS: 0002 > [56048.470505] RAX: 0101 RBX: 0246 RCX: > 001f > [56048.470505] RDX: RSI: RDI: > 94dcf5341dc0 > [56048.470506] RBP: 94dcf534 R08: 0002 R09: > 00029600 > [56048.470506] R10: 60d29656a45c R11: 94dcf534fd12 R12: > 94dcf5341db0 > [56048.470507] R13: 94dcf5341dc0 R14:
[Kernel-packages] [Bug 1971193] Re: Server Crash while running IO and switch port bounce test with 2K login session
So this is actually in 5.19, and has been pulled into 22.04 via our 5.15 kernel. Is there anything more to do here? commit eb2f403f098fedb4c58283e9532df2ff0d2a36e9 Author: James Smart Date: Tue Apr 12 15:19:44 2022 -0700 scsi: lpfc: Move cfg_log_verbose check before calling lpfc_dmp_dbg() BugLink: https://bugs.launchpad.net/bugs/1981864 [ Upstream commit e294647b1aed4247fe52851f3a3b2b19ae906228 ] In an attempt to log message 0126 with LOG_TRACE_EVENT, the following hard lockup call trace hangs the system. Call Trace: _raw_spin_lock_irqsave+0x32/0x40 lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc] lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc] lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc] lpfc_els_flush_cmd+0x43c/0x670 [lpfc] lpfc_els_flush_all_cmd+0x37/0x60 [lpfc] lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc] lpfc_do_work+0x1485/0x1d70 [lpfc] kthread+0x112/0x130 ret_from_fork+0x1f/0x40 Kernel panic - not syncing: Hard LOCKUP The same CPU tries to claim the phba->port_list_lock twice. Move the cfg_log_verbose checks as part of the lpfc_printf_vlog() and lpfc_printf_log() macros before calling lpfc_dmp_dbg(). There is no need to take the phba->port_list_lock within lpfc_dmp_dbg(). Link: https://lore.kernel.org/r/2022041008.126521-3-jsmart2...@gmail.com Co-developed-by: Justin Tee Signed-off-by: Justin Tee Signed-off-by: James Smart Signed-off-by: Martin K. Petersen Signed-off-by: Sasha Levin Signed-off-by: Kamal Mostafa Signed-off-by: Stefan Bader -- 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/1971193 Title: Server Crash while running IO and switch port bounce test with 2K login session Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Server crash and Call trace reported on one of the servers running IO and switch port bounce test from the 2K login session configuration. Call Trace: [56048.470488] Call Trace: [56048.470489] _raw_spin_lock_irqsave+0x32/0x40 [56048.470489] lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc] [56048.470490] lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc] [56048.470490] lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc] [56048.470490] lpfc_els_flush_cmd+0x43c/0x670 [lpfc] [56048.470491] lpfc_els_flush_all_cmd+0x37/0x60 [lpfc] [56048.470491] lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc] [56048.470492] lpfc_do_work+0x1485/0x1d70 [lpfc] [56048.470492] ? __schedule+0x280/0x700 [56048.470492] ? finish_wait+0x80/0x80 [56048.470493] ? lpfc_unregister_unused_fcf+0x80/0x80 [lpfc] [56048.470493] kthread+0x112/0x130 [56048.470493] ? kthread_flush_work_fn+0x10/0x10 [56048.470494] ret_from_fork+0x1f/0x40 [56048.470494] Kernel panic - not syncing: Hard LOCKUP [56048.470495] CPU: 0 PID: 682 Comm: lpfc_worker_0 Kdump: loaded Tainted: G IOE- - - 4.18.0-240.el8.x86_64 #1 [56048.470496] Hardware name: Dell Inc. PowerEdge R740/0DY2X0, BIOS 2.11.2 004/21/2021 [56048.470496] Call Trace: [56048.470496] [56048.470496] dump_stack+0x5c/0x80 [56048.470497] panic+0xe7/0x2a9 [56048.470497] ? __switch_to_asm+0x51/0x70 [56048.470497] nmi_panic.cold.9+0xc/0xc [56048.470498] watchdog_overflow_callback.cold.7+0x5c/0x70 [56048.470498] __perf_event_overflow+0x52/0xf0 [56048.470499] handle_pmi_common+0x1db/0x270 [56048.470499] ? __set_pte_vaddr+0x32/0x50 [56048.470499] ? __native_set_fixmap+0x24/0x30 [56048.470500] ? ghes_copy_tofrom_phys+0xd3/0x1c0 [56048.470500] ? __ghes_peek_estatus.isra.12+0x49/0xa0 [56048.470500] intel_pmu_handle_irq+0xbf/0x160 [56048.470501] perf_event_nmi_handler+0x2d/0x50 [56048.470501] nmi_handle+0x63/0x110 [56048.470501] default_do_nmi+0x4e/0x100 [56048.470502] do_nmi+0x128/0x190 [56048.470502] end_repeat_nmi+0x16/0x6a [56048.470503] RIP: 0010:native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470504] Code: 0f ba 2f 08 0f 92 c0 0f b6 c0 c1 e0 08 89 c2 8b 07 30 e4 09 d0 a9 00 01 ff ff 75 47 85 c0 74 0e 8b 07 84 c0 74 08 f3 90 8b 07 <84> c0 75 f8 b8 01 00 00 00 66 89 07 c3 8b 37 81 fe 00 01 00 00 75 [56048.470504] RSP: 0018:acebc7877ca8 EFLAGS: 0002 [56048.470505] RAX: 0101 RBX: 0246 RCX: 001f [56048.470505] RDX: RSI: RDI: 94dcf5341dc0 [56048.470506] RBP: 94dcf534 R08: 0002 R09: 00029600 [56048.470506] R10: 60d29656a45c R11: 94dcf534fd12 R12: 94dcf5341db0 [56048.470507] R13: 94dcf5341dc0 R14: 94dcc4ae8a00 R15: 0003 [56048.470507] ? native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470507] ? native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470508] [56048.470508] _raw_spin_lock_irqsave+0x32/0x40 [56048.470509]
[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade
I am getting this issue on two machines. One Dell 7530 Precision laptop, I have upgraded 18.04 - 20.04 and 22.04. It is really quite noticeable; after a few hours I start to notice it. After leaving it for a few days it gets worse and worse. Even typing this I suddenly get 15 of the same letter typed and stuttering. This machines got 6 core Intel i7, 42GB RAM, NVMe SSD. It does have a Radeon GPU but currently booted into the Intel GPU with switchable graphics. Might be worth trying it booted via the Radeon. Might be worth noting it is powered by a Dell Dock which says it doesn't deliver enough power when booting (but it does for my use). @Urban I installed 21.10 on a Dell XPS 9365 2 in 1 and upgraded to 22.04. It is happening on that too. Its not anywhere near as noticeable but definitely got some mouse stuttering which 21.10 didn't have. -- 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/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 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.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd: dmi.product.family:
[Kernel-packages] [Bug 1987184] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1987184/+attachment/5611398/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987184 Title: I am not sure about crash reports but I am having multiple issues with keyboard and touchpad.Touchpad gets stuck and keyboard keys are starts working erractically Status in linux package in Ubuntu: Confirmed Bug description: OS VERSION: Ubuntu 22.04 Laptop: Dell Precision 5550 Keyboard Layout Set: English(US) Touch pad gets stuck quite frequently while external mouse works just fine during that time. Sometimes using "sudo modprode psmouse" make touchpad start working again. Keyboard start working erratically suddenly and os suddenly starts acting erratically random things like opening mouse right click menu,closing apps,minimizing apps screen and so on.Normally issue comes while using vsCode since I do most my text work there. ctrl,shift,down arrow keys especially trigger this behaviour. I have no idea why this is happening though I know it did not happen in Ubuntu 20. Things get so bad only option is to reboot. And this happens quite frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:57730349:2022-08-16 22:46:36.768890857 +0530:2022-08-16 22:46:37.768890857 +0530:/var/crash/_opt_google_chrome_chrome.1000.crash 664:1000:124:0:2022-08-16 22:46:37.772890783 +0530:2022-08-16 22:46:37.772890783 +0530:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:124:672458:2022-08-14 18:59:42.264840602 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_usr_libexec_gvfsd-mtp.1000.crash 600:117:124:37:2022-08-16 22:46:39.708866983 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 04:31:10 2022 InstallationDate: Installed on 2022-08-08 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nipun 3034 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-08 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Precision 3541 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=8be20bde-302f-458f-9ea0-25e3f3b387ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 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.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/30/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.1 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.1:bd03/30/2022:br1.19:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987184/+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 1987184] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1987184/+attachment/5611396/+files/UdevDb.txt -- 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/1987184 Title: I am not sure about crash reports but I am having multiple issues with keyboard and touchpad.Touchpad gets stuck and keyboard keys are starts working erractically Status in linux package in Ubuntu: Confirmed Bug description: OS VERSION: Ubuntu 22.04 Laptop: Dell Precision 5550 Keyboard Layout Set: English(US) Touch pad gets stuck quite frequently while external mouse works just fine during that time. Sometimes using "sudo modprode psmouse" make touchpad start working again. Keyboard start working erratically suddenly and os suddenly starts acting erratically random things like opening mouse right click menu,closing apps,minimizing apps screen and so on.Normally issue comes while using vsCode since I do most my text work there. ctrl,shift,down arrow keys especially trigger this behaviour. I have no idea why this is happening though I know it did not happen in Ubuntu 20. Things get so bad only option is to reboot. And this happens quite frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:57730349:2022-08-16 22:46:36.768890857 +0530:2022-08-16 22:46:37.768890857 +0530:/var/crash/_opt_google_chrome_chrome.1000.crash 664:1000:124:0:2022-08-16 22:46:37.772890783 +0530:2022-08-16 22:46:37.772890783 +0530:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:124:672458:2022-08-14 18:59:42.264840602 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_usr_libexec_gvfsd-mtp.1000.crash 600:117:124:37:2022-08-16 22:46:39.708866983 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 04:31:10 2022 InstallationDate: Installed on 2022-08-08 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nipun 3034 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-08 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Precision 3541 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=8be20bde-302f-458f-9ea0-25e3f3b387ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 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.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/30/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.1 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.1:bd03/30/2022:br1.19:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987184/+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 1987184] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1987184/+attachment/5611389/+files/Lsusb-v.txt -- 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/1987184 Title: I am not sure about crash reports but I am having multiple issues with keyboard and touchpad.Touchpad gets stuck and keyboard keys are starts working erractically Status in linux package in Ubuntu: Confirmed Bug description: OS VERSION: Ubuntu 22.04 Laptop: Dell Precision 5550 Keyboard Layout Set: English(US) Touch pad gets stuck quite frequently while external mouse works just fine during that time. Sometimes using "sudo modprode psmouse" make touchpad start working again. Keyboard start working erratically suddenly and os suddenly starts acting erratically random things like opening mouse right click menu,closing apps,minimizing apps screen and so on.Normally issue comes while using vsCode since I do most my text work there. ctrl,shift,down arrow keys especially trigger this behaviour. I have no idea why this is happening though I know it did not happen in Ubuntu 20. Things get so bad only option is to reboot. And this happens quite frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:57730349:2022-08-16 22:46:36.768890857 +0530:2022-08-16 22:46:37.768890857 +0530:/var/crash/_opt_google_chrome_chrome.1000.crash 664:1000:124:0:2022-08-16 22:46:37.772890783 +0530:2022-08-16 22:46:37.772890783 +0530:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:124:672458:2022-08-14 18:59:42.264840602 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_usr_libexec_gvfsd-mtp.1000.crash 600:117:124:37:2022-08-16 22:46:39.708866983 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 04:31:10 2022 InstallationDate: Installed on 2022-08-08 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nipun 3034 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-08 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Precision 3541 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=8be20bde-302f-458f-9ea0-25e3f3b387ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 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.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/30/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.1 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.1:bd03/30/2022:br1.19:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987184/+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 1987184] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1987184/+attachment/5611397/+files/WifiSyslog.txt -- 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/1987184 Title: I am not sure about crash reports but I am having multiple issues with keyboard and touchpad.Touchpad gets stuck and keyboard keys are starts working erractically Status in linux package in Ubuntu: Confirmed Bug description: OS VERSION: Ubuntu 22.04 Laptop: Dell Precision 5550 Keyboard Layout Set: English(US) Touch pad gets stuck quite frequently while external mouse works just fine during that time. Sometimes using "sudo modprode psmouse" make touchpad start working again. Keyboard start working erratically suddenly and os suddenly starts acting erratically random things like opening mouse right click menu,closing apps,minimizing apps screen and so on.Normally issue comes while using vsCode since I do most my text work there. ctrl,shift,down arrow keys especially trigger this behaviour. I have no idea why this is happening though I know it did not happen in Ubuntu 20. Things get so bad only option is to reboot. And this happens quite frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:57730349:2022-08-16 22:46:36.768890857 +0530:2022-08-16 22:46:37.768890857 +0530:/var/crash/_opt_google_chrome_chrome.1000.crash 664:1000:124:0:2022-08-16 22:46:37.772890783 +0530:2022-08-16 22:46:37.772890783 +0530:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:124:672458:2022-08-14 18:59:42.264840602 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_usr_libexec_gvfsd-mtp.1000.crash 600:117:124:37:2022-08-16 22:46:39.708866983 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 04:31:10 2022 InstallationDate: Installed on 2022-08-08 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nipun 3034 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-08 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Precision 3541 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=8be20bde-302f-458f-9ea0-25e3f3b387ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 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.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/30/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.1 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.1:bd03/30/2022:br1.19:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987184/+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 1987184] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1987184/+attachment/5611390/+files/PaInfo.txt -- 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/1987184 Title: I am not sure about crash reports but I am having multiple issues with keyboard and touchpad.Touchpad gets stuck and keyboard keys are starts working erractically Status in linux package in Ubuntu: Confirmed Bug description: OS VERSION: Ubuntu 22.04 Laptop: Dell Precision 5550 Keyboard Layout Set: English(US) Touch pad gets stuck quite frequently while external mouse works just fine during that time. Sometimes using "sudo modprode psmouse" make touchpad start working again. Keyboard start working erratically suddenly and os suddenly starts acting erratically random things like opening mouse right click menu,closing apps,minimizing apps screen and so on.Normally issue comes while using vsCode since I do most my text work there. ctrl,shift,down arrow keys especially trigger this behaviour. I have no idea why this is happening though I know it did not happen in Ubuntu 20. Things get so bad only option is to reboot. And this happens quite frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:57730349:2022-08-16 22:46:36.768890857 +0530:2022-08-16 22:46:37.768890857 +0530:/var/crash/_opt_google_chrome_chrome.1000.crash 664:1000:124:0:2022-08-16 22:46:37.772890783 +0530:2022-08-16 22:46:37.772890783 +0530:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:124:672458:2022-08-14 18:59:42.264840602 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_usr_libexec_gvfsd-mtp.1000.crash 600:117:124:37:2022-08-16 22:46:39.708866983 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 04:31:10 2022 InstallationDate: Installed on 2022-08-08 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nipun 3034 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-08 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Precision 3541 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=8be20bde-302f-458f-9ea0-25e3f3b387ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 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.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/30/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.1 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.1:bd03/30/2022:br1.19:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987184/+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 1987184] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1987184/+attachment/5611395/+files/RfKill.txt -- 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/1987184 Title: I am not sure about crash reports but I am having multiple issues with keyboard and touchpad.Touchpad gets stuck and keyboard keys are starts working erractically Status in linux package in Ubuntu: Confirmed Bug description: OS VERSION: Ubuntu 22.04 Laptop: Dell Precision 5550 Keyboard Layout Set: English(US) Touch pad gets stuck quite frequently while external mouse works just fine during that time. Sometimes using "sudo modprode psmouse" make touchpad start working again. Keyboard start working erratically suddenly and os suddenly starts acting erratically random things like opening mouse right click menu,closing apps,minimizing apps screen and so on.Normally issue comes while using vsCode since I do most my text work there. ctrl,shift,down arrow keys especially trigger this behaviour. I have no idea why this is happening though I know it did not happen in Ubuntu 20. Things get so bad only option is to reboot. And this happens quite frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:57730349:2022-08-16 22:46:36.768890857 +0530:2022-08-16 22:46:37.768890857 +0530:/var/crash/_opt_google_chrome_chrome.1000.crash 664:1000:124:0:2022-08-16 22:46:37.772890783 +0530:2022-08-16 22:46:37.772890783 +0530:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:124:672458:2022-08-14 18:59:42.264840602 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_usr_libexec_gvfsd-mtp.1000.crash 600:117:124:37:2022-08-16 22:46:39.708866983 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 04:31:10 2022 InstallationDate: Installed on 2022-08-08 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nipun 3034 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-08 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Precision 3541 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=8be20bde-302f-458f-9ea0-25e3f3b387ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 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.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/30/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.1 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.1:bd03/30/2022:br1.19:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987184/+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 1987184] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1987184/+attachment/5611388/+files/Lsusb-t.txt -- 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/1987184 Title: I am not sure about crash reports but I am having multiple issues with keyboard and touchpad.Touchpad gets stuck and keyboard keys are starts working erractically Status in linux package in Ubuntu: Confirmed Bug description: OS VERSION: Ubuntu 22.04 Laptop: Dell Precision 5550 Keyboard Layout Set: English(US) Touch pad gets stuck quite frequently while external mouse works just fine during that time. Sometimes using "sudo modprode psmouse" make touchpad start working again. Keyboard start working erratically suddenly and os suddenly starts acting erratically random things like opening mouse right click menu,closing apps,minimizing apps screen and so on.Normally issue comes while using vsCode since I do most my text work there. ctrl,shift,down arrow keys especially trigger this behaviour. I have no idea why this is happening though I know it did not happen in Ubuntu 20. Things get so bad only option is to reboot. And this happens quite frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:57730349:2022-08-16 22:46:36.768890857 +0530:2022-08-16 22:46:37.768890857 +0530:/var/crash/_opt_google_chrome_chrome.1000.crash 664:1000:124:0:2022-08-16 22:46:37.772890783 +0530:2022-08-16 22:46:37.772890783 +0530:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:124:672458:2022-08-14 18:59:42.264840602 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_usr_libexec_gvfsd-mtp.1000.crash 600:117:124:37:2022-08-16 22:46:39.708866983 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 04:31:10 2022 InstallationDate: Installed on 2022-08-08 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nipun 3034 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-08 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Precision 3541 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=8be20bde-302f-458f-9ea0-25e3f3b387ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 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.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/30/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.1 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.1:bd03/30/2022:br1.19:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987184/+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 1987184] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1987184/+attachment/5611386/+files/Lspci-vt.txt -- 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/1987184 Title: I am not sure about crash reports but I am having multiple issues with keyboard and touchpad.Touchpad gets stuck and keyboard keys are starts working erractically Status in linux package in Ubuntu: Confirmed Bug description: OS VERSION: Ubuntu 22.04 Laptop: Dell Precision 5550 Keyboard Layout Set: English(US) Touch pad gets stuck quite frequently while external mouse works just fine during that time. Sometimes using "sudo modprode psmouse" make touchpad start working again. Keyboard start working erratically suddenly and os suddenly starts acting erratically random things like opening mouse right click menu,closing apps,minimizing apps screen and so on.Normally issue comes while using vsCode since I do most my text work there. ctrl,shift,down arrow keys especially trigger this behaviour. I have no idea why this is happening though I know it did not happen in Ubuntu 20. Things get so bad only option is to reboot. And this happens quite frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:57730349:2022-08-16 22:46:36.768890857 +0530:2022-08-16 22:46:37.768890857 +0530:/var/crash/_opt_google_chrome_chrome.1000.crash 664:1000:124:0:2022-08-16 22:46:37.772890783 +0530:2022-08-16 22:46:37.772890783 +0530:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:124:672458:2022-08-14 18:59:42.264840602 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_usr_libexec_gvfsd-mtp.1000.crash 600:117:124:37:2022-08-16 22:46:39.708866983 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 04:31:10 2022 InstallationDate: Installed on 2022-08-08 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nipun 3034 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-08 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Precision 3541 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=8be20bde-302f-458f-9ea0-25e3f3b387ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 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.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/30/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.1 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.1:bd03/30/2022:br1.19:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987184/+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 1987184] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1987184/+attachment/5611394/+files/ProcModules.txt -- 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/1987184 Title: I am not sure about crash reports but I am having multiple issues with keyboard and touchpad.Touchpad gets stuck and keyboard keys are starts working erractically Status in linux package in Ubuntu: Confirmed Bug description: OS VERSION: Ubuntu 22.04 Laptop: Dell Precision 5550 Keyboard Layout Set: English(US) Touch pad gets stuck quite frequently while external mouse works just fine during that time. Sometimes using "sudo modprode psmouse" make touchpad start working again. Keyboard start working erratically suddenly and os suddenly starts acting erratically random things like opening mouse right click menu,closing apps,minimizing apps screen and so on.Normally issue comes while using vsCode since I do most my text work there. ctrl,shift,down arrow keys especially trigger this behaviour. I have no idea why this is happening though I know it did not happen in Ubuntu 20. Things get so bad only option is to reboot. And this happens quite frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:57730349:2022-08-16 22:46:36.768890857 +0530:2022-08-16 22:46:37.768890857 +0530:/var/crash/_opt_google_chrome_chrome.1000.crash 664:1000:124:0:2022-08-16 22:46:37.772890783 +0530:2022-08-16 22:46:37.772890783 +0530:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:124:672458:2022-08-14 18:59:42.264840602 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_usr_libexec_gvfsd-mtp.1000.crash 600:117:124:37:2022-08-16 22:46:39.708866983 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 04:31:10 2022 InstallationDate: Installed on 2022-08-08 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nipun 3034 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-08 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Precision 3541 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=8be20bde-302f-458f-9ea0-25e3f3b387ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 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.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/30/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.1 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.1:bd03/30/2022:br1.19:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987184/+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 1987184] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1987184/+attachment/5611391/+files/ProcCpuinfo.txt -- 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/1987184 Title: I am not sure about crash reports but I am having multiple issues with keyboard and touchpad.Touchpad gets stuck and keyboard keys are starts working erractically Status in linux package in Ubuntu: Confirmed Bug description: OS VERSION: Ubuntu 22.04 Laptop: Dell Precision 5550 Keyboard Layout Set: English(US) Touch pad gets stuck quite frequently while external mouse works just fine during that time. Sometimes using "sudo modprode psmouse" make touchpad start working again. Keyboard start working erratically suddenly and os suddenly starts acting erratically random things like opening mouse right click menu,closing apps,minimizing apps screen and so on.Normally issue comes while using vsCode since I do most my text work there. ctrl,shift,down arrow keys especially trigger this behaviour. I have no idea why this is happening though I know it did not happen in Ubuntu 20. Things get so bad only option is to reboot. And this happens quite frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:57730349:2022-08-16 22:46:36.768890857 +0530:2022-08-16 22:46:37.768890857 +0530:/var/crash/_opt_google_chrome_chrome.1000.crash 664:1000:124:0:2022-08-16 22:46:37.772890783 +0530:2022-08-16 22:46:37.772890783 +0530:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:124:672458:2022-08-14 18:59:42.264840602 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_usr_libexec_gvfsd-mtp.1000.crash 600:117:124:37:2022-08-16 22:46:39.708866983 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 04:31:10 2022 InstallationDate: Installed on 2022-08-08 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nipun 3034 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-08 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Precision 3541 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=8be20bde-302f-458f-9ea0-25e3f3b387ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 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.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/30/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.1 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.1:bd03/30/2022:br1.19:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987184/+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 1987184] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1987184/+attachment/5611392/+files/ProcCpuinfoMinimal.txt -- 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/1987184 Title: I am not sure about crash reports but I am having multiple issues with keyboard and touchpad.Touchpad gets stuck and keyboard keys are starts working erractically Status in linux package in Ubuntu: Confirmed Bug description: OS VERSION: Ubuntu 22.04 Laptop: Dell Precision 5550 Keyboard Layout Set: English(US) Touch pad gets stuck quite frequently while external mouse works just fine during that time. Sometimes using "sudo modprode psmouse" make touchpad start working again. Keyboard start working erratically suddenly and os suddenly starts acting erratically random things like opening mouse right click menu,closing apps,minimizing apps screen and so on.Normally issue comes while using vsCode since I do most my text work there. ctrl,shift,down arrow keys especially trigger this behaviour. I have no idea why this is happening though I know it did not happen in Ubuntu 20. Things get so bad only option is to reboot. And this happens quite frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:57730349:2022-08-16 22:46:36.768890857 +0530:2022-08-16 22:46:37.768890857 +0530:/var/crash/_opt_google_chrome_chrome.1000.crash 664:1000:124:0:2022-08-16 22:46:37.772890783 +0530:2022-08-16 22:46:37.772890783 +0530:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:124:672458:2022-08-14 18:59:42.264840602 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_usr_libexec_gvfsd-mtp.1000.crash 600:117:124:37:2022-08-16 22:46:39.708866983 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 04:31:10 2022 InstallationDate: Installed on 2022-08-08 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nipun 3034 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-08 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Precision 3541 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=8be20bde-302f-458f-9ea0-25e3f3b387ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 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.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/30/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.1 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.1:bd03/30/2022:br1.19:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987184/+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 1987184] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1987184/+attachment/5611393/+files/ProcInterrupts.txt -- 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/1987184 Title: I am not sure about crash reports but I am having multiple issues with keyboard and touchpad.Touchpad gets stuck and keyboard keys are starts working erractically Status in linux package in Ubuntu: Confirmed Bug description: OS VERSION: Ubuntu 22.04 Laptop: Dell Precision 5550 Keyboard Layout Set: English(US) Touch pad gets stuck quite frequently while external mouse works just fine during that time. Sometimes using "sudo modprode psmouse" make touchpad start working again. Keyboard start working erratically suddenly and os suddenly starts acting erratically random things like opening mouse right click menu,closing apps,minimizing apps screen and so on.Normally issue comes while using vsCode since I do most my text work there. ctrl,shift,down arrow keys especially trigger this behaviour. I have no idea why this is happening though I know it did not happen in Ubuntu 20. Things get so bad only option is to reboot. And this happens quite frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:57730349:2022-08-16 22:46:36.768890857 +0530:2022-08-16 22:46:37.768890857 +0530:/var/crash/_opt_google_chrome_chrome.1000.crash 664:1000:124:0:2022-08-16 22:46:37.772890783 +0530:2022-08-16 22:46:37.772890783 +0530:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:124:672458:2022-08-14 18:59:42.264840602 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_usr_libexec_gvfsd-mtp.1000.crash 600:117:124:37:2022-08-16 22:46:39.708866983 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 04:31:10 2022 InstallationDate: Installed on 2022-08-08 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nipun 3034 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-08 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Precision 3541 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=8be20bde-302f-458f-9ea0-25e3f3b387ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 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.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/30/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.1 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.1:bd03/30/2022:br1.19:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987184/+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 1987184] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1987184/+attachment/5611387/+files/Lsusb.txt -- 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/1987184 Title: I am not sure about crash reports but I am having multiple issues with keyboard and touchpad.Touchpad gets stuck and keyboard keys are starts working erractically Status in linux package in Ubuntu: Confirmed Bug description: OS VERSION: Ubuntu 22.04 Laptop: Dell Precision 5550 Keyboard Layout Set: English(US) Touch pad gets stuck quite frequently while external mouse works just fine during that time. Sometimes using "sudo modprode psmouse" make touchpad start working again. Keyboard start working erratically suddenly and os suddenly starts acting erratically random things like opening mouse right click menu,closing apps,minimizing apps screen and so on.Normally issue comes while using vsCode since I do most my text work there. ctrl,shift,down arrow keys especially trigger this behaviour. I have no idea why this is happening though I know it did not happen in Ubuntu 20. Things get so bad only option is to reboot. And this happens quite frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:57730349:2022-08-16 22:46:36.768890857 +0530:2022-08-16 22:46:37.768890857 +0530:/var/crash/_opt_google_chrome_chrome.1000.crash 664:1000:124:0:2022-08-16 22:46:37.772890783 +0530:2022-08-16 22:46:37.772890783 +0530:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:124:672458:2022-08-14 18:59:42.264840602 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_usr_libexec_gvfsd-mtp.1000.crash 600:117:124:37:2022-08-16 22:46:39.708866983 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 04:31:10 2022 InstallationDate: Installed on 2022-08-08 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nipun 3034 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-08 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Precision 3541 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=8be20bde-302f-458f-9ea0-25e3f3b387ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 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.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/30/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.1 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.1:bd03/30/2022:br1.19:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987184/+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 1987184] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1987184/+attachment/5611385/+files/Lspci.txt -- 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/1987184 Title: I am not sure about crash reports but I am having multiple issues with keyboard and touchpad.Touchpad gets stuck and keyboard keys are starts working erractically Status in linux package in Ubuntu: Confirmed Bug description: OS VERSION: Ubuntu 22.04 Laptop: Dell Precision 5550 Keyboard Layout Set: English(US) Touch pad gets stuck quite frequently while external mouse works just fine during that time. Sometimes using "sudo modprode psmouse" make touchpad start working again. Keyboard start working erratically suddenly and os suddenly starts acting erratically random things like opening mouse right click menu,closing apps,minimizing apps screen and so on.Normally issue comes while using vsCode since I do most my text work there. ctrl,shift,down arrow keys especially trigger this behaviour. I have no idea why this is happening though I know it did not happen in Ubuntu 20. Things get so bad only option is to reboot. And this happens quite frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:57730349:2022-08-16 22:46:36.768890857 +0530:2022-08-16 22:46:37.768890857 +0530:/var/crash/_opt_google_chrome_chrome.1000.crash 664:1000:124:0:2022-08-16 22:46:37.772890783 +0530:2022-08-16 22:46:37.772890783 +0530:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:124:672458:2022-08-14 18:59:42.264840602 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_usr_libexec_gvfsd-mtp.1000.crash 600:117:124:37:2022-08-16 22:46:39.708866983 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 04:31:10 2022 InstallationDate: Installed on 2022-08-08 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nipun 3034 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-08 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Precision 3541 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=8be20bde-302f-458f-9ea0-25e3f3b387ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 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.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/30/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.1 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.1:bd03/30/2022:br1.19:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987184/+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 1987184] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1987184/+attachment/5611383/+files/CurrentDmesg.txt -- 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/1987184 Title: I am not sure about crash reports but I am having multiple issues with keyboard and touchpad.Touchpad gets stuck and keyboard keys are starts working erractically Status in linux package in Ubuntu: Confirmed Bug description: OS VERSION: Ubuntu 22.04 Laptop: Dell Precision 5550 Keyboard Layout Set: English(US) Touch pad gets stuck quite frequently while external mouse works just fine during that time. Sometimes using "sudo modprode psmouse" make touchpad start working again. Keyboard start working erratically suddenly and os suddenly starts acting erratically random things like opening mouse right click menu,closing apps,minimizing apps screen and so on.Normally issue comes while using vsCode since I do most my text work there. ctrl,shift,down arrow keys especially trigger this behaviour. I have no idea why this is happening though I know it did not happen in Ubuntu 20. Things get so bad only option is to reboot. And this happens quite frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:57730349:2022-08-16 22:46:36.768890857 +0530:2022-08-16 22:46:37.768890857 +0530:/var/crash/_opt_google_chrome_chrome.1000.crash 664:1000:124:0:2022-08-16 22:46:37.772890783 +0530:2022-08-16 22:46:37.772890783 +0530:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:124:672458:2022-08-14 18:59:42.264840602 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_usr_libexec_gvfsd-mtp.1000.crash 600:117:124:37:2022-08-16 22:46:39.708866983 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 04:31:10 2022 InstallationDate: Installed on 2022-08-08 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nipun 3034 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-08 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Precision 3541 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=8be20bde-302f-458f-9ea0-25e3f3b387ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 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.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/30/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.1 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.1:bd03/30/2022:br1.19:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987184/+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 1987184] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1987184/+attachment/5611384/+files/IwConfig.txt -- 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/1987184 Title: I am not sure about crash reports but I am having multiple issues with keyboard and touchpad.Touchpad gets stuck and keyboard keys are starts working erractically Status in linux package in Ubuntu: Confirmed Bug description: OS VERSION: Ubuntu 22.04 Laptop: Dell Precision 5550 Keyboard Layout Set: English(US) Touch pad gets stuck quite frequently while external mouse works just fine during that time. Sometimes using "sudo modprode psmouse" make touchpad start working again. Keyboard start working erratically suddenly and os suddenly starts acting erratically random things like opening mouse right click menu,closing apps,minimizing apps screen and so on.Normally issue comes while using vsCode since I do most my text work there. ctrl,shift,down arrow keys especially trigger this behaviour. I have no idea why this is happening though I know it did not happen in Ubuntu 20. Things get so bad only option is to reboot. And this happens quite frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:57730349:2022-08-16 22:46:36.768890857 +0530:2022-08-16 22:46:37.768890857 +0530:/var/crash/_opt_google_chrome_chrome.1000.crash 664:1000:124:0:2022-08-16 22:46:37.772890783 +0530:2022-08-16 22:46:37.772890783 +0530:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:124:672458:2022-08-14 18:59:42.264840602 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_usr_libexec_gvfsd-mtp.1000.crash 600:117:124:37:2022-08-16 22:46:39.708866983 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 04:31:10 2022 InstallationDate: Installed on 2022-08-08 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nipun 3034 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-08 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Precision 3541 Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=8be20bde-302f-458f-9ea0-25e3f3b387ba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 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.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/30/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.1 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.1:bd03/30/2022:br1.19:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987184/+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 1987184] Re: I am not sure about crash reports but I am having multiple issues with keyboard and touchpad.Touchpad gets stuck and keyboard keys are starts working erractically
apport information ** Tags added: apport-collected ** Description changed: OS VERSION: Ubuntu 22.04 Laptop: Dell Precision 5550 Keyboard Layout Set: English(US) Touch pad gets stuck quite frequently while external mouse works just fine during that time. Sometimes using "sudo modprode psmouse" make touchpad start working again. Keyboard start working erratically suddenly and os suddenly starts acting erratically random things like opening mouse right click menu,closing apps,minimizing apps screen and so on.Normally issue comes while using vsCode since I do most my text work there. ctrl,shift,down arrow keys especially trigger this behaviour. I have no idea why this is happening though I know it did not happen in Ubuntu 20. Things get so bad only option is to reboot. And this happens quite frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:57730349:2022-08-16 22:46:36.768890857 +0530:2022-08-16 22:46:37.768890857 +0530:/var/crash/_opt_google_chrome_chrome.1000.crash 664:1000:124:0:2022-08-16 22:46:37.772890783 +0530:2022-08-16 22:46:37.772890783 +0530:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:124:672458:2022-08-14 18:59:42.264840602 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_usr_libexec_gvfsd-mtp.1000.crash 600:117:124:37:2022-08-16 22:46:39.708866983 +0530:2022-08-17 13:10:25.015404871 +0530:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 04:31:10 2022 InstallationDate: Installed on 2022-08-08 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: nipun 3034 F pulseaudio + CRDA: N/A + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-08-08 (16 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + MachineType: Dell Inc. Precision 3541 + Package: linux (not installed) + ProcEnviron: + LANGUAGE=en_IN:en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_IN + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=8be20bde-302f-458f-9ea0-25e3f3b387ba ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 + 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.15.0-46-generic N/A + linux-backports-modules-5.15.0-46-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.4 + Tags: jammy + Uname: Linux 5.15.0-46-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 03/30/2022 + dmi.bios.release: 1.19 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.19.1 + dmi.board.name: 0Y8H01 + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.19.1:bd03/30/2022:br1.19:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A: + dmi.product.family: Precision + dmi.product.name: Precision 3541 + dmi.product.sku: 091A + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1987184/+attachment/5611382/+files/AlsaInfo.txt -- 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/1987184 Title: I am not sure about crash reports but I am having multiple issues with keyboard and touchpad.Touchpad gets stuck and keyboard keys are starts working erractically Status in linux package in Ubuntu: Confirmed Bug description: OS VERSION: Ubuntu 22.04 Laptop: Dell Precision 5550 Keyboard Layout Set: English(US) Touch pad gets stuck quite frequently while external mouse works just fine during that time. Sometimes using "sudo modprode psmouse" make touchpad start working again. Keyboard start working erratically suddenly and os suddenly starts acting erratically random things like opening mouse right click menu,closing apps,minimizing apps screen and so on.Normally issue comes while using vsCode since I do most my text
[Kernel-packages] [Bug 1987430] Re: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs
I booted the "stock" VM with slub_nomerge and after two hours of uptime (and constant Go compilation and testing), the top counts in slabtop for active objects and memory use are: OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME 536896 536869 99%2.00K 33556 16 1073792K kmalloc-2k 536350 536350 100%0.02K 3155 170 12620K audit_buffer 536320 536320 100%0.25K 33520 16134080K skbuff_head_cache 489099 489099 100%0.10K 12541 39 50164K buffer_head 78057 75309 96%0.19K 3717 21 14868K dentry 65110 59084 90%0.02K383 170 1532K lsm_inode_cache OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME 537104 537097 99%2.00K 33569 16 1074208K kmalloc-2k 536528 536528 100%0.25K 33533 16134132K skbuff_head_cache 465348 397547 85%0.10K 11932 39 47728K buffer_head 36936 36471 98%1.15K 1368 27 43776K ext4_inode_cache 76839 56841 73%0.19K 3659 21 14636K dentry 20988 19716 93%0.62K 1749 12 13992K inode_cache 536520 536520 100%0.02K 3156 170 12624K audit_buffer It seems suggestive that the top three by count have almost the same count (and it's a large one). -- 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/1987430 Title: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs Status in linux package in Ubuntu: Confirmed Bug description: Since updating to kernel 5.15.0-46-generic (package version 5.15.0-46.49), all of our Ubuntu 22.04 LTS servers are leaking kernel memory; our first server with 8 GB of RAM just fatally OOMed, causing us to detect this. Inspection of OOM reports, /proc/meminfo, and /proc/slabinfo says that it's mostly going to unreclaimable kmalloc-2k slabs: Aug 23 12:51:11 cluster kernel: [361299.864757] Unreclaimable slab info: Aug 23 12:51:11 cluster kernel: [361299.864757] Name Used Total [...] Aug 23 12:51:11 cluster kernel: [361299.864924] kmalloc-2k 6676584KB6676596KB Most of our machines appear to be leaking slab memory at a rate of around 20 to 40 Mbytes/hour, with some machines leaking much faster; the champions are leaking kernel memory at 145 Mbytes/hour and 237 Mbytes/hour. We aren't running any proprietary kernel modules and our only unusual kernel configuration is that we've disabled AppArmor with 'apparmor=0' on the kernel command line. /proc/version_signature: Ubuntu 5.15.0-46.49-generic 5.15.39 Full kernel command line from the Dell R240 system that fatally OOMd: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=3165564f-a2dd-4b39-935b-114f3e23ff54 ro console=ttyS0,115200 console=tty0 apparmor=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987430/+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
Earlier today, I upgraded my Mint 20.3 system to Mint 21.0 and got this "out of memory" issue (Asus ROG G752VT laptop.). The fix in comment #41 and #89 worked (changing the compression to 19), but a lot of the steps were not needed. This is the minimal steps needed, (maybe fewer possible, anybody up for some code golf?): $ sudo su - # mkdir root He probably had his disk encrypted, I do not: # cryptsetup luksOpen /dev/nvme0n1p3 nvme0n1p3_crypt This one was very different for me due to mint vs Ubuntu. # mount /dev/mapper/vgmint-root ./root was # mount /dev/mapper/vgubuntu-root ./root This one makes the computer think the normal root is really root to fake out update-initramfs: # chroot ./root Yes, do this: # ### Now edit line 196 of /usr/sbin/mkinitramfs to to use -19 instead of -1 This wasn't completely happy with me, but it worked out ok for me. # update-initramfs -u -k all This command completely failed for me, but it didn't seem to hate me afterwards: # update-grub # exit # reboot I hope you have a happy reboot too. Then re-run # update-initramfs -u -k all and # update-grub To clean up any oddities. I wish there were a way to recompress this from grub though. -- 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: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [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 fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we can ask 32bits+ on AllocatePages(). As most X86_64 platforms should support 64 bits addressing, we should extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available memory. * When users grown the initramfs, then probably will get initramfs not found which really annoyed and impact the user experience (system not able to boot). [Test Plan] * detailed instructions how to reproduce the bug: 1. Any method to grow the initramfs, such as install nvidia-driver. 2. If developers would like to reproduce, then could dd if=/dev/random of=... bs=1M count=500, something like: ``` $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500 ``` And then update-initramfs * After applying my patches, the issue is gone. * I did also test my test grubx64.efi in: 1. X86_64 qemu with 1.1. 60M initramfs + 5.15.0-37-generic kernel 1.2. 565M initramfs + 5.17.0-1011-oem kernel 2. Amd64 HP mobile workstation with 2.1. 65M initramfs + 5.15.0-39-generic kernel 2.2. 771M initramfs + 5.17.0-1011-oem kernel All working well. [Where problems could occur] * The changes almost in i386/efi, thus the impact will be in the i386 / x86_64 EFI system. The other change is to modify the “grub-core/kern/efi/mm.c” but I use the original addressing for “arm/arm64/ia64/riscv32/riscv64”. Thus it should not impact them. * There is a “#if defined(__x86_64__)” which intent to limit
[Kernel-packages] [Bug 1968391] Re: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS
FML, it's still happening - what even *is* a "beacon-loss' event? Is there any situation where getting reconnected every few minutes would ever even make sense?! Aug 24 14:43:21 banana wpa_supplicant[1164]: wlp4s0: CTRL-EVENT-BEACON-LOSS Aug 24 14:58:41 banana wpa_supplicant[897]: wlp4s0: CTRL-EVENT-BEACON-LOSS Aug 24 15:14:02 banana wpa_supplicant[897]: wlp4s0: CTRL-EVENT-BEACON-LOSS I couldn't find 5.15.0-23-generic so I used 5.15.0 root@banana:~# uname -a Linux banana 5.17.11-051711-generic #202205251331 SMP PREEMPT Wed May 25 13:57:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux I swear this hardware used to work fine on focal. I'll try put back the BSSID and power save mode too - i'm not sure what else to try. -- 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/1968391 Title: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS Status in linux package in Ubuntu: Fix Released Bug description: Using the current beta of Jammy, I no longer have stable WiFi after April 5, 2022 update of wpasupplicant from 2:2.10-2 to 2:2.10-6. There is a chance it may also be related to network-manager going from 1.36.4-1ubuntu1 to 1.36.4-2ubuntu1, but the logs seems to point to wpasupplicant (see below) Wifi is stable often, but also often it fails to load webpages intermittently or fails to download the packages using apt for example, so it's not browser related. Example output of journalctl -xe -u wpasupplicant: Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:23:4c:3c completed [id=0 id_str=] Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=7200 Apr 08 19:26:32 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:33 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:34 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:35 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:36 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:37 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:38 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-DISCONNECTED bssid=fc:34:97:23:4c:3c reason=4 locally_generated=1 Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:42 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: SME: Trying to authenticate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz) Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Trying to associate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz) Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Associated with fc:34:97:23:4c:3c Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CA Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: WPA: Key negotiation completed with fc:34:97:23:4c:3c [PTK=CCMP GTK=CCMP] Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:23:4c:3c completed [id=0 id_str=] Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=7200 Apr 08 19:29:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=-94 txrate=27 Apr 08 19:49:04 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-73 noise=-95 txrate=27 Apr 08 19:59:04 weasel wpa_supplicant[772]: wlp13s0: WPA: Group rekeying completed with fc:34:97:23:4c:3c [GTK=CCMP] Apr 08 20:00:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=-95 txrate=243000 Additional info: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy wpasupplicant wpasupplicant:
[Kernel-packages] [Bug 1984004] Re: Linux Firmware drops AMD RX6650 XT Performance
Using the "plain" link on the right side got the actual firmware files, and that works. Tested: 1) Deleted contents of /lib/firmware/amdgpu , populated it with the 12 dimgrey firmware files, "sudo update-initramfs -c -k all", rebooted. System started, FPS are high. 2) Reinstalled 20220329.git681281e4-0ubuntu3.4 from Synaptic. Updated the 12 dimgrey firmware files, "sudo update-initramfs -c -k all", rebooted. System started, FPS are high. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1984004 Title: Linux Firmware drops AMD RX6650 XT Performance Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Triaged Bug description: Kernel: 5.15.0-43-generic linux-firmware: 20220329.git681281e4-0ubuntu3.3 Tested with: Mint 21 Cinnamon (Ubuntu 22.04 based) In e.g. the Unigine benchmark, the linux-firmware packages drops the performance of my AMD RX 6650 XT GPU from 98 FPS in 1080p-high down to 23 FPS. That wasn't a problem in Mint 20.3 with kernel 5.15 (Ubuntu 20.04 based). Getting the firmware directly from git brings the performance back to about 100 FPS: git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git cd linux-firmware sudo make install sudo update-initramfs -c -k all Re-installing the linux-firmware package causes the performance to drop again. So there is a problem with the linux firmware at least for the RX 6650 XT, maybe for the whole RX 6000 series. The linux-firmware package in Ubuntu 22.04 should be updated. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: daelach1352 F pulseaudio /dev/snd/controlC0: daelach1352 F pulseaudio /dev/snd/controlC1: daelach1352 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Dependencies: firmware-sof-signed 2.0-1ubuntu3 [origin: Ubuntu] DistroRelease: Linux Mint 21 InstallationDate: Installed on 2020-08-24 (714 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: lono wireless extensions. enp6s0no wireless extensions. MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=UUID=a4b18dd9-4989-4bf5-8107-e55b8f8f6df4 ro amd_iommu=on iommu=pt quiet loglevel=3 splash ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Tags: vanessa third-party-packages Uname: Linux 5.15.0-43-generic x86_64 UnreportableReason: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4901 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4901:bd07/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1984004/+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 1987507] Re: Migrate oem-20.04 to hwe-5.15
** Summary changed: - Transition oem-20.04 to hwe-5.15 + Migrate oem-20.04 to hwe-5.15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987507 Title: Migrate oem-20.04 to hwe-5.15 Status in linux-meta-hwe-5.15 package in Ubuntu: Invalid Status in linux-restricted-modules-hwe-5.15 package in Ubuntu: Invalid Status in linux-meta-hwe-5.15 source package in Focal: New Status in linux-restricted-modules-hwe-5.15 source package in Focal: New Bug description: Migrate oem-5.14 to hwe-5.15 now that there should be no functional regressions left anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.15/+bug/1987507/+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 1987430] Re: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs
It appears that the combination of our audit rules being enabled and apparmor=0 is what triggers the leak. My test case is repeatedly compiling Go from source and running its self tests (cloning https://go.googlesource.com/go, then 'cd go/src; while true; do ./all.bash; done'). On a VM configured as one of our machines (with audit rules), this leaks visibly. On a basically stock 22.04 VM (and thus with no audit rules), this doesn't leak. If I disable auditd on our configuration, it stops leaking. On the stock configuration, if I install auditd and our rules, and enable auditd (and reboot), it immediately starts leaking with rapid growth in kmalloc-2k. Taken from slabtop on the stock VM + auditd: OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME 81360 81355 99%2.00K 5085 16162720K kmalloc-2k 44010 39386 89%1.15K 1630 27 52160K ext4_inode_cache [...] This is on a VM that's been up only 24 minutes so far; this is the top slab entry, far ahead of the second placed one I've also shown. And just in the process of writing this comment, it's grown to 206080K. Stopping auditd on the our-setup VM seems to stop further kmalloc-2k slab growth but doesn't reduce the current size. -- 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/1987430 Title: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs Status in linux package in Ubuntu: Confirmed Bug description: Since updating to kernel 5.15.0-46-generic (package version 5.15.0-46.49), all of our Ubuntu 22.04 LTS servers are leaking kernel memory; our first server with 8 GB of RAM just fatally OOMed, causing us to detect this. Inspection of OOM reports, /proc/meminfo, and /proc/slabinfo says that it's mostly going to unreclaimable kmalloc-2k slabs: Aug 23 12:51:11 cluster kernel: [361299.864757] Unreclaimable slab info: Aug 23 12:51:11 cluster kernel: [361299.864757] Name Used Total [...] Aug 23 12:51:11 cluster kernel: [361299.864924] kmalloc-2k 6676584KB6676596KB Most of our machines appear to be leaking slab memory at a rate of around 20 to 40 Mbytes/hour, with some machines leaking much faster; the champions are leaking kernel memory at 145 Mbytes/hour and 237 Mbytes/hour. We aren't running any proprietary kernel modules and our only unusual kernel configuration is that we've disabled AppArmor with 'apparmor=0' on the kernel command line. /proc/version_signature: Ubuntu 5.15.0-46.49-generic 5.15.39 Full kernel command line from the Dell R240 system that fatally OOMd: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=3165564f-a2dd-4b39-935b-114f3e23ff54 ro console=ttyS0,115200 console=tty0 apparmor=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987430/+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 1983436] Re: BUG:soft lockup - CPU#0 stuck for 36s! rcu_core_si kernel/rcu/tree.c:2807
@saltf1sh, thanks for reporting this, however, the 5.13 kernel is no longer supported (since July 2022). Are you able to reproduce the problem on a kernel version that's still supported (like 5.4 or 5.15)? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1983436 Title: BUG:soft lockup - CPU#0 stuck for 36s! rcu_core_si kernel/rcu/tree.c:2807 Status in linux-hwe-5.13 package in Ubuntu: New Bug description: We would like to report the following bug which has been found by our modified version of syzkaller. rcu_core_si in kernel/rcu/tree.c:2807 in the Linux kernel through 5.13 allows attackers to cause a denial of service (soft lockup) via a large number of different function calls. description: BUG: soft lockup in rcu_core_si affected file: kernel/rcu/tree.c kernel version: 5.13 kernel config, syzkaller reproducer and raw console output are all in the attachments. == Crash log: == watchdog: BUG: soft lockup - CPU#0 stuck for 36s! [syz-executor.6:14479] Modules linked in: CPU: 0 PID: 14479 Comm: syz-executor.6 Not tainted 5.13.19+ #6 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:cred_label security/apparmor/include/cred.h:27 [inline] RIP: 0010:apparmor_cred_free+0x5f/0x1a0 security/apparmor/lsm.c:69 Code: 01 00 00 48 63 1d a1 fd 4d 02 49 03 5c 24 78 48 b8 00 00 00 00 00 fc ff df 48 89 da 48 c1 ea 03 80 3c 02 00 0f 85 08 01 00 00 <4c> 8b 2b 4d 85 ed 74 68 e8 74 53 4b ff be 04 00 00 00 4c 89 ef bb RSP: 0018:888056609dc8 EFLAGS: 00010246 RAX: dc00 RBX: 888005c8fc80 RCX: 967eb4fd RDX: 111000b91f90 RSI: 0100 RDI: 888005821000 RBP: 888056609de8 R08: 0001 R09: ed1000b04201 R10: 888005821003 R11: ed1000b04200 R12: 888005821000 R13: 888005821000 R14: 888005821078 R15: 888007ba8000 FS: 7f5f81a40700() GS:88805660() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7ffe8252bb80 CR3: 03cf6006 CR4: 00770ef0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 PKRU: 5554 Call Trace: security_cred_free+0x83/0x130 security/security.c:1881 put_cred_rcu+0x71/0x360 kernel/cred.c:115 rcu_do_batch kernel/rcu/tree.c:2559 [inline] rcu_core+0x536/0x12f0 kernel/rcu/tree.c:2794 rcu_core_si+0xe/0x10 kernel/rcu/tree.c:2807 __do_softirq+0x187/0x576 kernel/softirq.c:559 invoke_softirq kernel/softirq.c:433 [inline] __irq_exit_rcu kernel/softirq.c:637 [inline] irq_exit_rcu+0x120/0x150 kernel/softirq.c:649 sysvec_apic_timer_interrupt+0x79/0x90 arch/x86/kernel/apic/apic.c:1100 asm_sysvec_apic_timer_interrupt+0x12/0x20 arch/x86/include/asm/idtentry.h:638 RIP: 0010:0xc01e0801 Code: cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc 0f 1f 44 00 00 <55> 48 89 e5 53 41 55 31 c0 45 31 ed 48 89 fb b8 ff ff ff 7f 41 5d RSP: 0018:888006ec7d58 EFLAGS: 0246 RAX: c01e07fc RBX: 7fff RCX: 95ccef6a RDX: 888007ba8000 RSI: c9763048 RDI: 888006ec7e10 RBP: 888006ec7eb8 R08: 0001 R09: ed1005374c87 R10: 888029ba6437 R11: ed1005374c86 R12: 888006ec7e10 R13: 888029ba6400 R14: c9763000 R15: dc00 Sending NMI from CPU 0 to CPUs 1: NMI backtrace for cpu 1 CPU: 1 PID: 27 Comm: khungtaskd Not tainted 5.13.19+ #6 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:check_hung_uninterruptible_tasks kernel/hung_task.c:190 [inline] RIP: 0010:watchdog+0x1e1/0xa60 kernel/hung_task.c:294 Code: 45 a8 e8 e2 74 fd ff 49 8d 87 40 03 00 00 48 b9 00 00 00 00 00 fc ff df 48 89 45 c0 48 c1 e8 03 80 3c 08 00 0f 85 dd 07 00 00 <49> 8b 9f 40 03 00 00 48 be 00 00 00 00 00 fc ff df 4c 8d 63 10 4c RSP: :888001d77ea0 EFLAGS: 00010246 RAX: 111000dea98b RBX: 88800669b630 RCX: dc00 RDX: 888001d6a080 RSI: RDI: 888005e4c918 RBP: 888001d77f00 R08: 0001 R09: fbfff34354d9 R10: 9a1aa6c7 R11: fbfff34354d8 R12: 88800669c010 R13: 003fff85 R14: 000100021a4b R15: 888006f54918 FS: () GS:88805670() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7ffcc3c83ce8 CR3: 04310004 CR4: 00770ee0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400
[Kernel-packages] [Bug 1973300] Re: NVIDIA CVE-2022-{28181|28183|28184|28185|28191|28192}
** Changed in: linux-restricted-modules (Ubuntu) Status: New => Fix Committed ** Changed in: linux-restricted-modules (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux-restricted-modules (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-restricted-modules (Ubuntu Impish) Status: New => Fix Committed ** Changed in: linux-restricted-modules (Ubuntu Jammy) Status: New => Fix Committed -- 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/1973300 Title: NVIDIA CVE-2022-{28181|28183|28184|28185|28191|28192} Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-470 package in Ubuntu: Fix Released Status in fabric-manager-510 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-470 package in Ubuntu: Fix Released Status in libnvidia-nscq-510 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-390 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-510 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-510-server package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Released Status in fabric-manager-470 source package in Bionic: Fix Released Status in fabric-manager-510 source package in Bionic: Fix Released Status in libnvidia-nscq-450 source package in Bionic: Fix Released Status in libnvidia-nscq-470 source package in Bionic: Fix Released Status in libnvidia-nscq-510 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510-server source package in Bionic: Fix Released Status in fabric-manager-450 source package in Focal: Fix Released Status in fabric-manager-470 source package in Focal: Fix Released Status in fabric-manager-510 source package in Focal: Fix Released Status in libnvidia-nscq-450 source package in Focal: Fix Released Status in libnvidia-nscq-470 source package in Focal: Fix Released Status in libnvidia-nscq-510 source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-510 source package in Focal: Fix Released Status in nvidia-graphics-drivers-510-server source package in Focal: Fix Released Status in fabric-manager-450 source package in Impish: Fix Released Status in fabric-manager-470 source package in Impish: Fix Released Status in fabric-manager-510 source package in Impish: Fix Released Status in libnvidia-nscq-450 source package in Impish: Fix Released Status in libnvidia-nscq-470 source package in Impish: Fix Released Status in libnvidia-nscq-510 source package in Impish: Fix Released Status in linux-restricted-modules source package in Impish: Fix Committed Status in nvidia-graphics-drivers-390 source package in Impish: Fix Released Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Released Status in nvidia-graphics-drivers-470 source package in Impish: Fix Released Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Released Status in nvidia-graphics-drivers-510 source package in Impish: Fix Released Status in nvidia-graphics-drivers-510-server source package in Impish: Fix Released Status in fabric-manager-450 source package in Jammy: Fix Released Status in fabric-manager-470 source package in Jammy: Fix Released Status in fabric-manager-510 source package in Jammy: Fix Released Status in libnvidia-nscq-450 source package in Jammy: Fix Released Status in libnvidia-nscq-470 source package in Jammy: Fix Released Status in libnvidia-nscq-510 source package in Jammy: Fix Released Status in
[Kernel-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
** Changed in: openafs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Fix Released Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: Confirmed Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1933880] Re: systemd-logind crash when suspend with nvidia-suspend.service masked, bringing session down with it
I remove the files in `/etc/systemd/system/systemd- suspend.service.wants` and it works -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-465 in Ubuntu. https://bugs.launchpad.net/bugs/1933880 Title: systemd-logind crash when suspend with nvidia-suspend.service masked, bringing session down with it Status in nvidia-graphics-drivers-465 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Run `sudo apt install nvidia-driver-465`. Then, without a need for a restart, run `sudo apt autoremove nvidia-driver-465`. 2. Leaving the terminal open, suspend the machine. Expected behavior: the machine suspend successfully and can be woken up successfully. Actual behavior: the machine doesn't suspend. It either: - hang with no respond other than SysRq+REISUB (or maybe network, but I didn't test), or - return you back to the login screen. Upon logging in, you'll notice that the terminal you opened is gone. Upon further inspection (on a session that doesn't hang), it's been found that X server died with: Fatal server error: [66.422] (EE) systemd-logind disappeared (stopped/restarted?) And checking journal for systemd-logind log, it said: Error during inhibitor-delayed operation (already returned success to client): Unit nvidia-suspend.service is masked. before the new process takes it place. The system is Ubuntu 20.04, X.org session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.7 ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 03:34:00 2021 InstallationDate: Installed on 2021-03-15 (105 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=th_TH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=06f2a676-a62c-443a-8bc8-4e0eda4600f4 ro log_buf_len=2M quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55756 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrEUCN31WW:bd01/01/2021:br1.31:efr1.31:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55756WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-465/+bug/1933880/+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 1982501] Re: NVIDIA CVE-2022-{31607|31608}
** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-510-server (Ubuntu) Status: New => Fix Committed -- 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/1982501 Title: NVIDIA CVE-2022-{31607|31608} Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-470 package in Ubuntu: Fix Released Status in fabric-manager-510 package in Ubuntu: Fix Released Status in fabric-manager-515 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-470 package in Ubuntu: Fix Released Status in libnvidia-nscq-510 package in Ubuntu: Fix Released Status in libnvidia-nscq-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-450-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-510-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515-server package in Ubuntu: Fix Released Status in fabric-manager-450 source package in Bionic: Fix Released Status in fabric-manager-470 source package in Bionic: Fix Released Status in fabric-manager-510 source package in Bionic: Fix Released Status in fabric-manager-515 source package in Bionic: Fix Released Status in libnvidia-nscq-450 source package in Bionic: Fix Released Status in libnvidia-nscq-470 source package in Bionic: Fix Released Status in libnvidia-nscq-510 source package in Bionic: Fix Released Status in libnvidia-nscq-515 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-515 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-515-server source package in Bionic: Fix Released Status in fabric-manager-450 source package in Focal: Fix Released Status in fabric-manager-470 source package in Focal: Fix Released Status in fabric-manager-510 source package in Focal: Fix Released Status in fabric-manager-515 source package in Focal: Fix Released Status in libnvidia-nscq-450 source package in Focal: Fix Released Status in libnvidia-nscq-470 source package in Focal: Fix Released Status in libnvidia-nscq-510 source package in Focal: Fix Released Status in libnvidia-nscq-515 source package in Focal: Fix Released Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-510 source package in Focal: Fix Released Status in nvidia-graphics-drivers-510-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in nvidia-graphics-drivers-515-server source package in Focal: Fix Released Status in fabric-manager-450 source package in Jammy: Fix Released Status in fabric-manager-470 source package in Jammy: Fix Released Status in fabric-manager-510 source package in Jammy: Fix Released Status in fabric-manager-515 source package in Jammy: Fix Released Status in libnvidia-nscq-450 source package in Jammy: Fix Released Status in libnvidia-nscq-470 source package in Jammy: Fix Released Status in libnvidia-nscq-510 source package in Jammy: Fix Released Status in libnvidia-nscq-515 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-390 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470 source package in Jammy:
[Kernel-packages] [Bug 1922910] Re: Unable to deploy HWE kernel with sub-arch set to xgene-uboot
I wonder if we just need to treat xgene-uboot as an alias for generic in the MAAS code? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922910 Title: Unable to deploy HWE kernel with sub-arch set to xgene-uboot Status in MAAS: New Status in linux package in Ubuntu: Expired Bug description: When trying to deploy Moonshot nodes, the sub-arch must be set to xgene-uboot for it to be deployed with GA kernel. However, when trying to deploy it with the HWE kernel it will complain that: Subarchitecture(xgene-uboot) must be generic when setting hwe_kernel. [ deleted the bit about how generic/hwe fails, because that is expected. this machine requires xgene-uboot/hwe ] To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1922910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922910] Re: Unable to deploy HWE kernel with sub-arch set to xgene-uboot
I'm not on the kernel team, but I'm not sure what would make this flavor invalid w/ HWE. The xgene-uboot flavor is merely a wrapped version of the -generic kernel. This kernel works fine on the target platform, once you can get it installed. ** Changed in: maas Status: Expired => New ** Description changed: When trying to deploy Moonshot nodes, the sub-arch must be set to xgene- uboot for it to be deployed with GA kernel. However, when trying to deploy it with the HWE kernel it will complain that: - Subarchitecture(xgene-uboot) must be generic when setting hwe_kernel. + Subarchitecture(xgene-uboot) must be generic when setting hwe_kernel. - Not sure if this is a bug in MAAS, or some by-design limitation. - - If I set the sub-arch to arm64/generic, the deployment for Xenial + - hwe-16.04 will drop into a boot loop with error message in console: - - append: nomodeset ro - root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/hwe-16.04/xenial/stable/squashfs - ip=mcdivitt35-kernel:BOOTIF ip6=off overlayroot=tmpfs - overlayroot_cfgdisk=disabled cc:{'datasource_list': ['MAAS']}end_cc - cloud-config-url=http://10.229.32.21:5248/MAAS/metadata/latest/by- - id/chbcrm/?op=get_preseed apparmor=0 log_host=10.229.32.21 log_port=5247 - --- console=ttyS0,9600nBad Linux ARM zImage magic! - - hyper-maas - MAAS version: 2.9.2 (9165-g.b5dc1fd6c) + [ deleted the bit about how generic/hwe fails, because that is expected. + this machine requires xgene-uboot/hwe ] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922910 Title: Unable to deploy HWE kernel with sub-arch set to xgene-uboot Status in MAAS: New Status in linux package in Ubuntu: Expired Bug description: When trying to deploy Moonshot nodes, the sub-arch must be set to xgene-uboot for it to be deployed with GA kernel. However, when trying to deploy it with the HWE kernel it will complain that: Subarchitecture(xgene-uboot) must be generic when setting hwe_kernel. [ deleted the bit about how generic/hwe fails, because that is expected. this machine requires xgene-uboot/hwe ] To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1922910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982501] Re: NVIDIA CVE-2022-{31607|31608}
This bug was fixed in the package nvidia-graphics-drivers-515 - 515.65.01-0ubuntu2 --- nvidia-graphics-drivers-515 (515.65.01-0ubuntu2) kinetic; urgency=medium * debian/nvidia_supported: - Add support for the open kernel driver using the --open argument. -- Alberto Milone Mon, 01 Aug 2022 19:55:45 + ** Changed in: nvidia-graphics-drivers-515 (Ubuntu) Status: New => Fix Released -- 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/1982501 Title: NVIDIA CVE-2022-{31607|31608} Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-470 package in Ubuntu: Fix Released Status in fabric-manager-510 package in Ubuntu: Fix Released Status in fabric-manager-515 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-470 package in Ubuntu: Fix Released Status in libnvidia-nscq-510 package in Ubuntu: Fix Released Status in libnvidia-nscq-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-470-server package in Ubuntu: New Status in nvidia-graphics-drivers-510 package in Ubuntu: New Status in nvidia-graphics-drivers-510-server package in Ubuntu: New Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515-server package in Ubuntu: Fix Released Status in fabric-manager-450 source package in Bionic: Fix Released Status in fabric-manager-470 source package in Bionic: Fix Released Status in fabric-manager-510 source package in Bionic: Fix Released Status in fabric-manager-515 source package in Bionic: Fix Released Status in libnvidia-nscq-450 source package in Bionic: Fix Released Status in libnvidia-nscq-470 source package in Bionic: Fix Released Status in libnvidia-nscq-510 source package in Bionic: Fix Released Status in libnvidia-nscq-515 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-515 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-515-server source package in Bionic: Fix Released Status in fabric-manager-450 source package in Focal: Fix Released Status in fabric-manager-470 source package in Focal: Fix Released Status in fabric-manager-510 source package in Focal: Fix Released Status in fabric-manager-515 source package in Focal: Fix Released Status in libnvidia-nscq-450 source package in Focal: Fix Released Status in libnvidia-nscq-470 source package in Focal: Fix Released Status in libnvidia-nscq-510 source package in Focal: Fix Released Status in libnvidia-nscq-515 source package in Focal: Fix Released Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-510 source package in Focal: Fix Released Status in nvidia-graphics-drivers-510-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in nvidia-graphics-drivers-515-server source package in Focal: Fix Released Status in fabric-manager-450 source package in Jammy: Fix Released Status in fabric-manager-470 source package in Jammy: Fix Released Status in fabric-manager-510 source package in Jammy: Fix Released Status in fabric-manager-515 source package in Jammy: Fix Released Status in libnvidia-nscq-450 source package in Jammy: Fix Released Status in libnvidia-nscq-470 source package in Jammy: Fix Released Status in libnvidia-nscq-510 source package in Jammy: Fix Released Status in libnvidia-nscq-515 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-390 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470-server source package in Jammy: Fix
[Kernel-packages] [Bug 1968391] Re: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS
I found https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970965 looking into a similar issue described here and I'm still having this same "CTRL-EVENT-BEACON-LOSS frequent reconnect" problem with wifi adapter after upgrading to jammy even tho my iwlist scan always shows strong signal (Quality=50/70 Signal level=-60 dBm). I have an ibm thinkpad: clayg@banana:~$ sudo lspci | grep -i wireless 04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 88) According to the other thread I tried going to a *newer* generic kernel and I'm still having problems: root@banana:~# uname -a Linux banana 5.17.11-051711-generic #202205251331 SMP PREEMPT Wed May 25 13:57:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Based on this thread I'll try going down to 5.15.0-23-generic (since I think I *was* running 5.15.0-46-generic originally after upgrade?) -- 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/1968391 Title: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS Status in linux package in Ubuntu: Fix Released Bug description: Using the current beta of Jammy, I no longer have stable WiFi after April 5, 2022 update of wpasupplicant from 2:2.10-2 to 2:2.10-6. There is a chance it may also be related to network-manager going from 1.36.4-1ubuntu1 to 1.36.4-2ubuntu1, but the logs seems to point to wpasupplicant (see below) Wifi is stable often, but also often it fails to load webpages intermittently or fails to download the packages using apt for example, so it's not browser related. Example output of journalctl -xe -u wpasupplicant: Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:23:4c:3c completed [id=0 id_str=] Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=7200 Apr 08 19:26:32 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:33 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:34 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:35 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:36 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:37 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:38 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-DISCONNECTED bssid=fc:34:97:23:4c:3c reason=4 locally_generated=1 Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:42 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: SME: Trying to authenticate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz) Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Trying to associate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz) Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Associated with fc:34:97:23:4c:3c Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CA Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: WPA: Key negotiation completed with fc:34:97:23:4c:3c [PTK=CCMP GTK=CCMP] Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:23:4c:3c completed [id=0 id_str=] Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=-95 txrate=7200 Apr 08 19:29:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=-94 txrate=27 Apr 08 19:49:04 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-73 noise=-95 txrate=27 Apr 08 19:59:04 weasel wpa_supplicant[772]: wlp13s0: WPA: Group rekeying completed with fc:34:97:23:4c:3c [GTK=CCMP] Apr 08 20:00:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=-95 txrate=243000 Additional info: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) The version of the package you
[Kernel-packages] [Bug 1896350] Re: nbd: requests can become stuck when disconnecting from server with qemu-nbd
This bug was fixed in the package linux - 5.4.0-125.141 --- linux (5.4.0-125.141) focal; urgency=medium * focal/linux: 5.4.0-125.141 -proposed tracker (LP: #1983947) * nbd: requests can become stuck when disconnecting from server with qemu-nbd (LP: #1896350) - blk-mq: blk-mq: provide forced completion method - blk-mq: move failure injection out of blk_mq_complete_request - nbd: don't handle response without a corresponding request message - nbd: make sure request completion won't concurrent - nbd: don't clear 'NBD_CMD_INFLIGHT' flag if request is not completed - nbd: fix io hung while disconnecting device * CVE-2021-33656 - vt: drop old FONT ioctls * CVE-2021-33061 - ixgbe: add the ability for the PF to disable VF link state - ixgbe: add improvement for MDD response functionality - ixgbevf: add disable link state -- Stefan Bader Wed, 10 Aug 2022 10:17:28 +0200 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33061 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33656 -- 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/1896350 Title: nbd: requests can become stuck when disconnecting from server with qemu-nbd Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux source package in Focal: Fix Released Status in linux source package in Impish: Won't Fix Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1896350 [Impact] After 2516ab1("nbd: only clear the queue on device teardown"), present in 4.12-rc1 onward, the ioctl NBD_CLEAR_SOCK can no longer clear requests currently being processed. This change was made to fix a race between using the NBD_CLEAR_SOCK ioctl to clear requests, and teardown of the device clearing requests. This worked for the most part, as several years ago systemd was not set up to watch nbd devices for changes in their state. But after: commit f82abfcda58168d9f667e2094d438763531d3fa6 From: Tony Asleson Date: Fri, 8 Feb 2019 15:47:10 -0600 Subject: rules: watch metadata changes on nbd devices Link: https://github.com/systemd/systemd/commit/f82abfcda58168d9f667e2094d438763531d3fa6 in systemd v242-rc1, nbd* devices were added to a udev rule to watch those devices for changes with the inotify subsystem. From man udev: > watch > Watch the device node with inotify; when the node is closed after being > opened for writing, a change uevent is synthesized. > > nowatch > Disable the watching of a device node with inotify. This changed the behaviour of device teardown, since systemd now keeps tabs on the device with inotify, outstanding requests cannot be cleared as nbd_xmit_timeout() will always return 'BLK_EH_RESET_TIMER', and requests get stuck, never to complete, because a disconnect has occurred, and never to timeout, as their timers keep being reset. Symptoms of this issue is that the nbd subsystem gets stuck with messages like: block nbd15: NBD_DISCONNECT block nbd15: Send disconnect failed -32 ... block nbd15: Possible stuck request 7fcf62ba: control (read@523915264,24576B). Runtime 30 seconds ... block nbd15: Possible stuck request 7fcf62ba: control (read@523915264,24576B). Runtime 150 seconds ... INFO: task qemu-nbd:1267 blocked for more than 120 seconds. Not tainted 5.15.0-23-generic #23-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:qemu-nbdstate:D stack:0 pid: 1267 ppid: 1 flags:0x0002 Call Trace: __schedule+0x23d/0x590 ? call_rcu+0xe/0x10 schedule+0x4e/0xb0 blk_mq_freeze_queue_wait+0x69/0xa0 ? wait_woken+0x70/0x70 blk_mq_freeze_queue+0x1b/0x30 nbd_add_socket+0x76/0x1f0 [nbd] __nbd_ioctl+0x18b/0x340 [nbd] ? security_capable+0x3d/0x60 nbd_ioctl+0x81/0xb0 [nbd] blkdev_ioctl+0x12e/0x270 ? __fget_files+0x86/0xc0 block_ioctl+0x46/0x50 __x64_sys_ioctl+0x91/0xc0 do_syscall_64+0x5c/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae Additionally, in syslog you will also see systemd-udevd get stuck: systemd-udevd[419]: nbd15: Worker [2004] processing SEQNUM=5661 is taking a long time $ ps aux ... 4191194 root D 0.1 systemd-udevd - We can workaround the issue by adding a higher priority udev rule to not watch nbd* devices. $ cat << EOF >> /etc/udev/rules.d/97-nbd-device.rules # Disable inotify watching of change events for NBD devices ACTION=="add|change", KERNEL=="nbd*", OPTIONS:="nowatch" EOF $ sudo udevadm control --reload-rules $
[Kernel-packages] [Bug 1963919] Re: fbtft overlay is missing
This bug was fixed in the package linux-raspi - 5.4.0-1069.79 --- linux-raspi (5.4.0-1069.79) focal; urgency=medium * focal/linux-raspi: 5.4.0-1069.79 -proposed tracker (LP: #1983941) * fbtft overlay is missing (LP: #1963919) - overlays: Add fbtft overlay [ Ubuntu: 5.4.0-125.141 ] * focal/linux: 5.4.0-125.141 -proposed tracker (LP: #1983947) * nbd: requests can become stuck when disconnecting from server with qemu-nbd (LP: #1896350) - blk-mq: blk-mq: provide forced completion method - blk-mq: move failure injection out of blk_mq_complete_request - nbd: don't handle response without a corresponding request message - nbd: make sure request completion won't concurrent - nbd: don't clear 'NBD_CMD_INFLIGHT' flag if request is not completed - nbd: fix io hung while disconnecting device * CVE-2021-33656 - vt: drop old FONT ioctls * CVE-2021-33061 - ixgbe: add the ability for the PF to disable VF link state - ixgbe: add improvement for MDD response functionality - ixgbevf: add disable link state -- Juerg Haefliger Thu, 18 Aug 2022 16:56:14 +0200 ** Changed in: linux-raspi (Ubuntu Focal) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33061 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33656 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1963919 Title: fbtft overlay is missing Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Focal: Fix Released Status in linux-raspi2 source package in Focal: Invalid Status in linux-raspi source package in Impish: Won't Fix Status in linux-raspi2 source package in Impish: Invalid Status in linux-raspi source package in Jammy: Fix Released Status in linux-raspi2 source package in Jammy: Invalid Bug description: [Impact] To attach TFT touchscreens the pi-foundation kernel ships the fbtft devicetree overlay along with rpi-display. While you can attach a stand-alone TFT display just fine when only using rpi-display to provide the drivers with hardcoded GPIO assignments, it gets extremely tricky to even enable the touchscreen input or to use such a TFT with other sensors attached since rpi- display does not allow any re-assignment of the GPIO pins in use. The upstream fbtft driver can make use of the already included rpi-display drivers by defining "rpi-display" in its params. It also allows to freely re-assign the GPIO pins for backlight, D/C and Reset to give you enough flexibility to have the display co-exist with any attached sensors and touch input devices that do not have the ability to re-assign GPIO pins and that clash with the hardcoded numbering of rpi-display. An example with freely assigned GPIOs can be seen in the upstream (rpi-foundation) overlay README file at: https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README#L884 Please include fbtft in the ubuntu kernels to allow a more flexible usage of SPI based TFT touchscreens on the Pi. [Test case] See above. [Fix] Backport commit 6a4525924c43 ("overlays: Add fbtft overlay") from rpi-5.15.y. [Where Problems could occur] Problems might show up when using the new DTB overlay on a Pi platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1963919/+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 1987312] Re: IWLMEI may cause device failure at resuming from s2idle
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Status: Invalid => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1987312 Title: IWLMEI may cause device failure at resuming from s2idle Status in HWE Next: New Status in backport-iwlwifi-dkms package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Jammy: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Status in backport-iwlwifi-dkms source package in Kinetic: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987312/+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
I found if the Max TOLUD is set to 1GB or higher in the BIOS (anything other than dynamic) then Ubuntu 22.04 ISO will not get this out of memory error -- 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: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [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 fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we can ask 32bits+ on AllocatePages(). As most X86_64 platforms should support 64 bits addressing, we should extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available memory. * When users grown the initramfs, then probably will get initramfs not found which really annoyed and impact the user experience (system not able to boot). [Test Plan] * detailed instructions how to reproduce the bug: 1. Any method to grow the initramfs, such as install nvidia-driver. 2. If developers would like to reproduce, then could dd if=/dev/random of=... bs=1M count=500, something like: ``` $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500 ``` And then update-initramfs * After applying my patches, the issue is gone. * I did also test my test grubx64.efi in: 1. X86_64 qemu with 1.1. 60M initramfs + 5.15.0-37-generic kernel 1.2. 565M initramfs + 5.17.0-1011-oem kernel 2. Amd64 HP mobile workstation with 2.1. 65M initramfs + 5.15.0-39-generic kernel 2.2. 771M initramfs + 5.17.0-1011-oem kernel All working well. [Where problems could occur] * The changes almost in i386/efi, thus the impact will be in the i386 / x86_64 EFI system. The other change is to modify the “grub-core/kern/efi/mm.c” but I use the original addressing for “arm/arm64/ia64/riscv32/riscv64”. Thus it should not impact them. * There is a “#if defined(__x86_64__)” which intent to limit the > 32bits code in i386 system and also ``` #if defined (__code_model_large__) -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__ +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff #else #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff #endif ``` If everything works as expected, then i386 should working good. If not lucky, based on “UEFI writers’ guide”[2], the i386 will get > 4GB memory region and never be able to access. [Other Info] * Upstream grub2 bug #61058 https://savannah.gnu.org/bugs/index.php?61058 * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320 * Test grubx64.efi: https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320 * Test source code: https://github.com/os369510/grub2/tree/lp1842320 * If you built the package, then test grubx64.efi is under “obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Hi renton, If you want to build it by yourself, then you should clone this: https://people.canonical.com/~jeremysu/lp1842320/ and built it locally and don't clear the build environment, you can found the efi binary on "obj/monolithic/grub-efi-amd64/grubx64.efi". I personally use pbuilder with some hooks when debugging. Alternatively, I upload the binary built by me on https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320v2 and for sure, the efi binary relates to security, then build it by yourself makes sense (but TBH it's not easy as other packages.) If you want to give it a try, then I suggest don't replace the original efi binary. Instead, you can use something like efibootmgr -c -L 'lp1842320' -d ${u-r-boot-dev} -p ${partition} -l '\EFI\ubuntu\grubx64.efi.lp1842320v2' for example: efibootmgr -c -L 'lp1842320' -d /dev/vda -p 2 -l '\EFI\ubuntu\grubx64.efi.lp1842320v2' and use something like 'efibootmgr -n ${your-boot-order-of-lp1842320}' or press F9 on HP machine or press F12 on Lenovo machine Please only do that if you know what you are doing. -- 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: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [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 fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we can ask 32bits+ on AllocatePages(). As most X86_64 platforms should support 64 bits addressing, we should extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available memory. * When users grown the initramfs, then probably will get initramfs not found which really annoyed and impact the user experience (system not able to boot). [Test Plan] * detailed instructions how to reproduce the bug: 1. Any method to grow the initramfs, such as install nvidia-driver. 2. If developers would like to reproduce, then could dd if=/dev/random of=... bs=1M count=500, something like: ``` $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500 ``` And then update-initramfs * After applying my patches, the issue is gone. * I did also test my test grubx64.efi in: 1. X86_64 qemu with 1.1. 60M initramfs + 5.15.0-37-generic kernel 1.2. 565M initramfs + 5.17.0-1011-oem kernel 2. Amd64 HP mobile workstation with 2.1. 65M initramfs + 5.15.0-39-generic kernel 2.2. 771M initramfs + 5.17.0-1011-oem kernel All working well. [Where problems could occur] * The changes almost in i386/efi, thus the impact will be in the i386 / x86_64 EFI system. The other change is to modify the “grub-core/kern/efi/mm.c” but I use the original addressing for “arm/arm64/ia64/riscv32/riscv64”. Thus it should not impact them. * There is a “#if defined(__x86_64__)” which intent to limit the > 32bits code in i386 system and also ``` #if defined (__code_model_large__) -#define
[Kernel-packages] [Bug 1987430] Re: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs
We've seen this on a wide variety of workloads, including general user logins with NFS mounts, SLURM head and cluster nodes, a Prometheus/Grafana server, a Grafana Loki server, two Exim servers, a Samba server, LDAP servers, Matlab license servers, and a monitoring machine that just runs conserver. It seems to be correlated with the amount of processes and activity that happens on a machine, as the two machines that leaked the most are our primary general use login server and our Prometheus server (which is constantly running a churn of monitoring and probe activity). As a result of this, I don't currently have any particular commands that reproduce this. It may be relevant that we are auditing some system calls. The generated /etc/audit/audit.rules on our servers has: -D -b 8192 -f 1 --backlog_wait_time 6 -a exit,always -F arch=b64 -S execve -a exit,always -F arch=b32 -S execve We also have audit log only to files by masking systemd-journald- audit.socket. I will see if I can reproduce this in a VM by generating random activity (I'm going to try repeatedly compiling something over and over), first in our standard configuration and then in a more minimal one. It will likely take at least a day or two to know one way or another. -- 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/1987430 Title: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs Status in linux package in Ubuntu: Confirmed Bug description: Since updating to kernel 5.15.0-46-generic (package version 5.15.0-46.49), all of our Ubuntu 22.04 LTS servers are leaking kernel memory; our first server with 8 GB of RAM just fatally OOMed, causing us to detect this. Inspection of OOM reports, /proc/meminfo, and /proc/slabinfo says that it's mostly going to unreclaimable kmalloc-2k slabs: Aug 23 12:51:11 cluster kernel: [361299.864757] Unreclaimable slab info: Aug 23 12:51:11 cluster kernel: [361299.864757] Name Used Total [...] Aug 23 12:51:11 cluster kernel: [361299.864924] kmalloc-2k 6676584KB6676596KB Most of our machines appear to be leaking slab memory at a rate of around 20 to 40 Mbytes/hour, with some machines leaking much faster; the champions are leaking kernel memory at 145 Mbytes/hour and 237 Mbytes/hour. We aren't running any proprietary kernel modules and our only unusual kernel configuration is that we've disabled AppArmor with 'apparmor=0' on the kernel command line. /proc/version_signature: Ubuntu 5.15.0-46.49-generic 5.15.39 Full kernel command line from the Dell R240 system that fatally OOMd: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=3165564f-a2dd-4b39-935b-114f3e23ff54 ro console=ttyS0,115200 console=tty0 apparmor=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987430/+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 1987387] Re: [UBUNTU 20.04] zgetdump can not handle multivolume dumps
** Package changed: linux (Ubuntu) => s390-tools (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: s390-tools (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-z-systems Importance: Undecided => Medium -- 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/1987387 Title: [UBUNTU 20.04] zgetdump can not handle multivolume dumps Status in Ubuntu on IBM z Systems: New Status in s390-tools package in Ubuntu: New Bug description: == Comment: #0 - Thorsten Diehl - 2022-08-16 12:40:46 == I installed Ubuntu 20.04.4 LTS on IBM z14, enabled two DASDs, created one partition on each DASD and created an mvdump.conf file like this: /dev/dasdc1 /dev/dasdd1 I wrote the boot record by zipl -n -M mvdump.conf and IPLed the system from dasdc devno. The dump completed succesfully. Then I tried to get this dump via zgetdump on the restarted Ubuntu 20.04.4 system (zgetdump -v reports version 2.12.0-build-20220506), I got the following error: root@m8330032:~# zgetdump -i /dev/dasdc zgetdump: Could not open "/sys/bus/ccw/devices/0.0.9405/dasdc/dev" (No such file or directory) root@m8330032:~# zgetdump -i /dev/dasdc1 zgetdump: Could not open "/sys/bus/ccw/devices/0.0.9405/dasdc/dev" (No such file or directory) root@m8330032:~# zgetdump -i /dev/dasdd zgetdump: Could not open "/sys/bus/ccw/devices/0.0.9405/dasdc/dev" (No such file or directory) root@m8330032:~# zgetdump -i /dev/dasdd1 zgetdump: No valid dump found on "/dev/dasdd1" root@m8330032:~# However, If I'm doing the same zgetdump on another system (e.g. with newer s390-tools version), I get the expected result m83lp32:~ # zgetdump -i /dev/dasdc General dump info: Dump format: s390mv_ext Version: 1 Dump created...: Tue, 16 Aug 2022 18:31:57 +0200 Dump ended.: Tue, 16 Aug 2022 18:32:02 +0200 Dump CPU ID: ff1fa1e739068000 UTS node name..: m8330032.lnxne.boe UTS kernel release.: 5.4.0-124-generic UTS kernel version.: #140-Ubuntu SMP Thu Aug 4 02:23:07 UTC 2022 Build arch.: s390x (64 bit) System arch: s390x (64 bit) CPU count (online).: 16 CPU count (real)...: 16 Dump memory range..: 4096 MB Real memory range..: 4096 MB Dump file size.: 849 MB Memory map: - (4096 MB) Dump device info: Volume 0: 0.0.9405 (online/active) Volume 1: 0.0.9406 (online/valid) m83lp32:~ # The error is easily reproducible. Please update zgetdump to a newer version to solve this RAS problem. With Jammy (22.04.1; s390-tools version 2.20.0-build-20220623) this problem does not occur. == Comment: #3 - Jan Hoeppner - 2022-08-22 01:43:45 == There were several issues fixed in s390-tools v2.15.1 in regards to multivolume dumps: https://github.com/ibm-s390-linux/s390-tools/releases/tag/v2.15.1 Especially the following upstream commit for zgetdump: https://github.com/ibm-s390-linux/s390-tools/commit/d55b787d05eb9bd70f93c36cf859b66b2ad02038 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1987387/+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 1985901] Re: kernel hang when connecting monitor
** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium -- 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/1985901 Title: kernel hang when connecting monitor Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: When I connected the ThinkVision 24i monitor on ThinkPad L14, we found below issue. Message from syslogd@u-ThinkPad-L14-Gen-3 at Aug 12 17:12:20 ... kernel:[ 77.803763] watchdog: BUG: soft lockup - CPU#0 stuck for 50s! [Xorg:1829] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 50s! [Xorg:1829] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Modules linked in: rfcomm ccm cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 intel_rapl_msr intel_rapl_common edac_mce_amd kvm_amd kvm snd_ctl_led crct10dif_pclmul ghash_clmulni_intel snd_hda_codec_realtek aesni_intel mt7921e snd_hda_codec_generic btusb btrtl crypto_simd uvcvideo mt76_connac_lib cryptd btbcm mt76 rapl videobuf2_vmalloc btintel videobuf2_memops snd_hda_codec_hdmi bluetooth videobuf2_v4l2 snd_hda_intel mac80211 snd_intel_dspcfg videobuf2_common snd_intel_sdw_acpi snd_hda_codec input_leds videodev snd_seq_midi snd_seq_midi_event snd_hda_core thinkpad_acpi ecdh_generic serio_raw mc ecc snd_pci_acp6x snd_hwdep efi_pstore snd_rawmidi nvram platform_profile snd_pcm snd_seq cfg80211 think_lmi wmi_bmof firmware_attributes_class ledtrig_audio ccp snd_rn_pci_acp3x libarc4 snd_pci_acp3x snd_seq_device snd_timer ucsi_acpi typec_ucsi typec snd soundcore amd_pmc mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp parport ip_tables x_tables 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: 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 amdgpu iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul psmouse drm sdhci_pci nvme cqhci xhci_pci i2c_piix4 r8169 xhci_pci_renesas sdhci nvme_core realtek wmi video 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CPU: 0 PID: 1829 Comm: Xorg Tainted: G L5.14.0-1048-oem #55-Ubuntu 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Hardware name: LENOVO 4810PZ0100/4810PZ0100, BIOS R1YET32W (1.09 ) 05/13/2022 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RIP: 0010:amdgpu_device_rreg.part.0+0x40/0xe0 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Code: 54 41 89 f4 53 48 89 fb 4c 3b af b0 08 00 00 73 1b 83 e2 02 75 09 f6 87 80 64 01 00 10 75 6f 4c 03 ab b8 08 00 00 45 8b 6d 00 12 4c 89 ee 48 8b 87 f8 08 00 00 e8 9f bc db f9 41 89 c5 66 90 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RSP: 0018:bea7c2d6b3e8 EFLAGS: 0282 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RAX: c07b6150 RBX: 9ab39d00 RCX: 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RDX: RSI: 6741 RDI: 9ab39d00 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: RBP: bea7c2d6b408 R08: 9ab39d00 R09: 1140 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R10: R11: 9ab389c9c400 R12: 6741 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: R13: R14: 0008 R15: 9ab389c9d400 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: FS: 7f9d97924a40() GS:9ab466e0() knlGS: 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CS: 0010 DS: ES: CR0: 80050033 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: CR2: 7fec71845110 CR3: 00010c878000 CR4: 00750ef0 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: PKRU: 5554 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: Call Trace: 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: amdgpu_device_rreg+0x17/0x20 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: amdgpu_cgs_read_register+0x14/0x20 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: dm_read_reg_func+0x3e/0xa0 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: amdgpu_dm_dmub_reg_read+0x23/0x30 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: dmub_dcn20_get_inbox1_rptr+0x20/0x30 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel: dmub_srv_wait_for_idle.part.0+0x26/0x60 [amdgpu] 8月 12 17:12:20 u-ThinkPad-L14-Gen-3 kernel:
[Kernel-packages] [Bug 1983498] Re: Jammy: Add OVS Internal Port HW Offload to mlx5 driver
** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1983498 Title: Jammy: Add OVS Internal Port HW Offload to mlx5 driver Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: SRU Justification [Impact] A request has been made, originating from https://bugs.launchpad.net/bugs/1980730, to add support for OVS internal port offload for the mlx5 driver. This feature takes care of certain traffic workloads that are not currently being offloaded to the hardware. [Test Case] Tested by the requester. [Where things could go wrong] These changes could potentially introduce regressions in behavior of the mlx5 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983498/+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 1983498] Re: Jammy: Add OVS Internal Port HW Offload to mlx5 driver
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** 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/1983498 Title: Jammy: Add OVS Internal Port HW Offload to mlx5 driver Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete Bug description: SRU Justification [Impact] A request has been made, originating from https://bugs.launchpad.net/bugs/1980730, to add support for OVS internal port offload for the mlx5 driver. This feature takes care of certain traffic workloads that are not currently being offloaded to the hardware. [Test Case] Tested by the requester. [Where things could go wrong] These changes could potentially introduce regressions in behavior of the mlx5 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983498/+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 1960771] Re: Use EC GPE for s2idle wakeup on AMD platforms
** Changed in: hwe-next Status: New => Fix Released -- 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/1960771 Title: Use EC GPE for s2idle wakeup on AMD platforms Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Opening lid doesn't wakeup some AMD platforms from s2idle. [Fix] Use EC GPE for lid events to wakeup the laptops. [Test] Close and only the lid. The affected laptop now can be woken up by lid. [Where problems could occur] The original issue was later fixed by "pinctrl: amd: Fix wakeups when IRQ is shared with SCI". However, EC GPE is prone to cause spurious wakeup, so we still need to keep an eye on the regression reports. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1960771/+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 1987513] Re: Use upstream LED description on Unmatched
** Changed in: linux-riscv (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Assignee: Emil Renner Berthing (esmil) Status: Fix Committed ** Also affects: linux-riscv (Ubuntu Kinetic) Importance: Undecided Assignee: Emil Renner Berthing (esmil) Status: In Progress ** Changed in: linux (Ubuntu Kinetic) Status: Fix Committed => 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/1987513 Title: Use upstream LED description on Unmatched Status in linux package in Ubuntu: Invalid Status in linux-riscv package in Ubuntu: In Progress Status in linux source package in Kinetic: Invalid Status in linux-riscv source package in Kinetic: In Progress Bug description: [Impact] * The Ubuntu RISC-V kernel carries out-of-tree patches to enable the two LEDs on the SiFive Unmatched board. * There is now an upstream solution to enable the LEDs that appears a little different from userspace. With the out-of-tree patches the three colours in the RGB LED appears as 3 different LEDs, but upstream models them as 1 RGB LED. * Replacing the out-of-tree patches with the upstream solution will make Ubuntu kernels behave like the upstream kernel going forward. [Test Plan] * Boot Ubuntu on the Unmatched board and look at how the LEDs show up in /sys/class/leds * Check that both the green D12 and all three colours of D2 can still be controlled from userspace. [Where problems could occur] * Users may have scripts setting up LEDs that will no longer work when updating to Kinetic with this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987513/+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 1987522] [NEW] Regression: missing Zen 3 data fabric perf events
Public bug reported: With 5.13.0-52-generic, "perf list" includes the following events: data fabric: dram_channel_data_controller_0 [Unit: amd_df] dram_channel_data_controller_1 [Unit: amd_df] dram_channel_data_controller_2 [Unit: amd_df] dram_channel_data_controller_3 [Unit: amd_df] ... With 5.15.0-46-generic the events are missing. This is occurring on Epyc 7003 processors (family 25, model 1, stepping 1). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-tools-5.15.0-46-generic 5.15.0-46.49~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_peermem nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Aug 24 12:08:11 2022 SourcePackage: linux-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987522 Title: Regression: missing Zen 3 data fabric perf events Status in linux-hwe-5.15 package in Ubuntu: New Bug description: With 5.13.0-52-generic, "perf list" includes the following events: data fabric: dram_channel_data_controller_0 [Unit: amd_df] dram_channel_data_controller_1 [Unit: amd_df] dram_channel_data_controller_2 [Unit: amd_df] dram_channel_data_controller_3 [Unit: amd_df] ... With 5.15.0-46-generic the events are missing. This is occurring on Epyc 7003 processors (family 25, model 1, stepping 1). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-tools-5.15.0-46-generic 5.15.0-46.49~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_peermem nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Aug 24 12:08:11 2022 SourcePackage: linux-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1987522/+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 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 AMD64
Some instances, show the same issue with test_021_aslr_dapper_mmap FAIL: test_021_aslr_dapper_mmap (__main__.KernelSecurityTest) ASLR of mmap Traceback (most recent call last): File "./test-kernel-security.py", line 1755, in test_021_aslr_dapper_mmap self._test_aslr('mmap', expected) File "./test-kernel-security.py", line 1727, in _test_aslr self._test_aslr_all(area, expected, "default %s" % area) File "./test-kernel-security.py", line 1720, in _test_aslr_all self._test_aslr_exec(area, expected, target, name) File "./test-kernel-security.py", line 1703, in _test_aslr_exec self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, "--verbose"], msg="%s:\n" % name) File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1203, in assertShellExitEquals self.assertEqual(expected, rc, msg + result + report) AssertionError: default mmap COMPAT: Got exit code 1, expected 0 Command: './aslr32', 'mmap', '--verbose' Output: Checking ASLR of mmap: 0xf7aff010 0xf7aff010 0xf7aff010 ASLR not functional (mmap always at 0xf7aff010) -- 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/1983357 Title: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 AMD64 Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: Incomplete Bug description: Issue found on 5.19.0-9.9 Kinetic AMD64 systems Test log: Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel: '5.19.0-9.9 (Ubuntu 5.19.0-9.9-generic 5.19.0-rc5)' arch: 'amd64' uid: 0/0 SUDO_USER: 'ubuntu') test_021_aslr_dapper_libs (__main__.KernelSecurityTest) ASLR of libs ... (default libs native) (default libs native rekey) (default libs COMPAT) FAIL == FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest) ASLR of libs -- Traceback (most recent call last): File "./test-kernel-security.py", line 1770, in test_021_aslr_dapper_libs self._test_aslr('libs', expected) File "./test-kernel-security.py", line 1727, in _test_aslr self._test_aslr_all(area, expected, "default %s" % area) File "./test-kernel-security.py", line 1720, in _test_aslr_all self._test_aslr_exec(area, expected, target, name) File "./test-kernel-security.py", line 1703, in _test_aslr_exec self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, "--verbose"], msg="%s:\n" % name) File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1203, in assertShellExitEquals self.assertEqual(expected, rc, msg + result + report) AssertionError: default libs COMPAT: Got exit code 1, expected 0 Command: './aslr32', 'libs', '--verbose' Output: Checking ASLR of libs: 0xf7c81790 0xf7c81790 0xf7c81790 FAIL: ASLR not functional (libs always at 0xf7c81790) -- Ran 1 test in 0.144s FAILED (failures=1) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1983357/+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 1987513] 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 1987513 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/1987513 Title: Use upstream LED description on Unmatched Status in linux package in Ubuntu: Incomplete Status in linux-riscv package in Ubuntu: New Bug description: [Impact] * The Ubuntu RISC-V kernel carries out-of-tree patches to enable the two LEDs on the SiFive Unmatched board. * There is now an upstream solution to enable the LEDs that appears a little different from userspace. With the out-of-tree patches the three colours in the RGB LED appears as 3 different LEDs, but upstream models them as 1 RGB LED. * Replacing the out-of-tree patches with the upstream solution will make Ubuntu kernels behave like the upstream kernel going forward. [Test Plan] * Boot Ubuntu on the Unmatched board and look at how the LEDs show up in /sys/class/leds * Check that both the green D12 and all three colours of D2 can still be controlled from userspace. [Where problems could occur] * Users may have scripts setting up LEDs that will no longer work when updating to Kinetic with this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987513/+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 1986833] Re: PolarFire Icicle Kit: L2 Cache wrong interrupts in devicetree
** Changed in: linux-riscv (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1986833 Title: PolarFire Icicle Kit: L2 Cache wrong interrupts in devicetree Status in linux-riscv package in Ubuntu: New Bug description: [Impact] The 5.19 kernel contains support for the PolarFire Icicle board. But booting with linux-image-5.19.0-1002-generic_5.19.0-1002.2_riscv64.deb fails. The cause is that the device-tree incorrectly specifies the PLIC interrupts used for the drivers/soc/sifive/sifive_l2_cache.c. A patch is available as https://lore.kernel.org/all/20220817132521.3159388-1-heinrich.schucha...@canonical.com/ [PATCH 1/1] riscv: dts: microchip: correct L2 cache interrupts This patch only changes the device-tree of the PolarFire Icicle Kit. Please, add the patch to the 5.19 and future kernels. [Test Plan] Use the SiFive Unmatched preinstalled image and install the 5.19 kernel. Try to boot on the Polarfire Icicle board. [Where problems could occur] The fix only concerns a board which has been unsupported by Ubuntu yet. In case of an incorrect fix the board might not boot or otherwise malfunction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1986833/+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 1986970] Re: PolarFire Icicle Kit: missing USB support
** Changed in: linux-riscv (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1986970 Title: PolarFire Icicle Kit: missing USB support Status in linux-riscv package in Ubuntu: New Bug description: [Impact] The 5.19 kernel contains support for the PolarFire Icicle board but the USB driver is missing. The following patches are available in Linux v6.0-rc1 and are sufficient to make USB usable on the PolarFire Icicle board. Please, apply them to the 5.19 kernel and set CONFIG_USB_MUSB_POLARFIRE_SOC=m. 7a96b6ea90a4 ("usb: musb: Add support for PolarFire SoC's musb controller") https://lore.kernel.org/r/20220613114642.1615292-2-conor.doo...@microchip.com 21cdd6a0e844 ("usb: musb: mpfs: Fix error codes in probe()") https://lore.kernel.org/r/YrVmLEc/FOEzNdzj@kili 98ceba755928 ("usb: musb: mpfs: add missing clk_disable_unprepare() in mpfs_remove()" https://lore.kernel.org/all/YrVmLEc%2FFOEzNdzj@kili/ With this change internal USB devices are fully usable. External devices are supported with the following Jumper settings: * J17 closed * J15 open [Test Plan] Ensure the correct jumper settings: * J17 closed * J15 open Use the SiFive Unmatched preinstalled image and install the 5.19 kernel. Try to boot on the Polarfire Icicle board. * Run lsusb. * Attach a USB device to J16 (USB port beside SD-card slot) * Run lsusb again. The new device appears. [Where problems could occur] The fix only concerns a board which has been unsupported by Ubuntu yet. In case of an incorrect fix the board might not boot or otherwise malfunction. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1986970/+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 1987513] Re: Use upstream LED description on Unmatched
** Changed in: linux-riscv (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Emil Renner Berthing (esmil) ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987513 Title: Use upstream LED description on Unmatched Status in linux package in Ubuntu: New Status in linux-riscv package in Ubuntu: New Bug description: [Impact] * The Ubuntu RISC-V kernel carries out-of-tree patches to enable the two LEDs on the SiFive Unmatched board. * There is now an upstream solution to enable the LEDs that appears a little different from userspace. With the out-of-tree patches the three colours in the RGB LED appears as 3 different LEDs, but upstream models them as 1 RGB LED. * Replacing the out-of-tree patches with the upstream solution will make Ubuntu kernels behave like the upstream kernel going forward. [Test Plan] * Boot Ubuntu on the Unmatched board and look at how the LEDs show up in /sys/class/leds * Check that both the green D12 and all three colours of D2 can still be controlled from userspace. [Where problems could occur] * Users may have scripts setting up LEDs that will no longer work when updating to Kinetic with this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987513/+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 1987513] 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 1987513 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/1987513 Title: Use upstream LED description on Unmatched Status in linux package in Ubuntu: Incomplete Status in linux-riscv package in Ubuntu: New Bug description: [Impact] * The Ubuntu RISC-V kernel carries out-of-tree patches to enable the two LEDs on the SiFive Unmatched board. * There is now an upstream solution to enable the LEDs that appears a little different from userspace. With the out-of-tree patches the three colours in the RGB LED appears as 3 different LEDs, but upstream models them as 1 RGB LED. * Replacing the out-of-tree patches with the upstream solution will make Ubuntu kernels behave like the upstream kernel going forward. [Test Plan] * Boot Ubuntu on the Unmatched board and look at how the LEDs show up in /sys/class/leds * Check that both the green D12 and all three colours of D2 can still be controlled from userspace. [Where problems could occur] * Users may have scripts setting up LEDs that will no longer work when updating to Kinetic with this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987513/+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 1987513] [NEW] Use upstream LED description on Unmatched
Public bug reported: [Impact] * The Ubuntu RISC-V kernel carries out-of-tree patches to enable the two LEDs on the SiFive Unmatched board. * There is now an upstream solution to enable the LEDs that appears a little different from userspace. With the out-of-tree patches the three colours in the RGB LED appears as 3 different LEDs, but upstream models them as 1 RGB LED. * Replacing the out-of-tree patches with the upstream solution will make Ubuntu kernels behave like the upstream kernel going forward. [Test Plan] * Boot Ubuntu on the Unmatched board and look at how the LEDs show up in /sys/class/leds * Check that both the green D12 and all three colours of D2 can still be controlled from userspace. [Where problems could occur] * Users may have scripts setting up LEDs that will no longer work when updating to Kinetic with this change. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: [Impact] - * The Ubuntu RISC-V kernel carries out-of-tree patches to enable -the two LEDs on the SiFive Unmatched board. + * The Ubuntu RISC-V kernel carries out-of-tree patches to enable + the two LEDs on the SiFive Unmatched board. - * There are now an upstream solution to enable the LEDs that appears -a little different from userspace. With the out-of-tree patches the -three colours in the RGB LED appears as 3 different LEDs, but upstream -models them as 1 RGB LED. + * There is now an upstream solution to enable the LEDs that appears + a little different from userspace. With the out-of-tree patches the + three colours in the RGB LED appears as 3 different LEDs, but upstream + models them as 1 RGB LED. - * Replacing the out-of-tree patches with the upstream solution will -make Ubuntu kernels behave like the upstream kernel going forward. - + * Replacing the out-of-tree patches with the upstream solution will + make Ubuntu kernels behave like the upstream kernel going forward. + [Test Plan] - * Boot Ubuntu on the Unmatched board and look at how the LEDs show up -in /sys/class/leds + * Boot Ubuntu on the Unmatched board and look at how the LEDs show up + in /sys/class/leds - * Check that both the green D12 and all three colours of D2 can still -be controlled from userspace. + * Check that both the green D12 and all three colours of D2 can still + be controlled from userspace. [Where problems could occur] - * Users may have scripts setting up LEDs that will no longer work when -updating to Kinetic with this change. + * Users may have scripts setting up LEDs that will no longer work when + updating to Kinetic with this change. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1987513 Title: Use upstream LED description on Unmatched Status in linux package in Ubuntu: Incomplete Status in linux-riscv package in Ubuntu: New Bug description: [Impact] * The Ubuntu RISC-V kernel carries out-of-tree patches to enable the two LEDs on the SiFive Unmatched board. * There is now an upstream solution to enable the LEDs that appears a little different from userspace. With the out-of-tree patches the three colours in the RGB LED appears as 3 different LEDs, but upstream models them as 1 RGB LED. * Replacing the out-of-tree patches with the upstream solution will make Ubuntu kernels behave like the upstream kernel going forward. [Test Plan] * Boot Ubuntu on the Unmatched board and look at how the LEDs show up in /sys/class/leds * Check that both the green D12 and all three colours of D2 can still be controlled from userspace. [Where problems could occur] * Users may have scripts setting up LEDs that will no longer work when updating to Kinetic with this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987513/+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 1984004] Re: Linux Firmware drops AMD RX6650 XT Performance
I tested in several steps: 1) Reinstalled 20220329.git681281e4-0ubuntu3.4 from Synaptic, then rebooted. The framerate was low - as expected. 2) Removed all files from /lib/firmware/amdgpu/ and copied over the 12 files from the link you gave, then rebooted. The framerate was still low. 3) Ran "sudo update-initramfs -c -k all", then rebooted. System didn't boot. 4) Hard reset system, started with nomodeset (reinstalled drivers later). The dmesg from the failed boot in step 3) is attached, that's why it's dmesg.0. The ACPI errors seem to be normal, I see that also in successful starts, but the following lines are unusual: [3.056634] kernel: amdgpu :03:00.0: amdgpu: failed to init sos firmware [3.056643] kernel: [drm:psp_sw_init [amdgpu]] *ERROR* Failed to load psp firmware! [3.056751] kernel: [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init of IP block failed -22 [3.056890] kernel: amdgpu :03:00.0: amdgpu: amdgpu_device_ip_init failed [3.056891] kernel: amdgpu :03:00.0: amdgpu: Fatal error during GPU init [3.056892] kernel: amdgpu :03:00.0: amdgpu: amdgpu: finishing device. [3.057112] kernel: amdgpu: probe of :03:00.0 failed with error -22 ** Attachment added: "dmesg from failed boot" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1984004/+attachment/5611300/+files/dmesg.0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1984004 Title: Linux Firmware drops AMD RX6650 XT Performance Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Triaged Bug description: Kernel: 5.15.0-43-generic linux-firmware: 20220329.git681281e4-0ubuntu3.3 Tested with: Mint 21 Cinnamon (Ubuntu 22.04 based) In e.g. the Unigine benchmark, the linux-firmware packages drops the performance of my AMD RX 6650 XT GPU from 98 FPS in 1080p-high down to 23 FPS. That wasn't a problem in Mint 20.3 with kernel 5.15 (Ubuntu 20.04 based). Getting the firmware directly from git brings the performance back to about 100 FPS: git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git cd linux-firmware sudo make install sudo update-initramfs -c -k all Re-installing the linux-firmware package causes the performance to drop again. So there is a problem with the linux firmware at least for the RX 6650 XT, maybe for the whole RX 6000 series. The linux-firmware package in Ubuntu 22.04 should be updated. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: daelach1352 F pulseaudio /dev/snd/controlC0: daelach1352 F pulseaudio /dev/snd/controlC1: daelach1352 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Dependencies: firmware-sof-signed 2.0-1ubuntu3 [origin: Ubuntu] DistroRelease: Linux Mint 21 InstallationDate: Installed on 2020-08-24 (714 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: lono wireless extensions. enp6s0no wireless extensions. MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=UUID=a4b18dd9-4989-4bf5-8107-e55b8f8f6df4 ro amd_iommu=on iommu=pt quiet loglevel=3 splash ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Tags: vanessa third-party-packages Uname: Linux 5.15.0-43-generic x86_64 UnreportableReason: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4901 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4901:bd07/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System
[Kernel-packages] [Bug 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 AMD64
For comment #2, I misread the output, it's actually calling aslr32 instead of aslr, and no it's not working with running the binary directly ubuntu@harpo:~/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/aslr$ sudo ./aslr32 libs --verbose Checking ASLR of libs: 0xf7c81790 0xf7c81790 0xf7c81790 FAIL: ASLR not functional (libs always at 0xf7c81790) -- 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/1983357 Title: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 AMD64 Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: Incomplete Bug description: Issue found on 5.19.0-9.9 Kinetic AMD64 systems Test log: Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel: '5.19.0-9.9 (Ubuntu 5.19.0-9.9-generic 5.19.0-rc5)' arch: 'amd64' uid: 0/0 SUDO_USER: 'ubuntu') test_021_aslr_dapper_libs (__main__.KernelSecurityTest) ASLR of libs ... (default libs native) (default libs native rekey) (default libs COMPAT) FAIL == FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest) ASLR of libs -- Traceback (most recent call last): File "./test-kernel-security.py", line 1770, in test_021_aslr_dapper_libs self._test_aslr('libs', expected) File "./test-kernel-security.py", line 1727, in _test_aslr self._test_aslr_all(area, expected, "default %s" % area) File "./test-kernel-security.py", line 1720, in _test_aslr_all self._test_aslr_exec(area, expected, target, name) File "./test-kernel-security.py", line 1703, in _test_aslr_exec self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, "--verbose"], msg="%s:\n" % name) File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1203, in assertShellExitEquals self.assertEqual(expected, rc, msg + result + report) AssertionError: default libs COMPAT: Got exit code 1, expected 0 Command: './aslr32', 'libs', '--verbose' Output: Checking ASLR of libs: 0xf7c81790 0xf7c81790 0xf7c81790 FAIL: ASLR not functional (libs always at 0xf7c81790) -- Ran 1 test in 0.144s FAILED (failures=1) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1983357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980829] Re: System freeze after resuming from suspend due to PCI ASPM settings
** Description changed: + For Jammy SRU + + [Impact] + While doing some tests such as suspend/resume or CPU stress tests the system would hang. + + [Fix] + The 2 commits fix the issue, but still not get accepted yet. + https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ + https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ + + So, I created a DMI quirk to make the patches only affects on listed + platforms. + + [Test] + Verified on the failed machines and ODM also verified on their side. + + [Where problems could occur] + The patches only affects on the listed platforms, and won't affect other platforms. + + == + [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The 2 patches look pretty safe to me, they try to preserve the ASPM state of devices. ** Description changed: - For Jammy SRU + For Jammy/Kinetic SRU [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ So, I created a DMI quirk to make the patches only affects on listed platforms. [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The patches only affects on the listed platforms, and won't affect other platforms. == [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The 2 patches look pretty safe to me, they try to preserve the ASPM state of devices. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1980829 Title: System freeze after resuming from suspend due to PCI ASPM settings Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: For Jammy/Kinetic SRU [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ So, I created a DMI quirk to make the patches only affects on listed platforms. [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The patches only affects on the listed platforms, and won't affect other platforms. == [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ [Test] Verified on the failed machines
[Kernel-packages] [Bug 1984004] Re: Linux Firmware drops AMD RX6650 XT Performance
Sorry for the late reply. Can you do the following for me? 1) Remove all files in /lib/firmware/amdgpu/. 2) Copy files dimgrey_cavefish_* from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu to /lib/firmware/amdgpu. 3) Reboot and check the GPU performance. 4) Attach the output of dmesg to this bug. It's unclear to me if amdgpu driver needs anything besides the dimgrey_cavefish firmware blobs but hopefully the dmesg output will tell us. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1984004 Title: Linux Firmware drops AMD RX6650 XT Performance Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Triaged Bug description: Kernel: 5.15.0-43-generic linux-firmware: 20220329.git681281e4-0ubuntu3.3 Tested with: Mint 21 Cinnamon (Ubuntu 22.04 based) In e.g. the Unigine benchmark, the linux-firmware packages drops the performance of my AMD RX 6650 XT GPU from 98 FPS in 1080p-high down to 23 FPS. That wasn't a problem in Mint 20.3 with kernel 5.15 (Ubuntu 20.04 based). Getting the firmware directly from git brings the performance back to about 100 FPS: git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git cd linux-firmware sudo make install sudo update-initramfs -c -k all Re-installing the linux-firmware package causes the performance to drop again. So there is a problem with the linux firmware at least for the RX 6650 XT, maybe for the whole RX 6000 series. The linux-firmware package in Ubuntu 22.04 should be updated. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: daelach1352 F pulseaudio /dev/snd/controlC0: daelach1352 F pulseaudio /dev/snd/controlC1: daelach1352 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Dependencies: firmware-sof-signed 2.0-1ubuntu3 [origin: Ubuntu] DistroRelease: Linux Mint 21 InstallationDate: Installed on 2020-08-24 (714 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: lono wireless extensions. enp6s0no wireless extensions. MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=UUID=a4b18dd9-4989-4bf5-8107-e55b8f8f6df4 ro amd_iommu=on iommu=pt quiet loglevel=3 splash ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Tags: vanessa third-party-packages Uname: Linux 5.15.0-43-generic x86_64 UnreportableReason: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4901 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4901:bd07/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1984004/+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 1987507] [NEW] Transition oem-20.04 to hwe-5.15
Public bug reported: Migrate oem-5.14 to hwe-5.15 now that there should be no functional regressions left anymore. ** Affects: linux-meta-hwe-5.15 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-restricted-modules-hwe-5.15 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-meta-hwe-5.15 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-restricted-modules-hwe-5.15 (Ubuntu Focal) Importance: Undecided Status: New ** Package changed: linux-oem-5.14 (Ubuntu) => linux-meta-hwe-5.15 (Ubuntu) ** Also affects: linux-meta-hwe-5.15 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-restricted-modules-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-meta-hwe-5.15 (Ubuntu) Status: New => Invalid ** Changed in: linux-restricted-modules-hwe-5.15 (Ubuntu) Status: New => Invalid -- 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/1987507 Title: Transition oem-20.04 to hwe-5.15 Status in linux-meta-hwe-5.15 package in Ubuntu: Invalid Status in linux-restricted-modules-hwe-5.15 package in Ubuntu: Invalid Status in linux-meta-hwe-5.15 source package in Focal: New Status in linux-restricted-modules-hwe-5.15 source package in Focal: New Bug description: Migrate oem-5.14 to hwe-5.15 now that there should be no functional regressions left anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.15/+bug/1987507/+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 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 AMD64
This test is trying to call a compiled binary "aslr32" and execute: ./aslr32 libs --verbose If you try to call it from the script, it will fail, however if you run the binary directly it will be good: ubuntu@harpo:~/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts$ sudo python2 ./test-kernel-security.py -v KernelSecurityTest.test_021_aslr_dapper_libs Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel: '5.19.0-15.15 (Ubuntu 5.19.0-15.15-generic 5.19.0)' arch: 'amd64' uid: 0/0 SUDO_USER: 'ubuntu') test_021_aslr_dapper_libs (__main__.KernelSecurityTest) ASLR of libs ... (default libs native) (default libs native rekey) (default libs COMPAT) FAIL == FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest) ASLR of libs -- Traceback (most recent call last): File "./test-kernel-security.py", line 1782, in test_021_aslr_dapper_libs self._test_aslr('libs', expected) File "./test-kernel-security.py", line 1739, in _test_aslr self._test_aslr_all(area, expected, "default %s" % area) File "./test-kernel-security.py", line 1732, in _test_aslr_all self._test_aslr_exec(area, expected, target, name) File "./test-kernel-security.py", line 1715, in _test_aslr_exec self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, "--verbose"], msg="%s:\n" % name) File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1203, in assertShellExitEquals self.assertEqual(expected, rc, msg + result + report) AssertionError: default libs COMPAT: Got exit code 1, expected 0 Command: './aslr32', 'libs', '--verbose' Output: Checking ASLR of libs: 0xf7c81790 0xf7c81790 0xf7c81790 FAIL: ASLR not functional (libs always at 0xf7c81790) -- Ran 1 test in 0.589s FAILED (failures=1) ubuntu@harpo:~/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts$ sudo ./kernel-security/aslr/aslr libs --verbose Checking ASLR of libs: 0x007fb495c907c0 0x007f674ea907c0 0x007f0e0fe907c0 ok: ASLR of libs functional -- 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/1983357 Title: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 AMD64 Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: Incomplete Bug description: Issue found on 5.19.0-9.9 Kinetic AMD64 systems Test log: Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel: '5.19.0-9.9 (Ubuntu 5.19.0-9.9-generic 5.19.0-rc5)' arch: 'amd64' uid: 0/0 SUDO_USER: 'ubuntu') test_021_aslr_dapper_libs (__main__.KernelSecurityTest) ASLR of libs ... (default libs native) (default libs native rekey) (default libs COMPAT) FAIL == FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest) ASLR of libs -- Traceback (most recent call last): File "./test-kernel-security.py", line 1770, in test_021_aslr_dapper_libs self._test_aslr('libs', expected) File "./test-kernel-security.py", line 1727, in _test_aslr self._test_aslr_all(area, expected, "default %s" % area) File "./test-kernel-security.py", line 1720, in _test_aslr_all self._test_aslr_exec(area, expected, target, name) File "./test-kernel-security.py", line 1703, in _test_aslr_exec self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, "--verbose"], msg="%s:\n" % name) File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1203, in assertShellExitEquals self.assertEqual(expected, rc, msg + result + report) AssertionError: default libs COMPAT: Got exit code 1, expected 0 Command: './aslr32', 'libs', '--verbose' Output: Checking ASLR of libs: 0xf7c81790 0xf7c81790 0xf7c81790 FAIL: ASLR not functional (libs always at 0xf7c81790) -- Ran 1 test in 0.144s FAILED (failures=1) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1983357/+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 1987413] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1987413/+attachment/5611268/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987413 Title: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871 https://gitlab.freedesktop.org/drm/amd/-/issues/1887 If you read the bugs, you find that people report kernel version 5.17 or more recent to fix them, which I can confirm: I started to run the Ubuntu OEM kernel ( 5.17.0-1015-oem ), and thus far got a 100% stable system. So, I guess these problems will be solved with the next HWE kernel, that is expected to be added to the Ubuntu 22.04 archive in October. However, for current Ubuntu 22.04 or 20.04 HWE users, there is no supported solution to get a stable system with various amdgpu adapters. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dennis 2163 F pulseaudio /dev/snd/controlC2: dennis 2163 F pulseaudio /dev/snd/controlC1: dennis 2163 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-05-01 (844 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B87 Package: linux-hwe-5.15 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=6eaf2615-5b03-4ec9-a9df-bee7f682670a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: wayland-session jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-19 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M GAMING PLUS (MS-7B87) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B87:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MGAMINGPLUS(MS-7B87):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B87 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987413/+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 1987413] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1987413/+attachment/5611267/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987413 Title: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871 https://gitlab.freedesktop.org/drm/amd/-/issues/1887 If you read the bugs, you find that people report kernel version 5.17 or more recent to fix them, which I can confirm: I started to run the Ubuntu OEM kernel ( 5.17.0-1015-oem ), and thus far got a 100% stable system. So, I guess these problems will be solved with the next HWE kernel, that is expected to be added to the Ubuntu 22.04 archive in October. However, for current Ubuntu 22.04 or 20.04 HWE users, there is no supported solution to get a stable system with various amdgpu adapters. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dennis 2163 F pulseaudio /dev/snd/controlC2: dennis 2163 F pulseaudio /dev/snd/controlC1: dennis 2163 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-05-01 (844 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B87 Package: linux-hwe-5.15 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=6eaf2615-5b03-4ec9-a9df-bee7f682670a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: wayland-session jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-19 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M GAMING PLUS (MS-7B87) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B87:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MGAMINGPLUS(MS-7B87):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B87 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987413/+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 1987413] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1987413/+attachment/5611266/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987413 Title: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871 https://gitlab.freedesktop.org/drm/amd/-/issues/1887 If you read the bugs, you find that people report kernel version 5.17 or more recent to fix them, which I can confirm: I started to run the Ubuntu OEM kernel ( 5.17.0-1015-oem ), and thus far got a 100% stable system. So, I guess these problems will be solved with the next HWE kernel, that is expected to be added to the Ubuntu 22.04 archive in October. However, for current Ubuntu 22.04 or 20.04 HWE users, there is no supported solution to get a stable system with various amdgpu adapters. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dennis 2163 F pulseaudio /dev/snd/controlC2: dennis 2163 F pulseaudio /dev/snd/controlC1: dennis 2163 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-05-01 (844 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B87 Package: linux-hwe-5.15 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=6eaf2615-5b03-4ec9-a9df-bee7f682670a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: wayland-session jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-19 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M GAMING PLUS (MS-7B87) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B87:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MGAMINGPLUS(MS-7B87):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B87 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987413/+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
I am getting this error and cannot even boot Ubuntu 22.04.1 from a live USB. I am using an HP Elite Dragonfly G2 with 16GB of RAM. I get an error: out of memory message then a kernel panic. Please fix this, I would very much like to try running Ubuntu but I have to run Fedora 36 instead due to the fact that I can't even boot Ubuntu because of this bug. -- 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: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [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 fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we can ask 32bits+ on AllocatePages(). As most X86_64 platforms should support 64 bits addressing, we should extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available memory. * When users grown the initramfs, then probably will get initramfs not found which really annoyed and impact the user experience (system not able to boot). [Test Plan] * detailed instructions how to reproduce the bug: 1. Any method to grow the initramfs, such as install nvidia-driver. 2. If developers would like to reproduce, then could dd if=/dev/random of=... bs=1M count=500, something like: ``` $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500 ``` And then update-initramfs * After applying my patches, the issue is gone. * I did also test my test grubx64.efi in: 1. X86_64 qemu with 1.1. 60M initramfs + 5.15.0-37-generic kernel 1.2. 565M initramfs + 5.17.0-1011-oem kernel 2. Amd64 HP mobile workstation with 2.1. 65M initramfs + 5.15.0-39-generic kernel 2.2. 771M initramfs + 5.17.0-1011-oem kernel All working well. [Where problems could occur] * The changes almost in i386/efi, thus the impact will be in the i386 / x86_64 EFI system. The other change is to modify the “grub-core/kern/efi/mm.c” but I use the original addressing for “arm/arm64/ia64/riscv32/riscv64”. Thus it should not impact them. * There is a “#if defined(__x86_64__)” which intent to limit the > 32bits code in i386 system and also ``` #if defined (__code_model_large__) -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__ +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff #else #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff #endif ``` If everything works as expected, then i386 should working good. If not lucky, based on “UEFI writers’ guide”[2], the i386 will get > 4GB memory region and never be able to access. [Other Info] * Upstream grub2 bug #61058 https://savannah.gnu.org/bugs/index.php?61058 * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320 * Test grubx64.efi: https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320 *
[Kernel-packages] [Bug 1987413] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1987413/+attachment/5611265/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987413 Title: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871 https://gitlab.freedesktop.org/drm/amd/-/issues/1887 If you read the bugs, you find that people report kernel version 5.17 or more recent to fix them, which I can confirm: I started to run the Ubuntu OEM kernel ( 5.17.0-1015-oem ), and thus far got a 100% stable system. So, I guess these problems will be solved with the next HWE kernel, that is expected to be added to the Ubuntu 22.04 archive in October. However, for current Ubuntu 22.04 or 20.04 HWE users, there is no supported solution to get a stable system with various amdgpu adapters. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dennis 2163 F pulseaudio /dev/snd/controlC2: dennis 2163 F pulseaudio /dev/snd/controlC1: dennis 2163 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-05-01 (844 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B87 Package: linux-hwe-5.15 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=6eaf2615-5b03-4ec9-a9df-bee7f682670a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: wayland-session jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-19 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M GAMING PLUS (MS-7B87) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B87:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MGAMINGPLUS(MS-7B87):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B87 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987413/+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 1987413] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1987413/+attachment/5611269/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987413 Title: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871 https://gitlab.freedesktop.org/drm/amd/-/issues/1887 If you read the bugs, you find that people report kernel version 5.17 or more recent to fix them, which I can confirm: I started to run the Ubuntu OEM kernel ( 5.17.0-1015-oem ), and thus far got a 100% stable system. So, I guess these problems will be solved with the next HWE kernel, that is expected to be added to the Ubuntu 22.04 archive in October. However, for current Ubuntu 22.04 or 20.04 HWE users, there is no supported solution to get a stable system with various amdgpu adapters. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dennis 2163 F pulseaudio /dev/snd/controlC2: dennis 2163 F pulseaudio /dev/snd/controlC1: dennis 2163 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-05-01 (844 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B87 Package: linux-hwe-5.15 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=6eaf2615-5b03-4ec9-a9df-bee7f682670a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: wayland-session jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-19 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M GAMING PLUS (MS-7B87) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B87:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MGAMINGPLUS(MS-7B87):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B87 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987413/+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 1987413] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1987413/+attachment/5611258/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987413 Title: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871 https://gitlab.freedesktop.org/drm/amd/-/issues/1887 If you read the bugs, you find that people report kernel version 5.17 or more recent to fix them, which I can confirm: I started to run the Ubuntu OEM kernel ( 5.17.0-1015-oem ), and thus far got a 100% stable system. So, I guess these problems will be solved with the next HWE kernel, that is expected to be added to the Ubuntu 22.04 archive in October. However, for current Ubuntu 22.04 or 20.04 HWE users, there is no supported solution to get a stable system with various amdgpu adapters. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dennis 2163 F pulseaudio /dev/snd/controlC2: dennis 2163 F pulseaudio /dev/snd/controlC1: dennis 2163 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-05-01 (844 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B87 Package: linux-hwe-5.15 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=6eaf2615-5b03-4ec9-a9df-bee7f682670a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: wayland-session jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-19 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M GAMING PLUS (MS-7B87) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B87:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MGAMINGPLUS(MS-7B87):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B87 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987413/+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 1987413] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1987413/+attachment/5611257/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987413 Title: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871 https://gitlab.freedesktop.org/drm/amd/-/issues/1887 If you read the bugs, you find that people report kernel version 5.17 or more recent to fix them, which I can confirm: I started to run the Ubuntu OEM kernel ( 5.17.0-1015-oem ), and thus far got a 100% stable system. So, I guess these problems will be solved with the next HWE kernel, that is expected to be added to the Ubuntu 22.04 archive in October. However, for current Ubuntu 22.04 or 20.04 HWE users, there is no supported solution to get a stable system with various amdgpu adapters. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dennis 2163 F pulseaudio /dev/snd/controlC2: dennis 2163 F pulseaudio /dev/snd/controlC1: dennis 2163 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-05-01 (844 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B87 Package: linux-hwe-5.15 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=6eaf2615-5b03-4ec9-a9df-bee7f682670a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: wayland-session jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-19 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M GAMING PLUS (MS-7B87) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B87:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MGAMINGPLUS(MS-7B87):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B87 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987413/+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 1987413] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1987413/+attachment/5611260/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987413 Title: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871 https://gitlab.freedesktop.org/drm/amd/-/issues/1887 If you read the bugs, you find that people report kernel version 5.17 or more recent to fix them, which I can confirm: I started to run the Ubuntu OEM kernel ( 5.17.0-1015-oem ), and thus far got a 100% stable system. So, I guess these problems will be solved with the next HWE kernel, that is expected to be added to the Ubuntu 22.04 archive in October. However, for current Ubuntu 22.04 or 20.04 HWE users, there is no supported solution to get a stable system with various amdgpu adapters. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dennis 2163 F pulseaudio /dev/snd/controlC2: dennis 2163 F pulseaudio /dev/snd/controlC1: dennis 2163 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-05-01 (844 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B87 Package: linux-hwe-5.15 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=6eaf2615-5b03-4ec9-a9df-bee7f682670a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: wayland-session jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-19 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M GAMING PLUS (MS-7B87) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B87:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MGAMINGPLUS(MS-7B87):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B87 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987413/+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 1987413] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1987413/+attachment/5611264/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987413 Title: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871 https://gitlab.freedesktop.org/drm/amd/-/issues/1887 If you read the bugs, you find that people report kernel version 5.17 or more recent to fix them, which I can confirm: I started to run the Ubuntu OEM kernel ( 5.17.0-1015-oem ), and thus far got a 100% stable system. So, I guess these problems will be solved with the next HWE kernel, that is expected to be added to the Ubuntu 22.04 archive in October. However, for current Ubuntu 22.04 or 20.04 HWE users, there is no supported solution to get a stable system with various amdgpu adapters. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dennis 2163 F pulseaudio /dev/snd/controlC2: dennis 2163 F pulseaudio /dev/snd/controlC1: dennis 2163 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-05-01 (844 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B87 Package: linux-hwe-5.15 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=6eaf2615-5b03-4ec9-a9df-bee7f682670a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: wayland-session jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-19 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M GAMING PLUS (MS-7B87) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B87:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MGAMINGPLUS(MS-7B87):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B87 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987413/+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 1987413] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1987413/+attachment/5611263/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987413 Title: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871 https://gitlab.freedesktop.org/drm/amd/-/issues/1887 If you read the bugs, you find that people report kernel version 5.17 or more recent to fix them, which I can confirm: I started to run the Ubuntu OEM kernel ( 5.17.0-1015-oem ), and thus far got a 100% stable system. So, I guess these problems will be solved with the next HWE kernel, that is expected to be added to the Ubuntu 22.04 archive in October. However, for current Ubuntu 22.04 or 20.04 HWE users, there is no supported solution to get a stable system with various amdgpu adapters. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dennis 2163 F pulseaudio /dev/snd/controlC2: dennis 2163 F pulseaudio /dev/snd/controlC1: dennis 2163 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-05-01 (844 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B87 Package: linux-hwe-5.15 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=6eaf2615-5b03-4ec9-a9df-bee7f682670a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: wayland-session jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-19 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M GAMING PLUS (MS-7B87) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B87:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MGAMINGPLUS(MS-7B87):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B87 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987413/+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 1987413] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1987413/+attachment/5611262/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987413 Title: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871 https://gitlab.freedesktop.org/drm/amd/-/issues/1887 If you read the bugs, you find that people report kernel version 5.17 or more recent to fix them, which I can confirm: I started to run the Ubuntu OEM kernel ( 5.17.0-1015-oem ), and thus far got a 100% stable system. So, I guess these problems will be solved with the next HWE kernel, that is expected to be added to the Ubuntu 22.04 archive in October. However, for current Ubuntu 22.04 or 20.04 HWE users, there is no supported solution to get a stable system with various amdgpu adapters. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dennis 2163 F pulseaudio /dev/snd/controlC2: dennis 2163 F pulseaudio /dev/snd/controlC1: dennis 2163 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-05-01 (844 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B87 Package: linux-hwe-5.15 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=6eaf2615-5b03-4ec9-a9df-bee7f682670a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: wayland-session jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-19 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M GAMING PLUS (MS-7B87) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B87:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MGAMINGPLUS(MS-7B87):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B87 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987413/+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 1987413] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1987413/+attachment/5611259/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987413 Title: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871 https://gitlab.freedesktop.org/drm/amd/-/issues/1887 If you read the bugs, you find that people report kernel version 5.17 or more recent to fix them, which I can confirm: I started to run the Ubuntu OEM kernel ( 5.17.0-1015-oem ), and thus far got a 100% stable system. So, I guess these problems will be solved with the next HWE kernel, that is expected to be added to the Ubuntu 22.04 archive in October. However, for current Ubuntu 22.04 or 20.04 HWE users, there is no supported solution to get a stable system with various amdgpu adapters. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dennis 2163 F pulseaudio /dev/snd/controlC2: dennis 2163 F pulseaudio /dev/snd/controlC1: dennis 2163 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-05-01 (844 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B87 Package: linux-hwe-5.15 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=6eaf2615-5b03-4ec9-a9df-bee7f682670a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: wayland-session jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-19 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M GAMING PLUS (MS-7B87) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B87:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MGAMINGPLUS(MS-7B87):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B87 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987413/+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 1987413] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1987413/+attachment/5611261/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987413 Title: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871 https://gitlab.freedesktop.org/drm/amd/-/issues/1887 If you read the bugs, you find that people report kernel version 5.17 or more recent to fix them, which I can confirm: I started to run the Ubuntu OEM kernel ( 5.17.0-1015-oem ), and thus far got a 100% stable system. So, I guess these problems will be solved with the next HWE kernel, that is expected to be added to the Ubuntu 22.04 archive in October. However, for current Ubuntu 22.04 or 20.04 HWE users, there is no supported solution to get a stable system with various amdgpu adapters. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dennis 2163 F pulseaudio /dev/snd/controlC2: dennis 2163 F pulseaudio /dev/snd/controlC1: dennis 2163 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-05-01 (844 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B87 Package: linux-hwe-5.15 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=6eaf2615-5b03-4ec9-a9df-bee7f682670a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: wayland-session jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-19 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M GAMING PLUS (MS-7B87) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B87:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MGAMINGPLUS(MS-7B87):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B87 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987413/+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 1987413] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1987413/+attachment/5611256/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987413 Title: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871 https://gitlab.freedesktop.org/drm/amd/-/issues/1887 If you read the bugs, you find that people report kernel version 5.17 or more recent to fix them, which I can confirm: I started to run the Ubuntu OEM kernel ( 5.17.0-1015-oem ), and thus far got a 100% stable system. So, I guess these problems will be solved with the next HWE kernel, that is expected to be added to the Ubuntu 22.04 archive in October. However, for current Ubuntu 22.04 or 20.04 HWE users, there is no supported solution to get a stable system with various amdgpu adapters. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dennis 2163 F pulseaudio /dev/snd/controlC2: dennis 2163 F pulseaudio /dev/snd/controlC1: dennis 2163 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-05-01 (844 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B87 Package: linux-hwe-5.15 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=6eaf2615-5b03-4ec9-a9df-bee7f682670a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: wayland-session jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-19 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M GAMING PLUS (MS-7B87) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B87:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MGAMINGPLUS(MS-7B87):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B87 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987413/+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 1987413] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1987413/+attachment/5611255/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987413 Title: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871 https://gitlab.freedesktop.org/drm/amd/-/issues/1887 If you read the bugs, you find that people report kernel version 5.17 or more recent to fix them, which I can confirm: I started to run the Ubuntu OEM kernel ( 5.17.0-1015-oem ), and thus far got a 100% stable system. So, I guess these problems will be solved with the next HWE kernel, that is expected to be added to the Ubuntu 22.04 archive in October. However, for current Ubuntu 22.04 or 20.04 HWE users, there is no supported solution to get a stable system with various amdgpu adapters. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dennis 2163 F pulseaudio /dev/snd/controlC2: dennis 2163 F pulseaudio /dev/snd/controlC1: dennis 2163 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-05-01 (844 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B87 Package: linux-hwe-5.15 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=6eaf2615-5b03-4ec9-a9df-bee7f682670a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: wayland-session jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-19 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M GAMING PLUS (MS-7B87) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B87:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MGAMINGPLUS(MS-7B87):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B87 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987413/+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 1987413] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1987413/+attachment/5611254/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987413 Title: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871 https://gitlab.freedesktop.org/drm/amd/-/issues/1887 If you read the bugs, you find that people report kernel version 5.17 or more recent to fix them, which I can confirm: I started to run the Ubuntu OEM kernel ( 5.17.0-1015-oem ), and thus far got a 100% stable system. So, I guess these problems will be solved with the next HWE kernel, that is expected to be added to the Ubuntu 22.04 archive in October. However, for current Ubuntu 22.04 or 20.04 HWE users, there is no supported solution to get a stable system with various amdgpu adapters. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dennis 2163 F pulseaudio /dev/snd/controlC2: dennis 2163 F pulseaudio /dev/snd/controlC1: dennis 2163 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-05-01 (844 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B87 Package: linux-hwe-5.15 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=6eaf2615-5b03-4ec9-a9df-bee7f682670a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: wayland-session jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-19 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M GAMING PLUS (MS-7B87) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B87:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MGAMINGPLUS(MS-7B87):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B87 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987413/+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 1987413] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1987413/+attachment/5611253/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987413 Title: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871 https://gitlab.freedesktop.org/drm/amd/-/issues/1887 If you read the bugs, you find that people report kernel version 5.17 or more recent to fix them, which I can confirm: I started to run the Ubuntu OEM kernel ( 5.17.0-1015-oem ), and thus far got a 100% stable system. So, I guess these problems will be solved with the next HWE kernel, that is expected to be added to the Ubuntu 22.04 archive in October. However, for current Ubuntu 22.04 or 20.04 HWE users, there is no supported solution to get a stable system with various amdgpu adapters. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dennis 2163 F pulseaudio /dev/snd/controlC2: dennis 2163 F pulseaudio /dev/snd/controlC1: dennis 2163 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-05-01 (844 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B87 Package: linux-hwe-5.15 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=6eaf2615-5b03-4ec9-a9df-bee7f682670a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: wayland-session jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-19 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M GAMING PLUS (MS-7B87) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B87:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MGAMINGPLUS(MS-7B87):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B87 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987413/+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 1987413] Re: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT
apport information ** Tags added: apport-collected jammy wayland-session ** Description changed: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871 https://gitlab.freedesktop.org/drm/amd/-/issues/1887 If you read the bugs, you find that people report kernel version 5.17 or more recent to fix them, which I can confirm: I started to run the Ubuntu OEM kernel ( 5.17.0-1015-oem ), and thus far got a 100% stable system. - So, I guess these problems will be solved with the next HWE kernel, that - is expected to be added to the Ubuntu 22.04 archive in October. However, - for current Ubuntu 22.04 or 20.04 HWE users, there is no supported - solution to get a stable system with various amdgpu adapters. + So, I guess these problems will be solved with the next HWE kernel, that is expected to be added to the Ubuntu 22.04 archive in October. However, for current Ubuntu 22.04 or 20.04 HWE users, there is no supported solution to get a stable system with various amdgpu adapters. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC3: dennis 2163 F pulseaudio + /dev/snd/controlC2: dennis 2163 F pulseaudio + /dev/snd/controlC1: dennis 2163 F pulseaudio + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2020-05-01 (844 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + IwConfig: + lono wireless extensions. + + enp37s0 no wireless extensions. + MachineType: Micro-Star International Co., Ltd. MS-7B87 + Package: linux-hwe-5.15 + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=6eaf2615-5b03-4ec9-a9df-bee7f682670a ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-47-generic N/A + linux-backports-modules-5.15.0-47-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.4 + RfKill: + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no + Tags: wayland-session jammy + Uname: Linux 5.15.0-47-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-08-19 (4 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark + _MarkForUpload: True + dmi.bios.date: 06/11/2020 + dmi.bios.release: 5.14 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1.C0 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: B450M GAMING PLUS (MS-7B87) + dmi.board.vendor: Micro-Star International Co., Ltd. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: To be filled by O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: Micro-Star International Co., Ltd. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B87:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MGAMINGPLUS(MS-7B87):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: MS-7B87 + dmi.product.sku: To be filled by O.E.M. + dmi.product.version: 1.0 + dmi.sys.vendor: Micro-Star International Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1987413/+attachment/5611252/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987413 Title: [amdgpu] Several stability bugs in pre-5.17 kernels, e.g. on AMD RX 6600 XT Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Since updating to kernel 5.15 in Ubuntu LTS 20.04, I got several stability issues with my AMD RX 6600 XT graphics adapter. I upgraded to LTS 22.04 with the hope to be able to get more recent kernels, but there are no HWE kernels and the GA kernel is still 5.15, while I would expect it to be at least on kernel.org's recent stable kernel, 5.19.3 as of now. These are the bugs that seem to affect me and other users of more recent AMD GPUs: https://gitlab.freedesktop.org/drm/amd/-/issues/1819 https://gitlab.freedesktop.org/drm/amd/-/issues/1871
[Kernel-packages] [Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
Still present on 5.15.0-46-generic (Ubuntu 20.04.3) [ 30.346347] UBSAN: array-index-out-of-bounds in /build/linux-hwe-5.15-69LdM0/linux-hwe-5.15-5.15.0/drivers/net/ethernet/aquantia/atlantic/aq_nic.c:1262:48 [ 30.346349] index 8 is out of range for type 'aq_vec_s *[8]' -- 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/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: The undefined behaviour sanitiser picks up an array-index-out-of- bounds in the aquantia atlantic driver. The NIC is (I think) built into my gigabyte motherboard (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME- rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to 22.04 (or at least dmesg didn't previously complain). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 13:02:10 2022 InstallationDate: Installed on 2019-08-07 (899 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS XTREME-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS XTREME dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973839] Re: 5.15.0-30-generic : SSBD mitigation results in "unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0000000000000004)" and flood of kernel traces in some cl
Same here after Updating from 20.04 to 22.04 today: [0.00] Linux version 5.15.0-46-generic (buildd@lcy02-amd64-115) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 (Ubuntu 5.15.0-46.49-generic 5.15.39) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=8eb2528b-9477-4dcd-b796-e38b25a16b14 ro console=tty1 console=ttyS0 ... [5.239998] unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0004) at rIP: 0xbbe960f4 (native_write_msr+0x4/0x30) [5.242224] Call Trace: [5.242228] [5.242229] ? write_spec_ctrl_current+0x45/0x50 [5.242240] speculation_ctrl_update+0x8f/0x200 [5.245439] speculation_ctrl_update_current+0x1f/0x30 [5.246406] ssb_prctl_set+0x9a/0xf0 [5.247183] arch_seccomp_spec_mitigate+0x66/0x70 [5.248195] seccomp_set_mode_filter+0x4e2/0x530 [5.249094] do_seccomp+0x37/0x200 [5.249829] __x64_sys_seccomp+0x18/0x20 [5.250614] do_syscall_64+0x5c/0xc0 [5.251371] ? exit_to_user_mode_prepare+0x37/0xb0 [5.252268] ? irqentry_exit_to_user_mode+0x9/0x20 [5.253181] ? irqentry_exit+0x1d/0x30 [5.253932] ? exc_page_fault+0x89/0x170 [5.254714] entry_SYSCALL_64_after_hwframe+0x61/0xcb [5.255633] RIP: 0033:0x7fd9bf82ca3d [5.256398] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 [5.259150] RSP: 002b:7fff2d4c0f88 EFLAGS: 0246 ORIG_RAX: 013d [5.260339] RAX: ffda RBX: 5604b1701620 RCX: 7fd9bf82ca3d [5.261476] RDX: 5604b16fc390 RSI: RDI: 0001 [5.262605] RBP: R08: 0001 R09: 5604b16fc390 [5.263780] R10: 0001 R11: 0246 R12: [5.264940] R13: 0001 R14: 5604b16fc390 R15: 0001 [5.266076] Starting [0;1;39mJournal Service[0m... [5.267097] Call Trace: [5.267721] [5.268288] ? write_spec_ctrl_current+0x45/0x50 [5.269123] __switch_to_xtra+0x110/0x4e0 [5.269919] __switch_to+0x260/0x450 [5.270658] __schedule+0x23d/0x590 [5.271400] ? __do_softirq+0x27f/0x2e7 [5.272180] schedule+0x4e/0xc0 [5.272891] smpboot_thread_fn+0xff/0x160 [5.273696] ? smpboot_register_percpu_thread+0x140/0x140 [5.274655] kthread+0x12a/0x150 [5.275366] ? set_kthread_struct+0x50/0x50 [5.276170] ret_from_fork+0x22/0x30 [5.276930] [5.278397] Call Trace: Cloud provider is https://www.ip-exchange.de/, based on OpenStack. -- 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/1973839 Title: 5.15.0-30-generic : SSBD mitigation results in "unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0004)" and flood of kernel traces in some cloud providers Status in linux package in Ubuntu: Confirmed Bug description: When booting this in one of our clouds, we see an error early in the kernel output kernel: unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0004) at rIP: 0xabc90af4 (native_write_msr+0x4/0x20) and then an un-ending stream of "bare" tracebacks; which I think must be related [2.285717] kernel: Call Trace: [2.285722] kernel: [2.285723] kernel: ? speculation_ctrl_update+0x95/0x200 [2.292001] kernel: speculation_ctrl_update_current+0x1f/0x30 [2.292011] kernel: ssb_prctl_set+0x92/0xe0 [2.292016] kernel: arch_seccomp_spec_mitigate+0x62/0x70 [2.292019] kernel: seccomp_set_mode_filter+0x4de/0x530 [2.292024] kernel: do_seccomp+0x37/0x1f0 [2.292026] kernel: __x64_sys_seccomp+0x18/0x20 [2.292028] kernel: do_syscall_64+0x5c/0xc0 [2.292035] kernel: ? handle_mm_fault+0xd8/0x2c0 [2.299617] kernel: ? do_user_addr_fault+0x1e3/0x670 [2.312878] kernel: ? exit_to_user_mode_prepare+0x37/0xb0 [2.312894] kernel: ? irqentry_exit_to_user_mode+0x9/0x20 [2.312905] kernel: ? irqentry_exit+0x19/0x30 [2.312907] kernel: ? exc_page_fault+0x89/0x160 [2.312909] kernel: ? asm_exc_page_fault+0x8/0x30 [2.312914] kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae [2.312919] kernel: RIP: 0033:0x7fcffd6eaa3d [2.312924] kernel: Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 [2.312926] kernel: RSP: 002b:7ffe352e2938 EFLAGS: 0246 ORIG_RAX: 013d [2.312930] kernel: RAX: ffda RBX: 557d99d0c0c0 RCX: 7fcffd6eaa3d [2.319941]
[Kernel-packages] [Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
Im on Ubuntu 20.04.3 Kernel 5.15.0-46-generic I keep getting these messages too. dmesg | grep -C 3 UBSAN [4.026246] usb 5-6: new high-speed USB device number 6 using xhci_hcd [4.218259] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [4.218268] [4.218294] UBSAN: array-index-out-of-bounds in /build/linux-hwe-5.15-69LdM0/linux-hwe-5.15-5.15.0/drivers/ata/libahci.c:968:41 [4.218325] index 15 is out of range for type 'ahci_em_priv [8]' [4.218341] CPU: 18 PID: 583 Comm: scsi_eh_0 Not tainted 5.15.0-46-generic #49~20.04.1-Ubuntu [4.218343] Hardware name: Gigabyte Technology Co., Ltd. TRX40 AORUS MASTER/TRX40 AORUS MASTER, BIOS FB 07/27/2021 -- [ 30.313812] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 30.314834] Bridge firewalling registered [ 30.346342] [ 30.346347] UBSAN: array-index-out-of-bounds in /build/linux-hwe-5.15-69LdM0/linux-hwe-5.15-5.15.0/drivers/net/ethernet/aquantia/atlantic/aq_nic.c:1262:48 [ 30.346349] index 8 is out of range for type 'aq_vec_s *[8]' [ 30.346351] CPU: 5 PID: 2606 Comm: dockerd Tainted: G OE 5.15.0-46-generic #49~20.04.1-Ubuntu [ 30.346354] Hardware name: Gigabyte Technology Co., Ltd. TRX40 AORUS MASTER/TRX40 AORUS MASTER, BIOS FB 07/27/2021 -- 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/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 Status in linux package in Ubuntu: Confirmed Bug description: Something wrong with ata driver in dmesg found: [1.980693] kernel: [1.980699] kernel: fbcon: Taking over console [1.980703] kernel: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 [1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]' [1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 5.15.0-25-generic #25-Ubuntu [1.980716] kernel: Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [1.980718] kernel: Call Trace: [1.980721] kernel: [1.980723] kernel: show_stack+0x52/0x58 [1.980729] kernel: dump_stack_lvl+0x4a/0x5f [1.980734] kernel: dump_stack+0x10/0x12 [1.980736] kernel: ubsan_epilogue+0x9/0x45 [1.980739] kernel: __ubsan_handle_out_of_bounds.cold+0x44/0x49 [1.980742] kernel: ahci_qc_issue+0x166/0x170 [libahci] [1.980748] kernel: ata_qc_issue+0x135/0x240 [1.980752] kernel: ata_exec_internal_sg+0x2c4/0x580 [1.980754] kernel: ? vprintk_default+0x1d/0x20 [1.980759] kernel: ata_exec_internal+0x67/0xa0 [1.980762] kernel: sata_pmp_read+0x8d/0xc0 [1.980765] kernel: sata_pmp_read_gscr+0x3c/0x90 [1.980768] kernel: sata_pmp_attach+0x8b/0x310 [1.980771] kernel: ata_eh_revalidate_and_attach+0x28c/0x4b0 [1.980775] kernel: ata_eh_recover+0x6b6/0xb30 [1.980778] kernel: ? ahci_do_hardreset+0x180/0x180 [libahci] [1.980783] kernel: ? ahci_stop_engine+0xb0/0xb0 [libahci] [1.980787] kernel: ? ahci_do_softreset+0x290/0x290 [libahci] [1.980792] kernel: ? trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0 [1.980795] kernel: sata_pmp_eh_recover.isra.0+0x214/0x560 [1.980799] kernel: sata_pmp_error_handler+0x23/0x40 [1.980802] kernel: ahci_error_handler+0x43/0x80 [libahci] [1.980806] kernel: ata_scsi_port_error_handler+0x2b1/0x600 [1.980810] kernel: ata_scsi_error+0x9c/0xd0 [1.980813] kernel: scsi_error_handler+0xa1/0x180 [1.980817] kernel: ? scsi_unjam_host+0x1c0/0x1c0 [1.980820] kernel: kthread+0x12a/0x150 [1.980823] kernel: ? set_kthread_struct+0x50/0x50 [1.980826] kernel: ret_from_fork+0x22/0x30 [1.980831] kernel: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene16798 F pulseaudio /dev/snd/pcmC0D0p: eugene16798 F...m pulseaudio /dev/snd/controlC1: eugene16798 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 24 05:13:34 2022 HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61 InstallationDate: Installed on 2019-04-13 (1106 days ago) InstallationMedia: Kubuntu 19.04 "Disco