FEDORA-2024-05229b82f6 — bugfix update for kernel

stable

kernel-6.9.7-200.fc40

FEDORA-2024-05229b82f6 created by acaringi 3 months ago for Fedora 40

The 6.9.7 stable kernel update contains a number of important fixes across the tree.

Reboot Required

After installing this update it is required that you reboot your system to ensure the changes supplied by this update are applied properly.

How to install

Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:

sudo dnf upgrade --refresh --advisory=FEDORA-2024-05229b82f6

This update has been submitted for testing by acaringi.

3 months ago

This update's test gating status has been changed to 'waiting'.

3 months ago

This update's test gating status has been changed to 'failed'.

3 months ago

This update's test gating status has been changed to 'waiting'.

3 months ago

bretth commented & provided feedback 3 months ago

karma

Default & performance test pass (KVM)

Test Case kernel regression

This update's test gating status has been changed to 'passed'.

3 months ago

valdyn commented & provided feedback 3 months ago

karma

No issues yet running on Xeon W-2225 + Arc A380.

Test Case kernel regression

nixuser commented & provided feedback 3 months ago

karma

Working for me both in a VirtualBox VM and on bare metal.

Dell Precision T5610 2 x Intel(R) Xeon(R) CPU E5-2603 v2 @ 1.80GHz (8 cores total) NVIDIA Corporation GK104 [GeForce GTX 760] (rev a1)

Intel NUC NUC13ANHi7 (NUC13ANHi7000) (rev N11225-207) 1 x 13th Gen Intel(R) Core(TM) i7-1360P Intel Corporation Raptor Lake-P [Iris Xe Graphics] (rev 04)

Test Case kernel regression

geraldosimiao commented & provided feedback 3 months ago

karma

Working fine on baremetal

Acer Aspire Intel® Core™ i7-3632QM CPU @ 2.20GHz         
Graphics Processor: Mesa DRI Intel® HD Graphics 4000. driver: i915 v: kernel arch: Gen-7          
wi-fi: Qualcomm Atheros AR9485 Wireless Network. Adapter vendor: Lite-On. driver: ath9k v: kernel.

kernel tests PASSED

Test Case kernel regression

markec provided feedback 3 months ago

karma

imabug provided feedback 3 months ago

karma

farribeiro provided feedback 3 months ago

karma

Test Case kernel regression

itrymybest80 commented & provided feedback 3 months ago

karma

Default regression test pass, but performance won't run; works in general.

anotheruser provided feedback 3 months ago

karma

Test Case kernel regression

boxjellyfish commented & provided feedback 3 months ago

karma

Default tests passed. AMD Ryzen 4500U using iGPU (Vega 6)

Test Case kernel regression

js314592 provided feedback 3 months ago

karma

g6avk commented & provided feedback 3 months ago

karma

Works for me. The enabled Default and Performance tests pass OK (manually uploaded the results)
Work Station, Asus prime mobo - Ryzen5 5600g/AMDGPU 400 Series Chipset, (UEFI) Secure boot, SSD's > RAID1 (ext4) running Plasma DE.

Test Case kernel regression

This update has been pushed to testing.

3 months ago

This update can be pushed to stable now if the maintainer wishes

3 months ago

bojan commented & provided feedback 3 months ago

karma

Works.

abcdefh commented & provided feedback 3 months ago

karma

commit 278c0efbdbd2029e9532a4ebea36d25c88a17dcb "thermal: core: Change PM notifier priority to the minimum", fixes https://bugzilla.kernel.org/show_bug.cgi?id=218881 Bug 218881 - After "Resume thermal zones asynchronously" commit: Wrong Battery Reading after Wake from S3 Sleep - Lenovo Thinkpad P1 Gen2

Now battery information reported properly after resume from Suspend.

Everything works normally.

Test Case kernel regression

johnh99 commented & provided feedback 3 months ago

karma

Works well here. Ryzen 3700x, Rog Strix B550-F, Nvidia from rpmfusion.

Test Case kernel regression

valdyn commented & provided feedback 3 months ago

karma

Works Ryzen 5600X + RX 7800 XT

Test Case kernel regression

leejm516 commented & provided feedback 3 months ago

karma

Works but failed kernel tests. Log submitted.

