[Stable Update] 2024-07-16 - Kernels, Firefox, Thunderbird, Nvidia, Systemd, LibreOffice

Yep, that’s what you get when you hire developers who’ve never read a book on UNIX, let alone that they’ve ever seen a UNIX terminal from up close. :wink:

1 Like

We were able to patch and build all missing extramodules of 6.10 kernel series. Including r8168 driver.

3 Likes

Just to report that new 6.10 kernel is not working properly with Hybernation on my system. Works fine to set create the image in swap, and to recover from it. It just fails to shut down the laptop after creating the hibernation image. You have to force the shutting down long pressing the power button, and everything starts fine after that, not giving errors, nor corrupted filesystem. Everything is properly executed, except the powering down. Nothing important.
And 6.9 still works fine, so I’m using it.

Probably something that will be corrected. But if you want to study that and need info, please, ask!

2 Likes

I’ve been having the same problem since the last update, and it happens when I have a monitor connected and the system goes to sleep after the scheduled idle time.

I had Kernel 6.9.9-1 and I have gone back to 6.6.40-1 and the initial tests seem to have gone well. I will continue testing and update here.

Edit: No luck. It still happens with the 6.6.40-1 kernel, but always with the monitor connected. If it goes to sleep without the monitor it works fine.

After the update the internal speakers of my laptop only output sound after either muting and then unmuting them or plugging and then unplugging the head phone jack.

System:
  Kernel: 6.9.9-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
    clocksource: tsc
  Desktop: GNOME v: 46.3.1 tk: GTK v: 3.24.43 wm: gnome-shell
    with: ulauncher tools: gsd-screensaver-proxy dm: GDM v: 46.2 Distro: Manjaro
    base: Arch Linux
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
    bus-ID: 07:00.1 chip-ID: 1002:1637 class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo
    driver: snd_rn_pci_acp3x v: kernel pcie: speed: 8 GT/s lanes: 16
    bus-ID: 07:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio vendor: Lenovo driver: snd_hda_intel
    v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 07:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  API: ALSA v: k6.9.9-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator
  Server-1: PipeWire v: 1.2.1 status: active with: 1: pipewire-pulse
    status: active 2: pipewire-media-session status: active 3: pipewire-alsa
    type: plugin 4: pw-jack type: plugin

Could be related to these issues:

Same. I have a desktop with wired Ethernet and Kernel 6.10 I was getting 5 messages per second. I’m surprised my machine had the horses to do anything else. Falling back to 6.9 fixed it.

It seems to have made it to a patch on the kernel bugzilla: 201761 – "failed to read out thermal zone" for wifi thermal zone . Go down to comment 72 - the topic has morphed greatly.

In case anyone is interested: thermal_zone0 is the wifi (iwlwifi_1) on my computer.
Also: inxi -Fazy

System:
  Kernel: 6.9.9-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.9-x86_64
    root=UUID=f0812a05-f95b-47a2-a7a3-d652d9b60591 rw
    resume=UUID=5052202f-aca8-4237-92d4-ae513ec48917 udev.log_priority=3
    intel_pstate=disable
  Desktop: KDE Plasma v: 6.0.5 tk: Qt v: N/A info: frameworks v: 6.3.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: ASRock model: A320M-HDV R4.0 serial: <superuser required>
    uuid: <superuser required> UEFI: American Megatrends v: P7.00
    date: 11/15/2021
CPU:
  Info: model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 gen: 3
    level: v3 note: check built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23)
    model-id: 0x71 (113) stepping: 0 microcode: 0x8701021
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 32 MiB
    desc: 2x16 MiB
  Speed (MHz): avg: 2653 high: 3600 min/max: 2200/4208 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 2200 2: 3600
    3: 2047 4: 2200 5: 2205 6: 3594 7: 3600 8: 2200 9: 2200 10: 3594 11: 2200
    12: 2200 bogomips: 86279
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP
    protection
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; STIBP:
    always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
    vendor: Micro-Star MSI driver: amdgpu v: kernel arch: GCN-4
    code: Arctic Islands process: GF 14nm built: 2016-20 pcie: gen: 3
    speed: 8 GT/s lanes: 16 ports: active: DP-2 empty: DP-1, DVI-D-1,
    HDMI-A-1, HDMI-A-2 bus-ID: 07:00.0 chip-ID: 1002:67df class-ID: 0300
    temp: 53.0 C
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.1
    compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: 0
  Monitor-1: DP-2 res: 3840x1600 size: N/A modes: N/A
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
    drv: radeonsi inactive: gbm
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.1.3-manjaro1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 580 Series (radeonsi
    polaris10 LLVM 18.1.8 DRM 3.57 6.9.9-1-MANJARO) device-ID: 1002:67df
    memory: 3.91 GiB unified: no display-ID: :1.0
  API: Vulkan v: 1.3.279 layers: 4 device: 0 type: discrete-gpu name: AMD
    Radeon RX 580 Series (RADV POLARIS10) driver: mesa radv
    v: 24.1.3-manjaro1.1 device-ID: 1002:67df surfaces: xcb,xlib,wayland
Audio:
  Device-1: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
    vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 07:00.1 chip-ID: 1002:aaf0 class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASRock
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 09:00.4 chip-ID: 1022:1487 class-ID: 0403
  API: ALSA v: k6.9.9-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.2.1 status: off with: wireplumber status: active
    tools: pw-cli,wpctl
  Server-3: PulseAudio v: 17.0 status: active with: pulseaudio-alsa
    type: plugin tools: pacat,pactl,pavucontrol
