Fresh Install Manjaro randomly crash

[OverSu]

Hi everyone,

System:
  Kernel: 6.1.30-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
    root=UUID=c3874422-fb47-4b74-8a48-5d92db94cc9d rw quiet splash
    udev.log_priority=3
  Desktop: KDE Plasma v: 5.27.4 tk: Qt v: 5.15.9 wm: kwin_x11 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: B450M MORTAR TITANIUM (MS-7B89) v: 2.0
    serial: <filter> UEFI: American Megatrends LLC. v: A.I1 date: 05/16/2023
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: available: 31.27 GiB used: 3.83 GiB (12.2%)
  Array-1: capacity: 128 GiB slots: 4 EC: None max-module-size: 32 GiB
    note: est.
  Device-1: DIMM 0 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 8 GiB speed: 2133 MT/s volts: curr: 1.2 min: 1.2 max: 1.2 width (bits):
    data: 64 total: 64 manufacturer: Corsair part-no: CMK16GX4M2A2666C16
    serial: N/A
  Device-2: DIMM 1 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 8 GiB speed: 2133 MT/s volts: curr: 1.2 min: 1.2 max: 1.2 width (bits):
    data: 64 total: 64 manufacturer: Corsair part-no: CMK16GX4M2A2666C16
    serial: N/A
  Device-3: DIMM 0 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 8 GiB speed: 2133 MT/s volts: curr: 1.2 min: 1.2 max: 1.2 width (bits):
    data: 64 total: 64 manufacturer: Corsair part-no: CMK16GX4M2A2666C16
    serial: N/A
  Device-4: DIMM 1 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 8 GiB speed: 2133 MT/s volts: curr: 1.2 min: 1.2 max: 1.2 width (bits):
    data: 64 total: 64 manufacturer: Corsair part-no: CMK16GX4M2A2666C16
    serial: N/A
