Issues with fresh installation of Manjaro

axoxx · 28 June 2022 04:52

I installed manjaro on my Asus laptop 2 days ago. Here are basic details about my laptop-

Kernel: 5.15.49-1-MANJARO
                               CPU: Intel i5-7200U (4) @ 3.100GHz 
                               GPU: NVIDIA GeForce MX110 
                               GPU: Intel HD Graphics 620 
                               Storage- 220 GB SSD
                               RAM-4GB

And additional hardware information - linux-hardware .org/ ?probe=0ba0fc4089 (remove space as i cant post links)

I have been facing below issues-

Laptop freezes while closing VLC player. Also resuming a paused video on VLC isnt smooth. The pamac gui also lags alot. While searching for packages, or while browsing packages, gui lags. Sometimes laptop freezes and i can only move my mouse. Everytime i have to hard reboot.

2.Battery overheats and discharges quickly. When i used windows, a full charge would go on for 3 hours and battery wouldnt overheat unless i used applications such as photoshop. But at linux a full charge is only good for 40-50 minutes. And the battery is always hot. (I repalced my original ASUS battery with a new one 7-8 months ago)

When i close my laptop lid, the laptop shuts down instead of going to sleep.
Generally it takes 2 secs to shut down. But yesterday night, it took 4-5 min to shut down completely and was showing Failed to start Journal Service.

My inxi output-

System:
  Kernel: 5.15.49-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64
    root=UUID=49a4081c-ad21-4aab-86b6-46fffa513a0f rw quiet apparmor=1
    security=apparmor udev.log_priority=3
  Desktop: KDE Plasma v: 5.24.5 tk: Qt v: 5.15.5 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: X507UB v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: X507UB v: 1.0 serial: <superuser required>
    UEFI: American Megatrends v: X507UB.305 date: 05/22/2019
Battery:
  ID-1: BAT0 charge: 24.1 Wh (88.9%) condition: 27.1/30.2 Wh (89.7%)
    volts: 10.8 min: 10.8 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A
    status: charging cycles: 414
Memory:
  RAM: total: 3.71 GiB used: 2.2 GiB (59.2%)
  RAM Report:
    permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake
    note: check gen: core 7 built: 2017 process: Intel 14nm family: 6
    model-id: 0x8E (142) stepping: 9 microcode: 0xF0
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
    L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
    L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 3099 high: 3100 min/max: 400/3100 scaling:
    driver: intel_pstate governor: performance cores: 1: 3100 2: 3100 3: 3100
    4: 3098 bogomips: 21607
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush clflushopt
    cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts
    epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu fsgsbase fxsr
    ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs ida intel_pt invpcid
    invpcid_single lahf_lm lm mca mce md_clear mmx monitor movbe mpx msr mtrr
    nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pln
    pni popcnt pse pse36 pti pts rdrand rdseed rdtscp rep_good sdbg sep smap
    smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow
    tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic xgetbv1 xsave
    xsavec xsaveopt xsaves xtopology xtpr
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf
    mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  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 mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel HD Graphics 620 vendor: ASUSTeK driver: i915 v: kernel
    arch: Gen9.5 process: Intel 14nm built: 2016-20 ports: active: eDP-1
    empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:5916 class-ID: 0300
  Device-2: NVIDIA GM108M [GeForce MX110] vendor: ASUSTeK driver: nvidia
    v: 515.48.07 alternate: nouveau,nvidia_drm non-free: 515.xx+
    status: current (as of 2022-06) arch: Maxwell process: TSMC 28nm
    built: 2014-19 pcie: gen: 1 speed: 2.5 GT/s lanes: 4 link-max: gen: 3
    speed: 8 GT/s bus-ID: 01:00.0 chip-ID: 10de:174e class-ID: 0302
  Device-3: IMC Networks USB2.0 VGA UVC WebCam type: USB driver: uvcvideo
    bus-ID: 1-6:2 chip-ID: 13d3:5a01 class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 21.1.3 compositor: kwin_x11 driver: X:
    loaded: modesetting,nvidia alternate: fbdev,nouveau,nv,vesa gpu: i915
    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")
  Monitor-1: eDP-1 model: ChiMei InnoLux 0x15f5 built: 2017 res: 1920x1080
    hz: 60 dpi: 142 gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5")
    ratio: 16:9 modes: 1920x1080
  OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 22.1.2
    direct render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel alternate: snd_soc_skl bus-ID: 00:1f.3
    chip-ID: 8086:9d71 class-ID: 0403
  Sound Server-1: ALSA v: k5.15.49-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.21 running: no
  Sound Server-3: PulseAudio v: 16.1 running: yes
  Sound Server-4: PipeWire v: 0.3.52 running: yes
