[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-riscv/6.5.0.27.28.1)
All autopkgtests for the newly accepted linux-meta-riscv (6.5.0.27.28.1) for mantic have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/unknown (amd64) casper/unknown (amd64) cryptsetup/unknown (ppc64el, s390x) ipmitool/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/mantic/update_excuses.html#linux-meta-riscv [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058191] Re: Getting SIGSEGV and SIGILL in many programs
** Attachment added: "_opt_brave.com_brave_brave.1000.crash" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058191/+attachment/5757404/+files/_opt_brave.com_brave_brave.1000.crash -- 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/2058191 Title: Getting SIGSEGV and SIGILL in many programs Status in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Okay, recently I upgraded to 24.04. I'm getting some SIGSEGV and SIGILLs from time to time. Sometimes the entire computer freezes and i can't even turn down unless i hold the power button for 5 secs. I tought it could be the kernel version, so I upgraded from Ubuntu's 6.8.0-11.11+1 to mainline 6.8.1. However, it didn't fix. Here are some softwares i got SIGSEGV or SIGILLs: - code-insiders (vscode) - brave (Brave browser) - bun (node.js alternative) - node.js I know i should upload more logs, but I didn't find the errors in syslog or journalctl. $ lsb_release -rd - No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+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 2058191] Re: Getting SIGSEGV and SIGILL in many programs
In dmesg log, i saw a line starting with "mar 20 02:04:10 eduapps whoopsie-upload-all[8574]" which was written by whoopsie that gave me a brave crash log. brave crash log is big but gives good info of what's going on. if you search for the word "SIGSEGV" you will find where the error occurs. ** Attachment added: "dmesg log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058191/+attachment/5757403/+files/journalctl.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058191 Title: Getting SIGSEGV and SIGILL in many programs Status in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Okay, recently I upgraded to 24.04. I'm getting some SIGSEGV and SIGILLs from time to time. Sometimes the entire computer freezes and i can't even turn down unless i hold the power button for 5 secs. I tought it could be the kernel version, so I upgraded from Ubuntu's 6.8.0-11.11+1 to mainline 6.8.1. However, it didn't fix. Here are some softwares i got SIGSEGV or SIGILLs: - code-insiders (vscode) - brave (Brave browser) - bun (node.js alternative) - node.js I know i should upload more logs, but I didn't find the errors in syslog or journalctl. $ lsb_release -rd - No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+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 2058191] Re: Getting SIGSEGV and SIGILL in many programs
FINALLY FOUND SOMETHING!! 6.8.1 kernel, but this time i got sigsegv from brave browser (log being attached): SourcePackage: brave-browser Stacktrace: #0 0x58e16cb3b49e in ??? () #1 0x36d80357c469 in ??? () #2 0x7ffe5ec94230 in ??? () #3 0x58e17798e4d8 in ??? () #4 0x10880058c000 in ??? () #5 0x58e177aa3880 in ??? () #6 0x7ffe5ec938f8 in ??? () #7 0x10880058c000 in ??? () #8 0x in ??? () StacktraceAddressSignature: /opt/brave.com/brave/brave:11:/opt/brave.com/brave/brave+ff049e:[stack]+24230:/opt/brave.com/brave/brave+e14d8:[anon..partition_alloc]+2:/opt/brave.com/brave/brave+1f6880:[stack]+238f8:[anon..partition_alloc]+2 StacktraceTop: ??? () ??? () ??? () ??? () ??? () ThreadStacktrace: . Thread 39 (Thread 0x7d6e830006c0 (LWP 23)): #0 0x7d6f1f498d61 in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x7d6e82fff190, op=137, expected=0, futex_word=0x7d6e82fff288) at ./nptl/futex-internal.c:57 -- 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/2058191 Title: Getting SIGSEGV and SIGILL in many programs Status in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Okay, recently I upgraded to 24.04. I'm getting some SIGSEGV and SIGILLs from time to time. Sometimes the entire computer freezes and i can't even turn down unless i hold the power button for 5 secs. I tought it could be the kernel version, so I upgraded from Ubuntu's 6.8.0-11.11+1 to mainline 6.8.1. However, it didn't fix. Here are some softwares i got SIGSEGV or SIGILLs: - code-insiders (vscode) - brave (Brave browser) - bun (node.js alternative) - node.js I know i should upload more logs, but I didn't find the errors in syslog or journalctl. $ lsb_release -rd - No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+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 2058330] Re: Update amd-pmf for AMD strix series
** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Anthony Wong (anthonywong) -- 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/2058330 Title: Update amd-pmf for AMD strix series Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: These updates will be enhanced amd-pmf for family 1AH on the supported OEM platforms, including enabling new revision for BIOS notify events, support static slider by APTS (AMD Performance and Thermal State)...etc. Needs to be backported into oem-6.8. Following are commits merged to linus tree for v6.9-rc1: * 8362e862fb879 platform/x86/amd/pmf: Update sps power thermals according to the platform-profiles * 3eecb434d7f21 platform/x86/amd/pmf: Add support to get sps default APTS index values * 48d38f569261b platform/x86/amd/pmf: Add support to get APTS index numbers for static slider * 6262938eef282 platform/x86/amd/pmf: Add support to notify sbios heart beat event * 5fdc8b82aab4c platform/x86/amd/pmf: Add support to get sbios requests in PMF driver * 233f78e11e1fa platform/x86/amd/pmf: Disable debugfs support for querying power thermals * a33e9e106601b platform/x86/amd/pmf: Differentiate PMF ACPI versions To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058331] Re: Update amd_sfh for AMD strix series
** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Anthony Wong (anthonywong) -- 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/2058331 Title: Update amd_sfh for AMD strix series Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: Extend MP2 register region to enable family 1AH based family on the supported OEM platforms, needs to be backported into oem-6.8. [ 0.784296] pcie_mp2_amd: probe of :c4:00.7 failed with error -12 Following fixes applied to linus tree: * 90184f90c9ac5 HID: amd_sfh: Set the AMD SFH driver to depend on x86 * 6296562f30b1c HID: amd_sfh: Extend MP2 register access to SFH * 2105e8e00da46 HID: amd_sfh: Improve boot time when SFH is available * c1db0073212ef HID: amd_sfh: Avoid disabling the interrupt * bbf0dec306966 HID: amd_sfh: Update HPD sensor structure elements * 333861f4cca6d HID: amd_sfh: Increase sensor command timeout To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058331/+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 2058333] Re: daisy chained thunderbolt devices not working at reboot on AMD strix platforms
** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Anthony Wong (anthonywong) -- 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/2058333 Title: daisy chained thunderbolt devices not working at reboot on AMD strix platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: Boot firmware (typically BIOS) might have created tunnels of its own. The tunnel configuration that it does might be sub-optimal. For instance it may only support HBR2 monitors so the DisplayPort tunnels it created may limit Linux graphics drivers. In addition there is an issue on some AMD based systems where the BIOS does not allocate enough PCIe resources for future topology extension. By resetting the USB4 topology the PCIe links will be reset as well allowing Linux to re-allocate. This aligns the behavior with Windows Connection Manager. Fixes merged to linus tree for v6.9-rc1: * 59a54c5f3dbde thunderbolt: Reset topology created by the boot firmware * ec8162b3f0683 thunderbolt: Make tb_switch_reset() support Thunderbolt 2, 3 and USB4 routers * b35c1d7b11da8 thunderbolt: Introduce tb_path_deactivate_hop() * 01da6b99d49f6 thunderbolt: Introduce tb_port_reset() To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058333/+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 2054218] Re: kvm: Running perf against qemu processes results in page fault inside guest
Performing verification for mantic.
I deployed mantic onto a bare metal server, with kernel 6.5.0-26-generic from
-updates.
I installed a KVM stack, synced a cloud image, and tested VM creation.
$ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-a release=jammy
arch=amd64
$ uvt-kvm ssh jammy-a
Welcome to Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-101-generic x86_64)
From there, I found the PID of the VM:
$ ps aux | grep qemu
libvirt+1799 107 1.5 9642380 1044752 ? Sl 03:21 0:38
/usr/bin/qemu-system-x86_64 -name guest=jammy-a,debug-threads=on -S -object
{"qom-ty
We run perf:
$ sudo perf top -p 1799
$ virsh console jammy-a
Connected to domain 'jammy-a'
Escape character is ^] (Ctrl + ])
[ 161.413890] BUG: unable to handle page fault for address: fe18cdb1c028
[ 161.419474] #PF: supervisor read access in kernel mode
[ 161.423707] #PF: error_code(0x) - not-present page
[ 161.427949] PGD 17ffca0[ 161.429508] BUG: unable to handle page fault for
address: fe18cdb1c028
[ 161.429513] #PF: supervisor read access in kernel mode
[ 161.429516] #PF: error_code(0x) - n
The VM suffers a page fault and crashes, and is not accessible over ssh.
$ uvt-kvm ssh jammy-a
(no response).
I then enabled -proposed, and installed 6.5.0-27-generic:
$ uname -rv
6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024
$ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-a release=jammy
arch=amd64
$ uvt-kvm ssh jammy-a
Welcome to Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-101-generic x86_64)
We get the pid of the VM:
$ ps aux | grep qemu
libvirt+1786 42.5 1.5 7960876 1022308 ? Sl 03:37 0:40
/usr/bin/qemu-system-x86_64 -name guest=jammy-a,debug-threads=on -S -object
{"qom-ty
We run perf:
$ sudo perf top -p 1786
This time, the VM does not crash, and stays running:
$ virsh console jammy-a
Connected to domain 'jammy-a'
Escape character is ^] (Ctrl + ])
jammy-a login:
jammy-a login:
We can also ssh to the VM just fine:
$ uvt-kvm ssh jammy-a
Welcome to Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-101-generic x86_64)
This is much better. The kernel in -proposed fixes the issue, happy to
mark verified for mantic.
** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux
--
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/2054218
Title:
kvm: Running perf against qemu processes results in page fault inside
guest
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Mantic:
Fix Committed
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2054218
[Impact]
Running perf against a QEMU/kvm process results in the guest suffering
a page fault in trying to store Precise Event Based Sampling (PEBS)
records for the host. This affects both using perf against a single
process, in which it crashes the targeted guest, or using perf system
wide, in which it crashes all running guests on the system.
The issue was introduced in 6.0 by:
commit c59a1f106f5cd4843c097069ff1bb2ad72103a67
Author: Like Xu
Date: Mon Apr 11 18:19:36 2022 +0800
Subject: KVM: x86/pmu: Add IA32_PEBS_ENABLE MSR emulation for extended PEBS
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c59a1f106f5cd4843c097069ff1bb2ad72103a67
This affects all 6.2 and 6.5 kernels. There is no known workaround,
apart from not using perf on affected systems.
[Fix]
The issue was fixed in 6.7 by:
commit 971079464001c6856186ca137778e534d983174a
Author: Paolo Bonzini
Date: Thu Jan 4 16:15:17 2024 +0100
Subject: KVM: x86/pmu: fix masking logic for MSR_CORE_PERF_GLOBAL_CTRL
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=971079464001c6856186ca137778e534d983174a
This reinstates the logic for setting MSR_CORE_PERF_GLOBAL_CTRL to
what it was before "KVM: x86/pmu: Add IA32_PEBS_ENABLE MSR emulation
for extended PEBS".
- .guest = intel_ctrl & (~cpuc->intel_ctrl_host_mask |
~pebs_mask),
+ .guest = intel_ctrl & ~cpuc->intel_ctrl_host_mask &
~pebs_mask,
The faulty logic includes any bit that isn't both marked as
exclude_guest and using PEBS, while it should really be excluding PEBS
from the host.
[Testcase]
Start a bare metal server. Enable KVM, start a few VMs. The VMs can be
idle, they don't require any workload.
$ sudo apt-get install qemu-kvm libvirt-daemon-system libvirt-clients
bridge-utils uvtool
$ sudo reboot
$ ssh-keygen
$ uvt-simplestreams-libvirt sync --source
http://cloud-images.ubuntu.com/daily release=jammy arch=amd64
$ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-a release=jammy
arch=amd64
$ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-b release=jammy
arch=amd64
$ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-c
[Kernel-packages] [Bug 2056491] Comment bridged from LTC Bugzilla
--- Comment From jldo...@us.ibm.com 2024-03-19 20:42 EDT--- *** Bug 205873 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056491 Title: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block` Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le Power9 or Power10 : error: out of memory. Press any key to continue... OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003) (powerpc64le-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 (Ubuntu 6.8.0-11.11-generic 6.8.0-rc4) Detected machine type: 0101 command line: BOOT_IMAGE=/casper/vmlinux quiet --- Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0e67 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 instantiating rtas at 0x1ec3... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x1078 -> 0x1078179e Device tree struct 0x1079 -> 0x107a Quiescing Open Firmware ... Booting Linux via __start() @ 0x0a75 ... [0.019184] plpks: POWER LPAR Platform KeyStore is not supported or enabled [0.114052] SED: plpks not available [0.114507] /dev/root: Can't open blockdev [0.114520] List of all bdev filesystems: [0.114523] ext3 [0.114523] ext2 [0.114525] ext4 [0.114527] squashfs [0.114529] vfat [0.114531] fuseblk [0.114532] [0.114535] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.114540] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-11-generic #11-Ubuntu [0.114545] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1030.00 (NH1030_017) hv:phyp pSeries [0.114551] Call Trace: [0.114553] [c6403b40] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.114562] [c6403b70] [c01926ec] panic+0x300/0x524 [0.114568] [c6403c10] [c301146c] mount_root_generic+0x208/0x448 [0.114574] [c6403ce0] [c30118d8] prepare_namespace+0x98/0x430 [0.114580] [c6403d70] [c3010820] kernel_init_freeable+0x32c/0x37c [0.114585] [c6403de0] [c00115ec] kernel_init+0x34/0x298 [0.114591] [c6403e50] [c000dfbc] ret_from_kernel_user_thread+0x14/0x1c [0.114596] --- interrupt: 0 at 0x0 [0.117006] pstore: backend (nvram) writing error (-1) [0.119362] Rebooting in 10 seconds.. This is the message from a Power10(9080-HEX), but the same is happening on a PowrerVM-Power9 (9009-22A) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056491/+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 2019247] Re: perf should be compiled with libtraceevent
This still appears to be an issue. Events are listed in `perf list` but not available for use by `perf record` e.g. $ sudo /usr/lib/linux-tools/6.2.0-39-generic/perf record -e syscalls:sys_enter_fsync -ag event syntax error: 'syscalls:sys_enter_fsync' \___ unsupported tracepoint libtraceevent is necessary for tracepoint support Run 'perf list' for a list of valid events Usage: perf record [] [] or: perf record [] -- [] -e, --eventevent selector. use 'perf list' to list available events ➜ test git:(UPM-29742) ✗ /usr/lib/linux-tools/6.2.0-39-generic/perf version perf version 6.2.16 -- 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/2019247 Title: perf should be compiled with libtraceevent Status in linux package in Ubuntu: Confirmed Bug description: libtraceevent was removed from the kernel tree in https://lore.kernel.org/lkml/20221130062935.2219247-1-irog...@google.com/. The linux-tools-6.2.0-20-generic I have in Lunar doesn't not use compile perf against libtraceevent, making perf unable to record traceevents. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019247/+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 2058315] Re: Mute/mic-mute LEDs not functioning on a HP platform
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) -- 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/2058315 Title: Mute/mic-mute LEDs not functioning on a HP platform Status in OEM Priority Project: New Status in linux package in Ubuntu: New Bug description: [Impact] LEDs on both mute and mic-mute key are not working on a HP platform. [Fix] The quirk in the commit b2d6a1fd0e3e513f5ebfc152d6fedae093df8e21 (ALSA: hda/realtek: Add quirks for HP G11 Laptops using CS35L56) in linux-next can make it work. [Test] 1. Install the v2023.12.1 of upstream sof-bin (https://github.com/thesofproject/sof-bin/releases/tag/v2023.12.1) 2. Then after the quirk is applied, both the mute and mic-mute LEDs on the keys should toggle accordingly on key presses. [Where problems could occur] If the subsystem ID is somehow reused by vendor for newer hardware, the newer hardware may not be functioning correctly. Also it requires correct tplg files to work. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2058315/+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 2058334] Re: package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to install/upgrade: installed linux-headers-6.5.0-26-generic package post-installation script subprocess r
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)
--
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/2058334
Title:
package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to
install/upgrade: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
Invalid
Bug description:
I got the error after login to the gnome
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-26-generic 6.5.0-26.26
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Mar 18 17:33:44 2024
ErrorMessage: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2021-12-26 (813 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-26-generic
root=UUID=336f83fe-a568-4a38-b14f-1d0964399570 ro rd.driver.blacklist=nouveau
modprobe.blacklist=nouveau nvidia-drm.modset=1 migrations=off mitigations=off
quiet splash rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
nvidia-drm.modset=1 migrations=off mitigations=off vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: /usr/bin/python3.11, Python 3.11.6, python-is-python3, 3.11.4-1
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
RfKill:
SourcePackage: linux
Title: package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to
install/upgrade: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to mantic on 2023-10-14 (157 days ago)
dmi.bios.date: 09/12/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F27
dmi.board.asset.tag: Default string
dmi.board.name: Z690 GAMING X DDR4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF27:bd09/12/2023:br5.27:svnGigabyteTechnologyCo.,Ltd.:pnZ690GAMINGXDDR4:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ690GAMINGXDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Z690 MB
dmi.product.name: Z690 GAMING X DDR4
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058334/+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 2058381] Re: Compression of ARM64 kernels causes problems with secureboot and systemd-boot
** Changed in: linux-meta (Ubuntu) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2058381 Title: Compression of ARM64 kernels causes problems with secureboot and systemd-boot Status in linux-meta package in Ubuntu: New Bug description: Hello, I'm trying to deploy an Ubuntu Server on arm64 with securbeoot and UKIs. I'm running into the problem that the shipped kernel is just a plain gzip compressed version of the kernel image. This causes two issues: - sbsign refuses to sign the kernel without uncompressing it first (Invalid DOS header magic) - systemd-stub/systemd-boot don't recognize this kernel as a valid binary (Bad kernel image: Load error\n Failed to execute Ubuntu Noble Numbat (development branch) (\EFI\Linux\ubuntu-6.8.0-11-generic.efi): Load error) Debian just ships an uncompressed kernel and Fedora ships a PE binary (which they can do because they dropped BIOS support, so this cannot be adopted for Ubuntu). Shipping an uncompressed kernel would be the easiest switch from my view, only causing problems on small /boot partitions or ESP partitions, respectively. The current version in Ubuntu causes unexpected behaviour with various bootchain tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2058381/+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 2056103] Re: Ubuntu OS 22.04.3 LTS running with Kernel 5.15.0-87-generic hangging intermittently while booting
Bug Number #1989258 helped us in resolving the issue. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989258). Installed kernel 5.19.0-50-generic on Ubuntu 22.04 fixed the issue. ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Srikanth Nimmagadda (srikanthn81n) -- 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/2056103 Title: Ubuntu OS 22.04.3 LTS running with Kernel 5.15.0-87-generic hangging intermittently while booting Status in linux package in Ubuntu: Fix Released Bug description: Ubuntu OS 22.04.3 LTS running with Kernel 5.15.0-87-generic hanging intermittently while booting. to bring it back it needs another restart from console. :~$ lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 :~$ :~$ cat /etc/os-release PRETTY_NAME="Ubuntu 22.04.3 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.3 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy :~$ Console log showing following messages. [1.401310] Run /init as init process [1.403958] usb 1-1: new full-speed USB device number 2 using uhci_hcd Loading, please wait... Starting version 249.11-0ubuntu3.11 [1.518785] virtio_blk virtio2: [vda] 419430400 512-byte logical blocks (215 GB/200 GiB) [1.519292] input: VirtualPS/2 VMware VMMouse as /devices/platform/i8042/serio1/input/input4 [1.528535] input: VirtualPS/2 VMware VMMouse as /devices/platform/i8042/serio1/input/input3 [1.532791] cryptd: max_cpu_qlen set to 1000 [1.534987] GPT:Primary header thinks Alt. header is not at the end of the disk. [1.534989] GPT:4612095 != 419430399 [1.534990] GPT:Alternate GPT header not at the end of the disk. [1.534991] GPT:4612095 != 419430399 [1.534992] GPT: Use GNU Parted to correct GPT errors. [1.535000] vda: vda1 vda14 vda15 [1.563361] FDC 0 is a S82078B [1.566411] AVX2 version of gcm_enc/dec engaged. [1.568630] AES CTR mode by8 optimization enabled [1.600840] virtio_net virtio0 ens3: renamed from eth0 [1.617473] usb 1-1: New USB device found, idVendor=0627, idProduct=0001, bcdDevice= 0.00 [1.620158] usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=5 [1.622469] usb 1-1: Product: QEMU USB Tablet [1.624186] usb 1-1: Manufacturer: QEMU [1.625735] usb 1-1: SerialNumber: 42 [1.628444] virtio_net virtio1 ens4: renamed from eth1 [1.645967] hid: raw HID events driver (C) Jiri Kosina [1.654600] usbcore: registered new interface driver usbhid [1.656528] usbhid: USB HID core driver [1.659587] input: QEMU QEMU USB Tablet as /devices/pci:00/:00:01.2/usb1/1-1/1-1:1.0/0003:0627:0001.0001/input/input5 [1.663583] hid-generic 0003:0627:0001.0001: input,hidraw0: USB HID v0.01 Mouse [QEMU QEMU USB Tablet] on usb-:00:01.2-1/input0 [ 242.955991] INFO: task systemd-udevd:183 blocked for more than 120 seconds. [ 242.957774] Not tainted 5.15.0-87-generic #97-Ubuntu [ 242.959137] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.961130] task:systemd-udevd state:D stack:0 pid: 183 ppid: 160 flags:0x4006 [ 242.963170] Call Trace: [ 242.963880] [ 242.964562] __schedule+0x24e/0x590 [ 242.965554] ? sched_clock_cpu+0x12/0xf0 [ 242.966583] schedule+0x69/0x110 [ 242.967454] schedule_preempt_disabled+0xe/0x20 [ 242.968641] __mutex_lock.constprop.0+0x267/0x490 [ 242.969879] ? try_to_wake_up+0x200/0x5a0 [ 242.970966] __mutex_lock_slowpath+0x13/0x20 [ 242.972063] mutex_lock+0x38/0x50 [ 242.972959] add_early_randomness+0x1c/0xd0 [ 242.974038] hwrng_register+0x164/0x1d0 [ 242.975039] virtrng_scan+0x19/0x30 [virtio_rng] [ 242.976214] virtio_dev_probe+0x1dd/0x260 [ 242.977322] really_probe+0x21f/0x420 [ 242.978293] __driver_probe_device+0xe8/0x140 [ 242.979404] driver_probe_device+0x23/0xc0 [ 242.980534] __driver_attach+0xf7/0x1f0 [ 242.982149] ? __device_attach_driver+0x140/0x140 [ 242.984057] bus_for_each_dev+0x7c/0xd0 [ 242.985659] driver_attach+0x1e/0x30 [ 242.987145] bus_add_driver+0x148/0x220 [ 242.988742] ? vunmap_range_noflush+0x3d5/0x470 [ 242.990581] driver_register+0x95/0x100 [ 242.992154] ? 0xc01e1000 [ 242.993551] register_virtio_driver+0x20/0x40 [ 242.995339] virtio_rng_driver_init+0x15/0x1000 [virtio_rng] [ 242.997587] do_one_initcall+0x46/0x1e0 [ 242.999177] ?
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.15.0.1054.50)
All autopkgtests for the newly accepted linux-meta-kvm (5.15.0.1054.50) for jammy have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/9858-0ubuntu3.4 (amd64) digimend-dkms/10-4ubuntu0.1 (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-kvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056491] Comment bridged from LTC Bugzilla
--- Comment From cha...@us.ibm.com 2024-03-19 14:42 EDT--- Regarding the main issue with the unable to mount to root, do you get the same errors prior to it as in the working installation? Are the kernel commandline the same? Any other differences? -- 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/2056491 Title: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block` Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le Power9 or Power10 : error: out of memory. Press any key to continue... OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003) (powerpc64le-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 (Ubuntu 6.8.0-11.11-generic 6.8.0-rc4) Detected machine type: 0101 command line: BOOT_IMAGE=/casper/vmlinux quiet --- Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0e67 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 instantiating rtas at 0x1ec3... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x1078 -> 0x1078179e Device tree struct 0x1079 -> 0x107a Quiescing Open Firmware ... Booting Linux via __start() @ 0x0a75 ... [0.019184] plpks: POWER LPAR Platform KeyStore is not supported or enabled [0.114052] SED: plpks not available [0.114507] /dev/root: Can't open blockdev [0.114520] List of all bdev filesystems: [0.114523] ext3 [0.114523] ext2 [0.114525] ext4 [0.114527] squashfs [0.114529] vfat [0.114531] fuseblk [0.114532] [0.114535] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.114540] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-11-generic #11-Ubuntu [0.114545] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1030.00 (NH1030_017) hv:phyp pSeries [0.114551] Call Trace: [0.114553] [c6403b40] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.114562] [c6403b70] [c01926ec] panic+0x300/0x524 [0.114568] [c6403c10] [c301146c] mount_root_generic+0x208/0x448 [0.114574] [c6403ce0] [c30118d8] prepare_namespace+0x98/0x430 [0.114580] [c6403d70] [c3010820] kernel_init_freeable+0x32c/0x37c [0.114585] [c6403de0] [c00115ec] kernel_init+0x34/0x298 [0.114591] [c6403e50] [c000dfbc] ret_from_kernel_user_thread+0x14/0x1c [0.114596] --- interrupt: 0 at 0x0 [0.117006] pstore: backend (nvram) writing error (-1) [0.119362] Rebooting in 10 seconds.. This is the message from a Power10(9080-HEX), but the same is happening on a PowrerVM-Power9 (9009-22A) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056491/+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 2056491] Comment bridged from LTC Bugzilla
--- Comment From cha...@us.ibm.com 2024-03-19 14:32 EDT--- error: out of memory. Press any key to continue... The above messages are likely coming from the bootloader (grub2). Which version of grub2 is being used? How exactly is the install being done, e.g. via USB or some other method? Can you try booting into the openfirmware prompt (Press 8 after restarting or activating the LPAR) and print out the real-base value? It should hopefully be set to the default value of 0xC0. 0 > printenv real-base -- Partition: common Signature: 0x70 --- real-basec0 c0 ok If not 0xC0 then try setting it with 0 > setenv real-base c0 -- 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/2056491 Title: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block` Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le Power9 or Power10 : error: out of memory. Press any key to continue... OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003) (powerpc64le-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 (Ubuntu 6.8.0-11.11-generic 6.8.0-rc4) Detected machine type: 0101 command line: BOOT_IMAGE=/casper/vmlinux quiet --- Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0e67 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 instantiating rtas at 0x1ec3... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x1078 -> 0x1078179e Device tree struct 0x1079 -> 0x107a Quiescing Open Firmware ... Booting Linux via __start() @ 0x0a75 ... [0.019184] plpks: POWER LPAR Platform KeyStore is not supported or enabled [0.114052] SED: plpks not available [0.114507] /dev/root: Can't open blockdev [0.114520] List of all bdev filesystems: [0.114523] ext3 [0.114523] ext2 [0.114525] ext4 [0.114527] squashfs [0.114529] vfat [0.114531] fuseblk [0.114532] [0.114535] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.114540] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-11-generic #11-Ubuntu [0.114545] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1030.00 (NH1030_017) hv:phyp pSeries [0.114551] Call Trace: [0.114553] [c6403b40] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.114562] [c6403b70] [c01926ec] panic+0x300/0x524 [0.114568] [c6403c10] [c301146c] mount_root_generic+0x208/0x448 [0.114574] [c6403ce0] [c30118d8] prepare_namespace+0x98/0x430 [0.114580] [c6403d70] [c3010820] kernel_init_freeable+0x32c/0x37c [0.114585] [c6403de0] [c00115ec] kernel_init+0x34/0x298 [0.114591] [c6403e50] [c000dfbc] ret_from_kernel_user_thread+0x14/0x1c [0.114596] --- interrupt: 0 at 0x0 [0.117006] pstore: backend (nvram) writing error (-1) [0.119362] Rebooting in 10 seconds.. This is the message from a Power10(9080-HEX), but the same is happening on a PowrerVM-Power9 (9009-22A) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056491/+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 2042363] Comment bridged from LTC Bugzilla
--- Comment From david_pa...@uk.ibm.com 2024-03-19 13:53 EDT--- Is there an update from Canonical please? Can we provide any further information or trace to help diagnose this issue ? -- 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/2042363 Title: AIX 7.3 NFS client frequently returns an EIO error to an application when reading or writing to a file that has been locked with fcntl() on a Ubuntu 20.04 NFSV4 server Status in linux package in Ubuntu: New Bug description: ---Problem Description--- AIX 7.3 NFS client frequently returns an EIO error to an application when reading or writing to a file that has been locked with fcntl(). NFS server is Ubuntu 20.04.6 LTS, GNU/Linux 5.4.0-139-generic x86_64. The problem does not appear to affect other combinations of NFS client (including AIX 7.2) with this NFS server. The AIX team have indicated that the cause of the EIO is triggered by the NFS server returning a BAD_SEQID error which leads to the AIX NFS client incorrectly zeroing the stateid, which then leads to the NFS server returning a BAD_STATEID error and the NFS client then returns the EIO error. The AIX team would like to understand why the BAD_SEQID has been returned. ---uname output--- Linux duckseason 5.4.0-156-generic #173-Ubuntu SMP Tue Jul 11 07:25:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Machine Type = VMware ESXi Server 7.0 4 x Intel(R) Xeon(R) Gold 6348H CPU @ 2.30GHz ---Steps to Reproduce--- We cannot offer a simple way to recreate the problem as it involves IBM MQ running on two primary machines (AIX) using the Ubuntu server for it's HA NFSv4 storage. However, we can provide any requested trace or dumps from any or all of the involved machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042363/+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 2051050] Re: Audio balancing setting doesn't work with the cirrus codec
This bug is awaiting verification that the linux-aws- fips/5.15.0-1056.61+fips1 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-jammy-linux-aws-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-jammy-linux-aws-fips-v2 verification-needed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051050 Title: Audio balancing setting doesn't work with the cirrus codec Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2051050 Currently this patch is in the linux-next, and will be in the mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble kernel, Noble kernel will have this patch automatically. [Impact] In the gnome audio setting, if we adjust balancing setting, it doesn't work at all on a Dell machine with cirrus codec, that is because with the current driver, the exported amixer controls can't be handled by pulseaudio. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booted with the patched kernel, move the bar to the left or right to adjust the balance, we could hear the sound from left channel or right channel accordingly. [Where problems could occur] This change will not create "Master Volume" amixer controls, probably will make the audio control malfunction, that is we couldn't control playback or capture volume correctly, but this regression possibility is very low, we already tested the patch on the machines with cirrus codec, they all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051050/+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 2043811] Re: AWS: arm64: pauth: don't sign leaf functions
This bug is awaiting verification that the linux-aws- fips/5.15.0-1056.61+fips1 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-jammy-linux-aws-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-jammy-linux-aws-fips-v2 verification-needed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2043811 Title: AWS: arm64: pauth: don't sign leaf functions Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Jammy: Fix Released Bug description: SRU Justification [Impact] From our experiments, we found that not signing leaf functions on AWS Graviton instances helps improve application performance. We would like to have the patch https://github.com/torvalds/linux/commit/c68cf5285e1896a2b725ec01a1351f08610165b8 backported to Ubuntu 5.15, 5.19 and 6.2 kernels. We saw some of these performance improvements: NGINX 1%, MySQL 2%, PyTorch 2% [Test Plan] AWS tested. [Regression Potential] Arm64 binaries may not work correctly. [Other Info] SF: #00372369 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2043811/+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 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out
This bug is awaiting verification that the linux-aws- fips/5.15.0-1056.61+fips1 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-jammy-linux-aws-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-jammy-linux-aws-fips-v2 verification-needed-jammy-linux-aws-fips -- 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/2036239 Title: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: In Progress Bug description: [Impact] * Issue is causing transmit hang on E810 ports with bonding enabled. * Based on the provided logs, TX hang can last for even a couple of minutes, but in most scenarios, the network will be recovered after the ice driver performs a PF reset (TX hang handler routine). * Originally, the issue was observed during Tempest tests on a newly created OpenStack cluster, resulting in a lack of certification. [Fix] * Initially, a workaround has been proposed by Intel engineers to disable LAG initialization [1]. This change has been tested in an environment where reproduction is easily achieved. After multiple iterations, no reproduction has been observed. * Shortly after, Intel proposed a patch [2] to disable LAG initialization if NVM does not expose proper capabilities. [Test Plan] * To reproduce the issue, over a 20-node cluster was used with Ceph-based storage. The problem could sometimes manifest while deploying a cluster or after the cluster was already deployed during the Tempest test run. * The issue could appear on a random node, making reproduction hard to achieve. * Multiple stress tests on single host with similar configuration did not trigger a reproduction. [Where problems could occur] * All ice drivers with ice_lag_event_handler registered can expose the issue. This handler is not implemented in 20.04 * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this capability will be released. Although potentialy issue is caused by using features without proper FW support [2], we want to take a closer look once NVMs with proper support are introduced. [1] - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40 [2] - https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html 4d50fcdc2476eef94c14c6761073af5667bb43b6 [Other Info] * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice driver backported from mainline kernel from before patch [2] was added. * Original description of the case below: I'm having issues with an Intel E810-XXV card on a Dell server under Ubuntu Jammy. Details: - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results. - using a bond over the two ports of the same card, at 25Gbps to two different switches, bond is using LACP with hash layer3+4 and fast timeout. But I believe the bug is not directly related to bonding as the problem seems to be in the interface. - machine installed by maas. No issues during installation, but at that time bond is not formed yet, later when linux is booted, the bond is formed and works without issues for a while - it works for about 2 to 3 hours fine, then the issue starts (may or may not be related to network load, but it seems that it is triggered by some tests that I run after openstack finishes installing) - one of the legs of the bond freezes and everything that would go to that lag is discarded, in and out, ping to random external hosts start losing every second packet - after some time you can see on the kernel log messages about "NETDEV WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack trace - the switch does log that the bond is flapping --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root
[Kernel-packages] [Bug 2044131] Re: i915 regression introduced with 5.5 kernel
This bug is awaiting verification that the linux-aws- fips/5.15.0-1056.61+fips1 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-jammy-linux-aws-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-jammy-linux-aws-fips-v2 verification-needed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2044131 Title: i915 regression introduced with 5.5 kernel Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.15 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.15 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-hwe-5.15 source package in Jammy: Invalid Status in linux source package in Mantic: Fix Released Status in linux-hwe-5.15 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-hwe-5.15 source package in Noble: Invalid Bug description: [ Impact ] Commit 8f4b1068e7fc3df1a77ac8151767e56b208cc87f introduced some timing checks which have been proven invalid for at least some hardware setups. A user trying to run Focal with HWE 5.15 kernel is not able to get any video output. After going through bisection between 5.4 and 5.5 this commit was identified. Reverting it on top of Focal HWE kernel fixes the issue. The issue has been addressed upstream in DRM tree (20c2dbff342aec13bf93c2f6c951da198916a455) and has been merge into linux-next (e0ef2daa8ca8ce4dbc2fd0959e383b753a87fd7d). dmesg and lspci from the affected configuration are attached to this bug. [ Test Plan ] 1. Boot the affected hardware with Ubuntu desktop running kernel v5.5 or higher. 2. Wait until boot finishes and see the blank screen. Actual result: there is no video output visible. Expected result: normal boot process should be visible (e.g. splash), then GUI should appear. [ Where problem could occur ] This bug was a result of assumptions in the checks that turned out to be not valid for some hardware. The checks were removed from global intel_mode_valid function and moved into connector specific .mode_valid() hooks, entirely skiping BXT/GLK DSI connectors. This should keep the checks where appropriate and skip for hardware that does not comply to them. [ Other info ] Original bug description: There is a regression preventing a user to upgrade from 5.4 kernel to anything that's higher than 5.5. When using such kernel the image orientation is wrong (rotated by 90°C). Also the kernel log contains: wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06 wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 24.8.0, H2C version 12 wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 80x25 wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga console wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory information wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:o> wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC firmware i915/glk_dmc_ver1_04.bin (v> wrz 15 09:19:49 desktop kernel: wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.> wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]' (full stack trace attached) The video hardware in use is: 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 [8086:3185] (rev 06) (prog-if 00 [VGA controller]) (...) Kernel driver in use: i915 Kernel modules: i915 The user wanted to upgrade from bionic to focal with HWE kernel (they needed it due to some networking hardware they wanted to have supported by the newer kernel). The user was testing mainline stable kernels and noticed that the last working kernel was the 5.4 series, while anything starting from 5.5 and above is BROKEN (symptoms as described in the first paragraph above). Together with the user we have run a bisection between v5.4 and v5.5 on the upstream stable kernel and we were
[Kernel-packages] [Bug 2047634] Re: Reject connection when malformed L2CAP signal packet is received
This bug is awaiting verification that the linux-aws- fips/5.15.0-1056.61+fips1 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-jammy-linux-aws-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-jammy-linux-aws-fips-v2 verification-needed-jammy-linux-aws-fips -- 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/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Released Bug description: The patch is merged in mainline kernel v6.7-rc7, so Noble kernel already have this fix. And this patch is CCed to sta...@vger.kernel.org, M and L kernel will have this fix with the SRU update sooner or later. For Jammy kernel, an OEM customer is waiting for this patch to be merged to Jammy kernel and OEM kernel, here I submit the review reqeust for Jammy only. [Impact] An OEM customer want to do the bluetooth profile testing suite (PTS) test, and they found if sending 2 commands and one of them is "unknown comands", the bluetooth stack doesn't reply the ack as expected, this broke the customer's PTS test. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. And I also tested the patched kernel with 2 bt headsets, 1 bt keyboard and my mobile phone, all worked as well as before. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. It has possibility to make some bt devices could not work with patched kernel, but this possibility is very low, I tested the patched kernel with 2 bt headsets, 1 bt keyboard and my Android mobile phone, all worked as well as before. [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+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 2048404] Re: Don't WARN_ON_ONCE() for a broken discovery table
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1056.61+fips1 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-jammy-linux-aws-fips' to
'verification-done-jammy-linux-aws-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-aws-fips' to
'verification-failed-jammy-linux-aws-fips'.
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-jammy-linux-aws-fips-v2
verification-needed-jammy-linux-aws-fips
--
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/2048404
Title:
Don't WARN_ON_ONCE() for a broken discovery table
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Won't Fix
Bug description:
SRU Justification
[Impact]
perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table
The kernel warning message is triggered, when SPR MCC is used.
[ 17.945331] [ cut here ]
[ 17.946305] WARNING: CPU: 65 PID: 1 at
arch/x86/events/intel/uncore_discovery.c:184
intel_uncore_has_discovery_tables+0x4c0/0x65c
[ 17.946305] Modules linked in:
[ 17.946305] CPU: 65 PID: 1 Comm: swapper/0 Not tainted
5.4.17-2136.313.1-X10-2c+ #4
It's caused by the broken discovery table of UPI.
The discovery tables are from hardware. Except for dropping the broken
information, there is nothing Linux can do. Using WARN_ON_ONCE() is
overkilled.
Use the pr_info() to replace WARN_ON_ONCE(), and specify what uncore unit
is dropped and the reason.
[Fix]
Commit 5d515ee40cb57ea5331998f27df7946a69f14dc3 ('perf/x86/uncore:
Don't WARN_ON_ONCE() for a broken discovery table')
[Test]
AWS tested
[Regression potential]
Low regression potential. Only the code that prints the warning has
been changed.
[Other Info]
SF: #00347830
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048404/+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 2056491] Re: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block`
** Tags added: architecture-ppc64le bugnameltc-205876 severity-medium targetmilestone-inin--- -- 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/2056491 Title: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block` Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le Power9 or Power10 : error: out of memory. Press any key to continue... OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003) (powerpc64le-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 (Ubuntu 6.8.0-11.11-generic 6.8.0-rc4) Detected machine type: 0101 command line: BOOT_IMAGE=/casper/vmlinux quiet --- Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0e67 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 instantiating rtas at 0x1ec3... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x1078 -> 0x1078179e Device tree struct 0x1079 -> 0x107a Quiescing Open Firmware ... Booting Linux via __start() @ 0x0a75 ... [0.019184] plpks: POWER LPAR Platform KeyStore is not supported or enabled [0.114052] SED: plpks not available [0.114507] /dev/root: Can't open blockdev [0.114520] List of all bdev filesystems: [0.114523] ext3 [0.114523] ext2 [0.114525] ext4 [0.114527] squashfs [0.114529] vfat [0.114531] fuseblk [0.114532] [0.114535] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.114540] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-11-generic #11-Ubuntu [0.114545] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1030.00 (NH1030_017) hv:phyp pSeries [0.114551] Call Trace: [0.114553] [c6403b40] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.114562] [c6403b70] [c01926ec] panic+0x300/0x524 [0.114568] [c6403c10] [c301146c] mount_root_generic+0x208/0x448 [0.114574] [c6403ce0] [c30118d8] prepare_namespace+0x98/0x430 [0.114580] [c6403d70] [c3010820] kernel_init_freeable+0x32c/0x37c [0.114585] [c6403de0] [c00115ec] kernel_init+0x34/0x298 [0.114591] [c6403e50] [c000dfbc] ret_from_kernel_user_thread+0x14/0x1c [0.114596] --- interrupt: 0 at 0x0 [0.117006] pstore: backend (nvram) writing error (-1) [0.119362] Rebooting in 10 seconds.. This is the message from a Power10(9080-HEX), but the same is happening on a PowrerVM-Power9 (9009-22A) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056491/+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 2043811] Re: AWS: arm64: pauth: don't sign leaf functions
** Changed in: linux-aws (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2043811 Title: AWS: arm64: pauth: don't sign leaf functions Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Jammy: Fix Released Bug description: SRU Justification [Impact] From our experiments, we found that not signing leaf functions on AWS Graviton instances helps improve application performance. We would like to have the patch https://github.com/torvalds/linux/commit/c68cf5285e1896a2b725ec01a1351f08610165b8 backported to Ubuntu 5.15, 5.19 and 6.2 kernels. We saw some of these performance improvements: NGINX 1%, MySQL 2%, PyTorch 2% [Test Plan] AWS tested. [Regression Potential] Arm64 binaries may not work correctly. [Other Info] SF: #00372369 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2043811/+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 2055805] Re: touchpad not working with kernel 6.8
Somehow I can't get 6.8.0-20 after adding the ppa and updating. But in some way I got the 6.8.0-19 kernel now (from proposed?) and that's working fine with the touchpad. -- 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/2055805 Title: touchpad not working with kernel 6.8 Status in linux package in Ubuntu: Confirmed Bug description: After the standard update procedure and installation of a new version of the kernel, the touchpad on the MacBook Pro 13 - 2014 stopped working. Even the mouse cursor does not appear on the screen. If you select the old kernel version 6.6 in the bootloader options, then everything works correctly Ubuntu 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Mar 3 11:11:43 2024 InstallationDate: Installed on 2023-11-06 (118 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.6.0-14-generic root=UUID=2075733d-58de-4836-9c71-04dd00378200 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.6.0-14-generic N/A linux-backports-modules-6.6.0-14-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 430.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr430.0.0.0.0:bd12/17/2020:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 2058191] Re: Getting SIGSEGV and SIGILL in many programs
That's the one I'm currently using. The Ubuntu's 6.8.0-11 also have the same problem. I will check other versions. I think the 6.5 might be working On Tue, Mar 19, 2024, 11:15 AM Andrea Righi <2058...@bugs.launchpad.net> wrote: > Can you give it a try also with the latest upstream 6.8 (available here > https://kernel.ubuntu.com/mainline/v6.8.1/). This should help to verify > if it's an upstream issue or a specific issue with the Ubuntu kernel. > > Thanks! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2058191 > > Title: > Getting SIGSEGV and SIGILL in many programs > > Status in Ubuntu: > New > Status in linux package in Ubuntu: > New > > Bug description: > Okay, recently I upgraded to 24.04. I'm getting some SIGSEGV and > SIGILLs from time to time. Sometimes the entire computer freezes and i > can't even turn down unless i hold the power button for 5 secs. > > I tought it could be the kernel version, so I upgraded from Ubuntu's > 6.8.0-11.11+1 to mainline 6.8.1. However, it didn't fix. > > Here are some softwares i got SIGSEGV or SIGILLs: >- code-insiders (vscode) >- brave (Brave browser) >- bun (node.js alternative) >- node.js > > I know i should upload more logs, but I didn't find the errors in > syslog or journalctl. > > $ lsb_release -rd > - > No LSB modules are available. > Description: Ubuntu Noble Numbat (development branch) > Release: 24.04 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+bug/2058191/+subscriptions > > -- 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/2058191 Title: Getting SIGSEGV and SIGILL in many programs Status in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Okay, recently I upgraded to 24.04. I'm getting some SIGSEGV and SIGILLs from time to time. Sometimes the entire computer freezes and i can't even turn down unless i hold the power button for 5 secs. I tought it could be the kernel version, so I upgraded from Ubuntu's 6.8.0-11.11+1 to mainline 6.8.1. However, it didn't fix. Here are some softwares i got SIGSEGV or SIGILLs: - code-insiders (vscode) - brave (Brave browser) - bun (node.js alternative) - node.js I know i should upload more logs, but I didn't find the errors in syslog or journalctl. $ lsb_release -rd - No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+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 2058191] Re: Getting SIGSEGV and SIGILL in many programs
That's the one I'm currently using. The Ubuntu's 6.8.0-11 also have the same problem. I will check other versions. I think the 6.5 might be working Hide quoted text -- 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/2058191 Title: Getting SIGSEGV and SIGILL in many programs Status in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Okay, recently I upgraded to 24.04. I'm getting some SIGSEGV and SIGILLs from time to time. Sometimes the entire computer freezes and i can't even turn down unless i hold the power button for 5 secs. I tought it could be the kernel version, so I upgraded from Ubuntu's 6.8.0-11.11+1 to mainline 6.8.1. However, it didn't fix. Here are some softwares i got SIGSEGV or SIGILLs: - code-insiders (vscode) - brave (Brave browser) - bun (node.js alternative) - node.js I know i should upload more logs, but I didn't find the errors in syslog or journalctl. $ lsb_release -rd - No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+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 2043811] Re: AWS: arm64: pauth: don't sign leaf functions
Confirmed as working by Amazon. ** Tags removed: verification-needed-jammy-linux-aws ** Tags added: verification-done-jammy-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2043811 Title: AWS: arm64: pauth: don't sign leaf functions Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Jammy: In Progress Bug description: SRU Justification [Impact] From our experiments, we found that not signing leaf functions on AWS Graviton instances helps improve application performance. We would like to have the patch https://github.com/torvalds/linux/commit/c68cf5285e1896a2b725ec01a1351f08610165b8 backported to Ubuntu 5.15, 5.19 and 6.2 kernels. We saw some of these performance improvements: NGINX 1%, MySQL 2%, PyTorch 2% [Test Plan] AWS tested. [Regression Potential] Arm64 binaries may not work correctly. [Other Info] SF: #00372369 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2043811/+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 2053155] Re: Add DPLL and syncE support
** Changed in: linux-bluefield (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2053155
Title:
Add DPLL and syncE support
Status in linux-bluefield package in Ubuntu:
Invalid
Status in linux-bluefield source package in Jammy:
Fix Committed
Bug description:
* intro
Synchronous Ethernet, or SyncE, is an ITU-T standard for computer networking
that facilitates the transference of clock signals over the Ethernet physical
layer. It is used to pass timing from node to node and is particularly
important for mobile networks.
The DPLL subsystem in the Linux kernel provides a general interface
for configuring devices that use any kind of Digital PLL. This
subsystem is designed to manage the clock signal synchronization of a
device with an external clock signal.
* Explain the bug(s)
We need to support mlx5 SyncE feature. The following patches are needed.
[net-next,v8,0/9] Create common DPLL configuration API
[net-next,v8,1/9] dpll: documentation on DPLL subsystem interface
[net-next,v8,2/9] dpll: spec: Add Netlink spec in YAML
[net-next,v8,3/9] dpll: core: Add DPLL framework base functions
[net-next,v8,4/9] dpll: netlink: Add DPLL framework base functions
[net-next,v8,5/9] netdev: expose DPLL pin handle for netdevice
[net-next,v8,6/9] ice: add admin commands to access cgu configuration
[net-next,v8,7/9] ice: implement dpll interface to control cgu
[net-next,v8,8/9] ptp_ocp: implement DPLL ops
[net-next,v8,9/9] mlx5: Implement SyncE support using DPLL infrastructure
https://lore.kernel.org/netdev/20230913204943.1051233-1-vadim.fedore...@linux.dev/
* Brief explanation of fixes
We identify several dependent patches, especially related to netlink gap
between current master-next.
We cherry-pick/backport series of patches related to netlink.
* How to test
$ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \
--dump device-get
ex:
root@bfqa-dell013-roy-oob:~/mlnx-ofa_kernel-4.0# /root/tools-net/ynl/cli.py
--spec ~/netlink/specs/dpll.yaml --dump device-get
[{'clock-id': 5237736944144095348,
'id': 0,
'lock-status': 'unlocked',
'mode': 'manual',
'mode-supported': ['manual'],
'module-name': 'mlx5_core',
'type': 'eec'}]
$ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \
--do pin-get
ex:
root@bfqa-dell013-roy-oob:~# /root/tools-net/ynl/cli.py --spec
~/netlink/specs/dpll.yaml --dump pin-get
[{'capabilities': 4,
'clock-id': 5237736944144095348,
'id': 0,
'module-name': 'mlx5_core',
'parent-device': [{'direction': 'input',
'parent-id': 0,
'state': 'disconnected'}],
'phase-adjust-max': 0,
'phase-adjust-min': 0,
'type': 'synce-eth-port'},
{'capabilities': 4,
'clock-id': 5237736944144095348,
'id': 1,
'module-name': 'mlx5_core',
'parent-device': [{'direction': 'input',
'parent-id': 0,
'state': 'disconnected'}],
'phase-adjust-max': 0,
'phase-adjust-min': 0,
'type': 'synce-eth-port'}]
* detect whether your device supports DPLL/SyncE
root@bfqa-dell013-roy-oob:~/linux-bluefield-jammy# mlxreg -d 03:00.0
--reg_name MCAM --get -i "access_reg_group=2,feature_group=0"
Field Name| Data
===
access_reg_group | 0x0002
feature_group | 0x
mng_access_reg_cap_mask[0]| 0x0004
mng_access_reg_cap_mask[1]| 0x0060 --> must see 6
OR,
$ mlxfwmanager
showing “Enhanced-SyncE & PTP GM support”,
* list of patches applied to 5.15 jammy
based on
911f816f4c04 mlxbf_gige: fix receive packet race condition
we applied the following
83a11d94c436 UBUNTU: SAUCE: fix build error after resv_start_op
036b2fecd315 genetlink: allow families to use split ops directly
9f40a82f73ea genetlink: inline old iteration helpers
d8ae137b98fc genetlink: use iterator in the op to policy map dumping
095792a3a723 genetlink: add iterator for walking family ops
764747ba0085 genetlink: limit the use of validation workarounds to old ops
35b95f016392 genetlink: inline genl_get_cmd()
c448680485e6 genetlink: support split policies in ctrl_dumppolicy_put_op()
a17efffb8ce8 genetlink: add policies for both doit and dumpit in
ctrl_dumppolicy_start()
82af441de2fa genetlink: check for callback type at op load time
dc17c9675d6d genetlink: load policy based on validation flags
d867b1e130d3 genetlink: move the private fields in struct genl_family
b515a3664ef5 genetlink: piggy back on resv_op to default to a reject policy
1fa6e0ec60a4 genetlink: refactor the cmd <> policy mapping dump
c8ba54011c1d netlink: add helpers for extack attr presence checking
[Kernel-packages] [Bug 2055052] Re: net/sched: flower: Add lock protection when remove filter handle
** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2055052 Title: net/sched: flower: Add lock protection when remove filter handle Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: * intro As IDR can't protect itself from the concurrent modification, place idr_remove() under the protection of tp->lock. * how to fix need to backport the patch from Jianbo "net/sched: flower: Add lock protection when remove filter handle" https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=1fde0ca3a0de7e9f917668941156959dd5e9108b * reproduce and verification It's hard to reproduce because it is a race condition we found in k8s+ovn deployment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2055052/+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 2055086] Re: mlxbf_gige: add support for pause frame counters
** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2055086 Title: mlxbf_gige: add support for pause frame counters Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] The BlueField-2 and BlueField-3 silicon designs include a provision for reporting pause frame counters, but the driver (mlxbf_gige) does not have software support yet. [Fix] The fix is to update the mlxbf_gige driver to support the "get_pause_stats()" callback, which enables display of pause frame counters via "ethtool -I -a ooob_net0". The support of this callback was added to Linux kernel 5.9.0 [Test Case] * Reboot BF platform, and configure oob_net0 interface * Issue command "ethtool -I -a oob_net0" to display pause frame counters * Send in multiple streams of traffic to oob_net0 interface, e.g. from two or three simultaneous SCP operations * Re-issue "ethtool -I -a oob_net0" and note difference in output [Regression Potential] The changed logic extends the ethtool support, so low risk for any problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2055086/+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 2054845] Re: mlxbf-gige: support fixed phy for Bobcat
** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2054845 Title: mlxbf-gige: support fixed phy for Bobcat Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Bobcat is a new board which doesn't have an external PHY connected to the OOB. There are no MDIO busses involved and no PHY involved. The OOB is directly connected to the switch (MAC to MAC). SO we need to use the linux fixed phy to be able to emulate the mdio behavior and load the ethernet driver. [Fix] * Register the fixed-phy register in the case of the bobcat. [Test Case] * Important: For testing on the bobcat board, make sure the corresponding UEFI image is also loaded, otherwise, the oob driver will fail to load. For other board, it is backward compatible. * Check if the mlxbf-gige is loaded on bobcat * Check that it is using the fixed-phy via dmesg | grep PHY * check that the oob interface is pingable * check that files can be copied over via oob interface * rmmod/modprobe * ifconfig up/down * reboot test [Regression Potential] * Redo all the OOB testing on other boards (moonraker) and make sure the bobcat changes dont trigger any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2054845/+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 2056364] Re: Add test script for DPLL
** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2056364 Title: Add test script for DPLL Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: * intro In bug 2053155 "Add DPLL and syncE support" below: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2053155 It requires using a yaml spec file, dpll.yaml, and a python script, cli.py, to verify the correctness. ex: $ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \ --dump device-get We've found that the script and spec file are missing in current repo (Ubuntu-bluefield-5.15.0-1037.39). * how to fix Since the existing Bluefield-5.15 doesn't have the tools/net/ynl directory, the efforts to cherry-pick all individual patches shouldn't be too hard due to no dependencies and most likely no conflict, but there are around 200 patches in tools/net/ynl $ git log --oneline tools/net/ynl/ | wc -l 205 and for Documentation/netlink/genetlink.yaml (a dependent file for dpll.yaml) $ git log --oneline Documentation/netlink/genetlink.yaml | wc -l 15 So we decided to just create a new patch consisting all the required files, shown below: create mode 100644 Documentation/netlink/genetlink.yaml create mode 100644 tools/net/ynl/cli.py create mode 100644 tools/net/ynl/lib/__init__.py create mode 100644 tools/net/ynl/lib/nlspec.py create mode 100644 tools/net/ynl/lib/ynl.py To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2056364/+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 2056718] Re: openvswitch gentling validation warning: missing .resv_start_op
** Changed in: linux-bluefield (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2056718
Title:
openvswitch gentling validation warning: missing .resv_start_op
Status in linux-bluefield package in Ubuntu:
New
Status in linux-bluefield source package in Jammy:
Fix Committed
Bug description:
Intro:
==
When hit a kernel warning when loading openvswitch kernel module. Digging
into the source code, we found it's due to the code snippet
if (WARN_ON(i.cmd >= family->resv_start_op &&
(i.doit.validate || i.dumpit.validate)))
return -EINVAL;
in the gene_validate_ops() in net/netlink/genetlink.c, introduced in
108880a07bab genetlink: add iterator for walking family ops
from buglink about DPLL/SynCE
https://bugs.launchpad.net/bugs/2053155
How to fix:
===
We need to cherry-pick the missing patch
Fixes: e4ba4554209f ("net: openvswitch: add missing .resv_start_op")
Author: Jakub Kicinski
Date: Thu Oct 27 20:25:01 2022 -0700
net: openvswitch: add missing .resv_start_op
I missed one of the families in OvS when annotating .resv_start_op.
This triggers the warning added in commit ce48ebdd5651 ("genetlink:
limit the use of validation workarounds to old ops").
Reported-by: syzbot+40eb8c0447c0e47a7...@syzkaller.appspotmail.com
Fixes: 9c5d03d36251 ("genetlink: start to validate reserved header bytes")
Link: https://lore.kernel.org/r/20221028032501.2724270-1-k...@kernel.org
Signed-off-by: Jakub Kicinski
Thanks!
How to reproduce:
=
simply load the openvswitch.ko and dmesg
[ 1083.518212] WARNING: CPU: 2 PID: 17269 at net/netlink/genetlink.c:554
genl_validate_ops+0x134/0x254
...
[ 1083.518306] CPU: 2 PID: 17269 Comm: modprobe Tainted: GW OE
5.15.0-1037.39.10.g319565b-bluefield #g319565b
[ 1083.518309] Hardware name: https://www.mellanox.com BlueField
SoC/BlueField SoC, BIOS 4.7.0.13056 Feb 28 2024
[ 1083.518311] pstate: 0049 (nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 1083.518313] pc : genl_validate_ops+0x134/0x254
[ 1083.518315] lr : genl_validate_ops+0x68/0x254
[ 1083.518317] sp : 8a773810
[ 1083.518318] x29: 8a773810 x28: 8a773ba0 x27:
b1ea36f87318
[ 1083.518321] x26: b1ea36f8cd20 x25: 0001 x24:
b1ea36f8cda8
[ 1083.518323] x23: x22: 0001 x21:
b1ea36f87210
[ 1083.518325] x20: b1ea36f8b410 x19: 0001 x18:
[ 1083.518328] x17: 000d00020008 x16: b1ea4b70c2d0 x15:
003c00010006
[ 1083.518330] x14: 68746170 x13: x12:
0001
[ 1083.518332] x11: x10: x9 :
b1ea4b709a5c
[ 1083.518335] x8 : x7 : x6 :
b1ea4d4218c0
[ 1083.518337] x5 : 0004 x4 : x3 :
0001
[ 1083.518339] x2 : x1 : x0 :
0003
[ 1083.518341] Call trace:
[ 1083.518343] genl_validate_ops+0x134/0x254
[ 1083.518344] genl_register_family+0x30/0x1f4
[ 1083.518347] dp_init+0xd4/0x174 [openvswitch]
[ 1083.518360] do_one_initcall+0x4c/0x250
[ 1083.518364] do_init_module+0x50/0x260
[ 1083.518368] load_module+0x9fc/0xbe0
[ 1083.518370] __do_sys_finit_module+0xa8/0x114
[ 1083.518372] __arm64_sys_finit_module+0x28/0x3c
[ 1083.518375] invoke_syscall+0x78/0x100
[ 1083.518379] el0_svc_common.constprop.0+0x54/0x184
[ 1083.518381] do_el0_svc+0x30/0xac
[ 1083.518383] el0_svc+0x48/0x160
[ 1083.518387] el0t_64_sync_handler+0xa4/0x12c
[ 1083.518390] el0t_64_sync+0x1a4/0x1a8
[ 1083.518392] ---[ end trace ec4279298c2ae7be ]---
[ 1083.830668] openvswitch: Open vSwitch switching datapath
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2056718/+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 2058191] Re: Getting SIGSEGV and SIGILL in many programs
Can you give it a try also with the latest upstream 6.8 (available here https://kernel.ubuntu.com/mainline/v6.8.1/). This should help to verify if it's an upstream issue or a specific issue with the Ubuntu kernel. Thanks! -- 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/2058191 Title: Getting SIGSEGV and SIGILL in many programs Status in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Okay, recently I upgraded to 24.04. I'm getting some SIGSEGV and SIGILLs from time to time. Sometimes the entire computer freezes and i can't even turn down unless i hold the power button for 5 secs. I tought it could be the kernel version, so I upgraded from Ubuntu's 6.8.0-11.11+1 to mainline 6.8.1. However, it didn't fix. Here are some softwares i got SIGSEGV or SIGILLs: - code-insiders (vscode) - brave (Brave browser) - bun (node.js alternative) - node.js I know i should upload more logs, but I didn't find the errors in syslog or journalctl. $ lsb_release -rd - No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+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)
Bump: PC: Lenovo Legion Y520-15IKBN SSD: Samsung SM951 M.2 PCIe SSD Drive (MZ-HPV256) --- lshw relevant parts: computer description: Notebook product: 80WK (LENOVO_MT_80WK_BU_idea_FM_Lenovo Y520-15IKBN) vendor: LENOVO version: Lenovo Y520-15IKBN serial: PF0UM7F3 width: 64 bits capabilities: smbios-3.0.0 dmi-3.0.0 smp vsyscall32 configuration: administrator_password=disabled boot=normal chassis=notebook family=IDEAPAD frontpanel_password=disabled keyboard_password=disabled power-on_password=disabled sku=LENOVO_MT_80WK_BU_idea_FM_Lenovo Y520-15IKBN uuid=e974c056-54a9-11e7-8ff5-54e1ad454041 (...) *-disk description: ATA Disk product: SAMSUNG MZHPV256 physical id: 0.0.0 bus info: scsi@3:0.0.0 logical name: /dev/sdb version: 500Q serial: S1X2NYAG800617 size: 238GiB (256GB) capabilities: gpt-1.00 partitioned partitioned:gpt configuration: ansiversion=5 guid=094cf7bd-71f3-4587-b26f-8cb0bd3ba964 logicalsectorsize=512 sectorsize=512 -- 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
[Kernel-packages] [Bug 2055686] Re: Drop ABI checks from kernel build
This bug is awaiting verification that the linux-aws/4.4.0-1167.182 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-xenial-linux-aws' to 'verification-done-xenial- linux-aws'. If the problem still exists, change the tag 'verification- needed-xenial-linux-aws' to 'verification-failed-xenial-linux-aws'. 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-xenial-linux-aws-v2 verification-needed-xenial-linux-aws -- 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/2055686 Title: Drop ABI checks from kernel build Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: Drop the internal checks on the kernel ABI, module lists, et al. These checks are now applied after the fact by the workflow manager. This allows us to validate change after the builds complete so we do no waste builds which were correct but not annotated at upload time. NOTE: we still record the ABI data and publish it in linux-buildinfo files. These are used to perform the external validation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055686/+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 2049358] Re: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1018.19 --- linux-oem-6.5 (6.5.0-1018.19) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1018.19 -proposed tracker (LP: #2057967) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2024.02.05) * The screen brightness is unable to adjust on BOE panel DPN#R6FD8 (LP: #2057430) - drm/amd/display: Re-add aux intercept disable delay generically for 2+ LTTPRs - drm/amd/display: Clear dpcd_sink_ext_caps if not set - drm/amd/display: Add monitor patch for specific eDP - drm/amd/display: Add monitor patch for specific eDP * Mute/mic LEDs no function on some HP EliteBook (LP: #2057785) - ALSA: hda/realtek: fix mute/micmute LEDs for HP EliteBook * mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 (LP: #2049358) - Revert "UBUNTU: SAUCE: net: wwan: t7xx: PCIe reset rescan" - Revert "UBUNTU: SAUCE: net: wwan: t7xx: Add AP CLDMA" - net: wwan: t7xx: Add AP CLDMA - wwan: core: Add WWAN fastboot port type - net: wwan: t7xx: Add sysfs attribute for device state machine - net: wwan: t7xx: Infrastructure for early port configuration - net: wwan: t7xx: Add fastboot WWAN port * Fix headphone mic detection issue on ALC897 (LP: #2056418) - SAUCE: ALSA: hda/realtek - Fix headset Mic no show at resume back for Lenovo ALC897 platform * Simplify kcontrol naming on Intel MTL platforms (LP: #2055866) - ASoC: dapm: Add a flag for not having widget name in kcontrol name - ASoC: SOF: topology: Add a token for dropping widget name in kcontrol name * Fix AMD brightness issue on AUO panel (LP: #2054773) - drm/amdgpu: make damage clips support configurable [ Ubuntu: 6.5.0-26.26 ] * mantic/linux: 6.5.0-26.26 -proposed tracker (LP: #2056049) * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts - debian/dkms-versions -- update from kernel-versions (main/s2024.02.05) * CVE-2024-26599 - pwm: Fix out-of-bounds access in of_pwm_single_xlate() * CVE-2024-26597 - net: qualcomm: rmnet: fix global oob in rmnet_policy * CVE-2024-1086 - netfilter: nf_tables: reject QUEUE/DROP verdict parameters * CVE-2024-1085 - netfilter: nf_tables: check if catch-all set element is active in next generation -- Timo Aaltonen Thu, 14 Mar 2024 22:22:07 +0200 ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-1085 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-1086 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-26597 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-26599 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] No modems were found sometimtes after reboot/poweroff Got below messages when it fails [ 1.294786] mtk_t7xx :05:00.0: enabling device ( -> 0002) [ 1.298085] mtk_t7xx :05:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [ 1.298108] mtk_t7xx :05:00.0: device [14c3:4d75] error status/mask=0010/0040 [ 1.298123] mtk_t7xx :05:00.0: [20] UnsupReq (First) [ 1.298136] mtk_t7xx :05:00.0: AER: TLP Header: 4001 000f 88824030 3e800100 [ 1.298460] mtk_t7xx :05:00.0: AER: can't recover (no error_detected callback) [ 3.302402] mtk_t7xx :05:00.0: Invalid device status 0x1 [Fix] Fibocom provides a fix for this issue which is included in linux-next now https://patchwork.kernel.org/project/netdevbpf/cover/meyp282mb26974aacdba0a16649d6f094bb...@meyp282mb2697.ausp282.prod.outlook.com/ 2dac6381c3da net: wwan: t7xx: Add fastboot WWAN port d27553c14f06 net: wwan: t7xx: Infrastructure for early port configuration 409c38d4f156 net: wwan: t7xx: Add sysfs attribute for device state machine e3caf184107a wwan: core: Add WWAN fastboot port type [Test Case] 1. Boot to OS. 2. Insert sim card to the system. 3. Check the gnome-settings with WWAN settings or check with command mmcli -L 4. Repeat 1, 2, 3 multiple times and make sure WWAN always exists
[Kernel-packages] [Bug 2054773] Re: Fix AMD brightness issue on AUO panel
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1018.19 --- linux-oem-6.5 (6.5.0-1018.19) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1018.19 -proposed tracker (LP: #2057967) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2024.02.05) * The screen brightness is unable to adjust on BOE panel DPN#R6FD8 (LP: #2057430) - drm/amd/display: Re-add aux intercept disable delay generically for 2+ LTTPRs - drm/amd/display: Clear dpcd_sink_ext_caps if not set - drm/amd/display: Add monitor patch for specific eDP - drm/amd/display: Add monitor patch for specific eDP * Mute/mic LEDs no function on some HP EliteBook (LP: #2057785) - ALSA: hda/realtek: fix mute/micmute LEDs for HP EliteBook * mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 (LP: #2049358) - Revert "UBUNTU: SAUCE: net: wwan: t7xx: PCIe reset rescan" - Revert "UBUNTU: SAUCE: net: wwan: t7xx: Add AP CLDMA" - net: wwan: t7xx: Add AP CLDMA - wwan: core: Add WWAN fastboot port type - net: wwan: t7xx: Add sysfs attribute for device state machine - net: wwan: t7xx: Infrastructure for early port configuration - net: wwan: t7xx: Add fastboot WWAN port * Fix headphone mic detection issue on ALC897 (LP: #2056418) - SAUCE: ALSA: hda/realtek - Fix headset Mic no show at resume back for Lenovo ALC897 platform * Simplify kcontrol naming on Intel MTL platforms (LP: #2055866) - ASoC: dapm: Add a flag for not having widget name in kcontrol name - ASoC: SOF: topology: Add a token for dropping widget name in kcontrol name * Fix AMD brightness issue on AUO panel (LP: #2054773) - drm/amdgpu: make damage clips support configurable [ Ubuntu: 6.5.0-26.26 ] * mantic/linux: 6.5.0-26.26 -proposed tracker (LP: #2056049) * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts - debian/dkms-versions -- update from kernel-versions (main/s2024.02.05) * CVE-2024-26599 - pwm: Fix out-of-bounds access in of_pwm_single_xlate() * CVE-2024-26597 - net: qualcomm: rmnet: fix global oob in rmnet_policy * CVE-2024-1086 - netfilter: nf_tables: reject QUEUE/DROP verdict parameters * CVE-2024-1085 - netfilter: nf_tables: check if catch-all set element is active in next generation -- Timo Aaltonen Thu, 14 Mar 2024 22:22:07 +0200 ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-1085 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-1086 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-26597 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-26599 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2054773 Title: Fix AMD brightness issue on AUO panel Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] When change brightness quickly on gnome menu, AUO panel will be stuck in previous brightness. [Fix] The TCON is random hung by PSR-SU. Force enable ffu mode on PSR-SU panel. [Test] Tested on hardware, the brightness is changed as expected. [Where problems could occur] It may break AMD display. The commit is already in v6.8-rc5, the platform is not fully supported in Jammy 5.15, So SRU oem-6.5 and mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054773/+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 2055866] Re: Simplify kcontrol naming on Intel MTL platforms
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1018.19 --- linux-oem-6.5 (6.5.0-1018.19) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1018.19 -proposed tracker (LP: #2057967) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2024.02.05) * The screen brightness is unable to adjust on BOE panel DPN#R6FD8 (LP: #2057430) - drm/amd/display: Re-add aux intercept disable delay generically for 2+ LTTPRs - drm/amd/display: Clear dpcd_sink_ext_caps if not set - drm/amd/display: Add monitor patch for specific eDP - drm/amd/display: Add monitor patch for specific eDP * Mute/mic LEDs no function on some HP EliteBook (LP: #2057785) - ALSA: hda/realtek: fix mute/micmute LEDs for HP EliteBook * mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 (LP: #2049358) - Revert "UBUNTU: SAUCE: net: wwan: t7xx: PCIe reset rescan" - Revert "UBUNTU: SAUCE: net: wwan: t7xx: Add AP CLDMA" - net: wwan: t7xx: Add AP CLDMA - wwan: core: Add WWAN fastboot port type - net: wwan: t7xx: Add sysfs attribute for device state machine - net: wwan: t7xx: Infrastructure for early port configuration - net: wwan: t7xx: Add fastboot WWAN port * Fix headphone mic detection issue on ALC897 (LP: #2056418) - SAUCE: ALSA: hda/realtek - Fix headset Mic no show at resume back for Lenovo ALC897 platform * Simplify kcontrol naming on Intel MTL platforms (LP: #2055866) - ASoC: dapm: Add a flag for not having widget name in kcontrol name - ASoC: SOF: topology: Add a token for dropping widget name in kcontrol name * Fix AMD brightness issue on AUO panel (LP: #2054773) - drm/amdgpu: make damage clips support configurable [ Ubuntu: 6.5.0-26.26 ] * mantic/linux: 6.5.0-26.26 -proposed tracker (LP: #2056049) * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts - debian/dkms-versions -- update from kernel-versions (main/s2024.02.05) * CVE-2024-26599 - pwm: Fix out-of-bounds access in of_pwm_single_xlate() * CVE-2024-26597 - net: qualcomm: rmnet: fix global oob in rmnet_policy * CVE-2024-1086 - netfilter: nf_tables: reject QUEUE/DROP verdict parameters * CVE-2024-1085 - netfilter: nf_tables: check if catch-all set element is active in next generation -- Timo Aaltonen Thu, 14 Mar 2024 22:22:07 +0200 ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-1085 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-1086 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-26597 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-26599 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2055866 Title: Simplify kcontrol naming on Intel MTL platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] We found some laptops from Lenovo and HP with Intel MTL platform suffer the same MIC-Mute led not working problem just like lp:2049569. [Fix] lp:2049569 adds switch/enum type of control on IPC4 to communicate correctly with MTL SoF FW. However, Lenovo and HP machines requires the additional patches from https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/ to fix the kcontrol naming problem to align with the MTL SoF FW. [Test Case] 1. Make sure the latest firmware-sof is installed. 2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. 3. The mic-mute led should be ON when mic-mute enabled, OFF when disabled. [Where problems could occur] It's only required for new sof-audio-pci-intel-mtl driver. The impact should be restricting. We may need more MTL machines to make sure the behavior is the aligned. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055866/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056418] Re: Fix headphone mic detection issue on ALC897
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1018.19 --- linux-oem-6.5 (6.5.0-1018.19) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1018.19 -proposed tracker (LP: #2057967) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2024.02.05) * The screen brightness is unable to adjust on BOE panel DPN#R6FD8 (LP: #2057430) - drm/amd/display: Re-add aux intercept disable delay generically for 2+ LTTPRs - drm/amd/display: Clear dpcd_sink_ext_caps if not set - drm/amd/display: Add monitor patch for specific eDP - drm/amd/display: Add monitor patch for specific eDP * Mute/mic LEDs no function on some HP EliteBook (LP: #2057785) - ALSA: hda/realtek: fix mute/micmute LEDs for HP EliteBook * mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 (LP: #2049358) - Revert "UBUNTU: SAUCE: net: wwan: t7xx: PCIe reset rescan" - Revert "UBUNTU: SAUCE: net: wwan: t7xx: Add AP CLDMA" - net: wwan: t7xx: Add AP CLDMA - wwan: core: Add WWAN fastboot port type - net: wwan: t7xx: Add sysfs attribute for device state machine - net: wwan: t7xx: Infrastructure for early port configuration - net: wwan: t7xx: Add fastboot WWAN port * Fix headphone mic detection issue on ALC897 (LP: #2056418) - SAUCE: ALSA: hda/realtek - Fix headset Mic no show at resume back for Lenovo ALC897 platform * Simplify kcontrol naming on Intel MTL platforms (LP: #2055866) - ASoC: dapm: Add a flag for not having widget name in kcontrol name - ASoC: SOF: topology: Add a token for dropping widget name in kcontrol name * Fix AMD brightness issue on AUO panel (LP: #2054773) - drm/amdgpu: make damage clips support configurable [ Ubuntu: 6.5.0-26.26 ] * mantic/linux: 6.5.0-26.26 -proposed tracker (LP: #2056049) * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts - debian/dkms-versions -- update from kernel-versions (main/s2024.02.05) * CVE-2024-26599 - pwm: Fix out-of-bounds access in of_pwm_single_xlate() * CVE-2024-26597 - net: qualcomm: rmnet: fix global oob in rmnet_policy * CVE-2024-1086 - netfilter: nf_tables: reject QUEUE/DROP verdict parameters * CVE-2024-1085 - netfilter: nf_tables: check if catch-all set element is active in next generation -- Timo Aaltonen Thu, 14 Mar 2024 22:22:07 +0200 ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-1085 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-1086 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-26597 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-26599 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2056418 Title: Fix headphone mic detection issue on ALC897 Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Headphone mic is lost after resume from S3 or reboot with plugin. [Fix] Restore the headphone mic detect logic for ALC897 after lost power. [Test] Tested on hardware, the headphone mic appears as plugin after boot or resume from S3, and works fine. [Where problems could occur] It may break ALC897 sound input. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2056418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057430] Re: The screen brightness is unable to adjust on BOE panel DPN#R6FD8
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1018.19 --- linux-oem-6.5 (6.5.0-1018.19) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1018.19 -proposed tracker (LP: #2057967) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2024.02.05) * The screen brightness is unable to adjust on BOE panel DPN#R6FD8 (LP: #2057430) - drm/amd/display: Re-add aux intercept disable delay generically for 2+ LTTPRs - drm/amd/display: Clear dpcd_sink_ext_caps if not set - drm/amd/display: Add monitor patch for specific eDP - drm/amd/display: Add monitor patch for specific eDP * Mute/mic LEDs no function on some HP EliteBook (LP: #2057785) - ALSA: hda/realtek: fix mute/micmute LEDs for HP EliteBook * mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 (LP: #2049358) - Revert "UBUNTU: SAUCE: net: wwan: t7xx: PCIe reset rescan" - Revert "UBUNTU: SAUCE: net: wwan: t7xx: Add AP CLDMA" - net: wwan: t7xx: Add AP CLDMA - wwan: core: Add WWAN fastboot port type - net: wwan: t7xx: Add sysfs attribute for device state machine - net: wwan: t7xx: Infrastructure for early port configuration - net: wwan: t7xx: Add fastboot WWAN port * Fix headphone mic detection issue on ALC897 (LP: #2056418) - SAUCE: ALSA: hda/realtek - Fix headset Mic no show at resume back for Lenovo ALC897 platform * Simplify kcontrol naming on Intel MTL platforms (LP: #2055866) - ASoC: dapm: Add a flag for not having widget name in kcontrol name - ASoC: SOF: topology: Add a token for dropping widget name in kcontrol name * Fix AMD brightness issue on AUO panel (LP: #2054773) - drm/amdgpu: make damage clips support configurable [ Ubuntu: 6.5.0-26.26 ] * mantic/linux: 6.5.0-26.26 -proposed tracker (LP: #2056049) * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts - debian/dkms-versions -- update from kernel-versions (main/s2024.02.05) * CVE-2024-26599 - pwm: Fix out-of-bounds access in of_pwm_single_xlate() * CVE-2024-26597 - net: qualcomm: rmnet: fix global oob in rmnet_policy * CVE-2024-1086 - netfilter: nf_tables: reject QUEUE/DROP verdict parameters * CVE-2024-1085 - netfilter: nf_tables: check if catch-all set element is active in next generation -- Timo Aaltonen Thu, 14 Mar 2024 22:22:07 +0200 ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-1085 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-1086 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-26597 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-26599 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2057430 Title: The screen brightness is unable to adjust on BOE panel DPN#R6FD8 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP To avoid conflicts, pull in 3 other small patches c4e532f75336 drm/amd/display: Re-add aux intercept disable delay generically for 2+ LTTPRs 923bbfe6c888 drm/amd/display: Clear dpcd_sink_ext_caps if not set 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] The first commit introduces no functional changes, it merely relocates the delay flag to dc_debug_options and makes some consequent modifications. The second commit introduce a new flag, but we don't use it. The third and forth commits add 4 panel IDs which should be pretty safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2057430/+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 2057785] Re: Mute/mic LEDs no function on some HP EliteBook
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1018.19 --- linux-oem-6.5 (6.5.0-1018.19) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1018.19 -proposed tracker (LP: #2057967) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2024.02.05) * The screen brightness is unable to adjust on BOE panel DPN#R6FD8 (LP: #2057430) - drm/amd/display: Re-add aux intercept disable delay generically for 2+ LTTPRs - drm/amd/display: Clear dpcd_sink_ext_caps if not set - drm/amd/display: Add monitor patch for specific eDP - drm/amd/display: Add monitor patch for specific eDP * Mute/mic LEDs no function on some HP EliteBook (LP: #2057785) - ALSA: hda/realtek: fix mute/micmute LEDs for HP EliteBook * mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 (LP: #2049358) - Revert "UBUNTU: SAUCE: net: wwan: t7xx: PCIe reset rescan" - Revert "UBUNTU: SAUCE: net: wwan: t7xx: Add AP CLDMA" - net: wwan: t7xx: Add AP CLDMA - wwan: core: Add WWAN fastboot port type - net: wwan: t7xx: Add sysfs attribute for device state machine - net: wwan: t7xx: Infrastructure for early port configuration - net: wwan: t7xx: Add fastboot WWAN port * Fix headphone mic detection issue on ALC897 (LP: #2056418) - SAUCE: ALSA: hda/realtek - Fix headset Mic no show at resume back for Lenovo ALC897 platform * Simplify kcontrol naming on Intel MTL platforms (LP: #2055866) - ASoC: dapm: Add a flag for not having widget name in kcontrol name - ASoC: SOF: topology: Add a token for dropping widget name in kcontrol name * Fix AMD brightness issue on AUO panel (LP: #2054773) - drm/amdgpu: make damage clips support configurable [ Ubuntu: 6.5.0-26.26 ] * mantic/linux: 6.5.0-26.26 -proposed tracker (LP: #2056049) * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts - debian/dkms-versions -- update from kernel-versions (main/s2024.02.05) * CVE-2024-26599 - pwm: Fix out-of-bounds access in of_pwm_single_xlate() * CVE-2024-26597 - net: qualcomm: rmnet: fix global oob in rmnet_policy * CVE-2024-1086 - netfilter: nf_tables: reject QUEUE/DROP verdict parameters * CVE-2024-1085 - netfilter: nf_tables: check if catch-all set element is active in next generation -- Timo Aaltonen Thu, 14 Mar 2024 22:22:07 +0200 ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-1085 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-1086 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-26597 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-26599 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2057785 Title: Mute/mic LEDs no function on some HP EliteBook Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Mantic: Won't Fix Status in linux-oem-6.5 source package in Noble: Won't Fix Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP EliteBook [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2057785/+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 2055805] Re: touchpad not working with kernel 6.8
@tijs not exactly that kernel, but a kernel that has all the fixes that are included in 6.8.1. :) If you are willing to do one more test to confirm that everything is fine in the next candidate kernel for 24.04, you could try with 6.8.0-20.20 from this ppa: https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/bootstrap -- 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/2055805 Title: touchpad not working with kernel 6.8 Status in linux package in Ubuntu: Confirmed Bug description: After the standard update procedure and installation of a new version of the kernel, the touchpad on the MacBook Pro 13 - 2014 stopped working. Even the mouse cursor does not appear on the screen. If you select the old kernel version 6.6 in the bootloader options, then everything works correctly Ubuntu 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Mar 3 11:11:43 2024 InstallationDate: Installed on 2023-11-06 (118 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.6.0-14-generic root=UUID=2075733d-58de-4836-9c71-04dd00378200 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.6.0-14-generic N/A linux-backports-modules-6.6.0-14-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 430.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr430.0.0.0.0:bd12/17/2020:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+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 2051835] Re: [24.04 FEAT] Memory hotplug vmem pages (s390x)
Patches that are needed for noble/24.04 submitted to the kernel teams mailing list: https://lists.ubuntu.com/archives/kernel-team/2024-March/149667.html https://lists.ubuntu.com/archives/kernel-team/2024-March/thread.html#149667 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-z-systems Status: New => In Progress ** Also affects: linux (Ubuntu Noble) Importance: High Status: In Progress ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- 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/2051835 Title: [24.04 FEAT] Memory hotplug vmem pages (s390x) Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Bug description: The current s390 specific memory hotplug backend allocates 'struct page' management structures for all standby memory regions, when those standby regions are detected at ipl time. The reason for this is, that setting standby online memory is supposed to succeed especially in memory constrained environments, since lack of free memory is likely the reason why additional memory is brought online. If in such cases 'struct pages' would have to be allocated before memory could be brought up, this would likely fail, and contradict the whole rationale of memory hotplug. However pre-allocating memory for 'struct pages' comes with the downside that for highly unbalanced ratios of online/standby memory a system might even fail to ipl, because there is not enough memory available for all possible struct pages which are required for standby memory. The idea is to improve the situation: when standby memory is brought online, the memory for struct pages (and maybe other management structures) required for this new memory area should be taken from the online memory, instead of pre-allocating them. This would solve the problems with unbalanced ratios as described above. Note: there are intentions to tell customers that they should always define the maximum size of standby memory for their LPAR activation profiles. This would allow for maximum flexibility for all LPARs during runtime, given that the amount of standby memory cannot be changed during runtime. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2051835/+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 2055805] Re: touchpad not working with kernel 6.8
Latest mainline build of kernel 6.8.1 is working. Touchpad on MacbookPro 2012 is working now. Thanks! This kernel is coming to Ubuntu 24.04? -- 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/2055805 Title: touchpad not working with kernel 6.8 Status in linux package in Ubuntu: Confirmed Bug description: After the standard update procedure and installation of a new version of the kernel, the touchpad on the MacBook Pro 13 - 2014 stopped working. Even the mouse cursor does not appear on the screen. If you select the old kernel version 6.6 in the bootloader options, then everything works correctly Ubuntu 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Mar 3 11:11:43 2024 InstallationDate: Installed on 2023-11-06 (118 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.6.0-14-generic root=UUID=2075733d-58de-4836-9c71-04dd00378200 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.6.0-14-generic N/A linux-backports-modules-6.6.0-14-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 430.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr430.0.0.0.0:bd12/17/2020:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+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 2055866] Re: Simplify kcontrol naming on Intel MTL platforms
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2055866 Title: Simplify kcontrol naming on Intel MTL platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] We found some laptops from Lenovo and HP with Intel MTL platform suffer the same MIC-Mute led not working problem just like lp:2049569. [Fix] lp:2049569 adds switch/enum type of control on IPC4 to communicate correctly with MTL SoF FW. However, Lenovo and HP machines requires the additional patches from https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/ to fix the kcontrol naming problem to align with the MTL SoF FW. [Test Case] 1. Make sure the latest firmware-sof is installed. 2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. 3. The mic-mute led should be ON when mic-mute enabled, OFF when disabled. [Where problems could occur] It's only required for new sof-audio-pci-intel-mtl driver. The impact should be restricting. We may need more MTL machines to make sure the behavior is the aligned. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055866/+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 2051835] Re: [24.04 FEAT] Memory hotplug vmem pages (s390x)
** Summary changed: - [24.04 FEAT] Memory hotplug vmem pages + [24.04 FEAT] Memory hotplug vmem pages (s390x) -- 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/2051835 Title: [24.04 FEAT] Memory hotplug vmem pages (s390x) Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: The current s390 specific memory hotplug backend allocates 'struct page' management structures for all standby memory regions, when those standby regions are detected at ipl time. The reason for this is, that setting standby online memory is supposed to succeed especially in memory constrained environments, since lack of free memory is likely the reason why additional memory is brought online. If in such cases 'struct pages' would have to be allocated before memory could be brought up, this would likely fail, and contradict the whole rationale of memory hotplug. However pre-allocating memory for 'struct pages' comes with the downside that for highly unbalanced ratios of online/standby memory a system might even fail to ipl, because there is not enough memory available for all possible struct pages which are required for standby memory. The idea is to improve the situation: when standby memory is brought online, the memory for struct pages (and maybe other management structures) required for this new memory area should be taken from the online memory, instead of pre-allocating them. This would solve the problems with unbalanced ratios as described above. Note: there are intentions to tell customers that they should always define the maximum size of standby memory for their LPAR activation profiles. This would allow for maximum flexibility for all LPARs during runtime, given that the amount of standby memory cannot be changed during runtime. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2051835/+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 2058381] [NEW] Compression of ARM64 kernels causes problems with secureboot and systemd-boot
Public bug reported: Hello, I'm trying to deploy an Ubuntu Server on arm64 with securbeoot and UKIs. I'm running into the problem that the shipped kernel is just a plain gzip compressed version of the kernel image. This causes two issues: - sbsign refuses to sign the kernel without uncompressing it first (Invalid DOS header magic) - systemd-stub/systemd-boot don't recognize this kernel as a valid binary (Bad kernel image: Load error\n Failed to execute Ubuntu Noble Numbat (development branch) (\EFI\Linux\ubuntu-6.8.0-11-generic.efi): Load error) Debian just ships an uncompressed kernel and Fedora ships a PE binary (which they can do because they dropped BIOS support, so this cannot be adopted for Ubuntu). Shipping an uncompressed kernel would be the easiest switch from my view, only causing problems on small /boot partitions or ESP partitions, respectively. The current version in Ubuntu causes unexpected behaviour with various bootchain tools. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2058381 Title: Compression of ARM64 kernels causes problems with secureboot and systemd-boot Status in linux-meta package in Ubuntu: New Bug description: Hello, I'm trying to deploy an Ubuntu Server on arm64 with securbeoot and UKIs. I'm running into the problem that the shipped kernel is just a plain gzip compressed version of the kernel image. This causes two issues: - sbsign refuses to sign the kernel without uncompressing it first (Invalid DOS header magic) - systemd-stub/systemd-boot don't recognize this kernel as a valid binary (Bad kernel image: Load error\n Failed to execute Ubuntu Noble Numbat (development branch) (\EFI\Linux\ubuntu-6.8.0-11-generic.efi): Load error) Debian just ships an uncompressed kernel and Fedora ships a PE binary (which they can do because they dropped BIOS support, so this cannot be adopted for Ubuntu). Shipping an uncompressed kernel would be the easiest switch from my view, only causing problems on small /boot partitions or ESP partitions, respectively. The current version in Ubuntu causes unexpected behaviour with various bootchain tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2058381/+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 2058381] Re: Compression of ARM64 kernels causes problems with secureboot and systemd-boot
The first failure can be easily reproduced by trying to sign vmlinuz, The second one by using mkosi (https://github.com/systemd/mkosi): ``` $ mkosi genkey $ mkosi --distribution=ubuntu --architecture=arm64 --release=noble -p linux-image-generic,systemd,systemd-sysv,udev,dbus,systemd-boot --qemu-firmware=uefi qemu ``` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2058381 Title: Compression of ARM64 kernels causes problems with secureboot and systemd-boot Status in linux-meta package in Ubuntu: New Bug description: Hello, I'm trying to deploy an Ubuntu Server on arm64 with securbeoot and UKIs. I'm running into the problem that the shipped kernel is just a plain gzip compressed version of the kernel image. This causes two issues: - sbsign refuses to sign the kernel without uncompressing it first (Invalid DOS header magic) - systemd-stub/systemd-boot don't recognize this kernel as a valid binary (Bad kernel image: Load error\n Failed to execute Ubuntu Noble Numbat (development branch) (\EFI\Linux\ubuntu-6.8.0-11-generic.efi): Load error) Debian just ships an uncompressed kernel and Fedora ships a PE binary (which they can do because they dropped BIOS support, so this cannot be adopted for Ubuntu). Shipping an uncompressed kernel would be the easiest switch from my view, only causing problems on small /boot partitions or ESP partitions, respectively. The current version in Ubuntu causes unexpected behaviour with various bootchain tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2058381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
Daniel, please review and comment https://code.launchpad.net/~bdrung/ubuntu/+source/initramfs- tools/+git/initramfs-tools/+merge/462691 (see the description for the two possible implementations) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049569] Re: Enable the mic-mute led on Dell MTL laptops
Sorry for the mistake. The sof-hda-generic-2ch.tplg is replaced for non-
MTL platform which would cause regression.
new MR for jammy proposed to restore the sof-tplg/sof-hda-generic-2ch.tplg and
replace the same file in sof-ace-tplg for MTL
https://code.launchpad.net/~mschiu77/ubuntu/+source/firmware-sof/+git/firmware-sof/+merge/462688
The `md5sum` of the files down below should match the upstream sof-bin-2023.12.1
$ md5sum lib/firmware/intel/sof-ace-tplg/sof-hda-generic-2ch.tplg
4f97f6f77ebeb5e8ed78923c36bc897e
lib/firmware/intel/sof-ace-tplg/sof-hda-generic-2ch.tplg
$ md5sum lib/firmware/intel/sof-ipc4/mtl/sof-mtl.ri
fe5ef04483649481146baf87059555f9 lib/firmware/intel/sof-ipc4/mtl/sof-mtl.ri
$ md5sum lib/firmware/intel/sof-ipc4/mtl/community/sof-mtl.ri
438869b48941968ab0b9c46877e9d1fa
lib/firmware/intel/sof-ipc4/mtl/community/sof-mtl.ri
$ md5sum lib/firmware/intel/sof-ipc4/mtl/intel-signed/sof-mtl.ri
fe5ef04483649481146baf87059555f9
lib/firmware/intel/sof-ipc4/mtl/intel-signed/sof-mtl.ri
PPA for jammy uploaded to
https://launchpad.net/~mschiu77/+archive/ubuntu/ppa-2049569-4.7
@Leo Lin, please verify with the new PPA. Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049569
Title:
Enable the mic-mute led on Dell MTL laptops
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Committed
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in firmware-sof source package in Noble:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justifications]
== kernels ==
[Impact]
On Dell's Precision 3550, Intel MTL platform, the MIC-Mute function is
working but the LED(on F4) state is not changed accordingly.
[Fix]
There's no problem on the same series on RPL platform. It needs MTL specific
SoF driver and controls to support the registered mixer switch. It requires the
patches in
https://lore.kernel.org/all/20230919103115.30783-1-peter.ujfal...@linux.intel.com/
and
https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/
[Test Case]
1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD
icon.
2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled.
[Where problems could occur]
It's only required for new sof-audio-pci-intel-mtl driver. The impact should
be restricting.
== firmware-sof ==
[Impact]
The mic-mute led not working on Intel MTL powered laptops.
[Fix]
For firmware-sof, it required the upstream commit fdc884baa4b3 ("Add
sof-ipc4-v2.8.1/mtl/, intel-signed + community") and the
sof-hda-generic-2ch.tplg from v2.8.1 to make sure the ipc4 topology and control
matches with the updated driver.
[Test Case]
1. enable -proposed pocket and install firmware-sof-signed
2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD
icon.
[Where problems could occur]
The updated sof-mtl.ri and the sof-hda-generic-2ch.tplg are shared by all
Intel MTL platforms. Need to verify audio function on MTL enpowered machines.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2049569/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
** Merge proposal linked: https://code.launchpad.net/~bdrung/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462690 ** Merge proposal linked: https://code.launchpad.net/~bdrung/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462691 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056475] Re: aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation
** Changed in: linux-aws (Ubuntu Focal) Assignee: (unassigned) => Philip Cox (philcox) ** Changed in: linux-aws (Ubuntu Jammy) Assignee: (unassigned) => Philip Cox (philcox) ** Changed in: linux-aws (Ubuntu Mantic) Assignee: (unassigned) => Philip Cox (philcox) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2056475 Title: aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation Status in linux-aws package in Ubuntu: Fix Committed Status in linux-aws source package in Focal: Fix Committed Status in linux-aws source package in Jammy: Fix Committed Status in linux-aws source package in Mantic: Fix Committed Status in linux-aws source package in Noble: Fix Committed Bug description: SRU Justification: [Impact] In Ubuntu AMIs for x86 and Graviton based EC2 instances, the standard Ubuntu AMI comes without IRQ moderation enabled for ENA, which for our latest generation instances with networking heavy workloads is up to a 25% performance regression (i.e. NGINX in a load-balancing configuration). [Fix] The mainline Linux kernel will now support IRQ moderation by default for ENA in the 6.9 kernel release via this patch: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/amazon/ena?id=50d7a2660579889fba28b7e4543d4ce85aa2311b [Test Plan] AWS tested [Where problems could occur] By enabling adaptive coalescing, the default interrupt behaviour will by changed to be more adaptive, which shows improvements on heavy network workloads, but my change the behaviour and performance on other network workloads differently. Rather than handling the interrupts based off of a fixed amount of time elapsed, it will change to an adaptive based approach. There should be no negative impact on light workloads, and a positive impact on heavy work loads. If there is an impact though, this option can be disabled via the ethtool command. [Other Info] SF: 00380449 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2056475/+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 2058191] Re: Getting SIGSEGV and SIGILL in many programs
I can try as many kernels as you want. Just give me some time to get back home. 23.10 was working alright, but I don't remember which kernel I was using in this version. -- 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/2058191 Title: Getting SIGSEGV and SIGILL in many programs Status in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Okay, recently I upgraded to 24.04. I'm getting some SIGSEGV and SIGILLs from time to time. Sometimes the entire computer freezes and i can't even turn down unless i hold the power button for 5 secs. I tought it could be the kernel version, so I upgraded from Ubuntu's 6.8.0-11.11+1 to mainline 6.8.1. However, it didn't fix. Here are some softwares i got SIGSEGV or SIGILLs: - code-insiders (vscode) - brave (Brave browser) - bun (node.js alternative) - node.js I know i should upload more logs, but I didn't find the errors in syslog or journalctl. $ lsb_release -rd - No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058047] Re: Versions 5.15.0-100 and 6.5.0-25 of the kernel hang upon accessing the Intel Ethernet controller (4) I219-LM [8086:15d7] (rev 21)
The issue is still present on kernels 6.5.0-26 et 5.15.0-101 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058047 Title: Versions 5.15.0-100 and 6.5.0-25 of the kernel hang upon accessing the Intel Ethernet controller (4) I219-LM [8086:15d7] (rev 21) Status in linux package in Ubuntu: New Bug description: The system hangs with Linux 5.15.0-100 and 6.5.0-25 upon accessing this Ethernet controller: $ lspci -nn ... 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (4) I219-LM [8086:15d7] (rev 21) Commands that deal with the network hang forever, e.g. "ip link". The machine must be hard-rebooted (magic sysrq) because systemd also hangs during reboot. Previous versions work perfectly fine (5.15.0-97 and 6.5.0-21). The issue is specific to the integrated network controller, because it goes away when the Ethernet controller is disabled in the BIOS. Attached is an extract of the kernel logs under the problematic kernel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-100-generic 5.15.0-100.110 ProcVersionSignature: Ubuntu 5.15.0-97.107-generic 5.15.136 Uname: Linux 5.15.0-97-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-97-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yl243478 3612 F pulseaudio CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckMismatches: ./boot.catalog CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Mar 15 16:48:19 2024 InstallationDate: Installed on 2022-11-10 (491 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0c45:6717 Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-97-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ipv6.disable=1 quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-97-generic N/A linux-backports-modules-5.15.0-97-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2023 dmi.bios.release: 1.36 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.36.0 dmi.board.name: 0YM3X5 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.36.0:bd12/13/2023:br1.36:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0YM3X5:rvrA01:cvnDellInc.:ct10:cvr:sku081C: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058047/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980831] Re: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!
It seems that I found a way to work around the issue without regularly rebooting my pc I was looking at the accessibility settings and found an option to disable animations on Gnome, after disabling the animations this issue disappeared for me. -- 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/1980831 Title: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: When working normally, random freezes happen. Everything freezes, except the mouse cursor. I tried from keyboard to: switch to another window, start a terminal, run a command to restart gnome, enabled ctrl+alt+backspace and tried it to restart X windows, ctrl+alt+delete, switch to another session with ctrl+alt+F1-F9 - nothing works. If I'm listening to something, the sound goes on for a while; sometimes it stops by itself, other times it keeps going. The only way to recover that I've found is to stop the laptop from the power button. For a while I thought it was due to firefox; I installed the deb version and then switched to chrome - same behavior. It didn't happen when I was playing Hollow Knight in Steam, or when I've used the terminal and nothing else. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 6 14:27:36 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-06-16 (19 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1980831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056418] Re: Fix headphone mic detection issue on ALC897
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2056418 Title: Fix headphone mic detection issue on ALC897 Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Headphone mic is lost after resume from S3 or reboot with plugin. [Fix] Restore the headphone mic detect logic for ALC897 after lost power. [Test] Tested on hardware, the headphone mic appears as plugin after boot or resume from S3, and works fine. [Where problems could occur] It may break ALC897 sound input. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2056418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053277] Re: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy
SRU: * https://kernel.ubuntu.com/gitea/kernel/linux-firmware/pulls/20 (jammy) * https://kernel.ubuntu.com/gitea/kernel/linux-firmware/pulls/21 (mantic) ** Description changed: + [SRU Justification] + + [Impact] + + Devices hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) + during warm boot stress test. + + [Fix] + + AMD GPU dcn firmware upgrade to upstream commit bd2ad5e6 needed. The + affected blob is amdgpu/dcn_3_2_0_dmcub.bin, which has stayed the first + revision since Jammy is ever released. However, the related commits from + the upgrade path have also included blob updates to all kinds of + different, unrelated hardware models. + + This pull request bumps only the affected binary to the target commit + per online discussion with AMD. + + [Test Case] + + Perform checkbox warmboot stress test: + + $ checkbox-cli run com.canonical.certification::stress/reboot + + [Where problems could occur] + + While DCN blob maybe shared with several hardware models, with + confirmation from IHV, there should be little risk to upgrade it. + + [Other Info] + + Affects both Jammy and Mantic. + + == original bug report == + Dell reported sporadically hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. After updating DMCUB firmware version to 0x07002600, they observed a significant improvement in passing rate. And Dell wants to add the updated DMCUB firmware (ver 0x7002600) to its OEM image. - - DMCUB firmware (ver 0x7002600) is at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20. + DMCUB firmware (ver 0x7002600) is at + https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- + firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20. ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Mantic) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu Mantic) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2053277 Title: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Mantic: In Progress Bug description: [SRU Justification] [Impact] Devices hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. [Fix] AMD GPU dcn firmware upgrade to upstream commit bd2ad5e6 needed. The affected blob is amdgpu/dcn_3_2_0_dmcub.bin, which has stayed the first revision since Jammy is ever released. However, the related commits from the upgrade path have also included blob updates to all kinds of different, unrelated hardware models. This pull request bumps only the affected binary to the target commit per online discussion with AMD. [Test Case] Perform checkbox warmboot stress test: $ checkbox-cli run com.canonical.certification::stress/reboot [Where problems could occur] While DCN blob maybe shared with several hardware models, with confirmation from IHV, there should be little risk to upgrade it. [Other Info] Affects both Jammy and Mantic. == original bug report == Dell reported sporadically hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. After updating DMCUB firmware version to 0x07002600, they observed a significant improvement in passing rate. And Dell wants to add the updated DMCUB firmware (ver 0x7002600) to its OEM image. DMCUB firmware (ver 0x7002600) is at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2053277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054773] Re: Fix AMD brightness issue on AUO panel
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2054773 Title: Fix AMD brightness issue on AUO panel Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] When change brightness quickly on gnome menu, AUO panel will be stuck in previous brightness. [Fix] The TCON is random hung by PSR-SU. Force enable ffu mode on PSR-SU panel. [Test] Tested on hardware, the brightness is changed as expected. [Where problems could occur] It may break AMD display. The commit is already in v6.8-rc5, the platform is not fully supported in Jammy 5.15, So SRU oem-6.5 and mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054773/+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 2055805] Re: touchpad not working with kernel 6.8
I don't have the hardware at the moment. It'd be great if you could do a test with the latest mainline build, so that we can better understand if it's an upstream issue or something specific with the Ubuntu kernel (or maybe a kernel .config issue): https://kernel.ubuntu.com/mainline/v6.8.1/ Thanks! -- 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/2055805 Title: touchpad not working with kernel 6.8 Status in linux package in Ubuntu: Confirmed Bug description: After the standard update procedure and installation of a new version of the kernel, the touchpad on the MacBook Pro 13 - 2014 stopped working. Even the mouse cursor does not appear on the screen. If you select the old kernel version 6.6 in the bootloader options, then everything works correctly Ubuntu 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Mar 3 11:11:43 2024 InstallationDate: Installed on 2023-11-06 (118 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.6.0-14-generic root=UUID=2075733d-58de-4836-9c71-04dd00378200 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.6.0-14-generic N/A linux-backports-modules-6.6.0-14-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 430.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr430.0.0.0.0:bd12/17/2020:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+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 2058357] Re: noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 2058221 packages: generate: linux-generate-oem-6.8 lrg: linux-restricted-generate-oem-6.8 lrm: linux-restricted-modules-oem-6.8 lrs: linux-restricted-signatures-oem-6.8 main: supported meta: linux-meta-oem-6.8 signed: linux-signed-oem-6.8 phase: Holding before Packaging phase-changed: Tuesday, 19. March 2024 09:51 UTC reason: :prepare-packages: Holding -b Not ready to be cranked prepare-package: Holding -- waiting for parent tracker variant: debs ~~: + clamps: + self: 6.8.0-1001.1 tracker: last-message: '2024-03-19 09:46:02.148495+00:00' -- 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/2058357 Title: noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow abi-testing series: New Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow boot-testing series: New Status in Kernel SRU Workflow new-review series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-generate series: New Status in Kernel SRU Workflow prepare-package-lrg series: New Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-lrs series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow sru-review series: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 2058221 packages: generate: linux-generate-oem-6.8 lrg: linux-restricted-generate-oem-6.8 lrm: linux-restricted-modules-oem-6.8 lrs: linux-restricted-signatures-oem-6.8 main: supported meta: linux-meta-oem-6.8 signed: linux-signed-oem-6.8 phase: Holding before Packaging phase-changed: Tuesday, 19. March 2024 09:51 UTC reason: :prepare-packages: Holding -b Not ready to be cranked prepare-package: Holding -- waiting for parent tracker variant: debs ~~: clamps: self: 6.8.0-1001.1 tracker: last-message: '2024-03-19 09:46:02.148495+00:00' To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/2058357/+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 2058357] Re: noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker
** Summary changed: - noble/linux-oem-6.8: -proposed tracker + noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker -- 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/2058357 Title: noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow abi-testing series: New Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow boot-testing series: New Status in Kernel SRU Workflow new-review series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-generate series: New Status in Kernel SRU Workflow prepare-package-lrg series: New Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-lrs series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow sru-review series: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 2058221 packages: generate: linux-generate-oem-6.8 lrg: linux-restricted-generate-oem-6.8 lrm: linux-restricted-modules-oem-6.8 lrs: linux-restricted-signatures-oem-6.8 main: supported meta: linux-meta-oem-6.8 signed: linux-signed-oem-6.8 phase: Holding before Packaging phase-changed: Tuesday, 19. March 2024 09:51 UTC reason: :prepare-packages: Holding -b Not ready to be cranked prepare-package: Holding -- waiting for parent tracker variant: debs ~~: clamps: self: 6.8.0-1001.1 tracker: last-message: '2024-03-19 09:46:02.148495+00:00' To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/2058357/+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 2058357] Re: noble/linux-oem-6.8: -proposed tracker
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058357 Title: noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow abi-testing series: New Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow boot-testing series: New Status in Kernel SRU Workflow new-review series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-generate series: New Status in Kernel SRU Workflow prepare-package-lrg series: New Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-lrs series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow sru-review series: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 2058221 packages: generate: linux-generate-oem-6.8 lrg: linux-restricted-generate-oem-6.8 lrm: linux-restricted-modules-oem-6.8 lrs: linux-restricted-signatures-oem-6.8 main: supported meta: linux-meta-oem-6.8 signed: linux-signed-oem-6.8 phase: Holding before Packaging phase-changed: Tuesday, 19. March 2024 09:51 UTC reason: :prepare-packages: Holding -b Not ready to be cranked prepare-package: Holding -- waiting for parent tracker variant: debs ~~: tracker: last-message: '2024-03-19 09:46:02.148495+00:00' To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/2058357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053277] Re: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy
** Changed in: linux-firmware (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2053277 Title: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: New Status in linux-firmware source package in Mantic: New Bug description: Dell reported sporadically hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. After updating DMCUB firmware version to 0x07002600, they observed a significant improvement in passing rate. And Dell wants to add the updated DMCUB firmware (ver 0x7002600) to its OEM image. DMCUB firmware (ver 0x7002600) is at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2053277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp/5.4.0.1126.128)
All autopkgtests for the newly accepted linux-meta-gcp (5.4.0.1126.128) for focal have finished running. The following regressions have been reported in tests triggered by the package: r8168/8.048.00-1ubuntu0.20.04.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-gcp [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058191] Re: Getting SIGSEGV and SIGILL in many programs
The message `mce: [Hardware Error]: Machine check events logged` really seems to indicate a potential hardware malfunction. Can you double check if this is happening only with the latest 6.8? Do you see anything similar in dmesg with other kernels? -- 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/2058191 Title: Getting SIGSEGV and SIGILL in many programs Status in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Okay, recently I upgraded to 24.04. I'm getting some SIGSEGV and SIGILLs from time to time. Sometimes the entire computer freezes and i can't even turn down unless i hold the power button for 5 secs. I tought it could be the kernel version, so I upgraded from Ubuntu's 6.8.0-11.11+1 to mainline 6.8.1. However, it didn't fix. Here are some softwares i got SIGSEGV or SIGILLs: - code-insiders (vscode) - brave (Brave browser) - bun (node.js alternative) - node.js I know i should upload more logs, but I didn't find the errors in syslog or journalctl. $ lsb_release -rd - No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+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 2058165] Re: System freeze on copy large files on usb
Can you elaborate more on the freeze part? Does the system completely freezes and it never recovers or is it a temporary freeze (until the copy completes)? How much RAM do you have in your system? Can you check if the following helps to mitigate the problem? $ echo $((32 * 1024 * 1024)) | sudo tee /proc/sys/vm/dirty_bytes $ echo $((16 * 1024 * 1024)) | sudo tee /proc/sys/vm/dirty_background_bytes Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2058165 Title: System freeze on copy large files on usb Status in linux-meta-lowlatency package in Ubuntu: New Bug description: Everytime i create/copy/move a large file >15GB on a usb the system freezes ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-lowlatency 6.8.0-7.7.1 ProcVersionSignature: Ubuntu 6.8.0-7.7.1-lowlatency 6.8.0-rc3 Uname: Linux 6.8.0-7-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Mar 17 18:55:31 2024 InstallationDate: Installed on 2024-03-10 (7 days ago) InstallationMedia: Ubuntu-Studio 24.04 LTS "Noble Numbat" - Daily amd64 (20240308) SourcePackage: linux-meta-lowlatency UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lowlatency/+bug/2058165/+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 2057792] Re: Certains jeux crashent liés à un vm_max_map_count trop faible
** Changed in: ubuntu Status: Fix Released => Confirmed ** Summary changed: - Certains jeux crashent liés à un vm_max_map_count trop faible + Some Games are crashing linked to a vm_max_map_count too low -- 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/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello there, I submit this request to improve the gaming experience in ubuntu for all users. Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just not starting because the vm_max_map_count is locked at 65530. If we change this value to a value > 20, all games are working well and there is no bug linked to maps. Some others distribution like Fedora or Pop OS, have already made the change few month before. It's time to Ubuntu to makes the change also. Thanks in advance for applying this request. How to make this change : One file to modify : /etc/sysctl.conf Add this line : vm.max_map_count=2147483642 Save Reboot and enjoy Best Regards Vinceff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2057792/+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 2058334] Re: package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to install/upgrade: installed linux-headers-6.5.0-26-generic package post-installation script subprocess r
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your log files attached to this bug report it
seems that a package failed to install due to a segmentation fault in
the application being used for the package installation process.
Unfortunately, this bug report isn't very useful in its current state
and a crash report would be much more useful. Could you try recreating
this issue by enabling apport to catch the crash report 'sudo service
apport start force_start=1' and then trying to install the same package
again? This process will create a new bug report so I am marking this
one as Invalid. Thanks again for helping out!
[This is an automated message. I apologize if it reached you
inappropriately; please just reply to this message indicating so.]
** Tags added: package-install-segfault
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2058334
Title:
package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to
install/upgrade: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
Invalid
Bug description:
I got the error after login to the gnome
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-26-generic 6.5.0-26.26
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Mar 18 17:33:44 2024
ErrorMessage: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2021-12-26 (813 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-26-generic
root=UUID=336f83fe-a568-4a38-b14f-1d0964399570 ro rd.driver.blacklist=nouveau
modprobe.blacklist=nouveau nvidia-drm.modset=1 migrations=off mitigations=off
quiet splash rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
nvidia-drm.modset=1 migrations=off mitigations=off vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: /usr/bin/python3.11, Python 3.11.6, python-is-python3, 3.11.4-1
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
RfKill:
SourcePackage: linux
Title: package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to
install/upgrade: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to mantic on 2023-10-14 (157 days ago)
dmi.bios.date: 09/12/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F27
dmi.board.asset.tag: Default string
dmi.board.name: Z690 GAMING X DDR4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF27:bd09/12/2023:br5.27:svnGigabyteTechnologyCo.,Ltd.:pnZ690GAMINGXDDR4:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ690GAMINGXDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Z690 MB
dmi.product.name: Z690 GAMING X DDR4
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058334/+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 2057808] Re: [LTS] cryptsetup-initramfs fails when kernel modules are compressed
** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Won't Fix ** Changed in: linux (Ubuntu Jammy) Importance: Critical => 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/2057808 Title: [LTS] cryptsetup-initramfs fails when kernel modules are compressed Status in cryptsetup package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in cryptsetup source package in Jammy: New Status in linux source package in Jammy: Won't Fix Bug description: This is the same cause as the Mantic bug "cryptsetup autopkgtest fails with zstd compressed kernel modules" https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2035120 where hooks/cryptroot::add_modules() needs postfix wildcards after $glob.ko on 2 lines. It affects 22.04 LTS with recent kernel or local kernel built with CONFIG_MODULE_COMPRESS_* I think the fix needs cherry-picking into LTS release(s). https://salsa.debian.org/cryptsetup- team/cryptsetup/-/commit/8359ad85a541b76f388cdc28f549229e3d71e750 At boot-time it results in the cryptic (pun intended) messages: device-mapper: table: 253:0 crypt: Error allocating crypto tfm (-ENOENT) device-mapper: ioctl: error adding target to table device-mapper: reload ioctl on luks_os (253:0) failed: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2057808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049569] Re: Enable the mic-mute led on Dell MTL laptops
The firmware-sof-signed in -proposed doesn't seem to fix the LEDs at
least on one HP platform. Reading the file from /sys/class/sound/ctl-
led/mic/card0/list shows nothing.
The md5sum of sof-ace-tplg/sof-hda-generic-2ch.tplg also doesn't match
the one in upstream v2023.12.1 release.
# From upstream release
$ md5sum sof-bin-2023.12.1/sof-ace-tplg/sof-hda-generic-2ch.tplg
4f97f6f77ebeb5e8ed78923c36bc897e
sof-bin-2023.12.1/sof-ace-tplg/sof-hda-generic-2ch.tplg
# From 2.0-1ubuntu4.6
$ md5sum sof-ace-tplg/sof-hda-generic-2ch.tplg
100186829692a835c518a34a576569c3 sof-ace-tplg/sof-hda-generic-2ch.tplg
** Tags removed: verification-needed-jammy
** Tags added: verification-failed-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049569
Title:
Enable the mic-mute led on Dell MTL laptops
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Committed
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in firmware-sof source package in Noble:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justifications]
== kernels ==
[Impact]
On Dell's Precision 3550, Intel MTL platform, the MIC-Mute function is
working but the LED(on F4) state is not changed accordingly.
[Fix]
There's no problem on the same series on RPL platform. It needs MTL specific
SoF driver and controls to support the registered mixer switch. It requires the
patches in
https://lore.kernel.org/all/20230919103115.30783-1-peter.ujfal...@linux.intel.com/
and
https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/
[Test Case]
1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD
icon.
2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled.
[Where problems could occur]
It's only required for new sof-audio-pci-intel-mtl driver. The impact should
be restricting.
== firmware-sof ==
[Impact]
The mic-mute led not working on Intel MTL powered laptops.
[Fix]
For firmware-sof, it required the upstream commit fdc884baa4b3 ("Add
sof-ipc4-v2.8.1/mtl/, intel-signed + community") and the
sof-hda-generic-2ch.tplg from v2.8.1 to make sure the ipc4 topology and control
matches with the updated driver.
[Test Case]
1. enable -proposed pocket and install firmware-sof-signed
2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD
icon.
[Where problems could occur]
The updated sof-mtl.ri and the sof-hda-generic-2ch.tplg are shared by all
Intel MTL platforms. Need to verify audio function on MTL enpowered machines.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2049569/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057783] Re: hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2057783 Title: hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version device is not recognized when using 6.8 kernel version /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/expensive /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/guid /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/instance_count /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/modalias /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/object_id /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/driver: 97845ED0-4E6D-11DE-8A39-0800200C9A66 bind module uevent unbind /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/gpio-aaeon.0: driver driver_override gpio gpiochip1 modalias power subsystem uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/hwmon-aaeon.0: driver_override modalias power subsystem uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/leds-aaeon.0: driver driver_override leds modalias power subsystem uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/power: async autosuspend_delay_ms control runtime_active_kids runtime_active_time runtime_enabled runtime_status runtime_suspended_time runtime_usage /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/subsystem: devices drivers drivers_autoprobe drivers_probe uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/wdt-aaeon.0: driver_override modalias power subsystem uevent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057783/+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 2058334] Re: package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to install/upgrade: installed linux-headers-6.5.0-26-generic package post-installation script subprocess r
** Tags removed: need-duplicate-check
--
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/2058334
Title:
package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to
install/upgrade: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
New
Bug description:
I got the error after login to the gnome
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-26-generic 6.5.0-26.26
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Mar 18 17:33:44 2024
ErrorMessage: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2021-12-26 (813 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-26-generic
root=UUID=336f83fe-a568-4a38-b14f-1d0964399570 ro rd.driver.blacklist=nouveau
modprobe.blacklist=nouveau nvidia-drm.modset=1 migrations=off mitigations=off
quiet splash rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
nvidia-drm.modset=1 migrations=off mitigations=off vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: /usr/bin/python3.11, Python 3.11.6, python-is-python3, 3.11.4-1
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
RfKill:
SourcePackage: linux
Title: package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to
install/upgrade: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to mantic on 2023-10-14 (157 days ago)
dmi.bios.date: 09/12/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F27
dmi.board.asset.tag: Default string
dmi.board.name: Z690 GAMING X DDR4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF27:bd09/12/2023:br5.27:svnGigabyteTechnologyCo.,Ltd.:pnZ690GAMINGXDDR4:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ690GAMINGXDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Z690 MB
dmi.product.name: Z690 GAMING X DDR4
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058334/+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 2058334] [NEW] package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to install/upgrade: installed linux-headers-6.5.0-26-generic package post-installation script subprocess
Public bug reported:
I got the error after login to the gnome
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-26-generic 6.5.0-26.26
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Mar 18 17:33:44 2024
ErrorMessage: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2021-12-26 (813 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-26-generic
root=UUID=336f83fe-a568-4a38-b14f-1d0964399570 ro rd.driver.blacklist=nouveau
modprobe.blacklist=nouveau nvidia-drm.modset=1 migrations=off mitigations=off
quiet splash rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
nvidia-drm.modset=1 migrations=off mitigations=off vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: /usr/bin/python3.11, Python 3.11.6, python-is-python3, 3.11.4-1
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
RfKill:
SourcePackage: linux
Title: package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to
install/upgrade: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to mantic on 2023-10-14 (157 days ago)
dmi.bios.date: 09/12/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F27
dmi.board.asset.tag: Default string
dmi.board.name: Z690 GAMING X DDR4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF27:bd09/12/2023:br5.27:svnGigabyteTechnologyCo.,Ltd.:pnZ690GAMINGXDDR4:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ690GAMINGXDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Z690 MB
dmi.product.name: Z690 GAMING X DDR4
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package mantic
--
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/2058334
Title:
package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to
install/upgrade: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
New
Bug description:
I got the error after login to the gnome
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-26-generic 6.5.0-26.26
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Mar 18 17:33:44 2024
ErrorMessage: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2021-12-26 (813 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-26-generic
root=UUID=336f83fe-a568-4a38-b14f-1d0964399570 ro rd.driver.blacklist=nouveau
modprobe.blacklist=nouveau nvidia-drm.modset=1 migrations=off mitigations=off
quiet splash rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
nvidia-drm.modset=1 migrations=off mitigations=off vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: /usr/bin/python3.11, Python 3.11.6, python-is-python3, 3.11.4-1
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
RfKill:
SourcePackage: linux
Title: package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to
install/upgrade: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to mantic on 2023-10-14 (157 days ago)
dmi.bios.date: 09/12/2023
dmi.bios.release: 5.27
dmi.bios.vendor:
[Kernel-packages] [Bug 2058226] Re: iwlwifi repeatedly logging microcode crashes
** Tags added: kern-9972 -- 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/2058226 Title: iwlwifi repeatedly logging microcode crashes Status in linux-firmware package in Ubuntu: New Bug description: The iwlwifi driver is logging microcode crashes on a daily basis. The chip is Intel 9462 (AX201). Ubuntu release 22.04 LTS, faithfully kept up to date. Crash log is different from what I've found by googling, and for similar errors the firmware version is much more recent. Here's the log output from crash (leaving some extra lines there as well to show the chip and firmware version): Mar 15 12:03:14 waplinuc kernel: [1203239.253200] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. Mar 15 12:03:14 waplinuc kernel: [1203239.253293] iwlwifi :00:14.3: Start IWL Error Log Dump: Mar 15 12:03:14 waplinuc kernel: [1203239.253295] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 Mar 15 12:03:14 waplinuc kernel: [1203239.253298] iwlwifi :00:14.3: Loaded firmware version: 77.206b0184.0 QuZ-a0-jf-b0-77.ucode Mar 15 12:03:14 waplinuc kernel: [1203239.253300] iwlwifi :00:14.3: 0x003F | ADVANCED_SYSASSERT Mar 15 12:03:14 waplinuc kernel: [1203239.253303] iwlwifi :00:14.3: 0x00A022F0 | trm_hw_status0 Mar 15 12:03:14 waplinuc kernel: [1203239.253305] iwlwifi :00:14.3: 0x | trm_hw_status1 Mar 15 12:03:14 waplinuc kernel: [1203239.253307] iwlwifi :00:14.3: 0x004C03F2 | branchlink2 Mar 15 12:03:14 waplinuc kernel: [1203239.253308] iwlwifi :00:14.3: 0x1820 | interruptlink1 Mar 15 12:03:14 waplinuc kernel: [1203239.253310] iwlwifi :00:14.3: 0x0001C346 | interruptlink2 Mar 15 12:03:14 waplinuc kernel: [1203239.253312] iwlwifi :00:14.3: 0x000601FF | data1 Mar 15 12:03:14 waplinuc kernel: [1203239.253313] iwlwifi :00:14.3: 0x00812C80 | data2 Mar 15 12:03:14 waplinuc kernel: [1203239.253315] iwlwifi :00:14.3: 0x0001C346 | data3 Mar 15 12:03:14 waplinuc kernel: [1203239.253316] iwlwifi :00:14.3: 0xB743 | beacon time Mar 15 12:03:14 waplinuc kernel: [1203239.253318] iwlwifi :00:14.3: 0x9AB048FC | tsf low Mar 15 12:03:14 waplinuc kernel: [1203239.253320] iwlwifi :00:14.3: 0x038D | tsf hi Mar 15 12:03:14 waplinuc kernel: [1203239.253321] iwlwifi :00:14.3: 0x | time gp1 Mar 15 12:03:14 waplinuc kernel: [1203239.253323] iwlwifi :00:14.3: 0xFF3E816F | time gp2 Mar 15 12:03:14 waplinuc kernel: [1203239.253324] iwlwifi :00:14.3: 0x0001 | uCode revision type Mar 15 12:03:14 waplinuc kernel: [1203239.253326] iwlwifi :00:14.3: 0x004D | uCode version major Mar 15 12:03:14 waplinuc kernel: [1203239.253327] iwlwifi :00:14.3: 0x206B0184 | uCode version minor Mar 15 12:03:14 waplinuc kernel: [1203239.253329] iwlwifi :00:14.3: 0x0351 | hw version Mar 15 12:03:14 waplinuc kernel: [1203239.253330] iwlwifi :00:14.3: 0x00489001 | board version Mar 15 12:03:14 waplinuc kernel: [1203239.253332] iwlwifi :00:14.3: 0x80D2FD25 | hcmd Mar 15 12:03:14 waplinuc kernel: [1203239.25] iwlwifi :00:14.3: 0x00021000 | isr0 Mar 15 12:03:14 waplinuc kernel: [1203239.253335] iwlwifi :00:14.3: 0x0004 | isr1 Mar 15 12:03:14 waplinuc kernel: [1203239.253336] iwlwifi :00:14.3: 0x08F2 | isr2 Mar 15 12:03:14 waplinuc kernel: [1203239.253337] iwlwifi :00:14.3: 0x04C3428D | isr3 Mar 15 12:03:14 waplinuc kernel: [1203239.253339] iwlwifi :00:14.3: 0x | isr4 Mar 15 12:03:14 waplinuc kernel: [1203239.253340] iwlwifi :00:14.3: 0x0502001C | last cmd Id Mar 15 12:03:14 waplinuc kernel: [1203239.253342] iwlwifi :00:14.3: 0x0001191E | wait_event Mar 15 12:03:14 waplinuc kernel: [1203239.253343] iwlwifi :00:14.3: 0x00D4 | l2p_control Mar 15 12:03:14 waplinuc kernel: [1203239.253345] iwlwifi :00:14.3: 0x0020 | l2p_duration Mar 15 12:03:14 waplinuc kernel: [1203239.253346] iwlwifi :00:14.3: 0x0007 | l2p_mhvalid Mar 15 12:03:14 waplinuc kernel: [1203239.253348] iwlwifi :00:14.3: 0x0081 | l2p_addr_match Mar 15 12:03:14 waplinuc kernel: [1203239.253349] iwlwifi :00:14.3: 0x0009 | lmpm_pmg_sel Mar 15 12:03:14 waplinuc kernel: [1203239.253351] iwlwifi :00:14.3: 0x | timestamp Mar 15 12:03:14 waplinuc kernel: [1203239.253352] iwlwifi :00:14.3: 0x5030 | flow_handler Mar 15 12:03:14 waplinuc kernel: [1203239.253394] iwlwifi :00:14.3: Start IWL Error Log Dump: Mar 15 12:03:14 waplinuc kernel: [1203239.253395] iwlwifi :00:14.3: Transport status: 0x004A, valid: 7 Mar 15 12:03:14 waplinuc kernel: [1203239.253397] iwlwifi :00:14.3: 0x2070 | NMI_INTERRUPT_LMAC_FATAL Mar 15 12:03:14 waplinuc kernel: [1203239.253399] iwlwifi :00:14.3: 0x |
[Kernel-packages] [Bug 2058333] Re: daisy chained thunderbolt devices not working at reboot on AMD strix platforms
** Tags added: amd oem-priority originate-from-2058213 ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058333 Title: daisy chained thunderbolt devices not working at reboot on AMD strix platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: Boot firmware (typically BIOS) might have created tunnels of its own. The tunnel configuration that it does might be sub-optimal. For instance it may only support HBR2 monitors so the DisplayPort tunnels it created may limit Linux graphics drivers. In addition there is an issue on some AMD based systems where the BIOS does not allocate enough PCIe resources for future topology extension. By resetting the USB4 topology the PCIe links will be reset as well allowing Linux to re-allocate. This aligns the behavior with Windows Connection Manager. Fixes merged to linus tree for v6.9-rc1: * 59a54c5f3dbde thunderbolt: Reset topology created by the boot firmware * ec8162b3f0683 thunderbolt: Make tb_switch_reset() support Thunderbolt 2, 3 and USB4 routers * b35c1d7b11da8 thunderbolt: Introduce tb_path_deactivate_hop() * 01da6b99d49f6 thunderbolt: Introduce tb_port_reset() To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058333/+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 2058333] [NEW] daisy chained thunderbolt devices not working at reboot on AMD strix platforms
Public bug reported: Boot firmware (typically BIOS) might have created tunnels of its own. The tunnel configuration that it does might be sub-optimal. For instance it may only support HBR2 monitors so the DisplayPort tunnels it created may limit Linux graphics drivers. In addition there is an issue on some AMD based systems where the BIOS does not allocate enough PCIe resources for future topology extension. By resetting the USB4 topology the PCIe links will be reset as well allowing Linux to re-allocate. This aligns the behavior with Windows Connection Manager. Fixes merged to linus tree for v6.9-rc1: * 59a54c5f3dbde thunderbolt: Reset topology created by the boot firmware * ec8162b3f0683 thunderbolt: Make tb_switch_reset() support Thunderbolt 2, 3 and USB4 routers * b35c1d7b11da8 thunderbolt: Introduce tb_path_deactivate_hop() * 01da6b99d49f6 thunderbolt: Introduce tb_port_reset() ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd oem-priority originate-from-2058213 -- 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/2058333 Title: daisy chained thunderbolt devices not working at reboot on AMD strix platforms Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: Boot firmware (typically BIOS) might have created tunnels of its own. The tunnel configuration that it does might be sub-optimal. For instance it may only support HBR2 monitors so the DisplayPort tunnels it created may limit Linux graphics drivers. In addition there is an issue on some AMD based systems where the BIOS does not allocate enough PCIe resources for future topology extension. By resetting the USB4 topology the PCIe links will be reset as well allowing Linux to re-allocate. This aligns the behavior with Windows Connection Manager. Fixes merged to linus tree for v6.9-rc1: * 59a54c5f3dbde thunderbolt: Reset topology created by the boot firmware * ec8162b3f0683 thunderbolt: Make tb_switch_reset() support Thunderbolt 2, 3 and USB4 routers * b35c1d7b11da8 thunderbolt: Introduce tb_path_deactivate_hop() * 01da6b99d49f6 thunderbolt: Introduce tb_port_reset() To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058333/+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 2058331] [NEW] Update amd_sfh for AMD strix series
Public bug reported: Extend MP2 register region to enable family 1AH based family on the supported OEM platforms, needs to be backported into oem-6.8. [ 0.784296] pcie_mp2_amd: probe of :c4:00.7 failed with error -12 Following fixes applied to linus tree: * 90184f90c9ac5 HID: amd_sfh: Set the AMD SFH driver to depend on x86 * 6296562f30b1c HID: amd_sfh: Extend MP2 register access to SFH * 2105e8e00da46 HID: amd_sfh: Improve boot time when SFH is available * c1db0073212ef HID: amd_sfh: Avoid disabling the interrupt * bbf0dec306966 HID: amd_sfh: Update HPD sensor structure elements * 333861f4cca6d HID: amd_sfh: Increase sensor command timeout ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Tags: amd oem-priority originate-from-2058211 ** Tags added: amd oem-priority originate-from-2058211 ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058331 Title: Update amd_sfh for AMD strix series Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: Extend MP2 register region to enable family 1AH based family on the supported OEM platforms, needs to be backported into oem-6.8. [ 0.784296] pcie_mp2_amd: probe of :c4:00.7 failed with error -12 Following fixes applied to linus tree: * 90184f90c9ac5 HID: amd_sfh: Set the AMD SFH driver to depend on x86 * 6296562f30b1c HID: amd_sfh: Extend MP2 register access to SFH * 2105e8e00da46 HID: amd_sfh: Improve boot time when SFH is available * c1db0073212ef HID: amd_sfh: Avoid disabling the interrupt * bbf0dec306966 HID: amd_sfh: Update HPD sensor structure elements * 333861f4cca6d HID: amd_sfh: Increase sensor command timeout To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058331/+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 2058330] Re: Update amd-pmf for AMD strix series
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058330 Title: Update amd-pmf for AMD strix series Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: These updates will be enhanced amd-pmf for family 1AH on the supported OEM platforms, including enabling new revision for BIOS notify events, support static slider by APTS (AMD Performance and Thermal State)...etc. Needs to be backported into oem-6.8. Following are commits merged to linus tree for v6.9-rc1: * 8362e862fb879 platform/x86/amd/pmf: Update sps power thermals according to the platform-profiles * 3eecb434d7f21 platform/x86/amd/pmf: Add support to get sps default APTS index values * 48d38f569261b platform/x86/amd/pmf: Add support to get APTS index numbers for static slider * 6262938eef282 platform/x86/amd/pmf: Add support to notify sbios heart beat event * 5fdc8b82aab4c platform/x86/amd/pmf: Add support to get sbios requests in PMF driver * 233f78e11e1fa platform/x86/amd/pmf: Disable debugfs support for querying power thermals * a33e9e106601b platform/x86/amd/pmf: Differentiate PMF ACPI versions To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049922] Re: PCI ATS quirk patch needed for IDPF
This bug is awaiting verification that the linux-
gcp-5.4/5.4.0-1125.134~18.04.1 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-bionic-linux-
gcp-5.4' to 'verification-done-bionic-linux-gcp-5.4'. If the problem
still exists, change the tag 'verification-needed-bionic-linux-gcp-5.4'
to 'verification-failed-bionic-linux-gcp-5.4'.
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-bionic-linux-gcp-5.4-v2
verification-needed-bionic-linux-gcp-5.4
--
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/2049922
Title:
PCI ATS quirk patch needed for IDPF
Status in linux-gcp package in Ubuntu:
New
Status in linux-gcp-4.15 package in Ubuntu:
New
Status in linux-gcp source package in Bionic:
In Progress
Status in linux-gcp-4.15 source package in Bionic:
Fix Committed
Status in linux-gcp source package in Focal:
Fix Released
Bug description:
[Impact]
* Request from Google to include Intel patches for IDPF support if used from
out-of-tree module to prevent system instability.
[Fixes]
f18b1137d38c ("PCI: Extract ATS disabling to a helper function")
a18615b1cfc0 ("PCI: Disable ATS for specific Intel IPU E2000 devices")
[Test Case]
* Compile test
* Boot test
* Test on non-IDPF instance
* Tested by Google
[Where things could go wrong]
* Low chance of regression, changes very isolated
[Other Info]
* SF #00376470
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2049922/+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 2058330] [NEW] Update amd-pmf for AMD strix series
Public bug reported: These updates will be enhanced amd-pmf for family 1AH on the supported OEM platforms, including enabling new revision for BIOS notify events, support static slider by APTS (AMD Performance and Thermal State)...etc. Needs to be backported into oem-6.8. Following are commits merged to linus tree for v6.9-rc1: * 8362e862fb879 platform/x86/amd/pmf: Update sps power thermals according to the platform-profiles * 3eecb434d7f21 platform/x86/amd/pmf: Add support to get sps default APTS index values * 48d38f569261b platform/x86/amd/pmf: Add support to get APTS index numbers for static slider * 6262938eef282 platform/x86/amd/pmf: Add support to notify sbios heart beat event * 5fdc8b82aab4c platform/x86/amd/pmf: Add support to get sbios requests in PMF driver * 233f78e11e1fa platform/x86/amd/pmf: Disable debugfs support for querying power thermals * a33e9e106601b platform/x86/amd/pmf: Differentiate PMF ACPI versions ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd oem-priority originate-from-2058194 ** Tags added: amd oem-priority originate-from-2058194 -- 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/2058330 Title: Update amd-pmf for AMD strix series Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: These updates will be enhanced amd-pmf for family 1AH on the supported OEM platforms, including enabling new revision for BIOS notify events, support static slider by APTS (AMD Performance and Thermal State)...etc. Needs to be backported into oem-6.8. Following are commits merged to linus tree for v6.9-rc1: * 8362e862fb879 platform/x86/amd/pmf: Update sps power thermals according to the platform-profiles * 3eecb434d7f21 platform/x86/amd/pmf: Add support to get sps default APTS index values * 48d38f569261b platform/x86/amd/pmf: Add support to get APTS index numbers for static slider * 6262938eef282 platform/x86/amd/pmf: Add support to notify sbios heart beat event * 5fdc8b82aab4c platform/x86/amd/pmf: Add support to get sbios requests in PMF driver * 233f78e11e1fa platform/x86/amd/pmf: Disable debugfs support for querying power thermals * a33e9e106601b platform/x86/amd/pmf: Differentiate PMF ACPI versions To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049922] Re: PCI ATS quirk patch needed for IDPF
This bug was fixed in the package linux-gcp - 5.4.0-1125.134
---
linux-gcp (5.4.0-1125.134) focal; urgency=medium
* focal/linux-gcp: 5.4.0-1125.134 -proposed tracker (LP: #2055955)
* PCI ATS quirk patch needed for IDPF (LP: #2049922)
- PCI: Extract ATS disabling to a helper function
- PCI: Disable ATS for specific Intel IPU E2000 devices
[ Ubuntu: 5.4.0-174.193 ]
* focal/linux: 5.4.0-174.193 -proposed tracker (LP: #2055978)
* Packaging resync (LP: #1786013)
- [Packaging] update annotations scripts
- debian/dkms-versions -- update from kernel-versions (main/s2024.02.05)
* CVE-2024-24855
- scsi: lpfc: Fix a possible data race in lpfc_unregister_fcf_rescan()
* CVE-2024-1086
- netfilter: nf_tables: reject QUEUE/DROP verdict parameters
* CVE-2023-23004
- malidp: Fix NULL vs IS_ERR() checking
* CVE-2023-23000
- phy: tegra: xusb: Fix return value of tegra_xusb_find_port_node function
-- John Cabaj Mon, 11 Mar 2024 11:18:10
-0500
** Changed in: linux-gcp (Ubuntu Focal)
Status: In Progress => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-23000
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-23004
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-1086
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-24855
--
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/2049922
Title:
PCI ATS quirk patch needed for IDPF
Status in linux-gcp package in Ubuntu:
New
Status in linux-gcp-4.15 package in Ubuntu:
New
Status in linux-gcp source package in Bionic:
In Progress
Status in linux-gcp-4.15 source package in Bionic:
Fix Committed
Status in linux-gcp source package in Focal:
Fix Released
Bug description:
[Impact]
* Request from Google to include Intel patches for IDPF support if used from
out-of-tree module to prevent system instability.
[Fixes]
f18b1137d38c ("PCI: Extract ATS disabling to a helper function")
a18615b1cfc0 ("PCI: Disable ATS for specific Intel IPU E2000 devices")
[Test Case]
* Compile test
* Boot test
* Test on non-IDPF instance
* Tested by Google
[Where things could go wrong]
* Low chance of regression, changes very isolated
[Other Info]
* SF #00376470
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2049922/+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
