[Kernel-packages] [Bug 2058752] Re: ath11k high jitter and packet loss when operating in 802.11ax mode
Well, that was a pleasant surprise! On 6.8.0-11 the problem seems to be completely gone. I guess I'll be upgrading to Noble as soon as possible. -- 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/2058752 Title: ath11k high jitter and packet loss when operating in 802.11ax mode Status in linux package in Ubuntu: New Bug description: On 6.5.0-26-generic, my QCNFA765 cannot really operate in 802.11ax mode. I have a Thinkpad P16s Gen 2 with a (soldered, sadly) QCNFA765 card, which uses the ath11k driver. I also have a Ruckus R650 AP, which supports wifi6. Connecting the two and pinging the AP yields the following: ``` 64 bytes from 192.168.16.77: icmp_seq=45 ttl=64 time=22.4 ms 64 bytes from 192.168.16.77: icmp_seq=46 ttl=64 time=29.6 ms 64 bytes from 192.168.16.77: icmp_seq=47 ttl=64 time=26.8 ms 64 bytes from 192.168.16.77: icmp_seq=48 ttl=64 time=2174 ms 64 bytes from 192.168.16.77: icmp_seq=49 ttl=64 time=1158 ms 64 bytes from 192.168.16.77: icmp_seq=50 ttl=64 time=130 ms 64 bytes from 192.168.16.77: icmp_seq=51 ttl=64 time=503 ms 64 bytes from 192.168.16.77: icmp_seq=54 ttl=64 time=1832 ms 64 bytes from 192.168.16.77: icmp_seq=55 ttl=64 time=808 ms 64 bytes from 192.168.16.77: icmp_seq=56 ttl=64 time=9.32 ms 64 bytes from 192.168.16.77: icmp_seq=57 ttl=64 time=2.11 ms 64 bytes from 192.168.16.77: icmp_seq=58 ttl=64 time=25.6 ms 64 bytes from 192.168.16.77: icmp_seq=59 ttl=64 time=30.9 ms 64 bytes from 192.168.16.77: icmp_seq=60 ttl=64 time=95.6 ms ^C --- 192.168.16.77 ping statistics --- 60 packets transmitted, 55 received, 8.3% packet loss, time 59273ms rtt min/avg/max/mdev = 2.105/275.084/2344.792/560.334 ms, pipe 3 ``` Those periodic bursts of >1s latency make some webpages fail to load and videochats unusable. No interference is present in my channel of choice. Nothing interesting is printed in dmesg while the above occurs. The above does not happen if: * I disable wifi 6 in the AP * I ping a wifi 5 AP (I also have an older R710, which is a 802.11ac AP) * I ping the R650 in wifi 6 mode from a AX210 on kernel 6.2 * I ping the R650 from a completely different OS and device (e.g. Android) I'll test with a 24.04 daily image next. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-26-generic 6.5.0-26.26 ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 21 16:58:07 2024 MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=zfs:zroot/ROOT/ubuntu quiet loglevel=4 rtc_cmos.use_acpi_alarm=1 spl.spl_hostid=0x4605c990 RelatedPackageVersions: linux-restricted-modules-6.5.0-26-generic N/A linux-backports-modules-6.5.0-26-generic N/A linux-firmware20230919.git3672ccab-0ubuntu2.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2024 dmi.bios.release: 1.18 dmi.bios.vendor: LENOVO dmi.bios.version: R2FET38W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 21K9001NUS dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnLENOVO:bvrR2FET38W(1.18):bd01/15/2024:br1.18:efr1.11:svnLENOVO:pn21K9001NUS:pvrThinkPadP16sGen2:rvnLENOVO:rn21K9001NUS:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K9_BU_Think_FM_ThinkPadP16sGen2: dmi.product.family: ThinkPad P16s Gen 2 dmi.product.name: 21K9001NUS dmi.product.sku: LENOVO_MT_21K9_BU_Think_FM_ThinkPad P16s Gen 2 dmi.product.version: ThinkPad P16s Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058752/+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 2056706] Re: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0"
All of my VMs running 6.8 under Xen with XCP-ng are impacted. Also affects non-Ubuntu distros with vanilla 6.8.1 kernels. 6.7.9 runs fine. -- 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/2056706 Title: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0" Status in linux package in Ubuntu: Confirmed Bug description: After upgrading a homelab 24.04 test machine from 6.6 to 6.8 kernel that was recently introduced, the test machine started flooding the terminal with following messages: [ 1877.712068] BUG: Bad page state in process swapper/0 pfn:58919 The process name varies and appears to be whatever is currently doing something. I installed a fresh up to date copy to see if this could be replicated elsewhere and the outcome is the same. Both of the machines are VMs running under Xen with XCP-ng, although unsure if it's related. The issue produces a notable amount of syslog entries. If left running, the system will eventually go into a state where processes get stuck and do not react to systemd control, even when there's no notable load, no memory pressure nor is the disk space low. Booted back to 6.6 kernel the issue no longer happens. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 11 00:31 seq crw-rw+ 1 root audio 116, 33 Mar 11 00:31 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Mon Mar 11 00:36:24 2024 InstallationDate: Installed on 2024-03-11 (0 days ago) InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily amd64 (20240222) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 002: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Xen HVM domU PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 LC_CTYPE=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=97002c6c-ab61-49d5-b937-891e4e8da514 ro RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2024 dmi.bios.release: 4.13 dmi.bios.vendor: Xen dmi.bios.version: 4.13 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.13:bd01/31/2024:br4.13:svnXen:pnHVMdomU:pvr4.13:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.13 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056706/+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 2058557] Re: Kernel panic during checkbox stress_ng_test on Grace running noble 6.8 (arm64+largemem) kernel
Earlier, I said that the device mapper observation did not seem to be a hard line - however, further testing now indicates that the situations where I observed panics when stressing nvme0n1 were due to an unrelated bug that is present in the latest 6.5 mainline tree, but *not* the latest 6.5 Ubuntu kernel tree (6.5.0-26-generic-64k). Therefore, from the perspective of *this* bug report, it once again *does* appear that this issue is only present when stressing dm-0 and not present when stressing a non-device-mapper device. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058557 Title: Kernel panic during checkbox stress_ng_test on Grace running noble 6.8 (arm64+largemem) kernel Status in linux package in Ubuntu: New Bug description: A kernel oops and panic occurred during 22.04 SoC certification on Gunyolk (Grace/Grace) with 6.8 kernel, arm64+largemem variant Steps to reproduce: Run (as root) the following commands: add-apt-repository -y ppa:checkbox-dev/stable apt-add-repository -y ppa:firmware-testing-team/ppa-fwts-stable apt update apt install -y canonical-certification-server /usr/lib/checkbox-provider-base/bin/stress_ng_test.py disk --device dm-0 --base-time 240 stress_ng_test caused a kernel panic after about 5 minutes. I have attached dmesg output from my reproducer to this report. Initially, this was identified via a panic during the above test, which was running as part of a run of certify-soc-22.04. Attached is a tarball containing: - apport.linux-image-6.8.0-11-generic-64k.kzsondji.apport: The output of `ubuntu-bug linux` on the machine (after reboot) - reproduced-dmesg.202403201942: The dmesg output captured by kdump when I reproduced my original issue by running only the single stress_ng_test.py command above (not the entire cert suite) - original-dmesg.txt: The dmesg output I captured when the stress_ng_test originally failed during the full cert suite run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-5.15/5.15.0.1060.69~20.04.1)
All autopkgtests for the newly accepted linux-meta-azure-5.15 (5.15.0.1060.69~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.23 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-azure-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp-5.15/5.15.0.1055.63~20.04.1)
All autopkgtests for the newly accepted linux-meta-gcp-5.15 (5.15.0.1055.63~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.15/5.15.0-1054.62~20.04.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-gcp-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi/5.15.0.1050.48)
All autopkgtests for the newly accepted linux-meta-raspi (5.15.0.1050.48) for jammy have finished running. The following regressions have been reported in tests triggered by the package: ddcci-driver-linux/unknown (arm64) digimend-dkms/unknown (arm64) nat-rtsp/unknown (arm64) nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf) nvidia-graphics-drivers-525/unknown (arm64) rtl8821ce/unknown (arm64) systemd/249.11-0ubuntu3.12 (arm64, armhf) wireguard/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-raspi [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057484] Re: kernel worker event freezes during traffic on iwlwifi
Issue still exists with 6.5.0-26 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2057484 Title: kernel worker event freezes during traffic on iwlwifi Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: With traffic on Intel Wifi 7 BE200 card, For a while kernel enter 100% cpu usage on a worker event thread and kworker/0:0-events_freezable is in D state. System highly unresponsive during this time. Happens in 6.5.0-25, does not happen in 6.5.0-17 Description:Ubuntu 22.04.4 LTS Release:22.04 Installed: 6.5.0-25.25~22.04.1 Candidate: 6.5.0-25.25~22.04.1 Version table: *** 6.5.0-25.25~22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status linux-modules-6.5.0-25-generic: Installed: 6.5.0-25.25~22.04.1 Candidate: 6.5.0-25.25~22.04.1 Version table: *** 6.5.0-25.25~22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status filename: /lib/modules/6.5.0-25-generic/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko license:GPL description:Intel(R) Wireless WiFi driver for Linux firmware: iwlwifi-100-5.ucode firmware: iwlwifi-1000-5.ucode firmware: iwlwifi-135-6.ucode firmware: iwlwifi-105-6.ucode firmware: iwlwifi-2030-6.ucode firmware: iwlwifi-2000-6.ucode firmware: iwlwifi-5150-2.ucode firmware: iwlwifi-5000-5.ucode firmware: iwlwifi-6000g2b-6.ucode firmware: iwlwifi-6000g2a-6.ucode firmware: iwlwifi-6050-5.ucode firmware: iwlwifi-6000-6.ucode firmware: iwlwifi-7265D-29.ucode firmware: iwlwifi-7265-17.ucode firmware: iwlwifi-3168-29.ucode firmware: iwlwifi-3160-17.ucode firmware: iwlwifi-7260-17.ucode firmware: iwlwifi-8265-36.ucode firmware: iwlwifi-8000C-36.ucode firmware: iwlwifi-9260-th-b0-jf-b0-46.ucode firmware: iwlwifi-9000-pu-b0-jf-b0-46.ucode firmware: iwlwifi-cc-a0-77.ucode firmware: iwlwifi-QuZ-a0-jf-b0-77.ucode firmware: iwlwifi-QuZ-a0-hr-b0-77.ucode firmware: iwlwifi-Qu-b0-jf-b0-77.ucode firmware: iwlwifi-Qu-c0-hr-b0-77.ucode firmware: iwlwifi-Qu-b0-hr-b0-77.ucode firmware: iwlwifi-ma-b0-mr-a0-83.ucode firmware: iwlwifi-ma-b0-gf4-a0-83.ucode firmware: iwlwifi-ma-b0-gf-a0-83.ucode firmware: iwlwifi-ma-b0-hr-b0-83.ucode firmware: iwlwifi-ma-a0-mr-a0-83.ucode firmware: iwlwifi-ma-a0-gf4-a0-83.ucode firmware: iwlwifi-ma-a0-gf-a0-83.ucode firmware: iwlwifi-ma-a0-hr-b0-83.ucode firmware: iwlwifi-ty-a0-gf-a0-83.ucode firmware: iwlwifi-so-a0-gf-a0-83.ucode firmware: iwlwifi-so-a0-hr-b0-83.ucode firmware: iwlwifi-so-a0-jf-b0-83.ucode firmware: iwlwifi-gl-c0-fm-c0-83.ucode firmware: iwlwifi-gl-b0-fm-b0-83.ucode firmware: iwlwifi-bz-a0-fm4-b0-83.ucode firmware: iwlwifi-bz-a0-fm-c0-83.ucode firmware: iwlwifi-bz-a0-fm-b0-83.ucode firmware: iwlwifi-bz-a0-gf4-a0-83.ucode firmware: iwlwifi-bz-a0-gf-a0-83.ucode firmware: iwlwifi-bz-a0-hr-b0-83.ucode firmware: iwlwifi-sc-a0-wh-a0-83.ucode firmware: iwlwifi-sc-a0-gf4-a0-83.ucode firmware: iwlwifi-sc-a0-gf-a0-83.ucode firmware: iwlwifi-sc-a0-hr-b0-83.ucode firmware: iwlwifi-sc-a0-hr-b0-83.ucode firmware: iwlwifi-sc-a0-fm-c0-83.ucode firmware: iwlwifi-sc-a0-fm-b0-83.ucode srcversion: CE34BB7E0E287E10FEC1E13 alias: pci:v8086dE440sv*sd*bc*sc*i* alias: pci:v8086d7740sv*sd*bc*sc*i* alias: pci:v8086dA840sv*sd*bc*sc*i* alias: pci:v8086d272Bsv*sd*bc*sc*i* alias: pci:v8086d2727sv*sd*bc*sc*i* alias: pci:v8086d7E40sv*sd*bc*sc*i* alias: pci:v8086d2729sv*sd*bc*sc*i* alias: pci:v8086d7F70sv*sd*bc*sc*i* alias: pci:v8086d54F0sv*sd*bc*sc*i* alias: pci:v8086d51F1sv*sd*bc*sc*i* alias: pci:v8086d51F1sv*sd*bc*sc*i* alias: pci:v8086d51F0sv*sd*bc*sc*i* alias: pci:v8086d7AF0sv*sd*bc*sc*i* alias: pci:v8086d7A70sv*sd*bc*sc*i* alias: pci:v8086d2725sv*sd*bc*sc*i* alias: pci:v8086d2723sv*sd*bc*sc*i* alias: pci:v8086dA0F0sv*sd*bc*sc*i* alias: pci:v8086d43F0sv*sd*bc*sc*i* alias:
[Kernel-packages] [Bug 2058557] Re: Kernel panic during checkbox stress_ng_test on Grace running noble 6.8 (arm64+largemem) kernel
I did not observe this issue with any other stress_ng disk tests on linux-image-6.8.0-11-generic-64k after 1 full run of the suite with the "aiol" test disabled. (When running the "aiol" test alone, it panicked reliably each time.) -- 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/2058557 Title: Kernel panic during checkbox stress_ng_test on Grace running noble 6.8 (arm64+largemem) kernel Status in linux package in Ubuntu: New Bug description: A kernel oops and panic occurred during 22.04 SoC certification on Gunyolk (Grace/Grace) with 6.8 kernel, arm64+largemem variant Steps to reproduce: Run (as root) the following commands: add-apt-repository -y ppa:checkbox-dev/stable apt-add-repository -y ppa:firmware-testing-team/ppa-fwts-stable apt update apt install -y canonical-certification-server /usr/lib/checkbox-provider-base/bin/stress_ng_test.py disk --device dm-0 --base-time 240 stress_ng_test caused a kernel panic after about 5 minutes. I have attached dmesg output from my reproducer to this report. Initially, this was identified via a panic during the above test, which was running as part of a run of certify-soc-22.04. Attached is a tarball containing: - apport.linux-image-6.8.0-11-generic-64k.kzsondji.apport: The output of `ubuntu-bug linux` on the machine (after reboot) - reproduced-dmesg.202403201942: The dmesg output captured by kdump when I reproduced my original issue by running only the single stress_ng_test.py command above (not the entire cert suite) - original-dmesg.txt: The dmesg output I captured when the stress_ng_test originally failed during the full cert suite run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058557/+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 2057424] Re: No variable refresh rate (VRR) on the Framework 16
FWIW it's in drm-fixes now. https://cgit.freedesktop.org/drm/drm/commit/?id=2f14c0c8cae8e9e3b603a3f91909baba66540027 -- 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/2057424 Title: No variable refresh rate (VRR) on the Framework 16 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Bug description: Quoted from AMD proposed fix in https://lore.kernel.org/amd- gfx/46657fa4-630e-47a5-a339-242ecd5ba...@amd.com/T/#m94e3b7d292e359f3d656babe3ccdbf7fc6daab6f > The monitor shipped with the Framework 16 supports VRR [1], but it's not > being advertised. > > This is because the detailed timing block doesn't contain > `EDID_DETAIL_MONITOR_RANGE` which amdgpu looks for to find min and max > frequencies. This check however is superfluous for this case because > update_display_info() calls drm_get_monitor_range() to get these ranges > already. > > So if the `DRM_EDID_FEATURE_CONTINUOUS_FREQ` EDID feature is found then > turn on freesync without extra checks. See: https://www.reddit.com/r/framework/comments/1b4y2i5/no_variable_refresh_rate_on_the_framework_16_on/ See: https://www.reddit.com/r/framework/comments/1b6vzcy/framework_16_variable_refresh_rate/ See: https://community.frame.work/t/resolved-no-vrr-freesync-with-amd-version/42338 Link: https://gist.github.com/superm1/e8fbacfa4d0f53150231d3a3e0a13faf To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2057424/+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 2054489] Re: Crash on blank screen
*** This bug is a duplicate of bug 2056445 *** https://bugs.launchpad.net/bugs/2056445 ** This bug has been marked a duplicate of bug 2056445 external monitors flash white with every interrupt -- 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/2054489 Title: Crash on blank screen Status in linux package in Ubuntu: New Bug description: When my computer screen goes blank and then locks due to inactivity, the screen goes white and requires a reboot to recover. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.6.0-14-generic 6.6.0-14.14 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 20 17:29:43 2024 InstallationDate: Installed on 2024-02-02 (19 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash RelatedPackageVersions: linux-restricted-modules-6.6.0-14-generic N/A linux-backports-modules-6.6.0-14-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP07 dmi.board.vendor: Framework dmi.board.version: A7 dmi.chassis.asset.tag: FRANDGCPA735010072 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A7 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP07 dmi.product.version: A7 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054489/+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 2053040] Re: GPU Crash When Waking from Suspend
*** This bug is a duplicate of bug 2056445 *** https://bugs.launchpad.net/bugs/2056445 ** This bug has been marked a duplicate of bug 2056445 external monitors flash white with every interrupt -- 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/2053040 Title: GPU Crash When Waking from Suspend Status in linux package in Ubuntu: New Bug description: Screen goes completely white, have to reboot the system to recover. I've manually attached the kernel log from the previous boot which contains the relevant errors. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.6.0-14-generic 6.6.0-14.14 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 13 10:19:39 2024 InstallationDate: Installed on 2024-02-02 (12 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash RelatedPackageVersions: linux-restricted-modules-6.6.0-14-generic N/A linux-backports-modules-6.6.0-14-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP07 dmi.board.vendor: Framework dmi.board.version: A7 dmi.chassis.asset.tag: FRANDGCPA735010072 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A7 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP07 dmi.product.version: A7 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053040/+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 2052467] Re: Unplugging External Monitor Causes GPU Crash
*** This bug is a duplicate of bug 2056445 *** https://bugs.launchpad.net/bugs/2056445 ** This bug has been marked a duplicate of bug 2056445 external monitors flash white with every interrupt -- 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/2052467 Title: Unplugging External Monitor Causes GPU Crash Status in linux package in Ubuntu: New Bug description: Unplugging an exteranal usb-c monitor caused the GPU to crash - the screen went white and unresponsive, reboot was required for the machine to become usable. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.6.0-14-generic 6.6.0-14.14 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:holmanb1976 F pipewire /dev/snd/controlC0: holmanb1989 F wireplumber /dev/snd/controlC1: holmanb1989 F wireplumber CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 5 16:20:03 2024 InstallationDate: Installed on 2024-02-02 (4 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash RelatedPackageVersions: linux-restricted-modules-6.6.0-14-generic N/A linux-backports-modules-6.6.0-14-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP07 dmi.board.vendor: Framework dmi.board.version: A7 dmi.chassis.asset.tag: FRANDGCPA735010072 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A7 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP07 dmi.product.version: A7 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052467/+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 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)
Asus N550JV (NVIDIA GeForce GT 750M and Intel(R) HD Graphics 4600). Flickering appears after the screen goes to sleep. I'm using Ubuntu 22.04.4 LTS. 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller Kernel driver in use: i915 -- 01:00.0 3D controller: NVIDIA Corporation GK107M [GeForce GT 750M] (rev a1) Subsystem: ASUSTeK Computer Inc. GK107M [GeForce GT 750M] Kernel driver in use: nvidia -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux source package in Lunar: Won't Fix Status in linux-hwe-5.19 source package in Lunar: Invalid Status in linux-hwe-6.2 source package in Lunar: Invalid Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel parameter i915.enable_dc=0 intel_idle.max_cstate=2 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+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 2057805] Re: On Noble, system is locking up when attempting to log back in after being away for a few minutes
Just wanted to say, this is still happening regularly to me. I can work around it if I remember to put the system in suspend rather than simply locking the screen, but if I lock the screen and walk away for too long, the system is locked up aside from the alt-sysrq keys. I have a system where I can readily reproduce the issue and am happy to work with devs re: testing or possible fixes; would love to get this fixed before noble goes out the door. -- 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/2057805 Title: On Noble, system is locking up when attempting to log back in after being away for a few minutes Status in linux package in Ubuntu: New Bug description: Context: On my laptop, connected to battery power, if I lock the screen and come back sometime later (likely after the 10 minute "screen blank" threshold I have set in Gnome), I find that it does not come back up properly. * I have 3 monitors (2 external and one built-in), and when I move my mouse to wake up my machine, only the wallpaper on the built-in display seems to come back. * I get no login prompt. * I have no visible mouse cursor, and pressing Num Lock on my keyboard doesn't toggle any lights on the keyboard. * Ctrl-Alt-F1, -F2, etc., do not work. * The only way I know to get out of this is to either hard-reboot the machine or use the Alt-SysRq keys (e.g. the "reisub" combination). * /var/log/syslog and kern.log do show a general protection fault. Actually, 3 of them. (I had at least 3 lockups yesterday.) I've attached one as general_protection_fault.txt here; hopefully "ubuntu-bug linux" could capture the others if they are helpful. Additional context in case it is helpful: * I recently upgraded from Mantic to Noble for the purpose of dogfooding prior to formal release. I had some problems on Mantic with stability which had similar crashes, but they were more intermittent and did not generate the protection faults in syslog. Since upgrading to Noble, the lockups have changed from intermittent to predictable, i.e. if I lock my screen and walk away for at least 10 minutes, I fully expect to have to reboot my machine. I am running the 2013 model of the ASUS ROG M16 Zephyrus. It does use Nvidia Optimus, and while I suspect the problems I was encountering on Mantic were perhaps due to Nvidia driver bugs, the issues in Noble do appear to be different since the crashes are more consistent and appear to also generate the general protection fault errors in syslog. (I explain this since without this nuance, it may be easy to just suspect the nvidia driver is causing the problem.) Hopefully this helps; let me know if there's anything else I can provide to assist with this bug. Best Regards, Paul Goins ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 13 08:30:23 2024 InstallationDate: Installed on 2023-09-11 (184 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus M16 GU604VI_GU604VI ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=c8e79db4-8ec5-4855-89b4-aea8fb2c5b8c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-03-07 (6 days ago) dmi.bios.date: 09/07/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GU604VI.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU604VI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.68 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGU604VI.312:bd09/07/2023:br5.27:efr0.68:svnASUSTeKCOMPUTERINC.:pnROGZephyrusM16GU604VI_GU604VI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU604VI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus M16 dmi.product.name: ROG Zephyrus M16 GU604VI_GU604VI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[Kernel-packages] [Bug 2050019] Re: [24.04 FEAT] [SEC2353] zcrypt: extend error recovery to deal with device scans
** Tags added: 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/2050019 Title: [24.04 FEAT] [SEC2353] zcrypt: extend error recovery to deal with device scans Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: The error recovery of a crypto request currently fails if a device is not available or the device is not completely setup and bound if the device has been discovered due to a bus scan. If, during request handling, a device is lost and a bus scan is triggered the DD must wait for the bus scan (including the device binding) to complete before giving up on reties. This item is important to support life guest relocation where the APQN sets on the source and target guests differ. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2050019/+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 2051560] Re: Provide python perf module
** Changed in: linux (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2051560 Title: Provide python perf module Status in linux package in Ubuntu: Fix Committed Bug description: [Impact] We need to provide the python perf module, because some applications (such as tuned) require it. This module is implemented inside perf, provided by the kernel. At the moment we provide a distinct perf for each kernel installed in the system. There is really no reason to do that, because perf is both backward and forward compatible, but this is a different issue and we are not going to solve it in this context and it will be addressed in a separate bug. For now, to solve this specific issue, we need to enable the python module when we build perf (as part of the kernel build) and ship the library inside the linux-tools- package. However, this brings a new problem, because we need to install the module in a standard python path (so that python applications can be able to use it in a regular way), but we need to support multiple installed versions and add some logic to transparently select the right one when a generic user-space python application uses `import perf`. For this reason we need to provide a python wrapper module that is imported via a regular `import perf` and it transparently loads the actual python perf module, based on the kernel that is currently running. [Test case] Install linux-tools- and run the following simple test case: $ python -c 'import perf; [print(c) for c in perf.cpu_map()]' [Fix] - Enable the python perf module build during the regular kernel build - Provide a virtual `perf` python module wrapper in linux-tools-common [Regression potential] We are adding a new python module to linux-tools (that is something new, we don't ship any other python module), but we are not changing anything that is already provided, so the only regression that can happen is an increased size of the linux-tools package. [Original bug report] The tuned package has some plugins which rely on the perf python module [1], and right now they are not working because we do not have the perf python module available in Ubuntu. Initially, this was reported in this other bug [2], but it seems the scope of that bug is bigger than what we (Server) need for tuned. So filing this new bug as requested by the Kernel team to provide just the python module. For reference, in Fedora it's shipped in the bin:python3-perf package: [root@f39 ~]# rpm -ql python3-perf /usr/lib/.build-id /usr/lib/.build-id/80 /usr/lib/.build-id/80/9022196f598cb3327545c2d497b1d9fdf55630 /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/PKG-INFO /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/SOURCES.txt /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/dependency_links.txt /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/top_level.txt /usr/lib64/python3.12/site-packages/perf.cpython-312-x86_64-linux-gnu.so /usr/share/licenses/python3-perf /usr/share/licenses/python3-perf/COPYING Built from their kernel-tools package[3]. [1] https://bugs.launchpad.net/ubuntu/+source/tuned/+bug/2051290 [2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613393 [3] https://src.fedoraproject.org/rpms/kernel-tools/blob/rawhide/f/kernel-tools.spec#_148 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051560/+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 2051560] Re: Provide python perf module
Patch sent to the kernel team mailing list for review: https://lists.ubuntu.com/archives/kernel-team/2024-March/149751.html -- 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/2051560 Title: Provide python perf module Status in linux package in Ubuntu: New Bug description: [Impact] We need to provide the python perf module, because some applications (such as tuned) require it. This module is implemented inside perf, provided by the kernel. At the moment we provide a distinct perf for each kernel installed in the system. There is really no reason to do that, because perf is both backward and forward compatible, but this is a different issue and we are not going to solve it in this context and it will be addressed in a separate bug. For now, to solve this specific issue, we need to enable the python module when we build perf (as part of the kernel build) and ship the library inside the linux-tools- package. However, this brings a new problem, because we need to install the module in a standard python path (so that python applications can be able to use it in a regular way), but we need to support multiple installed versions and add some logic to transparently select the right one when a generic user-space python application uses `import perf`. For this reason we need to provide a python wrapper module that is imported via a regular `import perf` and it transparently loads the actual python perf module, based on the kernel that is currently running. [Test case] Install linux-tools- and run the following simple test case: $ python -c 'import perf; [print(c) for c in perf.cpu_map()]' [Fix] - Enable the python perf module build during the regular kernel build - Provide a virtual `perf` python module wrapper in linux-tools-common [Regression potential] We are adding a new python module to linux-tools (that is something new, we don't ship any other python module), but we are not changing anything that is already provided, so the only regression that can happen is an increased size of the linux-tools package. [Original bug report] The tuned package has some plugins which rely on the perf python module [1], and right now they are not working because we do not have the perf python module available in Ubuntu. Initially, this was reported in this other bug [2], but it seems the scope of that bug is bigger than what we (Server) need for tuned. So filing this new bug as requested by the Kernel team to provide just the python module. For reference, in Fedora it's shipped in the bin:python3-perf package: [root@f39 ~]# rpm -ql python3-perf /usr/lib/.build-id /usr/lib/.build-id/80 /usr/lib/.build-id/80/9022196f598cb3327545c2d497b1d9fdf55630 /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/PKG-INFO /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/SOURCES.txt /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/dependency_links.txt /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/top_level.txt /usr/lib64/python3.12/site-packages/perf.cpython-312-x86_64-linux-gnu.so /usr/share/licenses/python3-perf /usr/share/licenses/python3-perf/COPYING Built from their kernel-tools package[3]. [1] https://bugs.launchpad.net/ubuntu/+source/tuned/+bug/2051290 [2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613393 [3] https://src.fedoraproject.org/rpms/kernel-tools/blob/rawhide/f/kernel-tools.spec#_148 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051560/+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 1286021] Re: 2.1 surround support (userspace)
I have a problem with 2.1 sound on Realtek High Definition Audio (2.1): 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel -- 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel -- 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/1286021 Title: 2.1 surround support (userspace) Status in alsa-lib package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-lib source package in Trusty: Confirmed Status in pulseaudio source package in Trusty: Confirmed Bug description: 2.1 surround should work as seamlessly as other surround options, such as 4.0, 5.1 and 7.1 work today. Alsa-lib and pulseaudio patches for 14.04 can be tested here: https://launchpad.net/~diwic/+archive/surround21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1286021/+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 2056418] Re: Fix headphone mic detection issue on ALC897
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2056418 Title: Fix headphone mic detection issue on ALC897 Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Headphone mic is lost after resume from S3 or reboot with plugin. [Fix] Restore the headphone mic detect logic for ALC897 after lost power. [Test] Tested on hardware, the headphone mic appears as plugin after boot or resume from S3, and works fine. [Where problems could occur] It may break ALC897 sound input. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2056418/+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 2058752] [NEW] ath11k high jitter and packet loss when operating in 802.11ax mode
Public bug reported: On 6.5.0-26-generic, my QCNFA765 cannot really operate in 802.11ax mode. I have a Thinkpad P16s Gen 2 with a (soldered, sadly) QCNFA765 card, which uses the ath11k driver. I also have a Ruckus R650 AP, which supports wifi6. Connecting the two and pinging the AP yields the following: ``` 64 bytes from 192.168.16.77: icmp_seq=45 ttl=64 time=22.4 ms 64 bytes from 192.168.16.77: icmp_seq=46 ttl=64 time=29.6 ms 64 bytes from 192.168.16.77: icmp_seq=47 ttl=64 time=26.8 ms 64 bytes from 192.168.16.77: icmp_seq=48 ttl=64 time=2174 ms 64 bytes from 192.168.16.77: icmp_seq=49 ttl=64 time=1158 ms 64 bytes from 192.168.16.77: icmp_seq=50 ttl=64 time=130 ms 64 bytes from 192.168.16.77: icmp_seq=51 ttl=64 time=503 ms 64 bytes from 192.168.16.77: icmp_seq=54 ttl=64 time=1832 ms 64 bytes from 192.168.16.77: icmp_seq=55 ttl=64 time=808 ms 64 bytes from 192.168.16.77: icmp_seq=56 ttl=64 time=9.32 ms 64 bytes from 192.168.16.77: icmp_seq=57 ttl=64 time=2.11 ms 64 bytes from 192.168.16.77: icmp_seq=58 ttl=64 time=25.6 ms 64 bytes from 192.168.16.77: icmp_seq=59 ttl=64 time=30.9 ms 64 bytes from 192.168.16.77: icmp_seq=60 ttl=64 time=95.6 ms ^C --- 192.168.16.77 ping statistics --- 60 packets transmitted, 55 received, 8.3% packet loss, time 59273ms rtt min/avg/max/mdev = 2.105/275.084/2344.792/560.334 ms, pipe 3 ``` Those periodic bursts of >1s latency make some webpages fail to load and videochats unusable. No interference is present in my channel of choice. Nothing interesting is printed in dmesg while the above occurs. The above does not happen if: * I disable wifi 6 in the AP * I ping a wifi 5 AP (I also have an older R710, which is a 802.11ac AP) * I ping the R650 in wifi 6 mode from a AX210 on kernel 6.2 * I ping the R650 from a completely different OS and device (e.g. Android) I'll test with a 24.04 daily image next. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-26-generic 6.5.0-26.26 ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 21 16:58:07 2024 MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=zfs:zroot/ROOT/ubuntu quiet loglevel=4 rtc_cmos.use_acpi_alarm=1 spl.spl_hostid=0x4605c990 RelatedPackageVersions: linux-restricted-modules-6.5.0-26-generic N/A linux-backports-modules-6.5.0-26-generic N/A linux-firmware20230919.git3672ccab-0ubuntu2.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2024 dmi.bios.release: 1.18 dmi.bios.vendor: LENOVO dmi.bios.version: R2FET38W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 21K9001NUS dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnLENOVO:bvrR2FET38W(1.18):bd01/15/2024:br1.18:efr1.11:svnLENOVO:pn21K9001NUS:pvrThinkPadP16sGen2:rvnLENOVO:rn21K9001NUS:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K9_BU_Think_FM_ThinkPadP16sGen2: dmi.product.family: ThinkPad P16s Gen 2 dmi.product.name: 21K9001NUS dmi.product.sku: LENOVO_MT_21K9_BU_Think_FM_ThinkPad P16s Gen 2 dmi.product.version: ThinkPad P16s Gen 2 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic 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/2058752 Title: ath11k high jitter and packet loss when operating in 802.11ax mode Status in linux package in Ubuntu: New Bug description: On 6.5.0-26-generic, my QCNFA765 cannot really operate in 802.11ax mode. I have a Thinkpad P16s Gen 2 with a (soldered, sadly) QCNFA765 card, which uses the ath11k driver. I also have a Ruckus R650 AP, which supports wifi6. Connecting the two and pinging the AP yields the following: ``` 64 bytes from 192.168.16.77: icmp_seq=45 ttl=64 time=22.4 ms 64 bytes from 192.168.16.77: icmp_seq=46 ttl=64 time=29.6 ms 64 bytes from 192.168.16.77: icmp_seq=47 ttl=64 time=26.8 ms 64 bytes from 192.168.16.77: icmp_seq=48 ttl=64 time=2174 ms 64 bytes from 192.168.16.77: icmp_seq=49 ttl=64 time=1158 ms 64 bytes from 192.168.16.77: icmp_seq=50 ttl=64 time=130 ms 64 bytes from 192.168.16.77: icmp_seq=51 ttl=64 time=503 ms 64 bytes from 192.168.16.77: icmp_seq=54 ttl=64 time=1832 ms 64 bytes from 192.168.16.77: icmp_seq=55 ttl=64 time=808 ms 64 bytes from 192.168.16.77: icmp_seq=56 ttl=64 time=9.32 ms 64 bytes from 192.168.16.77: icmp_seq=57 ttl=64 time=2.11 ms 64 bytes from 192.168.16.77: icmp_seq=58 ttl=64 time=25.6 ms 64
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-nvidia/5.15.0-1048.48)
All autopkgtests for the newly accepted linux-restricted-modules-nvidia (5.15.0-1048.48) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-nvidia [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058750] Re: i915 GPU HANG: ecode 12:1:db96edba
Sorry, I'm not sure what information was automatically attached to this report generated with the command `ubuntu-bug linux` but here is a snippet from the `syslog`: ``` Mar 22 14:01:45 james-xps kernel: [271888.137758] i915 :00:02.0: [drm] *ERROR* GT0: GUC: Engine reset failed on 0:0 (rcs0) because 0x Mar 22 14:01:45 james-xps kernel: [271888.191936] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:db96edba, in CanvasRenderer [2738] Mar 22 14:01:45 james-xps kernel: [271888.192116] i915 :00:02.0: [drm] Resetting chip for GuC failed to reset engine mask=0x1 Mar 22 14:01:45 james-xps kernel: [271888.297138] i915 :00:02.0: [drm] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} Mar 22 14:01:45 james-xps kernel: [271888.297885] i915 :00:02.0: [drm] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} Mar 22 14:01:45 james-xps kernel: [271888.298023] i915 :00:02.0: [drm] CanvasRenderer[2738] context reset due to GPU hang Mar 22 14:01:45 james-xps kernel: [271888.298126] i915 :00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.5.1 Mar 22 14:01:45 james-xps kernel: [271888.298139] i915 :00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3 Mar 22 14:01:45 james-xps kernel: [271888.321405] i915 :00:02.0: [drm] GT0: HuC: authenticated for all workloads Mar 22 14:01:45 james-xps kernel: [271888.326098] i915 :00:02.0: [drm] GT0: GUC: submission enabled Mar 22 14:01:45 james-xps kernel: [271888.326099] i915 :00:02.0: [drm] GT0: GUC: SLPC enabled ``` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058750 Title: i915 GPU HANG: ecode 12:1:db96edba Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: This has happened several times over a period of months when visiting the site https://www.windy.com and viewing satellite images. The computer completely freezes and must be hard restarted. I don't think I have triggered this freeze by visiting any other site. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 14:14:41 2024 InstallationDate: Installed on 2023-04-12 (344 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2058750/+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 2058750] [NEW] i915 GPU HANG: ecode 12:1:db96edba
Public bug reported: This has happened several times over a period of months when visiting the site https://www.windy.com and viewing satellite images. The computer completely freezes and must be hard restarted. I don't think I have triggered this freeze by visiting any other site. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 14:14:41 2024 InstallationDate: Installed on 2023-04-12 (344 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.5 (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-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058750 Title: i915 GPU HANG: ecode 12:1:db96edba Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: This has happened several times over a period of months when visiting the site https://www.windy.com and viewing satellite images. The computer completely freezes and must be hard restarted. I don't think I have triggered this freeze by visiting any other site. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 14:14:41 2024 InstallationDate: Installed on 2023-04-12 (344 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2058750/+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 2049635] Re: Roll UDA & ERD drivers from 525 to 535
** Also affects: nvidia-graphics-drivers-525 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525-server (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: fabric-manager-525 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-525 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525 (Ubuntu Noble) Importance: Undecided Status: Fix Released ** Also affects: nvidia-graphics-drivers-525-server (Ubuntu Noble) Importance: Undecided Status: Fix Released ** Also affects: fabric-manager-525 (Ubuntu Noble) Importance: Undecided Status: Fix Released ** Also affects: libnvidia-nscq-525 (Ubuntu Noble) Importance: Undecided Status: Fix Released ** Also affects: nvidia-graphics-drivers-525 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525-server (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: fabric-manager-525 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-525 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525-server (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: fabric-manager-525 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-525 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525-server (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: fabric-manager-525 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-525 (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2049635 Title: Roll UDA & ERD drivers from 525 to 535 Status in fabric-manager-525 package in Ubuntu: Fix Released Status in libnvidia-nscq-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in fabric-manager-525 source package in Bionic: New Status in libnvidia-nscq-525 source package in Bionic: New Status in nvidia-graphics-drivers-525 source package in Bionic: New Status in nvidia-graphics-drivers-525-server source package in Bionic: New Status in fabric-manager-525 source package in Focal: New Status in libnvidia-nscq-525 source package in Focal: New Status in nvidia-graphics-drivers-525 source package in Focal: New Status in nvidia-graphics-drivers-525-server source package in Focal: New Status in fabric-manager-525 source package in Jammy: New Status in libnvidia-nscq-525 source package in Jammy: New Status in nvidia-graphics-drivers-525 source package in Jammy: New Status in nvidia-graphics-drivers-525-server source package in Jammy: New Status in fabric-manager-525 source package in Mantic: New Status in libnvidia-nscq-525 source package in Mantic: New Status in nvidia-graphics-drivers-525 source package in Mantic: New Status in nvidia-graphics-drivers-525-server source package in Mantic: New Status in fabric-manager-525 source package in Noble: Fix Released Status in libnvidia-nscq-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525-server source package in Noble: Fix Released Bug description: [ Impact ] * 525 series of drivers is now end of life, roll these to 535 via transitional packages * 535 is a longterm branch [ Test Plan ] * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers * Enable proposed * apt full-upgrade should upgrade both userspace drivers and LRM to respective 535, 535-open, 535-server drivers [ Where problems could occur ] * Virtual provides in the past have caused kernel flavour switch during such rolls before, this remains unresolved. * All cards supported by 525 series of the driver are supported by the 535 driver, thus there is no loss of functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-525/+bug/2049635/+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 2007601] Re: On Boot after ramdisk loads: ACPI BIOS error (bug) AE_AML_Buffer_Limit, ... is beyond end of object
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.19 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007601 Title: On Boot after ramdisk loads: ACPI BIOS error (bug) AE_AML_Buffer_Limit, ... is beyond end of object Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: this tool shows linux-signed-hwe-5.19? But Grub shows 5.19.0-32-generic After regular Software Update to kernel 5.19.0-32-generic on boot after the boot disk is decrypted, and the ramdisk loads: the error message (see attached jpg) shows briefly before continuing to load to the log in screen. No noticeable problems, but I've not tried to suspend (which in the past works, most of the time) with this kernel loaded. Per wiki.ubuntu.com/Kernel/Bugs 1, hardware: see screenshot of Settings/About 2. every boot to this kernel produces the error 3. Does NOT Exist in previous kernels 5.15.0-60-generic and earlier 4. Problem: not sure how to test the latest development Ubuntu kernel version as well as the latest upstream mainline kernel. Towards a solution: This probably is the latest development kernel? (I've looked at https://wiki.ubuntu.com/Kernel/MainlineBuilds?action=show=KernelMainlineBuilds, AND I'm not familiar enough with the language to understand what I'd be doing, so unless I have specific directions on how to test the latest development and upstream mainline kernels, I'm not about to stab in the dark at it. I only get the basic drift that this bug may be fixed in the upcoming kernels, and installing them may or may not work (for other reasons) on the LTS I have running now. this command gives this result $ cat /proc/version_signature Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Not sure if this is a security risk or not, so to be safe I ticked that it is. Smells like it to me, anyway. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 16 10:08:33 2023 InstallationDate: Installed on 2023-01-11 (36 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2007601/+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 2058668] Re: [SRF] performance: hwmon: (coretemp) Fix core count limitation
Patchset submitted to the mailing list -- 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/2058668 Title: [SRF] performance: hwmon: (coretemp) Fix core count limitation Status in linux package in Ubuntu: New Status in linux source package in Jammy: In Progress Bug description: This is a public version of https://bugs.launchpad.net/bugs/2049792 Backport: [SRF] performance: hwmon: (coretemp) Fix core count limitation (merged upstream in 6.9) to jammy [Impact] In linux 6.8 the coretemp driver supports at most 128 cores per package. Cores higher than 128 will lose their core temperature information. There is an upstream patch set that allows to support more than 128 cores per package, it's applied to linux-next, then to Noble. We should apply the patch set to the Jammy 5.15 kernel, so that we can properly support systems with a large amount of cores per package. [Test case] Read temperature info from /sys/class/hwmon on a system with > 128 cores per package (that means we don't have a proper test case to verify the fix at the moment). [Fix] A series of patch is part of this improvement: 1a793caf6f69 hwmon: (coretemp) Use dynamic allocated memory for core temp_data 18b24a5f9ca3 hwmon: (coretemp) Remove redundant temp_data->is_pkg_data 326241f71f3d hwmon: (coretemp) Split package temp_data and core temp_data b0b01414a261 hwmon: (coretemp) Abstract core_temp helpers 87eb801925a0 hwmon: (coretemp) Remove redundant pdata->cpu_map[] 18d8f5583388 hwmon: (coretemp) Replace sensor_device_attribute with device_attribute 25f8e01baa05 hwmon: (coretemp) Remove unnecessary dependency of array index c8c2074020a8 hwmon: (coretemp) Introduce enum for attr index And some patch are required to make the backporting clean: 34cf8c657cf03 hwmon: (coretemp) Enlarge per package core count limit fdaf0c8629d45 hwmon: (coretemp) Fix bogus core_id to attr name mapping 4e440abc89458 hwmon: (coretemp) Fix out-of-bounds memory access a2930f6dc90f0 hwmon: (coretemp) Delete an obsolete comment 6c2b659913ad9 hwmon: (coretemp) Delete tjmax debug message 0f8b916bc5b5d hwmon: (coretemp) avoid RDMSR interrupts to isolated CPUs fae30e3c203e0 hwmon: (coretemp) Add support for dynamic ttarget c0c67f8761cec hwmon: (coretemp) Add support for dynamic tjmax 2bc0e6d07ee50 hwmon: (coretemp) rearrange tjmax handing code 5c0e64dde80ff hwmon: (coretemp) Remove obsolete temp_data->valid Only 5c0e64dde80ff has to be modified as it's deleting a variable which changed type because of a refactoring. There is a number of commits, but they are only changing one file. [Regression potential] We may experience hwmon-related regressions, either systems reading incorrect temperature information or even bugs/crashes when accessing data from /sys/class/hwmon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058668/+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 2058047] Re: On Dell Latitude ??90, versions 5.15.0-100 and 6.5.0-25 of the kernel hang upon accessing wired Ethernet
It seems that the issue is related to the Wi-Fi card and the iwlwifi driver. It can be fixed by installing the linux-modules-iwlwifi-generic / linux-modules-iwlwifi-generic-hwe-22.04 package, respectively. Also, the issue seems to only pop up on Dell Latitude ??90 laptops (confirmed on Latitude 7490 and 5590). ** Summary changed: - Versions 5.15.0-100 and 6.5.0-25 of the kernel hang upon accessing the Intel Ethernet controller (4) I219-LM [8086:15d7] (rev 21) + On Dell Latitude ??90, versions 5.15.0-100 and 6.5.0-25 of the kernel hang upon accessing wired Ethernet ** Summary changed: - On Dell Latitude ??90, versions 5.15.0-100 and 6.5.0-25 of the kernel hang upon accessing wired Ethernet + On Dell Latitude ??90, versions 5.15.0-100 and 6.5.0-25 of the kernel hang upon accessing wired Ethernet unless linux-modules-iwlwifi-generic is 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/2058047 Title: On Dell Latitude ??90, versions 5.15.0-100 and 6.5.0-25 of the kernel hang upon accessing wired Ethernet unless linux-modules-iwlwifi- generic is installed Status in linux package in Ubuntu: New Bug description: The system hangs with Linux 5.15.0-100 and 6.5.0-25 upon accessing this Ethernet controller: $ lspci -nn ... 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (4) I219-LM [8086:15d7] (rev 21) Commands that deal with the network hang forever, e.g. "ip link". The machine must be hard-rebooted (magic sysrq) because systemd also hangs during reboot. Previous versions work perfectly fine (5.15.0-97 and 6.5.0-21). The issue is specific to the integrated network controller, because it goes away when the Ethernet controller is disabled in the BIOS. Attached is an extract of the kernel logs under the problematic kernel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-100-generic 5.15.0-100.110 ProcVersionSignature: Ubuntu 5.15.0-97.107-generic 5.15.136 Uname: Linux 5.15.0-97-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-97-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yl243478 3612 F pulseaudio CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckMismatches: ./boot.catalog CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Mar 15 16:48:19 2024 InstallationDate: Installed on 2022-11-10 (491 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0c45:6717 Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-97-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ipv6.disable=1 quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-97-generic N/A linux-backports-modules-5.15.0-97-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2023 dmi.bios.release: 1.36 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.36.0 dmi.board.name: 0YM3X5 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.36.0:bd12/13/2023:br1.36:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0YM3X5:rvrA01:cvnDellInc.:ct10:cvr:sku081C: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058047/+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 2058668] Re: [SRF] performance: hwmon: (coretemp) Fix core count limitation
** Description changed: This is a public version of https://bugs.launchpad.net/bugs/2049792 Backport: [SRF] performance: hwmon: (coretemp) Fix core count limitation (merged upstream in 6.9) to jammy - [Description] - coretemp driver supports at most 128 cores per package. Cores higher than 128 will lose their core temperature information. - Some SRF SKUs have more than 128 cores per package and triggers the issue. + [Impact] + + In linux 6.8 the coretemp driver supports at most 128 cores per package. + Cores higher than 128 will lose their core temperature information. + + There is an upstream patch set that allows to support more than 128 + cores per package, it's applied to linux-next, then to Noble. + + We should apply the patch set to the Jammy 5.15 kernel, so that we can + properly support systems with a large amount of cores per package. + + [Test case] + + Read temperature info from /sys/class/hwmon on a system with > 128 cores + per package (that means we don't have a proper test case to verify the + fix at the moment). [Fix] + A series of patch is part of this improvement: + 1a793caf6f69 hwmon: (coretemp) Use dynamic allocated memory for core temp_data 18b24a5f9ca3 hwmon: (coretemp) Remove redundant temp_data->is_pkg_data 326241f71f3d hwmon: (coretemp) Split package temp_data and core temp_data b0b01414a261 hwmon: (coretemp) Abstract core_temp helpers 87eb801925a0 hwmon: (coretemp) Remove redundant pdata->cpu_map[] 18d8f5583388 hwmon: (coretemp) Replace sensor_device_attribute with device_attribute 25f8e01baa05 hwmon: (coretemp) Remove unnecessary dependency of array index c8c2074020a8 hwmon: (coretemp) Introduce enum for attr index + And some patch are required to make the backporting clean: + 34cf8c657cf03 hwmon: (coretemp) Enlarge per package core count limit fdaf0c8629d45 hwmon: (coretemp) Fix bogus core_id to attr name mapping 4e440abc89458 hwmon: (coretemp) Fix out-of-bounds memory access a2930f6dc90f0 hwmon: (coretemp) Delete an obsolete comment 6c2b659913ad9 hwmon: (coretemp) Delete tjmax debug message 0f8b916bc5b5d hwmon: (coretemp) avoid RDMSR interrupts to isolated CPUs fae30e3c203e0 hwmon: (coretemp) Add support for dynamic ttarget c0c67f8761cec hwmon: (coretemp) Add support for dynamic tjmax 2bc0e6d07ee50 hwmon: (coretemp) rearrange tjmax handing code 5c0e64dde80ff hwmon: (coretemp) Remove obsolete temp_data->valid - Only 5c0e64dde80ff has to be modified as it's delete a variable which changed type + Only 5c0e64dde80ff has to be modified as it's deleting a variable which changed type because of a refactoring. - [Test] - Verify on specific hardware if we can read temperature accordingly. + There is a number of commits, but they are only changing one file. + + [Regression potential] + + We may experience hwmon-related regressions, either systems reading + incorrect temperature information or even bugs/crashes when accessing + data from /sys/class/hwmon. ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Thibf (thibf) -- 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/2058668 Title: [SRF] performance: hwmon: (coretemp) Fix core count limitation Status in linux package in Ubuntu: New Status in linux source package in Jammy: In Progress Bug description: This is a public version of https://bugs.launchpad.net/bugs/2049792 Backport: [SRF] performance: hwmon: (coretemp) Fix core count limitation (merged upstream in 6.9) to jammy [Impact] In linux 6.8 the coretemp driver supports at most 128 cores per package. Cores higher than 128 will lose their core temperature information. There is an upstream patch set that allows to support more than 128 cores per package, it's applied to linux-next, then to Noble. We should apply the patch set to the Jammy 5.15 kernel, so that we can properly support systems with a large amount of cores per package. [Test case] Read temperature info from /sys/class/hwmon on a system with > 128 cores per package (that means we don't have a proper test case to verify the fix at the moment). [Fix] A series of patch is part of this improvement: 1a793caf6f69 hwmon: (coretemp) Use dynamic allocated memory for core temp_data 18b24a5f9ca3 hwmon: (coretemp) Remove redundant temp_data->is_pkg_data 326241f71f3d hwmon: (coretemp) Split package temp_data and core temp_data b0b01414a261 hwmon: (coretemp) Abstract core_temp helpers 87eb801925a0 hwmon: (coretemp) Remove redundant pdata->cpu_map[] 18d8f5583388 hwmon: (coretemp) Replace sensor_device_attribute with device_attribute 25f8e01baa05 hwmon: (coretemp) Remove unnecessary dependency of array index c8c2074020a8 hwmon: (coretemp) Introduce enum for attr index And some patch are
[Kernel-packages] [Bug 2054121] Re: Random whole system lockups on Lenovo ThinkStation P350 Tiny
Should I still submit logs? I think I'll just buy a new PC w/o NVIDIA and re-purpose this one... Here is the latest Lockup 070244 - SSL not avail ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5758328/+files/prevboot.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054121 Title: Random whole system lockups on Lenovo ThinkStation P350 Tiny Status in linux package in Ubuntu: New Bug description: Random lockups in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28 15:37:48 UTC 2023 GCC version: ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 16 09:08:41 2024 DistUpgraded: Fresh install DistroCodename: mantic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db] InstallationDate: Installed on 2024-02-16 (0 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2023 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: M3JKT3CA dmi.board.name: 32DD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN 3305435660291 dmi.chassis.type: 35 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny: dmi.product.family: ThinkStation P350 Tiny dmi.product.name: 30EF004VUS dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny dmi.product.version: ThinkStation P350 Tiny dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.115-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+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 2050019] Re: [24.04 FEAT] [SEC2353] zcrypt: extend error recovery to deal with device scans
I've submitted the PR to the kernel teams mailing list: https://lists.ubuntu.com/archives/kernel-team/2024-March/thread.html#149742 ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel Team (canonical-kernel-team) ** Information type changed from Private to Public -- 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/2050019 Title: [24.04 FEAT] [SEC2353] zcrypt: extend error recovery to deal with device scans Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: The error recovery of a crypto request currently fails if a device is not available or the device is not completely setup and bound if the device has been discovered due to a bus scan. If, during request handling, a device is lost and a bus scan is triggered the DD must wait for the bus scan (including the device binding) to complete before giving up on reties. This item is important to support life guest relocation where the APQN sets on the source and target guests differ. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2050019/+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 2058740] [NEW] New upstram reelase 535.161.08
Public bug reported: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] ** Affects: fabric-manager-535 (Ubuntu) Importance: Undecided Status: New ** Affects: libnvidia-nscq-535 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535-server (Ubuntu) Importance: Undecided Status: New ** Affects: fabric-manager-535 (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: libnvidia-nscq-535 (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535 (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535-server (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: fabric-manager-535 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: libnvidia-nscq-535 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535-server (Ubuntu Focal) Importance: Undecided Status: New ** Affects: fabric-manager-535 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: libnvidia-nscq-535 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535-server (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: fabric-manager-535 (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: libnvidia-nscq-535 (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535 (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535-server (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: fabric-manager-535 (Ubuntu Noble) Importance: Undecided Status: New ** Affects: libnvidia-nscq-535 (Ubuntu Noble) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535 (Ubuntu Noble) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535-server (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: fabric-manager-535 (Ubuntu) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-535 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535-server (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535-server (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: fabric-manager-535 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-535 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535-server (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: fabric-manager-535 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-535 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535-server (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: fabric-manager-535 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-535 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535-server (Ubuntu Mantic) Importance:
[Kernel-packages] [Bug 2015561] Re: Imac 16, 2 reboots instead of shutdown or sleep
** Description changed: Ubuntu 22.04 on Dual Boot Imac 2015 16,2 - When ask for reboot or sleep , it just reboots + When ask for Shutdown or sleep , it just reboots ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Apr 7 16:21:51 2023 InstallationDate: Installed on 2023-01-23 (74 days ago) InstallationMedia: Ubuntu 22.04.1 EKIMIA LTS "EKIMIA Jammy Jellyfish" (20230119) ProcEnviron: - TERM=xterm - PATH=(custom, no user) - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + LANG=fr_FR.UTF-8 + SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2015561 Title: Imac 16,2 reboots instead of shutdown or sleep Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: Ubuntu 22.04 on Dual Boot Imac 2015 16,2 When ask for Shutdown or sleep , it just reboots ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Apr 7 16:21:51 2023 InstallationDate: Installed on 2023-01-23 (74 days ago) InstallationMedia: Ubuntu 22.04.1 EKIMIA LTS "EKIMIA Jammy Jellyfish" (20230119) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2015561/+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 1970069] Re: Annoying boot messages interfering with splash screen
https://salsa.debian.org/ubuntu-dev- team/plymouth/-/commit/bd9d0119fdbeb3b30c8d3caafdb8a31b23c188c4 does not reflect the removal of the complete drm section. -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 2049569] Re: Enable the mic-mute led on Dell MTL laptops
Hello Chris, or anyone else affected, Accepted firmware-sof into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/firmware- sof/2.0-1ubuntu4.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-failed-jammy ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049569 Title: Enable the mic-mute led on Dell MTL laptops Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in firmware-sof source package in Noble: Fix Released Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justifications] == kernels == [Impact] On Dell's Precision 3550, Intel MTL platform, the MIC-Mute function is working but the LED(on F4) state is not changed accordingly. [Fix] There's no problem on the same series on RPL platform. It needs MTL specific SoF driver and controls to support the registered mixer switch. It requires the patches in https://lore.kernel.org/all/20230919103115.30783-1-peter.ujfal...@linux.intel.com/ and https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. 2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled. [Where problems could occur] It's only required for new sof-audio-pci-intel-mtl driver. The impact should be restricting. == firmware-sof == [Impact] The mic-mute led not working on Intel MTL powered laptops. [Fix] For firmware-sof, it required the upstream commit fdc884baa4b3 ("Add sof-ipc4-v2.8.1/mtl/, intel-signed + community") and the sof-hda-generic-2ch.tplg from v2.8.1 to make sure the ipc4 topology and control matches with the updated driver. [Test Case] 1. enable -proposed pocket and install firmware-sof-signed 2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. [Where problems could occur] The updated sof-mtl.ri and the sof-hda-generic-2ch.tplg are shared by all Intel MTL platforms. Need to verify audio function on MTL enpowered machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049569/+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 2055283] Please test proposed package
Hello Hui, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.30 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2055283 Title: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2055283 [Impact] We have an Lenovo laptop, after installing the oem-ubuntu-22.04 image and booting up, the bluetooth couldn't work at all. Checking the dmesg, the bluetooth driver needs to load the firmware intel/ibt-0180-4150.sfi, but there is no this firmware in the linux-firmware of Jammy, and I also checked the Mantic and Noble, Mandic doesn't have this firmware too, Noble already has the firmware since the upstream linux-firmware integrated the intel/ibt-0180-4150.sfi last year. [Fix] Backport 4 commits from upstream linux-firmware, these 4 commits are all on intel/ibt-0180-4150.sfi|ddc [Test Case] Put the firmware into the /lib/firmware/intel/, reboot the machine, check dmesg, the bluetooth driver loads the firmware successfully, run hciconfig, the hci0 shows up. run checkbox testcase, it could pass. [Checkbox job `com.canonical.certification::bluetooth/detect-output` output] [Where problems could occur] Probably could make the Intel AX201 BT adapter couldn't work, but the possibility is very low, we tested the firmware on different lenovo machines with the BT adapter AX201, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055283/+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 2055283] Re: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi
Hello Hui, or anyone else affected, Accepted linux-firmware into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20230919.git3672ccab-0ubuntu2.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2055283 Title: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2055283 [Impact] We have an Lenovo laptop, after installing the oem-ubuntu-22.04 image and booting up, the bluetooth couldn't work at all. Checking the dmesg, the bluetooth driver needs to load the firmware intel/ibt-0180-4150.sfi, but there is no this firmware in the linux-firmware of Jammy, and I also checked the Mantic and Noble, Mandic doesn't have this firmware too, Noble already has the firmware since the upstream linux-firmware integrated the intel/ibt-0180-4150.sfi last year. [Fix] Backport 4 commits from upstream linux-firmware, these 4 commits are all on intel/ibt-0180-4150.sfi|ddc [Test Case] Put the firmware into the /lib/firmware/intel/, reboot the machine, check dmesg, the bluetooth driver loads the firmware successfully, run hciconfig, the hci0 shows up. run checkbox testcase, it could pass. [Checkbox job `com.canonical.certification::bluetooth/detect-output` output] [Where problems could occur] Probably could make the Intel AX201 BT adapter couldn't work, but the possibility is very low, we tested the firmware on different lenovo machines with the BT adapter AX201, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055283/+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 2053277] Please test proposed package
Hello Richard, or anyone else affected, Accepted linux-firmware into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20230919.git3672ccab-0ubuntu2.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2053277 Title: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Bug description: [SRU Justification] [Impact] Devices hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. [Fix] AMD GPU dcn firmware upgrade to upstream commit bd2ad5e6 needed. The affected blob is amdgpu/dcn_3_2_0_dmcub.bin, which has stayed the first revision since Jammy is ever released. However, the related commits from the upgrade path have also included blob updates to all kinds of different, unrelated hardware models. This pull request bumps only the affected binary to the target commit per online discussion with AMD. [Test Case] Perform checkbox warmboot stress test: $ checkbox-cli run com.canonical.certification::stress/reboot [Where problems could occur] While DCN blob maybe shared with several hardware models, with confirmation from IHV, there should be little risk to upgrade it. [Other Info] Affects both Jammy and Mantic. == original bug report == Dell reported sporadically hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. After updating DMCUB firmware version to 0x07002600, they observed a significant improvement in passing rate. And Dell wants to add the updated DMCUB firmware (ver 0x7002600) to its OEM image. DMCUB firmware (ver 0x7002600) is at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2053277/+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 2053277] Please test proposed package
Hello Richard, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.30 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2053277 Title: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Bug description: [SRU Justification] [Impact] Devices hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. [Fix] AMD GPU dcn firmware upgrade to upstream commit bd2ad5e6 needed. The affected blob is amdgpu/dcn_3_2_0_dmcub.bin, which has stayed the first revision since Jammy is ever released. However, the related commits from the upgrade path have also included blob updates to all kinds of different, unrelated hardware models. This pull request bumps only the affected binary to the target commit per online discussion with AMD. [Test Case] Perform checkbox warmboot stress test: $ checkbox-cli run com.canonical.certification::stress/reboot [Where problems could occur] While DCN blob maybe shared with several hardware models, with confirmation from IHV, there should be little risk to upgrade it. [Other Info] Affects both Jammy and Mantic. == original bug report == Dell reported sporadically hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. After updating DMCUB firmware version to 0x07002600, they observed a significant improvement in passing rate. And Dell wants to add the updated DMCUB firmware (ver 0x7002600) to its OEM image. DMCUB firmware (ver 0x7002600) is at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2053277/+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 2051560] Re: Provide python perf module
** Description changed: + [Impact] + + We need to provide the python perf module, because some applications + (such as tuned) require it. + + This module is implemented inside perf, provided by the kernel. + + At the moment we provide a distinct perf for each kernel installed in + the system. There is really no reason to do that, because perf is both + backward and forward compatible, but this is a different issue and we + are not going to solve it in this context and it will be addressed in a + separate bug. + + For now, to solve this specific issue, we need to enable the python + module when we build perf (as part of the kernel build) and ship the + library inside the linux-tools- package. + + However, this brings a new problem, because we need to install the + module in a standard python path (so that python applications can be + able to use it in a regular way), but we need to support multiple + installed versions and add some logic to transparently select the right + one when a generic user-space python application uses `import perf`. + + For this reason we need to provide a python wrapper module that is + imported via a regular `import perf` and it transparently loads the + actual python perf module, based on the kernel that is currently + running. + + [Test case] + + Install linux-tools- and run the following simple test + case: + + $ python -c 'import perf; [print(c) for c in perf.cpu_map()]' + + [Fix] + + - Enable the python perf module build during the regular kernel build + - Provide a virtual `perf` python module wrapper in linux-tools-common + + [Regression potential] + + We are adding a new python module to linux-tools (that is something new, + we don't ship any other python module), but we are not changing anything + that is already provided, so the only regression that can happen is an + increased size of the linux-tools package. + + [Original bug report] + The tuned package has some plugins which rely on the perf python module [1], and right now they are not working because we do not have the perf python module available in Ubuntu. Initially, this was reported in this other bug [2], but it seems the scope of that bug is bigger than what we (Server) need for tuned. So filing this new bug as requested by the Kernel team to provide just the python module. For reference, in Fedora it's shipped in the bin:python3-perf package: [root@f39 ~]# rpm -ql python3-perf /usr/lib/.build-id /usr/lib/.build-id/80 /usr/lib/.build-id/80/9022196f598cb3327545c2d497b1d9fdf55630 /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/PKG-INFO /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/SOURCES.txt /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/dependency_links.txt /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/top_level.txt /usr/lib64/python3.12/site-packages/perf.cpython-312-x86_64-linux-gnu.so /usr/share/licenses/python3-perf /usr/share/licenses/python3-perf/COPYING Built from their kernel-tools package[3]. - [1] https://bugs.launchpad.net/ubuntu/+source/tuned/+bug/2051290 [2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613393 [3] https://src.fedoraproject.org/rpms/kernel-tools/blob/rawhide/f/kernel-tools.spec#_148 -- 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/2051560 Title: Provide python perf module Status in linux package in Ubuntu: New Bug description: [Impact] We need to provide the python perf module, because some applications (such as tuned) require it. This module is implemented inside perf, provided by the kernel. At the moment we provide a distinct perf for each kernel installed in the system. There is really no reason to do that, because perf is both backward and forward compatible, but this is a different issue and we are not going to solve it in this context and it will be addressed in a separate bug. For now, to solve this specific issue, we need to enable the python module when we build perf (as part of the kernel build) and ship the library inside the linux-tools- package. However, this brings a new problem, because we need to install the module in a standard python path (so that python applications can be able to use it in a regular way), but we need to support multiple installed versions and add some logic to transparently select the right one when a generic user-space python application uses `import perf`. For this reason we need to provide a python wrapper module that is imported via a regular `import perf` and it transparently loads the actual python perf module, based on the kernel that is currently running. [Test case] Install linux-tools- and run the following simple test case: $ python -c 'import perf;
[Kernel-packages] [Bug 2058330] Re: Update amd-pmf for AMD strix series
** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oem (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/2058330 Title: Update amd-pmf for AMD strix series Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Status in linux-oem source package in Noble: New Bug description: These updates will be enhanced amd-pmf for family 1AH on the supported OEM platforms, including enabling new revision for BIOS notify events, support static slider by APTS (AMD Performance and Thermal State)...etc. Needs to be backported into oem-6.8. Following are commits merged to linus tree for v6.9-rc1: * 8362e862fb879 platform/x86/amd/pmf: Update sps power thermals according to the platform-profiles * 3eecb434d7f21 platform/x86/amd/pmf: Add support to get sps default APTS index values * 48d38f569261b platform/x86/amd/pmf: Add support to get APTS index numbers for static slider * 6262938eef282 platform/x86/amd/pmf: Add support to notify sbios heart beat event * 5fdc8b82aab4c platform/x86/amd/pmf: Add support to get sbios requests in PMF driver * 233f78e11e1fa platform/x86/amd/pmf: Disable debugfs support for querying power thermals * a33e9e106601b platform/x86/amd/pmf: Differentiate PMF ACPI versions To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058330/+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 2056445] Re: external monitors flash white with every interrupt
** Changed in: linux Status: Unknown => 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/2056445 Title: external monitors flash white with every interrupt Status in Linux: New Status in linux package in Ubuntu: Triaged Bug description: an interesting amdgpu issue: I currently have two external monitors, and only one will display the desktop at a time - the other is completely white. The interesting thing is that with each interrupt that the kernel receives from keyboard / mouse, the screens will flip which one is visible. With my monitors positioned above and to the left of the laptop's built-in display, the flashing monitors feel akin to attending an electronic light show, or perhaps a display of fireworks - the monitors flip visibility with each keypress. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 05:23:23 2024 InstallationDate: Installed on 2024-02-02 (34 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP07 dmi.board.vendor: Framework dmi.board.version: A7 dmi.chassis.asset.tag: FRANDGCPA735010072 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A7 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP07 dmi.product.version: A7 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2056445/+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 2058710] [NEW] CONFIG_IRQ_TIME_ACCOUNTING option is not enabled in kernel-generic - 6.8 kernel - ubuntu noble version
Public bug reported: Hi Ubuntu Kernel Team, I notice this today. This option CONFIG_IRQ_TIME_ACCOUNTING is not enabled in Ubuntu Noble 6.8 Kernel. Is possible to add this at built-in? # CONFIG_IRQ_TIME_ACCOUNTING is not set It would help me for profiling in the future, when testing applications in the performance area. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Package changed: irqbalance (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058710 Title: CONFIG_IRQ_TIME_ACCOUNTING option is not enabled in kernel-generic - 6.8 kernel - ubuntu noble version Status in linux package in Ubuntu: New Bug description: Hi Ubuntu Kernel Team, I notice this today. This option CONFIG_IRQ_TIME_ACCOUNTING is not enabled in Ubuntu Noble 6.8 Kernel. Is possible to add this at built-in? # CONFIG_IRQ_TIME_ACCOUNTING is not set It would help me for profiling in the future, when testing applications in the performance area. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058710/+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 2058710] [NEW] CONFIG_IRQ_TIME_ACCOUNTING option is not enabled in kernel-generic - 6.8 kernel - ubuntu noble version
You have been subscribed to a public bug: Hi Ubuntu Kernel Team, I notice this today. This option CONFIG_IRQ_TIME_ACCOUNTING is not enabled in Ubuntu Noble 6.8 Kernel. Is possible to add this at built-in? # CONFIG_IRQ_TIME_ACCOUNTING is not set It would help me for profiling in the future, when testing applications in the performance area. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- CONFIG_IRQ_TIME_ACCOUNTING option is not enabled in kernel-generic - 6.8 kernel - ubuntu noble version https://bugs.launchpad.net/bugs/2058710 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058707] [NEW] Backport AXI 1-wire host driver
Public bug reported: [ Impact ] [ Test Plan ] [ Where problems could occur ] [ Other info ] ** Affects: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2058707 Title: Backport AXI 1-wire host driver Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: [ Impact ] [ Test Plan ] [ Where problems could occur ] [ Other info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2058707/+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 2058706] [NEW] Tegra234 SD card corruption after rebooting some number of times
Public bug reported: The SD card is being observed to get corrupted after some number of reboots, e.g. often in the neighborhood of 10-50 iterations. ** Affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2058706 Title: Tegra234 SD card corruption after rebooting some number of times Status in linux-nvidia-tegra package in Ubuntu: New Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: The SD card is being observed to get corrupted after some number of reboots, e.g. often in the neighborhood of 10-50 iterations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2058706/+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