that’s way over my pay grade, but i did drop back to the 6.6 kernel so we’ll see what happens
oh, @cscs - i forgot to mention - a while back @stephane mentioned something regarding what i guess is the CPU driver(?) - mine is acpi-cpufreq and it was suggested i make a change
curious what you think given you mentioned power stuff…
This is pass-through.
Its a generally safe option that will allow the parts of iommu that work to, er, work, and skip the rest.
This is an approach to try and remedy freezing such as was seen under the intel broadwell and some ryzen processors. In some cases the only way to achieve a stable system was to disable some number of cstates. This would disable cstate6 … which would also mean some loss in energy efficiency.
There is some more information at this archwiki section;
https://wiki.archlinux.org/title/Ryzen#Soft_lock_freezing
This is one of the 3 options for setting how amd pstate will work, aside from disable.
I use active (amd_pstate_epp) in conjunction with a udev rule and some scripts like here.
(The manual scripts are partially because I use TLP and not power-profiles-daemon)
With the options you showed above I would think amd_pstate would be used instead of acp_cpufreq.
Well that is except that it appears there is a typo and _ should be used instead of - .
amd_pstate=guided
Otherwise I dont really think much - if you can run without the cstate option then you should. If you need it then you need it.
Your amd_pstate options are up to your tastes and needs.
But according to the archwiki if you want to use acpi_cpufreq then amd_pstate should be disabled.
more things that didn’t work…
- kernel version doesn’t seem to matter (6.1, 6.6, 6.12, all LTS)
- tried EndevourOS (Plasma)
- tried testing branch (back on stable now)
i was starting to suspect KDE/Plasma, but then i saw a very recent issue over at the Tumbleweed forum where an XFCE user appears to be having exactly the same problem
Try MESA v25 from this thread.
hey Deano - thanks for the tip, but the newer driver didn’t work for me
i tested mesa 25.0.0 rc3 and the system logged me off while writing this post
anyone else with this system freeze problem that’s running an AMD (amdgpu) system that wants to try the newer mesa driver should continue reading that thread beyond the link to the post i provided in order to check for further updates
in my case (KDE/Plasma) i downloaded the tar.zst file > right clicked > ‘open with software installer’ and rebooted
by running vulkaninfo --summary i was able to see that the new driver was installed…
$ vulkaninfo --summary
GPU0:
[...]
driverInfo = Mesa 25.0.0-rc3 (git-3a8abfa39b) (LLVM 19.1.7)
unfortunately the fix didn’t work for me
A post was merged into an existing topic: Sudden freezes after update
not to others: this freezing issue seems to affect only AMD APUs
possible temp solution (testing): downgrade mesa to 1:24.2.7-1 (24.2.8 that some people mention wasn’t in the repo) and llvm-libs to 18.1.8-4
i’ll test for a day or 2 and post back if this works (until a new version of mesa/llvm comes along)
Hopefully the latest mesa update will fix things? (2025-02-16 update). I see all branches are now on the same version:
mbn info mesa -q
Branch : archlinux
Name : mesa
Version : 1:24.3.4-1
Repository : extra
Build Date : Thu 23 Jan 2025 00:24:18
Packager : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Branch : unstable
Name : mesa
Version : 1:24.3.4-1
Repository : extra
Build Date : Thu 23 Jan 2025 00:24:18
Packager : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Branch : testing
Name : mesa
Version : 1:24.3.4-1
Repository : extra
Build Date : Thu 23 Jan 2025 00:24:18
Packager : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Branch : stable
Name : mesa
Version : 1:24.3.4-1
Repository : extra
Build Date : Thu 23 Jan 2025 00:24:18
Packager : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
i don’t think so(?) - i think we’re waiting on v25.x or 24.4.x, but i could be suffering from semi-permanent computer induced insanity
well, no freezing since the downgrade 7hrs ago - that’s a good sign - but Firefox is acting very weird - tabs keep crashing
$ journalctl -p 3 -xb
Feb 16 13:43:10 atompc kernel: amdgpu 0000:27:00.0: amdgpu: Secure display: Generic Failure.
Feb 16 13:43:10 atompc kernel: amdgpu 0000:27:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Feb 16 20:47:04 atompc kernel: BUG: unable to handle page fault for address: ffff9a224bb05480
Feb 16 20:47:04 atompc kernel: #PF: supervisor write access in kernel mode
Feb 16 20:47:04 atompc kernel: #PF: error_code(0x0002) - not-present page
the first 2 errors are normal, but the rest are not, so i think i’ll try changing kernels - currently on 6.12.12-2
Your profile info suggests you are on Stable branch? But if you are on this one, it suggests Testing:
mbn info report
mbn info linux612 -q
Branch : unstable
Name : linux612
Version : 6.12.13-2
Repository : core
Build Date : Sun 09 Feb 2025 16:27:45
Packager : Manjaro Build Server <build@manjaro.org>
Branch : testing
Name : linux612
Version : 6.12.12-2
Repository : core
Build Date : Mon 03 Feb 2025 16:27:19
Packager : Manjaro Build Server <build@manjaro.org>
Branch : stable
Name : linux612
Version : 6.12.11-1
Repository : core
Build Date : Thu 23 Jan 2025 20:29:02
Packager : Manjaro Build Server <build@manjaro.org>
i’m currently on stable, but i did try testing - that was before i learned of the mesa issue
You might need to try
sudo pacman -Syuu
to allow package downgrades to your current branch; although, as already mentioned, mesa itself currently appears to be the same version on all branches.
still freezing
mesa 24.2.7-1
lvm-libs 18.1.8-4
kernel 6.1.127-2
@BG405 - pamac did that for me
back on latest (stable)…
mesa 24.3.4
llvm-libs 19.1.7
journalctl -p 3 -xb shows nothing unexpected - -p 4 gets ugly
inxi output...
$ inxi --filter --verbosity=8
System:
Kernel: 6.1.127-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: hpet avail: acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
root=UUID=a45e1246-f90b-4ee1-92a3-3fd1b85c9a33 rw nowatchdog
resume=UUID=5328fe9f-b880-45b1-9bf6-7d4ca3d0234e udev.log_priority=3
Desktop: KDE Plasma v: 6.2.5 tk: Qt v: N/A info: frameworks v: 6.10.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: B450 TOMAHAWK MAX (MS-7C02) v: 1.0
serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: 3.K2 date: 08/30/2024
Battery:
Message: No system battery data found. Is one present?
Memory:
System RAM: total: 16 GiB available: 13.57 GiB used: 2.03 GiB (14.9%)
Message: For most reliable report, use superuser + dmidecode.
Array-1: capacity: 128 GiB slots: 4 modules: 2 EC: None
max-module-size: 32 GiB note: est.
Device-1: Channel-A DIMM 0 type: no module installed
Device-2: Channel-A DIMM 1 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 8 GiB speed: 2133 MT/s volts: note: check curr: 1
min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: G.Skill
part-no: F4-3200C16-8GVGB serial: N/A
Device-3: Channel-B DIMM 0 type: no module installed
Device-4: Channel-B DIMM 1 type: DDR4 detail: synchronous unbuffered
(unregistered) size: 8 GiB speed: 2133 MT/s volts: note: check curr: 1
min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: G.Skill
part-no: F4-3200C16-8GVGB serial: N/A
PCI Slots:
Permissions: Unable to run dmidecode. Root privileges required.
CPU:
Info: model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64
type: MT MCP arch: Zen/Zen+ note: check gen: 1 level: v3 note: check
built: 2019 process: GF 12nm family: 0x17 (23) model-id: 0x18 (24)
stepping: 1 microcode: 0x8108109
Topology: cpus: 1x dies: 1 clusters: 1 cores: 4 threads: 8 tpc: 2
smt: enabled cache: L1: 384 KiB desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB
desc: 4x512 KiB L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 1491 min/max: 1400/3700 boost: enabled scaling:
driver: acpi-cpufreq governor: schedutil cores: 1: 1491 2: 1491 3: 1491
4: 1491 5: 1491 6: 1491 7: 1491 8: 1491 bogomips: 59217
Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
bmi2 bpext clflush clflushopt clzero cmov cmp_legacy constant_tsc cpb
cpuid cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid f16c
flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb irperf
lahf_lm lbrv lm mca mce misalignsse mmx mmxext monitor movbe msr mtrr
mwaitx nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae pat
pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_llc perfctr_nb
pfthreshold pge pni popcnt pse pse36 rapl rdrand rdseed rdtscp rep_good
sep sev sev_es sha_ni skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2
sse4a ssse3 succor svm svm_lock syscall tce topoext tsc tsc_scale
v_vmsave_vmload vgif vmcb_clean vme vmmcall wdt xgetbv1 xsave xsavec
xsaveerptr xsaveopt
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 vulnerable
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:
disabled; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Picasso/Raven 2 [Radeon Vega
Series / Radeon Mobile Series] driver: amdgpu v: kernel arch: GCN-5
code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s
lanes: 16 ports: active: HDMI-A-1 empty: DVI-D-1,HDMI-A-2,HDMI-A-3
bus-ID: 27:00.0 chip-ID: 1002:15d8 class-ID: 0300 temp: 34.0 C
Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.5
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93") monitors: <missing: xrandr>
Monitor-1: HDMI-A-1 model: BenQ EX2510 serial: <filter> built: 2020
res: 1920x1080 dpi: 90 gamma: 1.2 chroma: red: x: 0.651 y: 0.341 green:
x: 0.310 y: 0.631 blue: x: 0.145 y: 0.051 white: x: 0.314 y: 0.329
size: 544x303mm (21.42x11.93") diag: 623mm (24.5") ratio: 16:9
modes: 1920x1080, 3840x2160, 1680x1050, 1600x900, 1280x1024, 1440x900,
1280x800, 1152x864, 1280x720, 1024x768, 832x624, 800x600, 720x576,
720x480, 640x480, 720x400
EDID-Warnings: 1: parse_edid: unhandled CEA mode 96 2: parse_edid:
unhandled CEA mode 97
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi x11:
drv: radeonsi inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.3.4-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon Vega 11 Graphics
(radeonsi raven LLVM 19.1.7 DRM 3.49 6.1.127-2-MANJARO)
device-ID: 1002:15d8 memory: 1.95 GiB unified: no
API: Vulkan Message: No Vulkan data available.
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyinfo,xprop
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP
Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 16 bus-ID: 27:00.1 chip-ID: 1002:15de class-ID: 0403
Device-2: Mark of the Unicorn M Series driver: cdc_acm,snd-usb-audio
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1:2
chip-ID: 07fd:000b class-ID: 0a00 serial: <filter>
API: ALSA v: k6.1.127-2-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.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 22:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp34s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>
IF-ID-1: azirevpn-us-mia state: unknown speed: N/A duplex: N/A mac: N/A
IP v4: <filter> scope: global
IP v6: <filter> scope: global
Info: services: mld, NetworkManager, systemd-timesyncd
WAN IP: <filter>
Bluetooth:
Message: No bluetooth data found.
Logical:
Message: No logical block device data found.
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 9.1 TiB used: 2.91 TiB (32.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: WDS100T3XHC-00SJG0 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: 102000WD temp: 36.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 4B6Q scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Crucial model: CT2000MX500SSD1
size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 033 scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 870 EVO 4TB
size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 3B6Q scheme: GPT
ID-5: /dev/sdd maj-min: 8:48 vendor: SanDisk model: SDSSDH32000G
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 70RL scheme: MBR
Message: No optical or floppy data found.
Partition:
ID-1: / raw-size: 904.41 GiB size: 889.14 GiB (98.31%)
used: 14.69 GiB (1.7%) fs: ext4 dev: /dev/nvme0n1p3 maj-min: 259:3
label: root uuid: a45e1246-f90b-4ee1-92a3-3fd1b85c9a33
ID-2: /backup raw-size: 1.82 TiB size: 1.79 TiB (98.37%)
used: 853.92 GiB (46.6%) fs: ext4 dev: /dev/sdb1 maj-min: 8:17 label: backup
uuid: 5cc0fb64-e894-4df0-9075-42cdb94500b1
ID-3: /boot/efi raw-size: 1024 MiB size: 1022 MiB (99.80%)
used: 288 KiB (0.0%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 label: efi
uuid: 44B6-E25B
ID-4: /home raw-size: 931.02 GiB size: 915.33 GiB (98.31%)
used: 99.8 GiB (10.9%) fs: ext4 dev: /dev/sda1 maj-min: 8:1 label: home
uuid: d186724a-14d9-46e5-a29d-b16ae175fd25
ID-5: /multimedia raw-size: 3.64 TiB size: 3.58 TiB (98.40%)
used: 1.94 TiB (54.2%) fs: ext4 dev: /dev/sdc1 maj-min: 8:33
label: multimedia uuid: 45c9271b-5cff-490c-bd91-37fc1c7ffeb7
ID-6: /storage raw-size: 1.82 TiB size: 1.79 TiB (98.42%)
used: 25.91 GiB (1.4%) fs: ext4 dev: /dev/sdd1 maj-min: 8:49 label: storage
uuid: 1eb02be6-20af-4ad8-9e1b-d592992fab43
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
compressor: zstd max-pool: 20%
ID-1: swap-1 type: partition size: 26 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p2 maj-min: 259:2 label: swap
uuid: 5328fe9f-b880-45b1-9bf6-7d4ca3d0234e
Unmounted:
Message: No unmounted partitions found.
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 10 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Device-1: 1-1:2 info: Mark of the Unicorn M Series
type: audio,abstract (modem),CDC-data driver: cdc_acm,snd-usb-audio
interfaces: 7 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0
power: 500mA chip-ID: 07fd:000b class-ID: 0a00 serial: <filter>
Device-2: 1-2:3 info: Logitech G502 X type: mouse,HID
driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
lanes: 1 mode: 1.1 power: 100mA chip-ID: 046d:c099 class-ID: 0300
serial: <filter>
Device-3: 1-8:4 info: Cyber Power System CP1500 AVR UPS type: HID
driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
lanes: 1 mode: 1.1 power: 2mA chip-ID: 0764:0501 class-ID: 0300
serial: <filter>
Device-4: 1-9:5 info: Apple Aluminium Keyboard (ISO) type: keyboard,mouse
driver: apple,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
lanes: 1 mode: 1.1 power: 300mA chip-ID: 05ac:0250 class-ID: 0301
Hub-2: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-4: 4-0:1 info: super-speed hub ports: 4 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-5: 5-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-6: 6-0:1 info: super-speed hub ports: 1 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Sensors:
System Temperatures: cpu: 33.1 C mobo: N/A gpu: amdgpu temp: 33.0 C
Fan Speeds (rpm): N/A
Repos:
Packages: pm: pacman pkgs: 1335 libs: 295 tools: pamac pm: flatpak pkgs: 0
Active pacman repo servers in: /etc/pacman.d/mirrorlist
1: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
2: https://repo.ialab.dsu.edu/manjaro/stable/$repo/$arch
3: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
4: https://opencolo.mm.fcix.net/manjaro/stable/$repo/$arch
Processes:
CPU top: 5 of 256
1: cpu: 100% command: ps pid: 2011 mem: 3.70 MiB (0.0%)
2: cpu: 7.7% command: thunderbird pid: 1478 mem: 511.5 MiB (3.6%)
3: cpu: 4.3% command: kwin_x11 pid: 1067 mem: 225.7 MiB (1.6%)
4: cpu: 3.8% command: kate pid: 1948 mem: 232.2 MiB (1.6%)
5: cpu: 2.5% command: plasmashell pid: 1131 mem: 439.3 MiB (3.1%)
Memory top: 5 of 256
1: mem: 511.5 MiB (3.6%) command: thunderbird pid: 1478 cpu: 7.7%
2: mem: 439.3 MiB (3.1%) command: plasmashell pid: 1131 cpu: 2.5%
3: mem: 232.2 MiB (1.6%) command: kate pid: 1948 cpu: 3.8%
4: mem: 225.7 MiB (1.6%) command: kwin_x11 pid: 1067 cpu: 4.3%
5: mem: 210.9 MiB (1.5%) command: konsole pid: 1905 cpu: 1.4%
Info:
Processes: 256 Power: uptime: 10m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 5.41 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Compilers: gcc: 14.2.1 Shell: Bash v: 5.2.37 running-in: konsole
inxi: 3.3.37
journelctl output...
$ journalctl -p 4 -xb
Feb 17 07:00:10 atompc kernel: ata1.00: supports DRM functions and may not be fully accessible
Feb 17 07:00:10 atompc kernel: ata1.00: supports DRM functions and may not be fully accessible
Feb 17 07:00:10 atompc kernel: ata2.00: supports DRM functions and may not be fully accessible
Feb 17 07:00:10 atompc kernel: ata2.00: supports DRM functions and may not be fully accessible
Feb 17 07:00:10 atompc kernel: ata5.00: supports DRM functions and may not be fully accessible
Feb 17 07:00:10 atompc kernel: ata5.00: supports DRM functions and may not be fully accessible
Feb 17 07:00:10 atompc kernel: clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large:
Feb 17 07:00:10 atompc kernel: clocksource: 'hpet' wd_nsec: 506982591 wd_now: 1bbbcd1 wd_last: 14cf915 mask: ffffffff
Feb 17 07:00:10 atompc kernel: clocksource: 'tsc' cs_nsec: 506544411 cs_now: 11ace2d12f cs_last: 113d13d3b1 mask: ffffffffffffffff
Feb 17 07:00:10 atompc kernel: clocksource: 'tsc' is current clocksource.
Feb 17 07:00:10 atompc kernel: TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'.
Feb 17 07:00:10 atompc kernel: clocksource: Checking clocksource tsc synchronization from CPU 5 to CPUs 0.
Feb 17 07:00:10 atompc kernel: Unstable clock detected, switching default tracing clock to "global"
If you want to keep using the local clock, then add:
"trace_clock=local"
on the kernel command line
Feb 17 07:00:10 atompc kernel: amdgpu 0000:27:00.0: amdgpu: PSP runtime database doesn't exist
Feb 17 07:00:10 atompc kernel: amdgpu 0000:27:00.0: amdgpu: PSP runtime database doesn't exist
Feb 17 07:00:10 atompc kernel: [drm] psp gfx command LOAD_TA(0x1) failed and response status is (0x7)
Feb 17 07:00:10 atompc kernel: [drm] psp gfx command INVOKE_CMD(0x3) failed and response status is (0x4)
Feb 17 07:00:10 atompc kernel: amdgpu 0000:27:00.0: amdgpu: Secure display: Generic Failure.
Feb 17 07:00:10 atompc kernel: amdgpu 0000:27:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Feb 17 07:00:14 atompc dbus-broker-launch[738]: Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.
░░ Subject: Activation request failed due to missing unit
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░
░░ systemd failed to activate the name org.freedesktop.home1
░░ because the service dbus-org.freedesktop.home1.service could not be found.
░░
░░ A possible reason for this is that dbus-org.freedesktop.home1.service is an
░░ alias to a disabled service. This is allowed by design, to give the
░░ administrator a way to disable name activation for a given service while
░░ still allowing it to be installed and potentially started in other ways.
░░
░░ In order not to flood the logs, this message is only emitted once per name.
Feb 17 07:00:14 atompc dbus-broker-launch[836]: Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManag>
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░
░░ A service file is a ini-type configuration file.
░░
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.
Feb 17 07:00:14 atompc dbus-broker-launch[836]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░
░░ A service file is a ini-type configuration file.
░░
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.
Feb 17 07:00:14 atompc dbus-broker-launch[836]: Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notificat>
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░
░░ A service file is a ini-type configuration file.
░░
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.
Feb 17 07:05:32 atompc sddm-greeter-qt6[832]: file:///usr/share/sddm/themes/breath/Main.qml:230:17 Parameter "username" is not declared. Injection of parameters into signal handlers is dep>
Feb 17 07:05:33 atompc dbus-broker-launch[990]: Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManag>
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░
░░ A service file is a ini-type configuration file.
░░
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.
Feb 17 07:05:33 atompc dbus-broker-launch[990]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░
░░ A service file is a ini-type configuration file.
░░
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.
Feb 17 07:05:33 atompc dbus-broker-launch[990]: Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notificat>
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░
░░ A service file is a ini-type configuration file.
░░
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.
Feb 17 07:05:33 atompc kernel: block nvme0n1: No UUID available providing old NGUID
Feb 17 07:05:33 atompc kernel: block nvme0n1: No UUID available providing old NGUID
Feb 17 07:05:33 atompc kernel: block nvme0n1: No UUID available providing old NGUID
Feb 17 07:05:33 atompc kernel: block nvme0n1: No UUID available providing old NGUID
Feb 17 07:05:33 atompc kernel: block nvme0n1: No UUID available providing old NGUID
Feb 17 07:05:33 atompc kernel: block nvme0n1: No UUID available providing old NGUID
Feb 17 07:05:33 atompc kernel: block nvme0n1: No UUID available providing old NGUID
Feb 17 07:05:33 atompc kernel: block nvme0n1: No UUID available providing old NGUID
Feb 17 07:05:33 atompc kernel: block nvme0n1: No UUID available providing old NGUID
Feb 17 07:05:33 atompc kernel: block nvme0n1: No UUID available providing old NGUID
Feb 17 07:05:34 atompc kded6[1066]: org.kde.libkbolt: Failed to connect to Bolt manager DBus interface:
Feb 17 07:05:34 atompc baloo_file[1005]: qt.dbus.integration: QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.31'
Feb 17 07:05:34 atompc baloo_file[1005]: qt.dbus.integration: QDBusConnection: name 'org.freedesktop.UPower' had owner '' but we thought it was ':1.34'
Feb 17 07:05:34 atompc kded6[1066]: QDBusObjectPath: invalid path "/modules/plasma-session-shortcuts"
Feb 17 07:05:34 atompc kded6[1066]: kf.dbusaddons: The kded module name "plasma-session-shortcuts" is invalid!
Feb 17 07:05:34 atompc kconf_update[1267]: kf.config.kconf_update: /usr/share/kconf_update/ark.upd defined Version=5 but Version=6 was expected
Feb 17 07:05:34 atompc kconf_update[1267]: kf.config.kconf_update: /usr/share/kconf_update/breath2tobreath.upd defined Version=5 but Version=6 was expected
Feb 17 07:05:34 atompc kconf_update[1267]: kf.config.kconf_update: /usr/share/kconf_update/dolphin_detailsmodesettings.upd defined Version=5 but Version=6 was expected
Feb 17 07:05:34 atompc kconf_update[1267]: kf.config.kconf_update: /usr/share/kconf_update/dolphin_directorysizemode.upd defined Version=5 but Version=6 was expected
Feb 17 07:05:34 atompc kconf_update[1267]: kf.config.kconf_update: /usr/share/kconf_update/filepicker.upd defined Version=5 but Version=6 was expected
Feb 17 07:05:34 atompc kconf_update[1267]: kf.config.kconf_update: /usr/share/kconf_update/konsole.upd defined Version=5 but Version=6 was expected
Feb 17 07:05:34 atompc kconf_update[1267]: kf.config.kconf_update: /usr/share/kconf_update/okular.upd defined Version=5 but Version=6 was expected
Feb 17 07:05:34 atompc kded6[1066]: kscreen.kded: PowerDevil SuspendSession action not available!
Feb 17 07:05:34 atompc plasmashell[1131]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:178:25: QML FolderViewDropArea (parent or ancestor of QQuickLay>
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:201:9
Feb 17 07:05:34 atompc org_kde_powerdevil[1199]: Failed to create wl_display (No such file or directory)
Feb 17 07:05:34 atompc wireplumber[1170]: spa.bluez5: BlueZ system service is not available
Feb 17 07:05:35 atompc kded6[1066]: org.kde.pulseaudio: No object for name "auto_null.monitor"
Feb 17 07:05:35 atompc plasmashell[1131]: Toolbox not loading, toolbox package is either invalid or disabled.
Feb 17 07:05:35 atompc kded6[1066]: org.kde.pulseaudio: No object for name "auto_null"
Feb 17 07:05:35 atompc kded6[1066]: org.kde.pulseaudio: No object for name "auto_null.monitor"
Feb 17 07:05:35 atompc kded6[1066]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Feb 17 07:05:35 atompc kded6[1066]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Feb 17 07:05:35 atompc kded6[1066]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Feb 17 07:05:35 atompc kded6[1066]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Feb 17 07:05:35 atompc kded6[1066]: org.kde.pulseaudio: No object for name "alsa_input.usb-MOTU_M2_M2AE12AEVI-00.HiFi__Mic2__source"
Feb 17 07:05:35 atompc plasmashell[1131]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:50:9: QML KSortFilterProxyModel: Binding loop detected f>
Feb 17 07:05:35 atompc plasmashell[1131]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:50:9: QML KSortFilterProxyModel: Binding loop detected f>
Feb 17 07:05:35 atompc plasmashell[1131]: qt.dbus.integration: Could not connect "org.cups.cupsd.Notifier" to PrinterFinishingsChanged(QString, QString, QString, uint, QString, bool) :
Feb 17 07:05:36 atompc plasmashell[1131]: QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
Feb 17 07:05:37 atompc pipewire[1168]: pw.node: (alsa_output.usb-MOTU_M2_M2AE12AEVI-00.HiFi__Line1__sink-60) graph xrun not-triggered (0 suppressed)
Feb 17 07:05:37 atompc pipewire[1168]: pw.node: (alsa_output.usb-MOTU_M2_M2AE12AEVI-00.HiFi__Line1__sink-60) xrun state:0x7f28d17a5008 pending:1/1 s:0 a:0 f:0 waiting:0 process:0 status:tr>
Feb 17 07:05:37 atompc backlighthelper[1453]: org.kde.powerdevil: no kernel backlight interface found
Feb 17 07:05:38 atompc org_kde_powerdevil[1199]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for thi>
Feb 17 07:05:38 atompc org_kde_powerdevil[1199]: org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed
Feb 17 07:05:38 atompc org_kde_powerdevil[1199]: org.kde.powerdevil: Handle button events action could not check for screen configuration
Feb 17 07:05:38 atompc org_kde_powerdevil[1199]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for thi>
Feb 17 07:05:38 atompc easyeffects[1473]: Unknown key gtk-modules in /home/atom/.config/gtk-4.0/settings.ini
Feb 17 07:05:38 atompc xdg-desktop-portal-kde[1201]: xdp-kde-settings: Namespace "org.gnome.desktop.a11y.interface" is not supported
Feb 17 07:05:38 atompc easyeffects[1473]: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.
Feb 17 07:06:03 atompc systemd[953]: app-sync.sh@autostart.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ The unit UNIT has entered the 'failed' state with result 'exit-code'.
Feb 17 07:06:33 atompc systemd[953]: dbus-:1.2-org.kde.KSplash@0.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ The unit UNIT has entered the 'failed' state with result 'exit-code'.
I encountered the same problem. I fixed it by downloading the file from the post above mesa-test-git-25.0.0_devel.200908.66775c89fce-1-x86_64.pkg.tar. NOW IT DOESN’T HANG
hi @HaTTaB - how long have you been running mesa-test-git-25.0.0?
Works for three or four hours without freezing.
If you want to catch the bug yourself and not wait for freezing, you need to open any window, I opened the browser and often changed the size with the mouse horizontally or vertically, the interface froze as described in the problem. After installing mesa-test-git-25.0.0 nothing freezes.
i’m back on stable now (mesa 24.3.4, llvm-libs 19.1.7) and no freezes or Firefox wonkyness in 14 hrs, though i did do a BIOS reset also
welcome to the forum BTW