Network:
  Device-1: Realtek RTL8723BE PCIe Wireless Network Adapter vendor: Lite-On
    driver: rtl8723be v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000
    bus-ID: 02:00.0 chip-ID: 10ec:b723 class-ID: 0280
  IF: wlp2s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  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: 1-8:3 chip-ID: 0bda:b719 class-ID: e001 serial: <filter>
  Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 223.57 GiB used: 61.84 GiB (27.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Transcend model: TS240GMTS820S
    size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 7B0 scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 223.27 GiB size: 218.71 GiB (97.96%)
    used: 61.84 GiB (28.3%) fs: ext4 dev: /dev/sda2 maj-min: 8:2 label: N/A
    uuid: 49a4081c-ad21-4aab-86b6-46fffa513a0f
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 312 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1 label: NO_LABEL
    uuid: B617-88DA
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 GiB used: 694.2 MiB (16.9%) priority: -2
    file: /swapfile
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-6:2 info: IMC Networks USB2.0 VGA UVC WebCam type: Video
    driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s power: 500mA
    chip-ID: 13d3:5a01 class-ID: 0e02 serial: <filter>
  Device-2: 1-8:3 info: Realtek Bluetooth Radio type: Bluetooth
    driver: btusb interfaces: 2 rev: 2.1 speed: 12 Mb/s power: 500mA
    chip-ID: 0bda:b719 class-ID: e001 serial: <filter>
  Hub-2: 2-0:1 info: Super-speed hub ports: 6 rev: 3.0 speed: 5 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
Sensors:
  System Temperatures: cpu: 96.0 C pch: 60.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 4000
Info:
  Processes: 218 Uptime: 42m wakeups: 2 Init: systemd v: 251
  default: graphical tool: systemctl Compilers: gcc: 12.1.0 clang: 13.0.1
  Packages: 1312 pacman: 1300 lib: 370 flatpak: 9 snap: 3 Shell: Zsh v: 5.9
  default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.19

xrandr output:

Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm
   1920x1080     60.01*+  60.01    59.97    59.96    59.93  
   1680x1050     59.95    59.88  
   1400x1050     59.98  
   1600x900      59.99    59.94    59.95    59.82  
   1280x1024     60.02  
   1400x900      59.96    59.88  
   1280x960      60.00  
   1440x810      60.00    59.97  
   1368x768      59.88    59.85  
   1280x800      59.99    59.97    59.81    59.91  
   1280x720      60.00    59.99    59.86    59.74  
   1024x768      60.04    60.00  
   960x720       60.00  
   928x696       60.05  
   896x672       60.01  
   1024x576      59.95    59.96    59.90    59.82  
   960x600       59.93    60.00  
   960x540       59.96    59.99    59.63    59.82  
   800x600       60.00    60.32    56.25  
   840x525       60.01    59.88  
   864x486       59.92    59.57  
   700x525       59.98  
   800x450       59.95    59.82  
   640x512       60.02  
   700x450       59.96    59.88  
   640x480       60.00    59.94  
   720x405       59.51    58.99  
   684x384       59.88    59.85  
   640x400       59.88    59.98  
   640x360       59.86    59.83    59.84    59.32  
   512x384       60.00  
   512x288       60.00    59.92  
   480x270       59.63    59.82  
   400x300       60.32    56.34  
   432x243       59.92    59.57  
   320x240       60.05  
   360x202       59.51    59.13  
   320x180       59.84    59.32  
HDMI-1 disconnected (normal left inverted right x axis y axis)

Journalctl output:

Data from the specified boot (-1) is not available: No such boot ID in journal

Output of sudo journalctl -b0 -p4 :

Jun 28 10:47:02 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster systemd-journald[13629]: /dev/kmsg buffer overrun, some messages lost.
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster systemd-journald[13629]: /dev/kmsg buffer overrun, some messages lost.
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer,>
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Jun 28 10:47:08 asusmonster kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)

