[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
Same issue here, also with Ryzen5 3600 and Radeon RX 5600 XT on Displayport. As with others on this thread, able to boot fine into 5.15.0-52-generic. As a 'user' rather than an 'enthusiast', I would have to look up how to manually install one of your alternative kernels, and I have other priorities at the moment, so I'll just wait for an official fix to roll out. Thanks to those of you who dedicate the time and energy to sorting this stuff out. -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: == SRU Justification == [Impact] "UBUNTU: SAUCE: Revert "drm/amd/display: Add helper for blanking all dp displays" caused AMD Navi10 GFX to panic at boot. [Fix] Backport the revised version of "drm/amd/display: Add helper for blanking all dp displays". [Test] Users confirmed the issue went away with this fix. We also verified the original issue we fixed didn't reappear. [Where problems could occur] We didn't test all the combination of dce110/dcn10/dcn30/dcn31, so many cases are untested, hence the potential risk is there. == Original Bug Report == Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) 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:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):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-7C52 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/1996740/+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] Re: Support Intel IPU6 MIPI camera
This bug was fixed in the package linux-firmware - 20221114.git60310c2d-0ubuntu1 --- linux-firmware (20221114.git60310c2d-0ubuntu1) lunar; urgency=medium * Support Intel IPU6 MIPI camera (LP: #1987595) - SAUCE: intel-ipu6: update ipu6ep firmware - SAUCE: intel-ivsc: support more sensors - SAUCE: intel-ivsc: add more firmware * Realtek 8852c WiFi/BT firmware support (LP: #1995046) - Rebase to upstream commit 60310c2deb8c67948a38310ac5f15cf3abcc30e7 Rebase against git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git - Removing crnv32 - qca: Update firmware files for BT chip WCN3991. - i915: Add GuC v70.5.1 for DG1, DG2, TGL and ADL-P - i915: Add versionless HuC files for current platforms - cxgb4: Update firmware to revision 1.27.0.0 - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for MT7922 WiFi device - linux-firmware: update firmware for mediatek bluetooth chip (MT7921) - rtl_bt: Update RTL8852A BT USB firmware to 0xD9B8_8207 - linux-firmware: update firmware for mediatek bluetooth chip (MT7922) - mediatek: Update mt8186 SOF firmware to v0.2.1 - mediatek: Add new mt8195 SOF firmware - mediatek: mt8195: Update scp.img to v2.0.11956 - linux-firmware: Update AMD cpu microcode - mediatek: Update mt8186 SCP firmware - rtw89: 8852c: update fw to v0.27.56.0 - rtw89: 8852c: update fw to v0.27.56.1 - qcom: add squashed version of a530 zap shader - mediatek: Update mt8195 SOF firmware to v0.4.1 - amdgpu: update Sienna Cichlid RLC firmware - amdgpu: update Navy Flounder RLC firmware - amdgpu: update Dimgrey Cavefish RLC firmware - amdgpu: update Beige Goby RLC firmware - amdgpu: update Yellow Carp RLC firmware - amdgpu: update GC 10.3.7 RLC firmware - amdgpu: update GC 10.3.6 RLC firmware - rtl_bt: Update RTL8852C BT USB firmware to 0xD5B8_A40A - iwlwifi: update 9000-family firmwares to core72-129 - iwlwifi: add new FWs from core72-129 release - rtw89: 8852b: add initial fw v0.27.32.0 - linux-firmware: Add firmware for Cirrus CS35L41 on HP Laptops - linux-firmware: Add firmware for Cirrus CS35L41 on Lenovo Laptops - linux-firmware: Add firmware for Cirrus CS35L41 on ASUS Laptops - brcm: add symlink for Pi Zero 2 W NVRAM file - cnm: update chips wave521c firmware. - i915: Add HuC 7.10.3 for DG2 - rtlwifi: Add firmware v4.0 for RTL8188FU - rtlwifi: update firmware for rtl8192eu to v35.7 - rtw89: 8852b: update fw to v0.27.32.1 - qcom: replace split SC7180 venus firmware images with symlink - qcom: update venus firmware file for v5.4 - qcom: remove split SC7280 venus firmware images - qcom: update venus firmware files for VPU-2.0 - iwlwifi: add new FWs from core69-81 release - iwlwifi: add new PNVM binaries from core74-44 release - linux-firmware: Add firmware for Cirrus CS35L41 on new ASUS Laptop - qcom/venus-1.8: replace split firmware with the mbn file - qcom/venus-4.2: replace split firmware with the mbn file - qcom/venus-4.2: drop split firmware in favour of the mbn file - qcom/vpu-1.0: drop split firmware in favour of the mbn file - qcom: drop split a530_zap firmware file - iwlwifi: add new FWs from core74_pv-60 release - mrvl: prestera: Update Marvell Prestera Switchdev FW to v4.1 - WHENCE: mrvl: prestera: Add WHENCE entries for newly updated 4.1 FW images - rtl_bt: Update RTL8822C BT USB firmware to 0xFFB8_ABD3 - rtl_bt: Update RTL8822C BT UART firmware to 0xFFB8_ABD6 - amdgpu: update DMCUB firmware for DCN 3.1.6 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX200 - linux-firmware: Update firmware file for Intel Bluetooth AX210 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth 9462 - linux-firmware: Update firmware file for Intel Bluetooth 9462 -- Juerg Haefliger Wed, 16 Nov 2022 16:39:08 +0100 ** Changed in: linux-firmware (Ubuntu Lunar) Status: In Progress => Fix Released -- 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/1987595 Title: Support Intel IPU6 MIPI camera Status in HWE Next: New Status in linux
[Kernel-packages] [Bug 1995046] Re: Realtek 8852c WiFi/BT firmware support
This bug was fixed in the package linux-firmware - 20221114.git60310c2d-0ubuntu1 --- linux-firmware (20221114.git60310c2d-0ubuntu1) lunar; urgency=medium * Support Intel IPU6 MIPI camera (LP: #1987595) - SAUCE: intel-ipu6: update ipu6ep firmware - SAUCE: intel-ivsc: support more sensors - SAUCE: intel-ivsc: add more firmware * Realtek 8852c WiFi/BT firmware support (LP: #1995046) - Rebase to upstream commit 60310c2deb8c67948a38310ac5f15cf3abcc30e7 Rebase against git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git - Removing crnv32 - qca: Update firmware files for BT chip WCN3991. - i915: Add GuC v70.5.1 for DG1, DG2, TGL and ADL-P - i915: Add versionless HuC files for current platforms - cxgb4: Update firmware to revision 1.27.0.0 - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for MT7922 WiFi device - linux-firmware: update firmware for mediatek bluetooth chip (MT7921) - rtl_bt: Update RTL8852A BT USB firmware to 0xD9B8_8207 - linux-firmware: update firmware for mediatek bluetooth chip (MT7922) - mediatek: Update mt8186 SOF firmware to v0.2.1 - mediatek: Add new mt8195 SOF firmware - mediatek: mt8195: Update scp.img to v2.0.11956 - linux-firmware: Update AMD cpu microcode - mediatek: Update mt8186 SCP firmware - rtw89: 8852c: update fw to v0.27.56.0 - rtw89: 8852c: update fw to v0.27.56.1 - qcom: add squashed version of a530 zap shader - mediatek: Update mt8195 SOF firmware to v0.4.1 - amdgpu: update Sienna Cichlid RLC firmware - amdgpu: update Navy Flounder RLC firmware - amdgpu: update Dimgrey Cavefish RLC firmware - amdgpu: update Beige Goby RLC firmware - amdgpu: update Yellow Carp RLC firmware - amdgpu: update GC 10.3.7 RLC firmware - amdgpu: update GC 10.3.6 RLC firmware - rtl_bt: Update RTL8852C BT USB firmware to 0xD5B8_A40A - iwlwifi: update 9000-family firmwares to core72-129 - iwlwifi: add new FWs from core72-129 release - rtw89: 8852b: add initial fw v0.27.32.0 - linux-firmware: Add firmware for Cirrus CS35L41 on HP Laptops - linux-firmware: Add firmware for Cirrus CS35L41 on Lenovo Laptops - linux-firmware: Add firmware for Cirrus CS35L41 on ASUS Laptops - brcm: add symlink for Pi Zero 2 W NVRAM file - cnm: update chips wave521c firmware. - i915: Add HuC 7.10.3 for DG2 - rtlwifi: Add firmware v4.0 for RTL8188FU - rtlwifi: update firmware for rtl8192eu to v35.7 - rtw89: 8852b: update fw to v0.27.32.1 - qcom: replace split SC7180 venus firmware images with symlink - qcom: update venus firmware file for v5.4 - qcom: remove split SC7280 venus firmware images - qcom: update venus firmware files for VPU-2.0 - iwlwifi: add new FWs from core69-81 release - iwlwifi: add new PNVM binaries from core74-44 release - linux-firmware: Add firmware for Cirrus CS35L41 on new ASUS Laptop - qcom/venus-1.8: replace split firmware with the mbn file - qcom/venus-4.2: replace split firmware with the mbn file - qcom/venus-4.2: drop split firmware in favour of the mbn file - qcom/vpu-1.0: drop split firmware in favour of the mbn file - qcom: drop split a530_zap firmware file - iwlwifi: add new FWs from core74_pv-60 release - mrvl: prestera: Update Marvell Prestera Switchdev FW to v4.1 - WHENCE: mrvl: prestera: Add WHENCE entries for newly updated 4.1 FW images - rtl_bt: Update RTL8822C BT USB firmware to 0xFFB8_ABD3 - rtl_bt: Update RTL8822C BT UART firmware to 0xFFB8_ABD6 - amdgpu: update DMCUB firmware for DCN 3.1.6 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX200 - linux-firmware: Update firmware file for Intel Bluetooth AX210 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth 9462 - linux-firmware: Update firmware file for Intel Bluetooth 9462 -- Juerg Haefliger Wed, 16 Nov 2022 16:39:08 +0100 ** Changed in: linux-firmware (Ubuntu Lunar) Status: Fix Committed => Fix Released -- 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/1995046 Title: Realtek 8852c WiFi/BT firmware support Status in HWE Next: New Status
[Kernel-packages] [Bug 1997279] 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 1997279 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/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997279/+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 1997279] Re: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997279/+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 1997279] [NEW] Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS
You have been subscribed to a public bug: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS https://bugs.launchpad.net/bugs/1997279 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 187761] Re: Need a way to disable selected modules with a kernel flag
uas.ko hangs, fails, spams dmesg on all 5 HP AMD A10 systems tested, on all AMD USB3 ports if writing to any device that has UAS. If booting a livecd on a UAS capable device, UAS cannot be unloaded. UAS will stall any writes to the temp log partition ubuntu creates on the boot device. -- 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/187761 Title: Need a way to disable selected modules with a kernel flag Status in linux package in Ubuntu: In Progress Bug description: Binary package hint: linux-image Bug #90271 and bug #187671 describe situations where Live CDs and install CDs fail to work because a broken kernel module causes a hang before user has a say. The error may be in an optional kernel module (such as sound card driver or memory card reader) but the end user has no way to prevent kernel from loading a possibly known broken module. Vanilla kernels from kernel.org support flag disablemodules (e.g. disablemodules=8139too,sdhci prevents linux kernel from loading 8139too.ko or sdhci.ko) but such flag does not seem to work with Ubuntu. This is a feature request to enable such a flag. It is not needed for normal use but in case of rare hardware exposing a bug in a kernel module not having such a flag prevents one from booting Ubuntu. (I'd prefer booting without network adapter or memory card reader to not booting at all). This issue also causes slowdowns such as bug #187671 which cannot proceed until bug #90271 is fixed because testing possible fixes for the bug is really hard until the other kernel module has been fixed. (This is because both bugs affect the same laptop hardware and both kernel modules cause a kernel hang.) I'd consider disablemodules flag similar to acpi flag - it should not be needed but still we need it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/187761/+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
Confirmed that reducing the size of the initrd.img slightly allowed my machine to boot. I just enabled `COMPRESSLEVEL=19` with `COMPRESS=zstd` (default on debian) in initramfs.conf. That reduced my initrd.img size from 72MB to 62MB, which allowed my machine to boot. Ultimately, I set `MODULES=dep` (instead of `MODULES=most`) and reverted the compression to defaults. This reduced my initrd.img to 22MB, which includes Intel microcode (specific binary), nvme, crypto, and lvm support, among other things. --- For the record: My machine is running Debian bookworm with the Nvidia proprietary drivers with 32GB. I first noticed the issue when, coincidentally, upgrading from kernel 5.19 to 6.0. ``` Loading Linux 6.0.0-4amd64 ... Loading initial ramdisk ... error: out of memory. Press any key to continue... ``` -- 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: Triaged Status in grub2-unsigned package in Ubuntu: Triaged Status in initramfs-tools package in Ubuntu: Won't Fix 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
[Kernel-packages] [Bug 1953235] Re: systemctl suspend stopped working: laptop immeadeately wakes up again
You saved my day. I also install cuda stuff from nvidia driver repository (using ubuntu 20.04 and needed cuda 11) /etc/systemd/system/systemd-suspend.service.requires contained symbolic links which point to /lib/systemd/system/nvidia-resume.service removing these symbolic links made suspend work again. another symptom was: systemctl suspend was not working but pm-suspend was working. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1953235 Title: systemctl suspend stopped working: laptop immeadeately wakes up again Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: I always suspend my laptop using `systemctl suspend`. It worked for a year as expected until today. Buggy Behavior: after `systemctl suspend` the seemingly usual suspend happens, however the laptop wakes up immediately. Things get more weird from here, as I need to input my password twice to get back into GNOME. Troubleshooting I did: 1. apt update && apt dist-upgrade 2. Disabled nvidia-suspend.service, nvidia-persistenced.service, nvidia-resume.service 3. Booted with an earlier kernel version where it used to work: `5.11.0-40`, `5.11.0-38` 3. Detached all devices, and the power cable 4. Rebooted into a separate user that has no tweaks, gnome-extensions etc 5. The issue persists -- I attached relevant parts of `journalctl`: from the time when I used `systemctl suspend` till a minute or so after I logged back into GNOME. Additionally: ``` user@myLaptop:~$ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.6 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.7 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus A 00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus B 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 7 01:00.0 3D controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] (rev a1) 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 25) 04:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c2) 05:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller 05:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor 05:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 05:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 05:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller 06:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 61) ``` ``` user@myLaptop:~$ cat /proc/acpi/wakeup DeviceS-state Status Sysfs node GPP0S4*enabled pci::00:01.1 GPP1S4*enabled pci::00:01.2 GPP2S4*disabled GPP3S4*disabled GPP4S4*disabled GPP5S4*enabled pci::00:01.6 GP17S4*enabled pci::00:08.1 XHC0S4*enabled pci::05:00.3 XHC1S4
[Kernel-packages] [Bug 1993665] Re: Update the 470-server NVIDIA driver
Verification on kinetic is incomplete. Things do work on a cloud instance with a single gpgpu. In these cases, both the DKMS and LRM version of the driver works with the cuda samples test. Problems are encountered when running on either the DGX2 or A100 systems. For the A100, I have not been able to get either the 470.141.03 (in -release) or 470.141.10 (in -proposed) drivers to work. The 470.141.03 driver did pass the cuda tests on the DGX2, testing with 470.141.10 is still in progress. Both the DGX2 and A100 require the fabric-manager package. This could be where the problem lies or it could be something in the driver that is only exposed by these systems. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/1993665 Title: Update the 470-server NVIDIA driver Status in fabric-manager-470 package in Ubuntu: In Progress Status in libnvidia-nscq-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in fabric-manager-470 source package in Bionic: Fix Released Status in libnvidia-nscq-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in fabric-manager-470 source package in Focal: Fix Released Status in libnvidia-nscq-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in fabric-manager-470 source package in Jammy: Fix Released Status in libnvidia-nscq-470 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470-server source package in Jammy: Fix Released Status in fabric-manager-470 source package in Kinetic: In Progress Status in libnvidia-nscq-470 source package in Kinetic: In Progress Status in nvidia-graphics-drivers-470-server source package in Kinetic: In Progress Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-470/+bug/1993665/+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 1990190] Re: Focal update: v5.4.211 upstream stable release
It seems that commit bcf91619e32fe584ecfafa49a3db3d1db4ff70b2 included in 5.4.0-132.148 breaks Node Exporter and cadvisor, cf. https://github.com/prometheus/node_exporter/issues/2500. A minimal reproducer in Go is available at https://github.com/prometheus/node_exporter/issues/2500#issuecomment-1304847221 I have reverted that commit in my test environment and haven't been able to reproduce the problem since. ** Bug watch added: github.com/prometheus/node_exporter/issues #2500 https://github.com/prometheus/node_exporter/issues/2500 -- 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/1990190 Title: Focal update: v5.4.211 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.211 upstream stable release from git://git.kernel.org/ Makefile: link with -z noexecstack --no-warn-rwx-segments x86: link vdso and boot with -z noexecstack --no-warn-rwx-segments scsi: Revert "scsi: qla2xxx: Fix disk failure to rediscover" ALSA: bcd2000: Fix a UAF bug on the error path of probing igc: Remove _I_PHY_ID checking wifi: mac80211_hwsim: fix race condition in pending packet wifi: mac80211_hwsim: add back erroneously removed cast wifi: mac80211_hwsim: use 32-bit skb cookie add barriers to buffer_uptodate and set_buffer_uptodate HID: wacom: Only report rotation for art pen HID: wacom: Don't register pad_input for touch switch KVM: nVMX: Snapshot pre-VM-Enter BNDCFGS for !nested_run_pending case KVM: nVMX: Snapshot pre-VM-Enter DEBUGCTL for !nested_run_pending case KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0 KVM: nVMX: Let userspace set nVMX MSR to any _host_ supported value KVM: x86: Mark TSS busy during LTR emulation _after_ all fault checks KVM: x86: Set error code to segment selector on LLDT/LTR non-canonical #GP mm/mremap: hold the rmap lock in write mode when moving page table entries. ALSA: hda/conexant: Add quirk for LENOVO 20149 Notebook model ALSA: hda/cirrus - support for iMac 12,1 model ALSA: hda/realtek: Add quirk for another Asus K42JZ model tty: vt: initialize unicode screen buffer vfs: Check the truncate maximum size in inode_newsize_ok() fs: Add missing umask strip in vfs_tmpfile thermal: sysfs: Fix cooling_device_stats_setup() error code path fbcon: Fix boundary checks for fbcon=vc:n1-n2 parameters usbnet: Fix linkwatch use-after-free on disconnect ovl: drop WARN_ON() dentry is NULL in ovl_encode_fh() parisc: Fix device names in /proc/iomem parisc: io_pgetevents_time64() needs compat syscall in 32-bit compat mode drm/gem: Properly annotate WW context on drm_gem_lock_reservations() error drm/nouveau: fix another off-by-one in nvbios_addr drm/amdgpu: Check BO's requested pinning domains against its preferred_domains iio: light: isl29028: Fix the warning in isl29028_remove() fuse: limit nsec serial: mvebu-uart: uart2 error bits clearing md-raid10: fix KASAN warning ia64, processor: fix -Wincompatible-pointer-types in ia64_get_irr() PCI: Add defines for normal and subtractive PCI bridges powerpc/fsl-pci: Fix Class Code of PCIe Root Port powerpc/ptdump: Fix display of RW pages on FSL_BOOK3E powerpc/powernv: Avoid crashing if rng is NULL MIPS: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK coresight: Clear the connection field properly USB: HCD: Fix URB giveback issue in tasklet function ARM: dts: uniphier: Fix USB interrupts for PXs2 SoC arm64: dts: uniphier: Fix USB interrupts for PXs3 SoC netfilter: nf_tables: fix null deref due to zeroed list head epoll: autoremove wakers even more aggressively x86: Handle idle=nomwait cmdline properly for x86_idle arm64: Do not forget syscall when starting a new thread. arm64: fix oops in concurrently setting insn_emulation sysctls ext2: Add more validity checks for inode counts genirq: Don't return error on missing optional irq_request_resources() wait: Fix __wait_event_hrtimeout for RT/DL tasks ARM: dts: imx6ul: add missing properties for sram ARM: dts: imx6ul: change operating-points to uint32-matrix ARM: dts: imx6ul: fix csi node compatible ARM: dts: imx6ul: fix lcdif node compatible ARM: dts: imx6ul: fix qspi node compatible spi: synquacer: Add missing clk_disable_unprepare() ARM: OMAP2+: display: Fix refcount leak bug ACPI: EC: Remove duplicate
[Kernel-packages] [Bug 1979633] Re: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated"
Dame problem after reboot for install flatpak ando snap software in Ubuntu 22.10 x86_64 kernel 5.19.0-23-generic. The error in boot is /dev/sda3: clean, 348901/3973120 files, 4784925/15869184 blocks [ 4.721599] Dev loop0: unable to read RDB block 8 [ 7.184964] Dev loop15: unable to read RDB block 8 Hope your aport and solve. -- 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/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd 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: bonnaudl 5120 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy Uname: Linux 5.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 04/11/2022 dmi.bios.release: 7.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.15RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.6 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1997178] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997178 Title: Black screen after wake from S3 suspend on Nvidia proprietary driver redux Status in linux package in Ubuntu: Confirmed Bug description: When resuming from suspend in Ubuntu 22.04 with proprietary Nvidia driver 515, screen is black, and never changes after 10 minutes of waiting. However journalctl shows activity after wake (see attached log excerpt, where wake occurs around Nov 20 10:28:37 with black screen, followed by forced REISUB reboot a couple minutes later when screen failed to update). This makes me think the issue is around Nvidia driver <-> Linux kernel communication. I [previously reported](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987134) similar black screen after wake behavior that seemed resolve with a Linux kernel update, but subsequent Linux kernel and Nvidia driver updates steadily regressed back to the previous behavior. The most recent kernel update from a few days ago (5.15.0-53-generic) never wakes from suspend (so far out of 5 trials). Previous few kernels where regression was first noticed it was 50/50 odds of successful wake, so most recent kernel is a noticeable regression. Important note: most recent kernel (5.15.0-53) upgrade freezed system mid-upgrade (first time this has happened to me on Linux in at least 5 years!). Damaged GRUB and Nvidia DKMS, requiring reinstallation of GRUB, the kernel, Nvidia drivers, and a GRUB update (in that order). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0d.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 20 11:20:45 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/515.65.01, 5.15.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PNY GM204 [GeForce GTX 970] [196e:1131] InstallationDate: Installed on 2022-08-17 (95 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-53-generic root=UUID=70074436-a9a5-4212-9b57-7600a7dc6843 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.70 dmi.board.name: X470 Taichi Ultimate dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.70:bd03/29/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470TaichiUltimate:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
[Kernel-packages] [Bug 1860284]
Created attachment 303237 experimental patch That patch (d341838d776a ("x86/PCI: Disable E820 reserved region clipping via quirks")) relies on quirks that match DMI Vendor, Product Version, Product Name, and Board Name. This isn't an ideal solution because there are likely other systems we don't know about that need the a similar fix. The patch I'm attaching here is an experimental idea to work around this issue without the maintenance burden of the quirks. If anybody would be willing to test this patch, I would be very grateful. To test it, either start with a v5.18 or earlier kernel, or on a v5.19 or newer kernel, revert d341838d776a (or just remove your system's ID from the list in pci_crs_quirks[]). Then apply this patch, boot with the "efi=debug" parameter, connect a dock, see whether it works, and attach the dmesg log. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1860284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1860284]
>From the dmesg log in https://bugzilla.kernel.org/attachment.cgi?id=287483, BIOS-e820: [mem 0x4bc5-0xcfff] reserved pci_bus :00: root bus resource [mem 0x6540-0xbfff window] pci :00:07.1: PCI bridge to [bus 2b-54] pci :00:07.1: bridge window [mem 0x6600-0x721f] # add dock pcieport :00:07.1: pciehp: Slot(0-1): Card present pcieport :00:07.1: pciehp: Slot(0-1): Link Up pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] >From the log in https://bugzilla.kernel.org/attachment.cgi?id=287665, which includes the patch in https://bugzilla.kernel.org/attachment.cgi?id=287661 to "not exclude EFI MMIO regions": pci :2b:00.0: BAR 14: assigned [mem 0x6600-0x721f] The 00:07.1 bridge window was the same in both cases, so the same space is available on bus 2b. I think the reason the first one failed even though the space was available was because the entire MMIO aperture was marked "reserved" in E820, so PCI avoids assigning space from it. The patch basically avoids that E820 checking if the region is EfiMemoryMappedIO. The patch https://git.kernel.org/linus/d341838d776a ("x86/PCI: Disable E820 reserved region clipping via quirks") appeared in v5.19 and should work around this problem for this machine and others. -- 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias:
[Kernel-packages] [Bug 1997178] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver redux
Tested and confirmed that wake from sleep results in a black screen 100% of the time on 5.15.0-53-generic, but only ~10% of the time on 5.15.0-52-generic. Thus on the surface it seems 5.15.0-53-generic caused a regression. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997178 Title: Black screen after wake from S3 suspend on Nvidia proprietary driver redux Status in linux package in Ubuntu: New Bug description: When resuming from suspend in Ubuntu 22.04 with proprietary Nvidia driver 515, screen is black, and never changes after 10 minutes of waiting. However journalctl shows activity after wake (see attached log excerpt, where wake occurs around Nov 20 10:28:37 with black screen, followed by forced REISUB reboot a couple minutes later when screen failed to update). This makes me think the issue is around Nvidia driver <-> Linux kernel communication. I [previously reported](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987134) similar black screen after wake behavior that seemed resolve with a Linux kernel update, but subsequent Linux kernel and Nvidia driver updates steadily regressed back to the previous behavior. The most recent kernel update from a few days ago (5.15.0-53-generic) never wakes from suspend (so far out of 5 trials). Previous few kernels where regression was first noticed it was 50/50 odds of successful wake, so most recent kernel is a noticeable regression. Important note: most recent kernel (5.15.0-53) upgrade freezed system mid-upgrade (first time this has happened to me on Linux in at least 5 years!). Damaged GRUB and Nvidia DKMS, requiring reinstallation of GRUB, the kernel, Nvidia drivers, and a GRUB update (in that order). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0d.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 20 11:20:45 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/515.65.01, 5.15.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PNY GM204 [GeForce GTX 970] [196e:1131] InstallationDate: Installed on 2022-08-17 (95 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-53-generic root=UUID=70074436-a9a5-4212-9b57-7600a7dc6843 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.70 dmi.board.name: X470 Taichi Ultimate dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.70:bd03/29/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470TaichiUltimate:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1
[Kernel-packages] [Bug 1997178] [NEW] Black screen after wake from S3 suspend on Nvidia proprietary driver redux
You have been subscribed to a public bug: When resuming from suspend in Ubuntu 22.04 with proprietary Nvidia driver 515, screen is black, and never changes after 10 minutes of waiting. However journalctl shows activity after wake (see attached log excerpt, where wake occurs around Nov 20 10:28:37 with black screen, followed by forced REISUB reboot a couple minutes later when screen failed to update). This makes me think the issue is around Nvidia driver <-> Linux kernel communication. I [previously reported](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987134) similar black screen after wake behavior that seemed resolve with a Linux kernel update, but subsequent Linux kernel and Nvidia driver updates steadily regressed back to the previous behavior. The most recent kernel update from a few days ago (5.15.0-53-generic) never wakes from suspend (so far out of 5 trials). Previous few kernels where regression was first noticed it was 50/50 odds of successful wake, so most recent kernel is a noticeable regression. Important note: most recent kernel (5.15.0-53) upgrade freezed system mid-upgrade (first time this has happened to me on Linux in at least 5 years!). Damaged GRUB and Nvidia DKMS, requiring reinstallation of GRUB, the kernel, Nvidia drivers, and a GRUB update (in that order). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0d.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 20 11:20:45 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/515.65.01, 5.15.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PNY GM204 [GeForce GTX 970] [196e:1131] InstallationDate: Installed on 2022-08-17 (95 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-53-generic root=UUID=70074436-a9a5-4212-9b57-7600a7dc6843 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.70 dmi.board.name: X470 Taichi Ultimate dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.70:bd03/29/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470TaichiUltimate:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze jammy ubuntu -- Black screen after wake from S3 suspend on Nvidia proprietary driver
[Kernel-packages] [Bug 1903858] Re: Synaptics Touchpad not working dynabook TECRA A40-G
Thanks .. It's solutions done for me, i hope done for other persons. Setting kernel parameter kernel parameter "psmouse.synaptics_intertouch=1" solved the problem, as suggested in comment #4 above and here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907991/comments/29 Cheers! -- 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/1903858 Title: Synaptics Touchpad not working dynabook TECRA A40-G Status in linux package in Ubuntu: In Progress Bug description: Hi, I've got a (toshiba) dynabook TECRA A40-G with a non-functional touchpad. I tried the different debug steps on https://wiki.ubuntu.com/DebuggingTouchpadDetection/ This is on Description:Ubuntu 20.04.1 LTS Release:20.04 xserver-xorg-input-libinput: Installed: 0.29.0-1 Candidate: 0.29.0-1 Version table: *** 0.29.0-1 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status It sometimes "works" to move the pointer the slightest amount or to 'press and hold" when moving the usb mouse but not really enough to justify 'working and then not'. Please find attached debugging steps. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-libinput 0.29.0-1 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 11 11:40:10 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu InstallationDate: Installed on 2020-11-08 (2 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b689 Chicony Electronics Co., Ltd TOSHIBA Web Camera - HD Bus 001 Device 004: ID 8087:0029 Intel Corp. Bus 001 Device 002: ID 275d:0ba6 USB OPTICAL MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dynabook Inc. dynabook TECRA A40-G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=976c7b49-f194-41a9-86fa-7f2513dc77be ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/28/2020 dmi.bios.vendor: Dynabook Inc. dmi.bios.version: Version 3.10 dmi.board.asset.tag: 00 dmi.board.name: A0104/0002 dmi.board.vendor: Dynabook Inc. dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: Dynabook Inc. dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnDynabookInc.:bvrVersion3.10:bd04/28/2020:svnDynabookInc.:pndynabookTECRAA40-G:pvrPMZ20E-0K801FDU:rvnDynabookInc.:rnA0104/0002:rvrVersionA0:cvnDynabookInc.:ct10:cvrVersion1.0: dmi.product.family: dynabook TECRA dmi.product.name: dynabook TECRA A40-G dmi.product.sku: PMZ20E dmi.product.version: PMZ20E-0K801FDU dmi.sys.vendor: Dynabook Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903858/+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 1996740] Re: 5.15.0-53-generic no longer boots
I just ran apt update && apt upgrade, noticed the dkms upgrade, rebooted into 5.15.0-53-generic and still got a no-signal black monitor. See my previous comment for hardware. Is the fix not out yet or was the upgraded dkms package supposed to be the fix? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: == SRU Justification == [Impact] "UBUNTU: SAUCE: Revert "drm/amd/display: Add helper for blanking all dp displays" caused AMD Navi10 GFX to panic at boot. [Fix] Backport the revised version of "drm/amd/display: Add helper for blanking all dp displays". [Test] Users confirmed the issue went away with this fix. We also verified the original issue we fixed didn't reappear. [Where problems could occur] We didn't test all the combination of dce110/dcn10/dcn30/dcn31, so many cases are untested, hence the potential risk is there. == Original Bug Report == Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) 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:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):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-7C52 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/1996740/+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 1997250] [NEW] package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subproce
Public bug reported: Won't update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2 Uname: Linux 5.10.13-051013-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 21 14:24:56 2022 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-02-04 (655 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1997250 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2 failed to install/upgrade: installed bcmwl-kernel-source package post- installation script subprocess returned error exit status 10 Status in bcmwl package in Ubuntu: New Bug description: Won't update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2 Uname: Linux 5.10.13-051013-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 21 14:24:56 2022 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-02-04 (655 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.2 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1997250/+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 1851887] Re: [ASUS N550JK] After a system reboot, the audio seems muted until one raises the level above 50%
Ping! -- 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/1851887 Title: [ASUS N550JK] After a system reboot, the audio seems muted until one raises the level above 50% Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when I play a clip (be it a Video, song or a radiostation, it doesn't matter) and I have the volume lowered to 10% I can't hear any sound whatsoever. Not until I raise the volume with Fn + F12 (F12 has a speaker icon on it to raise the volume). It's as if PulseAudio is muted until I raise the volume. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7 Uname: Linux 5.3.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kristoffer 1627 F pulseaudio /dev/snd/controlC0: kristoffer 1627 F pulseaudio CurrentDesktop: MATE Date: Fri Nov 8 23:39:31 2019 InstallationDate: Installed on 2019-10-05 (34 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JK.208:bd09/26/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N550JK dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kristoffer 1338 F pulseaudio /dev/snd/controlC1: kristoffer 1338 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-11 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. N550JK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-22-generic root=UUID=cd07365f-1075-4d73-aa51-3e3b4e91a8d1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-22-generic N/A linux-backports-modules-5.3.0-22-generic N/A linux-firmware1.183.1 Tags: eoan Uname: Linux 5.3.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JK.208:bd09/26/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N550JK dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851887/+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 1997121] Re: Ubuntu can't wake up after being suspended with docking station and external monitor
** Description changed: Ubuntu can't wake up while being detached from docking station after being suspended with docking station and external monitor. Kernel 5.15.0-53-generic. I think I didn't have this problem before. Last upgrade (two days ago) seems to be the issue. Laptop thinkpad e14, docking station ThinkPad USB-C Dock Gen 2. Nothing works, switching into terminal Ctrl-Alt-F1 etc. doesn't work. Only hard shutdown seems to be effective. I wasn't able to find a way to wake up laptop in this situation. + + After several day I have to say that the situation is bad. I can't wake up + computer from time to time when it's connected to docking station all the time. This isn't funny! For me it looks like Ubuntu doesn't have any regression testing. + Hard reset is the only option to "wake up" the laptop, and this is serious! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: as 5898 F pulseaudio /dev/snd/controlC0: as 5898 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 18 23:05:42 2022 InstallationDate: Installed on 2020-12-06 (712 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20T6000TPB ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=a5796f3d-37a8-428b-aa28-c160ea77bc9b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2021 dmi.bios.release: 1.16 dmi.bios.vendor: LENOVO dmi.bios.version: R1AET40W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20T6000TPB dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrR1AET40W(1.16):bd09/06/2021:br1.16:efr1.16:svnLENOVO:pn20T6000TPB:pvrThinkPadE14Gen2:rvnLENOVO:rn20T6000TPB:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20T6_BU_Think_FM_ThinkPadE14Gen2: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20T6000TPB dmi.product.sku: LENOVO_MT_20T6_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO -- 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/1997121 Title: Ubuntu can't wake up after being suspended with docking station and external monitor Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu can't wake up while being detached from docking station after being suspended with docking station and external monitor. Kernel 5.15.0-53-generic. I think I didn't have this problem before. Last upgrade (two days ago) seems to be the issue. Laptop thinkpad e14, docking station ThinkPad USB-C Dock Gen 2. Nothing works, switching into terminal Ctrl-Alt-F1 etc. doesn't work. Only hard shutdown seems to be effective. I wasn't able to find a way to wake up laptop in this situation. After several day I have to say that the situation is bad. I can't wake up computer from time to time when it's connected to docking station all the time. This isn't funny! For me it looks like Ubuntu doesn't have any regression testing. Hard reset is the only option to "wake up" the laptop, and this is serious! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: as 5898 F pulseaudio /dev/snd/controlC0: as 5898 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 18 23:05:42 2022 InstallationDate: Installed on 2020-12-06 (712 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20T6000TPB ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=a5796f3d-37a8-428b-aa28-c160ea77bc9b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A
[Kernel-packages] [Bug 1991951] Re: RCU stalls
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991951 Title: RCU stalls Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: our RCU Stall Timeouts are different to upstream defaults; with regular one 3x longer; and expedited one 1000x shorter. not sure why. Let's harmonize on 60 & 0, which is 60 for regular ones that are set on most architectures; and upstream default for the expedited ones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991951/+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 1997248] [NEW] package nvidia-dkms-510 510.85.02-0ubuntu0.20.04.1 failed to install/upgrade: o subprocesso instalado, do pacote nvidia-dkms-510, o script post-installation retor
Public bug reported: asd ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-510 510.85.02-0ubuntu0.20.04.1 Uname: Linux 6.0.9-x64v1-xanmod1 x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 21 10:55:45 2022 ErrorMessage: o subprocesso instalado, do pacote nvidia-dkms-510, o script post-installation retornou erro do status de saída 10 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: nvidia-graphics-drivers-510 Title: package nvidia-dkms-510 510.85.02-0ubuntu0.20.04.1 failed to install/upgrade: o subprocesso instalado, do pacote nvidia-dkms-510, o script post-installation retornou erro do status de saída 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1997248 Title: package nvidia-dkms-510 510.85.02-0ubuntu0.20.04.1 failed to install/upgrade: o subprocesso instalado, do pacote nvidia-dkms-510, o script post-installation retornou erro do status de saída 10 Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: asd ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-510 510.85.02-0ubuntu0.20.04.1 Uname: Linux 6.0.9-x64v1-xanmod1 x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 21 10:55:45 2022 ErrorMessage: o subprocesso instalado, do pacote nvidia-dkms-510, o script post-installation retornou erro do status de saída 10 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: nvidia-graphics-drivers-510 Title: package nvidia-dkms-510 510.85.02-0ubuntu0.20.04.1 failed to install/upgrade: o subprocesso instalado, do pacote nvidia-dkms-510, o script post-installation retornou erro do status de saída 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1997248/+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 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 Status in linux source package in Jammy: Fix Committed 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 Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp2s0no wireless extensions. virbr0no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (1 days ago) dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Kernel-packages] [Bug 1997113] Re: Jammy update: v5.15.76 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997113 Title: Jammy update: v5.15.76 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.76 upstream stable release from git://git.kernel.org/ r8152: add PID for the Lenovo OneLink+ Dock arm64/mm: Consolidate TCR_EL1 fields usb: gadget: uvc: consistently use define for headerlen usb: gadget: uvc: use on returned header len in video_encode_isoc_sg usb: gadget: uvc: rework uvcg_queue_next_buffer to uvcg_complete_buffer usb: gadget: uvc: giveback vb2 buffer on req complete usb: gadget: uvc: improve sg exit condition UBUNTU: [Config] updateconfigs for ARM64_ERRATUM_1742098 arm64: errata: Remove AES hwcap for COMPAT tasks perf/x86/intel/pt: Relax address filter validation btrfs: enhance unsupported compat RO flags handling ocfs2: clear dinode links count in case of error ocfs2: fix BUG when iput after ocfs2_mknod fails selinux: enable use of both GFP_KERNEL and GFP_ATOMIC in convert_context() cpufreq: qcom: fix writes in read-only memory region i2c: qcom-cci: Fix ordering of pm_runtime_xx and i2c_add_adapter x86/microcode/AMD: Apply the patch early on every logical thread hwmon/coretemp: Handle large core ID value ata: ahci-imx: Fix MODULE_ALIAS ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS x86/resctrl: Fix min_cbm_bits for AMD cpufreq: qcom: fix memory leak in error path drm/amdgpu: fix sdma doorbell init ordering on APUs mm,hugetlb: take hugetlb_lock before decrementing h->resv_huge_pages kvm: Add support for arch compat vm ioctls KVM: arm64: vgic: Fix exit condition in scan_its_table() media: ipu3-imgu: Fix NULL pointer dereference in active selection access media: mceusb: set timeout to at least timeout provided media: venus: dec: Handle the case where find_format fails x86/topology: Fix multiple packages shown on a single-package system x86/topology: Fix duplicated core ID within a package btrfs: fix processing of delayed data refs during backref walking btrfs: fix processing of delayed tree block refs during backref walking drm/vc4: Add module dependency on hdmi-codec ACPI: extlog: Handle multiple records tipc: Fix recognition of trial period tipc: fix an information leak in tipc_topsrv_kern_subscr i40e: Fix DMA mappings leak HID: magicmouse: Do not set BTN_MOUSE on double report sfc: Change VF mac via PF as first preference if available. net/atm: fix proc_mpc_write incorrect return value net: phy: dp83867: Extend RX strap quirk for SGMII mode net: phylink: add mac_managed_pm in phylink_config structure scsi: lpfc: Fix memory leak in lpfc_create_port() udp: Update reuse->has_conns under reuseport_lock. cifs: Fix xid leak in cifs_create() cifs: Fix xid leak in cifs_copy_file_range() cifs: Fix xid leak in cifs_flock() cifs: Fix xid leak in cifs_ses_add_channel() dm: remove unnecessary assignment statement in alloc_dev() net: hsr: avoid possible NULL deref in skb_clone() ionic: catch NULL pointer issue on reconfig netfilter: nf_tables: relax NFTA_SET_ELEM_KEY_END set flags requirements nvme-hwmon: consistently ignore errors from nvme_hwmon_init nvme-hwmon: kmalloc the NVME SMART log buffer nvmet: fix workqueue MEM_RECLAIM flushing dependency net: sched: cake: fix null pointer access issue when cake_init() fails net: sched: delete duplicate cleanup of backlog and qlen net: sched: sfb: fix null pointer access issue when sfb_init() fails sfc: include vport_id in filter spec hash and equal() wwan_hwsim: fix possible memory leak in wwan_hwsim_dev_new() net: hns: fix possible memory leak in hnae_ae_register() net: sched: fix race condition in qdisc_graft() net: phy: dp83822: disable MDI crossover status change interrupt iommu/vt-d: Allow NVS regions in arch_rmrr_sanity_check() iommu/vt-d: Clean up si_domain in the init_dmars() error path fs: dlm: fix invalid derefence of sb_lvbptr arm64: mte: move register initialization to C ksmbd: handle smb2 query dir request for OutputBufferLength that is too small ksmbd: fix incorrect handling of iterate_dir tracing: Simplify conditional compilation code in tracing_set_tracer() tracing: Do not free snapshot if tracer is
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: == SRU Justification == [Impact] "UBUNTU: SAUCE: Revert "drm/amd/display: Add helper for blanking all dp displays" caused AMD Navi10 GFX to panic at boot. [Fix] Backport the revised version of "drm/amd/display: Add helper for blanking all dp displays". [Test] Users confirmed the issue went away with this fix. We also verified the original issue we fixed didn't reappear. [Where problems could occur] We didn't test all the combination of dce110/dcn10/dcn30/dcn31, so many cases are untested, hence the potential risk is there. == Original Bug Report == Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) 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:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):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-7C52 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/1996740/+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 1971712] Re: Add support for Intel DG2
Is this not going to happen? > kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip -- 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/1971712 Title: Add support for Intel DG2 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Confirmed Status in mesa source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip firmare: updates to i915 DMC, GuC [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971712/+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 1990068] Re: Kernel 5.19.0.15.15 crashes on boot (Ryzen 5 2500U)
After a lot of searching around, it seems that it is necessary to change the "iommu=soft" command on GRUB to "amd_iommu=off" on kernel 5.19 or higher. With that command, all kernels will boot fine afterwards. -- 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/1990068 Title: Kernel 5.19.0.15.15 crashes on boot (Ryzen 5 2500U) Status in linux package in Ubuntu: Confirmed Bug description: When installing the daily build ISO fo Ubuntu Kinect Kudu, the system will hang at boot, forcing a reboot and then going to Advanced Option (on GRUB) and select kernel 5.15.0.27.28, which comes preinstalled when Ubuntu is installed, which then works as it should. Testing with different Kernel versions shows that 5.18.19 works fine, without crashing on "Loading initial ramdisk...". This, unfortunately, won't create a single log file or crash dump, which makes error reporting hard, to say the least. System info: Laptop model: Lenovo ideapad 330S-15ARR CPU: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx x8 GPU: AMD Radeon Vega 8 Graphics RAM: 12GB - 2400MHz Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Also, it is always necessary to add the "iommu=soft" command to the GRUB_CMDLINE_LINUX_DEFAULT line on /etc/default/grub, because no kernels will boot without it (this is an older issue). Even with this command, Kernel 5.19.X will always crash while loading the initial ramdisk. --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matheus1693 F wireplumber /dev/snd/controlC0: matheus1693 F wireplumber /dev/snd/seq:matheus1690 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-09-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) MachineType: LENOVO 81JQ Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=45a8c70a-d30e-4f97-ab4f-e761450b6302 ro quiet splash iommu=soft rcu_nocbs=0-7 processor.max_cstate=1 nopti pti=off amdgpu.gpu_recovery=1 ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 clocksource=hpet amd_iommu=on amdgpu.dc=1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220819.git8413c63c-0ubuntu2 Tags: kinetic wayland-session Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2019 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.ec.firmware.release: 1.38 dmi.modalias: dmi:bvnLENOVO:bvr7WCN38WW:bd11/04/2019:br1.38:efr1.38:svnLENOVO:pn81JQ:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR:skuLENOVO_MT_81JQ_BU_idea_FM_ideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81JQ dmi.product.sku: LENOVO_MT_81JQ_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990068/+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 1971712] Re: Add support for Intel DG2
well not exactly, oem-6.0 will not get DG2 support.. -- 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/1971712 Title: Add support for Intel DG2 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Confirmed Status in mesa source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip firmare: updates to i915 DMC, GuC [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971712/+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 1997151] Re: The channels for the microphones does not have enough volume.
** Description changed: -- 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/1997151 Title: The channels for the microphones does not have enough volume. Status in linux package in Ubuntu: Confirmed Bug description: With the program Audacity, the missing gain can be estimated to about 1000 (30dB). It does not matter whether the internal microphone, a microphone on the headset via the jack plug or a USB microphone is used. In the audio system settings a inactiv "Card Renoir Radeon High Definition Audio Controller" is shown. Ubuntu 5.15.0-53.59-generic 5.15.64 https://linux-hardware.org/?probe=124d4a2353 grep "Codec:" /proc/asound/card*/codec* /proc/asound/card0/codec#0:Codec: ATI R6xx HDMI /proc/asound/card1/codec#0:Codec: Realtek ALC236 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997151/+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 1993052] Re: iwlwifi Not valid error log pointer 0x00000000 causes WiFi to not work but bluetooth works
Note that usually, after 10 minutes or so, I'm able to fix this with `sudo modprobe -r iwlwifi && sudo modprobe -i iwlwifi`. Might be a hardware problem? Overheating? -- 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/1993052 Title: iwlwifi Not valid error log pointer 0x causes WiFi to not work but bluetooth works Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: For some reason, Ubuntu gets glitched where the Bluetooth works but WiFi does not even show up. If I reboot into Windows, it is a similar issue (wifi does not show up, but device manager shows Code 10. If I disable and enable the adaptor Intel Wireless AC 9560, it sometimes works and most times does not). After a few days, the issue goes away. Relevent info: Laptop: Asus ROG Strig-G 531GT Using newest bios 308 WiFi Adaptor: Intel Wireless AC 9560 As for wifi connection, usually wifi icon does not even show and stays that way throughout the whole uptime. If I reboot a couple of times, this may change. However, the wifi I connect to usually is WiFi 5 on 5G channel running WPA2. If I use my laptop outside my home, it connects to enterprise WiFi Here is the Intel firmware version [5.088777] kernel: iwlwifi :00:14.3: loaded firmware version 46.fae53a8b.0 9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm Here is the relevent Dmesg output [code] [ 10.661344] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x3, CPU2 Status: 0x234c [ 10.661361] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 10.909316] iwlwifi :00:14.3: Not valid error log pointer 0x for Init uCode [ 10.909348] iwlwifi :00:14.3: IML/ROM dump: [ 10.909349] iwlwifi :00:14.3: 0x | IML/ROM error/state [ 10.909382] iwlwifi :00:14.3: 0x0003 | IML/ROM data1 [ 10.909397] iwlwifi :00:14.3: Fseq Registers: [ 10.909406] iwlwifi :00:14.3: 0x6F1F6FFD | FSEQ_ERROR_CODE [ 10.909414] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION [ 10.909422] iwlwifi :00:14.3: 0xC5F8DD60 | FSEQ_CNVIO_INIT_VERSION [ 10.909431] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION [ 10.909438] iwlwifi :00:14.3: 0x5B3DBD40 | FSEQ_TOP_CONTENT_VERSION [ 10.909447] iwlwifi :00:14.3: 0x420E0021 | FSEQ_ALIVE_TOKEN [ 10.909456] iwlwifi :00:14.3: 0xDC0D7CE6 | FSEQ_CNVI_ID [ 10.909464] iwlwifi :00:14.3: 0x548306C4 | FSEQ_CNVR_ID [ 10.909472] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP [ 10.909483] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP [ 10.909494] iwlwifi :00:14.3: 0x485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [ 10.909535] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [ 10.909543] iwlwifi :00:14.3: Failed to start INIT ucode: -110 [ 10.909544] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 14.088686] iwlwifi :00:14.3: Failed to run INIT ucode: -110 [ 14.101296] iwlwifi :00:14.3: retry init count 1 [ 14.104445] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560 160MHz, REV=0x318 [ 14.112168] thermal thermal_zone6: failed to read out thermal zone (-61) [ 15.141330] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x3, CPU2 Status: 0x234c [ 15.141345] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 15.390252] iwlwifi :00:14.3: Not valid error log pointer 0x for Init uCode [ 15.390284] iwlwifi :00:14.3: IML/ROM dump: [ 15.390285] iwlwifi :00:14.3: 0x | IML/ROM error/state [ 15.390316] iwlwifi :00:14.3: 0x0003 | IML/ROM data1 [ 15.390332] iwlwifi :00:14.3: Fseq Registers: [ 15.390340] iwlwifi :00:14.3: 0x6F1F6FFD | FSEQ_ERROR_CODE [ 15.390348] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION [ 15.390357] iwlwifi :00:14.3: 0xC5F8DD60 | FSEQ_CNVIO_INIT_VERSION [ 15.390365] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION [ 15.390373] iwlwifi :00:14.3: 0x5B3DBD40 | FSEQ_TOP_CONTENT_VERSION [ 15.390382] iwlwifi :00:14.3: 0x420E0021 | FSEQ_ALIVE_TOKEN [ 15.390390] iwlwifi :00:14.3: 0xDC0D7CE6 | FSEQ_CNVI_ID [ 15.390398] iwlwifi :00:14.3: 0x548306C4 | FSEQ_CNVR_ID [ 15.390407] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP [ 15.390417] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP [ 15.390428] iwlwifi :00:14.3: 0x485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [ 15.390469] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [ 15.390477] iwlwifi :00:14.3: Failed to start INIT ucode: -110 [ 15.390480] iwlwifi :00:14.3: WRT: Collecting data: ini trigger
[Kernel-packages] [Bug 1993052] Re: iwlwifi Not valid error log pointer 0x00000000 causes WiFi to not work but bluetooth works
Same error here. Wireless-AC 9560 on MSI Stealth GS65 9SE, Ubuntu 22.04 with kernel 5.15.0-53-generic. -- 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/1993052 Title: iwlwifi Not valid error log pointer 0x causes WiFi to not work but bluetooth works Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: For some reason, Ubuntu gets glitched where the Bluetooth works but WiFi does not even show up. If I reboot into Windows, it is a similar issue (wifi does not show up, but device manager shows Code 10. If I disable and enable the adaptor Intel Wireless AC 9560, it sometimes works and most times does not). After a few days, the issue goes away. Relevent info: Laptop: Asus ROG Strig-G 531GT Using newest bios 308 WiFi Adaptor: Intel Wireless AC 9560 As for wifi connection, usually wifi icon does not even show and stays that way throughout the whole uptime. If I reboot a couple of times, this may change. However, the wifi I connect to usually is WiFi 5 on 5G channel running WPA2. If I use my laptop outside my home, it connects to enterprise WiFi Here is the Intel firmware version [5.088777] kernel: iwlwifi :00:14.3: loaded firmware version 46.fae53a8b.0 9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm Here is the relevent Dmesg output [code] [ 10.661344] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x3, CPU2 Status: 0x234c [ 10.661361] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 10.909316] iwlwifi :00:14.3: Not valid error log pointer 0x for Init uCode [ 10.909348] iwlwifi :00:14.3: IML/ROM dump: [ 10.909349] iwlwifi :00:14.3: 0x | IML/ROM error/state [ 10.909382] iwlwifi :00:14.3: 0x0003 | IML/ROM data1 [ 10.909397] iwlwifi :00:14.3: Fseq Registers: [ 10.909406] iwlwifi :00:14.3: 0x6F1F6FFD | FSEQ_ERROR_CODE [ 10.909414] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION [ 10.909422] iwlwifi :00:14.3: 0xC5F8DD60 | FSEQ_CNVIO_INIT_VERSION [ 10.909431] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION [ 10.909438] iwlwifi :00:14.3: 0x5B3DBD40 | FSEQ_TOP_CONTENT_VERSION [ 10.909447] iwlwifi :00:14.3: 0x420E0021 | FSEQ_ALIVE_TOKEN [ 10.909456] iwlwifi :00:14.3: 0xDC0D7CE6 | FSEQ_CNVI_ID [ 10.909464] iwlwifi :00:14.3: 0x548306C4 | FSEQ_CNVR_ID [ 10.909472] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP [ 10.909483] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP [ 10.909494] iwlwifi :00:14.3: 0x485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [ 10.909535] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [ 10.909543] iwlwifi :00:14.3: Failed to start INIT ucode: -110 [ 10.909544] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 14.088686] iwlwifi :00:14.3: Failed to run INIT ucode: -110 [ 14.101296] iwlwifi :00:14.3: retry init count 1 [ 14.104445] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560 160MHz, REV=0x318 [ 14.112168] thermal thermal_zone6: failed to read out thermal zone (-61) [ 15.141330] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x3, CPU2 Status: 0x234c [ 15.141345] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 15.390252] iwlwifi :00:14.3: Not valid error log pointer 0x for Init uCode [ 15.390284] iwlwifi :00:14.3: IML/ROM dump: [ 15.390285] iwlwifi :00:14.3: 0x | IML/ROM error/state [ 15.390316] iwlwifi :00:14.3: 0x0003 | IML/ROM data1 [ 15.390332] iwlwifi :00:14.3: Fseq Registers: [ 15.390340] iwlwifi :00:14.3: 0x6F1F6FFD | FSEQ_ERROR_CODE [ 15.390348] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION [ 15.390357] iwlwifi :00:14.3: 0xC5F8DD60 | FSEQ_CNVIO_INIT_VERSION [ 15.390365] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION [ 15.390373] iwlwifi :00:14.3: 0x5B3DBD40 | FSEQ_TOP_CONTENT_VERSION [ 15.390382] iwlwifi :00:14.3: 0x420E0021 | FSEQ_ALIVE_TOKEN [ 15.390390] iwlwifi :00:14.3: 0xDC0D7CE6 | FSEQ_CNVI_ID [ 15.390398] iwlwifi :00:14.3: 0x548306C4 | FSEQ_CNVR_ID [ 15.390407] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP [ 15.390417] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP [ 15.390428] iwlwifi :00:14.3: 0x485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [ 15.390469] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [ 15.390477] iwlwifi :00:14.3: Failed to start INIT ucode: -110 [ 15.390480] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [/code] ProblemType: Bug
[Kernel-packages] [Bug 1967274] Re: Screen sometimes can't update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
Yes the mutter fix got lost/regressed and so we are dependent on having just the kernel fix now. This is being tracked in bug 1985869. -- 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/1967274 Title: Screen sometimes can't update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found] Status in Mutter: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in mutter source package in Jammy: Fix Released Bug description: Screen can't turn back on by clicking keyboard after screen off by meta + l key. Try to do VT switch can make the screen back, some error poped when I try to wake up screen. gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 GsettingsChanges: b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'" b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.privacy' b'report-technical-problems' b'true' InstallationDate: Installed on 2022-03-31 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 Tags: wayland-session jammy third-party-packages Uname: Linux 5.15.0-23-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu 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 lxd plugdev sambashare sudo _MarkForUpload: True == SRU Justification [Impact] The backlight power won't come back after the meta + l to turn off the display on ADL machines. [Fix] Below series of commits from v5.17 fix this issue 1c7ab5affa5e drm/i915/xelpd: Add Pipe Color Lut caps to platform config 17815f624a90 drm/i915/xelpd: Enable Pipe Degamma e83c18cffaed drm/i915/xelpd: Enable Pipe color support for D13 platform [Test] Verified on at least 2 different machines, the backlight is on after the screen dimmed with touchpad movement or key stroke. [Where problems could occcur] The patches only affect ADL-P and up. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1967274/+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 1963767] Re: [jammy] Microphone not working after suspend
Bug confirmed with a Logitech BRIO on 22.04 and 22.10. Though the bug does not occur with my laptops' built-in mics. ** Summary changed: - [jammy] Microphone not working after suspend + Logitech BRIO microphone not working after suspend ** No longer affects: pulseaudio (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kinetic suspend-resume -- 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/1963767 Title: Logitech BRIO microphone not working after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+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 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
'nvidia-wayland' means a bug only happens on Wayland, which this does not. We use the 'wayland' tag to indicate that a bug can occur on Wayland, which was already done in comment #9. ** Tags removed: nvidia-wayland -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: New Status in Mutter: Fix Released Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte
[Kernel-packages] [Bug 1991664] Update Released
The verification of the Stable Release Update for dkms has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1991664 Title: backport dkms fixes to build modules correctly for hwe-5.19+ kernels with custom compiler Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in v4l2loopback package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in backport-iwlwifi-dkms source package in Jammy: New Status in dkms source package in Jammy: Fix Released Status in linux source package in Jammy: Incomplete Status in v4l2loopback source package in Jammy: New Status in zfs-linux source package in Jammy: New Bug description: [ Impact ] * hwe-5.19 kernel has to be compiled with gcc-12+ for the new security kernel config options that have been enabled in that kernel (init zero structs). * dkms needs to be patched to attempt to use the same compiler as was used to build the kernel, specifically use gcc for v5.15 but gcc-12 for v5.19+ in jammy * dkms autopkgtests also need to be improved to ensure there are no false negatives when kernel has module under test already built-in at the same version. * because linux-headers packages in Ubuntu do not depend on a toolchain, and it is very hard to correctly depend on a native or cross-toolchain, add gcc-12 dependency in the dkms package. [ Test Plan ] * Retrigger dkms module test for a built-in package of the same version as already built into the kernel, for example zfs-linux dkms. It should pass. * Attempt to build dkms modules against v5.15 kernel and v5.19 kernel from proposed. dkms module should be built with gcc and gcc-12 respectively. [ Where problems could occur ] * New gcc-12 dependency on the dkms package may result in two compilers being installed in the Ubuntu Desktop Live image * New gcc-12 dependency may prevent automatic upgrade/installation of the dkms package update via unattended upgrades. [ Other Info ] * It is questionable for dkms to depend on any c-compiler, given that a module for a given kernel can really be built with the same toolchain and the same compiler features. * In debian, linux kernel packages ship and extra configuration file in the kernel headers, dkms uses said configuration file to use a matching compiler, and linux-headers packages depend on the toolchain used to build a given kernel. Maybe in the future Ubuntu could consider using the same packaging. * Some DKMS modules need further fixes to preserve and not loose the compiler setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1991664/+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 1991664] Re: backport dkms fixes to build modules correctly for hwe-5.19+ kernels with custom compiler
This bug was fixed in the package dkms - 2.8.7-2ubuntu2.1 --- dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium * Cherry-pick patches from kinetic/stable to address building dkms modules correctly for HWE kernels (LP: #1991664): + Fix dkms-autopkgtest when a given dkms package is built into the kernel already of the same version. (i.e. zfs-linux on Ubuntu). + Use exact compiler for dkms as used to build the kernel, when possible. + Depend on gcc-12 to build modules for HWE kernels correctly. -- Dimitri John Ledkov Tue, 04 Oct 2022 13:25:35 +0100 ** Changed in: dkms (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1991664 Title: backport dkms fixes to build modules correctly for hwe-5.19+ kernels with custom compiler Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in v4l2loopback package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in backport-iwlwifi-dkms source package in Jammy: New Status in dkms source package in Jammy: Fix Released Status in linux source package in Jammy: Incomplete Status in v4l2loopback source package in Jammy: New Status in zfs-linux source package in Jammy: New Bug description: [ Impact ] * hwe-5.19 kernel has to be compiled with gcc-12+ for the new security kernel config options that have been enabled in that kernel (init zero structs). * dkms needs to be patched to attempt to use the same compiler as was used to build the kernel, specifically use gcc for v5.15 but gcc-12 for v5.19+ in jammy * dkms autopkgtests also need to be improved to ensure there are no false negatives when kernel has module under test already built-in at the same version. * because linux-headers packages in Ubuntu do not depend on a toolchain, and it is very hard to correctly depend on a native or cross-toolchain, add gcc-12 dependency in the dkms package. [ Test Plan ] * Retrigger dkms module test for a built-in package of the same version as already built into the kernel, for example zfs-linux dkms. It should pass. * Attempt to build dkms modules against v5.15 kernel and v5.19 kernel from proposed. dkms module should be built with gcc and gcc-12 respectively. [ Where problems could occur ] * New gcc-12 dependency on the dkms package may result in two compilers being installed in the Ubuntu Desktop Live image * New gcc-12 dependency may prevent automatic upgrade/installation of the dkms package update via unattended upgrades. [ Other Info ] * It is questionable for dkms to depend on any c-compiler, given that a module for a given kernel can really be built with the same toolchain and the same compiler features. * In debian, linux kernel packages ship and extra configuration file in the kernel headers, dkms uses said configuration file to use a matching compiler, and linux-headers packages depend on the toolchain used to build a given kernel. Maybe in the future Ubuntu could consider using the same packaging. * Some DKMS modules need further fixes to preserve and not loose the compiler setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1991664/+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 1992714] Re: [SRU] SoF for RPL platform support
This bug was fixed in the package firmware-sof - 2.0-1ubuntu4 --- firmware-sof (2.0-1ubuntu4) jammy; urgency=medium * Add RPL firmware to v2.0.x - Intel relased v2.2.2 firmware to support both adl and rpl, and the rpl firmware are just symbolic links to adl firmware. The new firmware are suggested to be used together with v5.18+ kernel, so to prevent current adl platforms from being impacted, copy the firmware for rpl only, and leave the adl firmware untouched. (LP: #1992714) -- Chia-Lin Kao (AceLan) Wed, 19 Oct 2022 23:59:05 +0800 ** Changed in: firmware-sof (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1992714 Title: [SRU] SoF for RPL platform support Status in HWE Next: Fix Released Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Released Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Fix Released Status in firmware-sof source package in Kinetic: Fix Released Status in linux source package in Kinetic: Incomplete Status in linux-oem-6.0 source package in Kinetic: Invalid Status in firmware-sof source package in Lunar: Fix Released Status in linux source package in Lunar: Incomplete Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] RPL platforms require new sof struct and firmware to enable its audio [Fix] Below 2 commits are from v6.1-rc1 63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions 5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake Firmware are from here https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2 [Test] Verified Dell machine which comes with rpl sdw audio. [Where problems could occur] Adding new struct, new ID, and new firmware, it won't affect old systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1992714/+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 1992714] Re: [SRU] SoF for RPL platform support
I know this is a bit of a special package, but please always include more information about the verification. Since I had some verification details for kinetic, but for jammy it was just a comment switching the tags - please always give some context on which versions have been used for verification etc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1992714 Title: [SRU] SoF for RPL platform support Status in HWE Next: Fix Released Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Released Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Fix Released Status in firmware-sof source package in Kinetic: Fix Released Status in linux source package in Kinetic: Incomplete Status in linux-oem-6.0 source package in Kinetic: Invalid Status in firmware-sof source package in Lunar: Fix Released Status in linux source package in Lunar: Incomplete Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] RPL platforms require new sof struct and firmware to enable its audio [Fix] Below 2 commits are from v6.1-rc1 63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions 5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake Firmware are from here https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2 [Test] Verified Dell machine which comes with rpl sdw audio. [Where problems could occur] Adding new struct, new ID, and new firmware, it won't affect old systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1992714/+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 1992714] Update Released
The verification of the Stable Release Update for firmware-sof has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1992714 Title: [SRU] SoF for RPL platform support Status in HWE Next: Fix Released Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Fix Released Status in firmware-sof source package in Kinetic: Fix Released Status in linux source package in Kinetic: Incomplete Status in linux-oem-6.0 source package in Kinetic: Invalid Status in firmware-sof source package in Lunar: Fix Released Status in linux source package in Lunar: Incomplete Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] RPL platforms require new sof struct and firmware to enable its audio [Fix] Below 2 commits are from v6.1-rc1 63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions 5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake Firmware are from here https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2 [Test] Verified Dell machine which comes with rpl sdw audio. [Where problems could occur] Adding new struct, new ID, and new firmware, it won't affect old systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1992714/+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 1992714] Re: [SRU] SoF for RPL platform support
This bug was fixed in the package firmware-sof - 2.1.1-1ubuntu1.1 --- firmware-sof (2.1.1-1ubuntu1.1) kinetic; urgency=medium * Add RPL firmware to v2.1.x - Intel relased v2.2.2 firmware to support both adl and rpl, and the rpl firmware are just symbolic links to adl firmware. The new firmware are suggested to be used together with v5.18+ kernel, so to prevent current adl platforms from being impacted, copy the firmware for rpl only, and leave the adl firmware untouched. (LP: #1992714) -- Chia-Lin Kao (AceLan) Mon, 24 Oct 2022 16:02:09 +0800 ** Changed in: firmware-sof (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1992714 Title: [SRU] SoF for RPL platform support Status in HWE Next: Fix Released Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Fix Released Status in firmware-sof source package in Kinetic: Fix Released Status in linux source package in Kinetic: Incomplete Status in linux-oem-6.0 source package in Kinetic: Invalid Status in firmware-sof source package in Lunar: Fix Released Status in linux source package in Lunar: Incomplete Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] RPL platforms require new sof struct and firmware to enable its audio [Fix] Below 2 commits are from v6.1-rc1 63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions 5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake Firmware are from here https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2 [Test] Verified Dell machine which comes with rpl sdw audio. [Where problems could occur] Adding new struct, new ID, and new firmware, it won't affect old systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1992714/+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 1997213] 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 1997213 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/1997213 Title: [Lenovo Ubuntu 22.04 Bug]SATA disk couldn't be recognized by "lsblk" after hot add Status in linux package in Ubuntu: Incomplete Bug description: Description: After installing Ubuntu 22.04 and boot to OS, we try to hot add a SATA disk to the Onboard AHCI controller in our system by plugging a SATA disk into the SATA slot, However, the OS can not recognize the added disks, both running command "lsblk" and "lsscsi", even "ll /sys/class/block/" couldn't find these disks we added before, and there isn't any log show up in /var/log/syslog after adding this SATA disks. Produce Steps: 1. Install Ubunut 22.04 (kernel 5.15.0-25.25-generic) 2. Boot into OS 3. Hot plug a SATA disk into SATA slot in the front bay 4. wait and observe whether the disks are show up by command "lsblk" Configuration: Systems:Lenovo SR655, AMD GENOA platform OS:ubuntu-22.04-live-server-amd64.iso CPU:AMD EPYC 9654 96-Core Processor *1 Memory:Hynix 32GB 2RX8 DDR5-4800 16Gbit RDIMM M-Die *12 storage: 7MM Drive 0-1:7.68TB 7MM NVMe SSD(PN:MTFDKCB7T6TFR,FW:E2MU110) Drive 0:240GB SATA SSD (PN:SSS7B07725 ,FW:MQ31) Drive 1-2:1.92TB NVMe SSD(PN:SSDPF2KX019T1O,FW:9CV10320) Drive 3-4:400GB NVMe SSD(PN:SSDPF21Q400GB,FW:L0310600) Drive 5-8:12.0TB SATA HDD(PN:01GV193,FW:LEGNK9R5) Drive 9:240GB SATA SSD(PN:SSS7B07725,FW:MQ31) Drive 10-11:960GB SATA SSD(PN:SSS7A43198,FW:MP33) Expected results: OS can recognize the SATA disks we hot added in. Actual results: OS cannot recognize SATA disks we hot added in. Additional info: 1. Hot add more SATA disks to different slot, "lsblk" couldn't show up the added disks as well. 2. Other OS like RHEL9.0 can recognize this hot added disks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997213/+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 1997213] Re: [Lenovo Ubuntu 22.04 Bug]SATA disk couldn't be recognized by "lsblk" after hot add
We'll update two actions listed as following 1. Update to latest kernel and have a try. 2. upload file that generated by command "sosreport" -- 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/1997213 Title: [Lenovo Ubuntu 22.04 Bug]SATA disk couldn't be recognized by "lsblk" after hot add Status in linux package in Ubuntu: New Bug description: Description: After installing Ubuntu 22.04 and boot to OS, we try to hot add a SATA disk to the Onboard AHCI controller in our system by plugging a SATA disk into the SATA slot, However, the OS can not recognize the added disks, both running command "lsblk" and "lsscsi", even "ll /sys/class/block/" couldn't find these disks we added before, and there isn't any log show up in /var/log/syslog after adding this SATA disks. Produce Steps: 1. Install Ubunut 22.04 (kernel 5.15.0-25.25-generic) 2. Boot into OS 3. Hot plug a SATA disk into SATA slot in the front bay 4. wait and observe whether the disks are show up by command "lsblk" Configuration: Systems:Lenovo SR655, AMD GENOA platform OS:ubuntu-22.04-live-server-amd64.iso CPU:AMD EPYC 9654 96-Core Processor *1 Memory:Hynix 32GB 2RX8 DDR5-4800 16Gbit RDIMM M-Die *12 storage: 7MM Drive 0-1:7.68TB 7MM NVMe SSD(PN:MTFDKCB7T6TFR,FW:E2MU110) Drive 0:240GB SATA SSD (PN:SSS7B07725 ,FW:MQ31) Drive 1-2:1.92TB NVMe SSD(PN:SSDPF2KX019T1O,FW:9CV10320) Drive 3-4:400GB NVMe SSD(PN:SSDPF21Q400GB,FW:L0310600) Drive 5-8:12.0TB SATA HDD(PN:01GV193,FW:LEGNK9R5) Drive 9:240GB SATA SSD(PN:SSS7B07725,FW:MQ31) Drive 10-11:960GB SATA SSD(PN:SSS7A43198,FW:MP33) Expected results: OS can recognize the SATA disks we hot added in. Actual results: OS cannot recognize SATA disks we hot added in. Additional info: 1. Hot add more SATA disks to different slot, "lsblk" couldn't show up the added disks as well. 2. Other OS like RHEL9.0 can recognize this hot added disks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997213/+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 1997213] [NEW] [Lenovo Ubuntu 22.04 Bug]SATA disk couldn't be recognized by "lsblk" after hot add
Public bug reported: Description: After installing Ubuntu 22.04 and boot to OS, we try to hot add a SATA disk to the Onboard AHCI controller in our system by plugging a SATA disk into the SATA slot, However, the OS can not recognize the added disks, both running command "lsblk" and "lsscsi", even "ll /sys/class/block/" couldn't find these disks we added before, and there isn't any log show up in /var/log/syslog after adding this SATA disks. Produce Steps: 1. Install Ubunut 22.04 (kernel 5.15.0-25.25-generic) 2. Boot into OS 3. Hot plug a SATA disk into SATA slot in the front bay 4. wait and observe whether the disks are show up by command "lsblk" Configuration: Systems:Lenovo SR655, AMD GENOA platform OS:ubuntu-22.04-live-server-amd64.iso CPU:AMD EPYC 9654 96-Core Processor *1 Memory:Hynix 32GB 2RX8 DDR5-4800 16Gbit RDIMM M-Die *12 storage: 7MM Drive 0-1:7.68TB 7MM NVMe SSD(PN:MTFDKCB7T6TFR,FW:E2MU110) Drive 0:240GB SATA SSD (PN:SSS7B07725 ,FW:MQ31) Drive 1-2:1.92TB NVMe SSD(PN:SSDPF2KX019T1O,FW:9CV10320) Drive 3-4:400GB NVMe SSD(PN:SSDPF21Q400GB,FW:L0310600) Drive 5-8:12.0TB SATA HDD(PN:01GV193,FW:LEGNK9R5) Drive 9:240GB SATA SSD(PN:SSS7B07725,FW:MQ31) Drive 10-11:960GB SATA SSD(PN:SSS7A43198,FW:MP33) Expected results: OS can recognize the SATA disks we hot added in. Actual results: OS cannot recognize SATA disks we hot added in. Additional info: 1. Hot add more SATA disks to different slot, "lsblk" couldn't show up the added disks as well. 2. Other OS like RHEL9.0 can recognize this hot added disks. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "This is the syslog that collected after hot add SATA disks" https://bugs.launchpad.net/bugs/1997213/+attachment/5631811/+files/syslog_after -- 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/1997213 Title: [Lenovo Ubuntu 22.04 Bug]SATA disk couldn't be recognized by "lsblk" after hot add Status in linux package in Ubuntu: New Bug description: Description: After installing Ubuntu 22.04 and boot to OS, we try to hot add a SATA disk to the Onboard AHCI controller in our system by plugging a SATA disk into the SATA slot, However, the OS can not recognize the added disks, both running command "lsblk" and "lsscsi", even "ll /sys/class/block/" couldn't find these disks we added before, and there isn't any log show up in /var/log/syslog after adding this SATA disks. Produce Steps: 1. Install Ubunut 22.04 (kernel 5.15.0-25.25-generic) 2. Boot into OS 3. Hot plug a SATA disk into SATA slot in the front bay 4. wait and observe whether the disks are show up by command "lsblk" Configuration: Systems:Lenovo SR655, AMD GENOA platform OS:ubuntu-22.04-live-server-amd64.iso CPU:AMD EPYC 9654 96-Core Processor *1 Memory:Hynix 32GB 2RX8 DDR5-4800 16Gbit RDIMM M-Die *12 storage: 7MM Drive 0-1:7.68TB 7MM NVMe SSD(PN:MTFDKCB7T6TFR,FW:E2MU110) Drive 0:240GB SATA SSD (PN:SSS7B07725 ,FW:MQ31) Drive 1-2:1.92TB NVMe SSD(PN:SSDPF2KX019T1O,FW:9CV10320) Drive 3-4:400GB NVMe SSD(PN:SSDPF21Q400GB,FW:L0310600) Drive 5-8:12.0TB SATA HDD(PN:01GV193,FW:LEGNK9R5) Drive 9:240GB SATA SSD(PN:SSS7B07725,FW:MQ31) Drive 10-11:960GB SATA SSD(PN:SSS7A43198,FW:MP33) Expected results: OS can recognize the SATA disks we hot added in. Actual results: OS cannot recognize SATA disks we hot added in. Additional info: 1. Hot add more SATA disks to different slot, "lsblk" couldn't show up the added disks as well. 2. Other OS like RHEL9.0 can recognize this hot added disks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997213/+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