[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
If you are suggesting moving the logic from plymouth into initramfs- tools then please start by duplicating the code you'd like moved into initramfs-tools. That would be efficient since you have commit access to initramfs-tools, and would mean I only have to deal with plymouth here. -- 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 1970069] Re: Annoying boot messages interfering with splash screen
That change is in plymouth, but hooks/framebuffer is in initramfs-tools. If you're suggesting moving the code from plymouth into initramfs-tools then I kind of understand, but it's not directly related to fixing 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/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 2058321] Re: Unsupported platform 'ZynqMP KV260 revB
** Description changed: [ Impact ] + + * flash-kernel uses the model string in the kernel's device tree to determine what platform is running. Thus there is a dependency between the two packages + * A change in the model string for KR platforms was made to support rev B (LP #2046280) which breaks flash-kernel older versions of flash-kernel. [ Test Plan ] + * Kernel regression testing uses flash-kernel and will test this change + * certification testing uses flash-kernel and will test this change + [ Where problems could occur ] + * This will cause flash-kernel to be updated automatically when the + kernel is updated . This may introduce other issues caused by previous + flash-kernel changes that users were not running + [ Other info ] + + * flash-kernel SRU https://bugs.launchpad.net/ubuntu/+source/flash- + kernel/+bug/2054556 ** Changed in: linux-xilinx-zynqmp (Ubuntu) Assignee: (unassigned) => Portia Stephens (portias) ** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: New => In Progress ** Changed in: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided => High ** Description changed: [ Impact ] * flash-kernel uses the model string in the kernel's device tree to determine what platform is running. Thus there is a dependency between the two packages - * A change in the model string for KR platforms was made to support rev B (LP #2046280) which breaks flash-kernel older versions of flash-kernel. + * A change in the model string for KR platforms was made to support rev B (LP #2046280) which breaks older versions of flash-kernel. [ Test Plan ] * Kernel regression testing uses flash-kernel and will test this change * certification testing uses flash-kernel and will test this change [ Where problems could occur ] * This will cause flash-kernel to be updated automatically when the kernel is updated . This may introduce other issues caused by previous flash-kernel changes that users were not running [ Other info ] * flash-kernel SRU https://bugs.launchpad.net/ubuntu/+source/flash- kernel/+bug/2054556 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2058321 Title: Unsupported platform 'ZynqMP KV260 revB Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Bug description: [ Impact ] * flash-kernel uses the model string in the kernel's device tree to determine what platform is running. Thus there is a dependency between the two packages * A change in the model string for KR platforms was made to support rev B (LP #2046280) which breaks older versions of flash-kernel. [ Test Plan ] * Kernel regression testing uses flash-kernel and will test this change * certification testing uses flash-kernel and will test this change [ Where problems could occur ] * This will cause flash-kernel to be updated automatically when the kernel is updated . This may introduce other issues caused by previous flash-kernel changes that users were not running [ Other info ] * flash-kernel SRU https://bugs.launchpad.net/ubuntu/+source/flash- kernel/+bug/2054556 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2058321/+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 2058321] [NEW] Unsupported platform 'ZynqMP KV260 revB
Public bug reported: [ Impact ] [ Test Plan ] [ Where problems could occur ] [ Other info ] ** Affects: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2058321 Title: Unsupported platform 'ZynqMP KV260 revB Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: [ Impact ] [ Test Plan ] [ Where problems could occur ] [ Other info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2058321/+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 2056143] Re: block/loop: No longer allows to create partitions
Performing verification for Jammy. I started a fresh VM, with 5.15.0-101-generic from updates. I ran the following reproducer: $ fallocate -l 1G /tmp/blob $ LOOPDEV=$(sudo losetup --find --show /tmp/blob) $ sudo /usr/sbin/parted -s -m -a optimal $LOOPDEV -- unit KiB mklabel gpt mkpart primary 0% 100% Error: Partition(s) 1 on /dev/loop4 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes. I then enabled -proposed, and installed 5.15.0-102-generic: $ uname -rv 5.15.0-102-generic #112-Ubuntu SMP Tue Mar 5 16:50:32 UTC 2024 Running the reproducer: $ fallocate -l 1G /tmp/blob $ LOOPDEV=$(sudo losetup --find --show /tmp/blob) $ sudo /usr/sbin/parted -s -m -a optimal $LOOPDEV -- unit KiB mklabel gpt mkpart primary 0% 100% $ losetup -a /dev/loop4: []: (/tmp/blob) $ ll /dev ... brw-rw 1 root disk 7, 4 Mar 19 03:45 loop4 brw-rw 1 root disk259, 0 Mar 19 03:45 loop4p1 ... Things are now working as intended. The kernel in -proposed solves the issue. Happy to mark verified for Jammy. ** Tags removed: verification-needed-jammy-linux ** Tags added: sts verification-done-jammy-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/2056143 Title: block/loop: No longer allows to create partitions Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: == SRU Justification == -- Impact -- In 22.04/Jammy with the GA 5.15 kernel there was an upstream change preventing partition table operations when GENHD_FL_NO_PART is set. 1a721de8489f "block: don't add or resize partition on the disk with GENHD_FL_NO_PART" Beside of changing return codes and breaking some user-space that way this also causes loop block devices to no longer be able to have partitions manually created. This is because the loop block driver uses GENHD_FL_NO_PART to prevent active partition scans. -- Fix -- This was changed in 5.19 (and thus Mantic is not affected) by introducing a separate flag to prevent those scans: b9684a71fca7 "block, loop: support partitions without scanning" The fix depends on a larger rewrite so it cannot be simply picked. The biggest change from the original is moving the check for the new flag into a helper function in genhd.h which checks whether a disk should be scanned for partitions. That function was dropped with the upstream rewrite and checking moved into the loop driver directly. But it felt like adjusting the helper was the better approach. Note: The upstream patch has a follow-up change submitted: 748008e1da92 "block: don't add partitions if GD_SUPPRESS_PART_SCAN is set" We do _NOT_ need that in Jammy/5.15 because block/partitions/core.c: blk_add_partitions() checks disk_part_scan_enabled() which was where we added the check for the backport instead of modifying disk_scan_partitions() directly. -- Testcase -- $ fallocate -l 1G /tmp/blob $ LOOPDEV=$(sudo losetup --find --show /tmp/blob) $ sudo /usr/sbin/parted -s -m -a optimal $LOOPDEV -- unit KiB mklabel gpt mkpart primary 0% 100% -- Regression Potential -- If things go wrong it might be other devices which no longer get scanned automatically or other issues with the loop block driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-lowlatency-hwe-5.15/5.15.0.102.112~20.04.1)
All autopkgtests for the newly accepted linux-meta-lowlatency-hwe-5.15 (5.15.0.102.112~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-lowlatency-hwe-5.15/5.15.0-102.112~20.04.1 (amd64, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-lowlatency-hwe-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058315] [NEW] Mute/mic-mute LEDs not functioning on a HP platform
Public bug reported: [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. ** Affects: oem-priority Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2057730 originate-from-2057731 stella ** Tags added: oem-priority originate-from-2057730 stella ** Tags added: originate-from-2057731 -- 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 2047630] Re: Add quirk to disable i915 fastboot on B PC
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2047630 Title: Add quirk to disable i915 fastboot on B PC Status in HWE Next: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: [Impact] Some displays connect to the B PC device got the garbled display [Fix] The issue will disappear after commit 5ac860cc52540df8bca27e0bb25b6744df67e8f0, but these patches cannot be backported from 5.19 to 5.15. So add quirk to force disable the i915 fastboot on the device to fix the abnormal display [Test Case] 1. Connect the display and power on the B PC device 2. Check the display for boot up [Where problems could occur] Quirk only on the B PCs. Risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi/5.4.0.1106.136)
All autopkgtests for the newly accepted linux-meta-raspi (5.4.0.1106.136) for focal have finished running. The following regressions have been reported in tests triggered by the package: acpi-call/unknown (arm64) adv-17v35x/unknown (arm64) ddcci-driver-linux/unknown (arm64) dpdk/unknown (arm64) evdi/unknown (arm64) glibc/unknown (arm64) gost-crypto/unknown (arm64) iptables-netflow/unknown (arm64) jool/unknown (arm64) langford/unknown (arm64) lttng-modules/unknown (arm64) mali-midgard/unknown (arm64) nat-rtsp/unknown (arm64) nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (armhf) openafs/unknown (arm64) openrazer/unknown (arm64) r8168/unknown (arm64) rtl8821ce/unknown (arm64) systemd/unknown (arm64) wireguard/unknown (arm64) xtables-addons/unknown (arm64) zfs-linux/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-raspi [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054773] Re: Fix AMD brightness issue on AUO panel
** 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-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 2057484] Re: kernel worker event freezes during traffic on iwlwifi
I'm not sure the problem I'm having is exactly the same, but I also can't get any kernel after 6.5.0-21 to properly boot up on my laptop with an Intel wifi card. I'm attaching the portion of kern.log where a bunch of kernel worker tasks are reported as timed out; that happened, IIRC, after I tried to shut down the system by hitting the power button. The system wasn't really usable since most processes weren't able to start, so I couldn't really do a lot of investigation. Even trying to do "sudo blah" or just "ifconfig" would hang indefinitely. If it's any help, I have a bunch of options set for the Intel wifi driver: options iwlwifi power_save=0 options iwlmvm power_scheme=1 options iwldvm power_scheme=1 options lwlwifi bt_coex_active=enable ** Attachment added: "Kernel worker timeout reports from kern.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2057484/+attachment/5756935/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2057484 Title: kernel worker event freezes during traffic on iwlwifi Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: With traffic on Intel Wifi 7 BE200 card, For a while kernel enter 100% cpu usage on a worker event thread and kworker/0:0-events_freezable is in D state. System highly unresponsive during this time. Happens in 6.5.0-25, does not happen in 6.5.0-17 Description:Ubuntu 22.04.4 LTS Release:22.04 Installed: 6.5.0-25.25~22.04.1 Candidate: 6.5.0-25.25~22.04.1 Version table: *** 6.5.0-25.25~22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status linux-modules-6.5.0-25-generic: Installed: 6.5.0-25.25~22.04.1 Candidate: 6.5.0-25.25~22.04.1 Version table: *** 6.5.0-25.25~22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status filename: /lib/modules/6.5.0-25-generic/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko license:GPL description:Intel(R) Wireless WiFi driver for Linux firmware: iwlwifi-100-5.ucode firmware: iwlwifi-1000-5.ucode firmware: iwlwifi-135-6.ucode firmware: iwlwifi-105-6.ucode firmware: iwlwifi-2030-6.ucode firmware: iwlwifi-2000-6.ucode firmware: iwlwifi-5150-2.ucode firmware: iwlwifi-5000-5.ucode firmware: iwlwifi-6000g2b-6.ucode firmware: iwlwifi-6000g2a-6.ucode firmware: iwlwifi-6050-5.ucode firmware: iwlwifi-6000-6.ucode firmware: iwlwifi-7265D-29.ucode firmware: iwlwifi-7265-17.ucode firmware: iwlwifi-3168-29.ucode firmware: iwlwifi-3160-17.ucode firmware: iwlwifi-7260-17.ucode firmware: iwlwifi-8265-36.ucode firmware: iwlwifi-8000C-36.ucode firmware: iwlwifi-9260-th-b0-jf-b0-46.ucode firmware: iwlwifi-9000-pu-b0-jf-b0-46.ucode firmware: iwlwifi-cc-a0-77.ucode firmware: iwlwifi-QuZ-a0-jf-b0-77.ucode firmware: iwlwifi-QuZ-a0-hr-b0-77.ucode firmware: iwlwifi-Qu-b0-jf-b0-77.ucode firmware: iwlwifi-Qu-c0-hr-b0-77.ucode firmware: iwlwifi-Qu-b0-hr-b0-77.ucode firmware: iwlwifi-ma-b0-mr-a0-83.ucode firmware: iwlwifi-ma-b0-gf4-a0-83.ucode firmware: iwlwifi-ma-b0-gf-a0-83.ucode firmware: iwlwifi-ma-b0-hr-b0-83.ucode firmware: iwlwifi-ma-a0-mr-a0-83.ucode firmware: iwlwifi-ma-a0-gf4-a0-83.ucode firmware: iwlwifi-ma-a0-gf-a0-83.ucode firmware: iwlwifi-ma-a0-hr-b0-83.ucode firmware: iwlwifi-ty-a0-gf-a0-83.ucode firmware: iwlwifi-so-a0-gf-a0-83.ucode firmware: iwlwifi-so-a0-hr-b0-83.ucode firmware: iwlwifi-so-a0-jf-b0-83.ucode firmware: iwlwifi-gl-c0-fm-c0-83.ucode firmware: iwlwifi-gl-b0-fm-b0-83.ucode firmware: iwlwifi-bz-a0-fm4-b0-83.ucode firmware: iwlwifi-bz-a0-fm-c0-83.ucode firmware: iwlwifi-bz-a0-fm-b0-83.ucode firmware: iwlwifi-bz-a0-gf4-a0-83.ucode firmware: iwlwifi-bz-a0-gf-a0-83.ucode firmware: iwlwifi-bz-a0-hr-b0-83.ucode firmware: iwlwifi-sc-a0-wh-a0-83.ucode firmware: iwlwifi-sc-a0-gf4-a0-83.ucode firmware: iwlwifi-sc-a0-gf-a0-83.ucode firmware: iwlwifi-sc-a0-hr-b0-83.ucode firmware: iwlwifi-sc-a0-hr-b0-83.ucode firmware: iwlwifi-sc-a0-fm-c0-83.ucode firmware: iwlwifi-sc-a0-fm-b0-83.ucode srcversion: CE34BB7E0E287E10FEC1E13 alias: pci:v8086dE440sv*sd*bc*sc*i* alias:
[Kernel-packages] [Bug 2058191] Re: Getting SIGSEGV and SIGILL in many programs
** 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/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
** Changed in: linux-meta-lowlatency (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-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 2058226] Re: iwlwifi repeatedly logging microcode crashes
** Changed in: linux-firmware (Ubuntu) Assignee: (unassigned) => Jose Ogando Justo (joseogando) -- 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
[Kernel-packages] [Bug 2058208] Re: OpenGL renderer AMD defaults to Intel
** Changed in: linux-signed-oem-6.5 (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058208 Title: OpenGL renderer AMD defaults to Intel Status in linux-signed-oem-6.5 package in Ubuntu: Invalid Bug description: Checkbox job " com.canonical.certification::graphics/2_valid_opengl_renderer_PCI_ID_0x743f" fails with error: ``` Setting up PRIME GPU offloading for AMD discrete GPU OpenGL renderer string: Mesa Intel(R) Graphics (RPL-S) ERROR: renderer is Intel when DRI_PRIME=1 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-1016-oem 6.5.0-1016.17 ProcVersionSignature: Ubuntu 6.5.0-1016.17-oem 6.5.13 Uname: Linux 6.5.0-1016-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Mar 18 14:46:23 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-abra+X102 InstallationDate: Installed on 2024-03-15 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 SourcePackage: linux-signed-oem-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-6.5/+bug/2058208/+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 2058109] Re: Kernel 5.15.0-100 breaks Intel NIC
** 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/2058109 Title: Kernel 5.15.0-100 breaks Intel NIC Status in linux package in Ubuntu: New Bug description: From syslog: Mar 15 12:11:18 kvmMini systemd[1]: Starting Refresh fwupd metadata and update motd... Mar 15 12:11:18 kvmMini fwupdmgr[284042]: Updating lvfs Mar 15 12:11:18 kvmMini fwupdmgr[284042]: Downloading…: 0% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 100% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 0% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 1% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 2% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 3% ...trimmed content Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 97% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 98% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100% Mar 15 12:11:20 kvmMini fwupdmgr[284042]: Successfully downloaded new metadata: 0 local devices supported Mar 15 12:11:20 kvmMini systemd[1]: fwupd-refresh.service: Deactivated successfully. Mar 15 12:11:20 kvmMini systemd[1]: Finished Refresh fwupd metadata and update motd. Mar 15 12:17:01 kvmMini CRON[284549]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 15 12:23:59 kvmMini kernel: [3519186.337746] x86/split lock detection: #AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xf80746442fb3 Mar 15 12:26:49 kvmMini kernel: [3519356.515727] x86/split lock detection: #AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xf80746442fb3 Mar 15 13:05:00 kvmMini systemd[1]: run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.5pHMXa.mount: Deactivated successfully. Mar 15 13:07:48 kvmMini kernel: [3521815.001961] x86/split lock detection: #AC: CPU 0/KVM/279304 took a split_lock trap at address: 0xf80521c42fb3 Mar 15 13:17:01 kvmMini CRON[289583]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 15 13:20:49 kvmMini kernel: [3522596.527060] x86/split lock detection: #AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xf80746442fb3 Mar 15 13:30:01 kvmMini systemd[1]: run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.I79KlX.mount: Deactivated successfully. Mar 15 13:43:22 kvmMini kernel: [3523948.983970] x86/split lock detection: #AC: CPU 0/KVM/279304 took a split_lock trap at address: 0xf80521c42fb3 Mar 15 13:53:22 kvmMini kernel: [3524549.046156] x86/split lock detection: #AC: CPU 0/KVM/1774 took a split_lock trap at address: 0xf8041de42fb3 Mar 15 14:07:33 kvmMini systemd[1]: run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.K8Zq9M.mount: Deactivated successfully. Mar 15 14:17:01 kvmMini CRON[294744]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 15 14:20:03 kvmMini kernel: [3526150.403065] e1000e :00:1f.6 eno2: Detected Hardware Unit Hang: Mar 15 14:20:03 kvmMini kernel: [3526150.403065] TDH <9f> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] TDT <9> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] next_to_use <9> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] next_to_clean<9e> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] buffer_info[next_to_clean]: Mar 15 14:20:03 kvmMini kernel: [3526150.403065] time_stamp <1348a0aab> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] next_to_watch<9f> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] jiffies <1348a0bb0> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] next_to_watch.status <0> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] MAC Status <40080083> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY Status <796d> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY 1000BASE-T Status <3800> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY Extended Status<3000> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PCI Status <10> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] e1000e :00:1f.6 eno2: Detected Hardware Unit Hang: Mar 15 14:20:05 kvmMini kernel: [3526152.391042] TDH <9f> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] TDT <9> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] next_to_use <9> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] next_to_clean<9e> Mar 15 14:20:05
[Kernel-packages] [Bug 2058124] Re: Touchpad and Microphone not recognized
** Changed in: linux-signed-hwe-5.15 (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2058124 Title: Touchpad and Microphone not recognized Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Ubuntu20.04 Kernel:`5.15.0-100-generic #110~20.04.1-Ubuntu SMP Tue Feb 13 14:25:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux` The TouchPad and Microphone in my HP Laptop could not be recognized, but both are OK in Windows 11 system. `xinput` command result： ``` (base) ➜ ~ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Instant USB Optical Mouse id=9[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ HP True Vision FHD Camera: HP T id=10 [slave keyboard (3)] ↳ Intel HID eventsid=11 [slave keyboard (3)] ↳ Intel HID 5 button arrayid=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ↳ HP WMI hotkeys id=14 [slave keyboard (3)] ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-100-generic 5.15.0-100.110~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-100.110~20.04.1-generic 5.15.143 Uname: Linux 5.15.0-100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 09:10:00 2024 InstallationDate: Installed on 2024-03-02 (14 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2058124/+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: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2057792 Title: Certains jeux crashent liés à un vm_max_map_count trop faible Status in Ubuntu: Fix Released 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 2018584] Re: Ubuntu randomly goes to sleep during normal usage
*** This bug is a duplicate of bug 2043073 *** https://bugs.launchpad.net/bugs/2043073 I have the same symptoms as described in the initial post. I haven't seen any ACPI BIOS errors though. I'm not sure what logs might be helpful in debugging this but I'm happy to upload anything that might help get this solved. -- 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/2018584 Title: Ubuntu randomly goes to sleep during normal usage Status in linux package in Ubuntu: Confirmed Bug description: During normal utilization, Ubuntu 23.04 goes to sleep from time to time, without being idle for any period. A typical situation is that during typing on the keyboard, the notebook turns black, disconnects from Bluetooth devices and appears dead, without even the power button glowing. When pressing a key after a few seconds, the computer awakens to the login screen. lsb_release -rd: No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lukaschmela 10054 F wireplumber /dev/snd/seq:lukaschmela 10045 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-18 (17 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Dell Inc. Precision 3551 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=cs_CZ.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=UUID=c0c8c78a-a454-4946-903e-16f32226b875 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-18 (17 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 0M21VD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd02/13/2023:br1.20:svnDellInc.:pnPrecision3551:pvr:rvnDellInc.:rn0M21VD:rvrA00:cvnDellInc.:ct10:cvr:sku09C2: dmi.product.family: Precision dmi.product.name: Precision 3551 dmi.product.sku: 09C2 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018584/+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 1803881] Re: thermal thermal_zone4: failed to read out thermal zone (-61)
I've seen the same on Ubuntu 22.04.3, kernel 6.5.0-25-generic, desktop
AMD 5700G:
[110978.115995] thermal thermal_zone2: failed to read out thermal zone (-61)
[110978.116002] PM: suspend exit
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1803881
Title:
thermal thermal_zone4: failed to read out thermal zone (-61)
Status in linux package in Ubuntu:
Incomplete
Status in thermald package in Ubuntu:
Confirmed
Bug description:
Thermald can't read zone4. It's making my fan go crazy, this issue
seems to be a bit more controlled in 18.10.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
sudo apt-cache policy thermald
thermald:
Installed: 1.7.0-5ubuntu1
Candidate: 1.7.0-5ubuntu1
Version table:
*** 1.7.0-5ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
cat /sys/class/thermal/thermal_zone4/type
iwlwifi
find /sys/class/thermal/thermal_zone4/ -type f -print -exec cat {} \;
/sys/class/thermal/thermal_zone4/uevent
/sys/class/thermal/thermal_zone4/trip_point_5_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_3_type
passive
/sys/class/thermal/thermal_zone4/trip_point_4_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_2_type
passive
/sys/class/thermal/thermal_zone4/power/runtime_active_time
0
/sys/class/thermal/thermal_zone4/power/runtime_active_kids
0
/sys/class/thermal/thermal_zone4/power/runtime_usage
0
/sys/class/thermal/thermal_zone4/power/runtime_status
unsupported
/sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms
cat: /sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms:
Input/output error
/sys/class/thermal/thermal_zone4/power/async
disabled
/sys/class/thermal/thermal_zone4/power/runtime_suspended_time
0
/sys/class/thermal/thermal_zone4/power/runtime_enabled
disabled
/sys/class/thermal/thermal_zone4/power/control
auto
/sys/class/thermal/thermal_zone4/available_policies
power_allocator user_space bang_bang fair_share step_wise
/sys/class/thermal/thermal_zone4/policy
step_wise
/sys/class/thermal/thermal_zone4/trip_point_3_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_1_type
passive
/sys/class/thermal/thermal_zone4/k_d
cat: /sys/class/thermal/thermal_zone4/k_d: Input/output error
/sys/class/thermal/thermal_zone4/sustainable_power
cat: /sys/class/thermal/thermal_zone4/sustainable_power: Input/output error
/sys/class/thermal/thermal_zone4/type
iwlwifi
/sys/class/thermal/thermal_zone4/trip_point_7_type
passive
/sys/class/thermal/thermal_zone4/offset
cat: /sys/class/thermal/thermal_zone4/offset: Input/output error
/sys/class/thermal/thermal_zone4/slope
cat: /sys/class/thermal/thermal_zone4/slope: Input/output error
/sys/class/thermal/thermal_zone4/trip_point_2_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_0_type
passive
/sys/class/thermal/thermal_zone4/trip_point_6_type
passive
/sys/class/thermal/thermal_zone4/emul_temp
cat: /sys/class/thermal/thermal_zone4/emul_temp: Permission denied
/sys/class/thermal/thermal_zone4/k_po
cat: /sys/class/thermal/thermal_zone4/k_po: Input/output error
/sys/class/thermal/thermal_zone4/integral_cutoff
cat: /sys/class/thermal/thermal_zone4/integral_cutoff: Input/output error
/sys/class/thermal/thermal_zone4/k_i
cat: /sys/class/thermal/thermal_zone4/k_i: Input/output error
/sys/class/thermal/thermal_zone4/trip_point_1_temp
-32768000
/sys/class/thermal/thermal_zone4/k_pu
cat: /sys/class/thermal/thermal_zone4/k_pu: Input/output error
/sys/class/thermal/thermal_zone4/temp
46000
/sys/class/thermal/thermal_zone4/trip_point_7_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_5_type
passive
/sys/class/thermal/thermal_zone4/trip_point_0_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_6_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_4_type
passive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803881/+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 1772434] Re: Broadcom: IT (HBA) Driver Enablement in 18.04 (Patches)
Closing, this is an old bug and this support likely landed long ago. ** Changed in: dellserver Status: In Progress => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772434 Title: Broadcom: IT (HBA) Driver Enablement in 18.04 (Patches) Status in dellserver: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: The purpose of this bug is to track the patches needed to enable the IT (HBA) driver into 18.04. Below are upstream commit ids of IT driver which went in over the in- box driver of Ubuntu18.04 OS’s base kernel, 864449eea7c600596e305ffdc4a6a846414b222c scsi: mpt3sas: Do not mark fw_event workqueue as WQ_MEM_RECLAIM 6f9e09fd6488de7661ee20efb5d8ab4e05a59735 scsi: mpt3sas: clarify mmio pointer types 40114bde9773ccaf9ad77233ac2cc9039f0f2941 scsi: mpt3sas: Do not use 32-bit atomic request descriptor for Ventura controllers. b4472d7180894c96b6133ef5ff3df50836591eaa scsi: mpt3sas: Introduce function to clone mpi reply. e5747439366c1079257083f231f5dd9a84bf0fd7 scsi: mpt3sas: Introduce function to clone mpi request. 182ac784b41faee02e8b44cd7149575258ad6858 scsi: mpt3sas: Introduce Base function for cloning. 22ae5a3c2599381cf7aaa5aca25c515a3166adcc scsi: mpt3sas: Introduce API to get BAR0 mapped buffer address 0448f0195124e33f11d15b7d1e1cab959989eee7 scsi: mpt3sas: Configure reply post queue depth, DMA and sgl tablesize. c520691b38cde1d94f53e5782feba892f5645043 scsi: mpt3sas: Add PCI device ID for Andromeda. 4a8842de8db4953fdda7866626b78b12fb8adb97 scsi: mpt3sas: fix an out of bound write 61dfb8a5fb7e93e692856026fa4c778a27f28984 scsi: mpt3sas: make function _get_st_from_smid static dbec4c9040edc15442c3ebdb65408aa9d3b82c24 scsi: mpt3sas: lockless command submission 272e253c7bcabfeef5f4d0aaed94a413e13e520f scsi: mpt3sas: simplify _wait_for_commands_to_complete() 6da999fe5a9285c2a78f3cf1e768abcd48d7607e scsi: mpt3sas: simplify mpt3sas_scsi_issue_tm() 74fcfa5371b7a681e864d3a9d3b9ecfd5737d8ea scsi: mpt3sas: simplify task management functions b0cd285eb57cd3cb18d882565c22d39bccffe7f0 scsi: mpt3sas: always use first reserved smid for ioctl passthrough 9961c9bbf2b43acaaf030a0fbabc9954d937ad8c scsi: mpt3sas: check command status before attempting abort 12e7c6782bc58128392b768fc2a87b230414a2a5 scsi: mpt3sas: Introduce mpt3sas_get_st_from_smid() 02a386df3678275b01eec71fee39735c379e4a2a scsi: mpt3sas: open-code _scsih_scsi_lookup_get() 6a2d4618aef3d4ffb83514e5e58a091d61e54a03 scsi: mpt3sas: separate out _base_recovery_check() 05303dfb738066ad597d7feb422ff9fa2d3d8ef3 scsi: mpt3sas: use list_splice_init() ba4494d47bd02e5757b449a2ccfa3ff87bc8 scsi: mpt3sas: set default value for cb_idx f49d4aed1315a7b766d855f1367142e682b0cc87 scsi: mpt3sas: Proper handling of set/clear of "ATA command pending" flag. 45b7aef7fb7d5f5bfa3a2a6727f1accf7660f6fd scsi: mpt3sas: Remove unused variable requeue_event To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1772434/+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
** Tags removed: verification-needed-focal-linux-gcp
** Tags added: verification-done-focal-linux-gcp
--
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:
In Progress
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 2043208] Re: Headset microphone not properly recognized after 23.10 upgrade
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2043208 Title: Headset microphone not properly recognized after 23.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: [description] My wired headset (hyperx cloud 2) has a built in microphone that was working perfectly fine in 22.10 and 23.04 on my system. But after upgrading to 23.10 most of the time when plugging it into the headphone jack of my machine, audio output works perfectly fine however the microphone is often not recognized. Running "systemctl --user restart pipewire pipewire-pulse wireplumber" a few times often causes the microphone to be recognized by the system but applications such as firefox wouldn't recognize it. Restarting the machine usually would make applications able to detect and use the microphone. [possible solution] I have found a few reports of people having similar issues as me after upgrading to 23.10 and I was even able to find on the french ubuntu forums a possible fix where manually installing kernel 6.6rc5 or above has fixed the issue: https://forum.ubuntu-fr.org/viewtopic.php?id=2081994 I couldn't verify this solution for myself since I an still running the default 6.5 kernel that came with Mantic but I did find another user on askubuntu who upgraded to the 6.6rc5 kernel and had his microphone issues resolved: https://askubuntu.com/questions/1490935/built-in-microphone-not-detected-after-installing-ubuntu-23-10 This thread also referenced the "forum.ubuntu-fr.org" forum. My specific issue might be pipewire related and not kernel related but based on the number of reports I've seen that 6.6rc5 fixes the issue (6.6rc1 did not based on the reports) the issue is also kernel related to some extent. [system] Dell XPS 17 9720, intel core i9 12900HK, RTX 3060 6GB + intel iris Xe Kubuntu 23.10 using wayland with plasma 5.27.8 nvidia driver: 545.29.02 (proprietary). I also had the same issue on 535 driver Headset: Hyperx cloud II with the default microphone that came with the headset (microphone is detachable) uname -r: 6.5.0-10-generic Headset and microphone work perfectly fine on other systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043208/+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
** Tags removed: verification-needed-bionic-linux-gcp-4.15
** Tags added: verification-done-bionic-linux-gcp-4.15
--
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:
In Progress
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 2006259] Re: net: wwan: t7xx: Fix Runtime PM implementation
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: Incomplete => Won't Fix
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2006259
Title:
net: wwan: t7xx: Fix Runtime PM implementation
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.0 source package in Jammy:
Won't Fix
Status in linux-oem-6.1 source package in Jammy:
Won't Fix
Status in linux source package in Kinetic:
Won't Fix
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in linux-oem-6.0 source package in Lunar:
Invalid
Status in linux-oem-6.1 source package in Lunar:
Invalid
Bug description:
Upstream commit d10b3a695ba0 ("net: wwan: t7xx: Runtime PM")
introduced support for Runtime PM for this driver, but due to a bug in
the initialization logic the usage refcount would never reach 0,
leaving the feature unused. This patchset addresses that, together
with a bug found after runtime suspend was enabled.
https://lore.kernel.org/netdev/20230126132535.80339-1-min...@semihalf.com/
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2006259/+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 1995779] Re: [HP Pavilion All-in-One Desktop 27-ca1xxx] USB is broken on resume from suspend
oem-6.1 is about to be EOL ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/1995779 Title: [HP Pavilion All-in-One Desktop 27-ca1xxx] USB is broken on resume from suspend Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Won't Fix Bug description: Ubuntu: 22.04 jammy Computer: HP Pavilion All-in-One Desktop 27-ca1xxx So a desktop but with a hybrid GPU setup like a laptop. GPU: NVIDIA GeForce RTX 3050 Laptop GPU + Intel(R) Graphics (ADL-S GT1) GPU driver: This happens with all Nvidia proprietary drivers tested so far, 510, 515, 520. I reported it on the latest. Kernel: This happens with all kernels tested so far from 5.15 to 6.0 Desktop: This only happens with an X11 session! If I switch to Wayland it doesn't happen. Problem: When you suspend the computer a number of strange things may happen. Lose connection to keyboard and mouse. Lose connection to USB-C Audio speakers. Stuck on black VT terminal screen. Sometimes reproduced on first try, sometimes it takes 5 tries. Switching to Wayland allows to suspend/resume perfectly however. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ernst 113040 F pulseaudio /dev/snd/controlC0: ernst 113040 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (290 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP Pavilion All-in-One Desktop 27-ca1xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux-oem-6.1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1007-oem root=UUID=72ea78e1-7744-4fcc-b63c-3aa577c86a80 ro quiet splash ibt=off mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1007.7-oem 6.1.6 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.1.0-1007-oem N/A linux-backports-modules-6.1.0-1007-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 Tags: jammy wayland-session Uname: Linux 6.1.0-1007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/09/2022 dmi.bios.release: 15.2 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.name: 89E9 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnAMI:bvrF.02:bd02/09/2022:br15.2:efr1.16:svnHP:pnHPPavilionAll-in-OneDesktop27-ca1xxx:pvr:rvnHP:rn89E9:rvr0100:cvnHP:ct13:cvr:sku661Q7EA#UUW: dmi.product.family: 103C_53311M HP Pavilion dmi.product.name: HP Pavilion All-in-One Desktop 27-ca1xxx dmi.product.sku: 661Q7EA#UUW dmi.sys.vendor: HP modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-06-15T22:28:44.879144 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995779/+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 2008188] Re: blacklist: Problem blacklisting hash
** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2008188 Title: blacklist: Problem blacklisting hash Status in linux package in Ubuntu: Won't Fix Status in linux-oem-6.1 package in Ubuntu: Won't Fix Bug description: When boot up the system from oem-6.1 kernel, some errors will printed in the console. Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008188/+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 2016469] Re: test_maps in ubuntu_bpf failed on J-oem-6.1 ( run_parallel: Assertion `status == 0' failed.)
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2016469 Title: test_maps in ubuntu_bpf failed on J-oem-6.1 ( run_parallel: Assertion `status == 0' failed.) Status in ubuntu-kernel-tests: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Bug description: Issue found in J-oem-6.1.0-1009.9 after fixing the build issue in bug 2016455. The test_maps in ubuntu_bpf will fail with: test_maps: test_maps.c:1375: __run_parallel: Assertion `status == 0' failed. Test log: Running './test_maps' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, ,
[Kernel-packages] [Bug 2017277] Re: Regression: 6.1.0.9-1009 causes RTL8852BE WiFi to fail randomly
oem-6.1 is about to be EOL ** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2017277 Title: Regression: 6.1.0.9-1009 causes RTL8852BE WiFi to fail randomly Status in linux-oem-6.1 package in Ubuntu: Won't Fix Bug description: The 6.1 OEM kernel contains backported (from 6.2) support for the RTL8852BE wireless adapter. This has worked fine on my laptop since the support was backported. The latest release, 6.1.0.9-1009 is causing my adapter to occasionally stop working completely. The WiFi disconnects, and GNOME tells me an adapter cannot be found. A reboot is required to get the internet working again. This has happened twice. Running `dmesg` reports a lot of error messages with the adapter - find the output in error.txt, attached. Thanks for any help you can offer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2017277/+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 2025444] Re: Mute/mic LEDs no function on some HP Platforms
** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2025444 Title: Mute/mic LEDs no function on some HP Platforms Status in OEM Priority Project: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Bug description: [Impact] The mic mute/audio mute LEDS are not work on some HP Platforms [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk on linux-oem-6.1, 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/2025444/+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 2034535] Re: 6.1.0.1021.21: severe problems with f2fs
oem-6.1 is about to be EOL ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2034535 Title: 6.1.0.1021.21: severe problems with f2fs Status in linux-oem-6.1 package in Ubuntu: Won't Fix Bug description: After updating my system was unusable. The kernel dropped an error message multiple times. Downgrading to 6.1.0.1020.20 fixed the issue. I have 2 f2fs partitions on 2 SSDs - one NVME, the other SATA. Since it happens in recovery mode as well, I assume that it definitively happens on the NVME disk. Not sure about SATA. lsb_release -rd: Description:KDE neon 5.27 Release:22.04 apt-cache policy ..: linux-image-6.1.0-1021-oem: Installed: (none) Candidate: 6.1.0-1021.21 Version table: 6.1.0-1021.21 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status Error messages: (from /var/log/syslog) Sep 6 11:00:04 nyarly kernel: [ 21.885763] BUG: kernel NULL pointer dereference, address: 0024 Sep 6 11:00:04 nyarly kernel: [ 21.885769] #PF: supervisor write access in kernel mode Sep 6 11:00:04 nyarly kernel: [ 21.885771] #PF: error_code(0x0002) - not-present page Sep 6 11:00:04 nyarly kernel: [ 21.885772] PGD 0 P4D 0 Sep 6 11:00:04 nyarly kernel: [ 21.885776] Oops: 0002 [#9] PREEMPT SMP PTI Sep 6 11:00:04 nyarly kernel: [ 21.885778] CPU: 3 PID: 1430 Comm: containerd Tainted: P DOE 6.1.0-1021-oem #21-Ubuntu Sep 6 11:00:04 nyarly kernel: [ 21.885781] Hardware name: System manufacturer System Product Name/H170-PRO/USB 3.1, BIOS 2002 09/20/2016 Sep 6 11:00:04 nyarly kernel: [ 21.885783] RIP: 0010:f2fs_issue_flush+0x12f/0x1a0 [f2fs] Sep 6 11:00:04 nyarly kernel: [ 21.885813] Code: c9 ba 01 00 00 00 be 03 00 00 00 e8 5b 42 66 e6 48 83 3b 00 74 1d 4c 89 f7 e8 2d 95 45 e7 f0 ff 4b 24 8b 45 cc e9 5f ff ff ff ff 43 24 e9 43 ff ff ff 31 d2 48 87 53 28 48 85 d2 74 d8 44 89 Sep 6 11:00:04 nyarly kernel: [ 21.885815] RSP: 0018:a79b0924fcb8 EFLAGS: 00010246 Sep 6 11:00:04 nyarly kernel: [ 21.885818] RAX: RBX: RCX: Sep 6 11:00:04 nyarly kernel: [ 21.885819] RDX: 10bc RSI: 001cbbda RDI: a79b0924fcf0 Sep 6 11:00:04 nyarly kernel: [ 21.885821] RBP: a79b0924fd20 R08: R09: Sep 6 11:00:04 nyarly kernel: [ 21.885823] R10: R11: R12: 99821c12a000 Sep 6 11:00:04 nyarly kernel: [ 21.885824] R13: 001cbbda R14: a79b0924fcc0 R15: 0024 Sep 6 11:00:04 nyarly kernel: [ 21.885826] FS: 7faa52ffd640() GS:998525d8() knlGS: Sep 6 11:00:04 nyarly kernel: [ 21.885828] CS: 0010 DS: ES: CR0: 80050033 Sep 6 11:00:04 nyarly kernel: [ 21.885830] CR2: 0024 CR3: 00013b2d8005 CR4: 003706e0 Sep 6 11:00:04 nyarly kernel: [ 21.885832] DR0: DR1: DR2: Sep 6 11:00:04 nyarly kernel: [ 21.885833] DR3: DR6: fffe0ff0 DR7: 0400 Sep 6 11:00:04 nyarly kernel: [ 21.885835] Call Trace: Sep 6 11:00:04 nyarly kernel: [ 21.885836] Sep 6 11:00:04 nyarly kernel: [ 21.885838] ? show_trace_log_lvl+0x1e8/0x30d Sep 6 11:00:04 nyarly kernel: [ 21.885843] ? show_trace_log_lvl+0x1e8/0x30d Sep 6 11:00:04 nyarly kernel: [ 21.885848] ? f2fs_do_sync_file+0x78e/0xaa0 [f2fs] Sep 6 11:00:04 nyarly kernel: [ 21.885865] ? show_regs.part.0+0x23/0x31 Sep 6 11:00:04 nyarly kernel: [ 21.885869] ? __die_body.cold+0x8/0xd Sep 6 11:00:04 nyarly kernel: [ 21.885872] ? __die+0x2a/0x3b Sep 6 11:00:04 nyarly kernel: [ 21.885876] ? page_fault_oops+0x174/0x1b0 Sep 6 11:00:04 nyarly kernel: [ 21.885881] ? do_user_addr_fault+0x2f3/0x5a0 Sep 6 11:00:04 nyarly kernel: [ 21.885884] ? exc_page_fault+0x80/0x1b0 Sep 6 11:00:04 nyarly kernel: [ 21.885888] ? asm_exc_page_fault+0x27/0x30 Sep 6 11:00:04 nyarly kernel: [ 21.885892] ? f2fs_issue_flush+0x12f/0x1a0 [f2fs] Sep 6 11:00:04 nyarly kernel: [ 21.885917] f2fs_do_sync_file+0x78e/0xaa0 [f2fs] Sep 6 11:00:04 nyarly kernel: [ 21.885933] ? f2fs_buffered_write_iter+0x41/0x70 [f2fs] Sep 6 11:00:04 nyarly kernel: [ 21.885950] f2fs_sync_file+0x30/0x60 [f2fs] Sep 6 11:00:04 nyarly kernel: [ 21.885966] __x64_sys_fdatasync+0x4c/0xa0 Sep 6 11:00:04 nyarly kernel: [ 21.885969] do_syscall_64+0x58/0x90 Sep 6 11:00:04 nyarly kernel: [ 21.885972] ? __x64_sys_pwrite64+0xb6/0xd0 Sep 6
[Kernel-packages] [Bug 2036625] Re: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie
oem-6.1 is about to be EOL ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2036625 Title: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie linux-oem-5.17-tools-host 5.17.0-1035.36 Status in linux-oem-6.1 package in Ubuntu: Won't Fix Bug description: Install problem ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-oem-6.1-tools-host (not installed) ProcVersionSignature: Ubuntu 6.5.0-1003.3-oem 6.5.0 Uname: Linux 6.5.0-1003-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Sep 19 17:16:27 2023 ErrorMessage: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie linux-oem-5.17-tools-host 5.17.0-1035.36 InstallationDate: Installed on 2023-08-27 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: linux-oem-6.1 Title: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie linux-oem-5.17-tools-host 5.17.0-1035.36 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2036625/+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 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.1 / J-6.2 AMD64
** Changed in: linux-oem-6.1 (Ubuntu Lunar)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Mantic)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1983357
Title:
test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on
K-5.19 / J-OEM-6.1 / J-6.2 AMD64
Status in QA Regression Testing:
Invalid
Status in ubuntu-kernel-tests:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Won't Fix
Status in linux source package in Kinetic:
Invalid
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Won't Fix
Status in linux-oem-6.1 source package in Lunar:
Invalid
Status in linux source package in Mantic:
Fix Released
Status in linux-oem-6.1 source package in Mantic:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.1 source package in Noble:
Invalid
Bug description:
Issue found on 5.19.0-9.9 Kinetic AMD64 systems
Test log:
Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel:
'5.19.0-9.9 (Ubuntu 5.19.0-9.9-generic 5.19.0-rc5)' arch: 'amd64' uid: 0/0
SUDO_USER: 'ubuntu')
test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
ASLR of libs ... (default libs native) (default libs native rekey) (default
libs COMPAT) FAIL
==
FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
ASLR of libs
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 1770, in test_021_aslr_dapper_libs
self._test_aslr('libs', expected)
File "./test-kernel-security.py", line 1727, in _test_aslr
self._test_aslr_all(area, expected, "default %s" % area)
File "./test-kernel-security.py", line 1720, in _test_aslr_all
self._test_aslr_exec(area, expected, target, name)
File "./test-kernel-security.py", line 1703, in _test_aslr_exec
self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area,
"--verbose"], msg="%s:\n" % name)
File
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
line 1203, in assertShellExitEquals
self.assertEqual(expected, rc, msg + result + report)
AssertionError: default libs COMPAT:
Got exit code 1, expected 0
Command: './aslr32', 'libs', '--verbose'
Output:
Checking ASLR of libs:
0xf7c81790
0xf7c81790
0xf7c81790
FAIL: ASLR not functional (libs always at 0xf7c81790)
--
Ran 1 test in 0.144s
FAILED (failures=1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1983357/+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) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Mantic) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-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 2009952] Re: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel
oem-6.1 is about to be EOL ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009952 Title: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Bug description: After upgrading from kernel 5.19.0-35-generic to 6.1.0-1007-oem there is occasional screen flicker/ tear. It happens around every minute; it seems connected to window/ pointer movement, but I have no clear way of reproducing. Disruption is minor, but annoying. I'm running 22.04 LTS on a new Thinkpad T14s with AMD Ryzen 6850u. The system is fully functional. No crashes, nothing breaks. Background on the use of 6.1.0-1007-oem: 5.19.0-35-generic breaks suspend/ resume on my laptop, see https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718. In a way, running 6.1 is a 'flight forward', since 5.15.0-67-generic (previous 22.04.1 LTS kernel) works well, with working suspend/ resume, and without screen flicker. But that's an 'old' kernel now, missing some nice improvements for the newer Ryzen APUs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-oem-22.04c 6.1.0.1007.7 ProcVersionSignature: Ubuntu 6.1.0-1007.7-oem 6.1.6 Uname: Linux 6.1.0-1007-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 10 13:09:20 2023 InstallationDate: Installed on 2023-02-06 (31 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-meta-oem-6.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009952/+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 2053194] Re: latest kernel update breaks sata hotplug on z690
I can confirm sata hotplug is still not working as of kernel 6.5.0-26. It is working on 6.5.11-060511-generic mainline. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2053194 Title: latest kernel update breaks sata hotplug on z690 Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: SATA hotplug is not working on these kernels: linux-image-6.5.0-17-generic linux-image-5.15.0-94-generic SATA hotplug is working on these kernels: linux-image-6.5.0-15-generic linux-image-5.15.0-92-generic Affected platform: Gigabyte Z690 AORUS PRO BIOS Version: F28 Note that I can only repro this on Z690. I also tried Z390 and Z370 platforms and SATA hotplug it is working there. Steps to repro: 1. Enable SATA hotplug in BIOS 2. Boot to affected kernel 3. Hotplug a SATA drive while monitoring kernel messages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 14 13:20:34 2024 InstallationDate: Installed on 2024-01-26 (18 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-01-26T15:01:36.495491 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2053194/+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 2058265] [NEW] Failed to Connect to CoreDump Service on Shutdown
Public bug reported: Starting with this package, shutdown error: Mar 18 11:25:29 mic-Aspire-E5-576G systemd-coredump[4348]: Failed to connect to coredump service: Connection refused This error and splashed log on shutdown, NOT PRESENT BEFORE THIS KERNEL. Now persisting into Kernel ending ...101.111 Ref. https://forums.linuxmint.com/viewtopic.php?p=2445431#p2445431 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058265 Title: Failed to Connect to CoreDump Service on Shutdown Status in linux package in Ubuntu: New Bug description: Starting with this package, shutdown error: Mar 18 11:25:29 mic-Aspire-E5-576G systemd-coredump[4348]: Failed to connect to coredump service: Connection refused This error and splashed log on shutdown, NOT PRESENT BEFORE THIS KERNEL. Now persisting into Kernel ending ...101.111 Ref. https://forums.linuxmint.com/viewtopic.php?p=2445431#p2445431 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058265/+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 2038831] Re: Jammy update: v6.1.55 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2038831 Title: Jammy update: v6.1.55 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.55 upstream stable release from git://git.kernel.org/ Linux 6.1.55 interconnect: Teach lockdep about icc_bw_lock order net/sched: Retire rsvp classifier drm/amdgpu: fix amdgpu_cs_p1_user_fence Revert "memcg: drop kmem.limit_in_bytes" drm/amd/display: fix the white screen issue when >= 64GB DRAM ext4: fix rec_len verify error scsi: pm8001: Setup IRQs on resume scsi: megaraid_sas: Fix deadlock on firmware crashdump ata: libahci: clear pending interrupt status ata: libata: disallow dev-initiated LPM transitions to unsupported states i2c: aspeed: Reset the i2c controller when timeout occurs tracefs: Add missing lockdown check to tracefs_create_dir() nfsd: fix change_info in NFSv4 RENAME replies selinux: fix handling of empty opts in selinux_fs_context_submount() tracing: Have option files inc the trace array ref count tracing: Have current_trace inc the trace array ref count tracing: Increase trace array ref count on enable and filter files tracing: Have event inject files inc the trace array ref count tracing: Have tracing_max_latency inc the trace array ref count btrfs: check for BTRFS_FS_ERROR in pending ordered assert btrfs: release path before inode lookup during the ino lookup ioctl btrfs: fix a compilation error if DEBUG is defined in btree_dirty_folio btrfs: fix lockdep splat and potential deadlock after failure running delayed items dm: don't attempt to queue IO under RCU protection Revert "drm/amd: Disable S/G for APUs when 64GB or more host memory" md: Put the right device in md_seq_next nvme: avoid bogus CRTO values io_uring/net: fix iter retargeting for selected buf ovl: fix incorrect fdput() on aio completion ovl: fix failed copyup of fileattr on a symlink attr: block mode changes of symlinks Revert "SUNRPC: Fail faster on bad verifier" md/raid1: fix error: ISO C90 forbids mixed declarations samples/hw_breakpoint: fix building without module unloading x86/purgatory: Remove LTO flags x86/boot/compressed: Reserve more memory for page tables panic: Reenable preemption in WARN slowpath scsi: lpfc: Fix the NULL vs IS_ERR() bug for debugfs_create_file() scsi: target: core: Fix target_cmd_counter leak riscv: kexec: Align the kexeced kernel entry x86/ibt: Suppress spurious ENDBR selftests: tracing: Fix to unmount tracefs for recovering environment scsi: qla2xxx: Fix NULL vs IS_ERR() bug for debugfs_create_dir() drm: gm12u320: Fix the timeout usage for usb_bulk_msg() nvmet-tcp: pass iov_len instead of sg->length to bvec_set_page() nvmet: use bvec_set_page to initialize bvecs block: factor out a bvec_set_page helper btrfs: compare the correct fsid/metadata_uuid in btrfs_validate_super btrfs: add a helper to read the superblock metadata_uuid MIPS: Use "grep -E" instead of "egrep" misc: fastrpc: Fix incorrect DMA mapping unmap request misc: fastrpc: Prepare to dynamic dma-buf locking specification dma-buf: Add unlocked variant of attachment-mapping functions printk: Consolidate console deferred printing printk: Keep non-panic-CPUs out of console lock interconnect: Fix locking for runpm vs reclaim kobject: Add sanity check for kset->kobj.ktype in kset_register() media: pci: ipu3-cio2: Initialise timing struct to avoid a compiler warning usb: chipidea: add workaround for chipidea PEC bug usb: ehci: add workaround for chipidea PORTSC.PEC bug misc: open-dice: make OPEN_DICE depend on HAS_IOMEM serial: cpm_uart: Avoid suspicious locking scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() tools: iio: iio_generic_buffer: Fix some integer type and calculation usb: gadget: fsl_qe_udc: validate endpoint index for ch9 udc usb: cdns3: Put the cdns set active part outside the spin lock media: pci: cx23885: replace BUG with error return media: tuners: qt1010: replace BUG_ON with a regular error scsi: lpfc: Abort outstanding ELS cmds when mailbox timeout error is detected media: dvb-usb-v2: gl861: Fix null-ptr-deref in
[Kernel-packages] [Bug 2038830] Re: Jammy update: v6.1.54 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2038830 Title: Jammy update: v6.1.54 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.54 upstream stable release from git://git.kernel.org/ Linux 6.1.54 drm/amd/display: Fix a bug when searching for insert_above_mpcc MIPS: Only fiddle with CHECKFLAGS if `need-compiler' kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg(). ixgbe: fix timestamp configuration code tcp: Fix bind() regression for v4-mapped-v6 non-wildcard address. tcp: Fix bind() regression for v4-mapped-v6 wildcard address. tcp: Factorise sk_family-independent comparison in inet_bind2_bucket_match(_addr_any). ipv6: Remove in6addr_any alternatives. ipv6: fix ip6_sock_set_addr_preferences() typo net: macb: fix sleep inside spinlock net: macb: Enable PTP unicast net/tls: do not free tls_rec on async operation in bpf_exec_tx_verdict() platform/mellanox: NVSW_SN2201 should depend on ACPI platform/mellanox: mlxbf-pmc: Fix reading of unprogrammed events platform/mellanox: mlxbf-pmc: Fix potential buffer overflows platform/mellanox: mlxbf-tmfifo: Drop jumbo frames platform/mellanox: mlxbf-tmfifo: Drop the Rx packet if no more descriptors kcm: Fix memory leak in error path of kcm_sendmsg() r8152: check budget for r8152_poll() net: dsa: sja1105: block FDB accesses that are concurrent with a switch reset net: dsa: sja1105: serialize sja1105_port_mcast_flood() with other FDB accesses net: dsa: sja1105: fix multicast forwarding working only for last added mdb entry net: dsa: sja1105: propagate exact error code from sja1105_dynamic_config_poll_valid() net: dsa: sja1105: hide all multicast addresses from "bridge fdb show" net:ethernet:adi:adin1110: Fix forwarding offload net: ethernet: adi: adin1110: use eth_broadcast_addr() to assign broadcast address hsr: Fix uninit-value access in fill_frame_info() net: ethernet: mtk_eth_soc: fix possible NULL pointer dereference in mtk_hwlro_get_fdir_all() net: ethernet: mvpp2_main: fix possible OOB write in mvpp2_ethtool_get_rxnfc() net: stmmac: fix handling of zero coalescing tx-usecs net/smc: use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port_add selftests: Keep symlinks, when possible kselftest/runner.sh: Propagate SIGTERM to runner child net: ipv4: fix one memleak in __inet_del_ifa() kunit: Fix wild-memory-access bug in kunit_free_suite_set() drm/amdgpu: register a dirty framebuffer callback for fbcon drm/amd/display: Remove wait while locked drm/amd/display: always switch off ODM before committing more streams perf hists browser: Fix the number of entries for 'e' key perf tools: Handle old data in PERF_RECORD_ATTR perf test shell stat_bpf_counters: Fix test on Intel perf hists browser: Fix hierarchy mode header MIPS: Fix CONFIG_CPU_DADDI_WORKAROUNDS `modules_install' regression KVM: SVM: Skip VMSA init in sev_es_init_vmcb() if pointer is NULL KVM: SVM: Set target pCPU during IRTE update if target vCPU is running KVM: nSVM: Load L1's TSC multiplier based on L1 state, not L2 state KVM: nSVM: Check instead of asserting on nested TSC scaling support KVM: SVM: Get source vCPUs from source VM for SEV-ES intrahost migration KVM: SVM: Don't inject #UD if KVM attempts to skip SEV guest insn KVM: SVM: Take and hold ir_list_lock when updating vCPU's Physical ID entry drm/amd/display: prevent potential division by zero errors drm/amd/display: enable cursor degamma for DCN3+ DRM legacy gamma mtd: rawnand: brcmnand: Fix ECC level field setting for v7.2 controller mtd: rawnand: brcmnand: Fix potential false time out warning mtd: spi-nor: Correct flags for Winbond w25q128 mtd: rawnand: brcmnand: Fix potential out-of-bounds access in oob write mtd: rawnand: brcmnand: Fix crash during the panic_write drm/mxsfb: Disable overlay plane in mxsfb_plane_overlay_atomic_disable() btrfs: use the correct superblock to compare fsid in btrfs_validate_super btrfs: zoned: re-enable metadata over-commit for zoned mode btrfs: set page extent mapped after read_folio in relocate_one_page btrfs: don't start transaction when joining with
[Kernel-packages] [Bug 2038832] Re: Jammy update: v6.1.56 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2038832 Title: Jammy update: v6.1.56 upstream stable release Status in OEM Priority Project: Fix Released Status in linux-oem-6.1 package in Ubuntu: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.56 upstream stable release from git://git.kernel.org/ Linux 6.1.56 ASoC: amd: yc: Fix a non-functional mic on Lenovo 82TL mm, memcg: reconsider kmem.limit_in_bytes deprecation memcg: drop kmem.limit_in_bytes drm/meson: fix memory leak on ->hpd_notify callback drm/amdkfd: Use gpu_offset for user queue's wptr fs: binfmt_elf_efpic: fix personality for ELF-FDPIC power: supply: ab8500: Set typing and props power: supply: rk817: Add missing module alias drm/i915/gt: Fix reservation address in ggtt_reserve_guc_top ata: libata-sata: increase PMP SRST timeout to 10s ata: libata-core: Do not register PM operations for SAS ports ata: libata-core: Fix port and device removal ata: libata-core: Fix ata_port_request_pm() locking fs/smb/client: Reset password pointer to NULL net: thunderbolt: Fix TCPv6 GSO checksum calculation bpf: Fix BTF_ID symbol generation collision in tools/ bpf: Fix BTF_ID symbol generation collision bpf: Add override check to kprobe multi link attach media: uvcvideo: Fix OOB read btrfs: properly report 0 avail for very full file systems ring-buffer: Update "shortest_full" in polling mm: memcontrol: fix GFP_NOFS recursion in memory.high enforcement mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy() mm/damon/vaddr-test: fix memory leak in damon_do_test_apply_three_regions() arm64: defconfig: remove CONFIG_COMMON_CLK_NPCM8XX=y drm/tests: Fix incorrect argument in drm_test_mm_insert_range timers: Tag (hr)timer softirq as hotplug safe Revert "SUNRPC dont update timeout value on connection reset" netfilter: nf_tables: fix kdoc warnings after gc rework sched/rt: Fix live lock between select_fallback_rq() and RT push kernel/sched: Modify initial boot task idle setup ASoC: amd: yc: Fix non-functional mic on Lenovo 82QF and 82UG i2c: i801: unregister tco_pdev in i801_probe() error path io_uring/fs: remove sqe->rw_flags checking from LINKAT ata: libata-scsi: ignore reserved bits for REPORT SUPPORTED OPERATION CODES ata: libata-scsi: link ata port and scsi device LoongArch: numa: Fix high_memory calculation LoongArch: Define relocation types for ABI v2.10 ALSA: hda: Disable power save for solving pop issue on Lenovo ThinkCentre M70q netfilter: nf_tables: disallow rule removal from chain binding nilfs2: fix potential use after free in nilfs_gccache_submit_read_data() serial: 8250_port: Check IRQ data before use Revert "tty: n_gsm: fix UAF in gsm_cleanup_mux" misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to probe mptcp: fix bogus receive window shrinkage with multiple subflows KVM: x86/mmu: Do not filter address spaces in for_each_tdp_mmu_root_yield_safe() KVM: x86/mmu: Open code leaf invalidation from mmu_notifier KVM: SVM: Fix TSC_AUX virtualization setup KVM: SVM: INTERCEPT_RDTSCP is never intercepted anyway x86/srso: Add SRSO mitigation for Hygon processors x86/sgx: Resolves SECS reclaim vs. page fault for EAUG race iommu/arm-smmu-v3: Fix soft lockup triggered by arm_smmu_mm_invalidate_range smack: Retrieve transmuting information in smack_inode_getsecurity() smack: Record transmuting in smk_transmuted nvme-pci: always return an ERR_PTR from nvme_pci_alloc_dev scsi: qla2xxx: Fix NULL pointer dereference in target mode wifi: ath11k: Don't drop tx_status when peer cannot be found nvme-pci: do not set the NUMA node of device if it has none nvme-pci: factor out a nvme_pci_alloc_dev helper nvme-pci: factor the iod mempool creation into a helper perf build: Define YYNOMEM as YYNOABORT for bison < 3.81 fbdev/sh7760fb: Depend on FB=y LoongArch: Set all reserved memblocks on Node#0 at initialization tsnep: Fix NAPI polling with budget 0 tsnep: Fix NAPI scheduling net: hsr: Add __packed to struct hsr_sup_tlv. ncsi: Propagate carrier gain/loss events to the NCSI controller
[Kernel-packages] [Bug 2039174] Re: Jammy update: v6.1.57 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2039174
Title:
Jammy update: v6.1.57 upstream stable release
Status in linux-oem-6.1 package in Ubuntu:
Fix Released
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.1.57 upstream stable release
from git://git.kernel.org/
Linux 6.1.57
xen/events: replace evtchn_rwlock with RCU
ipv6: remove one read_lock()/read_unlock() pair in rt6_check_neigh()
btrfs: file_remove_privs needs an exclusive lock in direct io write
netlink: remove the flex array from struct nlmsghdr
btrfs: fix fscrypt name leak after failure to join log transaction
btrfs: fix an error handling path in btrfs_rename()
vrf: Fix lockdep splat in output path
ipv6: remove nexthop_fib6_nh_bh()
parisc: Restore __ldcw_align for PA-RISC 2.0 processors
ksmbd: fix uaf in smb20_oplock_break_ack
ksmbd: fix race condition between session lookup and expire
x86/sev: Use the GHCB protocol when available for SNP CPUID requests
RDMA/mlx5: Fix NULL string error
RDMA/mlx5: Fix mutex unlocking on error flow for steering anchor creation
RDMA/siw: Fix connection failure handling
RDMA/srp: Do not call scsi_done() from srp_abort()
RDMA/uverbs: Fix typo of sizeof argument
RDMA/cma: Fix truncation compilation warning in make_cma_ports
RDMA/cma: Initialize ib_sa_multicast structure to 0 when join
gpio: pxa: disable pinctrl calls for MMP_GPIO
gpio: aspeed: fix the GPIO number passed to pinctrl_gpio_set_config()
IB/mlx4: Fix the size of a buffer in add_port_entries()
of: dynamic: Fix potential memory leak in of_changeset_action()
RDMA/core: Require admin capabilities to set system parameters
dm zoned: free dmz->ddev array in dmz_put_zoned_devices
parisc: Fix crash with nr_cpus=1 option
smb: use kernel_connect() and kernel_bind()
intel_idle: add Emerald Rapids Xeon support
HID: intel-ish-hid: ipc: Disable and reenable ACPI GPE bit
HID: sony: remove duplicate NULL check before calling usb_free_urb()
netlink: annotate data-races around sk->sk_err
netlink: Fix potential skb memleak in netlink_ack
netlink: split up copies in the ack construction
sctp: update hb timer immediately after users change hb_interval
sctp: update transport state when processing a dupcook packet
tcp: fix delayed ACKs for MSS boundary condition
tcp: fix quick-ack counting to count actual ACKs of new data
tipc: fix a potential deadlock on >lock
net: stmmac: dwmac-stm32: fix resume on STM32 MCU
ipv4: Set offload_failed flag in fibmatch results
netfilter: nf_tables: nft_set_rbtree: fix spurious insertion failure
netfilter: nf_tables: Deduplicate nft_register_obj audit logs
selftests: netfilter: Extend nft_audit.sh
selftests: netfilter: Test nf_tables audit logging
netfilter: handle the connecting collision properly in nf_conntrack_proto_sctp
ibmveth: Remove condition to recompute TCP header checksum.
net: ethernet: ti: am65-cpsw: Fix error code in am65_cpsw_nuss_init_tx_chns()
net: nfc: llcp: Add lock when modifying device list
net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg
ipv6: tcp: add a missing nf_reset_ct() in 3WHS handling
net: dsa: mv88e6xxx: Avoid EEPROM timeout when EEPROM is absent
ptp: ocp: Fix error handling in ptp_ocp_device_init
ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data()
neighbour: fix data-races around n->output
neighbour: switch to standard rcu, instead of rcu_bh
neighbour: annotate lockless accesses to n->nud_state
bpf: Add BPF_FIB_LOOKUP_SKIP_NEIGH for bpf_fib_lookup
net: fix possible store tearing in neigh_periodic_work()
modpost: add missing else to the "of" check
bpf, sockmap: Reject sk_msg egress redirects to non-TCP sockets
bpf, sockmap: Do not inc copied_seq when PEEK flag set
bpf: tcp_read_skb needs to pop skb regardless of seq
NFSv4: Fix a nfs4_state_manager() race
ima: rework CONFIG_IMA dependency block
scsi: target: core: Fix deadlock due to recursive locking
ima: Finish deprecation of IMA_TRUSTED_KEYRING Kconfig
regulator/core: regulator_register: set device->class earlier
iommu/mediatek: Fix share pgtable for iova over 4GB
perf/x86/amd: Do not WARN() on every IRQ
wifi: mac80211: fix potential key use-after-free
regmap:
[Kernel-packages] [Bug 2051835] Re: [24.04 FEAT] Memory hotplug vmem pages
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2051835 Title: [24.04 FEAT] Memory hotplug vmem pages 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 2052961] Re: Error: OCI runtime error: crun: chmod : Operation not supported
Is there an ETA for a new package with the bugfix applied? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2052961 Title: Error: OCI runtime error: crun: chmod : Operation not supported Status in linux package in Ubuntu: Confirmed Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Bug description: There appears to be a regression due to a "change in the kernel" in which, as of "commit 5d1f903f75a80daa4dfb3d84e114ec8ecbf29956 in the kernel, present in a release since Linux 6.6 doesn't allow anymore to change the mode of a symlink, so just ignore the failure." Quote source: https://github.com/containers/crun/pull/1309#issue-1908555328 A fix for crun was committed as of v1.9.1, and I believe should be backported: https://github.com/containers/crun/commit/be16ee75ff8574698250352302e9d5496d888d69 I am attaching the apt/history.log file, which I believe reveals the kernel update that happened since February 8th that triggered the regression. This has been reproducible for me by using podman in combination with the "kind" tool (https://github.com/kubernetes- sigs/kind/releases/tag/v0.21.0 in this case) to attempt to start a Kubernetes cluster within a container. By running "kind create cluster" it is using the container image "kindest/node:v1.29.1" which triggers the error: "Error: OCI runtime error: crun: chmod `run/shm`: Operation not supported" ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: crun 1.8.5-1 ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 12 12:07:09 2024 InstallationDate: Installed on 2022-09-19 (511 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=screen-256color XDG_RUNTIME_DIR= SourcePackage: crun UpgradeStatus: Upgraded to mantic on 2023-11-07 (98 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052961/+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 2052961] Re: Error: OCI runtime error: crun: chmod : Operation not supported
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2052961 Title: Error: OCI runtime error: crun: chmod : Operation not supported Status in linux package in Ubuntu: Confirmed Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Bug description: There appears to be a regression due to a "change in the kernel" in which, as of "commit 5d1f903f75a80daa4dfb3d84e114ec8ecbf29956 in the kernel, present in a release since Linux 6.6 doesn't allow anymore to change the mode of a symlink, so just ignore the failure." Quote source: https://github.com/containers/crun/pull/1309#issue-1908555328 A fix for crun was committed as of v1.9.1, and I believe should be backported: https://github.com/containers/crun/commit/be16ee75ff8574698250352302e9d5496d888d69 I am attaching the apt/history.log file, which I believe reveals the kernel update that happened since February 8th that triggered the regression. This has been reproducible for me by using podman in combination with the "kind" tool (https://github.com/kubernetes- sigs/kind/releases/tag/v0.21.0 in this case) to attempt to start a Kubernetes cluster within a container. By running "kind create cluster" it is using the container image "kindest/node:v1.29.1" which triggers the error: "Error: OCI runtime error: crun: chmod `run/shm`: Operation not supported" ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: crun 1.8.5-1 ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 12 12:07:09 2024 InstallationDate: Installed on 2022-09-19 (511 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=screen-256color XDG_RUNTIME_DIR= SourcePackage: crun UpgradeStatus: Upgraded to mantic on 2023-11-07 (98 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052961/+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 2054121] Re: Random Freezing
Got it. Testing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
Incomplete
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006056] Re: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: trying to overwrite '/lib/systemd/system/kvm_stat.service', which is also in package lin
it shouldn't have built that package, but oem-6.1 is about to EOL so it won't get this fixed ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2006056 Title: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: trying to overwrite '/lib/systemd/system/kvm_stat.service', which is also in package linux-tools-host 5.15.0-58.64 Status in linux-oem-6.1 package in Ubuntu: Won't Fix Bug description: Faliure to install. trying to overwrite file in linux-ttols-host ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-oem-6.1-tools-host (not installed) ProcVersionSignature: Ubuntu 5.19.0-28.29~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Feb 5 11:40:05 2023 DuplicateSignature: package:linux-oem-6.1-tools-host:(not installed) Unpacking linux-oem-6.0-tools-host (6.0.0-1010.10) ... dpkg: error processing archive /tmp/apt-dpkg-install-MljDYl/15-linux-oem-6.0-tools-host_6.0.0-1010.10_all.deb (--unpack): trying to overwrite '/lib/systemd/system/kvm_stat.service', which is also in package linux-tools-host 5.15.0-58.64 ErrorMessage: trying to overwrite '/lib/systemd/system/kvm_stat.service', which is also in package linux-tools-host 5.15.0-58.64 InstallationDate: Installed on 2022-12-22 (45 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-oem-6.1 Title: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: trying to overwrite '/lib/systemd/system/kvm_stat.service', which is also in package linux-tools-host 5.15.0-58.64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2006056/+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 2052835] Re: Error running program on cifs filesystem
Hi, Is there any progress on this? We're experiencing the exact same issue. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2052835 Title: Error running program on cifs filesystem Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: Hi When I try and run a shell script which is on a cifs mounted system I get an error. This is on a 22.04 system - Linux bicr-compression 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux nkhan@bicr-compression:/mnt/cephfs/home/users/nkhan$ ~/data/NKHAN/linux-home/date.sh bash: /nfs/home/users/nkhan/data/NKHAN/linux-home/date.sh: /usr/bin/bash: bad interpreter: Input/output error In the kernel log there is: Feb 9 20:10:01 bicr-compression kernel: [ 1421.014745] [ cut here ] Feb 9 20:10:01 bicr-compression kernel: [ 1421.014761] WARNING: CPU: 16 PID: 5834 at fs/smb/client/file.c:3341 cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.014849] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 nfsv3 nfs_acl nfs lockd grace fscache netfs vsock_loopback vmw_vsock_virtio_transport_common intel_rapl_msr vmw_vsock_vmci_transport intel_rapl_common vsock intel_uncore_frequency_common binfmt_misc coretemp rapl nls_iso8859_1 vmw_balloon input_leds joydev serio_raw vmw_vmci mac_hid sch_fq_codel msr parport_pc auth_rpcgss ppdev lp parport efi_pstore sunrpc ip_tables x_tables autofs4 vmwgfx crct10dif_pclmul drm_ttm_helper crc32_pclmul polyval_clmulni ttm polyval_generic ghash_clmulni_intel drm_kms_helper aesni_intel crypto_simd mptspi mptscsih cryptd mptbase ahci drm psmouse libahci vmxnet3 scsi_transport_spi i2c_piix4 pata_acpi Feb 9 20:10:01 bicr-compression kernel: [ 1421.014910] CPU: 16 PID: 5834 Comm: bash Tainted: GW 6.5.0-17-generic #17~22.04.1-Ubuntu Feb 9 20:10:01 bicr-compression kernel: [ 1421.014914] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/30/2014 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014916] RIP: 0010:cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.014969] Code: c0 48 29 c2 75 c4 41 89 0b 4c 89 c0 48 8b 5d f8 c9 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 45 31 d2 45 31 db c3 cc cc cc cc <0f> 0b 45 31 c0 4c 89 c0 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014971] RSP: 0018:b4ee07117b90 EFLAGS: 00010297 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014974] RAX: 9de487836418 RBX: 9de4878363c0 RCX: Feb 9 20:10:01 bicr-compression kernel: [ 1421.014975] RDX: b4ee07117bdc RSI: 0100 RDI: 9de487836418 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014977] RBP: b4ee07117c18 R08: 0100 R09: Feb 9 20:10:01 bicr-compression kernel: [ 1421.014978] R10: R11: R12: 9de48f998000 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014979] R13: 9de48f982400 R14: 0100 R15: 9de49ba32000 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014981] FS: 7f8f2ae67740() GS:9dfb5e20() knlGS: Feb 9 20:10:01 bicr-compression kernel: [ 1421.014982] CS: 0010 DS: ES: CR0: 80050033 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014984] CR2: 558a1cb1bf98 CR3: 0001abfd4001 CR4: 003706e0 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015030] DR0: DR1: DR2: Feb 9 20:10:01 bicr-compression kernel: [ 1421.015033] DR3: DR6: fffe0ff0 DR7: 0400 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015034] Call Trace: Feb 9 20:10:01 bicr-compression kernel: [ 1421.015036] Feb 9 20:10:01 bicr-compression kernel: [ 1421.015040] ? show_regs+0x6d/0x80 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015116] ? __warn+0x89/0x160 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015127] ? cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.015181] ? report_bug+0x17e/0x1b0 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015198] ? handle_bug+0x46/0x90 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015212] ? exc_invalid_op+0x18/0x80 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015215] ? asm_exc_invalid_op+0x1b/0x20 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015226] ? cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.015277] ? cifs_send_async_read+0x11f/0x510 [cifs] Feb 9 20:10:01 bicr-compression
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle-6.5/6.5.0.1020.20~22.04.1)
All autopkgtests for the newly accepted linux-meta-oracle-6.5 (6.5.0.1020.20~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/2.1.5-1ubuntu6~22.04.3 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-oracle-6.5 [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 1970069] Re: Annoying boot messages interfering with splash screen
Looking at the remaining "add drm modules (only if MODULES=dep)" section: This logic should moved to hooks/framebuffer as well. -- 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 2055686] Re: Drop ABI checks from kernel build
This bug is awaiting verification that the linux- azure-4.15/4.15.0-1175.190 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- azure-4.15' to 'verification-done-bionic-linux-azure-4.15'. If the problem still exists, change the tag 'verification-needed-bionic-linux- azure-4.15' to 'verification-failed-bionic-linux-azure-4.15'. 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-azure-4.15-v2 verification-needed-bionic-linux-azure-4.15 -- 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 2055686] Re: Drop ABI checks from kernel build
This bug is awaiting verification that the linux-fips/4.4.0-1099.106 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-fips' to 'verification-done- xenial-linux-fips'. If the problem still exists, change the tag 'verification-needed-xenial-linux-fips' to 'verification-failed-xenial- linux-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-xenial-linux-fips-v2 verification-needed-xenial-linux-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/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 2058237] [NEW] Include support for Intel E830 QSFP56/SFP NIC devices on Ubuntu 24.04
Private bug reported: Include support for Intel E830 QSFP56/SFP NIC devices on Ubuntu 24.04 The PCI Device ID details: Vendor IDDevice IDSubVendor IDSubSystem ID 808612D2 8086 0002 808612D3 8086 0001 The PCI device IDs for the NIC devices exist upstream. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/ethernet/intel/ice/ice_devids.h?h=v6.7-rc5#n22 The NICs are getting supported on upcoming Dell 17G platforms. Hence requesting you to add support for this card in Ubuntu 24.04 GA ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private ** Description changed: Include support for Intel E830 QSFP56/SFP NIC devices on Ubuntu 24.04 + + The PCI Device ID details: + + Vendor IDDevice IDSubVendor IDSubSystem ID + 808612D2 8086 0002 + 808612D3 8086 0001 + + The PCI device IDs for the NIC devices exist upstream. + + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/ethernet/intel/ice/ice_devids.h?h=v6.7-rc5#n22 + + The NICs are getting supported on upcoming Dell 17G platforms. Hence + requesting you to add support for this card in Ubuntu 24.04 GA -- 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/2058237 Title: Include support for Intel E830 QSFP56/SFP NIC devices on Ubuntu 24.04 Status in linux package in Ubuntu: New Bug description: Include support for Intel E830 QSFP56/SFP NIC devices on Ubuntu 24.04 The PCI Device ID details: Vendor IDDevice IDSubVendor IDSubSystem ID 808612D2 8086 0002 808612D3 8086 0001 The PCI device IDs for the NIC devices exist upstream. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/ethernet/intel/ice/ice_devids.h?h=v6.7-rc5#n22 The NICs are getting supported on upcoming Dell 17G platforms. Hence requesting you to add support for this card in Ubuntu 24.04 GA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058237/+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 2055686] Re: Drop ABI checks from kernel build
This bug is awaiting verification that the linux- oracle/4.15.0-1129.140~16.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-xenial-linux- oracle' to 'verification-done-xenial-linux-oracle'. If the problem still exists, change the tag 'verification-needed-xenial-linux-oracle' to 'verification-failed-xenial-linux-oracle'. 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-oracle-v2 verification-needed-xenial-linux-oracle -- 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 2055686] Re: Drop ABI checks from kernel build
This bug is awaiting verification that the linux- gcp-4.15/4.15.0-1160.177 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-4.15' to 'verification-done-bionic-linux-gcp-4.15'. If the problem still exists, change the tag 'verification-needed-bionic-linux-gcp-4.15' to 'verification-failed-bionic-linux-gcp-4.15'. 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-4.15-v2 verification-needed-bionic-linux-gcp-4.15 -- 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 2058236] [NEW] Enable support for Dell storage controller PERC 13 in Ubuntu 24.04
Private bug reported: Enable support for Dell storage controller PERC 13 in Ubuntu 24.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private -- 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/2058236 Title: Enable support for Dell storage controller PERC 13 in Ubuntu 24.04 Status in linux package in Ubuntu: New Bug description: Enable support for Dell storage controller PERC 13 in Ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058236/+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
** Changed in: initramfs-tools (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1786013] Autopkgtest regression report (linux-meta-hwe-6.5/6.5.0.27.28~22.04.1)
All autopkgtests for the newly accepted linux-meta-hwe-6.5 (6.5.0.27.28~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: systemd/249.11-0ubuntu3.12 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-hwe-6.5 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-lowlatency/5.15.0.102.98)
All autopkgtests for the newly accepted linux-meta-lowlatency (5.15.0.102.98) for jammy have finished running. The following regressions have been reported in tests triggered by the package: linux-lowlatency/5.15.0-102.112 (amd64, arm64) systemd/249.11-0ubuntu3.12 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-lowlatency [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-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 2055686] Re: Drop ABI checks from kernel build
This bug is awaiting verification that the linux-aws- hwe/4.15.0-1166.179~16.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-xenial-linux-aws- hwe' to 'verification-done-xenial-linux-aws-hwe'. If the problem still exists, change the tag 'verification-needed-xenial-linux-aws-hwe' to 'verification-failed-xenial-linux-aws-hwe'. 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-hwe-v2 verification-needed-xenial-linux-aws-hwe -- 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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
I ran into the same issue here.
It's the same symptom. I'm running Noble with ZFS on root and kernel
6.8.
Setting up tomcat10-common (10.1.16-1) ...
Setting up tomcat10 (10.1.16-1) ...
Creating group 'tomcat' with GID 994.
Creating user 'tomcat' (Apache Tomcat) with UID 994 and GID 994.
Failed to backup /etc/group: Operation not supported
dpkg: error processing package tomcat10 (--configure):
installed tomcat10 package post-installation script subprocess returned error
exit status 1
Processing triggers for rsyslog (8.2312.0-3ubuntu3) ...
Processing triggers for libc-bin (2.39-0ubuntu2) ...
Errors were encountered while processing:
tomcat10
E: Sub-process /usr/bin/dpkg returned an error code (1)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
New
Status in zfs-linux package in Ubuntu:
Confirmed
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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
It seems unlikely my all-in-one kernel fix will be accepted upstream. While I could propose it as an Ubuntu patch, another alternative is to just let the linux task track bug 2049390 (Fix Committed). Then most people will only need the above Plymouth patch to get a complete fix. The remaining tasks beyond that are: initramfs-tools: Required to keep the initrd size under control after the Plymouth fix is released. systemd: Would still be nice to implement a redundant fix to suppress the "clean" message. That would fix bug 1914409 and when combined with loglevel=3, would also prevent this bug 1970069. ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- 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: In Progress 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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zfs-linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
New
Status in zfs-linux package in Ubuntu:
Confirmed
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2049390] Re: Please change CONFIG_CONSOLE_LOGLEVEL_QUIET to 3
In proposed: https://launchpad.net/ubuntu/+source/linux/6.8.0-19.19 ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049390 Title: Please change CONFIG_CONSOLE_LOGLEVEL_QUIET to 3 Status in linux package in Ubuntu: Fix Committed Bug description: The Ubuntu Desktop boot isn't flickerfree today as reported on bug #1970069 , one of the reason is that kernel error messages are often being logged and not filtered out by our default loglevel (one example with usb messages on https://launchpadlibrarian.net/598152686/20220422_014058.jpg) Fedora is using CONFIG_CONSOLE_LOGLEVEL_QUIET=3 (instead of 4 which is the default), they change it 5 years ago (https://src.fedoraproject.org/rpms/kernel/c/838818e5), the rational is in the commit message that added the configuration option to the kernel > This for example will allow distros which want quiet to really mean quiet to set > CONSOLE_LOGLEVEL_QUIET so that only messages with a higher severity then KERN_ERR (CRIT, ALERT, EMERG) > get printed, avoiding an endless game of whack-a-mole silencing harmless error messages. ' Could we also get the default change to 3 in Ubuntu? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049390/+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 2058226] [NEW] iwlwifi repeatedly logging microcode crashes
Public bug reported: 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 | umac branchlink1 Mar 15 12:03:14 waplinuc kernel: [1203239.253401] iwlwifi :00:14.3: 0x804539C6 | umac branchlink2 Mar 15 12:03:14 waplinuc kernel: [1203239.253402] iwlwifi :00:14.3: 0x8047065A | umac interruptlink1 Mar 15 12:03:14 waplinuc kernel: [1203239.253403] iwlwifi :00:14.3: 0x8047065A | umac interruptlink2 Mar 15 12:03:14 waplinuc kernel: [1203239.253405] iwlwifi
[Kernel-packages] [Bug 2058224] [NEW] Noble update: v6.8.1 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.8.1 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058224 Title: Noble update: v6.8.1 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: Confirmed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.8.1 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058224/+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
Here's a fix for plymouth/noble. The source is in: https://salsa.debian.org/ubuntu-dev-team/plymouth/-/commits/ubuntu/latest We skipped ubuntu5 because that technically existed in bug 2054769 for 10 days already. Also note this will cause some temporary initrd bloat while the initramfs-tools change is pending in comment #90. ** Patch added: "plymouth_24.004.60-1ubuntu6.debdiff" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1970069/+attachment/5756732/+files/plymouth_24.004.60-1ubuntu6.debdiff -- 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: In Progress Status in linux package in Ubuntu: In Progress 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 2057792] Re: Certains jeux crashent liés à un vm_max_map_count trop faible
** Summary changed: - Some Games are crashing linked to a vm_max_map_count too low + Certains jeux crashent liés à un vm_max_map_count trop faible -- 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: Certains jeux crashent liés à un vm_max_map_count trop faible 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 2056418] Re: Fix headphone mic detection issue on ALC897
** Changed in: linux (Ubuntu Noble) Status: In Progress => Invalid ** Changed in: hwe-next Status: New => In Progress -- 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 2056762] Re: ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Mantic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2056762
Title:
ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Mantic:
Confirmed
Bug description:
We updated a number of (amd64) machines from linux-
image-6.5.0-21-generic (6.5.0-21.21~22.04.1) to linux-
image-6.5.0-25-generic (6.5.0-25.25~22.04.1), and this caused
ThreadSanitizer-instrumented programs to immediately exit with an
error similar to:
FATAL: ThreadSanitizer: unexpected memory mapping
0x5c4dc2bcd000-0x5c4dc2bed000
Reverting the kernel back to 6.5.0-21.21~22.04.1 and rebooting makes
the same executables work again.
There are a few older bugs including
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67308 and
https://github.com/google/sanitizers/issues/503 but these are from
~2015, and about gcc 7 and linux 4.1 so it does not seem to be the
same problem.
A very small program, lifted from
https://github.com/google/sanitizers/wiki/ThreadSanitizerCppManual can
be used to show the problem:
$ cat simple-race.c
#include
#include
int Global;
void *Thread1(void *x) {
Global++;
return NULL;
}
void *Thread2(void *x) {
Global--;
return NULL;
}
int main() {
pthread_t t[2];
pthread_create([0], NULL, Thread1, NULL);
pthread_create([1], NULL, Thread2, NULL);
pthread_join(t[0], NULL);
pthread_join(t[1], NULL);
}
$ cc -fsanitize=thread -fPIE -pie -g simple-race.c -o simple-race
$ ./simple-race
FATAL: ThreadSanitizer: unexpected memory mapping
0x5d161227c000-0x5d161227d000
$ uname -a
Linux buildhost 6.5.0-25-generic #25~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue
Feb 20 16:09:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
When running that exact same binary, on the same machine, but with
linux 6.5.0-21:
$ ./simple-race
==
WARNING: ThreadSanitizer: data race (pid=19373)
Read of size 4 at 0x560964a2d014 by thread T2:
#0 Thread2 /home/lxc-unpriv/simple-race.c:12 (simple-race+0x12d1)
Previous write of size 4 at 0x560964a2d014 by thread T1:
#0 Thread1 /home/lxc-unpriv/simple-race.c:7 (simple-race+0x128c)
Location is global 'Global' of size 4 at 0x560964a2d014 (simple-
race+0x4014)
Thread T2 (tid=19376, running) created by main thread at:
#0 pthread_create
../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:969
(libtsan.so.0+0x605b8)
#1 main /home/lxc-unpriv/simple-race.c:19 (simple-race+0x1368)
Thread T1 (tid=19375, finished) created by main thread at:
#0 pthread_create
../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:969
(libtsan.so.0+0x605b8)
#1 main /home/lxc-unpriv/simple-race.c:18 (simple-race+0x1347)
SUMMARY: ThreadSanitizer: data race /home/lxc-unpriv/simple-race.c:12 in
Thread2
==
ThreadSanitizer: reported 1 warnings
$ uname -a
Linux buildhost 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri
Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056762/+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 2056762] Re: ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2056762
Title:
ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Mantic:
Confirmed
Bug description:
We updated a number of (amd64) machines from linux-
image-6.5.0-21-generic (6.5.0-21.21~22.04.1) to linux-
image-6.5.0-25-generic (6.5.0-25.25~22.04.1), and this caused
ThreadSanitizer-instrumented programs to immediately exit with an
error similar to:
FATAL: ThreadSanitizer: unexpected memory mapping
0x5c4dc2bcd000-0x5c4dc2bed000
Reverting the kernel back to 6.5.0-21.21~22.04.1 and rebooting makes
the same executables work again.
There are a few older bugs including
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67308 and
https://github.com/google/sanitizers/issues/503 but these are from
~2015, and about gcc 7 and linux 4.1 so it does not seem to be the
same problem.
A very small program, lifted from
https://github.com/google/sanitizers/wiki/ThreadSanitizerCppManual can
be used to show the problem:
$ cat simple-race.c
#include
#include
int Global;
void *Thread1(void *x) {
Global++;
return NULL;
}
void *Thread2(void *x) {
Global--;
return NULL;
}
int main() {
pthread_t t[2];
pthread_create([0], NULL, Thread1, NULL);
pthread_create([1], NULL, Thread2, NULL);
pthread_join(t[0], NULL);
pthread_join(t[1], NULL);
}
$ cc -fsanitize=thread -fPIE -pie -g simple-race.c -o simple-race
$ ./simple-race
FATAL: ThreadSanitizer: unexpected memory mapping
0x5d161227c000-0x5d161227d000
$ uname -a
Linux buildhost 6.5.0-25-generic #25~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue
Feb 20 16:09:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
When running that exact same binary, on the same machine, but with
linux 6.5.0-21:
$ ./simple-race
==
WARNING: ThreadSanitizer: data race (pid=19373)
Read of size 4 at 0x560964a2d014 by thread T2:
#0 Thread2 /home/lxc-unpriv/simple-race.c:12 (simple-race+0x12d1)
Previous write of size 4 at 0x560964a2d014 by thread T1:
#0 Thread1 /home/lxc-unpriv/simple-race.c:7 (simple-race+0x128c)
Location is global 'Global' of size 4 at 0x560964a2d014 (simple-
race+0x4014)
Thread T2 (tid=19376, running) created by main thread at:
#0 pthread_create
../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:969
(libtsan.so.0+0x605b8)
#1 main /home/lxc-unpriv/simple-race.c:19 (simple-race+0x1368)
Thread T1 (tid=19375, finished) created by main thread at:
#0 pthread_create
../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:969
(libtsan.so.0+0x605b8)
#1 main /home/lxc-unpriv/simple-race.c:18 (simple-race+0x1347)
SUMMARY: ThreadSanitizer: data race /home/lxc-unpriv/simple-race.c:12 in
Thread2
==
ThreadSanitizer: reported 1 warnings
$ uname -a
Linux buildhost 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri
Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056762/+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
As now this could be something related to hardware, let me log some cpu info: $ sudo lshw -c cpu -- *-cpu description: CPU product: Intel(R) Core(TM) i9-14900K vendor: Intel Corp. physical id: 4f bus info: cpu@0 version: 6.183.1 serial: To Be Filled By O.E.M. slot: U3E1 size: 5700MHz capacity: 5700MHz width: 64 bits clock: 100MHz capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp x86-64 constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect user_shstk avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi vnmi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities cpufreq configuration: cores=24 enabledcores=24 microcode=290 threads=32 -- 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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
** Changed in: zfs
Status: Unknown => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
New
Status in zfs-linux package in Ubuntu:
New
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 2058208] Re: OpenGL renderer AMD defaults to Intel
Related: https://github.com/canonical/checkbox/issues/889 ** Changed in: linux-signed-oem-6.5 (Ubuntu) Status: New => Invalid ** Bug watch added: github.com/canonical/checkbox/issues #889 https://github.com/canonical/checkbox/issues/889 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058208 Title: OpenGL renderer AMD defaults to Intel Status in linux-signed-oem-6.5 package in Ubuntu: Invalid Bug description: Checkbox job " com.canonical.certification::graphics/2_valid_opengl_renderer_PCI_ID_0x743f" fails with error: ``` Setting up PRIME GPU offloading for AMD discrete GPU OpenGL renderer string: Mesa Intel(R) Graphics (RPL-S) ERROR: renderer is Intel when DRI_PRIME=1 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-1016-oem 6.5.0-1016.17 ProcVersionSignature: Ubuntu 6.5.0-1016.17-oem 6.5.13 Uname: Linux 6.5.0-1016-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Mar 18 14:46:23 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-abra+X102 InstallationDate: Installed on 2024-03-15 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 SourcePackage: linux-signed-oem-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-6.5/+bug/2058208/+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
Enable -proposed2 and install linux-oem-6.5/6.5.0-1018.19 on REX13-PV- SKU3_202402-33490 and REX14-PV-SKU7_202402-33495. The LEDs work as expected. ** 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/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 Committed 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 2058208] [NEW] OpenGL renderer AMD defaults to Intel
Public bug reported: Checkbox job " com.canonical.certification::graphics/2_valid_opengl_renderer_PCI_ID_0x743f" fails with error: ``` Setting up PRIME GPU offloading for AMD discrete GPU OpenGL renderer string: Mesa Intel(R) Graphics (RPL-S) ERROR: renderer is Intel when DRI_PRIME=1 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-1016-oem 6.5.0-1016.17 ProcVersionSignature: Ubuntu 6.5.0-1016.17-oem 6.5.13 Uname: Linux 6.5.0-1016-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Mar 18 14:46:23 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-abra+X102 InstallationDate: Installed on 2024-03-15 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 SourcePackage: linux-signed-oem-6.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cert-sru jammy regression-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058208 Title: OpenGL renderer AMD defaults to Intel Status in linux-signed-oem-6.5 package in Ubuntu: New Bug description: Checkbox job " com.canonical.certification::graphics/2_valid_opengl_renderer_PCI_ID_0x743f" fails with error: ``` Setting up PRIME GPU offloading for AMD discrete GPU OpenGL renderer string: Mesa Intel(R) Graphics (RPL-S) ERROR: renderer is Intel when DRI_PRIME=1 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-1016-oem 6.5.0-1016.17 ProcVersionSignature: Ubuntu 6.5.0-1016.17-oem 6.5.13 Uname: Linux 6.5.0-1016-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Mar 18 14:46:23 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-abra+X102 InstallationDate: Installed on 2024-03-15 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 SourcePackage: linux-signed-oem-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-6.5/+bug/2058208/+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
** 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/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 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: 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 and works well [Where problems could occur] Hard to tell, but ODM and us did some tests and confirmed the WWAN doesn't keep working during 1900 reboot stress test. = At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias:
[Kernel-packages] [Bug 2057430] Re: The screen brightness is unable to adjust on BOE panel DPN#R6FD8
** 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/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 Committed 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
