Manjaro won't shutdown/reboot sometimes, ^@^@^@^@^@^@^@ stays on display

So, today I bought a new notebook (Lenovo IdeaPad 3 with Ryzen 7 5700U) and installed Manjaro on it. Sometimes, after using the notebook for a while, it won’t reboot or shutdown. It just goes to a black screen with “^@^@^@^@^@^@^@” displayed on top left. If i just hold the power button, it shutdowns and initialize normal after that, but I’m concerned that it might be some issue that’s fixable.

System information:

System:
  Kernel: 5.10.105-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64
    root=UUID=62c60756-a93e-45ad-82c9-2f205a6525b7 rw quiet apparmor=1
    security=apparmor udev.log_priority=3
  Desktop: KDE Plasma 5.24.3 tk: Qt 5.15.3 wm: kwin_wayland vt: 2 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 82MF v: IdeaPad 3 15ALC6
    serial: <superuser required> Chassis: type: 10 v: IdeaPad 3 15ALC6
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0T76464WIN
    serial: <superuser required> UEFI: LENOVO v: GLCN40WW date: 07/23/2021
Battery:
  ID-1: BAT0 charge: 22.7 Wh (57.6%) condition: 39.4/38.0 Wh (103.6%)
    volts: 7.8 min: 7.7 model: SMP L20M2PF0 type: Li-poly serial: <filter>
    status: Discharging cycles: 1
