[Kernel-packages] [Bug 2093622] Re: IDPF: TX timeout and crash
** Changed in: linux-gcp (Ubuntu Noble) Status: New => Fix Committed ** Changed in: linux-gcp (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-gke (Ubuntu Noble) Status: New => Fix Committed ** Changed in: linux-gke (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-gkeop (Ubuntu Noble) Status: New => Fix Committed ** Changed in: linux-gkeop (Ubuntu) Status: New => Fix Committed ** Changed in: linux-gke (Ubuntu) Status: New => Fix Committed ** Changed in: linux-gcp (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2093622 Title: IDPF: TX timeout and crash Status in linux-gcp package in Ubuntu: Fix Committed Status in linux-gke package in Ubuntu: Fix Committed Status in linux-gkeop package in Ubuntu: Fix Committed Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gke source package in Jammy: Fix Committed Status in linux-gcp source package in Noble: Fix Committed Status in linux-gke source package in Noble: Fix Committed Status in linux-gkeop source package in Noble: Fix Committed Status in linux-gcp source package in Oracular: Fix Committed Bug description: SRU Justification [Impact] Google has requested a patchset to be backported to resolve an issue in the IDPF module. The issue can lead to timeouts and potentially a system crash. [Fix] Backport a patchset from linux upstream to all IDPF-enabled Google kernels. [Test Plan] Compile and boot tested. [Regression Potential] This is a medium size backport and affects several kernels. Only the Oracular patches were applied cleanly, which increases the chance of human error in the backport process. Problems related to this fix could lead to further issues in the Intel IDPF module, but there have been no changes to other drivers or the core kernel. [Other] SF #00404007 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2093622/+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 2080454] Re: NIC(r8169) didn't link up after resuming from suspend
linux-oem-22.04d 6.8.0-53.55~22.04.1 in jammy-proposed contains the fix. https://changelogs.ubuntu.com/changelogs/pool/main/l/linux- hwe-6.8/linux-hwe-6.8_6.8.0-53.55~22.04.1/changelog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2080454 Title: NIC(r8169) didn't link up after resuming from suspend Status in linux-signed-hwe-6.8 package in Ubuntu: Fix Released Bug description: [Summary] During the SRU testing, I found a hp laptop always timeout after suspend test, after checking I found that the NIC didn't link up. Part of journal log as follows: Sep 12 11:13:01 ubuntu kernel: PM: suspend entry (s2idle) ... ... Sep 12 11:13:10 ubuntu kernel: PM: suspend exit ... Sep 12 11:13:14 ubuntu kernel: r8169 :02:00.1 enp2s0f1: PCI error (cmd = 0x0407, status_errs = 0x) [Expected result] SRU test can continue after suspend test. [Actual result] SRU test times out and NIC is down. [Additional information] Following are the DUTs that are impacted. https://certification.canonical.com/hardware/202304-31463/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.8.0-44-generic 6.8.0-44.44~22.04.1 ProcVersionSignature: Ubuntu 6.8.0-44.44~22.04.1-generic 6.8.12 Uname: Linux 6.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail Date: Thu Sep 12 11:16:43 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20230920-537 InstallationDate: Installed on 2024-09-11 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20230920-537 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.8 UpgradeStatus: No upgrade log present (probably fresh install) X-HWE-Bug: Bug #2087507 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.8/+bug/2080454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-lowlatency/5.15.0-132.142)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency (5.15.0-132.142) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-450-server/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-restricted-modules-lowlatency [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 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 2077731] Re: [SRU] riscv64 EDK 2 crashes in KVM based emulation
I'll let Heinrich reply because he's the one driving the upstream effort. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-riscv in Ubuntu. https://bugs.launchpad.net/bugs/2077731 Title: [SRU] riscv64 EDK 2 crashes in KVM based emulation Status in edk2 package in Ubuntu: Fix Released Status in linux-meta-riscv package in Ubuntu: Invalid Status in qemu package in Ubuntu: New Status in edk2 source package in Noble: Fix Released Status in linux-meta-riscv source package in Noble: Invalid Status in qemu source package in Noble: New Status in edk2 source package in Oracular: Fix Released Status in linux-meta-riscv source package in Oracular: Invalid Status in qemu source package in Oracular: New Bug description: [ Impact ] When running EDK2 as payload for QEMU using KVM a crash occurs in the VM: $ qemu-system-riscv64 -M virt,acpi=off -accel kvm -m 4096 -nographic -drive if=pflash,format=raw,unit=0,file=RISCV_VIRT_CODE.fd,readonly=on -drive if=pflash,format=raw,unit=1,file=RISCV_VIRT_VARS.fd RISCV64 Exception Type - 0002(EXCEPT_RISCV_ILLEGAL_INST) t0 = 0x083FFFB28t1 = 0x083238BC8 t2 = 0x0t3 = 0x0 t4 = 0x0t5 = 0x0 t6 = 0x0s0 = 0x083FFFBC0 s1 = 0x0s2 = 0x0 s3 = 0x0s4 = 0x0 s5 = 0x0s6 = 0x0 s7 = 0x0s8 = 0x0 s9 = 0x0 s10 = 0x0 s11 = 0x0a0 = 0x17E1DDD10 a1 = 0x00021a2 = 0x17E1B1A80 a3 = 0x00032a4 = 0x00021 a5 = 0x00021a6 = 0x0832391E0 a7 = 0x083FFFA64 zero = 0x0 ra = 0x17E0AFA08sp = 0x4 gp = 0x0tp = 0x0 sepc = 0x17E0B0824 sstatus = 0x20120 stval = 0x0D20787D3 QEMU: Terminated [ Test Plan ] To reproduce the issue: Run RISC-V virtual machine as described in https://wiki.ubuntu.com/RISC-V/QEMU. sudo apt-get update sudo apt-get install qemu-efi-riscv64 qemu-system-misc cp /usr/share/qemu-efi-riscv64/RISCV_VIRT_*.fd . qemu-system-riscv64 \ -M virt,acpi=off -accel tcg -m 1024 \ -nographic \ -drive if=pflash,format=raw,unit=0,file=RISCV_VIRT_CODE.fd,readonly=on \ -drive if=pflash,format=raw,unit=1,file=RISCV_VIRT_VARS.fd # In the EFI shell reset -s sudo modprobe kvm sudo qemu-system-riscv64 \ -M virt,acpi=off -accel kvm -m 1024 \ -nographic \ -drive if=pflash,format=raw,unit=0,file=RISCV_VIRT_CODE.fd,readonly=on \ -drive if=pflash,format=raw,unit=1,file=RISCV_VIRT_VARS.fd # A crash occurs # RISCV64 Exception Type - 0002(EXCEPT_RISCV_ILLEGAL_INST) # Terminate emulation with [ Where problems could occur ] The change that has been merged into upstream EDK II with merge request https://github.com/tianocore/edk2/pull/6210 only influences the state of the floating point unit. If the patch were incorrect, it could result in a failure to boot. [ Other Info ] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/2077731/+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 2077731] Re: [SRU] riscv64 EDK 2 crashes in KVM based emulation
Is qemu still in need for a fix here? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-riscv in Ubuntu. https://bugs.launchpad.net/bugs/2077731 Title: [SRU] riscv64 EDK 2 crashes in KVM based emulation Status in edk2 package in Ubuntu: Fix Released Status in linux-meta-riscv package in Ubuntu: Invalid Status in qemu package in Ubuntu: New Status in edk2 source package in Noble: Fix Released Status in linux-meta-riscv source package in Noble: Invalid Status in qemu source package in Noble: New Status in edk2 source package in Oracular: Fix Released Status in linux-meta-riscv source package in Oracular: Invalid Status in qemu source package in Oracular: New Bug description: [ Impact ] When running EDK2 as payload for QEMU using KVM a crash occurs in the VM: $ qemu-system-riscv64 -M virt,acpi=off -accel kvm -m 4096 -nographic -drive if=pflash,format=raw,unit=0,file=RISCV_VIRT_CODE.fd,readonly=on -drive if=pflash,format=raw,unit=1,file=RISCV_VIRT_VARS.fd RISCV64 Exception Type - 0002(EXCEPT_RISCV_ILLEGAL_INST) t0 = 0x083FFFB28t1 = 0x083238BC8 t2 = 0x0t3 = 0x0 t4 = 0x0t5 = 0x0 t6 = 0x0s0 = 0x083FFFBC0 s1 = 0x0s2 = 0x0 s3 = 0x0s4 = 0x0 s5 = 0x0s6 = 0x0 s7 = 0x0s8 = 0x0 s9 = 0x0 s10 = 0x0 s11 = 0x0a0 = 0x17E1DDD10 a1 = 0x00021a2 = 0x17E1B1A80 a3 = 0x00032a4 = 0x00021 a5 = 0x00021a6 = 0x0832391E0 a7 = 0x083FFFA64 zero = 0x0 ra = 0x17E0AFA08sp = 0x4 gp = 0x0tp = 0x0 sepc = 0x17E0B0824 sstatus = 0x20120 stval = 0x0D20787D3 QEMU: Terminated [ Test Plan ] To reproduce the issue: Run RISC-V virtual machine as described in https://wiki.ubuntu.com/RISC-V/QEMU. sudo apt-get update sudo apt-get install qemu-efi-riscv64 qemu-system-misc cp /usr/share/qemu-efi-riscv64/RISCV_VIRT_*.fd . qemu-system-riscv64 \ -M virt,acpi=off -accel tcg -m 1024 \ -nographic \ -drive if=pflash,format=raw,unit=0,file=RISCV_VIRT_CODE.fd,readonly=on \ -drive if=pflash,format=raw,unit=1,file=RISCV_VIRT_VARS.fd # In the EFI shell reset -s sudo modprobe kvm sudo qemu-system-riscv64 \ -M virt,acpi=off -accel kvm -m 1024 \ -nographic \ -drive if=pflash,format=raw,unit=0,file=RISCV_VIRT_CODE.fd,readonly=on \ -drive if=pflash,format=raw,unit=1,file=RISCV_VIRT_VARS.fd # A crash occurs # RISCV64 Exception Type - 0002(EXCEPT_RISCV_ILLEGAL_INST) # Terminate emulation with [ Where problems could occur ] The change that has been merged into upstream EDK II with merge request https://github.com/tianocore/edk2/pull/6210 only influences the state of the floating point unit. If the patch were incorrect, it could result in a failure to boot. [ Other Info ] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/2077731/+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 2086606] Re: Add list of source files to linux-buildinfo
** Changed in: linux-realtime (Ubuntu) Status: New => Fix Committed ** Changed in: linux-realtime (Ubuntu) Assignee: (unassigned) => Kevin Becker (kevinbecker) -- 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/2086606 Title: Add list of source files to linux-buildinfo Status in linux package in Ubuntu: Fix Committed Status in linux-aws package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-gkeop package in Ubuntu: New Status in linux-ibm package in Ubuntu: Fix Committed Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Status in linux-lowlatency-hwe-6.8 package in Ubuntu: New Status in linux-oem-6.11 package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Status in linux-realtime package in Ubuntu: Fix Committed Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-ibm source package in Focal: New Status in linux-lowlatency source package in Focal: New Status in linux source package in Jammy: Fix Committed Status in linux-ibm source package in Jammy: New Status in linux-lowlatency source package in Jammy: New Status in linux-lowlatency-hwe-6.8 source package in Jammy: Fix Committed Status in linux-raspi source package in Jammy: Fix Committed Status in linux source package in Noble: Fix Committed Status in linux-ibm source package in Noble: New Status in linux-lowlatency source package in Noble: Fix Committed Status in linux source package in Oracular: Fix Committed Status in linux-ibm source package in Oracular: New Status in linux-lowlatency source package in Oracular: Fix Committed Status in linux source package in Plucky: Fix Committed Status in linux-ibm source package in Plucky: Fix Committed Status in linux-lowlatency source package in Plucky: New Bug description: [Impact] For CVE triaging, it's helpful to have an exact list of the source files used for a build. Add that information to the linux-buildinfo packages. [Test Case] Check content of linux-buildinfo packages of the individual kernels. Test packages for Noble, Jammy and Focal: https://launchpad.net/~juergh/+archive/ubuntu/linux/+packages [Where Problems Could Occur] Build failures. This does not change the functionality of any of the kernel packages but just adds another text file to the linux-buildinfo packages so should not cause any user visible issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086606/+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/6.11.0-1009.9)
All autopkgtests for the newly accepted linux-meta-azure (6.11.0-1009.9) for oracular have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/1:0~89.12325-git36c5be1a-0ubuntu1 (amd64, arm64) snapd/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/oracular/update_excuses.html#linux-meta-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux 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 2091719] Re: BTRFS kernel panic on btrfs_remove_qgroup
** Also affects: linux (Ubuntu Oracular) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Oracular) Status: New => In Progress ** Changed in: linux (Ubuntu Oracular) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Oracular) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Summary changed: - BTRFS kernel panic on btrfs_remove_qgroup + btrfs will WARN_ON() in btrfs_remove_qgroup() unnecessarily ** Description changed: - We are able to trigger a kernel oops in the btrfs code from userspace: + BugLink: https://bugs.launchpad.net/bugs/2091719 - [ 46.597006] Kernel panic - not syncing: kernel: panic_on_warn set ... - [ 46.597474] CPU: 0 PID: 1316 Comm: (sd-clean) Not tainted 6.8.0-50-generic #51-Ubuntu - [ 46.597660] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-3.fc41 04/01/2014 - [ 46.597882] Call Trace: - [ 46.597948] - [ 46.598028] dump_stack_lvl+0x27/0xa0 - [ 46.598115] dump_stack+0x10/0x20 - [ 46.598222] panic+0x366/0x3c0 - [ 46.598319] ? btrfs_remove_qgroup+0x271/0x490 [btrfs] - [ 46.598517] check_panic_on_warn+0x4f/0x60 - [ 46.598609] __warn+0x95/0x160 - [ 46.598703] ? btrfs_remove_qgroup+0x271/0x490 [btrfs] - [ 46.598932] report_bug+0x17e/0x1b0 - [ 46.599245] handle_bug+0x51/0xa0 - [ 46.599414] exc_invalid_op+0x18/0x80 - [ 46.599645] asm_exc_invalid_op+0x1b/0x20 - [ 46.599794] RIP: 0010:btrfs_remove_qgroup+0x271/0x490 [btrfs] - [ 46.600073] Code: c0 0f 85 27 fe ff ff 48 8b 43 b0 4c 39 f0 75 d5 4d 8d b5 e0 08 00 00 4c 89 f7 e8 8a 45 19 e2 48 83 7b 98 00 0f 84 52 01 00 00 <0f> 0b 49 8b 45 10 a8 10 74 42 41 f6 85 d0 08 00 00 0c 75 38 48 83 - [ 46.600516] RSP: 0018:a0a0c30b3d58 EFLAGS: 00010206 - [ 46.600640] RAX: RBX: 958787663cb8 RCX: - [ 46.600826] RDX: RSI: RDI: - [ 46.601025] RBP: a0a0c30b3dc0 R08: R09: - [ 46.601199] R10: R11: R12: 00ff010f - [ 46.601385] R13: 95878b73 R14: 95878b7308e0 R15: - [ 46.601579] ? btrfs_remove_qgroup+0x266/0x490 [btrfs] - [ 46.601867] btrfs_ioctl+0x12b9/0x13a0 [btrfs] - [ 46.602100] ? srso_alias_return_thunk+0x5/0xfbef5 - [ 46.602575] ? __seccomp_filter+0x368/0x570 - [ 46.602696] ? __fput+0x15e/0x2e0 - [ 46.602993] __x64_sys_ioctl+0xa3/0xf0 - [ 46.603143] x64_sys_call+0x12a3/0x25a0 - [ 46.603379] do_syscall_64+0x7f/0x180 - [ 46.603557] ? srso_alias_return_thunk+0x5/0xfbef5 - [ 46.603680] ? do_syscall_64+0x8c/0x180 - [ 46.603774] ? srso_alias_return_thunk+0x5/0xfbef5 - [ 46.603898] ? syscall_exit_to_user_mode+0x86/0x260 - [ 46.604043] ? srso_alias_return_thunk+0x5/0xfbef5 - [ 46.604155] ? do_syscall_64+0x8c/0x180 - [ 46.604248] ? do_syscall_64+0x8c/0x180 - [ 46.604341] ? srso_alias_return_thunk+0x5/0xfbef5 - [ 46.604693] entry_SYSCALL_64_after_hwframe+0x78/0x80 - [ 46.605029] RIP: 0033:0x7c2fbeb24ded - [ 46.605283] Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1a 48 8b 45 c8 64 48 2b 04 25 28 00 00 00 - [ 46.606374] RSP: 002b:7ffe3e103770 EFLAGS: 0246 ORIG_RAX: 0010 - [ 46.607365] RAX: ffda RBX: RCX: 7c2fbeb24ded - [ 46.607872] RDX: 7ffe3e1037d0 RSI: 4010942a RDI: 0016 - [ 46.608856] RBP: 7ffe3e1037c0 R08: 0069 R09: - [ 46.609477] R10: R11: 0246 R12: 0016 - [ 46.609672] R13: R14: 00ff010f R15: 0016 - [ 46.609862] - [ 46.611054] Kernel Offset: 0x2060 from 0x8100 (relocation range: 0x8000-0xbfff) + [Impact] - This happens on Ubuntu Noble since the kernel update to 6.8.0-50-generic - which was promoted from proposed to updates this week, it did not happen - before. The upstream systemd CI on Github reproduces this issue - consistently, e.g.: + The following commit for noble and oracular introduced two new WARN_ON() calls + in btrfs qgroup removals, and even though the author at the time believed they + would not be reachable, it turns out it can happen quite frequently in the + right conditions. + + ubuntu-noble b2ad25ba539452f492805e5f7d94e80894aa860f + commit a776bf5f3c2300cfdf8a195663460b1793ac9847 + Author: Qu Wenruo + Date: Fri Apr 19 14:29:32 2024 +0930 + Subject: btrfs: slightly loosen the requirement for qgroup removal + Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a776bf5f3c2300cfdf8a195663460b1793ac9847 + + $ git describe --contains b2ad25ba539452f492805e5f7d94e80894aa860f + Ubuntu-6.8.0-50.51~143 + + This primarily affects the systemd CI that runs integra
[Kernel-packages] [Bug 2092384] Re: [SRU] Introduce support for RTL8125BPH 2.5 GbE controller.
** Changed in: linux-firmware (Ubuntu Noble) Assignee: (unassigned) => Leo Lin (0xff07) ** Changed in: linux-firmware (Ubuntu Oracular) Assignee: (unassigned) => Leo Lin (0xff07) ** Changed in: linux-firmware (Ubuntu Plucky) Assignee: (unassigned) => Leo Lin (0xff07) ** Changed in: linux-oem-6.11 (Ubuntu Noble) Assignee: (unassigned) => Leo Lin (0xff07) ** Changed in: linux-oem-6.11 (Ubuntu Oracular) Assignee: (unassigned) => Leo Lin (0xff07) ** Changed in: linux-oem-6.11 (Ubuntu Plucky) Assignee: (unassigned) => Leo Lin (0xff07) -- 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/2092384 Title: [SRU] Introduce support for RTL8125BPH 2.5 GbE controller. Status in HWE Next: New Status in linux-firmware package in Ubuntu: Confirmed Status in linux-oem-6.11 package in Ubuntu: Fix Committed Status in linux-firmware source package in Noble: Confirmed Status in linux-oem-6.11 source package in Noble: In Progress Status in linux-firmware source package in Oracular: Confirmed Status in linux-oem-6.11 source package in Oracular: Invalid Status in linux-firmware source package in Plucky: Confirmed Status in linux-oem-6.11 source package in Plucky: Fix Committed Bug description: [ Impact ] RTL8125BPH 2.5 GbE controller is not functional. [ Fix ] This introduce support for RTL8125BPH 2.5 GbE controller by adding: 1. linux-firmware (already upstreamed[1]). 2. Driver patch[2] and its dependent patches. The dependent patches includes: 1. The PHY support for PHY ID 0x001cc841, which is needed for RTL8125BP 2. Refactoring when support for other models (e.g. RTL8125D, RTL8125D rev.b) were added. 3. Dependent patches for the patch itself. [ Test ] 1. Install the linux-firmware 2. Install the kernel 3. Test basic network function (ping, firefox etc.) [ Where the problem could occur ] Error in the patches and firmware will make the said controller not function properly, which happens to be the status quo. To avoid conflict, the dependent patches include some commits for newer models, in particular the RTL8125D and RTL8125D rev.b. That however doesn't mean those models are readily usable for now. [ Additional information ] [1] https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/393/diffs?commit_id=e1e114f8872f8e5645056a28767cddce77740d39 [2] b11bff90f2ad52c5 (r8169: add support for RTL8125BP rev.b) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2092384/+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 2091719] Re: btrfs will WARN_ON() in btrfs_remove_qgroup() unnecessarily
Hi Luca, The patch is on the Ubuntu Kernel Team mailing list: Cover Letter: https://lists.ubuntu.com/archives/kernel-team/2025-January/156531.html Patch: https://lists.ubuntu.com/archives/kernel-team/2025-January/156530.html Looking at https://kernel.ubuntu.com/, this should be accepted into the 2025.02.10 SRU cycle. There would likely be a kernel in -proposed the week of 10th Feb for verification, and a general release to -updates the week of 10th March. I'll keep an eye out for the Kernel Team's acks, and will let you know when a fixed kernel lands in -proposed. Thanks, Matthew -- 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/2091719 Title: btrfs will WARN_ON() in btrfs_remove_qgroup() unnecessarily Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: In Progress Status in linux source package in Oracular: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/2091719 [Impact] The following commit for noble and oracular introduced two new WARN_ON() calls in btrfs qgroup removals, and even though the author at the time believed they would not be reachable, it turns out it can happen quite frequently in the right conditions. ubuntu-noble b2ad25ba539452f492805e5f7d94e80894aa860f commit a776bf5f3c2300cfdf8a195663460b1793ac9847 Author: Qu Wenruo Date: Fri Apr 19 14:29:32 2024 +0930 Subject: btrfs: slightly loosen the requirement for qgroup removal Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a776bf5f3c2300cfdf8a195663460b1793ac9847 $ git describe --contains b2ad25ba539452f492805e5f7d94e80894aa860f Ubuntu-6.8.0-50.51~143 This primarily affects the systemd CI that runs integration tests on merge: https://github.com/systemd/systemd/actions/runs/12297539029/job/34318915884?pr=35589 Kernel panic - not syncing: kernel: panic_on_warn set ... CPU: 0 PID: 1316 Comm: (sd-clean) Not tainted 6.8.0-50-generic #51-Ubuntu Call Trace: dump_stack_lvl+0x27/0xa0 dump_stack+0x10/0x20 panic+0x366/0x3c0 ? btrfs_remove_qgroup+0x271/0x490 [btrfs] check_panic_on_warn+0x4f/0x60 __warn+0x95/0x160 ? btrfs_remove_qgroup+0x271/0x490 [btrfs] report_bug+0x17e/0x1b0 handle_bug+0x51/0xa0 exc_invalid_op+0x18/0x80 asm_exc_invalid_op+0x1b/0x20 RIP: 0010:btrfs_remove_qgroup+0x271/0x490 [btrfs] Code: c0 0f 85 27 fe ff ff 48 8b 43 b0 4c 39 f0 75 d5 4d 8d b5 e0 08 00 00 4c 89 f7 e8 8a 45 19 e2 48 83 7b 98 00 0f 84 52 01 00 00 <0f> 0b 49 8b 45 10 a8 10 74 42 41 f6 85 d0 08 00 00 0c 75 38 48 83 ? btrfs_remove_qgroup+0x266/0x490 [btrfs] btrfs_ioctl+0x12b9/0x13a0 [btrfs] ? srso_alias_return_thunk+0x5/0xfbef5 ? __seccomp_filter+0x368/0x570 ? __fput+0x15e/0x2e0 __x64_sys_ioctl+0xa3/0xf0 x64_sys_call+0x12a3/0x25a0 do_syscall_64+0x7f/0x180 entry_SYSCALL_64_after_hwframe+0x78/0x80 [Fix] The fix just landed in mainline as: commit c0def46dec9c547679a25fe7552c4bcbec0b0dd2 Author: Qu Wenruo Date: Mon Nov 11 07:29:07 2024 +1030 Subject: btrfs: improve the warning and error message for btrfs_remove_qgroup() Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c0def46dec9c547679a25fe7552c4bcbec0b0dd2 The commit places the WARN_ON behind CONFIG_BTRFS_DEBUG, which silences the warning for most users. It is safe to do so, as noted by the Author, as the user space tool managing the qgroups would rescan them, to fix the inconsistent view. This is needed for both noble and oracular. [Testcase] The upstream systemd CI tests can consistently reproduce the issue, so the test and proposed kernels will be run against the systemd CI for verification. There is a test kernel available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2091719-test If you install it, the systemd CI will run to completion. [Where problems could occur] We are changing the WARN_ON() to occur only when CONFIG_BTRFS_DEBUG is enabled. There is no other change in logic, so functionality should be the same as what we have now. If a regression were to occur, it would affect systems with btrfs filesystems that are utilising subvolumes. It would not likely cause any data loss or disk corruption, as userspace tools should be able to automatically fix up any inconsistent views without user interaction. [Other info] Systemd upstream bisected the issue here: https://github.com/systemd/systemd/pull/35567#issuecomment-2538160543 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2091719/+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-lowlatency/6.11.0-1009.10)
All autopkgtests for the newly accepted linux-meta-lowlatency (6.11.0-1009.10) for oracular have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/1:0~89.12325-git36c5be1a-0ubuntu1 (amd64, 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/oracular/update_excuses.html#linux-meta-lowlatency [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 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 1746340] Re: Samsung SSD corruption (fsck needed)
Switched to a Western Digital 256gb 2280 Nvme Sn810 and problem dissappeared. Maybe original SSD drive was corrupt ¯\_(ツ)_/¯ -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Razer Blade Stealth Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boo
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-realtime/6.11.0-1005.5)
All autopkgtests for the newly accepted linux-meta-realtime (6.11.0-1005.5) for oracular have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/1:0~89.12325-git36c5be1a-0ubuntu1 (amd64, 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/oracular/update_excuses.html#linux-meta-realtime [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 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 2095543] Re: package linux-firmware upgrade failed.
[1281780.201048] SQUASHFS error: xz decompression failed, data probably corrupt [1281780.201082] SQUASHFS error: Failed to read block 0x7b4530: -5 [1281780.202024] SQUASHFS error: xz decompression failed, data probably corrupt [1281780.202054] SQUASHFS error: Failed to read block 0x7b4530: -5 [1281780.203438] SQUASHFS error: xz decompression failed, data probably corrupt [1281780.203469] SQUASHFS error: Failed to read block 0x7b4530: -5 [1385807.050590] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1650: inode #14173: comm dpkg: checksumming directory block 0 [1385919.846619] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1650: inode #14173: comm apport-gtk: checksumming directory block 0 [1385919.846925] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1650: inode #14173: comm apport-gtk: checksumming directory block 0 [1385919.847128] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1650: inode #14173: comm apport-gtk: checksumming directory block 0 [1385919.847307] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1650: inode #14173: comm apport-gtk: checksumming directory block 0 [1385919.847466] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1650: inode #14173: comm apport-gtk: checksumming directory block 0 [1385919.847614] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1650: inode #14173: comm apport-gtk: checksumming directory block 0 [1385937.983986] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1650: inode #14173: comm md5sum: checksumming directory block 0 [1385937.984144] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1650: inode #14173: comm md5sum: checksumming directory block 0 [1385937.984240] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1650: inode #14173: comm md5sum: checksumming directory block 0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2095543 Title: package linux-firmware upgrade failed. Status in linux-firmware package in Ubuntu: Incomplete Bug description: package linux-firmware 20240913.gita34e7a5f-0ubuntu2.2 [modified: lib/firmware/amdgpu/renoir_vcn.bin.zst lib/firmware/amdgpu/sienna_cichlid_rlc.bin.zst] failed to install/upgrade: unable to stat './lib/firmware/cxgb3/ael2005_opt_edc.bin.zst' (which was about to be installed): Bad message I was upgrading my system and it crash. I use the command sudo apt update and supd apt upgrade. ProblemType: Package DistroRelease: Ubuntu 24.10 Package: linux-firmware 20240913.gita34e7a5f-0ubuntu2.2 [modified: lib/firmware/amdgpu/renoir_vcn.bin.zst lib/firmware/amdgpu/sienna_cichlid_rlc.bin.zst] ProcVersionSignature: Ubuntu 6.11.0-1005.5-raspi 6.11.0 Uname: Linux 6.11.0-1005-raspi aarch64 ApportVersion: 2.30.0-0ubuntu4 AptOrdering: linux-firmware:arm64: Install libopenjp2-7:arm64: Install NULL: ConfigurePending Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:fckwan 2508 F pipewire /dev/snd/controlC0: fckwan 2512 F wireplumber /dev/snd/controlC1: fckwan 2512 F wireplumber CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/mmcblk0p1) Date: Wed Jan 22 17:56:53 2025 DpkgTerminalLog: Preparing to unpack .../linux-firmware_20240913.gita34e7a5f-0ubuntu2.4_arm64.deb ... Unpacking linux-firmware (20240913.gita34e7a5f-0ubuntu2.4) over (20240913.gita34e7a5f-0ubuntu2.2) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-firmware_20240913.gita34e7a5f-0ubuntu2.4_arm64.deb (--unpack): unable to stat './lib/firmware/cxgb3/ael2005_opt_edc.bin.zst' (which was about to be installed): Bad message ErrorMessage: unable to stat './lib/firmware/cxgb3/ael2005_opt_edc.bin.zst' (which was about to be installed): Bad message ImageMediaBuild: 20241007.1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller ProcFB: 0 vc4drmfb ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=D8:3A:DD:1D:A5:16 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=zstd multipath=off dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash Python3Details: /usr/bin/python3.12, Python 3.12.7, python3-minimal, 3.12.6-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A SourcePackage: linux-firmware StagingDrivers: bcm2835_isp vc_sm_cma bcm2835_mmal_vchiq bcm2835_v4l2 snd_bcm2835 rpivid_hevc bcm2835_cod
[Kernel-packages] [Bug 2091077] Re: UBSAN: array-index-out-of-bounds in module mt76 in mt76_wcid_cleanup
Verified linux-oem-6.8/noble-proposed version 6.8.0-1021.21.
** Tags removed: verification-needed-noble-linux-oem-6.8
** Tags added: verification-done-noble-linux-oem-6.8
--
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/2091077
Title:
UBSAN: array-index-out-of-bounds in module mt76 in mt76_wcid_cleanup
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.11 source package in Noble:
Fix Released
Status in linux-oem-6.8 source package in Noble:
Fix Committed
Status in linux source package in Oracular:
Fix Released
Status in linux-oem-6.11 source package in Oracular:
Invalid
Status in linux-oem-6.8 source package in Oracular:
Invalid
Status in linux source package in Plucky:
Fix Released
Status in linux-oem-6.11 source package in Plucky:
Invalid
Status in linux-oem-6.8 source package in Plucky:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2091077
[Impact]
UBSAN warning at system shutting down:
```
[ 33.399506] UBSAN: array-index-out-of-bounds in
/home/kernel/COD/linux/drivers/net/wireless/mediatek/mt76/mac80211.c:1532:34
[ 33.399517] index 3 is out of range for type 'mt76_phy *[3]'
[ 33.399523] CPU: 0 UID: 0 PID: 1153 Comm: NetworkManager Not tainted
6.11.0-061100rc7-generic #202409082235
[ 33.399528] Hardware name: HP HP ZBook Ultra 14 inch G1a Mobile Workstation
PC/8D01, BIOS X89 Ver. 89.17.22 09/11/2024
[ 33.399532] Call Trace:
[ 33.399537]
[ 33.399546] show_stack+0x49/0x60
[ 33.399556] dump_stack_lvl+0x5f/0x90
[ 33.399573] dump_stack+0x10/0x18
[ 33.399576] ubsan_epilogue+0x9/0x40
[ 33.399581] __ubsan_handle_out_of_bounds.cold+0x44/0x49
[ 33.399584] mt76_wcid_cleanup+0x269/0x280 [mt76]
[ 33.399603] ? mt76_connac_mcu_uni_add_dev+0x15a/0x200 [mt76_connac_lib]
[ 33.399620] mt792x_mac_link_bss_remove+0x136/0x190 [mt792x_lib]
[ 33.399627] mt792x_remove_interface+0x7f/0xd0 [mt792x_lib]
```
[Fix]
Proposed fix commit 862bf7cbd772c2bad570ef0c5b5556a1330656dd ("wifi:
mt76: mt7915: fix oops on non-dbdc mt7986") from v6.12-rc1. The origin
of this warning, commit 0335c034e7265 ("wifi: mt76: fix race condition
related to checking tx queue fill status"), traces back to v6.7-rc1.
[Test Case]
1. install kernel from -proposed, and boot from it,
2. shut down the device under test,
3. reboot and search dmesg of the last boot for that UBSAN warning.
[Where problems could occur]
No. This calls `mt76_dev_phy` to ensure the right phy ref is returned.
[Other Info]
While the affected commit was first introduced in v6.7, nominating all
kernels since then: unstable, oracular, oem-6.11, noble, and oem-6.8.
== original bug report ==
This is a follow-up for bug 2081785.
[ 33.399506] UBSAN: array-index-out-of-bounds in
/home/kernel/COD/linux/drivers/net/wireless/mediatek/mt76/mac80211.c:1532:34
[ 33.399517] index 3 is out of range for type 'mt76_phy *[3]'
[ 33.399523] CPU: 0 UID: 0 PID: 1153 Comm: NetworkManager Not tainted
6.11.0-061100rc7-generic #202409082235
[ 33.399528] Hardware name: HP HP ZBook Ultra 14 inch G1a Mobile Workstation
PC/8D01, BIOS X89 Ver. 89.17.22 09/11/2024
[ 33.399532] Call Trace:
[ 33.399537]
[ 33.399546] show_stack+0x49/0x60
[ 33.399556] dump_stack_lvl+0x5f/0x90
[ 33.399573] dump_stack+0x10/0x18
[ 33.399576] ubsan_epilogue+0x9/0x40
[ 33.399581] __ubsan_handle_out_of_bounds.cold+0x44/0x49
[ 33.399584] mt76_wcid_cleanup+0x269/0x280 [mt76]
[ 33.399603] ? mt76_connac_mcu_uni_add_dev+0x15a/0x200 [mt76_connac_lib]
[ 33.399620] mt792x_mac_link_bss_remove+0x136/0x190 [mt792x_lib]
[ 33.399627] mt792x_remove_interface+0x7f/0xd0 [mt792x_lib]
[ 33.399633] drv_remove_interface+0xf1/0x1b0 [mac80211]
[ 33.399686] ieee80211_do_stop+0x5c0/0x990 [mac80211]
[ 33.399727] ? synchronize_rcu_expedited+0x1f4/0x220
[ 33.399733] ieee80211_stop+0x5c/0x1c0 [mac80211]
[ 33.399765] __dev_close_many+0xae/0x140
[ 33.399768] __dev_change_flags+0xe6/0x230
[ 33.399773] dev_change_flags+0x27/0x80
[ 33.399775] do_setlink+0x39e/0xd90
[ 33.399780] ? genl_family_rcv_msg_doit+0x11c/0x160
[ 33.399785] ? __nla_validate_parse+0x49/0x1b0
[ 33.399790] ? inode_sub_bytes+0x72/0x90
[ 33.399797] __rtnl_newlink+0x5c8/0x760
[ 33.399802] rtnl_newlink+0x77/0xa0
[ 33.399805] rtnetlink_rcv_msg+0x160/0x460
[ 33.399808] ? __legitimize_path+0x30/0x80
[ 33.399812] ? __pfx_rtnetlink_rcv_msg+0x10/0x10
[ 33.399815] netlink_rcv_skb+0x52/0x100
[ 33.399818] rtnetlink_rcv+0x15/0x30
[ 33.399820] netlink_unicast+0x245/0x390
[ 33.399823] netlink_sendmsg+0x214/0x460
[ 33.399826] sys_sendmsg+0x3b1/0x3f0
[ 33.399830] ___sys_sendmsg+0x9a/0xf0
[ 33.39
[Kernel-packages] [Bug 2095543] Re: package linux-firmware upgrade failed.
Hm. It's most certainly not a linux-firmware package problem. Can you retry the upgrade? Maybe memory corruption for some reason. ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2095543 Title: package linux-firmware upgrade failed. Status in linux-firmware package in Ubuntu: Incomplete Bug description: package linux-firmware 20240913.gita34e7a5f-0ubuntu2.2 [modified: lib/firmware/amdgpu/renoir_vcn.bin.zst lib/firmware/amdgpu/sienna_cichlid_rlc.bin.zst] failed to install/upgrade: unable to stat './lib/firmware/cxgb3/ael2005_opt_edc.bin.zst' (which was about to be installed): Bad message I was upgrading my system and it crash. I use the command sudo apt update and supd apt upgrade. ProblemType: Package DistroRelease: Ubuntu 24.10 Package: linux-firmware 20240913.gita34e7a5f-0ubuntu2.2 [modified: lib/firmware/amdgpu/renoir_vcn.bin.zst lib/firmware/amdgpu/sienna_cichlid_rlc.bin.zst] ProcVersionSignature: Ubuntu 6.11.0-1005.5-raspi 6.11.0 Uname: Linux 6.11.0-1005-raspi aarch64 ApportVersion: 2.30.0-0ubuntu4 AptOrdering: linux-firmware:arm64: Install libopenjp2-7:arm64: Install NULL: ConfigurePending Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:fckwan 2508 F pipewire /dev/snd/controlC0: fckwan 2512 F wireplumber /dev/snd/controlC1: fckwan 2512 F wireplumber CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/mmcblk0p1) Date: Wed Jan 22 17:56:53 2025 DpkgTerminalLog: Preparing to unpack .../linux-firmware_20240913.gita34e7a5f-0ubuntu2.4_arm64.deb ... Unpacking linux-firmware (20240913.gita34e7a5f-0ubuntu2.4) over (20240913.gita34e7a5f-0ubuntu2.2) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-firmware_20240913.gita34e7a5f-0ubuntu2.4_arm64.deb (--unpack): unable to stat './lib/firmware/cxgb3/ael2005_opt_edc.bin.zst' (which was about to be installed): Bad message ErrorMessage: unable to stat './lib/firmware/cxgb3/ael2005_opt_edc.bin.zst' (which was about to be installed): Bad message ImageMediaBuild: 20241007.1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller ProcFB: 0 vc4drmfb ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=D8:3A:DD:1D:A5:16 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=zstd multipath=off dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash Python3Details: /usr/bin/python3.12, Python 3.12.7, python3-minimal, 3.12.6-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A SourcePackage: linux-firmware StagingDrivers: bcm2835_isp vc_sm_cma bcm2835_mmal_vchiq bcm2835_v4l2 snd_bcm2835 rpivid_hevc bcm2835_codec Title: package linux-firmware 20240913.gita34e7a5f-0ubuntu2.2 [modified: lib/firmware/amdgpu/renoir_vcn.bin.zst lib/firmware/amdgpu/sienna_cichlid_rlc.bin.zst] failed to install/upgrade: unable to stat './lib/firmware/cxgb3/ael2005_opt_edc.bin.zst' (which was about to be installed): Bad message UpgradeStatus: No upgrade log present (probably fresh install) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2095543/+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 2062972] Re: ntfs partition does not mount with linux 6.8 and CONFIG_BLK_DEV_WRITE_MOUNTED=n
Using the app "Disks" to correct for this problem is a non sequitur to this issue. "Disks" by default does not use ntfs3 it uses ntfs-3g. This issue isn't associated with ntfs-3g. Only with ntfs3. -- 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/2062972 Title: ntfs partition does not mount with linux 6.8 and CONFIG_BLK_DEV_WRITE_MOUNTED=n Status in linux package in Ubuntu: Confirmed Status in ntfs-3g package in Ubuntu: Confirmed Bug description: I am using Ubuntu 24.04 Development Branch (Beta). I am dualbooting it with Windows 11. When I try to mount my NTFS Windows partition via the Ubuntu Dock, I get: "Error mounting /dev/nvme01np3 at /media/chris(my username)/Windows:wrong fs type, bad option, bad superblock on /dev/nvme01np3, missing codepageor helper program, or other error". Output of sudo apt-cache policy ntfs-3g: ntfs-3g: Installed: 1:2022.10.3-1.2ubuntu3 Candidate: 1:2022.10.3-1.2ubuntu3 Version table: *** 1:2022.10.3-1.2ubuntu3 500 500 http://gr.archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ntfs-3g 1:2022.10.3-1.2ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 Uname: Linux 6.8.0-28-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 18:25:55 2024 InstallationDate: Installed on 2024-04-20 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ntfs-3g UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062972/+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 2086606] Re: Add list of source files to linux-buildinfo
** Also affects: linux-oem-6.11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2086606 Title: Add list of source files to linux-buildinfo Status in linux package in Ubuntu: Fix Committed Status in linux-aws package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-gkeop package in Ubuntu: New Status in linux-ibm package in Ubuntu: Fix Committed Status in linux-lowlatency package in Ubuntu: New Status in linux-lowlatency-hwe-6.8 package in Ubuntu: New Status in linux-oem-6.11 package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Status in linux-realtime package in Ubuntu: New Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-ibm source package in Focal: New Status in linux-lowlatency source package in Focal: New Status in linux source package in Jammy: Fix Committed Status in linux-ibm source package in Jammy: New Status in linux-lowlatency source package in Jammy: New Status in linux-lowlatency-hwe-6.8 source package in Jammy: Fix Committed Status in linux-raspi source package in Jammy: Fix Committed Status in linux source package in Noble: Fix Committed Status in linux-ibm source package in Noble: New Status in linux-lowlatency source package in Noble: Fix Committed Status in linux source package in Oracular: Fix Committed Status in linux-ibm source package in Oracular: New Status in linux-lowlatency source package in Oracular: Fix Committed Status in linux source package in Plucky: Fix Committed Status in linux-ibm source package in Plucky: Fix Committed Status in linux-lowlatency source package in Plucky: New Bug description: [Impact] For CVE triaging, it's helpful to have an exact list of the source files used for a build. Add that information to the linux-buildinfo packages. [Test Case] Check content of linux-buildinfo packages of the individual kernels. Test packages for Noble, Jammy and Focal: https://launchpad.net/~juergh/+archive/ubuntu/linux/+packages [Where Problems Could Occur] Build failures. This does not change the functionality of any of the kernel packages but just adds another text file to the linux-buildinfo packages so should not cause any user visible issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086606/+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 2086606] Re: Add list of source files to linux-buildinfo
** Also 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-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2086606 Title: Add list of source files to linux-buildinfo Status in linux package in Ubuntu: Fix Committed Status in linux-aws package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-gkeop package in Ubuntu: New Status in linux-ibm package in Ubuntu: Fix Committed Status in linux-lowlatency package in Ubuntu: New Status in linux-lowlatency-hwe-6.8 package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Status in linux-realtime package in Ubuntu: New Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-ibm source package in Focal: New Status in linux-lowlatency source package in Focal: New Status in linux source package in Jammy: Fix Committed Status in linux-ibm source package in Jammy: New Status in linux-lowlatency source package in Jammy: New Status in linux-lowlatency-hwe-6.8 source package in Jammy: Fix Committed Status in linux-raspi source package in Jammy: Fix Committed Status in linux source package in Noble: Fix Committed Status in linux-ibm source package in Noble: New Status in linux-lowlatency source package in Noble: Fix Committed Status in linux source package in Oracular: Fix Committed Status in linux-ibm source package in Oracular: New Status in linux-lowlatency source package in Oracular: Fix Committed Status in linux source package in Plucky: Fix Committed Status in linux-ibm source package in Plucky: Fix Committed Status in linux-lowlatency source package in Plucky: New Bug description: [Impact] For CVE triaging, it's helpful to have an exact list of the source files used for a build. Add that information to the linux-buildinfo packages. [Test Case] Check content of linux-buildinfo packages of the individual kernels. Test packages for Noble, Jammy and Focal: https://launchpad.net/~juergh/+archive/ubuntu/linux/+packages [Where Problems Could Occur] Build failures. This does not change the functionality of any of the kernel packages but just adds another text file to the linux-buildinfo packages so should not cause any user visible issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086606/+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 2022824] Re: [amdgpu] random blue/pink frames in the desktop
It seems like the random blue/pink frames issue might be caused by your GPU's power state or a driver problem. Since the issue doesn’t happen during fullscreen games or with two monitors (when your VRAM clock is boosted), try forcing your GPU to run at a higher power state all the time. You can do this by enabling the "performance" power profile in the AMD GPU settings using a tool like `CoreCtrl` or by adding the kernel parameter `amdgpu.ppfeaturemask=0x` to unlock full GPU features. After making this change, reboot your system. If the issue persists, try updating to the latest Mesa drivers or switch to the `amdgpu-pro` drivers. I had the same issue while playing https://www.clashofclansmods.com/clash-of-clans-mod-apk-pc/. But the issue was resolved thankfully. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2022824 Title: [amdgpu] random blue/pink frames in the desktop Status in linux-hwe-5.19 package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: I am running a fresh install of ubuntu 22.04 with kde-plasma-desktop. every 1-2 minutes, there will be a random blue/pink frame(i'm not sure of the color because it only appears for a short time). I don't get this problem in fullscreen games running with dxvk and the random frames didn't show when I recorded my desktop with obs studio. I also got this problem in gnome(on wayland). When I have a dxvk game running or when I have 2 monitors connected, I don't get this issue. One thing to note is that when I have 2 monitors connected, my gpu will boost its vram clock to 2000mhz. what I tried: -rebooting -updating -disabling blur in kde settings -lowering my refresh rate from 144hz to 120hz ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Sat Jun 3 00:45:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT / 6800M] [1002:73df] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Navi 22 [Radeon RX 6700/6700 XT / 6800M] [1043:05d7] InstallationDate: Installed on 2023-06-01 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=ca576fb0-08b4-45d8-aadd-83e9df696ff2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: B450M Pro4-F dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd05/10/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4-F:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2022824/+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 2095287] Re: Enable DP tunnel on xe driver(for lunar lake platform)
** Tags added: cpl jira-cpl-6 oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.11 in Ubuntu. https://bugs.launchpad.net/bugs/2095287 Title: Enable DP tunnel on xe driver(for lunar lake platform) Status in HWE Next: New Status in linux-oem-6.11 package in Ubuntu: New Status in linux-oem-6.11 source package in Noble: In Progress Bug description: [Impact] TBT monitors can not reach 4K@60Hz with two 4K@60Hz monitors connected to dock on Lunar lake platform. [Fix] Intel provide a fix for this issue. 73900dce57e4 drm/xe/dp: Enable DP tunneling [Test] 1. Connect Dell dock to the lunar lake platform. 2. Plug in two/three 4K@60Hz monitor to the Dock(include one TBT monitor connected at the end) 3. all monitors can reach 4K@60Hz [Where problems could occur] I can't see any issues may occur while enabling the DP tunneling on xe driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2095287/+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 2091719] Re: BTRFS kernel panic on btrfs_remove_qgroup
Hi Luca, The commit has now landed in mainline as: commit c0def46dec9c547679a25fe7552c4bcbec0b0dd2 Author: Qu Wenruo Date: Mon Nov 11 07:29:07 2024 +1030 Subject: btrfs: improve the warning and error message for btrfs_remove_qgroup() Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c0def46dec9c547679a25fe7552c4bcbec0b0dd2 I will write up a SRU template, and get the patch on the Kernel Team mailing list. Thanks, Matthew -- 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/2091719 Title: BTRFS kernel panic on btrfs_remove_qgroup Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: In Progress Bug description: We are able to trigger a kernel oops in the btrfs code from userspace: [ 46.597006] Kernel panic - not syncing: kernel: panic_on_warn set ... [ 46.597474] CPU: 0 PID: 1316 Comm: (sd-clean) Not tainted 6.8.0-50-generic #51-Ubuntu [ 46.597660] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-3.fc41 04/01/2014 [ 46.597882] Call Trace: [ 46.597948] [ 46.598028] dump_stack_lvl+0x27/0xa0 [ 46.598115] dump_stack+0x10/0x20 [ 46.598222] panic+0x366/0x3c0 [ 46.598319] ? btrfs_remove_qgroup+0x271/0x490 [btrfs] [ 46.598517] check_panic_on_warn+0x4f/0x60 [ 46.598609] __warn+0x95/0x160 [ 46.598703] ? btrfs_remove_qgroup+0x271/0x490 [btrfs] [ 46.598932] report_bug+0x17e/0x1b0 [ 46.599245] handle_bug+0x51/0xa0 [ 46.599414] exc_invalid_op+0x18/0x80 [ 46.599645] asm_exc_invalid_op+0x1b/0x20 [ 46.599794] RIP: 0010:btrfs_remove_qgroup+0x271/0x490 [btrfs] [ 46.600073] Code: c0 0f 85 27 fe ff ff 48 8b 43 b0 4c 39 f0 75 d5 4d 8d b5 e0 08 00 00 4c 89 f7 e8 8a 45 19 e2 48 83 7b 98 00 0f 84 52 01 00 00 <0f> 0b 49 8b 45 10 a8 10 74 42 41 f6 85 d0 08 00 00 0c 75 38 48 83 [ 46.600516] RSP: 0018:a0a0c30b3d58 EFLAGS: 00010206 [ 46.600640] RAX: RBX: 958787663cb8 RCX: [ 46.600826] RDX: RSI: RDI: [ 46.601025] RBP: a0a0c30b3dc0 R08: R09: [ 46.601199] R10: R11: R12: 00ff010f [ 46.601385] R13: 95878b73 R14: 95878b7308e0 R15: [ 46.601579] ? btrfs_remove_qgroup+0x266/0x490 [btrfs] [ 46.601867] btrfs_ioctl+0x12b9/0x13a0 [btrfs] [ 46.602100] ? srso_alias_return_thunk+0x5/0xfbef5 [ 46.602575] ? __seccomp_filter+0x368/0x570 [ 46.602696] ? __fput+0x15e/0x2e0 [ 46.602993] __x64_sys_ioctl+0xa3/0xf0 [ 46.603143] x64_sys_call+0x12a3/0x25a0 [ 46.603379] do_syscall_64+0x7f/0x180 [ 46.603557] ? srso_alias_return_thunk+0x5/0xfbef5 [ 46.603680] ? do_syscall_64+0x8c/0x180 [ 46.603774] ? srso_alias_return_thunk+0x5/0xfbef5 [ 46.603898] ? syscall_exit_to_user_mode+0x86/0x260 [ 46.604043] ? srso_alias_return_thunk+0x5/0xfbef5 [ 46.604155] ? do_syscall_64+0x8c/0x180 [ 46.604248] ? do_syscall_64+0x8c/0x180 [ 46.604341] ? srso_alias_return_thunk+0x5/0xfbef5 [ 46.604693] entry_SYSCALL_64_after_hwframe+0x78/0x80 [ 46.605029] RIP: 0033:0x7c2fbeb24ded [ 46.605283] Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1a 48 8b 45 c8 64 48 2b 04 25 28 00 00 00 [ 46.606374] RSP: 002b:7ffe3e103770 EFLAGS: 0246 ORIG_RAX: 0010 [ 46.607365] RAX: ffda RBX: RCX: 7c2fbeb24ded [ 46.607872] RDX: 7ffe3e1037d0 RSI: 4010942a RDI: 0016 [ 46.608856] RBP: 7ffe3e1037c0 R08: 0069 R09: [ 46.609477] R10: R11: 0246 R12: 0016 [ 46.609672] R13: R14: 00ff010f R15: 0016 [ 46.609862] [ 46.611054] Kernel Offset: 0x2060 from 0x8100 (relocation range: 0x8000-0xbfff) This happens on Ubuntu Noble since the kernel update to 6.8.0-50-generic which was promoted from proposed to updates this week, it did not happen before. The upstream systemd CI on Github reproduces this issue consistently, e.g.: https://github.com/systemd/systemd/actions/runs/12297539029/job/34318915884?pr=35589 It also happens on the newest upstream kernel, and was reproduced with the same backtrace on Archlinux too. It was bisected to one of the following upstream BTRFS commits listed in this Github comment: https://github.com/systemd/systemd/pull/35567#issuecomment-2538160543 A fix has been proposed by SUSE and tested on Archlinux, and confirmed to solve the crash: https://github.com/btrfs/linux/commit/c61ffaa0a3d9a2094e24d1f
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-lowlatency/5.15.0.132.119)
All autopkgtests for the newly accepted linux-meta-lowlatency (5.15.0.132.119) for jammy have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/11510-0ubuntu1~22.04.1 (amd64, arm64) linux-lowlatency/5.15.0-132.142 (amd64, arm64) lttng-modules/2.13.8-1~ubuntu22.04.0 (amd64, arm64) zfs-linux/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-lowlatency [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 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 2090880] Re: Azure: backport SMB lease key fixes
This bug is awaiting verification that the linux-azure/6.8.0-1022.26
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-azure' to 'verification-done-noble-
linux-azure'. If the problem still exists, change the tag 'verification-
needed-noble-linux-azure' to 'verification-failed-noble-linux-azure'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-noble-linux-azure-v2
verification-needed-noble-linux-azure
--
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/2090880
Title:
Azure: backport SMB lease key fixes
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Noble:
Fix Committed
Bug description:
[Impact]
Microsoft has requested for the following bugfixes to be backported
into the noble:linux-azure tree:
2c7d399e551c ("smb: client: reuse file lease key in compound operations")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2c7d399e551ccfd87bcae4ef5573097f3313d779
ffceb7640cbf ("smb: client: do not defer close open handles to deleted files")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ffceb7640cbfe6ea60e7769e107451d63a2fe3d3
71f15c90e785 ("smb: client: retry compound request without reusing lease")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=71f15c90e785d1de4bcd65a279e7256684c25c0d
fc20c523211a ("cifs: fixes for get_inode_info")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fc20c523211a38b87fc850a959cb2149e4fd64b0
ec4535b2a1d7 ("smb: client: fix NULL ptr deref in
cifs_mark_open_handles_for_deleted_file()")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ec4535b2a1d709d3a1fbec26739c672f13c98a7b
f9c169b51b6c ("smb: client: fix double put of @CFILE in smb2_set_path_size()")
https://github.com/torvalds/linux/commit/f9c169b51b6ce20394594ef674d6b10efba31220
3523a3df03c6 ("smb: client: fix double put of @CFILE in smb2_rename_path()")
https://github.com/torvalds/linux/commit/3523a3df03c6f04f7ea9c2e7050102657e331a4f
[Fix]
2c7d399e551c ("smb: client: reuse file lease key in compound operations")
- cherry-pick
ffceb7640cbf ("smb: client: do not defer close open handles to deleted files")
- backported
71f15c90e785 ("smb: client: retry compound request without reusing lease")
- cherry-pick
fc20c523211a ("cifs: fixes for get_inode_info")
- cherry-pick
ec4535b2a1d7 ("smb: client: fix NULL ptr deref in
cifs_mark_open_handles_for_deleted_file()")
- cherry-pick
f9c169b51b6c ("smb: client: fix double put of @CFILE in smb2_set_path_size()")
- backported
3523a3df03c6 ("smb: client: fix double put of @CFILE in smb2_rename_path()")
- cherry-pick
[Test plan]
Build and boot tested, also ran the xfstests for CIFS to ensure basic
functionality was not compromised.
[Where problems could occur]
Although the changes here are somewhat self-contained, the diff is
still sizeable (especially in ffceb7640cbf ("smb: client: do not defer
close open handles to deleted files")), so there is a moderate
regression risk. Issues here would cause hangs and/or faulty behavior
in CIFS filesystems for impacted users.
[Other info]
SF #00391202
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2090880/+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-oem-6.8/6.8.0-1021.21)
All autopkgtests for the newly accepted linux-meta-oem-6.8 (6.8.0-1021.21) for noble have finished running. The following regressions have been reported in tests triggered by the package: dkms/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/noble/update_excuses.html#linux-meta-oem-6.8 [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 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 2093871] Re: Introduce and use sendpages_ok() instead of sendpage_ok() in nvme-tcp and drbg
** Description changed: - Can you please cherry-pick those 2 important commits from upstream? + BugLink: https://bugs.launchpad.net/bugs/2093871 - 1. net: introduce helper sendpages_ok() - (https://github.com/torvalds/linux/commit/23a55f44) + [Impact] - Network drivers are using sendpage_ok() to check the first page of an - iterator in order to disable MSG_SPLICE_PAGES. The iterator can - represent list of contiguous pages. + Currently the nvme-tcp and drbg subsystems try to enable the MSG_SPLICE_PAGES + flag on pages to be written, and when MSG_SPLICE_PAGES is set, eventually it + calls skb_splice_from_iter(), which then checks all pages with sendpage_ok() + to see if all the pages are sendable. - When MSG_SPLICE_PAGES is enabled skb_splice_from_iter() is being used, - it requires all pages in the iterator to be sendable. Therefore it needs - to check that each page is sendable. + At the moment, both subsystems only check the first page in a potentially + contiguous block of pages, if they are sendpage_ok(), and if the first page is, + then it just assumes all the rest are sendpage_ok() too, and sends the I/O off + to eventually be found out by skb_splice_from_iter(). If one or more of the + pages in the contiguous block is not sendpage_ok(), then we get a warn printed, + data transfer is aborted. In the nvme-tcp case, IO then hangs. - The patch introduces a helper sendpages_ok(), it returns true if all the - contiguous pages are sendable. + This patchset introduces sendpages_ok() which iterates over each page in a + contiguous block, checks if it is sendpage_ok(), and only returns true if all + of them are. - Drivers who want to send contiguous pages with MSG_SPLICE_PAGES may use - this helper to check whether the page list is OK. If the helper does not - return true, the driver should remove MSG_SPLICE_PAGES flag. + This resolves the whole MSG_SPLICE_PAGES flag situation, since you can now + depend on the result of sendpages_ok(), instead of just assuming everything is + okay. + This issue is what caused bug 2075110 [0] to be discovered in the first place, + since it was responsible for contigious blocks of pages where the first was + sendpage_ok(), but pages further into the block were not. - 2. nvme-tcp: use sendpages_ok() instead of sendpage_ok() (https://github.com/torvalds/linux/commit/6af7331a) + [0] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2075110 - Currently nvme_tcp_try_send_data() use sendpage_ok() in order to disable - MSG_SPLICE_PAGES, it check the first page of the iterator, the iterator - may represent contiguous pages. + Even with "md/md-bitmap: fix writing non bitmap pages" applied, the issue can + still happen, e.g. with merged IO pages, so this fix is still needed to + eliminate the issue. - MSG_SPLICE_PAGES enables skb_splice_from_iter() which checks all the - pages it sends with sendpage_ok(). + [Fix] - When nvme_tcp_try_send_data() sends an iterator that the first page is - sendable, but one of the other pages isn't skb_splice_from_iter() warns - and aborts the data transfer. + The fixes landed in mainline 6.12-rc1: - Using the new helper sendpages_ok() in order to disable MSG_SPLICE_PAGES - solves the issue. + commit 23a55f4492fcf868d068da31a2cd30c15f46207d + Author: Ofir Gal + Date: Thu Jul 18 11:45:12 2024 +0300 + Subject: net: introduce helper sendpages_ok() + Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=23a55f4492fcf868d068da31a2cd30c15f46207d + + commit 6af7331a70b4888df43ec1d7e1803ae2c43b6981 + Author: Ofir Gal + Date: Thu Jul 18 11:45:13 2024 +0300 + Subject: nvme-tcp: use sendpages_ok() instead of sendpage_ok() + Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6af7331a70b4888df43ec1d7e1803ae2c43b6981 + + commit 7960af373ade3b39e10106ef415e43a1d2aa48c6 + Author: Ofir Gal + Date: Thu Jul 18 11:45:14 2024 +0300 + Subject: drbd: use sendpages_ok() instead of sendpage_ok() + Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7960af373ade3b39e10106ef415e43a1d2aa48c6 + + They are needed for noble and oracular. + + [Testcase] + + This is the same testcase as the original bug 2075110 [0], as the fix is + designed to prevent it or similar other bugs from happening again. + + [0] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2075110 + + Because of this, the fix: + + commit ab99a87542f194f28e2364a42afbf9fb48b1c724 + Author: Ofir Gal + Date: Fri Jun 7 10:27:44 2024 +0300 + Subject: md/md-bitmap: fix writing non bitmap pages + Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab99a87542f194f28e2364a42afbf9fb48b1c724 + + needs to be reverted during your test runs, or you won't see the issue + reproduce. + + You can use this ppa for updated kernels with the revert to trigger the + issue: + + https://launchpad.net/~mruffell/+archive/ubuntu/sf404844-revert + + This
[Kernel-packages] [Bug 2095287] Re: Enable DP tunnel on xe driver(for lunar lake platform)
@acelankao is that means it's not supported on i915? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.11 in Ubuntu. https://bugs.launchpad.net/bugs/2095287 Title: Enable DP tunnel on xe driver(for lunar lake platform) Status in HWE Next: New Status in linux-oem-6.11 package in Ubuntu: New Status in linux-oem-6.11 source package in Noble: In Progress Bug description: [Impact] TBT monitors can not reach 4K@60Hz with two 4K@60Hz monitors connected to dock on Lunar lake platform. [Fix] Intel provide a fix for this issue. 73900dce57e4 drm/xe/dp: Enable DP tunneling [Test] 1. Connect Dell dock to the lunar lake platform. 2. Plug in two/three 4K@60Hz monitor to the Dock(include one TBT monitor connected at the end) 3. all monitors can reach 4K@60Hz [Where problems could occur] I can't see any issues may occur while enabling the DP tunneling on xe driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2095287/+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 2093871] Re: Introduce and use sendpages_ok() instead of sendpage_ok() in nvme-tcp and drbg
** Summary changed: - Using sendpages_ok() in nvme_tcp_try_send_data() + Introduce and use sendpages_ok() instead of sendpage_ok() in nvme-tcp and drbg -- 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/2093871 Title: Introduce and use sendpages_ok() instead of sendpage_ok() in nvme-tcp and drbg Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: In Progress Status in linux source package in Oracular: In Progress Bug description: Can you please cherry-pick those 2 important commits from upstream? 1. net: introduce helper sendpages_ok() (https://github.com/torvalds/linux/commit/23a55f44) Network drivers are using sendpage_ok() to check the first page of an iterator in order to disable MSG_SPLICE_PAGES. The iterator can represent list of contiguous pages. When MSG_SPLICE_PAGES is enabled skb_splice_from_iter() is being used, it requires all pages in the iterator to be sendable. Therefore it needs to check that each page is sendable. The patch introduces a helper sendpages_ok(), it returns true if all the contiguous pages are sendable. Drivers who want to send contiguous pages with MSG_SPLICE_PAGES may use this helper to check whether the page list is OK. If the helper does not return true, the driver should remove MSG_SPLICE_PAGES flag. 2. nvme-tcp: use sendpages_ok() instead of sendpage_ok() (https://github.com/torvalds/linux/commit/6af7331a) Currently nvme_tcp_try_send_data() use sendpage_ok() in order to disable MSG_SPLICE_PAGES, it check the first page of the iterator, the iterator may represent contiguous pages. MSG_SPLICE_PAGES enables skb_splice_from_iter() which checks all the pages it sends with sendpage_ok(). When nvme_tcp_try_send_data() sends an iterator that the first page is sendable, but one of the other pages isn't skb_splice_from_iter() warns and aborts the data transfer. Using the new helper sendpages_ok() in order to disable MSG_SPLICE_PAGES solves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2093871/+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 2096624] [NEW] [SRU] Add Intel Touch Host Controller drivers
Public bug reported: [Impact] The new touchscreen on Intel LNL is lack of driver support. 00:10.0 Digitizer Pen [0901]: Intel Corporation Device [8086:a848] (rev 10) [Fix] Enable Intel THC driver to support it. [4.122639] input: quicki2c-hid 27C6:012D Touchscreen as /devices/pci:00/:00:10.0/0001:27C6:012D.0003/input/input12 [4.122704] input: quicki2c-hid 27C6:012D as /devices/pci:00/:00:10.0/0001:27C6:012D.0003/input/input13 [Test] Tested on hardware, multi-touch works fine on Wacom and Goodix touchscreens. [Where problems could occur] It introduces a brand new driver, may break hid functions. Because this is a new feature driver, SRU for oracular/plucky/oem-6.11. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux-oem (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: Invalid ** Affects: linux-oem (Ubuntu Noble) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Oracular) Importance: Undecided Status: In Progress ** Affects: linux-oem (Ubuntu Oracular) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Plucky) Importance: Undecided Status: In Progress ** Affects: linux-oem (Ubuntu Plucky) Importance: Undecided Status: Invalid ** Tags: jira-sutton-290 jira-sutton-709 oem-priority ** Tags added: jira-sutton-290 oem-priority ** Tags added: jira-sutton-709 ** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Plucky) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Plucky) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) Status: New => Invalid ** Changed in: linux-oem (Ubuntu Oracular) Status: New => Invalid ** Changed in: linux-oem (Ubuntu Plucky) Status: New => Invalid ** Changed in: linux-oem (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Oracular) Status: New => In Progress ** Changed in: linux (Ubuntu Plucky) Status: New => In Progress ** Description changed: [Impact] The new touchscreen on Intel LNL is lack of driver support. 00:10.0 Digitizer Pen [0901]: Intel Corporation Device [8086:a848] (rev 10) [Fix] Enable Intel THC driver to support it. [4.122639] input: quicki2c-hid 27C6:012D Touchscreen as /devices/pci:00/:00:10.0/0001:27C6:012D.0003/input/input12 [4.122704] input: quicki2c-hid 27C6:012D as /devices/pci:00/:00:10.0/0001:27C6:012D.0003/input/input13 [Test] - Tested on hardware, multi-touch works fine Wacom and Goodix touchscreens. + Tested on hardware, multi-touch works fine on Wacom and Goodix touchscreens. [Where problems could occur] It introduces a brand new driver, may break hid functions. Because this is a new feature driver, SRU for oracular/plucky/oem-6.11. -- 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/2096624 Title: [SRU] Add Intel Touch Host Controller drivers Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem source package in Noble: In Progress Status in linux source package in Oracular: In Progress Status in linux-oem source package in Oracular: Invalid Status in linux source package in Plucky: In Progress Status in linux-oem source package in Plucky: Invalid Bug description: [Impact] The new touchscreen on Intel LNL is lack of driver support. 00:10.0 Digitizer Pen [0901]: Intel Corporation Device [8086:a848] (rev 10) [Fix] Enable Intel THC driver to support it. [4.122639] input: quicki2c-hid 27C6:012D Touchscreen as /devices/pci:00/:00:10.0/0001:27C6:012D.0003/input/input12 [4.122704] input: quicki2c-hid 27C6:012D as /devices/pci:00/:00:10.0/0001:27C6:012D.0003/input/input13 [Test] Tested on hardware, multi-touch works fine on Wacom and Goodix touchscreens. [Where problems could occur] It introduces a brand new driver, may break hid functions. Because this is a new feature driver, SRU for oracular/plucky/oem-6.11. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2096624/+subscriptio
[Kernel-packages] [Bug 2045882] Re: tegra-qspi NVDA1513:00: device reset failed
Hi I had occured the same messages. Is the log asked for GPU to connected a device ( I have no idea what device should be connected) ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045882 Title: tegra-qspi NVDA1513:00: device reset failed Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: The partner report below syslog error related to: Aug 30 09:10:48 localhost kernel: [7.335926] tegra186-gpio NVDA0508:00: invalid resource Aug 30 09:10:48 localhost kernel: [7.341446] tegra186-gpio NVDA0508:00: invalid resource Aug 30 09:10:48 localhost kernel: [ 53.419539] tegra-i2c NVDA0301:00: cannot use DMA: -19 Aug 30 09:10:48 localhost kernel: [ 53.424816] tegra-i2c NVDA0301:00: falling back to PIO Aug 30 09:10:48 localhost kernel: [ 53.508666] tegra-qspi NVDA1513:00: Adding to iommu group 15 Aug 30 09:10:48 localhost kernel: [ 53.510539] tegra-qspi NVDA1513:00: device reset failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2045882/+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 2093871] Re: Using sendpages_ok() in nvme_tcp_try_send_data()
** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Oracular) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Oracular) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Changed in: linux (Ubuntu Oracular) Assignee: (unassigned) => Matthew Ruffell (mruffell) -- 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/2093871 Title: Using sendpages_ok() in nvme_tcp_try_send_data() Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: In Progress Status in linux source package in Oracular: In Progress Bug description: Can you please cherry-pick those 2 important commits from upstream? 1. net: introduce helper sendpages_ok() (https://github.com/torvalds/linux/commit/23a55f44) Network drivers are using sendpage_ok() to check the first page of an iterator in order to disable MSG_SPLICE_PAGES. The iterator can represent list of contiguous pages. When MSG_SPLICE_PAGES is enabled skb_splice_from_iter() is being used, it requires all pages in the iterator to be sendable. Therefore it needs to check that each page is sendable. The patch introduces a helper sendpages_ok(), it returns true if all the contiguous pages are sendable. Drivers who want to send contiguous pages with MSG_SPLICE_PAGES may use this helper to check whether the page list is OK. If the helper does not return true, the driver should remove MSG_SPLICE_PAGES flag. 2. nvme-tcp: use sendpages_ok() instead of sendpage_ok() (https://github.com/torvalds/linux/commit/6af7331a) Currently nvme_tcp_try_send_data() use sendpage_ok() in order to disable MSG_SPLICE_PAGES, it check the first page of the iterator, the iterator may represent contiguous pages. MSG_SPLICE_PAGES enables skb_splice_from_iter() which checks all the pages it sends with sendpage_ok(). When nvme_tcp_try_send_data() sends an iterator that the first page is sendable, but one of the other pages isn't skb_splice_from_iter() warns and aborts the data transfer. Using the new helper sendpages_ok() in order to disable MSG_SPLICE_PAGES solves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2093871/+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-intel-iotg/5.15.0.1073.73)
All autopkgtests for the newly accepted linux-meta-intel-iotg (5.15.0.1073.73) for jammy have finished running. The following regressions have been reported in tests triggered by the package: librem-ec-acpi/unknown (amd64) lime-forensics/unknown (amd64) lttng-modules/unknown (amd64) nvidia-graphics-drivers-450-server/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-intel-iotg [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 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 2095302] Re: Jammy update: v5.15.175 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2095302 Title: Jammy update: v5.15.175 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.175 upstream stable release from git://git.kernel.org/ tcp: check space before adding MPTCP SYN options ALSA: usb-audio: Add implicit feedback quirk for Yamaha THR5 usb: host: max3421-hcd: Correctly abort a USB request. ata: sata_highbank: fix OF node reference leak in highbank_initialize_phys() usb: dwc2: Fix HCD resume usb: dwc2: hcd: Fix GetPortStatus & SetPortFeature usb: dwc2: Fix HCD port connection race usb: ehci-hcd: fix call balance of clocks handling routines usb: gadget: u_serial: Fix the issue that gs_start_io crashed due to accessing null pointer drm/i915: Fix memory leak by correcting cache object name in error handler xfs: update btree keys correctly when _insrec splits an inode root block xfs: don't drop errno values when we fail to ficlone the entire range xfs: return from xfs_symlink_verify early on V4 filesystems xfs: fix scrub tracepoints when inode-rooted btrees are involved bpf, sockmap: Fix update element with same virtio/vsock: Fix accept_queue memory leak exfat: fix potential deadlock on __exfat_get_dentry_set acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl batman-adv: Do not send uninitialized TT changes batman-adv: Remove uninitialized data in full table TT response batman-adv: Do not let TT changes list grows indefinitely tipc: fix NULL deref in cleanup_bearer() selftests: mlxsw: sharedbuffer: Remove h1 ingress test case selftests: mlxsw: sharedbuffer: Remove duplicate test cases ptp: kvm: Use decrypted memory in confidential guest on x86 ptp: kvm: x86: Return EOPNOTSUPP instead of ENODEV from kvm_arch_ptp_init() net: lapb: increase LAPB_HEADER_LEN net: sparx5: fix FDMA performance issue net: sparx5: fix the maximum frame length register ACPI: resource: Fix memory resource type union access cxgb4: use port number to set mac addr qca_spi: Fix clock speed for multiple QCA7000 qca_spi: Make driver probing reliable Documentation: PM: Clarify pm_runtime_resume_and_get() return value net/sched: netem: account for backlog updates from child qdisc bonding: Fix feature propagation of NETIF_F_GSO_ENCAP_ALL team: Fix feature propagation of NETIF_F_GSO_ENCAP_ALL ACPICA: events/evxfregn: don't release the ContextMutex that was never acquired blk-iocost: Avoid using clamp() on inuse in __propagate_weights() bpf: sync_linked_regs() must preserve subreg_def tracing/kprobes: Skip symbol counting logic for module symbols in create_local_trace_kprobe() xen/netfront: fix crash when removing device x86: make get_cpu_vendor() accessible from Xen code objtool/x86: allow syscall instruction x86/static-call: provide a way to do very early static-call updates x86/static-call: Remove early_boot_irqs_disabled check to fix Xen PVH dom0 x86/asm: Make serialize() always_inline x86/xen: don't do PV iret hypercall through hypercall page x86/xen: add central hypercall functions x86/xen: use new hypercall functions instead of hypercall page x86/xen: remove hypercall page ALSA: usb-audio: Fix a DMA to stack memory bug x86/static-call: fix 32-bit build Linux 5.15.175 UBUNTU: Upstream stable to v5.15.175 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2095302/+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 2095199] Re: Focal update: v5.4.288 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2095199 Title: Focal update: v5.4.288 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.288 upstream stable release from git://git.kernel.org/ usb: host: max3421-hcd: Correctly abort a USB request. ata: sata_highbank: fix OF node reference leak in highbank_initialize_phys() usb: dwc2: hcd: Fix GetPortStatus & SetPortFeature usb: ehci-hcd: fix call balance of clocks handling routines usb: gadget: u_serial: Fix the issue that gs_start_io crashed due to accessing null pointer xfs: don't drop errno values when we fail to ficlone the entire range bpf, sockmap: Fix update element with same batman-adv: Do not send uninitialized TT changes batman-adv: Remove uninitialized data in full table TT response batman-adv: Do not let TT changes list grows indefinitely tipc: fix NULL deref in cleanup_bearer() net: lapb: increase LAPB_HEADER_LEN ACPI: resource: Fix memory resource type union access qca_spi: Fix clock speed for multiple QCA7000 qca_spi: Make driver probing reliable net/sched: netem: account for backlog updates from child qdisc ACPICA: events/evxfregn: don't release the ContextMutex that was never acquired blk-iocost: clamp inuse and skip noops in __propagate_weights() blk-iocost: fix weight updates of inner active iocgs blk-iocost: Avoid using clamp() on inuse in __propagate_weights() KVM: arm64: Ignore PMCNTENSET_EL0 while checking for overflow status tracing/kprobes: Skip symbol counting logic for module symbols in create_local_trace_kprobe() xen/netfront: fix crash when removing device ALSA: usb-audio: Fix a DMA to stack memory bug Linux 5.4.288 UBUNTU: Upstream stable to v5.4.288 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2095199/+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 2095283] Re: Jammy update: v5.15.174 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2095283 Title: Jammy update: v5.15.174 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.174 upstream stable release from git://git.kernel.org/ arm64: dts: allwinner: pinephone: Add mount matrix to accelerometer media: imx-jpeg: Set video drvdata before register video device media: i2c: tc358743: Fix crash in the probe error path when using polling media: imx-jpeg: Ensure power suppliers be suspended before detach them media: ts2020: fix null-ptr-deref in ts2020_probe() media: venus: Fix pm_runtime_set_suspended() with runtime pm enabled media: gspca: ov534-ov772x: Fix off-by-one error in set_frame_rate() media: platform: allegro-dvt: Fix possible memory leak in allocate_buffers_internal() media: uvcvideo: Stop stream during unregister ovl: Filter invalid inodes with missing lookup function ftrace: Fix regression with module command in stack_trace_filter vmstat: call fold_vm_zone_numa_events() before show per zone NUMA event iommu/io-pgtable-arm: Fix stage-2 map/unmap for concatenated tables leds: lp55xx: Remove redundant test for invalid channel number clk: qcom: gcc-qcs404: fix initial rate of GPLL3 netlink: terminate outstanding dump on socket close drm/rockchip: vop: Fix a dereferenced before check warning net/mlx5: fs, lock FTE when checking if active net/mlx5e: kTLS, Fix incorrect page refcounting net/mlx5e: CT: Fix null-ptr-deref in add rule err flow samples: pktgen: correct dev to DEV ARM: 9419/1: mm: Fix kernel memory mapping for xip kernels x86/mm: Fix a kdump kernel failure on SME system when CONFIG_IMA_KEXEC=y mm: fix NULL pointer dereference in alloc_pages_bulk_noprof ocfs2: uncache inode which has failed entering the group vdpa/mlx5: Fix PA offset with unaligned starting iotlb map KVM: nVMX: Treat vpid01 as current if L2 is active, but with VPID disabled KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint ocfs2: fix UBSAN warning in ocfs2_verify_volume() nilfs2: fix null-ptr-deref in block_dirty_buffer tracepoint Revert "mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K" drm/bridge: tc358768: Fix DSI command tx mmc: sunxi-mmc: Add D1 MMC variant mmc: sunxi-mmc: Fix A100 compatible description lib/buildid: Fix build ID parsing logic media: dvbdev: fix the logic when DVB_DYNAMIC_MINORS is not set NFSD: initialize copy->cp_clp early in nfsd4_copy for use by trace point NFSD: Async COPY result needs to return a write verifier NFSD: Limit the number of concurrent async COPY operations NFSD: Initialize struct nfsd4_copy earlier NFSD: Never decrement pending_async_copies on error mptcp: cope racing subflow creation in mptcp_rcv_space_adjust mm: revert "mm: shmem: fix data-race in shmem_getattr()" mm: avoid unsafe VMA hook invocation when error arises on mmap hook mm: unconditionally close VMAs on error mm: refactor arch_calc_vm_flag_bits() and arm64 MTE handling mm: resolve faulty mmap_region() error path behaviour NFS: nfs_async_write_reschedule_io must not recurse into the writeback code ASoC: Intel: bytcr_rt5640: Add support for non ACPI instantiated codec ASoC: Intel: bytcr_rt5640: Add DMI quirk for Vexia Edu Atla 10 tablet ASoC: Intel: sst: Support LPE0F28 ACPI HID wifi: iwlwifi: mvm: Use the sync timepoint API in suspend mac80211: fix user-power when emulating chanctx usb: add support for new USB device ID 0x17EF:0x3098 for the r8152 driver selftests/watchdog-test: Fix system accidentally reset after watchdog-test ALSA: hda/realtek: Add subwoofer quirk for Infinix ZERO BOOK 13 x86/amd_nb: Fix compile-testing without CONFIG_AMD_NB net: usb: qmi_wwan: add Quectel RG650V soc: qcom: Add check devm_kasprintf() returned value regulator: rk808: Add apply_bit for BUCK3 on RK809 platform/x86: dell-smbios-base: Extends support to Alienware products platform/x86: dell-wmi-base: Handle META key Lock/Unlock events can: j1939: fix error in J1939 documentation. ASoC: stm: Prevent potential division by zero in stm32_sai_mclk_round_rate() ASoC: stm: Prevent potential divis
[Kernel-packages] [Bug 2095145] Re: Focal update: v5.4.287 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2095145 Title: Focal update: v5.4.287 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.287 upstream stable release from git://git.kernel.org/ netlink: terminate outstanding dump on socket close net/mlx5: fs, lock FTE when checking if active net/mlx5e: kTLS, Fix incorrect page refcounting ocfs2: uncache inode which has failed entering the group KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint ocfs2: fix UBSAN warning in ocfs2_verify_volume() nilfs2: fix null-ptr-deref in block_dirty_buffer tracepoint Revert "mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K" media: dvbdev: fix the logic when DVB_DYNAMIC_MINORS is not set kbuild: Use uname for LINUX_COMPILE_HOST detection mm: revert "mm: shmem: fix data-race in shmem_getattr()" ASoC: Intel: bytcr_rt5640: Add DMI quirk for Vexia Edu Atla 10 tablet mac80211: fix user-power when emulating chanctx selftests/watchdog-test: Fix system accidentally reset after watchdog-test ALSA: hda/realtek: Add subwoofer quirk for Infinix ZERO BOOK 13 x86/amd_nb: Fix compile-testing without CONFIG_AMD_NB net: usb: qmi_wwan: add Quectel RG650V soc: qcom: Add check devm_kasprintf() returned value regulator: rk808: Add apply_bit for BUCK3 on RK809 ASoC: stm: Prevent potential division by zero in stm32_sai_mclk_round_rate() ASoC: stm: Prevent potential division by zero in stm32_sai_get_clk_div() proc/softirqs: replace seq_printf with seq_put_decimal_ull_width ipmr: Fix access to mfc_cache_list without lock held cifs: Fix buffer overflow when parsing NFS reparse points NFSD: Force all NFSv4.2 COPY requests to be synchronous nvme: fix metadata handling in nvme-passthrough mips: asm: fix warning when disabling MIPS_FP_SUPPORT initramfs: avoid filename buffer overrun nvme-pci: fix freeing of the HMB descriptor table m68k: mvme147: Fix SCSI controller IRQ numbers m68k: mvme16x: Add and use "mvme16x.h" m68k: mvme147: Reinstate early console acpi/arm64: Adjust error handling procedure in gtdt_parse_timer_block() s390/syscalls: Avoid creation of arch/arch/ directory hfsplus: don't query the device logical block size multiple times firmware: google: Unregister driver_info on failure and exit in gsmi firmware: google: Unregister driver_info on failure EDAC/bluefield: Fix potential integer overflow EDAC/fsl_ddr: Fix bad bit shift operations crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY crypto: cavium - Fix the if condition to exit loop after timeout crypto: bcm - add error check in the ahash_hmac_init function crypto: cavium - Fix an error handling path in cpt_ucode_load_fw() time: Fix references to _msecs_to_jiffies() handling of values soc: ti: smartreflex: Use IRQF_NO_AUTOEN flag in request_irq() soc: qcom: geni-se: fix array underflow in geni_se_clk_tbl_get() mmc: mmc_spi: drop buggy snprintf() efi/tpm: Pass correct address to memblock_reserve tpm: fix signed/unsigned bug when checking event logs ARM: dts: cubieboard4: Fix DCDC5 regulator constraints regmap: irq: Set lockdep class for hierarchical IRQ domains firmware: arm_scpi: Check the DVFS OPP count returned by the firmware drm/mm: Mark drm_mm_interval_tree*() functions with __maybe_unused wifi: ath9k: add range check for conn_rsp_epid in htc_connect_service() drm/omap: Fix locking in omap_gem_new_dmabuf() wifi: p54: Use IRQF_NO_AUTOEN flag in request_irq() wifi: mwifiex: Use IRQF_NO_AUTOEN flag in request_irq() drm/imx/ipuv3: Use IRQF_NO_AUTOEN flag in request_irq() dt-bindings: vendor-prefixes: Add NeoFidelity, Inc ASoC: fsl_micfil: Drop unnecessary register read ASoC: fsl_micfil: do not define SHIFT/MASK for single bits ASoC: fsl_micfil: use GENMASK to define register bit fields ASoC: fsl_micfil: fix regmap_write_bits usage bpf: Fix the xdp_adjust_tail sample prog issue wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_config_scan() drm/panfrost: Remove unused id_mask from struct panfrost_model drm/msm/adreno: Use IRQF_NO_AUTOEN flag
[Kernel-packages] [Bug 2095327] Re: Jammy update: v5.15.176 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2095327 Title: Jammy update: v5.15.176 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.176 upstream stable release from git://git.kernel.org/ ALSA: usb: Fix UBSAN warning in parse_audio_unit() usb: cdns3: Add quirk flag to enable suspend residency ASoC: Intel: sof_sdw: fix jack detection on ADL-N variant RVP PCI: vmd: Create domain symlink before pci_bus_add_devices() PCI: Add ACS quirk for Broadcom BCM5760X NIC MIPS: Loongson64: DTS: Fix msi node for ls7a usb: dwc2: gadget: Don't write invalid mapped sg entries into dma_desc with iommu enabled i2c: pnx: Fix timeout in wait functions erofs: fix incorrect symlink detection in fast symlink net/smc: check sndbuf_space again after NOSPACE flag is set in smc_poll net/smc: check iparea_offset and ipv6_prefixes_cnt when receiving proposal msg net/smc: check smcd_v2_ext_offset when receiving proposal msg net/smc: check return value of sock_recvmsg when draining clc data netdevsim: prevent bad user input in nsim_dev_health_break_write() ionic: Fix netdev notifier unregister on failure ionic: use ee->offset when returning sprom data net: hinic: Fix cleanup in create_rxqs/txqs() net: ethernet: bgmac-platform: fix an OF node reference leak netfilter: ipset: Fix for recursive locking warning net: mdiobus: fix an OF node reference leak mmc: sdhci-tegra: Remove SDHCI_QUIRK_BROKEN_ADMA_ZEROLEN_DESC quirk chelsio/chtls: prevent potential integer overflow on 32bit i2c: riic: Always round-up when calculating bus period efivarfs: Fix error on non-existent file USB: serial: option: add TCL IK512 MBIM & ECM USB: serial: option: add MeiG Smart SLM770A USB: serial: option: add Netprisma LCUK54 modules for WWAN Ready USB: serial: option: add MediaTek T7XX compositions USB: serial: option: add Telit FE910C04 rmnet compositions drm/modes: Avoid divide by zero harder in drm_mode_vrefresh() hwmon: (tmp513) Don't use "proxy" headers hwmon: (tmp513) Simplify with dev_err_probe() hwmon: (tmp513) Use SI constants from units.h hwmon: (tmp513) Fix interpretation of values of Shunt Voltage and Limit Registers hwmon: (tmp513) Fix Current Register value interpretation hwmon: (tmp513) Fix interpretation of values of Temperature Result and Limit Registers hwmon: (tmp513) Fix division of negative numbers sh: clk: Fix clk_enable() to return 0 on NULL clk zram: refuse to use zero sized block device as backing device btrfs: tree-checker: reject inline extent items with 0 ref count Drivers: hv: util: Avoid accessing a ringbuffer not initialized yet KVM: x86: Play nice with protected guests in complete_hypercall_exit() tracing: Fix test_event_printk() to process entire print argument tracing: Add missing helper functions in event pointer dereference check tracing: Add "%s" check in test_event_printk() NFS/pnfs: Fix a live lock between recalled layouts and layoutget of/irq: Fix using uninitialized variable @addr_len in API of_irq_parse_one() nilfs2: prevent use of deleted inode udmabuf: also check for F_SEAL_FUTURE_WRITE of: Fix error path in of_parse_phandle_with_args_map() of: Fix refcount leakage for OF node returned by __of_get_dma_parent() ceph: validate snapdirname option length when mounting epoll: Add synchronous wakeup support for ep_poll_callback drm/amdgpu: Handle NULL bo->tbo.resource (again) in amdgpu_vm_bo_update media: dvb-frontends: dib3000mb: fix uninit-value in dib3000_write_reg mm/vmstat: fix a W=1 clang compiler warning tcp_bpf: Charge receive socket buffer in bpf_tcp_ingress() tcp_bpf: Add sk_rmem_alloc related logic for tcp_bpf ingress redirection bpf: Check negative offsets in __bpf_skb_min_len() nfsd: restore callback functionality for NFSv4.0 mtd: diskonchip: Cast an operand to prevent potential overflow mtd: rawnand: arasan: Fix double assertion of chip-select mtd: rawnand: arasan: Fix missing de-registration of NAND phy: core: Fix an OF node refcount leakage in _of_phy_get() phy: core: Fix an OF node refcount leakage in of_phy_provider_lookup() phy: core: Fix that API devm_phy_put() fails to release the phy phy: core: Fix tha
[Kernel-packages] [Bug 2095437] Re: Focal update: v5.4.289 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2095437 Title: Focal update: v5.4.289 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.289 upstream stable release from git://git.kernel.org/ usb: dwc2: gadget: Don't write invalid mapped sg entries into dma_desc with iommu enabled PCI/AER: Disable AER service on suspend ALSA: usb: Fix UBSAN warning in parse_audio_unit() PCI: Add ACS quirk for Broadcom BCM5760X NIC i2c: pnx: Fix timeout in wait functions drm/i915: Fix memory leak by correcting cache object name in error handler erofs: fix order >= MAX_ORDER warning due to crafted negative i_size erofs: fix incorrect symlink detection in fast symlink net/smc: check sndbuf_space again after NOSPACE flag is set in smc_poll ionic: use ee->offset when returning sprom data net: hinic: Fix cleanup in create_rxqs/txqs() net: ethernet: bgmac-platform: fix an OF node reference leak netfilter: ipset: Fix for recursive locking warning mmc: sdhci-tegra: Remove SDHCI_QUIRK_BROKEN_ADMA_ZEROLEN_DESC quirk chelsio/chtls: prevent potential integer overflow on 32bit i2c: riic: Always round-up when calculating bus period efivarfs: Fix error on non-existent file USB: serial: option: add TCL IK512 MBIM & ECM USB: serial: option: add MeiG Smart SLM770A USB: serial: option: add Netprisma LCUK54 modules for WWAN Ready USB: serial: option: add MediaTek T7XX compositions USB: serial: option: add Telit FE910C04 rmnet compositions sh: clk: Fix clk_enable() to return 0 on NULL clk zram: refuse to use zero sized block device as backing device btrfs: tree-checker: reject inline extent items with 0 ref count NFS/pnfs: Fix a live lock between recalled layouts and layoutget of/irq: Fix using uninitialized variable @addr_len in API of_irq_parse_one() nilfs2: prevent use of deleted inode udmabuf: also check for F_SEAL_FUTURE_WRITE of: Fix error path in of_parse_phandle_with_args_map() of: Fix refcount leakage for OF node returned by __of_get_dma_parent() media: dvb-frontends: dib3000mb: fix uninit-value in dib3000_write_reg bpf: Check negative offsets in __bpf_skb_min_len() nfsd: restore callback functionality for NFSv4.0 mtd: diskonchip: Cast an operand to prevent potential overflow phy: core: Fix an OF node refcount leakage in _of_phy_get() phy: core: Fix an OF node refcount leakage in of_phy_provider_lookup() phy: core: Fix that API devm_phy_put() fails to release the phy phy: core: Fix that API devm_phy_destroy() fails to destroy the phy dmaengine: mv_xor: fix child node refcount handling in early exit dmaengine: at_xdmac: avoid null_prt_deref in at_xdmac_prep_dma_memset mtd: rawnand: fix double free in atmel_pmecc_create_user() tracing/kprobe: Make trace_kprobe's module callback called after jump_label update scsi: qla1280: Fix hw revision numbering for ISP1020/1040 scsi: megaraid_sas: Fix for a potential deadlock regmap: Use correct format specifier for logging range errors platform/x86: asus-nb-wmi: Ignore unknown event 0xCF scsi: mpt3sas: Diag-Reset when Doorbell-In-Use bit is set during driver load time virtio-blk: don't keep queue frozen during system suspend epoll: Add synchronous wakeup support for ep_poll_callback MIPS: Probe toolchain support of -msym32 ipv6: use skb_expand_head in ip6_finish_output2 ipv6: use skb_expand_head in ip6_xmit ipv6: fix possible UAF in ip6_finish_output2() bpf: fix recursive lock when verdict program return SK_PASS tracing: Constify string literal data member in struct trace_event_call btrfs: avoid monopolizing a core when activating a swap file ipv6: prevent possible UAF in ip6_xmit() selinux: ignore unknown extended permissions Drivers: hv: util: Avoid accessing a ringbuffer not initialized yet IB/mlx5: Introduce and use mlx5_core_is_vf() net/mlx5: Make API mlx5_core_is_ecpf accept const pointer RDMA/mlx5: Enforce same type port association for multiport RoCE RDMA/bnxt_re: Add check for path mtu in modify_qp RDMA/bnxt_re: Fix reporting hw_ver in query_device RDMA/bnxt_re: Fix max_qp_wrs reported drm: bridge: adv7511: Enable SPDIF DAI drm/bridge: adv7511_audio: Update Audio InfoFrame properly netro
[Kernel-packages] [Bug 2052439] Re: Don't produce linux-*-source- package
** Changed in: linux-ibm-6.8 (Ubuntu Jammy) Assignee: (unassigned) => Mehmet Basaran (mehmetbasaran) ** Changed in: linux-ibm-6.8 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ibm in Ubuntu. https://bugs.launchpad.net/bugs/2052439 Title: Don't produce linux-*-source- package Status in linux package in Ubuntu: Fix Released Status in linux-ibm package in Ubuntu: New Status in linux-gkeop source package in Focal: New Status in linux-hwe-5.15 source package in Focal: New Status in linux-ibm source package in Focal: New Status in linux-ibm-5.15 source package in Focal: New Status in linux-ibm source package in Jammy: New Status in linux-ibm-6.8 source package in Jammy: Fix Committed Status in linux-ibm source package in Noble: New Bug description: [Impact] Some kernels produce a linux-*-source- binary deb package. That is all wrong and confusing, only the primary/main linux source package should produce that package. [Test Case] Check list of built binary packages in LP and verify the package is not built. [Where Problems Could Occur] Already installed packages won't upgrade and become stale. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052439/+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 2086606] Re: Add list of source files to linux-buildinfo
** Also affects: linux-ibm-6.8 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-ibm-6.8 (Ubuntu) Status: New => Fix Committed ** Changed in: linux-ibm-6.8 (Ubuntu) Assignee: (unassigned) => Mehmet Basaran (mehmetbasaran) ** No longer affects: linux-ibm-6.8 (Ubuntu) ** Also affects: linux-ibm-6.8 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-ibm-6.8 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2086606 Title: Add list of source files to linux-buildinfo Status in linux package in Ubuntu: Fix Committed Status in linux-aws package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-gkeop package in Ubuntu: New Status in linux-ibm package in Ubuntu: Fix Committed Status in linux-lowlatency package in Ubuntu: New Status in linux-lowlatency-hwe-6.8 package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Status in linux-realtime package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-ibm source package in Focal: New Status in linux-lowlatency source package in Focal: New Status in linux source package in Jammy: Fix Committed Status in linux-ibm source package in Jammy: New Status in linux-lowlatency source package in Jammy: New Status in linux-lowlatency-hwe-6.8 source package in Jammy: Fix Committed Status in linux-raspi source package in Jammy: Fix Committed Status in linux source package in Noble: Fix Committed Status in linux-ibm source package in Noble: New Status in linux-lowlatency source package in Noble: Fix Committed Status in linux source package in Oracular: Fix Committed Status in linux-ibm source package in Oracular: New Status in linux-lowlatency source package in Oracular: Fix Committed Status in linux source package in Plucky: Fix Committed Status in linux-ibm source package in Plucky: Fix Committed Status in linux-lowlatency source package in Plucky: New Bug description: [Impact] For CVE triaging, it's helpful to have an exact list of the source files used for a build. Add that information to the linux-buildinfo packages. [Test Case] Check content of linux-buildinfo packages of the individual kernels. Test packages for Noble, Jammy and Focal: https://launchpad.net/~juergh/+archive/ubuntu/linux/+packages [Where Problems Could Occur] Build failures. This does not change the functionality of any of the kernel packages but just adds another text file to the linux-buildinfo packages so should not cause any user visible issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086606/+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 2096642] [NEW] No desktop with kernel 6.12.0-10-generic
Public bug reported: With linux-kernel 6.12.0-10-generic the desktop is not shown on my Ubuntu 25.04 system using KDE. I only see a black screen with a blinking text cursor. I cannot switch to alternative desktops. 0b:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1) 0b:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1) ** Affects: nvidia-graphics-drivers-560 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-560 in Ubuntu. https://bugs.launchpad.net/bugs/2096642 Title: No desktop with kernel 6.12.0-10-generic Status in nvidia-graphics-drivers-560 package in Ubuntu: New Bug description: With linux-kernel 6.12.0-10-generic the desktop is not shown on my Ubuntu 25.04 system using KDE. I only see a black screen with a blinking text cursor. I cannot switch to alternative desktops. 0b:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1) 0b:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-560/+bug/2096642/+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 2089237] Re: Lenovo X13s fails to boot kernel 6.11
** Changed in: linux (Ubuntu Oracular) Status: New => Fix Committed ** Changed in: linux (Ubuntu Oracular) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2089237 Title: Lenovo X13s fails to boot kernel 6.11 Status in linux package in Ubuntu: Invalid Status in linux source package in Oracular: Fix Committed Bug description: [ Impact ] Upgraded to Oracular, rebooted, the kernel (6.11) started to run and then the display went blank and the machine eventually crashed. [ Test Plan ] Install kernel, boot X13s. [ Where Problems Could Occur ] Breakage of Qualcomm Snapdragon based machines. All commits are very specific to Qualcomm HW so only users with that HW should be affected. Mainly sc8280xp SoC users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2089237/+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 2091719] Re: btrfs will WARN_ON() in btrfs_remove_qgroup() unnecessarily
Great news, thank you for taking care of it! -- 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/2091719 Title: btrfs will WARN_ON() in btrfs_remove_qgroup() unnecessarily Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: In Progress Status in linux source package in Oracular: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/2091719 [Impact] The following commit for noble and oracular introduced two new WARN_ON() calls in btrfs qgroup removals, and even though the author at the time believed they would not be reachable, it turns out it can happen quite frequently in the right conditions. ubuntu-noble b2ad25ba539452f492805e5f7d94e80894aa860f commit a776bf5f3c2300cfdf8a195663460b1793ac9847 Author: Qu Wenruo Date: Fri Apr 19 14:29:32 2024 +0930 Subject: btrfs: slightly loosen the requirement for qgroup removal Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a776bf5f3c2300cfdf8a195663460b1793ac9847 $ git describe --contains b2ad25ba539452f492805e5f7d94e80894aa860f Ubuntu-6.8.0-50.51~143 This primarily affects the systemd CI that runs integration tests on merge: https://github.com/systemd/systemd/actions/runs/12297539029/job/34318915884?pr=35589 Kernel panic - not syncing: kernel: panic_on_warn set ... CPU: 0 PID: 1316 Comm: (sd-clean) Not tainted 6.8.0-50-generic #51-Ubuntu Call Trace: dump_stack_lvl+0x27/0xa0 dump_stack+0x10/0x20 panic+0x366/0x3c0 ? btrfs_remove_qgroup+0x271/0x490 [btrfs] check_panic_on_warn+0x4f/0x60 __warn+0x95/0x160 ? btrfs_remove_qgroup+0x271/0x490 [btrfs] report_bug+0x17e/0x1b0 handle_bug+0x51/0xa0 exc_invalid_op+0x18/0x80 asm_exc_invalid_op+0x1b/0x20 RIP: 0010:btrfs_remove_qgroup+0x271/0x490 [btrfs] Code: c0 0f 85 27 fe ff ff 48 8b 43 b0 4c 39 f0 75 d5 4d 8d b5 e0 08 00 00 4c 89 f7 e8 8a 45 19 e2 48 83 7b 98 00 0f 84 52 01 00 00 <0f> 0b 49 8b 45 10 a8 10 74 42 41 f6 85 d0 08 00 00 0c 75 38 48 83 ? btrfs_remove_qgroup+0x266/0x490 [btrfs] btrfs_ioctl+0x12b9/0x13a0 [btrfs] ? srso_alias_return_thunk+0x5/0xfbef5 ? __seccomp_filter+0x368/0x570 ? __fput+0x15e/0x2e0 __x64_sys_ioctl+0xa3/0xf0 x64_sys_call+0x12a3/0x25a0 do_syscall_64+0x7f/0x180 entry_SYSCALL_64_after_hwframe+0x78/0x80 [Fix] The fix just landed in mainline as: commit c0def46dec9c547679a25fe7552c4bcbec0b0dd2 Author: Qu Wenruo Date: Mon Nov 11 07:29:07 2024 +1030 Subject: btrfs: improve the warning and error message for btrfs_remove_qgroup() Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c0def46dec9c547679a25fe7552c4bcbec0b0dd2 The commit places the WARN_ON behind CONFIG_BTRFS_DEBUG, which silences the warning for most users. It is safe to do so, as noted by the Author, as the user space tool managing the qgroups would rescan them, to fix the inconsistent view. This is needed for both noble and oracular. [Testcase] The upstream systemd CI tests can consistently reproduce the issue, so the test and proposed kernels will be run against the systemd CI for verification. There is a test kernel available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2091719-test If you install it, the systemd CI will run to completion. [Where problems could occur] We are changing the WARN_ON() to occur only when CONFIG_BTRFS_DEBUG is enabled. There is no other change in logic, so functionality should be the same as what we have now. If a regression were to occur, it would affect systems with btrfs filesystems that are utilising subvolumes. It would not likely cause any data loss or disk corruption, as userspace tools should be able to automatically fix up any inconsistent views without user interaction. [Other info] Systemd upstream bisected the issue here: https://github.com/systemd/systemd/pull/35567#issuecomment-2538160543 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2091719/+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 2095287] Re: Enable DP tunnel on xe driver(for lunar lake platform)
** Changed in: linux-oem-6.11 (Ubuntu Noble) 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.11 in Ubuntu. https://bugs.launchpad.net/bugs/2095287 Title: Enable DP tunnel on xe driver(for lunar lake platform) Status in HWE Next: New Status in linux-oem-6.11 package in Ubuntu: New Status in linux-oem-6.11 source package in Noble: Fix Committed Bug description: [Impact] TBT monitors can not reach 4K@60Hz with two 4K@60Hz monitors connected to dock on Lunar lake platform. [Fix] Intel provide a fix for this issue. 73900dce57e4 drm/xe/dp: Enable DP tunneling [Test] 1. Connect Dell dock to the lunar lake platform. 2. Plug in two/three 4K@60Hz monitor to the Dock(include one TBT monitor connected at the end) 3. all monitors can reach 4K@60Hz [Where problems could occur] I can't see any issues may occur while enabling the DP tunneling on xe driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2095287/+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 2092384] Re: [SRU] Introduce support for RTL8125BPH 2.5 GbE controller.
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- 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/2092384 Title: [SRU] Introduce support for RTL8125BPH 2.5 GbE controller. Status in HWE Next: New Status in linux-firmware package in Ubuntu: Confirmed Status in linux-oem-6.11 package in Ubuntu: Fix Committed Status in linux-firmware source package in Noble: Confirmed Status in linux-oem-6.11 source package in Noble: Fix Committed Status in linux-firmware source package in Oracular: Confirmed Status in linux-oem-6.11 source package in Oracular: Invalid Status in linux-firmware source package in Plucky: Confirmed Status in linux-oem-6.11 source package in Plucky: Fix Committed Bug description: [ Impact ] RTL8125BPH 2.5 GbE controller is not functional. [ Fix ] This introduce support for RTL8125BPH 2.5 GbE controller by adding: 1. linux-firmware (already upstreamed[1]). 2. Driver patch[2] and its dependent patches. The dependent patches includes: 1. The PHY support for PHY ID 0x001cc841, which is needed for RTL8125BP 2. Refactoring when support for other models (e.g. RTL8125D, RTL8125D rev.b) were added. 3. Dependent patches for the patch itself. [ Test ] 1. Install the linux-firmware 2. Install the kernel 3. Test basic network function (ping, firefox etc.) [ Where the problem could occur ] Error in the patches and firmware will make the said controller not function properly, which happens to be the status quo. To avoid conflict, the dependent patches include some commits for newer models, in particular the RTL8125D and RTL8125D rev.b. That however doesn't mean those models are readily usable for now. [ Additional information ] [1] https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/393/diffs?commit_id=e1e114f8872f8e5645056a28767cddce77740d39 [2] b11bff90f2ad52c5 (r8169: add support for RTL8125BP rev.b) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2092384/+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 2095279] Re: MT7925 controller timeout during Suspend stress test
** Changed in: linux-oem-6.11 (Ubuntu Noble) 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/2095279 Title: MT7925 controller timeout during Suspend stress test Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: New Status in linux-oem-6.11 package in Ubuntu: New Status in linux source package in Noble: Invalid Status in linux-firmware source package in Noble: New Status in linux-oem-6.11 source package in Noble: Fix Committed Status in linux source package in Oracular: New Status in linux-firmware source package in Oracular: New Status in linux-oem-6.11 source package in Oracular: New Status in linux source package in Plucky: Invalid Status in linux-firmware source package in Plucky: New Status in linux-oem-6.11 source package in Plucky: New Bug description: [Impact] When doing suspend test, the system will fail to be suspended since the MT7925 controller couldn't be suspended. The root cause is caused by the command timeout issued from mt7925 driver. [Fix] Cherry-pick the following two patches from linux-next: 1b97fc8443ae wifi: mt76: mt7925: fix the unfinished command of regd_notifier before suspend 8f6571ad470f wifi: mt76: mt7925: add handler to hif suspend/resume event Also, cherry-pick the following commits from linux-firmware: 47c8a6053c64 linux-firmware: update firmware for MT7925 WiFi device 62ee1c4b2d35 linux-firmware: update firmware for MT7925 WiFi device [Test Plan] 1. Install Ubuntu image and boot into the OS 2. Run the suspend test by $ fwts s3 --s3-device-check --s3-device-check-delay=60 --s3-multiple=1 --s3-sleep-delay=60, and see if the error occurred. [Where problems could occur] Due to the new FW, there might be a unexpected behavior of the MT7925 hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2095279/+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 2095561] Re: The ALS doesn't work(regression)
** Changed in: linux-oem-6.11 (Ubuntu Noble)
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.11 in Ubuntu.
https://bugs.launchpad.net/bugs/2095561
Title:
The ALS doesn't work(regression)
Status in HWE Next:
New
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux-oem-6.11 source package in Noble:
Fix Committed
Bug description:
[Impact]
The sauce patch leads to the regression, and the patch is not accepted by the
upstream.
a6c8904f3e958 ("UBUNTU: SAUCE: iio: hid-sensor-attributes: validate
sensitivity attributes")
[Fix]
Revert the problamatic patch and apply the new fix.
https://patchwork.kernel.org/project/linux-input/patch/20250115070020.221-1-acelan@canonical.com/
[Test]
1. Boots up the machine with this USB camera which comes with an invalid i2c
sensor
Bus 003 Device 002: ID 0408:5473 Quanta Computer, Inc. HP 5MP Camera
2. Run iio_info, it should return the iio information immediately
[Where problems could occur]
It's a quirk dedicated to a certain USB webcam, so it won't lead to other
sesnors fail to work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2095561/+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 2092703] Re: Ubuntu 22.04 fails to start after kernel update to 6.8.0-50
Today I tried to boot kernel 6.8.0-51 again, and it was successful. So, for me the problem disappeared. I am not sure why. One of the recent updates (while using kernel 6.8.0-49) was xwayland. Maybe this update solved the problem. -- 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/2092703 Title: Ubuntu 22.04 fails to start after kernel update to 6.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: Hello, I've recently (2024-12-24) updated the kernel in my Ubuntu 22.04 from 6.8.0-49 to 6.8.0-50, but it doesn't work. I can still successfully boot 6.8.0-49 kernel. I'm using Lenovo Thinkpad L15 Gen 2 with AMD Ryzen 5850U. As far as I noticed in boot logs from previous boot (journalctl -b -1), there is some problem with X.org: gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) modesetting: Driver for Modesetting Kernel Drivers: kms gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) FBDEV: driver for framebuffer: fbdev gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) VESA: driver for VESA chipsets: vesa gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: xf86EnableIO: failed to enable I/O ports -03ff (Operation not permitted) gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) open /dev/dri/card0: No such file or directory gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (WW) Falling back to old probe method for modesetting gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) open /dev/dri/card0: No such file or directory gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Loading sub module "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) LoadModule: "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Loading /usr/lib/xorg/modules/libfbdevhw.so gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Module fbdevhw: vendor="X.Org Foundation" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: compiled for 1.21.1.4, module version = 0.0.2 gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: ABI class: X.Org Video Driver, version 25.2 gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Unable to find a valid framebuffer device gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (WW) Falling back to old probe method for fbdev gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Loading sub module "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) LoadModule: "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Loading /usr/lib/xorg/modules/libfbdevhw.so gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Module fbdevhw: vendor="X.Org Foundation" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: compiled for 1.21.1.4, module version = 0.0.2 gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: ABI class: X.Org Video Driver, version 25.2 gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) open /dev/fb0: No such file or directory gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: vesa: Ignoring device with a bound kernel driver gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Screen 0 deleted because of no matching config section. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadModule: "modesetting" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Screen 0 deleted because of no matching config section. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadModule: "fbdev" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadSubModule: "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadSubModule: "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadSubModule: "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Screen 0 deleted because of no matching config section. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadModule: "vesa" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Device(s) detect
Re: [Kernel-packages] [Bug 2092703] Re: Ubuntu 22.04 fails to start after kernel update to 6.8.0-50
I can also confirm I can most of the times boot 6.8.0-51 kernel. But still not always, it sometimes fails to boot. pt., 24 sty 2025, 14:16 użytkownik WDW <2092...@bugs.launchpad.net> napisał: > Today I tried to boot kernel 6.8.0-51 again, and it was successful. So, > for me the problem disappeared. I am not sure why. One of the recent > updates (while using kernel 6.8.0-49) was xwayland. Maybe this update > solved the problem. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2092703 > > Title: > Ubuntu 22.04 fails to start after kernel update to 6.8.0-50 > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Hello, I've recently (2024-12-24) updated the kernel in my Ubuntu > 22.04 from 6.8.0-49 to 6.8.0-50, but it doesn't work. I can still > successfully boot 6.8.0-49 kernel. I'm using Lenovo Thinkpad L15 Gen 2 > with AMD Ryzen 5850U. > > As far as I noticed in boot logs from previous boot (journalctl -b > -1), there is some problem with X.org: > > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (II) modesetting: Driver for Modesetting > Kernel Drivers: kms > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (II) FBDEV: driver for framebuffer: fbdev > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (II) VESA: driver for VESA chipsets: vesa > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: xf86EnableIO: failed to enable I/O ports > -03ff (Operation not permitted) > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (EE) open /dev/dri/card0: No such file or > directory > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (WW) Falling back to old probe method for > modesetting > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (EE) open /dev/dri/card0: No such file or > directory > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (II) Loading sub module "fbdevhw" > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (II) LoadModule: "fbdevhw" > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (II) Loading > /usr/lib/xorg/modules/libfbdevhw.so > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (II) Module fbdevhw: vendor="X.Org > Foundation" > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: compiled for 1.21.1.4, module > version = 0.0.2 > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: ABI class: X.Org Video Driver, > version 25.2 > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (EE) Unable to find a valid framebuffer > device > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (WW) Falling back to old probe method for > fbdev > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (II) Loading sub module "fbdevhw" > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (II) LoadModule: "fbdevhw" > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (II) Loading > /usr/lib/xorg/modules/libfbdevhw.so > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (II) Module fbdevhw: vendor="X.Org > Foundation" > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: compiled for 1.21.1.4, module > version = 0.0.2 > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: ABI class: X.Org Video Driver, > version 25.2 > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (EE) open /dev/fb0: No such file or > directory > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: vesa: Ignoring device with a bound kernel > driver > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (EE) Screen 0 deleted because of no > matching config section. > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (II) UnloadModule: "modesetting" > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (EE) Screen 0 deleted because of no > matching config section. > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (II) UnloadModule: "fbdev" > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (II) UnloadSubModule: "fbdevhw" > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (II) UnloadSubModule: "fbdevhw" > gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a > /usr/libexec/gdm-x-session[1667]: (II) UnloadSubModule: "fbdevhw" > gru 30 07:00:40 ad
[Kernel-packages] [Bug 209669] Re: laptop wireless notification light not showing
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/209669 ** Tags added: iso-testing -- 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/209669 Title: laptop wireless notification light not showing Status in linux package in Ubuntu: Invalid Bug description: In 8.04, even though I can connect perfectly to the wireless network, the wireless notification light on my laptop (Lenovo X60s) does not light up to reflect that connectivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/209669/+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: Screen flickering in Ubuntu
** Summary changed: - [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) + Screen flickering in Ubuntu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/1958191 Title: Screen flickering in Ubuntu 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-hwe-6.5 package in Ubuntu: Confirmed Status in linux-hwe-6.8 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 Status in linux-hwe-6.5 source package in Lunar: Won't Fix 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 2093622] Re: IDPF: TX timeout and crash
** Changed in: linux-gcp (Ubuntu Oracular) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2093622 Title: IDPF: TX timeout and crash Status in linux-gcp package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux-gkeop package in Ubuntu: New Status in linux-gcp source package in Jammy: New Status in linux-gke source package in Jammy: New Status in linux-gcp source package in Noble: New Status in linux-gke source package in Noble: New Status in linux-gkeop source package in Noble: New Status in linux-gcp source package in Oracular: Fix Committed Bug description: SRU Justification [Impact] Google has requested a patchset to be backported to resolve an issue in the IDPF module. The issue can lead to timeouts and potentially a system crash. [Fix] Backport a patchset from linux upstream to all IDPF-enabled Google kernels. [Test Plan] Compile and boot tested. [Regression Potential] This is a medium size backport and affects several kernels. Only the Oracular patches were applied cleanly, which increases the chance of human error in the backport process. Problems related to this fix could lead to further issues in the Intel IDPF module, but there have been no changes to other drivers or the core kernel. [Other] SF #00404007 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2093622/+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 2086606] Re: Add list of source files to linux-buildinfo
** Also affects: linux-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2086606 Title: Add list of source files to linux-buildinfo Status in linux package in Ubuntu: Fix Committed Status in linux-aws package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-gkeop package in Ubuntu: New Status in linux-ibm package in Ubuntu: Fix Committed Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Status in linux-lowlatency-hwe-6.8 package in Ubuntu: New Status in linux-oem-6.11 package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Status in linux-realtime package in Ubuntu: New Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-ibm source package in Focal: New Status in linux-lowlatency source package in Focal: New Status in linux source package in Jammy: Fix Committed Status in linux-ibm source package in Jammy: New Status in linux-lowlatency source package in Jammy: New Status in linux-lowlatency-hwe-6.8 source package in Jammy: Fix Committed Status in linux-raspi source package in Jammy: Fix Committed Status in linux source package in Noble: Fix Committed Status in linux-ibm source package in Noble: New Status in linux-lowlatency source package in Noble: Fix Committed Status in linux source package in Oracular: Fix Committed Status in linux-ibm source package in Oracular: New Status in linux-lowlatency source package in Oracular: Fix Committed Status in linux source package in Plucky: Fix Committed Status in linux-ibm source package in Plucky: Fix Committed Status in linux-lowlatency source package in Plucky: New Bug description: [Impact] For CVE triaging, it's helpful to have an exact list of the source files used for a build. Add that information to the linux-buildinfo packages. [Test Case] Check content of linux-buildinfo packages of the individual kernels. Test packages for Noble, Jammy and Focal: https://launchpad.net/~juergh/+archive/ubuntu/linux/+packages [Where Problems Could Occur] Build failures. This does not change the functionality of any of the kernel packages but just adds another text file to the linux-buildinfo packages so should not cause any user visible issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086606/+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: Screen flickering in Ubuntu
This bug is related to screen flickering when DPMS is enabled and is not related to mouse movement. Flickering looks like a decrease in the screen refresh rate several times. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/1958191 Title: Screen flickering in Ubuntu 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-hwe-6.5 package in Ubuntu: Confirmed Status in linux-hwe-6.8 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 Status in linux-hwe-6.5 source package in Lunar: Won't Fix 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 2081613] Re: linux-azure: Enable erofs.ko to linux-modules package
This bug is awaiting verification that the linux-azure/6.8.0-1022.26 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-azure' to 'verification-done-noble- linux-azure'. If the problem still exists, change the tag 'verification- needed-noble-linux-azure' to 'verification-failed-noble-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-azure-v2 verification-needed-noble-linux-azure -- 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/2081613 Title: linux-azure: Enable erofs.ko to linux-modules package Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Noble: Fix Committed Bug description: [Impact] erofs is starting to see more use as a modern alternative to squashfs. Since squashfs is already included in linux-modules, let's include erofs in linux-modules as well so that it can be used as a filesystem in virtual machines with just linux-virtual installed. [Fix] Clean cherry-pick to the noble tree. [Test plan] Build and boot tested; also installed the generated linux-image and linux-modules packages to confirm that the erofs module could be loaded with "modprobe erofs". [Where problems could occur] Very small risk of regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2081613/+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