CPU:
  Info: model: AMD Ryzen 7 2700X socket: AM4 bits: 64 type: MT MCP arch: Zen+
    gen: 2 level: v3 note: check built: 2018-21 process: GF 12nm
    family: 0x17 (23) model-id: 8 stepping: 2 microcode: 0x800820D
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 768 KiB desc: d-8x32 KiB; i-8x64 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB
    desc: 2x8 MiB
  Speed (MHz): avg: 2356 high: 3700 min/max: 2200/3700 boost: enabled
    base/boost: 3700/4350 scaling: driver: acpi-cpufreq governor: schedutil
    volts: 1.2 V ext-clock: 100 MHz cores: 1: 3200 2: 2200 3: 2200 4: 2200
    5: 2200 6: 3700 7: 2200 8: 2200 9: 2200 10: 2200 11: 2200 12: 2200 13: 2200
    14: 2200 15: 2200 16: 2200 bogomips: 118447
  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: 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 mitigation: untrained return thunk; SMT vulnerable
  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
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT]
    vendor: XFX Speedster MERC 319 driver: amdgpu v: kernel arch: RDNA-2
    code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4
    speed: 16 GT/s lanes: 16 ports: active: DP-1,DP-2 empty: DP-3,HDMI-A-1
    bus-ID: 28:00.0 chip-ID: 1002:73bf class-ID: 0300
  Device-2: Microsoft LifeCam HD-3000 driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-10:11
    chip-ID: 045e:0779 class-ID: 0102
  Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.1
    compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 5760x1080 s-dpi: 96 s-size: 1524x285mm (60.00x11.22")
    s-diag: 1550mm (61.04")
  Monitor-1: DP-1 mapped: DisplayPort-0 pos: primary,left
    model: Samsung C49HG9x serial: <filter> built: 2019 res: 3840x1080 hz: 100
    dpi: 81 gamma: 1.2 size: 1200x340mm (47.24x13.39") diag: 1242mm (48.9")
    modes: max: 3840x1080 min: 720x400
  Monitor-2: DP-2 mapped: DisplayPort-1 pos: right model: Toshiba TOSHIBA-TV
    serial: <filter> built: 2012 res: 1920x1080 hz: 50 dpi: 55 gamma: 1.2
    size: 885x498mm (34.84x19.61") diag: 1013mm (39.9") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  API: OpenGL v: 4.6 Mesa 23.0.3 renderer: AMD Radeon RX 6900 XT (navi21
    LLVM 15.0.7 DRM 3.49 6.1.30-1-MANJARO) direct-render: Yes
Audio:
  Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 28:00.1 chip-ID: 1002:ab28
    class-ID: 0403
  Device-2: AMD Family 17h HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 2a:00.3 chip-ID: 1022:1457 class-ID: 0403
  Device-3: Microsoft LifeCam HD-3000 driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-10:11
    chip-ID: 045e:0779 class-ID: 0102
  Device-4: C-Media BIRD UM1 driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-7:10
    chip-ID: 0d8c:0134 class-ID: 0300
  API: ALSA v: k6.1.30-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: 0.3.70 status: n/a (root, process) with: wireplumber
    status: active tools: pw-cli,wpctl
  Server-3: PulseAudio v: 16.1 status: active (root, process)
    with: pulseaudio-alsa type: plugin tools: pacat,pactl
Network:
  Device-1: Realtek RTL8111/8168/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: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Device-2: Intel driver: N/A pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A
    bus-ID: 25:00.0 chip-ID: 8086:093c class-ID: 0280
  WAN IP: <filter>
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
    v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-4:7
    chip-ID: 0a12:0001 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 5.08 TiB used: 19.14 GiB (0.4%)
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Corsair model: Force MP300
    size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 15.8 Gb/s
    lanes: 2 tech: SSD serial: <filter> fw-rev: E8FM11.7 temp: 48.9 C
    scheme: GPT
  SMART: yes health: PASSED on: 1y 46d 12h cycles: 1,039
    read-units: 24,794,916 [12.6 TB] written-units: 39,656,996 [20.3 TB]
  ID-2: /dev/sda maj-min: 8:0 vendor: PNY model: CS900 480GB SSD
    family: Driven SSDs size: 447.13 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.2 speed: 6.0 Gb/s tech: SSD serial: <filter>
    fw-rev: 0KB3 temp: 33 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 57d 15h cycles: 739
    written: 3104 GiB
  ID-3: /dev/sdb maj-min: 8:16 vendor: Crucial model: CT1000MX500SSD1
    family: Micron Client SSDs size: 931.51 GiB block-size: physical: 4096 B
    logical: 512 B sata: 3.3 speed: 6.0 Gb/s tech: SSD serial: <filter>
    fw-rev: 023 temp: 36 C scheme: MBR
  SMART: yes state: enabled health: PASSED on: 123d 17h cycles: 4192
    written: 5.71 TiB Old-Age: UDMA CRC errors: 147
  ID-4: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 860 EVO 500GB
    family: based SSDs size: 465.76 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.1 speed: 6.0 Gb/s tech: SSD serial: <filter>
    fw-rev: 1B6Q temp: 28 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 203d 15h cycles: 1254
    written: 3.93 TiB
  ID-5: /dev/sdd maj-min: 8:48 vendor: PNY model: CS900 480GB SSD
    family: Driven SSDs size: 447.13 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.2 speed: 6.0 Gb/s tech: SSD serial: <filter>
    fw-rev: 0KB3 temp: 33 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 57d 11h cycles: 738
    written: 4642 GiB
  ID-6: /dev/sde maj-min: 8:64 model: TUF ESD-T1A size: 1.82 TiB block-size:
    physical: 512 B logical: 512 B type: USB rev: 2.1 spd: 480 Mb/s lanes: 1
    mode: 2.0 tech: N/A serial: <filter> fw-rev: 1.00 scheme: GPT
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-7: /dev/sdf maj-min: 8:80 model: USB3.1 NVME SATA size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B type: USB rev: 2.1 spd: 480 Mb/s
    lanes: 1 mode: 2.0 tech: SSD serial: <filter> drive serial: <filter>
    fw-rev: 1.00 drive-rev: P2CR033 temp: 26 Celsius C scheme: GPT
  SMART: yes health: PASSED on: 144d 0h cycles: 1,623
    read-units: 5,426,504 [2.77 TB] written-units: 7,570,583 [3.87 TB]
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 27.18 GiB size: 26.58 GiB (97.81%) used: 19.12 GiB (71.9%)
    fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p5 maj-min: 259:5 label: N/A
    uuid: c3874422-fb47-4b74-8a48-5d92db94cc9d
  ID-2: /boot/efi raw-size: 500 MiB size: 499 MiB (99.80%)
    used: 18.5 MiB (3.7%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
    maj-min: 259:1 label: N/A uuid: CB13-FDFE
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/nvme0n1p2 maj-min: 259:2 size: 83.13 GiB fs: ntfs
    label: Nana's Memory [NVME] uuid: DC08F6FA08F6D30E
  ID-2: /dev/nvme0n1p3 maj-min: 259:3 size: 500 MiB fs: vfat label: N/A
    uuid: CB16-F5FA
  ID-3: /dev/nvme0n1p4 maj-min: 259:4 size: 500 MiB fs: N/A label: N/A
    uuid: N/A
  ID-4: /dev/sda2 maj-min: 8:2 size: 447.11 GiB fs: ntfs
    label: ex Nana's VR [SSD] uuid: 529ECC199ECBF38F
  ID-5: /dev/sdb1 maj-min: 8:17 size: 931.51 GiB fs: ntfs
    label: Nana's VR [SSD] uuid: 50FA3D72FA3D5586
  ID-6: /dev/sdc1 maj-min: 8:33 size: 16 MiB fs: N/A label: N/A uuid: N/A
  ID-7: /dev/sdc2 maj-min: 8:34 size: 465.75 GiB fs: ntfs label: Nouveau nom
    uuid: 7E28BA3128B9E873
  ID-8: /dev/sdd2 maj-min: 8:50 size: 447.11 GiB fs: ntfs
    label: Nana's Data [SSD] uuid: 2AA0920CA091DE9F
  ID-9: /dev/sde1 maj-min: 8:65 size: 16 MiB fs: N/A label: N/A uuid: N/A
  ID-10: /dev/sde2 maj-min: 8:66 size: 1.82 TiB fs: ntfs label: Lied's Backup
    uuid: 4CFC4945FC492B12
  ID-11: /dev/sdf2 maj-min: 8:82 size: 931.5 GiB fs: ntfs label: Nana's
    Games [NVME USB.C] uuid: 561013021012E92F
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
  Hub-2: 1-1:3 info: VIA Labs USB2.0 Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 2109:2817
    class-ID: 0900
  Device-1: 1-1.2:6 info: ASUSTek TUF Gaming Jet-A1 type: mass storage
    driver: usb-storage interfaces: 1 rev: 2.1 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 power: 500mA chip-ID: 0b05:1a8a class-ID: 0806
    serial: <filter>
  Device-2: 1-2:4 info: Realtek RTL9210 M.2 NVME Adapter type: mass storage
    driver: usb-storage interfaces: 1 rev: 2.1 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 power: 500mA chip-ID: 0bda:9210 class-ID: 0806
    serial: <filter>
  Device-3: 1-3:5 info: Maxxter Wireless Receiver type: mouse,keyboard
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 50mA chip-ID: 248a:8368 class-ID: 0301
  Device-4: 1-4:7 info: Cambridge Silicon Radio Bluetooth Dongle (HCI mode)
    type: bluetooth driver: btusb interfaces: 2 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 0a12:0001
    class-ID: e001
  Device-5: 1-7:10 info: C-Media BIRD UM1 type: audio,HID
    driver: hid-generic,snd-usb-audio,usbhid interfaces: 3 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 0d8c:0134 class-ID: 0300
  Device-6: 1-10:11 info: Microsoft LifeCam HD-3000 type: video,audio
    driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA
    chip-ID: 045e:0779 class-ID: 0102
  Hub-3: 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-4: 2-1:2 info: VIA Labs USB3.0 Hub ports: 4 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 2109:0817
    class-ID: 0900
  Hub-5: 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
  Device-1: 3-2:2 info: Elgato Systems GmbH Stream Deck MK.2 type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA
    chip-ID: 0fd9:0080 class-ID: 0300 serial: <filter>
  Hub-6: 3-3:3 info: Manufacturer hub ports: 4 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA chip-ID: 0a05:7211
    class-ID: 0900
  Device-1: 3-3.1:5 info: Holtek E-Signal LUOM G10 Mechanical Gaming Mouse
    type: mouse,HID driver: hid-generic,usbhid interfaces: 3 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 04d9:a09f class-ID: 0300
  Device-2: 3-3.2:8 info: Megawin Defender Gaming Keyboard type: keyboard
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s (183 KiB/s)
    lanes: 1 mode: 1.0 power: 100mA chip-ID: 0e6a:02c0 class-ID: 0301
  Hub-7: 3-4:4 info: Manufacturer hub ports: 4 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA chip-ID: 0a05:7211
    class-ID: 0900
  Device-1: 3-4.2:6 info: QinHeng CH340 serial converter
    type: <vendor specific> driver: ch341,ch341-uart interfaces: 1 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
    chip-ID: 1a86:7523 class-ID: ff00
  Device-2: 3-4.4:7 info: Saitek PLC X52 Pro Flight Control System 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: 230mA chip-ID: 06a3:0762 class-ID: 0300
  Hub-8: 4-0:1 info: super-speed hub ports: 4 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 40.5 C mobo: N/A gpu: amdgpu temp: 47.0 C
    mem: 46.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Info:
  Processes: 354 Uptime: 45m wakeups: 0 Init: systemd v: 252 default: graphical
  tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7 Packages: pm: pacman
  pkgs: 1173 libs: 359 tools: pamac pm: flatpak pkgs: 0 Shell: Zsh (sudo)
  v: 5.9 default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.27

I use Linux since a long time now. But new user on Arch based. From now on, I have a few error on every single distro I had installed. But on my computer, my newly installed Manjaro seems to be f*ck up.

Everything is running OK. Graphics Cards, some video games, audio, bluetooth and other.

But, every 1 or 5 hours (random), the system is shutting down (crash) and reboot. Just like if I had shut down the Power Supply.

I had check the logs, and I saw a LOT of things. But I dunno which one is serious and which one is just a warning.

I saw a lot of manners to see all error logs. So I use the KSystemlog to check out.

This is what I get :

30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Transmitter ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00001041/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 6] BadTLP                
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [12] Timeout               
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00001040/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 6] BadTLP                
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [12] Timeout               
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000081/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 7] BadDLLP               
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000001/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000001/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000001/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000081/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 7] BadDLLP               
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000001/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000001/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000081/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 7] BadDLLP               
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000001/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000081/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 7] BadDLLP               
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000001/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000001/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000001/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000081/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 7] BadDLLP               
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000081/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 7] BadDLLP               
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000081/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 7] BadDLLP               
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000081/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 7] BadDLLP               
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000001/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000001/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000001/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000001/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000081/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 7] BadDLLP               
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000001/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000081/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 7] BadDLLP               
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000001/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000081/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 7] BadDLLP               
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000001/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first
30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:   device [1022:43c7] error status/mask=00000001/00002000
30/07/2023 16:21	kernel	pcieport 0000:20:04.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
30/07/2023 16:21	kernel	pci 0000:25:00.0:   device [8086:093c] error status/mask=00000001/00000000
30/07/2023 16:21	kernel	pci 0000:25:00.0:    [ 0] RxErr                  (First)
30/07/2023 16:21	kernel	pci 0000:25:00.0: AER:   Error of this Agent is reported first