System:
  Host: lggram-fedora Kernel: 6.9.7-200.fc40.x86_64 arch: x86_64 bits: 64
  Desktop: GNOME v: 46.2 Distro: Fedora Linux 40 (Workstation Edition)
Machine:
  Type: Laptop System: LG product: 14ZD950-GX58K v: 0.1
    serial: <superuser required>
  Mobo: LG model: White Tip Mountain v: FAB3 serial: <superuser required>
    UEFI: Phoenix v: 14Z950FN X64 date: 12/17/2015
Memory:
  System RAM: total: 8 GiB available: 7.66 GiB used: 2.35 GiB (30.7%)
  Array-1: capacity: 8 GiB slots: 1 modules: 1 EC: None
  Device-1: ChannelA-DIMM0 type: DDR3 size: 8 GiB speed: 1600 MT/s
CPU:
  Info: dual core model: Intel Core i5-5200U bits: 64 type: MT MCP cache:
    L2: 512 KiB
  Speed (MHz): avg: 1506 min/max: 500/2700 cores: 1: 500 2: 500 3: 2694
    4: 2332

Test Case kernel regression

pawef9 provided feedback 3 months ago

karma

eifr0980 provided feedback 3 months ago

karma

pampelmuse commented & provided feedback 3 months ago

karma

Works for me.

Test Case kernel regression

ibims provided feedback 3 months ago

karma

Test Case kernel regression

py0xc3 commented & provided feedback 3 months ago

karma

Works fine in KVM/QEMU with cpu-passthrough (Ryzen 7 PRO 6850U). F40 KDE Spin with SELinux confined user account, up to date with testing repos enabled. Tainted = 0. Experience as expected. Regression pass.

Test Case kernel regression

steubens commented & provided feedback 2 months ago

karma

battery charge limit from lg-laptop stopped working

Handle 0x001D, DMI type 2, 15 bytes Base Board Information Manufacturer: LG Electronics Product Name: 14Z90Q Version: FAB1 Serial Number: <snip>14Z90Q-K.AAB7U1

markec commented 2 months ago

hm, now when you mention it it does seems to constantly charge here as well on T14s gen4 / AMD

frantisekz commented & provided feedback 2 months ago

karma

Works fine on Lenovo ThinkPad P1 Gen 2

leejm516 commented 2 months ago

Battery charge limit is not a problem in my LG laptop (GNOME). But I found that battery charge limit is reset upon every booting in another ASUS laptop (KDE). Reverting kernel back to 6.9.4 did not solve the problem... so it is possible that this issue might result from a plasma bug. Just my opinion.

agurenko provided feedback 2 months ago

karma

steubens commented & provided feedback 2 months ago

karma

wrt: charging and 'not working', lg-laptop refers to the wmi/acpi module for the laptop, and how i was interacting with it was via sysfs (/sys/devices/platform/lg-laptop/battery_care_limit) specifically, though 80 and 100 were still the only valid values to write, when read again after setting, the result was always 0

$ cat /etc/udev/rules.d/99-set-charge-end-threshold.rules

#bios configured value? alternate write location? available at /sys/devices/platform/lg-laptop/battery_care_limit

#only values of 80 or 100 are valid, and if it's 100 it's not 80 ...
#technically this is all that's really needed
SUBSYSTEM=="power_supply", ATTR{charge_control_end_threshold}=="100", ATTR{charge_control_end_threshold}="80", RUN+="/bin/logger udev: setting battery_care_limit to 80 via power_supply"

#module instead
#KERNEL[165943.895179] add      /module/lg_laptop (module)
#ACTION=add
#DEVPATH=/module/lg_laptop
#SUBSYSTEM=module
#SEQNUM=106657

# /sys/devices/platform/lg-laptop/battery_care_limit
DEVPATH=="/module/lg_laptop", SUBSYSTEM=="module", ACTION=="add", RUN+="/bin/sh -c '/bin/echo -n 80 > /sys/devices/platform/lg-laptop/battery_care_limit && /bin/logger udev: setting battery_care_limit to 80 via lg_laptop"

both rules do the same thing, just at different times

on 6.9.6-200: $ cat /sys/devices/platform/lg-laptop/battery_care_limit