[SOLVED]dmesg output not expected

yuanhao · 2022-01-18 11:20:49

Hi, I am follow the instruction to config the network: https://wiki.archlinux.org/title/Networ … n/Wireless
It asks me to check kernel messages for firmware being loaded using the command

dmesg | grep firmware

or

dmesg | grep iwlwifi

(I do use iwlwifi)
However I get no output from both this two command, and then I check the out put of dmesg:

[ 4410.388088] pcieport 0000:00:06.0: AER: Corrected error received: 0000:00:06.0
[ 4410.388105] pcieport 0000:00:06.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 4410.388110] pcieport 0000:00:06.0:   device [8086:4c09] error status/mask=00000001/00002000
[ 4410.388116] pcieport 0000:00:06.0:    [ 0] RxErr                  (First)
[ 4410.430346] pcieport 0000:00:06.0: AER: Corrected error received: 0000:00:06.0
[ 4410.430363] pcieport 0000:00:06.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 4410.430368] pcieport 0000:00:06.0:   device [8086:4c09] error status/mask=00000001/00002000
[ 4410.430374] pcieport 0000:00:06.0:    [ 0] RxErr                  (First)
[ 4410.458110] pcieport 0000:00:06.0: AER: Corrected error received: 0000:00:06.0
[ 4410.458126] pcieport 0000:00:06.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 4410.458131] pcieport 0000:00:06.0:   device [8086:4c09] error status/mask=00000001/00002000
[ 4410.458137] pcieport 0000:00:06.0:    [ 0] RxErr                  (First)
[ 4410.531602] pcieport 0000:00:06.0: AER: Corrected error received: 0000:00:06.0
[ 4410.531619] pcieport 0000:00:06.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 4410.531624] pcieport 0000:00:06.0:   device [8086:4c09] error status/mask=00000001/00002000
[ 4410.531630] pcieport 0000:00:06.0:    [ 0] RxErr                  (First)
[ 4410.547426] pcieport 0000:00:06.0: AER: Corrected error received: 0000:02:00.0
[ 4410.547444] nvme 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 4410.547449] nvme 0000:02:00.0:   device [1987:5016] error status/mask=00000001/00006000
[ 4410.547455] nvme 0000:02:00.0:    [ 0] RxErr                  (First)
[ 4410.600932] pcieport 0000:00:06.0: AER: Corrected error received: 0000:00:06.0
[ 4410.600949] pcieport 0000:00:06.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 4410.600954] pcieport 0000:00:06.0:   device [8086:4c09] error status/mask=00000001/00002000
[ 4410.600960] pcieport 0000:00:06.0:    [ 0] RxErr                  (First)
[ 4410.708719] pcieport 0000:00:06.0: AER: Corrected error received: 0000:00:06.0
[ 4410.708736] pcieport 0000:00:06.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 4410.708741] pcieport 0000:00:06.0:   device [8086:4c09] error status/mask=00000001/00002000
[ 4410.708747] pcieport 0000:00:06.0:    [ 0] RxErr                  (First)
[ 4410.731263] pcieport 0000:00:06.0: AER: Corrected error received: 0000:00:06.0
[ 4410.731281] pcieport 0000:00:06.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)

...............(lots of same thing)

[ 4455.417684] pcieport 0000:00:06.0: AER: Corrected error received: 0000:00:06.0
[ 4455.417700] pcieport 0000:00:06.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 4455.417705] pcieport 0000:00:06.0:   device [8086:4c09] error status/mask=00000001/00002000
[ 4455.417711] pcieport 0000:00:06.0:    [ 0] RxErr                  (First)
[ 4455.621681] pcieport 0000:00:06.0: AER: Corrected error received: 0000:00:06.0
[ 4455.621697] pcieport 0000:00:06.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 4455.621702] pcieport 0000:00:06.0:   device [8086:4c09] error status/mask=00000001/00002000
[ 4455.621708] pcieport 0000:00:06.0:    [ 0] RxErr                  (First)
[ 4456.122824] pcieport 0000:00:06.0: AER: Corrected error received: 0000:00:06.0
[ 4456.122842] pcieport 0000:00:06.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 4456.122847] pcieport 0000:00:06.0:   device [8086:4c09] error status/mask=00000001/00002000
[ 4456.122853] pcieport 0000:00:06.0:    [ 0] RxErr                  (First)
[ 4456.147536] audit: type=1100 audit(1642504647.520:194): pid=9248 uid=1000 auid=1000 ses=2 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="yuanhao" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 4456.147539] audit: type=1101 audit(1642504647.520:195): pid=9248 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="yuanhao" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 4456.147947] audit: type=1110 audit(1642504647.520:196): pid=9248 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[ 4456.148017] audit: type=1105 audit(1642504647.520:197): pid=9248 uid=1000 auid=1000 ses=2 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'

Is there any thing wrong?

Last edited by yuanhao (2022-01-18 19:40:47)

Lone_Wolf · 2022-01-18 13:18:43

dmesg needs to be run as root (or sudo) to see everything .

Please run

journalctl -b |& curl -F 'f:1=<-' ix.io

and post the link it outputs (may take some time)

Last edited by Lone_Wolf (2022-01-18 13:18:56)

yuanhao · 2022-01-18 13:40:22

Lone_Wolf wrote:

dmesg needs to be run as root (or sudo) to see everything .
Please run
journalctl -b |& curl -F 'f:1=<-' ix.io 
and post the link it outputs (may take some time)

Yes, I did run using sudo.
and for the command

journalctl -b |& curl -F 'f:1=<-' ix.io

it outputs nothing (no matter I use sudo or not). TAT