If someone can help me to understand. Maybe this is some basic error, but I just wanna know WHAT is causing the shutdown.

Thanks

[andreas85]

Welcome to Manjaro!

1. Please read the information behind this link. It will help you to post necessary information.

[HowTo] Request support

Difficulty: ★☆☆☆☆ Strong of its many members, the Manjaro support forum can provide you help whenever you have an issue with your Manjaro installation. But in order to work efficiently, we shall also ask you to follow three major points. Provide context Simply signaling an issue is rarely enough to understand how it occurred. It is thus important to provide details on how it happened: Detail prior actions leading to the issue. List solutions and guides you already tried, with links when…

2. Please press the three dots … below your post and then press the

• If you give us information about your system, we can see what we’re talking about and make better suggestions.
• You can do this by using inxi in a terminal or in console.

sudo 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.

3. 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.

[HowTo] Post command output and file content as formatted text

Difficulty: ★☆☆☆☆ Formatting differences Discourse – this forum’s engine – uses Markdown to format its posts, and removes “unnecessary” whitespace. Terminal commands often produce output formatted so that they are better readable by the user, taking advantage of the monospaced font used. Programming code often rely on indentation to make it more readable. Using preformatting in Markdown Markdown includes a pattern to provide preformatting when necessary. You only need to put the part to f…