What should I do?

brahma · 28 June 2022 06:22

its this error whats causing the issue:

PCIe Bus Error: severity=Corrected,

it spams your logs with probably hundreds messages a second, and thats why you have the issue…
provide output from:
lspci
then we will fix it

zbe · 28 June 2022 06:24

Regarding journal errors: https://askubuntu.com/questions/863150/pcie-bus-error-severity-corrected-type-physical-layer-id-00e5receiver-id

andreas85 · 28 June 2022 07:00

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

gabriellewilson · 28 June 2022 19:53

thanks for sharing that tutorial. nice contribution.

axoxx · 29 June 2022 05:30

here is the output of lspci:

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 02)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 02)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)
00:1e.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO UART Controller #0 (rev 21)
00:1e.2 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO SPI Controller #0 (rev 21)
00:1e.6 SD Host controller: Intel Corporation Sunrise Point-LP Secure Digital IO Controller (rev 21)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC Controller/eSPI Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce MX110] (rev a2)
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter

brahma · 29 June 2022 06:44

Open this file:
kate /etc/default/grub
And edit this line: GRUB_CMDLINE_LINUX_DEFAULT - inside the quotes put this parameter:
pci=nomsi
dont remove any other parameters, just add it to the existing one. Save the file and run this command:
sudo update-grub
Reboot and see if it helped. If it didnt work, we try another parameter - there are 4 as a possible fix, so we have to try one at a time

axoxx · 29 June 2022 09:56

I have updated as you said. On bootup it shows only dev/sda/2 clean now and enters into DE. But problems with graphics persist. I had intel nvidia hybrid drivers: i uninstalled it and installed nvidia driver. But sill not happy with the results. Its kinda buggy and sometimes lags the system and i have to go to ctl+alt+f3 to kill everything.

Here is the journalctl output:

