You are not logged in.
Pages: 1
My dmesg keeps printing this error message, I don't know how it affects me, can anyone help me, my laptop model is MSI GE62-6QF
uname -a: Linux shenweijie-pc 5.15.43-1-lts #1 SMP Wed, 25 May 2022 14:08:34 +0000 x86_64 GNU/Linux
dmesg:
[ 542.968842] pcieport 0000:00:1c.0: [ 0] RxErr (First)
[ 543.214571] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 543.214590] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 543.214596] pcieport 0000:00:1c.0: device [8086:a110] error status/mask=00000001/00002000
[ 543.214603] pcieport 0000:00:1c.0: [ 0] RxErr (First)
[ 543.296473] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 543.296492] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 543.296498] pcieport 0000:00:1c.0: device [8086:a110] error status/mask=00000001/00002000
[ 543.296505] pcieport 0000:00:1c.0: [ 0] RxErr (First)
[ 543.706083] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 543.706102] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 543.706108] pcieport 0000:00:1c.0: device [8086:a110] error status/mask=00000001/00002000
[ 543.706115] pcieport 0000:00:1c.0: [ 0] RxErr (First)
[ 543.788044] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 543.788063] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 543.788069] pcieport 0000:00:1c.0: device [8086:a110] error status/mask=00000001/00002000
[ 543.788076] pcieport 0000:00:1c.0: [ 0] RxErr (First)
[ 544.033615] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 544.033632] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 544.033639] pcieport 0000:00:1c.0: device [8086:a110] error status/mask=00000001/00002000
[ 544.033646] pcieport 0000:00:1c.0: [ 0] RxErr (First)
[ 544.050527] audit: type=1101 audit(1653834140.868:113): pid=1600 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="shenweijie" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 544.051172] audit: type=1110 audit(1653834140.868:114): pid=1600 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 544.052075] audit: type=1105 audit(1653834140.868:115): pid=1600 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Offline
I am not familiar with these error messages. But taking an educated guess, they could be related to this bug report.
If you know how to do it, you could compile a kernel with the patch mentioned in comment #6 to see if it fixes the issue.
Other possible solutions:
- install the current linux kernel (try this first)
- update your BIOS (only do this if you think the error messages indicate some actual issues on your system)
Offline
As long as you have only a few instances of the error, I would not worry. That error has been following me for several years now.
Take a look at my post if you want to find out which component is causing the issue.
Offline
Pages: 1