Have you already for your problem in the forum ? (Wisdom lies in asking → listening → reading )

[Mirdarthos]

Hi @OverSu, and welcome!!!

a Better way to inspect the logs would be journalctl as it will allow you to pinpoint what is the problem, and by what it’s caused.

Please provide the output of:

sudo journalctl --boot=-1 --priority=4 --no-pager

Where:

• sudo will run it as root;
• --boot=-1 will limit the output to be messsages from the previous boot. Feel free to adjust this as neccessary: -1 for the previous boot, -2 for the one before that, -3 for the one before that, and so on and so forth. Feel free to adjust this as neccesssary;
• --priority=4 will limit the messages to be warnings and errors only;
• --no-pager will format the output nicely for use here, on the forum.

---

I wanted to give you a tip on providing terminal output, but I see you know about it already.

But, please, see the rest anyway:

• [HowTo] Provide System Information,
• [HowTo] Post screenshots and links,
• [HowTo] Request support, and
• [HowTo] Post command output and file content as formatted text.

Please also note and heed: Forum Rules - Manjaro

Hope you manage!

---

Tip:

To provide terminal output, copy the text you wish to share, and paste it here, surrounded by three (3) backticks, a.k.a grave accents. Like this:

```
pasted text
```

Or three (3) tilde signs, like this:

