Hey, since I'm on kernel version 6.2 I have a problem with my computer which lock itself redirecting to login and once I enter password all applications are closed. It happend randomly even while I'm active after minutes or hours.
I checked journalctl -b0 and there are thousand of this line to each minute
juin 26 17:12:26 avocadocs-Green-G4 kernel: pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:00:1d.0
juin 26 17:12:26 avocadocs-Green-G4 kernel: pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
juin 26 17:12:26 avocadocs-Green-G4 kernel: pcieport 0000:00:1d.0: device [8086:54b0] error status/mask=00000001/00002000
juin 26 17:12:26 avocadocs-Green-G4 kernel: pcieport 0000:00:1d.0: [ 0] RxErr (First)
juin 26 17:12:26 avocadocs-Green-G4 kernel: pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:00:1d.0
juin 26 17:12:26 avocadocs-Green-G4 kernel: pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
juin 26 17:12:26 avocadocs-Green-G4 kernel: pcieport 0000:00:1d.0: device [8086:54b0] error status/mask=00000001/00002000
juin 26 17:12:26 avocadocs-Green-G4 kernel: pcieport 0000:00:1d.0: [ 0] RxErr (First)
juin 26 17:12:27 avocadocs-Green-G4 kernel: pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:00:1d.0
juin 26 17:12:27 avocadocs-Green-G4 kernel: pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
juin 26 17:12:27 avocadocs-Green-G4 kernel: pcieport 0000:00:1d.0: device [8086:54b0] error status/mask=00000001/00002000
juin 26 17:12:27 avocadocs-Green-G4 kernel: pcieport 0000:00:1d.0: [ 0] RxErr (First)
juin 26 17:12:28 avocadocs-Green-G4 kernel: pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:00:1d.0
juin 26 17:12:28 avocadocs-Green-G4 kernel: pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
juin 26 17:12:28 avocadocs-Green-G4 kernel: pcieport 0000:00:1d.0: device [8086:54b0] error status/mask=00000001/00002000```
Done a websearch on that and found this re Ubuntu:
Don't know if anything there will help, or point to something that will help you.
Sadly it doesn't fix, it redid same just now looks like it just kill current session here are logs before and after crash around 22:30
The log is not as informative as I would have liked; there were some Stop Service issues, but generically listed.
Some things you can check:
Is Root full?
sudo journalctl --vacuum-time=2d
sudo apt clean && sudo apt autoremove
Check your Disk space usage and see if you can clear anything else out if your disk shows as pretty full.
Check for Broken packages:
sudo apt update --fix-missing
sudo apt --fix-broken install
sudo dpkg --configure -a
Check graphics: Are you using Nvidia?
sudo lshw -C video
You may need to add the nomodeset grub parameter if you have Nvidia Card as dedicated and Intel as integrated.
It's weird because I have a lot of space remaining, I have installed less than 10 apps nothing else
No I'm not using Nvidia
Now display is not unclaimed at least
*-display
description: VGA compatible controller
produit: Intel Corporation
fabricant: Intel Corporation
identifiant matériel: 2
information bus: pci@0000:00:02.0
nom logique: /dev/fb0
version: 00
bits: 64 bits
horloge: 33MHz
fonctionnalités: pciexpress msi pm vga_controller bus_master cap_list rom fb
configuration : depth=32 driver=i915 latency=0 mode=1920x1080 visual=truecolor xres=1920 yres=1080
ressources : mémoireE/S:600-5ff mémoireE/S:400-3ff irq:16 mémoire:6000000000-6000ffffff mémoire:4000000000-400fffffff portE/S:4000(taille=64) mémoire:c0000-dffff mémoire:4010000000-4016ffffff mémoire:4020000000-40ffffffff```
1 Like
In addition when problem happend, I always have remaining ram and processor.
So since it's since I use new kernel maybe I should use an older one but still newer than first one where I had monitor issue?
So, we went from Freezing on lock and display unclaimed, to display claimed and not freezing on lock - but randomly locking and shutting down. 
Yeah, except it's not shutting down, only apps so I have to relaunch all and sometimes it re happens 2 mins later
Is it plugged in or running on battery when this occurs?
My thought process is that pci power saving is enabled, reducing power to PCI, forcing the drive to power down which is kicking you out. I could be wrong.
This would effect NVMe drives, maybe ssd.