Memory:
  RAM: total: 5.72 GiB used: 2.91 GiB (50.8%)
  RAM Report:
    permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 7 5700U with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 2 family: 0x17 (23) model-id: 0x68 (104) stepping: 1
    microcode: 0x8608103
  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: 8 MiB
    desc: 2x4 MiB
  Speed (MHz): avg: 1582 high: 3735 min/max: 1400/4370 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1397 2: 3735
    3: 1677 4: 1397 5: 1397 6: 1396 7: 1745 8: 1397 9: 1397 10: 1397 11: 1397
    12: 1397 13: 1397 14: 1397 15: 1397 16: 1397 bogomips: 57513
  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 extapic extd_apicid
    f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb ibrs ibs
    irperf lahf_lm lbrv lm mba 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 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_vmsave_vmload vgif vmcb_clean vme vmmcall wbnoinvd wdt
    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: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl and seccomp
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: conditional, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Lucienne vendor: Lenovo driver: amdgpu v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s ports: active: eDP-1
    empty: HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:164c class-ID: 0300
  Device-2: Syntek Integrated Camera type: USB driver: uvcvideo
    bus-ID: 1-3:2 chip-ID: 174f:244c class-ID: 0e02 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.0
    compositor: kwin_wayland driver: X: loaded: amdgpu,ati unloaded: modesetting
    alternate: fbdev,vesa gpu: amdgpu display-ID: 0
  Monitor-1: eDP-1 res: 1920x1080 size: N/A
  OpenGL: renderer: AMD RENOIR (DRM 3.40.0 5.10.105-1-MANJARO LLVM 13.0.1)
    v: 4.6 Mesa 21.3.7 direct render: Yes
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.1 chip-ID: 1002:1637
    class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo driver: N/A
    alternate: snd_pci_acp3x, snd_rn_pci_acp3x pcie: gen: 3 speed: 8 GT/s
    lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 03: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: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s bus-ID: 03:00.6 chip-ID: 1022:15e3 class-ID: 0403
  Sound Server-1: ALSA v: k5.10.105-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.20 running: no
  Sound Server-3: PulseAudio v: 15.0 running: yes
  Sound Server-4: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter
    vendor: Lenovo driver: rtw_8822ce v: N/A modules: rtw88_8822ce pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 01:00.0 chip-ID: 10ec:c822
    class-ID: 0280
  IF: wlp1s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  WAN IP: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8
    bus-ID: 3-4:2 chip-ID: 0bda:c123 class-ID: e001 serial: <filter>
  Report: bt-adapter ID: hci0 rfk-id: 2 state: up address: <filter>
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 238.47 GiB used: 29.29 GiB (12.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SSSTC model: CL1-4D256
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: BS262 temp: 34.9 C scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 100 GiB size: 97.87 GiB (97.87%) used: 22.42 GiB (22.9%)
    fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:1 label: N/A
    uuid: 62c60756-a93e-45ad-82c9-2f205a6525b7
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
    used: 288 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p3 maj-min: 259:2
    label: NO_LABEL uuid: 03A1-2C6D
  ID-3: /home raw-size: 137.46 GiB size: 134.24 GiB (97.66%)
    used: 6.87 GiB (5.1%) fs: ext4 dev: /dev/nvme0n1p4 maj-min: 259:3 label: N/A
    uuid: 11bc7e4c-d298-4560-b1e5-467309264ed9
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 8 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-3:2 info: Syntek Integrated Camera type: Video
    driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s power: 500mA
    chip-ID: 174f:244c class-ID: 0e02 serial: <filter>
  Hub-2: 2-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s
    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 chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 3-4:2 info: Realtek Bluetooth Radio type: Bluetooth
    driver: btusb interfaces: 2 rev: 1.0 speed: 12 Mb/s power: 500mA
    chip-ID: 0bda:c123 class-ID: e001 serial: <filter>
  Hub-4: 4-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
Sensors:
  System Temperatures: cpu: 47.0 C mobo: N/A gpu: amdgpu temp: 39.0 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 340 Uptime: 24m wakeups: 1 Init: systemd v: 250 tool: systemctl
  Compilers: gcc: 11.2.0 clang: 13.0.1 Packages: pacman: 1447 lib: 366
  flatpak: 0 Shell: Zsh v: 5.8.1 default: Bash v: 5.1.16 running-in: konsole
  inxi: 3.3.13

With journalctl -b -1 you’ll get the full log of the last boot.

Scroll do the bottom and see if there’s anything of interest. If you don’t find anything, paste the contents of the last (maybe 50?) lines here in code tags.

Okay, now I just need to wait for the error to show again.

Well if you remember when it happened, you can go back in time by decreasing the -1 in the command

So, journalctl -b -5 would give you the log from the 5th last boot.

1 Like

Thank you! I really didn’t know that. I’m going to investigate the last boots and if I find something meaningful in one of them, I’ll post here.

So I just rebooted and the error happened, found this on journalctl and I think it might be meaningul:

mar 17 19:32:47 victor kernel: [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: stat>
mar 17 19:32:47 victor xdg-desktop-portal-kde[1129]: The Wayland connection broke. Did the Wayland compositor>
mar 17 19:32:47 victor baloorunner[1293]: The Wayland connection broke. Did the Wayland compositor die?
mar 17 19:32:47 victor baloorunner[1293]: The Wayland connection broke. Did the Wayland compositor die?
mar 17 19:32:47 victor kactivitymanagerd[974]: The Wayland connection broke. Did the Wayland compositor die?
mar 17 19:32:47 victor kactivitymanagerd[974]: The Wayland connection broke. Did the Wayland compositor die?
mar 17 19:32:47 victor systemd[744]: plasma-baloorunner.service: Main process exited, code=exited, status=1/F>
mar 17 19:32:47 victor systemd[744]: plasma-baloorunner.service: Failed with result 'exit-code'.
mar 17 19:32:47 victor systemd[744]: plasma-xdg-desktop-portal-kde.service: Main process exited, code=exited,>
mar 17 19:32:47 victor systemd[744]: plasma-xdg-desktop-portal-kde.service: Failed with result 'exit-code'.
mar 17 19:32:47 victor systemd[744]: plasma-kactivitymanagerd.service: Main process exited, code=exited, stat>
mar 17 19:32:47 victor systemd[744]: plasma-kactivitymanagerd.service: Failed with result 'exit-code'.

I don’t have any problems but since I switched to wayland I also have ^@^@^@^@^@^@^@ when I shutdown/reboot.

What causes this ?

Can you post your PC specs? I’m suspecting it may happen since kernel 5.15 to new AMD gpu’s.

I downgraded to kernel 5.10 and by far it’s doing great, rebooted a lot and got no errors since then.

1 Like

Welcome to Manjaro! :smiling_face_with_three_hearts:

  1. Please read the information behind this link. It will help you to post necessary information. [HowTo] Provide System Information
  2. Please press the three dots below your post and then press the :pencil2:
  • If you give us information about your system, we can see what we’re talking about and make better suggestions.
  1. You can do this by using inxi in a terminal or in console.
inxi --admin --verbosity=7 --filter --no-host --width
  • Personally identifiable information such as serial numbers and MAC addresses are filtered out by this command
  • Presenting the information in this way allows everyone to be familiar with the format and quickly find the items they need without missing anything.
  1. Copy the output from inxi (including the command) and paste it into your post.
  • To make it more readable, add 3 backticks ``` on an extra line before and after the pasted text.

Gentle shut down a suddenly hanged PC to minimize a chance of getting a broken filesystem and data loss:

Is it possible that your PC did shutdown, but forgot to switch the power off at the end of shutdown?

1 Like

It happens to me sometimes on my desktop 5700G too.

But it usually gets done after a minute or so on it’s own.

Thank you for the guide on how to reboot/shutdown! I really didn’t know that forcing the PC to shutdown could cause long-term problems. Will definitely write all that down.

And answering the question: I waited a couple of minutes and then forced the shutdown by holding the power button for ~10s.

The human analogy would be holding a pillow over someone’s face until they don’t move anymore.

1 Like

Wow. It really seems to have something with the AMD new cpu/gpu’s. (1; 2).

Well, since the downgrade everything is fine here. If something happens, I’m going to update here.