~~~
pasted text
~~~

This will just cause it to be rendered like this:

Portaest sed
elementum
cursus nisl nisi
hendrerit ac quis
sit
adipiscing
tortor sit leo commodo.

Instead of like this:

Portaest sed elementum cursus nisl nisi hendrerit ac quis sit adipiscing tortor sit leo commodo.

Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.

Thereby improving legibility and making it much easier for those trying to be of assistance.

---

Additionally

If your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:

LC_ALL=C bluetoothctl

This will just cause the terminal output to be in English, making it easier to understand and debug.

Please edit your post accordingly.

[brahma]

@OverSu

30/07/2023 16:21	kernel	pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:25:00.0
30/07/2023 16:21	kernel	pcieport 0000:20:04.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)

you have these errors, which are causing the crashes… i had them too… so lets fix them… open this:
kate /etc/default/grub
and edit this line: GRUB_CMDLINE_LINUX_DEFAULT - inside the quotes “” add this parameter:
pci=nommconf
dont remove any parameters, just add them to the existing one, then save the file, and run this:
sudo update-grub
reboot and check again logs, if the aer/pci logs are gone…

[OverSu]

Thanks to @Mirdarthos I had see all the errors.
Thanks to @brahma I had fix the AER/pcie errors.
But @brahma , what did you just do ?

Now, this is what I get

