Only a minor issue with the kitty terminal:
the font seems a lot thicker / bolder than before … didn’f find a solution for now …
akonadi failed to upgrade its database on the first system reboot and crashed.
It succeeded on the second.
3 Likes
Replace qemu-virtiofsd with extra/virtiofsd?
Some advice for this ?
PS: I have chosen to replace and seems everything is ok…
1 Like
after the upgrade, i am experiencing (kernel?) crashes (both on 6.2 and 6.3), without any specific error in journalctl, it just resets the whole system (like having pressed the reset power button), reverting to before (thanks to snapper) fixes the issue for now
the last journalctl of the run where it resets look like:
May 07 13:40:47 Meicoo-Manjaro rtkit-daemon[1501]: Supervising 11 threads of 6 processes of 1 users.
May 07 13:40:47 Meicoo-Manjaro rtkit-daemon[1501]: Supervising 11 threads of 6 processes of 1 users.
May 07 13:41:30 Meicoo-Manjaro rtkit-daemon[1501]: Supervising 11 threads of 6 processes of 1 users.
May 07 13:41:30 Meicoo-Manjaro rtkit-daemon[1501]: Supervising 11 threads of 6 processes of 1 users.
May 07 13:42:14 Meicoo-Manjaro rtkit-daemon[1501]: Supervising 11 threads of 6 processes of 1 users.
May 07 13:42:14 Meicoo-Manjaro rtkit-daemon[1501]: Supervising 11 threads of 6 processes of 1 users.
May 07 13:43:59 Meicoo-Manjaro kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
May 07 13:43:59 Meicoo-Manjaro kernel: ata1.00: configured for UDMA/133
May 07 13:44:04 Meicoo-Manjaro kernel: ata1.00: qc timeout after 5000 msecs (cmd 0xa0)
May 07 13:44:04 Meicoo-Manjaro kernel: ata1.00: TEST_UNIT_READY failed (err_mask=0x4)
May 07 13:44:14 Meicoo-Manjaro kernel: ata1: softreset failed (1st FIS failed)
May 07 13:44:14 Meicoo-Manjaro rtkit-daemon[1501]: Supervising 11 threads of 6 processes of 1 users.
May 07 13:44:14 Meicoo-Manjaro rtkit-daemon[1501]: Supervising 11 threads of 6 processes of 1 users.
May 07 13:44:15 Meicoo-Manjaro kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
May 07 13:44:15 Meicoo-Manjaro kernel: ata1.00: configured for UDMA/133
without a notice of a reboot / reset or kernel panic
pacman.log from the upgrade (for package changes reference)
also i dont know if it matters, but after such a reset happens, it prints the following on the next boot (both on screen for a short time and in the journal log) but does not print this when rebooting normally (like via poweroff --reboot or via shutdown and pressing power button):
May 07 13:45:30 Meicoo-Manjaro kernel: mce: [Hardware Error]: CPU 2: Machine Check: 0 Bank 5: bea0000001000108
May 07 13:45:30 Meicoo-Manjaro kernel: microcode: CPU13: patch_level=0x0a20120a
May 07 13:45:30 Meicoo-Manjaro kernel: fbcon: Taking over console
May 07 13:45:30 Meicoo-Manjaro kernel: mce: [Hardware Error]: TSC 0 ADDR ffffff8bd8b6d6 MISC d012000100000000 SYND 4d000000 IPID 500b000000000
May 07 13:45:30 Meicoo-Manjaro kernel: mce: [Hardware Error]: PROCESSOR 2:a20f12 TIME 1683459924 SOCKET 0 APIC 4 microcode a20120a
maybe something related to the amd-ucode package update?
kde system info (when running before the upgrade):
Operating System: Manjaro Linux
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.12-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX Vega
Manufacturer: ASUS
PS: in total the resets happened 2 times since the upgrade (within ~2 hours after the upgrade)
ERROR: Hook ‘zfs’ cannot be found
on all kernels
Also no linux63-zfs package
In version 0.28 there’s new config option introduced which configures the thing you mentioned
1 Like
Upstream does not yet support 6.3.
check with kernel 5.15 LTS if you get same errors
also check cables for error on sata1.
can you report
inxi -fzaremoved 6.3 and still getting this messages with 6.1 and 6.2
reinstalled linux61-zfs and linux62-zfs - no effect.
tested zfs-dkms - it generates modules, but ‘mkinicpio -P’ still generate the error.
I fear to reboot 
check with kernel 5.15 LTS if you get same errors
like i said earlier, it happens regardless of kernel (tested new 6.3 new 6.2 and before-upgrade)
also check cables for error on sata1.
it works without problems before the update (like i am running now), also ata1 (like mentioned in the journalctl) is my disk drive (bluray to be specific), with nothing in it
inxi -fza
(without amd-ucode update)
CPU:
Info: model: AMD Ryzen 7 5800X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 2 microcode: 0xA20120A
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 2880 high: 4295 min/max: 2200/4850 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 2200 2: 2200
3: 3258 4: 2200 5: 2200 6: 2200 7: 2200 8: 4295 9: 3594 10: 3399 11: 2200
12: 2876 13: 3800 14: 2880 15: 2878 16: 3704 bogomips: 121639
Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists erms extapic
extd_apicid f16c flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt ht
hw_pstate ibpb ibrs ibs invpcid irperf lahf_lm lbrv lm mba mca mce
misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt
nrip_save nx ospke osvw overflow_recov pae pat pausefilter pclmulqdq
pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pku pni
popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep
sha_ni skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3
stibp succor svm svm_lock syscall tce topoext tsc tsc_scale umip
v_spec_ctrl v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall vpclmulqdq
wbnoinvd wdt x2apic xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
Vulnerabilities:
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: retbleed status: Not affected
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, IBRS_FW,
STIBP: always-on, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
see for adding on boot kernel
“iommu=pt amd_pstate=passive processor.max_cstate=5”
you can block amd-ucode update and do a try , if errors still occurs ( that will indicate that there is error from microcode )
Update the BIOS.
thanks for notifying that there is a bios update, though still it shouldnt break after a linux system update
I’m running into one new issue caused with this update, KDE Plasma (Wayland) with Dolphin: Whenever I move a file to another directory by shift-dragging, the view doesn’t refresh to show the old file having been moved, I have to press F5 to do a manual refresh after which the moved file is no longer displayed in its old location. Anyone else getting this one?
see for adding on boot kernel
did you mean before or after the amd-ucode update?
you can block amd-ucode update and do a try , if errors still occurs ( that will indicate that there is error from microcode )
i am currently running the update, without amd-ucode updated and linux63 installed, and it seems to work fine (also not yet bios updated like suggested in another comment)
blocked before the update after this is a downgrade
The updated ucode requires a new AGESA version, hence, a BIOS update is required.
You can always blacklist the amd-ucode package.
Future amd-code updates will require the newer BIOS too.
EDIT: That is a common issue and it does not depend on Manjaro. It was reported on gentoo forums for the firs time and it affects all linux versions which include the updated microcode.
It’s up to you to keep your hardware firmware up to date.
wow, really great help! Thank you so much !!!