[Kernel-packages] [Bug 1992409] [NEW] USB disk not detected at boot since 5.15.0-1015-raspi
Public bug reported: The RPI4 setup is composed by two USB disks running on Ubuntu desktop 22.04: - USB SSD containing the OS (ASM1153) - USB disk for the data, on its own power supply (ASM1051E) This setup worked fine the last months but since 5.15.0-1015-raspi the USB disk (data) is not recognized at boot (cool start or reboot). The same is valid with 5.15.0-1016-raspi. The disk is powered (power led) but not spinning so I simply need to disconnect/connect the USB cable or reset the power (of the disk) to make it works. Once the disk is recognized it runs w/o problem for days and even weeks (24/7 running setup). PS: I want to keep it in UASP mode Some details: lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 174c:1153 ASMedia Technology Inc. ASM1153 SATA 3Gb/s bridge Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- sudo dmesg|grep scsi [2.343664] scsi host0: uas [2.344714] scsi 0:0:0:0: Direct-Access Inateck ASM1153E 0 PQ: 0 ANSI: 6 [2.346284] sd 0:0:0:0: Attached scsi generic sg0 type 0 [2.354045] scsi host1: uas [2.355083] scsi 1:0:0:0: Direct-Access WDC WD60 EFRX-68MYMN1 0 PQ: 0 ANSI: 6 [2.356890] sd 1:0:0:0: Attached scsi generic sg1 type 0 -- sudo dmesg|grep usb [0.159937] usbcore: registered new interface driver usbfs [0.159986] usbcore: registered new interface driver hub [0.160042] usbcore: registered new device driver usb [0.729235] usbcore: registered new interface driver lan78xx [0.729288] usbcore: registered new interface driver smsc95xx [1.442961] usb_phy_generic phy: supply vcc not found, using dummy regulator [1.443112] usb_phy_generic phy: dummy supplies not allowed for exclusive requests [1.509268] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15 [1.509285] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.509291] usb usb1: Product: xHCI Host Controller [1.509296] usb usb1: Manufacturer: Linux 5.15.0-1016-raspi xhci-hcd [1.509301] usb usb1: SerialNumber: :01:00.0 [1.511924] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.15 [1.511941] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.511946] usb usb2: Product: xHCI Host Controller [1.511952] usb usb2: Manufacturer: Linux 5.15.0-1016-raspi xhci-hcd [1.511956] usb usb2: SerialNumber: :01:00.0 [1.573196] dwc2 fe98.usb: supply vusb_d not found, using dummy regulator [1.573513] dwc2 fe98.usb: supply vusb_a not found, using dummy regulator [1.783600] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [1.783872] dwc2 fe98.usb: DWC OTG Controller [1.783892] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [1.783918] dwc2 fe98.usb: irq 20, io mem 0xfe98 [1.784066] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15 [1.784075] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.784080] usb usb3: Product: DWC OTG Controller [1.784086] usb usb3: Manufacturer: Linux 5.15.0-1016-raspi dwc2_hsotg [1.784091] usb usb3: SerialNumber: fe98.usb [1.847534] usb 1-1: new high-speed USB device number 2 using xhci_hcd [1.998154] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21 [1.998178] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [1.998191] usb 1-1: Product: USB2.0 Hub [2.123982] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd [2.145228] usb 2-1: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00 [2.145248] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [2.145260] usb 2-1: Product: ASM1153E [2.145272] usb 2-1: Manufacturer: Inateck [2.145282] usb 2-1: SerialNumber: 123456789716 [2.275970] usb 2-2: new SuperSpeed USB device number 3 using xhci_hcd [2.297226] usb 2-2: New USB device found, idVendor=174c, idProduct=1153, bcdDevice= 1.00 [2.297245] usb 2-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [2.297258] usb 2-2: Product: Ugreen Storage Device [2.297269] usb 2-2: Manufacturer: Ugreen [2.297279] usb 2-2: SerialNumber: 26A1EE838332 [2.335218] usbcore: registered new interface driver usb-storage [2.354544] usbcore: registered new interface driver uas ** Affects: linux-
Re: [Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
When is this going to be fixed and is there a work-around. I have tried both updating from 20.04 and direct installation of 22.04 and have found this problem preventing me from using 22.04 [it never boots]. I have two computers. One is a Dell with nvidia drivers [the perfect target machine to show this problem] - and it fails, but I also have a desktop I built myself that should not have problems [and obviously some having installed 22.04 do NOT have problems, but I do - and can not tell you what component is the problem [hardware or software]. Somewhere I read that making some spaces larger for the possible 'expansion' to not cause problems, but can not find it now with all of the many entries. I have spent MONTHS trying to install 22.04without success on either machine. I do not think you are correct that it only effects a small number of machines. Anyway, for those of us who it does, the problem is IMMENSE and total. On 03/08/2022 10:44, Julian Andres Klode wrote: > Yes, grub will be fixed eventually, but we are blocked by the security > update not being out yet. This is not a blocker for enabling upgrades to > 22.04.1, as it only affects a small number of systems and grub fixes > itself by using the previous kernel version if the new one fails. > -- 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 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 i
[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
** Changed in: kunpeng920/ubuntu-20.04-hwe Status: Fix Committed => Fix Released ** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv_genirq uio hisi_sec2 hisi_qm uacce authenc acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler hisi
[Kernel-packages] [Bug 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
Same problem here. After a amount of time (can be a day, can be 10 minutes) it starts spamming the `failed to init addr cam`. its the same: product: RTL8852AE 802.11ax PCIe Wireless Network Adapter 5.15.0-43-generic if more info is needed, please do ask! -- 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/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: Confirmed Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A3MZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A3MZ:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A3MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A3MZ dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/+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
Workaround: You can usually install Ubuntu on a drive in one machine and then move the drive into another machine. At least I think that's what I did on the affected machine with 22.04, which is why I never discovered this bug until 22.10 development started. -- 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 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 GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff #endif ``` If everything works as expected, then i386 should working good. If not lucky, based on “UEFI writers’ guide”[2], the i386 will get > 4GB memory region and never be able to access. [Other Info] * Upstream grub2 bug #61058 https://savannah.gnu.org/bugs/index.php?61058 * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320 * Test grubx64.efi: https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320 * Test source code: https://github.com/os369510/grub2/tree/lp1842320 * If you built the package,
[Kernel-packages] [Bug 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
Is there a workaround available for this? Eg, would connecting to network with cable and disable wifi remedy this? There is no rj45 on my machine so i have not been able to test this, but if it works I'll try to get the needed accessory to connect a cable. -- 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/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: Confirmed Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A3MZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A3MZ:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A3MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A3MZ dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/+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 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
SRU: https://lists.ubuntu.com/archives/kernel- team/2022-October/133872.html (linux-meta-hwe-5.15) ** Description changed: [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances of such failures vary from one to another. [Fix] A few solutions were considered. The very first one is to ask Intel to fix -64 firmware directly, and the answer is a solid no claimed -64 is not the planned production version of AX211. It's also possible to backport FW API from v5.16, but while iwlwifi FW API is more or less a black box to us and the new FW APIs also depends on updates on the wireless stack, this is going to be very risky and actually we had regressions before after such backports. The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on the effected platforms. This means oem-5.14 and its migration target, hwe-5.15 will not be able to drive this piece of hw flawlessly without backport-iwlwifi-dkms installed. However, while we need secureboot to be enabled on these platforms, backport-iwlwifi-dkms must also be signed somehow. There are two possible method to achieve this, too. One, to prebuild this dkms as zfs and v4l2loopback does. However, while backport-iwlwifi-dkms generates kernel modules with exactly the same name as the in-tree ones, when prebuilt, they'll be available directly from the linux-modules package and therefore overrides the in-tree ones always, turning the in-tree driver completely useless and risk the stability of all other generic installations. The second one is to build backport-iwlwifi-dkms as nvidia graphic drivers in the linux-restricted-modules source package. In this way, affected platforms may install the corresponding packages when needed without interfering others. However, l-r-m is for restricted modules that needs special care of redistribution of its binaries, and backport-iwlwifi-dkms is GPL licensed. Here a similar but simpler process in the main kernel tree is re-implemented. Two additional packages, linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package linux-modules-MODULE-FLAVOUR will be created. [Test Case] Test builds: ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb [Where problems could occur] The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails to build under this proposed process. Debdiff attached to the same bug. Different from nvidia packages built from l-r-m, the generated package names do not carry an additional short version string, e.g. nvidia-410, as there is no such necessity to build multiple versions of iwlwifi. The modules are installed to /lib/modules//kernel/iwlwifi, not iwlwifi-9858/. + == linux-meta-hwe-5.15 SRU == + + [Impact] + + To bring standalone dkms module builds to hwe-5.15 as well. + + [Fix] + + Same fix that has been applied to + Unstable/Kinetic/Jammy/OEM-6.0/OEM-5.14/HWE-5.19. + + [Test Case] + + This should generate meta packages: + * linux-modules-iwlwifi-generic-hwe-20.04 + * linux-modules-iwlwifi-generic-hwe-20.04-edge + * linux-modules-iwlwifi-oem-20.04 + * linux-modules-iwlwifi-oem-20.04d + + [Where problems could occur] + + This creates only the meta packages that are currently missing. No + function changes. + + [Other Info] + + While this has been ported to all other series in concern, only hwe-5.15 + is nominated for fix here. + + The patch titled "UBUNTU: [Packaging] skip standalone dkms modules for + virtual flavour" was not tagged with a BugLink line, but we'd need that + to skip generating linux-modules-foo meta packages for virtual flavour. + == backport-iwlwifi-dkms SRU == In order to be compiled with dkms-build in kernel source package, the kernel header dir will not be /lib/modules//build but a temporary directory. This change specifies KLIB_BUILD from dkms variable ${kernel_source_dir}. [backport-iwlwifi-dkms] Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has: MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver" ** Changed in: linux-meta-hwe-5.1
[Kernel-packages] [Bug 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
** No longer affects: linux-meta-oem (Ubuntu) ** No longer affects: linux-meta-oem (Ubuntu Focal) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1969434 Title: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Fix Released Status in linux-meta-hwe-5.15 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-meta source package in Focal: Invalid Status in linux-meta-hwe-5.15 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in backport-iwlwifi-dkms source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-meta source package in Jammy: Fix Released Status in linux-meta-hwe-5.15 source package in Jammy: Invalid Status in linux-meta-oem source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances of such failures vary from one to another. [Fix] A few solutions were considered. The very first one is to ask Intel to fix -64 firmware directly, and the answer is a solid no claimed -64 is not the planned production version of AX211. It's also possible to backport FW API from v5.16, but while iwlwifi FW API is more or less a black box to us and the new FW APIs also depends on updates on the wireless stack, this is going to be very risky and actually we had regressions before after such backports. The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on the effected platforms. This means oem-5.14 and its migration target, hwe-5.15 will not be able to drive this piece of hw flawlessly without backport-iwlwifi-dkms installed. However, while we need secureboot to be enabled on these platforms, backport-iwlwifi-dkms must also be signed somehow. There are two possible method to achieve this, too. One, to prebuild this dkms as zfs and v4l2loopback does. However, while backport-iwlwifi-dkms generates kernel modules with exactly the same name as the in-tree ones, when prebuilt, they'll be available directly from the linux-modules package and therefore overrides the in-tree ones always, turning the in-tree driver completely useless and risk the stability of all other generic installations. The second one is to build backport-iwlwifi-dkms as nvidia graphic drivers in the linux-restricted-modules source package. In this way, affected platforms may install the corresponding packages when needed without interfering others. However, l-r-m is for restricted modules that needs special care of redistribution of its binaries, and backport-iwlwifi-dkms is GPL licensed. Here a similar but simpler process in the main kernel tree is re-implemented. Two additional packages, linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package linux-modules-MODULE-FLAVOUR will be created. [Test Case] Test builds: ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb [Where problems could occur] The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails to build under this proposed process. Debdiff attached to the same bug. Different from nvidia packages built from l-r-m, the generated package names do not carry an additional short version string, e.g. nvidia-410, as there is no such necessity to build multiple versions of iwlwifi. The modules are installed to /lib/modules//kernel/iwlwifi, not iwlwifi-9858/. == linux-meta-hwe-5.15 SRU == [Impact] To bring standalone dkms module builds to hwe-5.15 as well. [Fix] Same fix that ha
[Kernel-packages] [Bug 1992432] [NEW] HDMI sleeps and can't be woken
Public bug reported: HDMI sleeps and can't be woken (sometimes) on Raspberry Pi 400: $ uname -a Linux pi400 5.19.0-1002-raspi #6-Ubuntu SMP PREEMPT Wed Sep 28 09:20:32 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Oct 11 16:28:55 pi400 kernel: vc4-drm gpu: [drm] *ERROR* flip_done timed out Oct 11 16:28:55 pi400 kernel: vc4-drm gpu: [drm] *ERROR* [CONNECTOR:32:HDMI-A-1] commit wait timed out Oct 11 16:29:05 pi400 kernel: vc4-drm gpu: [drm] *ERROR* flip_done timed out Oct 11 16:29:05 pi400 kernel: vc4-drm gpu: [drm] *ERROR* [PLANE:84:plane-3] commit wait timed out Oct 11 16:29:15 pi400 kernel: vc4-drm gpu: [drm] *ERROR* flip_done timed out Oct 11 16:29:15 pi400 kernel: vc4-drm gpu: [drm] *ERROR* [PLANE:307:plane-25] commit wait timed out Oct 11 16:29:25 pi400 kernel: vc4-drm gpu: [drm] *ERROR* flip_done timed out Oct 11 16:29:25 pi400 kernel: vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit Oct 11 16:29:35 pi400 kernel: vc4-drm gpu: [drm] *ERROR* [CRTC:94:crtc-3] flip_done timed out Oct 11 16:29:46 pi400 kernel: vc4-drm gpu: [drm] *ERROR* flip_done timed out Oct 11 16:29:46 pi400 kernel: vc4-drm gpu: [drm] *ERROR* [CRTC:94:crtc-3] commit wait timed out Oct 11 16:29:56 pi400 kernel: vc4-drm gpu: [drm] *ERROR* flip_done timed out Oct 11 16:29:56 pi400 kernel: vc4-drm gpu: [drm] *ERROR* [CONNECTOR:32:HDMI-A-1] commit wait timed out Oct 11 16:30:06 pi400 kernel: vc4-drm gpu: [drm] *ERROR* flip_done timed out Oct 11 16:30:06 pi400 kernel: vc4-drm gpu: [drm] *ERROR* [PLANE:84:plane-3] commit wait timed out Oct 11 16:30:16 pi400 kernel: vc4-drm gpu: [drm] *ERROR* flip_done timed out Oct 11 16:30:16 pi400 kernel: vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit Oct 11 16:30:27 pi400 kernel: vc4-drm gpu: [drm] *ERROR* [CRTC:94:crtc-3] flip_done timed out ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: kinetic raspi raspi-gfx ** Description changed: HDMI sleeps and can't be woken (sometimes) on Raspberry Pi 400: + + $ uname -a + Linux pi400 5.19.0-1002-raspi #6-Ubuntu SMP PREEMPT Wed Sep 28 09:20:32 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux + Oct 11 16:28:55 pi400 kernel: vc4-drm gpu: [drm] *ERROR* flip_done timed out Oct 11 16:28:55 pi400 kernel: vc4-drm gpu: [drm] *ERROR* [CONNECTOR:32:HDMI-A-1] commit wait timed out Oct 11 16:29:05 pi400 kernel: vc4-drm gpu: [drm] *ERROR* flip_done timed out Oct 11 16:29:05 pi400 kernel: vc4-drm gpu: [drm] *ERROR* [PLANE:84:plane-3] commit wait timed out Oct 11 16:29:15 pi400 kernel: vc4-drm gpu: [drm] *ERROR* flip_done timed out Oct 11 16:29:15 pi400 kernel: vc4-drm gpu: [drm] *ERROR* [PLANE:307:plane-25] commit wait timed out Oct 11 16:29:25 pi400 kernel: vc4-drm gpu: [drm] *ERROR* flip_done timed out Oct 11 16:29:25 pi400 kernel: vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit Oct 11 16:29:35 pi400 kernel: vc4-drm gpu: [drm] *ERROR* [CRTC:94:crtc-3] flip_done timed out Oct 11 16:29:46 pi400 kernel: vc4-drm gpu: [drm] *ERROR* flip_done timed out Oct 11 16:29:46 pi400 kernel: vc4-drm gpu: [drm] *ERROR* [CRTC:94:crtc-3] commit wait timed out Oct 11 16:29:56 pi400 kernel: vc4-drm gpu: [drm] *ERROR* flip_done timed out Oct 11 16:29:56 pi400 kernel: vc4-drm gpu: [drm] *ERROR* [CONNECTOR:32:HDMI-A-1] commit wait timed out Oct 11 16:30:06 pi400 kernel: vc4-drm gpu: [drm] *ERROR* flip_done timed out Oct 11 16:30:06 pi400 kernel: vc4-drm gpu: [drm] *ERROR* [PLANE:84:plane-3] commit wait timed out Oct 11 16:30:16 pi400 kernel: vc4-drm gpu: [drm] *ERROR* flip_done timed out Oct 11 16:30:16 pi400 kernel: vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit Oct 11 16:30:27 pi400 kernel: vc4-drm gpu: [drm] *ERROR* [CRTC:94:crtc-3] flip_done timed out -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1992432 Title: HDMI sleeps and can't be woken Status in linux-raspi package in Ubuntu: New Bug description: HDMI sleeps and can't be woken (sometimes) on Raspberry Pi 400: $ uname -a Linux pi400 5.19.0-1002-raspi #6-Ubuntu SMP PREEMPT Wed Sep 28 09:20:32 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Oct 11 16:28:55 pi400 kernel: vc4-drm gpu: [drm] *ERROR* flip_done timed out Oct 11 16:28:55 pi400 kernel: vc4-drm gpu: [drm] *ERROR* [CONNECTOR:32:HDMI-A-1] commit wait timed out Oct 11 16:29:05 pi400 kernel: vc4-drm gpu: [drm] *ERROR* flip_done timed out Oct 11 16:29:05 pi400 kernel: vc4-drm gpu: [drm] *ERROR* [PLANE:84:plane-3] commit wait timed out Oct 11 16:29:15 pi400 kernel: vc4-drm gpu: [drm] *ERROR* flip_done timed out Oct 11 16:29:15 pi400 kernel: vc4-drm gpu: [drm] *ERROR* [PLANE:307:plane-25] commit wait timed out Oct 11 16:29:25 pi400 kernel: vc4-drm gpu: [drm] *ERROR* flip_done timed out Oct 11 16:29:25 pi400 kernel: vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit Oct 11 16:29:35 pi400 kernel: vc4
[Kernel-packages] [Bug 1992435] [NEW] sof-hda-dsp Dmic0 not initial correctly
Public bug reported: [Impact] Device use sof-hda-dsp driver will not able to initial the Dmic0 status correctly [Test Plan] 1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service" 2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state" 3. reboot system 4. Dmic should be on and volume set to 70% [Where problems could occur] Only fix for Dmic0 control and upstream already merged the code. The risk will be low [Other Info] Pull Request in upstream https://github.com/alsa-project/alsa-ucm-conf/pull/132 ** Affects: oem-priority Importance: Undecided Assignee: Dirk Su (dirksu) Status: Confirmed ** Affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1992435 Title: sof-hda-dsp Dmic0 not initial correctly Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: New Bug description: [Impact] Device use sof-hda-dsp driver will not able to initial the Dmic0 status correctly [Test Plan] 1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service" 2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state" 3. reboot system 4. Dmic should be on and volume set to 70% [Where problems could occur] Only fix for Dmic0 control and upstream already merged the code. The risk will be low [Other Info] Pull Request in upstream https://github.com/alsa-project/alsa-ucm-conf/pull/132 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1992435/+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 1992435] Re: sof-hda-dsp Dmic0 not initial correctly
debdiff for jammy ** Patch added: "alsa-ucm-conf_1.2.6.3-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1992435/+attachment/5622937/+files/alsa-ucm-conf_1.2.6.3-1ubuntu2.debdiff ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Dirk Su (dirksu) ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1992435 Title: sof-hda-dsp Dmic0 not initial correctly Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: New Bug description: [Impact] Device use sof-hda-dsp driver will not able to initial the Dmic0 status correctly [Test Plan] 1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service" 2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state" 3. reboot system 4. Dmic should be on and volume set to 70% [Where problems could occur] Only fix for Dmic0 control and upstream already merged the code. The risk will be low [Other Info] Pull Request in upstream https://github.com/alsa-project/alsa-ucm-conf/pull/132 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1992435/+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 1992435] Re: sof-hda-dsp Dmic0 not initial correctly
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1992435 Title: sof-hda-dsp Dmic0 not initial correctly Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: New Bug description: [Impact] Device use sof-hda-dsp driver will not able to initial the Dmic0 status correctly [Test Plan] 1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service" 2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state" 3. reboot system 4. Dmic should be on and volume set to 70% [Where problems could occur] Only fix for Dmic0 control and upstream already merged the code. The risk will be low [Other Info] Pull Request in upstream https://github.com/alsa-project/alsa-ucm-conf/pull/132 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1992435/+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 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
** No longer affects: linux-meta-oem (Ubuntu Jammy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1969434 Title: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Fix Released Status in linux-meta-hwe-5.15 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-meta source package in Focal: Invalid Status in linux-meta-hwe-5.15 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in backport-iwlwifi-dkms source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-meta source package in Jammy: Fix Released Status in linux-meta-hwe-5.15 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances of such failures vary from one to another. [Fix] A few solutions were considered. The very first one is to ask Intel to fix -64 firmware directly, and the answer is a solid no claimed -64 is not the planned production version of AX211. It's also possible to backport FW API from v5.16, but while iwlwifi FW API is more or less a black box to us and the new FW APIs also depends on updates on the wireless stack, this is going to be very risky and actually we had regressions before after such backports. The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on the effected platforms. This means oem-5.14 and its migration target, hwe-5.15 will not be able to drive this piece of hw flawlessly without backport-iwlwifi-dkms installed. However, while we need secureboot to be enabled on these platforms, backport-iwlwifi-dkms must also be signed somehow. There are two possible method to achieve this, too. One, to prebuild this dkms as zfs and v4l2loopback does. However, while backport-iwlwifi-dkms generates kernel modules with exactly the same name as the in-tree ones, when prebuilt, they'll be available directly from the linux-modules package and therefore overrides the in-tree ones always, turning the in-tree driver completely useless and risk the stability of all other generic installations. The second one is to build backport-iwlwifi-dkms as nvidia graphic drivers in the linux-restricted-modules source package. In this way, affected platforms may install the corresponding packages when needed without interfering others. However, l-r-m is for restricted modules that needs special care of redistribution of its binaries, and backport-iwlwifi-dkms is GPL licensed. Here a similar but simpler process in the main kernel tree is re-implemented. Two additional packages, linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package linux-modules-MODULE-FLAVOUR will be created. [Test Case] Test builds: ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb [Where problems could occur] The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails to build under this proposed process. Debdiff attached to the same bug. Different from nvidia packages built from l-r-m, the generated package names do not carry an additional short version string, e.g. nvidia-410, as there is no such necessity to build multiple versions of iwlwifi. The modules are installed to /lib/modules//kernel/iwlwifi, not iwlwifi-9858/. == linux-meta-hwe-5.15 SRU == [Impact] To bring standalone dkms module builds to hwe-5.15 as well. [Fix] Same fix that has been applied to Unstable/Kinetic/Jammy/OEM-6.0/OEM-5.14/HWE-5.19. [Test Case] This should generate me
[Kernel-packages] [Bug 1991608] Re: TEE Support for CCP driver
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress -- 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/1991608 Title: TEE Support for CCP driver Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] Missing support for of AMD Secure Processor device for PCI ID 0x14CA. [Fix] A patch is being proposed in upstream and CC-ed stable. [Test Case] Without a proper fix, following error appears in dmesg: ccp :02:00.5: tee: missing driver data ccp :02:00.5: tee initialization failed [Where problems could occur] This adds a new driver data entry to support ccp device that provides both sev and tee feature at the same time. [Other Info] While this is proposed to stable 5.15+, all kernels >= 5.15 are nominated for fix. == original bug description == Client and datacenter Zen4 SOC same PCI-ID but offer different functionality from the PSP. Genoa offers SEV, Client part offers TEE. This patch fixes an ERR level message and CCP driver functionality not working. ccp :02:00.5: tee: missing driver data ccp :02:00.5: tee initialization failed https://lore.kernel.org/linux- crypto/20220928184506.13981-1-mario.limoncie...@amd.com/T/#m1b933ea4b961d17cb1be5be74e2d22a860507ca0 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1991608/+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 1992212] Re: nouveau pmu: firmware unavailable gp107
** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware (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/1992212 Title: nouveau pmu: firmware unavailable gp107 Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Incomplete Bug description: /lib/firmware/nvidia/gp107 /lib/firmware/nvidia/gp107/acr /lib/firmware/nvidia/gp107/gr /lib/firmware/nvidia/gp107/gr/fecs_bl.bin /lib/firmware/nvidia/gp107/gr/fecs_data.bin /lib/firmware/nvidia/gp107/gr/fecs_inst.bin /lib/firmware/nvidia/gp107/gr/fecs_sig.bin /lib/firmware/nvidia/gp107/gr/gpccs_bl.bin /lib/firmware/nvidia/gp107/gr/gpccs_data.bin /lib/firmware/nvidia/gp107/gr/gpccs_inst.bin /lib/firmware/nvidia/gp107/gr/gpccs_sig.bin /lib/firmware/nvidia/gp107/gr/sw_ctx.bin /lib/firmware/nvidia/gp107/gr/sw_nonctx.bin /lib/firmware/nvidia/gp107/nvdec /lib/firmware/nvidia/gp107/sec2 /lib/firmware/nvidia/gp107/acr/bl.bin /lib/firmware/nvidia/gp107/acr/ucode_load.bin /lib/firmware/nvidia/gp107/acr/ucode_unload.bin /lib/firmware/nvidia/gp107/acr/unload_bl.bin /lib/firmware/nvidia/gp107/gr/sw_bundle_init.bin /lib/firmware/nvidia/gp107/gr/sw_method_init.bin /lib/firmware/nvidia/gp107/nvdec/scrubber.bin /lib/firmware/nvidia/gp107/sec2/desc-1.bin /lib/firmware/nvidia/gp107/sec2/desc.bin /lib/firmware/nvidia/gp107/sec2/image-1.bin /lib/firmware/nvidia/gp107/sec2/image.bin /lib/firmware/nvidia/gp107/sec2/sig-1.bin /lib/firmware/nvidia/gp107/sec2/sig.bin Package: linux-firmware Status: install ok installed Priority: optional Section: misc Installed-Size: 846721 Maintainer: Ubuntu Kernel Team Architecture: all Multi-Arch: foreign Version: 20220329.git681281e4-0ubuntu3.5 Replaces: atmel-firmware, linux-firmware-snapdragon (<= 1.2-0ubuntu1), linux-res tricted-common Provides: atmel-firmware Recommends: firmware-sof-signed Breaks: linux-firmware-raspi2 (<= 1.20190819-0ubuntu2), linux-firmware-snapdrago n (<= 1.2-0ubuntu1) Conflicts: atmel-firmware Description: Firmware for Linux kernel drivers This package provides firmware used by Linux kernel drivers. Oct 8 08:49:44 fx504 kernel: [2.659551] MXM: GUID detected in BIOS Oct 8 08:49:44 fx504 kernel: [2.660477] ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210730/ns arguments-61) Oct 8 08:49:44 fx504 kernel: [2.661646] ACPI Warning: \_SB.PCI0.PEG0.PEGP._ DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (202107 30/nsarguments-61) Oct 8 08:49:44 fx504 kernel: [2.663101] pci :01:00.0: optimus capabilit ies: enabled, status dynamic power, hda bios codec supported Oct 8 08:49:44 fx504 kernel: [2.664016] VGA switcheroo: detected Optimus DS M method \_SB_.PCI0.PEG0.PEGP handle Oct 8 08:49:44 fx504 kernel: [2.664940] nouveau :01:00.0: enabling devi ce (0006 -> 0007) Oct 8 08:49:44 fx504 kernel: [2.665979] checking generic (8000 7e9000) vs hw (a300 100) Oct 8 08:49:44 fx504 kernel: [2.665981] checking generic (8000 7e9000) vs hw (9000 1000) Oct 8 08:49:44 fx504 kernel: [2.665982] checking generic (8000 7e9000) vs hw (a000 200) Oct 8 08:49:44 fx504 kernel: [2.666029] nouveau :01:00.0: NVIDIA GP107 (137000a1) Oct 8 08:49:44 fx504 kernel: [2.680631] checking generic (8000 7e9000) vs hw (a200 100) Oct 8 08:49:44 fx504 kernel: [2.680632] checking generic (8000 7e9000) vs hw (8000 1000) Oct 8 08:49:44 fx504 kernel: [2.746655] nouveau :01:00.0: bios: version 86.07.50.00.59 Oct 8 08:49:44 fx504 kernel: [2.747754] nouveau :01:00.0: pmu: firmware unavailable Oct 8 08:49:44 fx504 kernel: [2.755349] i915 :00:02.0: [drm] [ENCODER:1 02:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it Oct 8 08:49:44 fx504 kernel: [2.803611] nouveau :01:00.0: fb: 4096 MiB GDDR5 Oct 8 08:49:44 fx504 kernel: [3.132263] [drm] Initialized i915 1.6.0 202011 03 for :00:02.0 on minor 0 Oct 8 08:49:44 fx504 kernel: [3.139712] ACPI: video: Video Device [GFX0] (m ulti-head: yes rom: no post: no) Oct 8 08:49:44 fx504 kernel: [3.139759] nouveau :01:00.0: DRM: VRAM: 40 96 MiB Oct 8 08:49:44 fx504 kernel: [3.139763] nouveau :01:00.0: DRM: GART: 53 6870912 MiB Oct 8 08:49:44 fx504 kernel: [3.139766] nouveau :01:00.0: DRM: BIT tabl e 'A' not found Oct 8 08:49:44 fx504 kernel: [3.139768] nouveau :01:00.0: DRM: BIT tabl e 'L' not found Oct 8 08:49:44 fx504 kernel: [3.139770] nouveau :01:00.0: DRM:
[Kernel-packages] [Bug 1992194] Re: random CSR_RESET errors in iwlwifi appear under kinetic
** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: 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/1992194 Title: random CSR_RESET errors in iwlwifi appear under kinetic Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: A Gigabyte GC-WBAX210 WIFI 6E Aorus PCI card worked fine under Ubuntu 22.04 LTS but under Ubuntu 22.10 fails to initialize properly half of the time. When this occurs, the kern.log shows... Oct 2 10:59:26 howarth-X570-UD kernel: [5.581395] iwlwifi :05:00.0: CSR_RESET = 0x10 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581410] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x0 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581427] iwlwifi :05:00.0: value [iter 0]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581443] iwlwifi :05:00.0: value [iter 1]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581459] iwlwifi :05:00.0: value [iter 2]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581474] iwlwifi :05:00.0: value [iter 3]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581490] iwlwifi :05:00.0: value [iter 4]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581505] iwlwifi :05:00.0: value [iter 5]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581521] iwlwifi :05:00.0: value [iter 6]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581537] iwlwifi :05:00.0: value [iter 7]: 0x3f7d0830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581552] iwlwifi :05:00.0: value [iter 8]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581568] iwlwifi :05:00.0: value [iter 9]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581583] iwlwifi :05:00.0: value [iter 10]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581599] iwlwifi :05:00.0: value [iter 11]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581614] iwlwifi :05:00.0: value [iter 12]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581630] iwlwifi :05:00.0: value [iter 13]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581646] iwlwifi :05:00.0: value [iter 14]: 0x3f7d0c30 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581659] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x1 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581675] iwlwifi :05:00.0: value [iter 0]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581691] iwlwifi :05:00.0: value [iter 1]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581706] iwlwifi :05:00.0: value [iter 2]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581722] iwlwifi :05:00.0: value [iter 3]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581737] iwlwifi :05:00.0: value [iter 4]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581753] iwlwifi :05:00.0: value [iter 5]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581768] iwlwifi :05:00.0: value [iter 6]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581784] iwlwifi :05:00.0: value [iter 7]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581799] iwlwifi :05:00.0: value [iter 8]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581815] iwlwifi :05:00.0: value [iter 9]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581830] iwlwifi :05:00.0: value [iter 10]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581845] iwlwifi :05:00.0: value [iter 11]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581861] iwlwifi :05:00.0: value [iter 12]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581877] iwlwifi :05:00.0: value [iter 13]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581893] iwlwifi :05:00.0: value [iter 14]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581906] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x6 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581922] iwlwifi :05:00.0: value [iter 0]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581938] iwlwifi :05:00.0: value [iter 1]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581953] iwlwifi :05:00.0: value [iter 2]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581969] iwlwifi :05:00.0: value [iter 3]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581984] iwlwifi :05:00.0: value [iter 4]: 0xb00c7c75 Oct 2 10:59:26 howarth-
[Kernel-packages] [Bug 1992230] Re: APU Packages missing in Kernel too long boot
These files seem to be missing in the linux-firmware package. ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Jammy) 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/1992230 Title: APU Packages missing in Kernel too long boot Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Confirmed Bug description: Error in new 15 Kernel by a brandnew installed Linux without any programs installed. kemie@kemie-853-opz623:~$ sudo update-initramfs -u [sudo] password for kemie: update-initramfs: Generating /boot/initrd.img-5.15.0-48-generic W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vangogh_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu I: The initramfs will attempt to resume from /dev/sdb4 I: (UUID=579e79cb-4822-44ee-881b-e27ac58e5d0c) I: Set the RESUME variable to override this. System: Kernel: 5.15.0-27-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: Cinnamon 5.4.12 tk: GTK 3.24.33 wm: Mutter dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Desktop Mobo: Micro-Star model: MPG B550 GAMING PLUS (MS-7C56) v: 1.0 serial: UEFI: American Megatrends LLC. v: 1.A0 date: 05/21/2022 CPU: Info: 8-core model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64 type: MT MCP arch: Zen 3 rev: 0 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB Speed (MHz): avg: 2411 high: 2994 min/max: 1400/4672 boost: disabled cores: 1: 2770 2: 2394 3: 2395 4: 2395 5: 2394 6: 2992 7: 2392 8: 1953 9: 1397 10: 1397 11: 2676 12: 2487 13: 2561 14: 2993 15: 2994 16: 2394 bogomips: 121368 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] driver: nouveau v: kernel pcie: speed: 2.5 GT/s lanes: 8 ports: active: HDMI-A-1 empty: DP-1,DVI-D-1 bus-ID: 10:00.0 chip-ID: 10de:1c82 Device-2: AMD Cezanne driver: amdgpu v: kernel pcie: speed: 8 GT/s lanes: 16 ports: active: none empty: DP-2,DP-3,HDMI-A-2 bus-ID: 30:00.0 chip-ID: 1002:1638 Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: amdgpu,ati,modesetting unloaded: fbdev,vesa gpu: nouveau display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: HDMI-1 mapped: HDMI-A-1 model: L236VA res: 1920x1080 dpi: 94 diag: 598mm (23.5") OpenGL: renderer: NV137 v: 4.3 Mesa 22.0.5 direct render: Yes Audio: Device-1: NVIDIA GP107GL High Definition Audio driver: snd_hda_intel v: kernel pcie: speed: 2.5 GT/s lanes: 8 bus-ID: 10:00.1 chip-ID: 10de:0fb9 Device-2: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 30:00.1 chip-ID: 1002:1637 Device-3: AMD Family 17h HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 30:00.6 chip-ID: 1022:15e3 Sound Server-1: ALSA v: k5.15.0-27-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Network: Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 21:00.0 chip-ID: 8086:2725 IF: wlp33s0 state: down m
[Kernel-packages] [Bug 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
@Göran: I tried https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/comments/13 , so far so good, but sometimes I get days without this bug triggering, so I'm not yet sure it works perfectly -- 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/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: Confirmed Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A3MZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A3MZ:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A3MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A3MZ dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/+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 1951861] Re: Fix non-working e1000e device after resume
adding Intel team in this bug for a common topic It is also referring to the other bug #1990215 where intel team suggested to take all following patches https://bugs.launchpad.net/somerville/+bug/1990215/comments/15 related patches: e1000e: Additional PHY power saving in S0ix https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/intel/e1000e?id=3ad3e28cb203309fb29022dea41cd65df0583632 e1000e: Add polling mechanism to indicate CSME DPG exit https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/intel/e1000e?id=ef407b86d3cc7ab7ad37658c1c7a094cb8f3b6b4 e1000e: Add handshake with the CSME to support S0ix https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/intel/e1000e?id=3e55d231716ea361b1520b801c6778c4c48de102 The solution applied in this bug was to *revert* the second commit #e1000e: Add polling mechanism to indicate CSME DPG exit In case of re-applying the second patch, this bug #1951861 would break again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1951861 Title: Fix non-working e1000e device after resume Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Released Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] e1000e devices stop working after s2idle resume. [Fix] Revert the offending patch series, which is to bring some minor power saving. [Test] Vendor did extensive tests and didn't find any regression, and the power consumption remains the same. [Where problems could occur] Maybe on some system the series can save some energy, so reverting will cause some power consumption increase. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951861/+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 1991691] Re: cannot change mount namespace
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991691 Title: cannot change mount namespace Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Incomplete Bug description: Multiple snaps are either broken or "only" display permission denied messages. slack snap is not starting at all with: > update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied firefox snap does start, but also logs errors: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat /var/lib/snapd/hostfs/usr/share/doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat /var/lib/snapd/hostfs/usr/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat /usr/local/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat /var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Oct 4 17:29:01 2022 InstallationDate: Installed on 2017-09-26 (1834 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170924) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1991691/+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 1991691] Re: cannot change mount namespace
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991691 Title: cannot change mount namespace Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Incomplete Bug description: Multiple snaps are either broken or "only" display permission denied messages. slack snap is not starting at all with: > update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied firefox snap does start, but also logs errors: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat /var/lib/snapd/hostfs/usr/share/doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat /var/lib/snapd/hostfs/usr/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat /usr/local/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat /var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Oct 4 17:29:01 2022 InstallationDate: Installed on 2017-09-26 (1834 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170924) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1991691/+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 1991691] Re: cannot change mount namespace
There is an apparmor userspace update in flight as well can you confirm your apparmor version by adding the output of dpkg -l apparmor -- 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/1991691 Title: cannot change mount namespace Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Incomplete Bug description: Multiple snaps are either broken or "only" display permission denied messages. slack snap is not starting at all with: > update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied firefox snap does start, but also logs errors: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat /var/lib/snapd/hostfs/usr/share/doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat /var/lib/snapd/hostfs/usr/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat /usr/local/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat /var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Oct 4 17:29:01 2022 InstallationDate: Installed on 2017-09-26 (1834 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170924) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1991691/+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
Are there any plans for providing an i915 DKMS Module with DG2 Support for oem-5.17? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Released 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: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [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-oem-5.17/+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 1991691] Re: cannot change mount namespace
I am not the original author but it affects me too: apparmor 3.0.7-1ubuntu1 amd64user-space parser utility for AppArmor -- 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/1991691 Title: cannot change mount namespace Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Incomplete Bug description: Multiple snaps are either broken or "only" display permission denied messages. slack snap is not starting at all with: > update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied firefox snap does start, but also logs errors: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat /var/lib/snapd/hostfs/usr/share/doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat /var/lib/snapd/hostfs/usr/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat /usr/local/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat /var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Oct 4 17:29:01 2022 InstallationDate: Installed on 2017-09-26 (1834 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170924) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1991691/+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 1988989] Re: HDMI/DisplayPort over USB-C unstable since kernel 5.19 on Intel 12th Gen.
> Kernel 6.0 seems to have fixed it for me: > https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.0/amd64/ Not here, still 5.15 is the newest kernel that doesn't put the external screen into a frenzy. -- 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/1988989 Title: HDMI/DisplayPort over USB-C unstable since kernel 5.19 on Intel 12th Gen. Status in linux package in Ubuntu: Confirmed Bug description: Having upgraded to 5.19.0-15, my display connected over a USB-C → HDMI connection goes off and on multiple times a minute, rendering it unusable. Downgrading back to 5.15.0-27 makes it work again. I've bisected mainline kernels from https://kernel.ubuntu.com/~kernel- ppa/mainline/ to reach: v5.18.19 GOOD v5.19-rc3 BAD ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 7948 F wireplumber /dev/snd/controlC0: michal 7948 F wireplumber /dev/snd/seq:michal 7939 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 7 14:28:48 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-08-31 (6 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) MachineType: Framework Laptop (12th Gen Intel Core) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_zw6n2j@/vmlinuz-5.19.0-15-generic root=ZFS=rpool/ROOT/ubuntu_zw6n2j ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220831.gitd3c92280-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA42321000N dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988989/+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 1991691] Re: cannot change mount namespace
Thanks Alex and John for jumping in -- I did some investigation and I'm more and more persuaded that this is indeed a kernel (AppArmor bug). The good thing is that this is 100% reproducible by just installing the latest 22.10 daily images: firefox starts with warnings, and slack does not start at all. It's also true, as first suggested by Mathias, that booting with the kernel 5.19.0-18-generic makes the problem go away. Even with that kernel there are still error messages left, related to mkdir failing, but that is due to bug 1951210 which has been fixed with https://github.com/snapcore/snapd/pull/12127 (but the fix has not been released yet, hence we still see these errors). The errors which turns out to be fatal (for slack) are those mentioned by Andreas as he submitted the bug: > update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied The failure is on "lstat", which triggers the AppArmor's getattr permission. The audit logs with the latest kernel show a flood of denials on getattr, which disappear with the previous kernel version. Could it be that the latest kernel has changed something in the way that getattr is handled? I just found https://gitlab.com/apparmor/apparmor/-/issues/132 and I wonder if that code path has finally been enabled. ** Bug watch added: gitlab.com/apparmor/apparmor/-/issues #132 https://gitlab.com/apparmor/apparmor/-/issues/132 -- 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/1991691 Title: cannot change mount namespace Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Incomplete Bug description: Multiple snaps are either broken or "only" display permission denied messages. slack snap is not starting at all with: > update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied firefox snap does start, but also logs errors: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat /var/lib/snapd/hostfs/usr/share/doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat /var/lib/snapd/hostfs/usr/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat /usr/local/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat /var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: un
[Kernel-packages] [Bug 1991691] Re: cannot change mount namespace
So re: issue/132 that code path has always been enabled. How we have worked around it is by implicitly adding the GETATTR perm to the mapping. Their were significant changes around permission lookup and mapping but not around how/where the check is done, so I assume it is in the mapping code though at first glance it appears to be right. I am still digging. -- 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/1991691 Title: cannot change mount namespace Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Incomplete Bug description: Multiple snaps are either broken or "only" display permission denied messages. slack snap is not starting at all with: > update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied firefox snap does start, but also logs errors: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat /var/lib/snapd/hostfs/usr/share/doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat /var/lib/snapd/hostfs/usr/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat /usr/local/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat /var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Oct 4 17:29:01 2022 InstallationDate: Installed on 2017-09-26 (1834 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170924) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1991691/+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 1991691] Re: cannot change mount namespace
Sorry for not responding earlier. The logs already posted by others mirror what I have seen. The work-around for me is also to 5.19.0-18-generic (or rather 6.0.0-06.202210022231 from the mainline PPA). It feels like the problem might be related to the kernel change discussed in https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064 -- 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/1991691 Title: cannot change mount namespace Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Incomplete Bug description: Multiple snaps are either broken or "only" display permission denied messages. slack snap is not starting at all with: > update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied firefox snap does start, but also logs errors: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat /var/lib/snapd/hostfs/usr/share/doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat /var/lib/snapd/hostfs/usr/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat /usr/local/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat /var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Oct 4 17:29:01 2022 InstallationDate: Installed on 2017-09-26 (1834 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170924) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1991691/+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 1986965] Re: 12th gen intel PC can't boot with kernel upper than the pre-installed
Bug still here with the 5.15.0-50, must boot by selecting the oldest one in grub. I only have a secured machine because I have suscribed to Livepatch who will do the job every time i reboot on the old kernel (aka every reboot) If you need more logs or info, just ping me ** Summary changed: - 12th gen intel PC can't boot with kernel 5.15.0-46 + 12th gen intel PC can't boot with kernel upper than the pre-installed -- 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/1986965 Title: 12th gen intel PC can't boot with kernel upper than the pre-installed Status in linux package in Ubuntu: Confirmed Bug description: Hi, Ubuntu 22.04 LTS here. I don't know if it is a bug directly linked to linux kernel but: Before my July holidays, PC booted fine, in less than 3sec, when I came back in august, there were some updates to install, including new kernel 5.15.0-46. After installing, I never was able to boot on it. - PC boot - GRUB will load - default select lastest kernel (5.15.0-46) - [see 1st attached PNG] a few line of log appears (same on working boot) - [see 2nd attached PNG] then default boot screen "MSI + ubuntu logo" appears, but "long time" - [see 3rd attached PNG] then [ OK ] linux boot log got displayed and stay on same line for few moment too. I guess that's the attached image that show the most important stuff. - [see 4th attached PNG] then black screen with top left corner with the white blinky cursor - CTRL+ALT+DEL to reboot To use my PC I have to choose additional ubuntu options and select 5.15.0-41 in grub. Using this option allow to boot normaly, and got livepatch applying an update at every reboot (so if it apply the -46, it works during live patch, but sadly not on hard reboot. Do you need more info/logs ? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_15_0_41_44_generic_88 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 18 16:18:56 2022 InstallationDate: Installed on 2022-04-29 (111 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7D25 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6e1766db-1fb6-4255-9258-a7a4c4a1f70d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2021 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.00 dmi.board.asset.tag: Default string dmi.board.name: PRO Z690-A DDR4(MS-7D25) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.00:bd09/14/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-ADDR4(MS-7D25):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D25 dmi.product.sku: Default string 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/1986965/+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 1991691] Re: cannot change mount namespace
This is not related to the change in lp1990064. If it was you would see log messages similar to apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=21323 comm="steamwebhelper" requested="userns_create" denied="userns_create" which we are not seeing. We are seeing a huge jump in getattr log messages and that will be related to a different change. -- 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/1991691 Title: cannot change mount namespace Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Incomplete Bug description: Multiple snaps are either broken or "only" display permission denied messages. slack snap is not starting at all with: > update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied firefox snap does start, but also logs errors: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat /var/lib/snapd/hostfs/usr/share/doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat /var/lib/snapd/hostfs/usr/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat /usr/local/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat /var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Oct 4 17:29:01 2022 InstallationDate: Installed on 2017-09-26 (1834 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170924) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1991691/+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 1690085]
Thanks for the information shared. Keep updating blogs regularly. If you have time visit https://www.jaisuntourism.com/ ">Best tour operator in Coimbatore -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https:/
[Kernel-packages] [Bug 1992435] Re: sof-hda-dsp Dmic0 not initial correctly
The attachment "alsa-ucm-conf_1.2.6.3-1ubuntu2.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1992435 Title: sof-hda-dsp Dmic0 not initial correctly Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: New Bug description: [Impact] Device use sof-hda-dsp driver will not able to initial the Dmic0 status correctly [Test Plan] 1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service" 2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state" 3. reboot system 4. Dmic should be on and volume set to 70% [Where problems could occur] Only fix for Dmic0 control and upstream already merged the code. The risk will be low [Other Info] Pull Request in upstream https://github.com/alsa-project/alsa-ucm-conf/pull/132 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1992435/+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 1992458] [NEW] Disable VMAP_STACK as it causes crash in EFI
*** This bug is a duplicate of bug 1967130 *** https://bugs.launchpad.net/bugs/1967130 Public bug reported: [ Impact ] The kernel crashes when trying to access the EFI runtime services/variables if the kernel is configured with CONFIG_VMAP_STACK. Indeed, to access EFI variables/services, the kernel switches to the EFI page table which is created during the boot process *but* is never updated during the life of the kernel: as CONFIG_VMAP_STACK allocates the kernel stack in the vmalloc region and maps it in the *kernel page table*, the EFI page table never has this new mapping and then segfaults when trying to access the kernel stack of the current process. This is easier to reproduce on the Unmatched than on QEMU (never reproduced on this platform): ubuntu@ubuntu:~$ cat /sys/firmware/efi/efivars/* Which gives rise to a kernel crash, gdb traces below: (gdb) bt #0 handle_exception () at /home/alex/work/linux/arch/riscv/kernel/entry.S:27 #1 0x8080741a in efi_virtmap_load () at /home/alex/work/linux/arch/riscv/include/asm/current.h:31 #2 0x in ?? () (gdb) p/x $stval $1 = 0xffc8946cbc38 (gdb) display /i $sepc 1: x/i $sepc 0x8000392c :sd ra,8(sp) (gdb) p/x $sp $6 = 0xffc8946cbc30 A workaround can be to disable CONFIG_VMAP_STACK but actually any mapping in the kernel page table that is not also added to the EFI page table can cause such crash: but I'm not sure this can happen and this workaround was enough in the previous release to fix this bug and to be able to live install a system. I advise to implement this workaround for now as I'm implementing the proper patch which consists in updating the EFI page table before switching to it, just like x86 does. [ Test Plan ] Use a kernel with CONFIG_VMAP_STACK disabled and simply enter the following command, preferably on the Unmatched: ubuntu@ubuntu:~$ cat /sys/firmware/efi/efivars/* This should not trigger a crash. [ Where problems could occur ] As said above, just disabling CONFIG_VMAP_STACK may not be enough. ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1967130 rcu_sched detected stalls on CPUs/tasks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1992458 Title: Disable VMAP_STACK as it causes crash in EFI Status in linux-riscv package in Ubuntu: New Bug description: [ Impact ] The kernel crashes when trying to access the EFI runtime services/variables if the kernel is configured with CONFIG_VMAP_STACK. Indeed, to access EFI variables/services, the kernel switches to the EFI page table which is created during the boot process *but* is never updated during the life of the kernel: as CONFIG_VMAP_STACK allocates the kernel stack in the vmalloc region and maps it in the *kernel page table*, the EFI page table never has this new mapping and then segfaults when trying to access the kernel stack of the current process. This is easier to reproduce on the Unmatched than on QEMU (never reproduced on this platform): ubuntu@ubuntu:~$ cat /sys/firmware/efi/efivars/* Which gives rise to a kernel crash, gdb traces below: (gdb) bt #0 handle_exception () at /home/alex/work/linux/arch/riscv/kernel/entry.S:27 #1 0x8080741a in efi_virtmap_load () at /home/alex/work/linux/arch/riscv/include/asm/current.h:31 #2 0x in ?? () (gdb) p/x $stval $1 = 0xffc8946cbc38 (gdb) display /i $sepc 1: x/i $sepc 0x8000392c : sd ra,8(sp) (gdb) p/x $sp $6 = 0xffc8946cbc30 A workaround can be to disable CONFIG_VMAP_STACK but actually any mapping in the kernel page table that is not also added to the EFI page table can cause such crash: but I'm not sure this can happen and this workaround was enough in the previous release to fix this bug and to be able to live install a system. I advise to implement this workaround for now as I'm implementing the proper patch which consists in updating the EFI page table before switching to it, just like x86 does. [ Test Plan ] Use a kernel with CONFIG_VMAP_STACK disabled and simply enter the following command, preferably on the Unmatched: ubuntu@ubuntu:~$ cat /sys/firmware/efi/efivars/* This should not trigger a crash. [ Where problems could occur ] As said above, just disabling CONFIG_VMAP_STACK may not be enough. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1992458/+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 1970819] Re: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi
Hello, guys! There's any news about this subject? My Dell Vostro 5402 with intel Bluetooth intel/ibt-19-0-0.sfi is not working. There's something that I can help? Thanks a lot :) snap --version snap2.56.2-4.fc36 snapd 2.56.2-4.fc36 series 16 fedora 36 kernel 5.19.14-200.fc36.x86_64 $neofetch .',;;,'.tp@tp .';::;,.- .;cc;. OS: Fedora Linux 36 (Workstation Edition) x86_64 .:cc:. Host: Vostro 5402 .;c;.:dddl:.;ccc;. Kernel: 5.19.14-200.fc36.x86_64 .:c;OWMKOOXMWd;ccc:.Uptime: 24 mins .:c;KMMc;cc;xMMc:ccc:. Packages: 2343 (rpm), 19 (flatpak), 12 (snap) ,cc;MMM.;cc;;WW::, Shell: zsh 5.8.1 :cc;MMM.;: Resolution: 1920x1080 :ccc;oxOOOo;MMM0OOk.;: DE: GNOME 42.5 cc:0MMKxdd:;MMMkddc.;; WM: Mutter c:XM0';;MMM.;' WM Theme: Adwaita c;MMo;c;MMW.;ccc;Theme: Adwaita [GTK2/3] c;0MNc.ccc.xMMd:ccc; Icons: Adwaita [GTK2/3] cc;dNMWXXXWM0::cc:, Terminal: gnome-terminal ;.:odl:.;cc:,. CPU: 11th Gen Intel i7-1165G7 (8) @ 4.700GHz ::'. GPU: NVIDIA GeForce MX330 .:cc:;,..GPU: Intel TigerLake-LP GT2 [Iris Xe Graphics] '::cc::;,. Memory: 3357MiB / 15724MiB -- 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/1970819 Title: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi Status in linux package in Ubuntu: Fix Committed Status in snapd package in Ubuntu: Confirmed Status in Fedora: New Bug description: When testing the beta image for uc22 on an Intel NUC, I noticed that bluetooth was not working. This NUC has worked for bluetooth tests on uc18, 20, and even on jammy. However on uc22, we see this in dmesg: [ 11.954649] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 11.962817] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-17-16-1.sfi (-2) [ 11.966951] Bluetooth: hci0: Failed to read MSFT supported features (-56) Here's the full dmesg with grep -i blue: https://pastebin.canonical.com/p/99KvzHY4n9/ On Jammy, for comparison, the firmware gets loaded and bluetoothctl can see nearby devices: [5.650860] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.653214] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi [7.059104] Bluetooth: hci0: Waiting for firmware download to complete [7.059838] Bluetooth: hci0: Firmware loaded in 1373648 usecs [7.059903] Bluetooth: hci0: Waiting for device to boot [7.073886] Bluetooth: hci0: Device booted in 13691 usecs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970819/+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 1970819] Re: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: snapd (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/1970819 Title: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi Status in linux package in Ubuntu: Fix Committed Status in snapd package in Ubuntu: Confirmed Status in Fedora: New Bug description: When testing the beta image for uc22 on an Intel NUC, I noticed that bluetooth was not working. This NUC has worked for bluetooth tests on uc18, 20, and even on jammy. However on uc22, we see this in dmesg: [ 11.954649] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 11.962817] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-17-16-1.sfi (-2) [ 11.966951] Bluetooth: hci0: Failed to read MSFT supported features (-56) Here's the full dmesg with grep -i blue: https://pastebin.canonical.com/p/99KvzHY4n9/ On Jammy, for comparison, the firmware gets loaded and bluetoothctl can see nearby devices: [5.650860] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.653214] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi [7.059104] Bluetooth: hci0: Waiting for firmware download to complete [7.059838] Bluetooth: hci0: Firmware loaded in 1373648 usecs [7.059903] Bluetooth: hci0: Waiting for device to boot [7.073886] Bluetooth: hci0: Device booted in 13691 usecs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970819/+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 1970819] Re: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi
** Also affects: fedora Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970819 Title: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi Status in linux package in Ubuntu: Fix Committed Status in snapd package in Ubuntu: Confirmed Status in Fedora: New Bug description: When testing the beta image for uc22 on an Intel NUC, I noticed that bluetooth was not working. This NUC has worked for bluetooth tests on uc18, 20, and even on jammy. However on uc22, we see this in dmesg: [ 11.954649] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 11.962817] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-17-16-1.sfi (-2) [ 11.966951] Bluetooth: hci0: Failed to read MSFT supported features (-56) Here's the full dmesg with grep -i blue: https://pastebin.canonical.com/p/99KvzHY4n9/ On Jammy, for comparison, the firmware gets loaded and bluetoothctl can see nearby devices: [5.650860] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.653214] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi [7.059104] Bluetooth: hci0: Waiting for firmware download to complete [7.059838] Bluetooth: hci0: Firmware loaded in 1373648 usecs [7.059903] Bluetooth: hci0: Waiting for device to boot [7.073886] Bluetooth: hci0: Device booted in 13691 usecs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970819/+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 1991704] Re: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
** Changed in: linux (Ubuntu) Status: Triaged => 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/1991704 Title: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen Status in linux package in Ubuntu: Fix Committed Bug description: After today's Kinetic update my Framework laptop won't boot. The boot hangs after this output: [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci :00:07.1: DPC: RP PIO log size 8 is invalid [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci :00:07.3: DPC: RP PIO log size 0 is invalid [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst ead Falling back to 5.19.0-15-generic works. My Thinkpad X1 Carbon 6th gen does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik4014 F wireplumber /dev/snd/seq:jik4009 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 13:55:09 2022 InstallationDate: Installed on 2022-09-17 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Framework Laptop (12th Gen Intel Core) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA423350021 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+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 1967130] Re: rcu_sched detected stalls on CPUs/tasks
There is more information in LP: #1992458 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1967130 Title: rcu_sched detected stalls on CPUs/tasks Status in linux-riscv package in Ubuntu: Fix Released Bug description: When running the riscv64 live installer (https://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy- live-server-riscv64.iso) on the SiFive Unmatched board we reproducibly see rcu_sched stalls related to accessing the UEFI runtime: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451647] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451673] rcu: 3-...0: (3 GPs behind) idle=d03/1/0x4000 softirq=85648/85648 fqs=7326 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451698](detected by 0, t=15002 jiffies, g=155853, q=1286) Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451712] Task dump for CPU 3: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451720] task:kworker/u8:1 state:R running task stack:0 pid: 3715 ppid: 2 flags:0x0008 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451750] Workqueue: efi_rts_wq efi_call_rts Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451777] Call Trace: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451782] [] __schedule+0x226/0x644 uname -a: Linux ubuntu-server 5.15.0-1004-generic #4-Ubuntu SMP Wed Feb 9 18:17:33 UTC 2022 riscv64 riscv64 riscv64 GNU/Linux --- ProblemType: Bug Architecture: riscv64 DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.1004.4 PackageArchitecture: riscv64 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 Uname: Linux 5.15.0-1004-generic riscv64 UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967130/+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 1992467] [NEW] Screen Tearing
Public bug reported: Screen Tearing ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andre 1515 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 11 10:57:49 2022 InstallationDate: Installed on 2022-10-11 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Latitude 3490 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=UUID=7970276e-6642-48a8-af7d-02e8e109b252 ro quiet splash vt.handoff=7 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.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2022 dmi.bios.release: 1.21 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.0 dmi.board.name: 04HCMV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.0:bd08/15/2022:br1.21:svnDellInc.:pnLatitude3490:pvr:rvnDellInc.:rn04HCMV:rvrA01:cvnDellInc.:ct10:cvr:sku0839: dmi.product.family: Latitude dmi.product.name: Latitude 3490 dmi.product.sku: 0839 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992467 Title: Screen Tearing Status in linux package in Ubuntu: New Bug description: Screen Tearing ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andre 1515 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 11 10:57:49 2022 InstallationDate: Installed on 2022-10-11 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Latitude 3490 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=UUID=7970276e-6642-48a8-af7d-02e8e109b252 ro quiet splash vt.handoff=7 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.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2022 dmi.bios.release: 1.21 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.0 dmi.board.name: 04HCMV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.0:bd08/15/2022:br1.21:svnDellInc.:pnLatitude3490:pvr:rvnDellInc.:rn04HCMV:rvrA01:cvnDellInc.:ct10:cvr:sku0839: dmi.product.family: Latitude dmi.product.name: Latitude 3490 dmi.product.sku: 0839 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992467/+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 1991975] Re: dev file system is mounted without nosuid or noexec
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Dave Chiluk (chiluk) ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Dave Chiluk (chiluk) -- 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/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in linux source package in Focal: In Progress Status in systemd source package in Focal: Confirmed Status in linux source package in Jammy: In Progress Status in systemd source package in Jammy: Confirmed Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+subscriptions -- Maili
[Kernel-packages] [Bug 1992467] 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/1992467 Title: Screen Tearing Status in linux package in Ubuntu: Confirmed Bug description: Screen Tearing ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andre 1515 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 11 10:57:49 2022 InstallationDate: Installed on 2022-10-11 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Latitude 3490 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=UUID=7970276e-6642-48a8-af7d-02e8e109b252 ro quiet splash vt.handoff=7 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.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2022 dmi.bios.release: 1.21 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.0 dmi.board.name: 04HCMV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.0:bd08/15/2022:br1.21:svnDellInc.:pnLatitude3490:pvr:rvnDellInc.:rn04HCMV:rvrA01:cvnDellInc.:ct10:cvr:sku0839: dmi.product.family: Latitude dmi.product.name: Latitude 3490 dmi.product.sku: 0839 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992467/+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 1992474] [NEW] Flickering started right after install
Public bug reported: My computer is a Lenovo Thinkpad p-Series Gen 2 with Intel Core i9. I've tried updating my grub file as is suggested in Bugs #1970426, #1958191, and #1973676. That is, I've tried GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0 intel_idle.max_cstate=2" And, I've tried cstate=4. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moon 2093 F pulseaudio /dev/snd/controlC1: moon 2093 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 11 08:05:20 2022 InstallationDate: Installed on 2020-03-29 (926 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QTCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=39110848-f164-47a5-bf96-fda0216c46fb ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-20 (51 days ago) dmi.bios.date: 05/07/2020 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:br1.31:efr1.23:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QT_BU_Think_FM_ThinkPadP1Gen2: dmi.product.family: ThinkPad P1 Gen2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen2 dmi.product.version: ThinkPad P1 Gen2 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992474 Title: Flickering started right after install Status in linux package in Ubuntu: New Bug description: My computer is a Lenovo Thinkpad p-Series Gen 2 with Intel Core i9. I've tried updating my grub file as is suggested in Bugs #1970426, #1958191, and #1973676. That is, I've tried GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0 intel_idle.max_cstate=2" And, I've tried cstate=4. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moon 2093 F pulseaudio /dev/snd/controlC1: moon 2093 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 11 08:05:20 2022 InstallationDate: Installed on 2020-03-29 (926 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QTCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=39110848-f164-47a5-bf96-fda0216c46fb ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-20 (51 days ago) dmi.bios.date: 05/07/2020 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:br1.31:efr1.23:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0K1
[Kernel-packages] [Bug 1992474] 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/1992474 Title: Flickering started right after install Status in linux package in Ubuntu: Confirmed Bug description: My computer is a Lenovo Thinkpad p-Series Gen 2 with Intel Core i9. I've tried updating my grub file as is suggested in Bugs #1970426, #1958191, and #1973676. That is, I've tried GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0 intel_idle.max_cstate=2" And, I've tried cstate=4. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moon 2093 F pulseaudio /dev/snd/controlC1: moon 2093 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 11 08:05:20 2022 InstallationDate: Installed on 2020-03-29 (926 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QTCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=39110848-f164-47a5-bf96-fda0216c46fb ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-20 (51 days ago) dmi.bios.date: 05/07/2020 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:br1.31:efr1.23:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QT_BU_Think_FM_ThinkPadP1Gen2: dmi.product.family: ThinkPad P1 Gen2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen2 dmi.product.version: ThinkPad P1 Gen2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992474/+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 1990425] Re: Keyboard inoperative on Asus Vivobook S5402ZA
*** This bug is a duplicate of bug 1992266 *** https://bugs.launchpad.net/bugs/1992266 ** This bug has been marked a duplicate of bug 1992266 input/keyboard: the keyboard on some Asus laptops can't work -- 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/1990425 Title: Keyboard inoperative on Asus Vivobook S5402ZA Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: [Impact] * The builtin keyboard on the Asus S5402ZA doesn't work with any currently released kernel. [Fix] * 6e5cbe7c4b41824e500acbb42411da692d1435f1 ACPI: resource: Add ASUS model S5402ZA to quirks * https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux- pm.git/commit/?h=bleeding- edge&id=6e5cbe7c4b41824e500acbb42411da692d1435f1 * e12dee3736731e24b1e7367f87d66ac0fcd73ce7 ACPI: resource: Skip IRQ override on Asus Vivobook K3402ZA/K3502ZA * https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux- pm.git/commit/?h=bleeding- edge&id=e12dee3736731e24b1e7367f87d66ac0fcd73ce7 * These are from the upstream linux-pm tree, accepted for Linux 6.1, https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/ [Test Plan] * Install Ubuntu on an Asus S5402ZA and verify that the internal keyboard doesn't work. * Install kernel with the above patches. * Boot into patched kernel and verify that the internal keyboard now works. [Where problems could occur] * These patches could cause the keyboard to not work if there are differences in hardware/firmware revisions. [Other Info] * The patch requires e12dee3736731e24b1e7367f87d66ac0fcd73ce7 for the addition of the quirk mechanism. * e12dee373673 includes quirks for the Asus K3402ZA/K3502ZA models. These were tested and accepted by upstream. See bug below. * The patchset has been tested on an Asus S5402ZA with a test kernel and found to work. * Upstream bug tracker: https://bugzilla.kernel.org/show_bug.cgi?id=216158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990425/+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 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work
Marked LP#1990425 as a duplicate of this one, since the patches include that patch. -- 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/1992266 Title: input/keyboard: the keyboard on some Asus laptops can't work Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: This is upstream tracking bug: https://bugzilla.kernel.org/show_bug.cgi?id=216158 The bug originates from an upstream bug, and the ubuntu users request me to do a SRU to make the ubuntu linux work on their Asus laptops, so once the pathces are merge to mainline kernel, I start to prepare this SRU. [Impact] Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel will override to a new configuration for that IRQ, this will make the keyboard not work anymore under linux. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, test the keyboard, all regular keys could work. [Where problems could occur] The patches use the dmi table to match the machines, so only the matched Asus laptops will be impacted by the patches, if there is any regression, the regression only affects those matched Asus laptops, and the regression possibility is very low since ubuntu users already tested the patches on their own Asus laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992266/+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 1964093] Re: nfsver=3, udp not working anymore
I've encountered same problem after 22.04 upgrade. I want to mount shares from SPARCstation 10 based SunOS 4.1.4 system on the 22.04 system but cannot. It does work in the other direction, ie. I can mount 22.04 shares on the Sun. If you could confirm my understanding that recompiling the Kernel reconfiguration to remove the nfs-udp load block, I will not be able to do anything to restore the sunos nfs udp export loading on the 22.04 system, it would save me a lot of time messing with this. I understand from what you've written above that providing nfs udp service opens a security risk. -- 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/1964093 Title: nfsver=3,udp not working anymore Status in linux package in Ubuntu: Confirmed Bug description: Package: nfs-kernel-server Architecture: amd64 Version: 1:2.6.1-1~exp1ubuntu1 nfsversion 3 with proto udp seems not to be supported by the nfs- kernel-server anymore. In Ubuntu 18.04 (nfs-kernel-server 1:1.3.4-2.1ubuntu5) it was still possible. I could mount with either tcp or udp: 1. tcp mount -o nfsvers=3 192.168.0.1:/srv/nfs/testshare /mnt mount|grep mnt: 192.168.0.1:/srv/nfs/testshare on /mnt type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1) 2. udp mount -o nfsvers=3,udp 192.168.0.1:/srv/nfs/testshare /mnt mount|grep mnt: 192.168.0.1:/srv/nfs/testshare on /mnt type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1) Now in Ubuntu 22.04 I get the message: mount.nfs: an incorrect mount option was specified I tried to enable upd in /etc/nfs.conf in section [nfsd]: [nfsd] # debug=0 # threads=8 # host= # port=0 # grace-time=90 # lease-time=90 # udp=n udp=y # tcp=y # vers2=n # vers3=y But there was no effect. nfs3 with udp is needed by several busybox mount binaries in initrds of Knoppix and other live distributions used via PXE boot. Best regards Jörg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964093/+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 1992484] [NEW] Kernel regression openjdk on riscv64
Public bug reported: Over at https://lore.kernel.org/linux- riscv/Yz80ewHKTPI5Rvuz@spud/T/#ebde47064434d4ca4807b4abb8eb39898c48a8de2 it is reported that 2139619bcad7ac44cc8f6f749089120594056613 regresses userspace (openjdk) on riscv64. This commit has already been released in v6.0 kernel upstream, but has also been included in the stable patch series all the way back to v4.19.y There is a proposed fix for this at https://lore.kernel.org/linux- riscv/20220915193702.2201018-1-abres...@rivosinc.com/ which has not yet been merged upstream or in stable series. Please review and merge above proposed fix, or please revert 2139619bcad7ac44cc8f6f749089120594056613 to stop the regression spreading to all the distributions. ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1992484 Title: Kernel regression openjdk on riscv64 Status in linux package in Ubuntu: Incomplete Bug description: Over at https://lore.kernel.org/linux- riscv/Yz80ewHKTPI5Rvuz@spud/T/#ebde47064434d4ca4807b4abb8eb39898c48a8de2 it is reported that 2139619bcad7ac44cc8f6f749089120594056613 regresses userspace (openjdk) on riscv64. This commit has already been released in v6.0 kernel upstream, but has also been included in the stable patch series all the way back to v4.19.y There is a proposed fix for this at https://lore.kernel.org/linux- riscv/20220915193702.2201018-1-abres...@rivosinc.com/ which has not yet been merged upstream or in stable series. Please review and merge above proposed fix, or please revert 2139619bcad7ac44cc8f6f749089120594056613 to stop the regression spreading to all the distributions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992484/+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 1992484] 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 1992484 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/1992484 Title: Kernel regression openjdk on riscv64 Status in linux package in Ubuntu: Incomplete Bug description: Over at https://lore.kernel.org/linux- riscv/Yz80ewHKTPI5Rvuz@spud/T/#ebde47064434d4ca4807b4abb8eb39898c48a8de2 it is reported that 2139619bcad7ac44cc8f6f749089120594056613 regresses userspace (openjdk) on riscv64. This commit has already been released in v6.0 kernel upstream, but has also been included in the stable patch series all the way back to v4.19.y There is a proposed fix for this at https://lore.kernel.org/linux- riscv/20220915193702.2201018-1-abres...@rivosinc.com/ which has not yet been merged upstream or in stable series. Please review and merge above proposed fix, or please revert 2139619bcad7ac44cc8f6f749089120594056613 to stop the regression spreading to all the distributions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992484/+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 1992484] Re: Kernel regresses openjdk on riscv64
** Summary changed: - Kernel regression openjdk on riscv64 + Kernel regresses openjdk on riscv64 -- 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/1992484 Title: Kernel regresses openjdk on riscv64 Status in linux package in Ubuntu: Incomplete Bug description: Over at https://lore.kernel.org/linux- riscv/Yz80ewHKTPI5Rvuz@spud/T/#ebde47064434d4ca4807b4abb8eb39898c48a8de2 it is reported that 2139619bcad7ac44cc8f6f749089120594056613 regresses userspace (openjdk) on riscv64. This commit has already been released in v6.0 kernel upstream, but has also been included in the stable patch series all the way back to v4.19.y There is a proposed fix for this at https://lore.kernel.org/linux- riscv/20220915193702.2201018-1-abres...@rivosinc.com/ which has not yet been merged upstream or in stable series. Please review and merge above proposed fix, or please revert 2139619bcad7ac44cc8f6f749089120594056613 to stop the regression spreading to all the distributions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992484/+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
not in ubuntu archive -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Released 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: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [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-oem-5.17/+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 1971712] Re: Add support for Intel DG2
but you'll have an oem-6.0 with support built in later -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Released 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: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [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-oem-5.17/+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 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144
** Tags added: foundations-triage-discuss -- 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/1991285 Title: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux/5.4.0-128.144 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 1991691] Re: cannot change mount namespace
** Changed in: linux (Ubuntu) Milestone: None => ubuntu-22.10 ** Changed in: snapd (Ubuntu) Milestone: None => ubuntu-22.10 -- 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/1991691 Title: cannot change mount namespace Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Incomplete Bug description: Multiple snaps are either broken or "only" display permission denied messages. slack snap is not starting at all with: > update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied firefox snap does start, but also logs errors: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat /var/lib/snapd/hostfs/usr/share/doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat /var/lib/snapd/hostfs/usr/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat /usr/local/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat /var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Oct 4 17:29:01 2022 InstallationDate: Installed on 2017-09-26 (1834 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170924) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1991691/+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 1992518] [NEW] package linux-modules-5.15.0-50-generic (not installed) failed to install/upgrade: Neue Datei »/var/lib/dpkg/info/linux-modules-5.15.0-50-generic.list-new« kann n
Public bug reported: system error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-5.15.0-50-generic (not installed) ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andi 3480 F pulseaudio /dev/snd/controlC1: andi 3480 F pulseaudio CasperMD5CheckResult: unknown Date: Tue Oct 11 22:31:55 2022 DpkgTerminalLog: Vorbereitung zum Entpacken von .../0-linux-modules-5.15.0-50-generic_5.15.0-50.56_amd64.deb ... Entpacken von linux-modules-5.15.0-50-generic (5.15.0-50.56) ... dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-VRyuLA/0-linux-modules-5.15.0-50-generic_5.15.0-50.56_amd64.deb (--unpack): Neue Datei »/var/lib/dpkg/info/linux-modules-5.15.0-50-generic.list-new« kann nicht angelegt werden: Vorgang nicht zulässig ErrorMessage: Neue Datei »/var/lib/dpkg/info/linux-modules-5.15.0-50-generic.list-new« kann nicht angelegt werden: Vorgang nicht zulässig InstallationDate: Installed on 2020-01-25 (989 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Precision M6500 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=76342c9b-c354-4fb4-9195-fe5920a05ddc ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: linux Title: package linux-modules-5.15.0-50-generic (not installed) failed to install/upgrade: Neue Datei »/var/lib/dpkg/info/linux-modules-5.15.0-50-generic.list-new« kann nicht angelegt werden: Vorgang nicht zulässig UpgradeStatus: Upgraded to jammy on 2022-09-17 (24 days ago) dmi.bios.date: 06/04/2013 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/04/2013:br1.0:efr1.0:svnDellInc.:pnPrecisionM6500:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:sku: dmi.product.name: Precision M6500 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992518 Title: package linux-modules-5.15.0-50-generic (not installed) failed to install/upgrade: Neue Datei »/var/lib/dpkg/info/linux- modules-5.15.0-50-generic.list-new« kann nicht angelegt werden: Vorgang nicht zulässig Status in linux package in Ubuntu: New Bug description: system error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-5.15.0-50-generic (not installed) ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andi 3480 F pulseaudio /dev/snd/controlC1: andi 3480 F pulseaudio CasperMD5CheckResult: unknown Date: Tue Oct 11 22:31:55 2022 DpkgTerminalLog: Vorbereitung zum Entpacken von .../0-linux-modules-5.15.0-50-generic_5.15.0-50.56_amd64.deb ... Entpacken von linux-modules-5.15.0-50-generic (5.15.0-50.56) ... dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-VRyuLA/0-linux-modules-5.15.0-50-generic_5.15.0-50.56_amd64.deb (--unpack): Neue Datei »/var/lib/dpkg/info/linux-modules-5.15.0-50-generic.list-new« kann nicht angelegt werden: Vorgang nicht zulässig ErrorMessage: Neue Datei »/var/lib/dpkg/info/linux-modules-5.15.0-50-generic.list-new« kann nicht angelegt werden: Vorgang nicht zulässig InstallationDate: Installed on 2020-01-25 (989 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Precision M6500 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=76342c9b-c354-4fb4-9195-fe5920a05ddc ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7
[Kernel-packages] [Bug 1992517] [NEW] rtw88_8822ce: unable to ping anything, "failed to write TX skb to HCI" and "failed to pusk skb, ret -28" in dmesg
Public bug reported: I am able to associate with a SSID and receive an IP address, but when trying to ping anything, the ping fails and I get repeated messages in the syslog: Oct 11 22:32:29 Brutus kernel: [51072.191588] rtw_8822ce :03:00.0: failed to pusk skb, ret -28 Oct 11 22:32:30 Brutus kernel: [51073.215591] rtw_8822ce :03:00.0: failed to write TX skb to HCI Oct 11 22:32:30 Brutus kernel: [51073.215600] rtw_8822ce :03:00.0: failed to pusk skb, ret -28 Oct 11 22:32:31 Brutus kernel: [51074.119382] rtw_8822ce :03:00.0: failed to write TX skb to HCI They appear at the same rate as the ping is attempted. Ubuntu Kinetic (22.10), up-to-date as of October 11. Kernel 5.19.0-19-generic. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-19-generic 5.19.0-19.19 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kelner 4762 F wireplumber /dev/snd/seq:kelner 4758 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 11 22:28:26 2022 InstallationDate: Installed on 2020-09-12 (758 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP Pavilion Gaming Laptop 15-ec0xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=UUID=bc5eaf09-3825-4513-9cf6-b6e691ac42a6 ro quiet splash nogpumanager nvidia.NVreg_DynamicPowerManagement=0x02 intel_idle.max_cstate=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-06 (5 days ago) dmi.bios.date: 03/03/2022 dmi.bios.release: 15.13 dmi.bios.vendor: AMI dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86D6 dmi.board.vendor: HP dmi.board.version: 96.45 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 96.45 dmi.modalias: dmi:bvnAMI:bvrF.13:bd03/03/2022:br15.13:efr96.45:svnHP:pnHPPavilionGamingLaptop15-ec0xxx:pvr:rvnHP:rn86D6:rvr96.45:cvnHP:ct10:cvrChassisVersion:sku8BS92EA#AKD: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-ec0xxx dmi.product.sku: 8BS92EA#AKD dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1992517/+attachment/5623115/+files/version.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/1992517 Title: rtw88_8822ce: unable to ping anything, "failed to write TX skb to HCI" and "failed to pusk skb, ret -28" in dmesg Status in linux package in Ubuntu: New Bug description: I am able to associate with a SSID and receive an IP address, but when trying to ping anything, the ping fails and I get repeated messages in the syslog: Oct 11 22:32:29 Brutus kernel: [51072.191588] rtw_8822ce :03:00.0: failed to pusk skb, ret -28 Oct 11 22:32:30 Brutus kernel: [51073.215591] rtw_8822ce :03:00.0: failed to write TX skb to HCI Oct 11 22:32:30 Brutus kernel: [51073.215600] rtw_8822ce :03:00.0: failed to pusk skb, ret -28 Oct 11 22:32:31 Brutus kernel: [51074.119382] rtw_8822ce :03:00.0: failed to write TX skb to HCI They appear at the same rate as the ping is attempted. Ubuntu Kinetic (22.10), up-to-date as of October 11. Kernel 5.19.0-19-generic. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-19-generic 5.19.0-19.19 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kelner 4762 F wireplumber /dev/snd/seq:kelner 4758 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 11 22:28:26 2022 InstallationDate: Installed on 2020-09-12 (758 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP Pavilion Gaming Laptop 15-ec0xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=UUID=bc5eaf09-3825-4513-9cf6-b6e691ac42a6 ro quiet splash nogpuman
[Kernel-packages] [Bug 1992518] 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/1992518 Title: package linux-modules-5.15.0-50-generic (not installed) failed to install/upgrade: Neue Datei »/var/lib/dpkg/info/linux- modules-5.15.0-50-generic.list-new« kann nicht angelegt werden: Vorgang nicht zulässig Status in linux package in Ubuntu: Confirmed Bug description: system error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-5.15.0-50-generic (not installed) ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andi 3480 F pulseaudio /dev/snd/controlC1: andi 3480 F pulseaudio CasperMD5CheckResult: unknown Date: Tue Oct 11 22:31:55 2022 DpkgTerminalLog: Vorbereitung zum Entpacken von .../0-linux-modules-5.15.0-50-generic_5.15.0-50.56_amd64.deb ... Entpacken von linux-modules-5.15.0-50-generic (5.15.0-50.56) ... dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-VRyuLA/0-linux-modules-5.15.0-50-generic_5.15.0-50.56_amd64.deb (--unpack): Neue Datei »/var/lib/dpkg/info/linux-modules-5.15.0-50-generic.list-new« kann nicht angelegt werden: Vorgang nicht zulässig ErrorMessage: Neue Datei »/var/lib/dpkg/info/linux-modules-5.15.0-50-generic.list-new« kann nicht angelegt werden: Vorgang nicht zulässig InstallationDate: Installed on 2020-01-25 (989 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Precision M6500 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=76342c9b-c354-4fb4-9195-fe5920a05ddc ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: linux Title: package linux-modules-5.15.0-50-generic (not installed) failed to install/upgrade: Neue Datei »/var/lib/dpkg/info/linux-modules-5.15.0-50-generic.list-new« kann nicht angelegt werden: Vorgang nicht zulässig UpgradeStatus: Upgraded to jammy on 2022-09-17 (24 days ago) dmi.bios.date: 06/04/2013 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/04/2013:br1.0:efr1.0:svnDellInc.:pnPrecisionM6500:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:sku: dmi.product.name: Precision M6500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992518/+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 1992517] 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/1992517 Title: rtw88_8822ce: unable to ping anything, "failed to write TX skb to HCI" and "failed to pusk skb, ret -28" in dmesg Status in linux package in Ubuntu: Confirmed Bug description: I am able to associate with a SSID and receive an IP address, but when trying to ping anything, the ping fails and I get repeated messages in the syslog: Oct 11 22:32:29 Brutus kernel: [51072.191588] rtw_8822ce :03:00.0: failed to pusk skb, ret -28 Oct 11 22:32:30 Brutus kernel: [51073.215591] rtw_8822ce :03:00.0: failed to write TX skb to HCI Oct 11 22:32:30 Brutus kernel: [51073.215600] rtw_8822ce :03:00.0: failed to pusk skb, ret -28 Oct 11 22:32:31 Brutus kernel: [51074.119382] rtw_8822ce :03:00.0: failed to write TX skb to HCI They appear at the same rate as the ping is attempted. Ubuntu Kinetic (22.10), up-to-date as of October 11. Kernel 5.19.0-19-generic. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-19-generic 5.19.0-19.19 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kelner 4762 F wireplumber /dev/snd/seq:kelner 4758 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 11 22:28:26 2022 InstallationDate: Installed on 2020-09-12 (758 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP Pavilion Gaming Laptop 15-ec0xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=UUID=bc5eaf09-3825-4513-9cf6-b6e691ac42a6 ro quiet splash nogpumanager nvidia.NVreg_DynamicPowerManagement=0x02 intel_idle.max_cstate=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-06 (5 days ago) dmi.bios.date: 03/03/2022 dmi.bios.release: 15.13 dmi.bios.vendor: AMI dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86D6 dmi.board.vendor: HP dmi.board.version: 96.45 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 96.45 dmi.modalias: dmi:bvnAMI:bvrF.13:bd03/03/2022:br15.13:efr96.45:svnHP:pnHPPavilionGamingLaptop15-ec0xxx:pvr:rvnHP:rn86D6:rvr96.45:cvnHP:ct10:cvrChassisVersion:sku8BS92EA#AKD: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-ec0xxx dmi.product.sku: 8BS92EA#AKD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992517/+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 1992525] [NEW] Boot failure when not in recovery mode
Public bug reported: I just upgraded the kernel to 5.19.0-19 and can only boot in recovery mode. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-19-generic 5.19.0-19.19 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bdmurray 5525 F pipewire bdmurray 5528 F wireplumber /dev/snd/seq:bdmurray 5525 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 11 15:15:29 2022 InstallationDate: Installed on 2022-01-07 (277 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20XY0027US ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=UUID=c58ecc55-8765-4214-b495-303b0d3056b4 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-09-15 (26 days ago) dmi.bios.date: 09/06/2021 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET71W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrN32ET71W(1.47):bd09/06/2021:br1.47:efr1.29:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug kinetic -- 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/1992525 Title: Boot failure when not in recovery mode Status in linux package in Ubuntu: New Bug description: I just upgraded the kernel to 5.19.0-19 and can only boot in recovery mode. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-19-generic 5.19.0-19.19 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bdmurray 5525 F pipewire bdmurray 5528 F wireplumber /dev/snd/seq:bdmurray 5525 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 11 15:15:29 2022 InstallationDate: Installed on 2022-01-07 (277 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20XY0027US ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=UUID=c58ecc55-8765-4214-b495-303b0d3056b4 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-09-15 (26 days ago) dmi.bios.date: 09/06/2021 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET71W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrN32ET71W(1.47):bd09/06/2021:br1.47:efr1.29:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO To manage notif
[Kernel-packages] [Bug 1992525] Re: Boot failure when not in recovery mode
Here is a photo of where it hangs with quiet enabled. ** Attachment added: "IMG_20221011_145910.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992525/+attachment/5623203/+files/IMG_20221011_145910.jpg -- 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/1992525 Title: Boot failure when not in recovery mode Status in linux package in Ubuntu: Confirmed Bug description: I just upgraded the kernel to 5.19.0-19 and can only boot in recovery mode. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-19-generic 5.19.0-19.19 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bdmurray 5525 F pipewire bdmurray 5528 F wireplumber /dev/snd/seq:bdmurray 5525 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 11 15:15:29 2022 InstallationDate: Installed on 2022-01-07 (277 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20XY0027US ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=UUID=c58ecc55-8765-4214-b495-303b0d3056b4 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-09-15 (26 days ago) dmi.bios.date: 09/06/2021 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET71W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrN32ET71W(1.47):bd09/06/2021:br1.47:efr1.29:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992525/+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 1992525] Re: Boot failure when not in recovery mode
Here is a phot of where it hangs without quiet enabled. ** Attachment added: "IMG_20221011_145643.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992525/+attachment/5623204/+files/IMG_20221011_145643.jpg ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992525 Title: Boot failure when not in recovery mode Status in linux package in Ubuntu: Confirmed Bug description: I just upgraded the kernel to 5.19.0-19 and can only boot in recovery mode. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-19-generic 5.19.0-19.19 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bdmurray 5525 F pipewire bdmurray 5528 F wireplumber /dev/snd/seq:bdmurray 5525 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 11 15:15:29 2022 InstallationDate: Installed on 2022-01-07 (277 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20XY0027US ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=UUID=c58ecc55-8765-4214-b495-303b0d3056b4 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-09-15 (26 days ago) dmi.bios.date: 09/06/2021 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET71W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrN32ET71W(1.47):bd09/06/2021:br1.47:efr1.29:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992525/+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 1992525] 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/1992525 Title: Boot failure when not in recovery mode Status in linux package in Ubuntu: Confirmed Bug description: I just upgraded the kernel to 5.19.0-19 and can only boot in recovery mode. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-19-generic 5.19.0-19.19 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bdmurray 5525 F pipewire bdmurray 5528 F wireplumber /dev/snd/seq:bdmurray 5525 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 11 15:15:29 2022 InstallationDate: Installed on 2022-01-07 (277 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20XY0027US ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=UUID=c58ecc55-8765-4214-b495-303b0d3056b4 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-09-15 (26 days ago) dmi.bios.date: 09/06/2021 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET71W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrN32ET71W(1.47):bd09/06/2021:br1.47:efr1.29:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992525/+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 1992532] [NEW] Enable DG2 graphics support
Public bug reported: DG2 graphics support should be enabled by default, dmesg outputs the following: i915 :67:00.0: Your graphics device 56a5 is not properly supported by the driver in this kernel version. To force driver probe anyway, use i915.force_probe=56a5 module parameter or CONFIG_DRM_I915_FORCE_PROBE=56a5 configuration option, or (recommended) check for kernel updates. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-oem-22.04b 6.0.0.1005.5 ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0 Uname: Linux 6.0.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 12 01:29:02 2022 InstallationDate: Installed on 2022-10-11 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-oem-6.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy package-from-proposed ** Package changed: linux-meta-oem-6.0 (Ubuntu) => linux-oem-6.0 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1992532 Title: Enable DG2 graphics support Status in linux-oem-6.0 package in Ubuntu: New Bug description: DG2 graphics support should be enabled by default, dmesg outputs the following: i915 :67:00.0: Your graphics device 56a5 is not properly supported by the driver in this kernel version. To force driver probe anyway, use i915.force_probe=56a5 module parameter or CONFIG_DRM_I915_FORCE_PROBE=56a5 configuration option, or (recommended) check for kernel updates. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-oem-22.04b 6.0.0.1005.5 ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0 Uname: Linux 6.0.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 12 01:29:02 2022 InstallationDate: Installed on 2022-10-11 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-oem-6.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992532/+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 1992497] [NEW] 22.04 LTS: alsa-library + PulseAudio won't detect my USB sound card
You have been subscribed to a public bug: ALSA+Pulseaudio have always been difficult with USB Sound. In order to make it work under the best of circumstances, one would have to edit /etc/modprobe.d/alsa-base.conf And comment out any line that said options snd-usb-audio index=-2 Without commenting that out, PulseAudio cannot detect the card. Now, Ubuntu 22.04 LTS worked for a while with that change. Until Roughly the last week of September, 2022. A normal update got pushed which disabled my sound card. Alsa-lib version: 1.2.6.1 In /var/log/syslog: Oct 02 14:33:56 patchwork alsactl[1000]: alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -2 After two weeks of effort, and attempts to roll back to an earlier version of 22.04 LTS, I scrubbed the root partition and reverted to 20.04 LTS which works right. Samples of output from my exercise can be found here: https://ubuntuforums.org/showthread.php?t=2479484 Again, Xubuntu 22.04 LTS worked (after the alsa-base.conf edit) fine, Until the end of September update. The above thread on ubuntuforums.org has samples of lsusb, syslog, output from various ALSA utilities and PulseAudio utilities, brands and models of USB sound DACs tried, alsa-version output, and so on. If you need me to, I can build a throwaway system to get you any further information you want, but I'd rather not scrub a fully configured root partition *again* to go through this effort. linuxquestions.org showed that a search on "failed to open hw:1 use case configuration" or subsets of that phrase will show this bug. The tip of the ALSA development chain release notes for a while back shows no effort put forward to fixing this problem. What works is Alsa- lib version 1.2.2. ** Affects: alsa-lib (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- 22.04 LTS: alsa-library + PulseAudio won't detect my USB sound card https://bugs.launchpad.net/bugs/1992497 You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib 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 1992497] Re: 22.04 LTS: alsa-library + PulseAudio won't detect my USB sound card
Alsa-lib + Pulseaudio. Library version 1.2.6.1 ** Package changed: ubuntu => alsa-lib (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1992497 Title: 22.04 LTS: alsa-library + PulseAudio won't detect my USB sound card Status in alsa-lib package in Ubuntu: New Bug description: ALSA+Pulseaudio have always been difficult with USB Sound. In order to make it work under the best of circumstances, one would have to edit /etc/modprobe.d/alsa-base.conf And comment out any line that said options snd-usb-audio index=-2 Without commenting that out, PulseAudio cannot detect the card. Now, Ubuntu 22.04 LTS worked for a while with that change. Until Roughly the last week of September, 2022. A normal update got pushed which disabled my sound card. Alsa-lib version: 1.2.6.1 In /var/log/syslog: Oct 02 14:33:56 patchwork alsactl[1000]: alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -2 After two weeks of effort, and attempts to roll back to an earlier version of 22.04 LTS, I scrubbed the root partition and reverted to 20.04 LTS which works right. Samples of output from my exercise can be found here: https://ubuntuforums.org/showthread.php?t=2479484 Again, Xubuntu 22.04 LTS worked (after the alsa-base.conf edit) fine, Until the end of September update. The above thread on ubuntuforums.org has samples of lsusb, syslog, output from various ALSA utilities and PulseAudio utilities, brands and models of USB sound DACs tried, alsa-version output, and so on. If you need me to, I can build a throwaway system to get you any further information you want, but I'd rather not scrub a fully configured root partition *again* to go through this effort. linuxquestions.org showed that a search on "failed to open hw:1 use case configuration" or subsets of that phrase will show this bug. The tip of the ALSA development chain release notes for a while back shows no effort put forward to fixing this problem. What works is Alsa-lib version 1.2.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1992497/+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 1990342] Re: Intel EGS PCH tSATA RAID cannot be detected in Ubuntu20.04.5, Ubuntu 22.04 and Ubuntu 22.04.1
Both of those patches are in Kinetic. -- 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/1990342 Title: Intel EGS PCH tSATA RAID cannot be detected in Ubuntu20.04.5,Ubuntu 22.04 and Ubuntu 22.04.1 Status in linux package in Ubuntu: Confirmed Bug description: Configuration: OS:ubuntu-20.04.5-live-server-amd64.iso,ubuntu-22.04-live-server-amd64.iso,ubuntu-22.04.1-live-server-amd64.iso CPU:SPR-SP XCC D-0 48c 270w ES2 99AL8V/QYFN BMC Version 0.48 (Build ID: ESX303K) UEFI Version 0.62 (Build ID: ESE105G) SSD:931.51GB 7.2K SATA HDD S471A08RSH20K04054 00LF039 SSD*2(SATA 0/1):894.25GB SATA SSD HDD*2(SATA 2 alias tsata): 1TB SATA HDD Boot mode:UEFI Reproduce Steps: 1.Boot UEFI,System Settings->Devices and I/O ports,Onboard SATA 2 mode set to "RAID",save and reboot. 2.Boot UEFI,UEFI,System Settings->Storage->Intel VROC tSATA Controller,via drive 12,13 HDD to create RAID Volume,save and reboot. 3.During the installation of Ubuntu(Ubuntu20.04.5,Ubuntu 22.04 and Ubuntu 22.004.1),the raid group under tSATA is not detected. 4.In the OS,the RAID of the tSATA group is not detected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990342/+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 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic
*** This bug is a duplicate of bug 1991704 *** https://bugs.launchpad.net/bugs/1991704 Hi Andrea, Many thanks for the fixed kernel. I tried installing it with "sudo dpkg -i --force-overwrite *" but it would not boot. I see multiple error messages like "failed to validate module [crc32_pclmul] BTF: -22 ..." Did I install it incorrectly? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1991703 Title: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic Status in linux-signed package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: Since the last kernel update today my system stops in the middle of the boot process and does not reach KDE. --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-05-26 (495 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/vgkubuntu-root ro default_hugepagesz=1G hugepagesz=1G hugepages=4 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic uec-images Uname: Linux 5.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/24/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4204 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4204:bd02/24/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1991703/+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 1992435] Re: sof-hda-dsp Dmic0 not initial correctly
** Tags added: originate-from-1989414 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1992435 Title: sof-hda-dsp Dmic0 not initial correctly Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: New Bug description: [Impact] Device use sof-hda-dsp driver will not able to initial the Dmic0 status correctly [Test Plan] 1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service" 2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state" 3. reboot system 4. Dmic should be on and volume set to 70% [Where problems could occur] Only fix for Dmic0 control and upstream already merged the code. The risk will be low [Other Info] Pull Request in upstream https://github.com/alsa-project/alsa-ucm-conf/pull/132 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1992435/+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 1988989] Re: HDMI over USB-C unstable since kernel 5.19 on Intel 12th Gen.
** Summary changed: - HDMI/DisplayPort over USB-C unstable since kernel 5.19 on Intel 12th Gen. + HDMI over USB-C unstable since kernel 5.19 on Intel 12th Gen. -- 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/1988989 Title: HDMI over USB-C unstable since kernel 5.19 on Intel 12th Gen. Status in linux package in Ubuntu: Confirmed Bug description: Having upgraded to 5.19.0-15, my display connected over a USB-C → HDMI connection goes off and on multiple times a minute, rendering it unusable. Downgrading back to 5.15.0-27 makes it work again. I've bisected mainline kernels from https://kernel.ubuntu.com/~kernel- ppa/mainline/ to reach: v5.18.19 GOOD v5.19-rc3 BAD ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 7948 F wireplumber /dev/snd/controlC0: michal 7948 F wireplumber /dev/snd/seq:michal 7939 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 7 14:28:48 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-08-31 (6 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) MachineType: Framework Laptop (12th Gen Intel Core) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_zw6n2j@/vmlinuz-5.19.0-15-generic root=ZFS=rpool/ROOT/ubuntu_zw6n2j ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220831.gitd3c92280-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA42321000N dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988989/+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 1991704] Re: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
** Changed in: linux (Ubuntu) Milestone: None => ubuntu-22.10 -- 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/1991704 Title: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen Status in linux package in Ubuntu: Fix Committed Bug description: After today's Kinetic update my Framework laptop won't boot. The boot hangs after this output: [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci :00:07.1: DPC: RP PIO log size 8 is invalid [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci :00:07.3: DPC: RP PIO log size 0 is invalid [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst ead Falling back to 5.19.0-15-generic works. My Thinkpad X1 Carbon 6th gen does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik4014 F wireplumber /dev/snd/seq:jik4009 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 13:55:09 2022 InstallationDate: Installed on 2022-09-17 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Framework Laptop (12th Gen Intel Core) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA423350021 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+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 1992230] Re: APU Packages missing in Kernel too long boot
Please: $ sudo apt install apport $ sudo apport-collect 1992230 ** Tags added: kern-4598 -- 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/1992230 Title: APU Packages missing in Kernel too long boot Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Confirmed Bug description: Error in new 15 Kernel by a brandnew installed Linux without any programs installed. kemie@kemie-853-opz623:~$ sudo update-initramfs -u [sudo] password for kemie: update-initramfs: Generating /boot/initrd.img-5.15.0-48-generic W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vangogh_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu I: The initramfs will attempt to resume from /dev/sdb4 I: (UUID=579e79cb-4822-44ee-881b-e27ac58e5d0c) I: Set the RESUME variable to override this. System: Kernel: 5.15.0-27-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: Cinnamon 5.4.12 tk: GTK 3.24.33 wm: Mutter dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Desktop Mobo: Micro-Star model: MPG B550 GAMING PLUS (MS-7C56) v: 1.0 serial: UEFI: American Megatrends LLC. v: 1.A0 date: 05/21/2022 CPU: Info: 8-core model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64 type: MT MCP arch: Zen 3 rev: 0 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB Speed (MHz): avg: 2411 high: 2994 min/max: 1400/4672 boost: disabled cores: 1: 2770 2: 2394 3: 2395 4: 2395 5: 2394 6: 2992 7: 2392 8: 1953 9: 1397 10: 1397 11: 2676 12: 2487 13: 2561 14: 2993 15: 2994 16: 2394 bogomips: 121368 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] driver: nouveau v: kernel pcie: speed: 2.5 GT/s lanes: 8 ports: active: HDMI-A-1 empty: DP-1,DVI-D-1 bus-ID: 10:00.0 chip-ID: 10de:1c82 Device-2: AMD Cezanne driver: amdgpu v: kernel pcie: speed: 8 GT/s lanes: 16 ports: active: none empty: DP-2,DP-3,HDMI-A-2 bus-ID: 30:00.0 chip-ID: 1002:1638 Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: amdgpu,ati,modesetting unloaded: fbdev,vesa gpu: nouveau display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: HDMI-1 mapped: HDMI-A-1 model: L236VA res: 1920x1080 dpi: 94 diag: 598mm (23.5") OpenGL: renderer: NV137 v: 4.3 Mesa 22.0.5 direct render: Yes Audio: Device-1: NVIDIA GP107GL High Definition Audio driver: snd_hda_intel v: kernel pcie: speed: 2.5 GT/s lanes: 8 bus-ID: 10:00.1 chip-ID: 10de:0fb9 Device-2: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 30:00.1 chip-ID: 1002:1637 Device-3: AMD Family 17h HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 30:00.6 chip-ID: 1022:15e3 Sound Server-1: ALSA v: k5.15.0-27-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Network: Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 21:00.0 chip-ID: 8086:2725 IF: wlp33s0 state: down mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 2a:00.0 chip-ID: 10ec:8168 IF: enp42s0 state: up speed: 100 Mbps duplex: full mac: Bluetooth: Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-2.3:4 chip-ID: 8087:0032 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardw
[Kernel-packages] [Bug 1992230] Re: APU Packages missing in Kernel too long boot
Note that warnings like 'W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_gpu_info.bin for module amdgpu` are just that, warnings. That doesn't mean that your system actually needs these firmware blobs, it simply means that a driver has been included in the initramfs that references said blobs. Can you at least attach the output of 'sudo dmesg'? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1992230 Title: APU Packages missing in Kernel too long boot Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Confirmed Bug description: Error in new 15 Kernel by a brandnew installed Linux without any programs installed. kemie@kemie-853-opz623:~$ sudo update-initramfs -u [sudo] password for kemie: update-initramfs: Generating /boot/initrd.img-5.15.0-48-generic W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vangogh_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu I: The initramfs will attempt to resume from /dev/sdb4 I: (UUID=579e79cb-4822-44ee-881b-e27ac58e5d0c) I: Set the RESUME variable to override this. System: Kernel: 5.15.0-27-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: Cinnamon 5.4.12 tk: GTK 3.24.33 wm: Mutter dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Desktop Mobo: Micro-Star model: MPG B550 GAMING PLUS (MS-7C56) v: 1.0 serial: UEFI: American Megatrends LLC. v: 1.A0 date: 05/21/2022 CPU: Info: 8-core model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64 type: MT MCP arch: Zen 3 rev: 0 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB Speed (MHz): avg: 2411 high: 2994 min/max: 1400/4672 boost: disabled cores: 1: 2770 2: 2394 3: 2395 4: 2395 5: 2394 6: 2992 7: 2392 8: 1953 9: 1397 10: 1397 11: 2676 12: 2487 13: 2561 14: 2993 15: 2994 16: 2394 bogomips: 121368 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] driver: nouveau v: kernel pcie: speed: 2.5 GT/s lanes: 8 ports: active: HDMI-A-1 empty: DP-1,DVI-D-1 bus-ID: 10:00.0 chip-ID: 10de:1c82 Device-2: AMD Cezanne driver: amdgpu v: kernel pcie: speed: 8 GT/s lanes: 16 ports: active: none empty: DP-2,DP-3,HDMI-A-2 bus-ID: 30:00.0 chip-ID: 1002:1638 Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: amdgpu,ati,modesetting unloaded: fbdev,vesa gpu: nouveau display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: HDMI-1 mapped: HDMI-A-1 model: L236VA res: 1920x1080 dpi: 94 diag: 598mm (23.5") OpenGL: renderer: NV137 v: 4.3 Mesa 22.0.5 direct render: Yes Audio: Device-1: NVIDIA GP107GL High Definition Audio driver: snd_hda_intel v: kernel pcie: speed: 2.5 GT/s lanes: 8 bus-ID: 10:00.1 chip-ID: 10de:0fb9 Device-2: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 30:00.1 chip-ID: 1002:1637 Device-3: AMD Family 17h HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 30:00.6 chip-ID: 1022:15e3 Sound Server-1: ALSA v: k5.15.0-27-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Network: Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 21:00.0 chip-ID: 8086:2725 IF: wlp33s0 state: down mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 2a:00.0 chip-ID: 10ec:8168
[Kernel-packages] [Bug 1992212] Re: nouveau pmu: firmware unavailable gp107
Is it not working or are you just worried about the firmware load error/warning? ** Tags added: kern-4599 -- 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/1992212 Title: nouveau pmu: firmware unavailable gp107 Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Incomplete Bug description: /lib/firmware/nvidia/gp107 /lib/firmware/nvidia/gp107/acr /lib/firmware/nvidia/gp107/gr /lib/firmware/nvidia/gp107/gr/fecs_bl.bin /lib/firmware/nvidia/gp107/gr/fecs_data.bin /lib/firmware/nvidia/gp107/gr/fecs_inst.bin /lib/firmware/nvidia/gp107/gr/fecs_sig.bin /lib/firmware/nvidia/gp107/gr/gpccs_bl.bin /lib/firmware/nvidia/gp107/gr/gpccs_data.bin /lib/firmware/nvidia/gp107/gr/gpccs_inst.bin /lib/firmware/nvidia/gp107/gr/gpccs_sig.bin /lib/firmware/nvidia/gp107/gr/sw_ctx.bin /lib/firmware/nvidia/gp107/gr/sw_nonctx.bin /lib/firmware/nvidia/gp107/nvdec /lib/firmware/nvidia/gp107/sec2 /lib/firmware/nvidia/gp107/acr/bl.bin /lib/firmware/nvidia/gp107/acr/ucode_load.bin /lib/firmware/nvidia/gp107/acr/ucode_unload.bin /lib/firmware/nvidia/gp107/acr/unload_bl.bin /lib/firmware/nvidia/gp107/gr/sw_bundle_init.bin /lib/firmware/nvidia/gp107/gr/sw_method_init.bin /lib/firmware/nvidia/gp107/nvdec/scrubber.bin /lib/firmware/nvidia/gp107/sec2/desc-1.bin /lib/firmware/nvidia/gp107/sec2/desc.bin /lib/firmware/nvidia/gp107/sec2/image-1.bin /lib/firmware/nvidia/gp107/sec2/image.bin /lib/firmware/nvidia/gp107/sec2/sig-1.bin /lib/firmware/nvidia/gp107/sec2/sig.bin Package: linux-firmware Status: install ok installed Priority: optional Section: misc Installed-Size: 846721 Maintainer: Ubuntu Kernel Team Architecture: all Multi-Arch: foreign Version: 20220329.git681281e4-0ubuntu3.5 Replaces: atmel-firmware, linux-firmware-snapdragon (<= 1.2-0ubuntu1), linux-res tricted-common Provides: atmel-firmware Recommends: firmware-sof-signed Breaks: linux-firmware-raspi2 (<= 1.20190819-0ubuntu2), linux-firmware-snapdrago n (<= 1.2-0ubuntu1) Conflicts: atmel-firmware Description: Firmware for Linux kernel drivers This package provides firmware used by Linux kernel drivers. Oct 8 08:49:44 fx504 kernel: [2.659551] MXM: GUID detected in BIOS Oct 8 08:49:44 fx504 kernel: [2.660477] ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210730/ns arguments-61) Oct 8 08:49:44 fx504 kernel: [2.661646] ACPI Warning: \_SB.PCI0.PEG0.PEGP._ DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (202107 30/nsarguments-61) Oct 8 08:49:44 fx504 kernel: [2.663101] pci :01:00.0: optimus capabilit ies: enabled, status dynamic power, hda bios codec supported Oct 8 08:49:44 fx504 kernel: [2.664016] VGA switcheroo: detected Optimus DS M method \_SB_.PCI0.PEG0.PEGP handle Oct 8 08:49:44 fx504 kernel: [2.664940] nouveau :01:00.0: enabling devi ce (0006 -> 0007) Oct 8 08:49:44 fx504 kernel: [2.665979] checking generic (8000 7e9000) vs hw (a300 100) Oct 8 08:49:44 fx504 kernel: [2.665981] checking generic (8000 7e9000) vs hw (9000 1000) Oct 8 08:49:44 fx504 kernel: [2.665982] checking generic (8000 7e9000) vs hw (a000 200) Oct 8 08:49:44 fx504 kernel: [2.666029] nouveau :01:00.0: NVIDIA GP107 (137000a1) Oct 8 08:49:44 fx504 kernel: [2.680631] checking generic (8000 7e9000) vs hw (a200 100) Oct 8 08:49:44 fx504 kernel: [2.680632] checking generic (8000 7e9000) vs hw (8000 1000) Oct 8 08:49:44 fx504 kernel: [2.746655] nouveau :01:00.0: bios: version 86.07.50.00.59 Oct 8 08:49:44 fx504 kernel: [2.747754] nouveau :01:00.0: pmu: firmware unavailable Oct 8 08:49:44 fx504 kernel: [2.755349] i915 :00:02.0: [drm] [ENCODER:1 02:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it Oct 8 08:49:44 fx504 kernel: [2.803611] nouveau :01:00.0: fb: 4096 MiB GDDR5 Oct 8 08:49:44 fx504 kernel: [3.132263] [drm] Initialized i915 1.6.0 202011 03 for :00:02.0 on minor 0 Oct 8 08:49:44 fx504 kernel: [3.139712] ACPI: video: Video Device [GFX0] (m ulti-head: yes rom: no post: no) Oct 8 08:49:44 fx504 kernel: [3.139759] nouveau :01:00.0: DRM: VRAM: 40 96 MiB Oct 8 08:49:44 fx504 kernel: [3.139763] nouveau :01:00.0: DRM: GART: 53 6870912 MiB Oct 8 08:49:44 fx504 kernel: [3.139766] nouveau :01:00.0: DRM: BIT tabl e 'A' not found Oct 8 08:49:44 fx504 kernel: [3.139768] nouveau :01:00.0: DRM: BIT tabl e 'L' not found Oct 8 08:49:44 fx504 kernel: [3.139770] nouveau :01:00.0: DRM: Pointer to TMDS table not found Oct 8 08:49:4