-- Boot 109824c4da4143ae867ad7d617666b38 --
juil. 30 17:12:24 NANA kernel: tpm tpm0: AMD fTPM version 0x3000700000003 causes system stutter; hwrng disabled
juil. 30 17:12:24 NANA kernel: blacklist: Problem blacklisting hash (-13)
juil. 30 17:12:24 NANA kernel: blacklist: Problem blacklisting hash (-13)
juil. 30 17:12:24 NANA kernel: blacklist: Problem blacklisting hash (-13)
juil. 30 17:12:24 NANA kernel: blacklist: Problem blacklisting hash (-13)
juil. 30 17:12:24 NANA kernel: blacklist: Problem blacklisting hash (-13)
juil. 30 17:12:24 NANA kernel: blacklist: Problem blacklisting hash (-13)
juil. 30 17:12:24 NANA kernel: ata2.00: supports DRM functions and may not be fully accessible
juil. 30 17:12:24 NANA kernel: ata2.00: supports DRM functions and may not be fully accessible
juil. 30 17:12:24 NANA kernel: ata5.00: supports DRM functions and may not be fully accessible
juil. 30 17:12:24 NANA kernel: ata5.00: supports DRM functions and may not be fully accessible
juil. 30 17:12:23 NANA systemd-vconsole-setup[387]: Failed to import credentials, ignoring: Aucun fichier ou dossier de ce type
juil. 30 17:12:25 NANA kernel: amdgpu 0000:28:00.0: amdgpu: PSP runtime database doesn't exist
juil. 30 17:12:25 NANA kernel: amdgpu 0000:28:00.0: amdgpu: PSP runtime database doesn't exist
juil. 30 17:12:26 NANA kernel: usb 1-1.3: device descriptor read/64, error -32
juil. 30 17:12:26 NANA kernel: usb 1-1.3: device descriptor read/64, error -32
juil. 30 17:12:27 NANA kernel: usb 1-1.3: device descriptor read/64, error -32
juil. 30 17:12:27 NANA kernel: usb 1-1.3: device descriptor read/64, error -32
juil. 30 17:12:28 NANA kernel: hid-generic 0003:0D8C:0134.000A: No inputs registered, leaving
juil. 30 17:12:28 NANA bluetoothd[664]: src/plugin.c:plugin_init() System does not support csip plugin
juil. 30 17:12:28 NANA bluetoothd[664]: src/plugin.c:plugin_init() System does not support vcp plugin
juil. 30 17:12:28 NANA bluetoothd[664]: src/plugin.c:plugin_init() System does not support mcp plugin
juil. 30 17:12:28 NANA bluetoothd[664]: src/plugin.c:plugin_init() System does not support bass plugin
juil. 30 17:12:28 NANA bluetoothd[664]: src/plugin.c:plugin_init() System does not support bap plugin
juil. 30 17:12:29 NANA kernel: amdgpu 0000:28:00.0: amdgpu: SMU driver if version not matched
juil. 30 17:12:29 NANA kernel: amdgpu: SRAT table not found
juil. 30 17:12:33 NANA ksplashqml[765]: file:///usr/share/plasma/look-and-feel/org.manjaro.breath.desktop/contents/splash/Splash.qml:49: ReferenceError: maxWidth is not defined
juil. 30 17:12:33 NANA ksplashqml[765]: file:///usr/share/plasma/look-and-feel/org.manjaro.breath.desktop/contents/splash/Splash.qml:49: ReferenceError: maxWidth is not defined
juil. 30 17:12:33 NANA ksplashqml[765]: file:///usr/share/plasma/look-and-feel/org.manjaro.breath.desktop/contents/splash/Splash.qml:81:29: Unable to assign int to QEasingCurve
juil. 30 17:12:33 NANA ksplashqml[765]: file:///usr/share/plasma/look-and-feel/org.manjaro.breath.desktop/contents/splash/Splash.qml:81:29: Unable to assign int to QEasingCurve
juil. 30 17:12:33 NANA baloo_file[785]: QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.18'
juil. 30 17:12:33 NANA baloo_file[785]: QDBusConnection: name 'org.freedesktop.UPower' had owner '' but we thought it was ':1.21'
juil. 30 17:12:33 NANA ksmserver[844]: Qt: Session management error: networkIdsList argument is NULL
juil. 30 17:12:33 NANA kded5[846]: org.kde.libkbolt: Failed to connect to Bolt manager DBus interface:
juil. 30 17:12:33 NANA kwin_x11[847]: kwin_xkbcommon: XKB: inet:323:58: unrecognized keysym "XF86EmojiPicker"
juil. 30 17:12:33 NANA kwin_x11[847]: kwin_xkbcommon: XKB: inet:324:58: unrecognized keysym "XF86Dictate"
juil. 30 17:12:33 NANA ksmserver[844]: QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.13'
juil. 30 17:12:34 NANA plasmashell[880]: Checking screens: available: (QScreen(0x564f7453e1e0, name="DisplayPort-0"), QScreen(0x564f7453e2d0, name="DisplayPort-1")) redundant: QHash() fake: QSet() all: (QScreen(0x564f7453e1e0, name="DisplayPort-0"), QScreen(0x564f7453e2d0, name="DisplayPort-1"))
juil. 30 17:12:34 NANA plasmashell[880]: Checking screens: available: (QScreen(0x564f7453e1e0, name="DisplayPort-0"), QScreen(0x564f7453e2d0, name="DisplayPort-1")) redundant: QHash() fake: QSet() all: (QScreen(0x564f7453e1e0, name="DisplayPort-0"), QScreen(0x564f7453e2d0, name="DisplayPort-1"))
juil. 30 17:12:34 NANA backlighthelper[970]: org.kde.powerdevil: no kernel backlight interface found
juil. 30 17:12:34 NANA org_kde_powerdevil[916]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
juil. 30 17:12:34 NANA kded5[846]: g_settings_set_value: key 'scaling-factor' in 'org.gnome.desktop.interface' expects type 'u', but a GVariant of type 'i' was given
juil. 30 17:12:34 NANA org_kde_powerdevil[916]: org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed
juil. 30 17:12:34 NANA plasmashell[880]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
juil. 30 17:12:34 NANA plasmashell[880]: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.
juil. 30 17:12:34 NANA plasmashell[880]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
juil. 30 17:12:34 NANA plasmashell[880]: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.
juil. 30 17:12:34 NANA org_kde_powerdevil[916]: org.kde.powerdevil: Handle button events action could not check for screen configuration
juil. 30 17:12:34 NANA org_kde_powerdevil[916]: org.kde.powerdevil: The profile  "AC" tried to activate "DimDisplay" a non-existent action. This is usually due to an installation problem, a configuration problem, or because the action is not supported
juil. 30 17:12:34 NANA org_kde_powerdevil[916]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
juil. 30 17:12:34 NANA kded5[846]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
juil. 30 17:12:34 NANA wireplumber[971]: <WpPortalPermissionStorePlugin:0x563eb7953500> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
juil. 30 17:12:34 NANA wireplumber[971]: <WpPortalPermissionStorePlugin:0x563eb7953500> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
juil. 30 17:12:35 NANA plasmashell[880]: org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout
juil. 30 17:12:35 NANA plasmashell[880]: org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout
juil. 30 17:12:35 NANA kioslave5[1168]: QObject::connect: No such slot DesktopProtocol::_k_slotRedirection(KIO::Job *, QUrl)
juil. 30 17:12:35 NANA kioslave5[1168]: QObject::connect: No such slot DesktopProtocol::_k_slotRedirection(KIO::Job *, QUrl)
juil. 30 17:12:36 NANA plasmashell[880]: Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
juil. 30 17:12:36 NANA plasmashell[880]: org.kde.plasma.kicker: Entry is not valid "org.kde.kontact.desktop" QSharedPointer(0x564f757a06b0)
juil. 30 17:12:36 NANA plasmashell[880]: org.kde.plasma.kicker: Entry is not valid "ktp-contactlist.desktop" QSharedPointer(0x564f757a0840)
juil. 30 17:12:36 NANA plasmashell[880]: org.kde.plasma.kicker: Entry is not valid "org.kde.discover.desktop" QSharedPointer(0x564f757a12f0)
juil. 30 17:12:36 NANA plasmashell[880]: org.kde.plasma.kicker: Entry is not valid "org.kde.kontact.desktop" QSharedPointer(0x564f757a1c30)
juil. 30 17:12:36 NANA plasmashell[880]: org.kde.plasma.kicker: Entry is not valid "ktp-contactlist.desktop" QSharedPointer(0x564f757a12f0)
juil. 30 17:12:36 NANA plasmashell[880]: org.kde.plasma.kicker: Entry is not valid "org.kde.discover.desktop" QSharedPointer(0x564f757a1220)
juil. 30 17:12:37 NANA plasmashell[880]: Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationHeader.qml"
juil. 30 17:12:37 NANA plasmashell[880]: Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/ThumbnailStrip.qml"
juil. 30 17:12:38 NANA plasmashell[880]: file:///usr/share/plasma/plasmoids/org.kde.plasma.networkmanagement/contents/ui/main.qml:95: TypeError: Cannot read property 'airplaneModeAvailable' of null
juil. 30 17:12:38 NANA kwin_x11[847]: kwin_core: XCB error: 152 (BadDamage), sequence: 4106, resource id: 14680102, major code: 143 (DAMAGE), minor code: 3 (Subtract)
juil. 30 17:12:38 NANA kwin_x11[847]: kwin_core: XCB error: 3 (BadWindow), sequence: 4129, resource id: 4194345, major code: 129 (SHAPE), minor code: 6 (Input)
juil. 30 17:12:38 NANA plasmashell[880]: file:///usr/share/plasma/plasmoids/org.kde.plasma.networkmanagement/contents/ui/main.qml:95: TypeError: Cannot read property 'airplaneModeAvailable' of null
juil. 30 17:12:38 NANA plasmashell[880]: Both point size and pixel size set. Using pixel size.
juil. 30 17:12:38 NANA plasmashell[880]: file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/Tooltip.qml:78:9: QML GridLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth"
juil. 30 17:12:38 NANA plasmashell[880]: org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout
juil. 30 17:12:38 NANA plasmashell[880]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:18:1: QML MouseArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth"
juil. 30 17:12:38 NANA plasmashell[880]: org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout
juil. 30 17:12:38 NANA kioslave5[1168]: QObject::connect: No such slot DesktopProtocol::_k_slotRedirection(KIO::Job *, QUrl)
juil. 30 17:12:38 NANA plasmashell[880]: QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
juil. 30 17:12:38 NANA plasmashell[880]: file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:61:17: Unable to assign [undefined] to int
juil. 30 17:12:38 NANA kioslave5[1168]: QObject::connect: No such slot DesktopProtocol::_k_slotRedirection(KIO::Job *, QUrl)
juil. 30 17:12:38 NANA pulseaudio[1201]: stat('/etc/pulse/default.pa.d'): Aucun fichier ou dossier de ce type
juil. 30 17:12:39 NANA plasmashell[880]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
juil. 30 17:12:39 NANA plasmashell[880]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
juil. 30 17:12:39 NANA plasmashell[880]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
juil. 30 17:12:40 NANA plasmashell[880]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
juil. 30 17:12:40 NANA plasmashell[880]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
juil. 30 17:12:41 NANA plasmashell[880]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
juil. 30 17:12:41 NANA plasmashell[880]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
juil. 30 17:12:41 NANA plasmashell[880]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
juil. 30 17:12:42 NANA plasmashell[880]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
juil. 30 17:12:42 NANA plasmashell[880]: file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/DeviceItem.qml:36:5: Unable to assign [undefined] to bool
juil. 30 17:12:42 NANA plasmashell[880]: file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/DeviceItem.qml:35:5: Unable to assign [undefined] to bool
juil. 30 17:12:42 NANA plasmashell[880]: file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/DeviceItem.qml:36:5: Unable to assign [undefined] to bool
juil. 30 17:12:42 NANA plasmashell[880]: file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/DeviceItem.qml:35:5: Unable to assign [undefined] to bool
juil. 30 17:12:42 NANA plasmashell[880]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
juil. 30 17:12:43 NANA plasmashell[880]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
juil. 30 17:12:44 NANA plasmashell[880]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
juil. 30 17:12:45 NANA plasmashell[880]: kf.sonnet.core: No language dictionaries for the language: "en_US"
juil. 30 17:12:45 NANA plasmashell[880]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
juil. 30 17:12:47 NANA kdesud[1292]: kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Copyright (c) 1999,2000 Geert Jansen" msgid_plural: "" msgctxt: ""
juil. 30 17:12:47 NANA kdesud[1292]: kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Daemon used by kdesu" msgid_plural: "" msgctxt: ""
juil. 30 17:12:47 NANA kdesud[1292]: kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "KDE su daemon" msgid_plural: "" msgctxt: ""
juil. 30 17:12:47 NANA kdesud[1292]: kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Author" msgid_plural: "" msgctxt: ""
juil. 30 17:12:47 NANA kdesud[1292]: kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Geert Jansen" msgid_plural: "" msgctxt: ""
juil. 30 17:13:18 NANA konsole[1322]: kf.xmlgui: Shortcut for action  "" "Afficher les commandes rapides" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
juil. 30 17:13:18 NANA konsole[1322]: kf.xmlgui: Shortcut for action  "" "Afficher le gestionnaire de clés SSH" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.