Network:
  Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 05:00.0
    chip-ID: 8086:24fb class-ID: 0280
  IF: wlp5s0 state: down mac: <filter>
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASRock driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    port: f000 bus-ID: 06:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp6s0 state: up speed: 100 Mbps duplex: full mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
  Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Intel Wireless-AC 3168 Bluetooth driver: btusb v: 0.8 type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-7:2 chip-ID: 8087:0aa7
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 3 state: up address: <filter> bt-v: 4.2
    lmp-v: 8 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
  Local Storage: total: 2.95 TiB used: 1.37 TiB (46.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Crucial model: CT1000P3SSD8
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: P9CR30A temp: 40.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: WDC WDS240G2G0A-00JH30
    size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 0400 scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WD10EZEX-08WN4A0 size: 931.51 GiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
    fw-rev: 1A02 scheme: GPT
  ID-4: /dev/sdc maj-min: 8:32 vendor: Western Digital
    model: WD10SDRW-11A0XS1 size: 931.48 GiB block-size: physical: 512 B
    logical: 512 B type: USB rev: 3.1 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1
    tech: HDD rpm: 5400 serial: <filter> fw-rev: 1018 scheme: GPT
Partition:
  ID-1: / raw-size: 922.42 GiB size: 906.86 GiB (98.31%)
    used: 498.22 GiB (54.9%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 27.2 MiB (9.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
  System Temperatures: cpu: 59.8 C mobo: N/A gpu: amdgpu temp: 54.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 210
Info:
  Memory: total: 32 GiB available: 31.28 GiB used: 7.17 GiB (22.9%)
  Processes: 342 Power: uptime: 20h 46m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 2 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.5 GiB services: org_kde_powerdevil,upowerd
    Init: systemd v: 256 default: graphical tool: systemctl
  Packages: 1919 pm: pacman pkgs: 1906 libs: 528 tools: pamac,yay pm: rpm
    pkgs: 1 pm: flatpak pkgs: 12 Compilers: clang: 18.1.8 gcc: 14.1.1 Shell: Zsh
    v: 5.9 running-in: konsole inxi: 3.3.35

(I have already fallen back to the 6.9 kernel at this time)

2 Likes

so over the past couple days there have been some small updates to what I imagine are nvidia drivers (don’t know/care as an amdgpu user), but while browsing for any orphans in the pamac-gui, I noticed a couple are listed now that weren’t after originally applying the 2024-07-16 update:

  1. openvr - I don’t have any openvr hardware, so this ones a no-brainer to uninstall
  2. wlroots - this ones got me a bit leary both wlroots and xorg-xwayland list the other as an optional dependency

is it “safe” under KDE plasma wayland to remove wlroots as the compositor is kwin? Or is this one of those moments where the better option is to mark wlroots as explicitly installed so that it does not come up in future orphan checks?

1 Like

Is Interesting the original entry is from 2018 Kernel 4.18 like a Uboot that keeps popping up briefly. i’m back to 6.9 and waiting for improvement.

I read it as solely a one-way dependency: wlroots optionally depends on xorg-xwayland.

$ pacman -Sii wlroots
Name            : wlroots
Optional Deps   : xorg-xwayland: Xwayland support
Optional For    : None
$ pacman -Sii xorg-xwayland
Name            : xorg-xwayland
Optional Deps   : None
Optional For    : cage  qtile  sway  weston  wlroots  wlroots0.17

@dad23innj and @Hal9000 please switch to testing and see if the kernel update fixes it for you. If I will forward it to stable branch.

Ah, Optional For versus Optional Dependency, thank you for pointing that out.

pamac info wlroots | grep Optional                                                                                                     
Optional Dependencies : xorg-xwayland: Xwayland support [Installed]
Optional For          : --
pamac info xorg-xwayland | grep Optional                                                                                                   
Optional Dependencies : --
Optional For          : wlroots

So should be safe to remove without causing any issues.

@philm Thank you, it worked. No more spurious messages in the journal. My kernel version is now:

uname -a                                                                                                                                            ✔  28s  
Linux flashymanjaro 6.10.0-3-MANJARO #1 SMP PREEMPT_DYNAMIC Mon Jul 22 03:31:44 UTC 2024 x86_64 GNU/Linux

I am on Plasma with Wayland and I don’t even have wlroots installed. So yes, you can safely delete it.

1 Like

After switching to testing Kernel 6.10.0.-3 no more thermal zone errors! :+1:

Linux NUC14RVKU7 6.10.0-3-MANJARO #1 SMP PREEMPT_DYNAMIC Mon Jul 22 03:31:44 UTC 2024 x86_64 GNU/Linux

I also went back to 6.9 from 6.10 kernel, as on 6.10 every time I open Steam, after a few minutes, every thing freezes and I have to hard boot the PC again. Fine on 6.9.
Will try 6.10 again after an update or two

2 Likes

A post was split to a new topic: File conflict errors related to Python 3.12

@dad23innj and @Hal9000 thx for testing the kernel. Now forwarded to stable branch.

And now, justo to report that after today’s kernel update, Hybernation is working fine again.

EDIT: Sorry, it’s not working yet. Just first time.
Reverting to 6.9

1 Like

I also experienced several (about one every two days) system hangs with 6.10 on an aging intel haswell with integrated gfx. On some hangs the kernel managed to write a message to the system log:

kernel: BUG: kernel NULL pointer dereference, address: 0000000000000001

and

kernel: BUG: unable to handle page fault for address: ffff9ef25a84da18
kernel: #PF: supervisor write access in kernel mode

Switched back to 6.9 for now as well.

Same here!
Now I am not getting the notification from pacman, but discover makes the notification that the package needs to be updated.

Doesn’t both tools use the same repositories from manjaro?
(Sorry I can’t post images, I am getting this error: “An error occurred: Sorry, you can’t embed media items in a post.”)

1 Like