seth · 2022-01-18 14:36:44

If there's too much™ junk in the journal you might exceed the quota.

sudo journalctl -b > /tmp/journal.txt

and upload that file somewhere.

yuanhao · 2022-01-18 15:16:55

seth wrote:

If there's too much™ junk in the journal you might exceed the quota.
sudo journalctl -b > /tmp/journal.txt
and upload that file somewhere.

Yes, I notice the file is 36M
how do I upload this or is there any way around to fix my origin problem?

seth · 2022-01-18 15:21:18

[ 4410.531619] pcieport 0000:00:06.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)

indicates a wonky signal on the PCI bus.
You can suppress it by passing "pci=noaer" to the kernel commandline and should check "lspci" for what that device is.
It's not fatal, though (all posted errors are "corrected", what means the bus drives to fast)

About the firmware, frst and foremost make sure to install https://archlinux.org/packages/core/any/linux-firmware/ and specify your wifi chip.

yuanhao · 2022-01-18 16:11:19

seth wrote:

[ 4410.531619] pcieport 0000:00:06.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
indicates a wonky signal on the PCI bus.
You can suppress it by passing "pci=noaer" to the kernel commandline and should check "lspci" for what that device is.
It's not fatal, though (all posted errors are "corrected", what means the bus drives to fast)
About the firmware, frst and foremost make sure to install https://archlinux.org/packages/core/any/linux-firmware/ and specify your wifi chip.

I have checked, linux firmware above is installed, and the pcie 0000:00:06.0 is

00:06.0 PCI bridge: Intel Corporation Device 4c09 (rev 01)
        Kernel driver in use: pcieport

seth · 2022-01-18 16:15:14

It's then something behind that bridge.
You've also not explained what your wifi chip is (or your actual problem, aside from trying to grep dmesg for "something")

yuanhao · 2022-01-18 16:32:44

seth wrote:

It's then something behind that bridge.
You've also not explained what your wifi chip is (or your actual problem, aside from trying to grep dmesg for "something")

This is my wifi info according to lspci

05:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a)
        Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi

And after I add pci=noaer and reboot, the dmesg | grep iwlwifi command gives the message

[    1.594248] iwlwifi 0000:05:00.0: loaded firmware version 67.8f59b80b.0 ty-a0-gf-a0-67.ucode op_mode iwlmvm

which is just the same message as it says on https://wiki.archlinux.org/title/Networ … n/Wireless
However it also produce other message, here are full message:

[    1.581827] iwlwifi 0000:05:00.0: enabling device (0000 -> 0002)
[    1.594061] iwlwifi 0000:05:00.0: api flags index 2 larger than supported by driver
[    1.594076] iwlwifi 0000:05:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.34
[    1.594248] iwlwifi 0000:05:00.0: loaded firmware version 67.8f59b80b.0 ty-a0-gf-a0-67.ucode op_mode iwlmvm
[    1.742907] iwlwifi 0000:05:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
[    1.749152] iwlwifi 0000:05:00.0: WRT: Failed to set DRAM buffer for alloc id 1, ret=-1
[    1.749153] iwlwifi 0000:05:00.0: WRT: Failed to set DRAM buffer for alloc id 2, ret=-1
[    1.749154] iwlwifi 0000:05:00.0: WRT: Failed to set DRAM buffer for alloc id 3, ret=-1
[    1.890367] iwlwifi 0000:05:00.0: loaded PNVM version 4b50f925
[    1.901931] iwlwifi 0000:05:00.0: Detected RF GF, rfid=0x10d000
[    1.968987] iwlwifi 0000:05:00.0: base HW address: e8:84:a5:67:d9:f5
[    2.140835] iwlwifi 0000:05:00.0 wlp5s0: renamed from wlan0
[    2.444089] iwlwifi 0000:05:00.0: WRT: Failed to set DRAM buffer for alloc id 1, ret=-1
[    2.444091] iwlwifi 0000:05:00.0: WRT: Failed to set DRAM buffer for alloc id 2, ret=-1
[    2.444092] iwlwifi 0000:05:00.0: WRT: Failed to set DRAM buffer for alloc id 3, ret=-1
[    2.688074] iwlwifi 0000:05:00.0: WRT: Failed to set DRAM buffer for alloc id 1, ret=-1
[    2.688076] iwlwifi 0000:05:00.0: WRT: Failed to set DRAM buffer for alloc id 2, ret=-1
[    2.688076] iwlwifi 0000:05:00.0: WRT: Failed to set DRAM buffer for alloc id 3, ret=-1

But I have successfully connected to wifi follow the rest of the instruction... so I think every thing is fine?

seth · 2022-01-18 18:07:16

No, this is fine.
The previous grep failed because dmesg is a ringbuffer and overflew by the pci errors (which you still might want to address in a different threwad)

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2022-01-18 11:20:49

[SOLVED]dmesg output not expected

#2 2022-01-18 13:18:43

Re: [SOLVED]dmesg output not expected

#3 2022-01-18 13:40:22

Re: [SOLVED]dmesg output not expected

#4 2022-01-18 14:36:44

Re: [SOLVED]dmesg output not expected

#5 2022-01-18 15:16:55

Re: [SOLVED]dmesg output not expected

#6 2022-01-18 15:21:18

Re: [SOLVED]dmesg output not expected

#7 2022-01-18 16:11:19

Re: [SOLVED]dmesg output not expected

#8 2022-01-18 16:15:14

Re: [SOLVED]dmesg output not expected

#9 2022-01-18 16:32:44

Re: [SOLVED]dmesg output not expected

#10 2022-01-18 18:07:16

Re: [SOLVED]dmesg output not expected

Board footer