[linux-aarhus]

Custom theming?

Heat - dirty radiator grid inside computer?

@OverSu

Swap:
  Alert: No swap data was found.

Even you have enough RAM you should consider at least a 2GB swap.

[brahma]

@OverSu

Now, this is what I get

those are normal logs…
now test if you still have the crashes… also pay attention, if there are some possible new issues… and also clear your logs. First check the size:
journalctl --disk-usage
and clear it:

sudo journalctl --rotate
sudo journalctl -m --vacuum-time=1s

[OverSu]

This is the new error since the last crash (last night)

NANA kernel: blacklist: Problem blacklisting hash (-13)
NANA kernel: hid-generic 0003:0D8C:0134.000A: No inputs registered, leaving
NANA kernel: Bluetooth: hci0: SCO packet for unknown connection handle 69
NANA kernel: watchdog: watchdog0: watchdog did not stop!

Then it’s crashed.

Thanks again for your quick help.

[brahma]

so replace the pci=nommconf parameter:
kate /etc/default/grub
and edit this line: GRUB_CMDLINE_LINUX_DEFAULT - inside the quotes “” add this parameter:
pci=nomsi
dont remove any parameters, just add them to the existing one, then save the file, and run this:
sudo update-grub
reboot and check logs for the pci/aer errors…
if there are any, see if it crashes again… if it does, provide the logs, but provide the full output:

@Mirdarthos

sudo journalctl --boot=-1 --priority=4 --no-pager