Jun 29 15:52:39 asusmonster kernel: [Firmware Bug]: TSC ADJUST: CPU0: -33244374 force to 0
Jun 29 15:52:39 asusmonster kernel: x86/cpu: SGX disabled by BIOS.
Jun 29 15:52:39 asusmonster kernel: [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all e>
Jun 29 15:52:39 asusmonster kernel:  #2
Jun 29 15:52:39 asusmonster kernel: MDS CPU bug present and SMT on, data leak possible. See https://w>
Jun 29 15:52:39 asusmonster kernel: MMIO Stale Data CPU bug present and SMT on, data leak possible. S>
Jun 29 15:52:39 asusmonster kernel:  #3
Jun 29 15:52:39 asusmonster kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jun 29 15:52:39 asusmonster kernel: hpet_acpi_add: no address or irqs in _CRS
Jun 29 15:52:39 asusmonster kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is in>
Jun 29 15:52:39 asusmonster kernel: sdhci-pci 0000:00:1e.6: failed to setup card detect gpio
Jun 29 15:52:40 asusmonster kernel: urandom_read_iter: 2 callbacks suppressed
Jun 29 15:52:40 asusmonster thermald[361]: NO RAPL sysfs present
Jun 29 15:52:40 asusmonster thermald[361]: Thermal DTS: No coretemp sysfs found
Jun 29 15:52:40 asusmonster thermald[361]: Thermal DTS or hwmon: No Zones present Need to configure m>
Jun 29 15:52:42 asusmonster kernel: bluetooth hci0: Direct firmware load for rtl_bt/rtl8723b_config.b>
Jun 29 15:52:42 asusmonster kernel: kauditd_printk_skb: 62 callbacks suppressed
Jun 29 15:52:44 asusmonster kernel: nvidia: loading out-of-tree module taints kernel.
Jun 29 15:52:44 asusmonster kernel: nvidia: module license 'NVIDIA' taints kernel.
Jun 29 15:52:44 asusmonster kernel: Disabling lock debugging due to kernel taint
Jun 29 15:52:44 asusmonster kernel: 
Jun 29 15:52:44 asusmonster kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  515.48.07  Fri Ma>
Jun 29 15:52:44 asusmonster kernel: NVRM: GPU 0000:01:00.0: Failed to enable MSI; falling back to PCI>
Jun 29 15:52:44 asusmonster kernel: ACPI Warning: \_SB.PCI0.RP01.PEGP._DSM: Argument #4 type mismatch>
Jun 29 15:52:48 asusmonster klauncher[838]: Connecting to deprecated signal QDBusConnectionInterface:>
Jun 29 15:52:49 asusmonster ksplashqml[818]: file:///usr/share/plasma/look-and-feel/org.manjaro.breat>
Jun 29 15:52:49 asusmonster ksplashqml[818]: file:///usr/share/plasma/look-and-feel/org.manjaro.breat>
Jun 29 15:52:49 asusmonster kcminit_startup[842]: QDBusConnection: error: could not send signal to se>
Jun 29 15:52:49 asusmonster kwin_x11[855]: Warning: Setting a new default format with a different ver>
Jun 29 15:52:49 asusmonster kwin_x11[855]: kwin_xkbcommon: XKB: inet:323:58: unrecognized keysym "XF8>
Jun 29 15:52:49 asusmonster kwin_x11[855]: kwin_xkbcommon: XKB: inet:324:58: unrecognized keysym "XF8>
Jun 29 15:52:49 asusmonster ksmserver[898]: Qt: Session management error: networkIdsList argument is >
Jun 29 15:52:50 asusmonster kwin_x11[855]: kwin_core: XCB error: 10 (BadAccess), sequence: 802, resou>

    ~  sudo journalctl -b0 -p4                                                    INT ✘  18s  
Jun 29 15:52:39 asusmonster kernel: [Firmware Bug]: TSC ADJUST: CPU0: -33244374 force to 0
Jun 29 15:52:39 asusmonster kernel: x86/cpu: SGX disabled by BIOS.
Jun 29 15:52:39 asusmonster kernel: [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all e>
Jun 29 15:52:39 asusmonster kernel:  #2
Jun 29 15:52:39 asusmonster kernel: MDS CPU bug present and SMT on, data leak possible. See https://w>
Jun 29 15:52:39 asusmonster kernel: MMIO Stale Data CPU bug present and SMT on, data leak possible. S>
Jun 29 15:52:39 asusmonster kernel:  #3
Jun 29 15:52:39 asusmonster kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jun 29 15:52:39 asusmonster kernel: hpet_acpi_add: no address or irqs in _CRS
Jun 29 15:52:39 asusmonster kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is in>
Jun 29 15:52:39 asusmonster kernel: sdhci-pci 0000:00:1e.6: failed to setup card detect gpio
Jun 29 15:52:40 asusmonster kernel: urandom_read_iter: 2 callbacks suppressed
Jun 29 15:52:40 asusmonster thermald[361]: NO RAPL sysfs present
Jun 29 15:52:40 asusmonster thermald[361]: Thermal DTS: No coretemp sysfs found
Jun 29 15:52:40 asusmonster thermald[361]: Thermal DTS or hwmon: No Zones present Need to configure m>
Jun 29 15:52:42 asusmonster kernel: bluetooth hci0: Direct firmware load for rtl_bt/rtl8723b_config.b>
Jun 29 15:52:42 asusmonster kernel: kauditd_printk_skb: 62 callbacks suppressed
Jun 29 15:52:44 asusmonster kernel: nvidia: loading out-of-tree module taints kernel.
Jun 29 15:52:44 asusmonster kernel: nvidia: module license 'NVIDIA' taints kernel.
Jun 29 15:52:44 asusmonster kernel: Disabling lock debugging due to kernel taint
Jun 29 15:52:44 asusmonster kernel: 
Jun 29 15:52:44 asusmonster kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  515.48.07  Fri Ma>
Jun 29 15:52:44 asusmonster kernel: NVRM: GPU 0000:01:00.0: Failed to enable MSI; falling back to PCI>
Jun 29 15:52:44 asusmonster kernel: ACPI Warning: \_SB.PCI0.RP01.PEGP._DSM: Argument #4 type mismatch>
Jun 29 15:52:48 asusmonster klauncher[838]: Connecting to deprecated signal QDBusConnectionInterface:>
Jun 29 15:52:49 asusmonster ksplashqml[818]: file:///usr/share/plasma/look-and-feel/org.manjaro.breat>
Jun 29 15:52:49 asusmonster ksplashqml[818]: file:///usr/share/plasma/look-and-feel/org.manjaro.breat>
Jun 29 15:52:49 asusmonster kcminit_startup[842]: QDBusConnection: error: could not send signal to se>
Jun 29 15:52:49 asusmonster kwin_x11[855]: Warning: Setting a new default format with a different ver>
Jun 29 15:52:49 asusmonster kwin_x11[855]: kwin_xkbcommon: XKB: inet:323:58: unrecognized keysym "XF8>
Jun 29 15:52:49 asusmonster kwin_x11[855]: kwin_xkbcommon: XKB: inet:324:58: unrecognized keysym "XF8>
Jun 29 15:52:49 asusmonster ksmserver[898]: Qt: Session management error: networkIdsList argument is >
Jun 29 15:52:50 asusmonster kwin_x11[855]: kwin_core: XCB error: 10 (BadAccess), sequence: 802, resou>
Jun 29 15:52:50 asusmonster kwin_x11[855]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequ>
Jun 29 15:52:50 asusmonster kded5[852]: QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but>
Jun 29 15:52:51 asusmonster kded5[852]: kscreen.kded: PowerDevil SuspendSession action not available!
Jun 29 15:52:39 asusmonster kernel: [Firmware Bug]: TSC ADJUST: CPU0: -33244374 force to 0
Jun 29 15:52:39 asusmonster kernel: x86/cpu: SGX disabled by BIOS.
Jun 29 15:52:39 asusmonster kernel: [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all e>
Jun 29 15:52:39 asusmonster kernel:  #2
Jun 29 15:52:39 asusmonster kernel: MDS CPU bug present and SMT on, data leak possible. See https://w>
Jun 29 15:52:39 asusmonster kernel: MMIO Stale Data CPU bug present and SMT on, data leak possible. S>
Jun 29 15:52:39 asusmonster kernel:  #3
Jun 29 15:52:39 asusmonster kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jun 29 15:52:39 asusmonster kernel: hpet_acpi_add: no address or irqs in _CRS
Jun 29 15:52:39 asusmonster kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is in>
Jun 29 15:52:39 asusmonster kernel: sdhci-pci 0000:00:1e.6: failed to setup card detect gpio
Jun 29 15:52:40 asusmonster kernel: urandom_read_iter: 2 callbacks suppressed
Jun 29 15:52:40 asusmonster thermald[361]: NO RAPL sysfs present
Jun 29 15:52:40 asusmonster thermald[361]: Thermal DTS: No coretemp sysfs found
Jun 29 15:52:40 asusmonster thermald[361]: Thermal DTS or hwmon: No Zones present Need to configure m>
Jun 29 15:52:42 asusmonster kernel: bluetooth hci0: Direct firmware load for rtl_bt/rtl8723b_config.b>
Jun 29 15:52:42 asusmonster kernel: kauditd_printk_skb: 62 callbacks suppressed
Jun 29 15:52:44 asusmonster kernel: nvidia: loading out-of-tree module taints kernel.
Jun 29 15:52:44 asusmonster kernel: nvidia: module license 'NVIDIA' taints kernel.
Jun 29 15:52:44 asusmonster kernel: Disabling lock debugging due to kernel taint
Jun 29 15:52:44 asusmonster kernel: 
Jun 29 15:52:44 asusmonster kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  515.48.07  Fri Ma>
Jun 29 15:52:44 asusmonster kernel: NVRM: GPU 0000:01:00.0: Failed to enable MSI; falling back to PCI>
Jun 29 15:52:44 asusmonster kernel: ACPI Warning: \_SB.PCI0.RP01.PEGP._DSM: Argument #4 type mismatch>
Jun 29 15:52:48 asusmonster klauncher[838]: Connecting to deprecated signal QDBusConnectionInterface:>
Jun 29 15:52:49 asusmonster ksplashqml[818]: file:///usr/share/plasma/look-and-feel/org.manjaro.breat>
Jun 29 15:52:49 asusmonster ksplashqml[818]: file:///usr/share/plasma/look-and-feel/org.manjaro.breat>
Jun 29 15:52:49 asusmonster kcminit_startup[842]: QDBusConnection: error: could not send signal to se>
Jun 29 15:52:49 asusmonster kwin_x11[855]: Warning: Setting a new default format with a different ver>
Jun 29 15:52:49 asusmonster kwin_x11[855]: kwin_xkbcommon: XKB: inet:323:58: unrecognized keysym "XF8>
Jun 29 15:52:49 asusmonster kwin_x11[855]: kwin_xkbcommon: XKB: inet:324:58: unrecognized keysym "XF8>
Jun 29 15:52:49 asusmonster ksmserver[898]: Qt: Session management error: networkIdsList argument is >
Jun 29 15:52:50 asusmonster kwin_x11[855]: kwin_core: XCB error: 10 (BadAccess), sequence: 802, resou>
Jun 29 15:52:50 asusmonster kwin_x11[855]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequ>
Jun 29 15:52:50 asusmonster kded5[852]: QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but>
Jun 29 15:52:51 asusmonster kded5[852]: kscreen.kded: PowerDevil SuspendSession action not available!
Jun 29 15:52:51 asusmonster pulseaudio[929]: stat('/etc/pulse/default.pa.d'): No such file or directo>
Jun 29 15:52:51 asusmonster org_kde_powerdevil[911]: org.kde.powerdevil: Handle button events action >
Jun 29 15:52:52 asusmonster plasmashell[914]: qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaC>
Jun 29 15:52:53 asusmonster plasmashell[914]: file:///usr/share/plasma/plasmoids/org.kde.plasma.digit>
Jun 29 15:52:53 asusmonster plasmashell[914]: file:///usr/share/plasma/plasmoids/org.kde.plasma.digit>
Jun 29 15:52:53 asusmonster plasmashell[914]: file:///usr/share/plasma/plasmoids/org.kde.plasma.syste>
Jun 29 15:52:53 asusmonster plasmashell[914]: Trying to use rootObject before initialization is compl>
Jun 29 15:52:53 asusmonster plasmashell[914]: Entry is not valid "org.kde.kontact.desktop" QSharedPoi>
Jun 29 15:52:53 asusmonster plasmashell[914]: Entry is not valid "ktp-contactlist.desktop" QSharedPoi>
Jun 29 15:52:53 asusmonster plasmashell[914]: Entry is not valid "org.kde.discover.desktop" QSharedPo>
Jun 29 15:52:53 asusmonster plasmashell[914]: Entry is not valid "org.kde.kontact.desktop" QSharedPoi>
Jun 29 15:52:53 asusmonster plasmashell[914]: Entry is not valid "ktp-contactlist.desktop" QSharedPoi>
Jun 29 15:52:53 asusmonster plasmashell[914]: Entry is not valid "org.kde.discover.desktop" QSharedPo>
Jun 29 15:52:53 asusmonster plasmashell[914]: file:///usr/share/plasma/plasmoids/org.kde.plasma.syste>
Jun 29 15:52:53 asusmonster plasmashell[914]: file:///usr/share/plasma/plasmoids/org.kde.plasma.digit>
Jun 29 15:52:53 asusmonster plasmashell[914]: file:///usr/share/plasma/plasmoids/org.kde.plasma.digit>
Jun 29 15:52:53 asusmonster plasmashell[914]: file:///usr/share/plasma/plasmoids/org.kde.plasma.digit>
Jun 29 15:52:53 asusmonster plasmashell[914]: file:///usr/share/ksysguard/sensorfaces/org.kde.ksysgua>
Jun 29 15:52:53 asusmonster plasmashell[914]: file:///usr/share/ksysguard/sensorfaces/org.kde.ksysgua>
Jun 29 15:52:53 asusmonster plasmashell[914]: file:///usr/share/ksysguard/sensorfaces/org.kde.ksysgua>
Jun 29 15:52:53 asusmonster plasmashell[914]: file:///usr/share/ksysguard/sensorfaces/org.kde.ksysgua>
Jun 29 15:52:53 asusmonster plasmashell[914]: file:///usr/share/plasma/plasmoids/org.kde.panel/conten>
Jun 29 15:52:53 asusmonster plasmashell[914]: Cyclic dependency detected between "file:///usr/share/p>
Jun 29 15:52:53 asusmonster plasmashell[914]: file:///usr/share/plasma/plasmoids/org.kde.plasma.priva>
Jun 29 15:52:53 asusmonster kwin_x11[855]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequ>
Jun 29 15:52:53 asusmonster plasmashell[914]: QFont::setPointSizeF: Point size <= 0 (0.000000), must >
Jun 29 15:52:58 asusmonster kwin_x11[855]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequ>
Jun 29 15:52:58 asusmonster kwin_x11[855]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequ>
Jun 29 15:52:58 asusmonster plasmashell[914]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskm>
Jun 29 15:53:21 asusmonster kernel: kauditd_printk_skb: 25 callbacks suppressed
Jun 29 15:54:03 asusmonster kstart5[1578]: Omitting both --window and --windowclass arguments is not >
Jun 29 15:54:03 asusmonster kwin_x11[855]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequ>
Jun 29 15:54:09 asusmonster kernel: kauditd_printk_skb: 2 callbacks suppressed

brahma · 29 June 2022 18:12

so it looks like the pcie errors are fixed…
edit your logs, they are cut off…
provide output from:
mhwd-kernel -li && mhwd -l && mhwd -li

axoxx · 30 June 2022 05:15

Output from mhwd-kernel -li && mhwd -l && mhwd -li:

Currently running: 5.15.49-1-MANJARO (linux515)
The following kernels are installed in your system:
   * linux515
> 0000:01:00.0 (0302:10de:174e) Display controller nVidia Corporation:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
video-hybrid-intel-nvidia-prime            2021.12.18               false            PCI
video-hybrid-intel-nvidia-470xx-prime            2021.12.18               false            PCI
video-hybrid-intel-nvidia-390xx-bumblebee            2021.12.18               false            PCI
          video-nvidia            2021.12.18               false            PCI
    video-nvidia-470xx            2021.12.18               false            PCI
    video-nvidia-390xx            2021.12.18               false            PCI
           video-linux            2018.05.04                true            PCI


> 0000:00:02.0 (0300:8086:5916) Display controller Intel Corporation:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
video-hybrid-intel-nvidia-prime            2021.12.18               false            PCI
video-hybrid-intel-nvidia-470xx-prime            2021.12.18               false            PCI
video-hybrid-intel-nvidia-390xx-bumblebee            2021.12.18               false            PCI
           video-linux            2018.05.04                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI


> Installed PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
     video-modesetting            2020.01.13                true            PCI
          video-nvidia            2021.12.18               false            PCI


Warning: No installed USB configs!

brahma · 30 June 2022 06:22

so uninstall nvidia and install video-linux only, and see if you still have issues…
install video linux:
sudo mhwd -i pci video-linux
uninstall nvidia:
sudo mhwd -r pci video-nvidia
sudo mhwd -r pci video-modesetting
reboot and test

axoxx · 30 June 2022 07:57

I uninstalled hybrid driver, reinstalled nvidia driver along with video linux. Its performing pretty good now. But VLC keeps crashing. Other than vlc everything else is fine right now. I think i will just switch to another video player and see if i face issues.

Battery issues have been fixed thanks to tlp, autocpufreq and optimus manager along with better battery configs.
Currently no odd shutup message is coming since adding pci=nomsi in /etc/default/grub .

Thank you very much for your help

brahma · 30 June 2022 07:59

so run vlc from terminal and see what the logs are when it crashes…
also check log size because of the pcie error spam:
journalctl --disk-usage

axoxx · 30 June 2022 08:04

journalctl output shows:
Archived and active journals take up 4.0G in the file system.

brahma · 30 June 2022 08:07

thats a lot… clean it:
sudo journalctl --rotate
sudo journalctl -m --vacuum-time=1s

also you need to add the pci=nomsi parameter everytime you do a fresh install of any linux distro
and also some usb distros wont even boot if you dont add the parameter during booting into the grub menu … here is a link on how to do it … but you should add this paramater into any live usb you are trying to boot…

axoxx · 30 June 2022 09:46

I cleaned active journals. Thank you very much. And i am currently using smplayer, it doesnt bug like vlc. Thank you very very much

Yochanan · 15 May 2023 21:47