You are not logged in.

Pages: 1 2

#26 2022-10-14 10:23:18

ambition_echo
Member
Registered: 2022-09-24
Posts: 10
Website

Re: [SOLVED] Random freeze issue

I got some logs before the crash in journalctl:
There are many errors about the wired network card RTL8169, I don't know if it is related to this.

Oct 14 17:33:16 TxPC kernel: pcieport 0000:00:02.1: AER: Uncorrected (Fatal) error received: 0000:03:00.0
Oct 14 17:33:16 TxPC kernel: r8169 0000:03:00.0: AER: PCIe Bus Error: severity=Uncorrected (Fatal), type=Inaccessible, (Unregistered Agent ID)
Oct 14 17:33:16 TxPC kernel: r8169 0000:03:00.0: AER: can't recover (no error_detected callback)
Oct 14 17:33:17 TxPC kernel: pcieport 0000:00:02.1: AER: Root Port link has been reset (0)
Oct 14 17:33:17 TxPC kernel: pcieport 0000:00:02.1: AER: device recovery failed
Oct 14 17:35:37 TxPC kernel: pcieport 0000:00:02.1: AER: Multiple Corrected error received: 0000:03:00.0
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Transmitter ID)
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:   device [10ec:8168] error status/mask=ffffffff/00006000
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [ 0] RxErr                  (First)
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [ 1] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [ 2] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [ 3] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [ 4] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [ 5] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [ 6] BadTLP
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [ 7] BadDLLP
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [ 8] Rollover
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [ 9] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [10] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [11] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [12] Timeout
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [15] HeaderOF
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [16] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [17] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [18] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [19] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [20] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [21] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [22] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [23] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [24] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [25] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [26] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [27] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [28] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [29] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [30] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0:    [31] Unknown Error Bit
Oct 14 17:35:38 TxPC kernel: pcieport 0000:00:02.1: AER: Uncorrected (Fatal) error received: 0000:03:00.0
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0: AER: PCIe Bus Error: severity=Uncorrected (Fatal), type=Inaccessible, (Unregistered Agent ID)
Oct 14 17:35:38 TxPC kernel: r8169 0000:03:00.0: AER: can't recover (no error_detected callback)
Oct 14 17:35:39 TxPC kernel: pcieport 0000:00:02.1: AER: Root Port link has been reset (0)
Oct 14 17:35:39 TxPC kernel: pcieport 0000:00:02.1: AER: device recovery failed
Oct 14 17:35:39 TxPC kernel: pcieport 0000:00:02.1: AER: Multiple Uncorrected (Fatal) error received: 0000:03:00.0
Oct 14 17:35:39 TxPC kernel: r8169 0000:03:00.0: AER: PCIe Bus Error: severity=Uncorrected (Fatal), type=Inaccessible, (Unregistered Agent ID)
Oct 14 17:35:39 TxPC kernel: r8169 0000:03:00.0: AER: can't recover (no error_detected callback)
Oct 14 17:35:40 TxPC kernel: pcieport 0000:00:02.1: AER: Root Port link has been reset (0)
Oct 14 17:35:40 TxPC kernel: pcieport 0000:00:02.1: AER: device recovery failed
Oct 14 17:35:40 TxPC kernel: pcieport 0000:00:02.1: AER: Multiple Uncorrected (Fatal) error received: 0000:03:00.0
Oct 14 17:35:40 TxPC kernel: r8169 0000:03:00.0: AER: PCIe Bus Error: severity=Uncorrected (Fatal), type=Inaccessible, (Unregistered Agent ID)
Oct 14 17:35:40 TxPC kernel: r8169 0000:03:00.0: AER: can't recover (no error_detected callback)
Oct 14 17:35:41 TxPC kernel: pcieport 0000:00:02.1: AER: Root Port link has been reset (0)
Oct 14 17:35:41 TxPC kernel: pcieport 0000:00:02.1: AER: device recovery failed
Oct 14 17:35:42 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:35:42 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:35:47 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:35:48 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:35:51 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:35:53 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:35:53 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:35:56 TxPC dhcpcd[701]: eno1: pid 712 deleted default route via fe80::5
Oct 14 17:36:04 TxPC kernel: r8169 0000:03:00.0 eno1: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
Oct 14 17:36:05 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:08 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:08 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:09 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:10 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:20 TxPC dhcpcd[701]: eno1: fe80::5 is unreachable
Oct 14 17:36:20 TxPC dhcpcd[701]: eno1: adding default route via fe80::5
Oct 14 17:36:21 TxPC dhcpcd[701]: eno1: soliciting an IPv6 router
Oct 14 17:36:21 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:23 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:23 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:24 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:28 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:28 TxPC dhcpcd[701]: eno1: fe80::5 is reachable again
Oct 14 17:36:29 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:29 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:29 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:30 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:30 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:32 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:33 TxPC dhcpcd[701]: eno1: no IPv6 Routers available
Oct 14 17:36:34 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:34 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:35 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:36 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:36 TxPC kernel: [UFW BLOCK] IN=eno1 OUT= MAC=58:11:22:84:ef:2c:98:00:6a:06:b3:86:08:00 SRC=220.246.254.226 DST=192.168.5.6 LEN=341 >
Oct 14 17:36:36 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:36 TxPC dhcpcd[701]: eno1: fe80::5 is unreachable
Oct 14 17:36:36 TxPC dhcpcd[701]: eno1: fe80::5 is reachable again
Oct 14 17:36:37 TxPC dhcpcd[701]: eno1: soliciting an IPv6 router
Oct 14 17:36:37 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:38 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:42 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:44 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:45 TxPC dhcpcd[701]: eno1: fe80::5 is unreachable
Oct 14 17:36:45 TxPC dhcpcd[701]: eno1: fe80::5 is reachable again
Oct 14 17:36:45 TxPC dhcpcd[701]: eno1: soliciting an IPv6 router
Oct 14 17:36:47 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:53 TxPC dhcpcd[701]: eno1: fe80::5 is unreachable
Oct 14 17:36:53 TxPC kernel: pcieport 0000:00:02.1: AER: Corrected error received: 0000:03:00.0
Oct 14 17:36:54 TxPC dhcpcd[701]: eno1: soliciting an IPv6 router
Oct 14 17:36:54 TxPC dhcpcd[701]: eno1: fe80::5 is reachable again
Oct 14 17:37:00 TxPC dhcpcd[701]: eno1: pid 712 deleted default route via fe80::5
Oct 14 17:37:21 TxPC kernel: [UFW BLOCK] IN=eno1 OUT= MAC=58:11:22:84:ef:2c:98:00:6a:06:b3:86:08:00 SRC=220.246.254.226 DST=192.168.5.6 LEN=341 >
Oct 14 17:37:38 TxPC kernel: pcieport 0000:00:02.1: AER: Uncorrected (Fatal) error received: 0000:03:00.0
Oct 14 17:37:38 TxPC kernel: r8169 0000:03:00.0: AER: PCIe Bus Error: severity=Uncorrected (Fatal), type=Inaccessible, (Unregistered Agent ID)
Oct 14 17:37:38 TxPC kernel: r8169 0000:03:00.0: AER: can't recover (no error_detected callback)
Oct 14 17:37:39 TxPC kernel: pcieport 0000:00:02.1: AER: Root Port link has been reset (0)
Oct 14 17:37:39 TxPC kernel: pcieport 0000:00:02.1: AER: device recovery failed

Last edited by ambition_echo (2022-10-14 17:36:31)

Offline

#27 2022-10-14 17:19:20

ambition_echo
Member
Registered: 2022-09-24
Posts: 10
Website

Re: [SOLVED] Random freeze issue

I'm almost certain it's the problem with the wired network card, I disconnected the wired connection and worked with WIFI for three hours and didn't experience the crash.

                   -`                    hgy@TxPC
                  .o+`                   --------
                 `ooo/                   OS: Arch Linux x86_64
                `+oooo:                  Host: ASUS TUF Gaming A15 FA507RM_FA507RM 1.0
               `+oooooo:                 Kernel: 6.0.1-arch2-1
               -+oooooo+:                Uptime: 3 hours, 44 mins
             `/:-:++oooo+:               Packages: 1358 (pacman)
            `/++++/+++++++:              Shell: fish 3.5.1
           `/++++++++++++++:             Resolution: 1920x1080
          `/+++ooooooooooooo/`           DE: Plasma 5.26.0
         ./ooosssso++osssssso+`          WM: KWin
        .oossssso-````/ossssss+`         WM Theme: Breeze 微风
       -osssssso.      :ssssssso.        Theme: [Plasma], Adwaita-dark [GTK2/3]
      :osssssss/        osssso+++.       Icons: Papirus-Dark [Plasma], Papirus-Dark [GTK2/3]
     /ossssssss/        +ssssooo/-       Terminal: WezTerm
   `/ossssso+/:-        -:/+osssso+-     CPU: AMD Ryzen 7 6800H with Radeon Graphics (16) @ 3.200GHz
  `+sso+:-`                 `.-/+oso:    GPU: NVIDIA GeForce RTX 3060 Mobile / Max-Q
 `++:.                           `-/+/   GPU: AMD ATI Radeon 680M
 .`                                 `/   Memory: 7080MiB / 15236MiB

Offline

#28 2022-10-15 08:01:28

Misaka19465
Member
Registered: 2022-08-16
Posts: 14

Re: [SOLVED] Random freeze issue

I'm almost certain it's the problem with the wired network card, I disconnected the wired connection and worked with WIFI for three hours and didn't experience the crash.

Seemingly works for me as well.

Maybe we should move to another topic, and mark this as solved?

Offline

#29 2022-10-15 08:42:31

ambition_echo
Member
Registered: 2022-09-24
Posts: 10
Website

Re: [SOLVED] Random freeze issue

Misaka19465 wrote:

Maybe we should move to another topic, and mark this as solved?

Ok, you can put the link to the new topic here and put the error message above in the new topic, that's the only error message I can find.

Offline

#30 2022-10-15 09:53:35

Misaka19465
Member
Registered: 2022-08-16
Posts: 14

Re: [SOLVED] Random freeze issue

Maybe here is the solution. Installing r8168-dkms then add r8169 to blacklist keep my laptop alive for a couple of hours.

Offline

#31 2022-10-15 12:11:42

ambition_echo
Member
Registered: 2022-09-24
Posts: 10
Website

Re: [SOLVED] Random freeze issue

Misaka19465 wrote:

Maybe here is the solution. Installing r8168-dkms then add r8169 to blacklist keep my laptop alive for a couple of hours.

Why install r8168-dkms instead of r8168

Offline

#32 2022-10-15 22:43:17

Misaka19465
Member
Registered: 2022-08-16
Posts: 14

Re: [SOLVED] Random freeze issue

I'm using zen kernel. It's up to you.

Offline

#33 2022-10-16 03:03:17

ambition_echo
Member
Registered: 2022-09-24
Posts: 10
Website

Re: [SOLVED] Random freeze issue

Ok, This method worked for me, I think you can mark the topic as solved.

The automatic restart caused by the kernel panic is caused by the R8169 module of the Realtek network card.

summary:

Solution 1:

Use the LTS kernel to avoid this problem.

Solution 2:

Use the R8168 module instead of the R8169

1. install `r8168` or `r8168-dkms` package, Which one to install depends on the kernel you are using.

sudo pacman -S r8168

2. add r8169 to blacklist.

Create `no8169.conf` file in the `/etc/modprobe.d/`
Write the following in it:

# Do not load the 'r8169' module on boot.
blacklist r8169

3. add config file in the `/etc/mkinitcpio.conf`

Edit `/etc/mkinitcpio.conf`
Find `FILES=()`, add`/etc/modprobe.d/no8169.conf`, make it look like this:

FILES=(/etc/modprobe.d/no8169.conf)

4.  regenerate the initramfs.

sudo mkinitcpio -p linux # Depends on the kernel you are using

Last edited by ambition_echo (2022-10-16 03:05:07)

Offline

#34 2022-10-17 14:53:32

joanmanel
Member
Registered: 2012-11-06
Posts: 234

Re: [SOLVED] Random freeze issue

I am having a similar problem since the last Kernel update I did this morning to 6.0.2.

The computer randomly freezes and I need to force a reboot through the tower button. The GPU is an Nvidia 2070S and the CPU is intel i5.

The wifi connects and disconnects constantly. I use the drivers rtl88x2bu-dkms-git.

As said, I never had these problems until I updated the kernel this morning. Since then, the computer freezes every 30min to 1h, while the wifi connects and disconnects every 2/3 min.

Log from journalctl

Oct 17 15:53:17 housepc kernel: start_addr=(0x20000), end_addr=(0x40000), buffer_size=(0x20000), smp_number_max=(16384)
Oct 17 15:53:17 housepc kernel: RTW: WARN _beamforming_leave: 00:00:00:00:00:00 is neither beamforming ee or er!!
Oct 17 15:53:17 housepc kernel: RTW: ERROR Free disconnecting network of scanned_queue failed due to pwlan == NULL
Oct 17 15:53:17 housepc NetworkManager[548]: <info>  [1666018397.3093] device (wlp0s20f0u13u2): set-hw-addr: set MAC address to 0A:15:AB:A2:FA:8F (scanning)
Oct 17 15:53:17 housepc NetworkManager[548]: <info>  [1666018397.3541] device (wlp0s20f0u13u2): supplicant interface state: internal-starting -> disconnected
Oct 17 15:53:17 housepc NetworkManager[548]: <info>  [1666018397.3542] Wi-Fi P2P device controlled by interface wlp0s20f0u13u2 created
Oct 17 15:53:17 housepc NetworkManager[548]: <info>  [1666018397.3543] manager: (p2p-dev-wlp0s20f0u13u2): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/10)
Oct 17 15:53:17 housepc NetworkManager[548]: <info>  [1666018397.3544] device (p2p-dev-wlp0s20f0u13u2): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 17 15:53:17 housepc NetworkManager[548]: <info>  [1666018397.3547] device (wlp0s20f0u13u2): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'm>
Oct 17 15:53:17 housepc NetworkManager[548]: <info>  [1666018397.3549] device (p2p-dev-wlp0s20f0u13u2): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 17 15:53:17 housepc goa-daemon[1222]: goa_ews_client_autodiscover() failed: 2 — Error resolving “outlook.office365.com”: Temporary failure in name resolution
Oct 17 15:53:17 housepc goa-daemon[1222]: goa_ews_client_autodiscover() failed: 2 — Error resolving “autodiscover.outlook.office365.com”: Temporary failure in name resolution
Oct 17 15:53:17 housepc goa-daemon[1222]: /org/gnome/OnlineAccounts/Accounts/account_1651134248_0: Setting AttentionNeeded to TRUE because EnsureCredentials() failed with: Invalid password >
Oct 17 15:53:19 housepc goa-daemon[1222]: goa_ews_client_autodiscover() failed: 2 — Error resolving “outlook.office365.com”: Temporary failure in name resolution
Oct 17 15:53:19 housepc goa-daemon[1222]: goa_ews_client_autodiscover() failed: 2 — Error resolving “autodiscover.outlook.office365.com”: Temporary failure in name resolution
Oct 17 15:53:21 housepc NetworkManager[548]: <info>  [1666018401.0136] policy: auto-activating connection 'BT-TGCP67' (b05e256c-9ed0-4e27-93e6-d4dc0a8d456c)
Oct 17 15:53:21 housepc NetworkManager[548]: <info>  [1666018401.0138] device (wlp0s20f0u13u2): Activation: starting connection 'BT-TGCP67' (b05e256c-9ed0-4e27-93e6-d4dc0a8d456c)
Oct 17 15:53:21 housepc NetworkManager[548]: <info>  [1666018401.0139] device (wlp0s20f0u13u2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 17 15:53:21 housepc NetworkManager[548]: <info>  [1666018401.0140] manager: NetworkManager state is now CONNECTING
Oct 17 15:53:21 housepc kernel: RTW: nolinked power save enter
Oct 17 15:53:21 housepc NetworkManager[548]: <info>  [1666018401.0246] device (wlp0s20f0u13u2): set-hw-addr: reset MAC address to 14:EB:B6:54:EB:26 (preserve)
Oct 17 15:53:21 housepc NetworkManager[548]: <info>  [1666018401.0247] device (wlp0s20f0u13u2): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 17 15:53:21 housepc NetworkManager[548]: <info>  [1666018401.0249] device (wlp0s20f0u13u2): Activation: (wifi) access point 'BT-TGCP67' has security, but secrets are required.
Oct 17 15:53:21 housepc NetworkManager[548]: <info>  [1666018401.0249] device (wlp0s20f0u13u2): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Oct 17 15:53:21 housepc NetworkManager[548]: <info>  [1666018401.0249] sup-iface[78417584cffa4cfd,3,wlp0s20f0u13u2]: wps: type pbc start...
Oct 17 15:53:21 housepc NetworkManager[548]: <info>  [1666018401.0254] device (wlp0s20f0u13u2): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 17 15:53:21 housepc NetworkManager[548]: <info>  [1666018401.0255] device (wlp0s20f0u13u2): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 17 15:53:21 housepc NetworkManager[548]: <info>  [1666018401.0256] device (wlp0s20f0u13u2): Activation: (wifi) connection 'BT-TGCP67' has security, and secrets exist.  No new secrets ne>
Oct 17 15:53:21 housepc NetworkManager[548]: <info>  [1666018401.0256] Config: added 'ssid' value 'BT-TGCP67'
Oct 17 15:53:21 housepc NetworkManager[548]: <info>  [1666018401.0256] Config: added 'scan_ssid' value '1'
Oct 17 15:53:21 housepc NetworkManager[548]: <info>  [1666018401.0256] Config: added 'bgscan' value 'simple:30:-70:86400'
Oct 17 15:53:21 housepc NetworkManager[548]: <info>  [1666018401.0256] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Oct 17 15:53:21 housepc NetworkManager[548]: <info>  [1666018401.0257] Config: added 'auth_alg' value 'OPEN'
Oct 17 15:53:21 housepc NetworkManager[548]: <info>  [1666018401.0257] Config: added 'psk' value '<hidden>'
Oct 17 15:53:21 housepc wpa_supplicant[801]: wlp0s20f0u13u2: WPS-CANCEL
Oct 17 15:53:21 housepc wpa_supplicant[801]: wlp0s20f0u13u2: Trying to associate with c0:d7:aa:79:dd:ca (SSID='BT-TGCP67' freq=5180 MHz)
Oct 17 15:53:21 housepc kernel: RTW: [HALMAC][ALWAYS]shall R reg twice!!
Oct 17 15:53:21 housepc systemd[1]: systemd-rfkill.service: Deactivated successfully.
Oct 17 15:53:21 housepc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?>
Oct 17 15:53:21 housepc kernel: audit: type=1131 audit(1666018401.629:128): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd">
Oct 17 15:53:21 housepc kernel: start_addr=(0x20000), end_addr=(0x40000), buffer_size=(0x20000), smp_number_max=(16384)
Oct 17 15:53:21 housepc NetworkManager[548]: <info>  [1666018401.7518] device (wlp0s20f0u13u2): supplicant interface state: disconnected -> associating
Oct 17 15:53:21 housepc NetworkManager[548]: <info>  [1666018401.7518] device (p2p-dev-wlp0s20f0u13u2): supplicant management interface state: disconnected -> associating
Oct 17 15:53:21 housepc kernel: RTW: nolinked power save leave
Oct 17 15:53:21 housepc kernel: RTW: rtw_set_802_11_connect(wlp0s20f0u13u2)  fw_state=0x00000008
Oct 17 15:53:21 housepc wpa_supplicant[801]: wlp0s20f0u13u2: CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=5180 ht_enabled=1 ch_offset=1 ch_width=80 MHz cf1=5210 cf2=0
Oct 17 15:53:22 housepc kernel: RTW: start auth
Oct 17 15:53:22 housepc kernel: RTW: auth success, start assoc
Oct 17 15:53:22 housepc kernel: RTW: assoc success
Oct 17 15:53:22 housepc wpa_supplicant[801]: wlp0s20f0u13u2: Associated with c0:d7:aa:79:dd:ca
Oct 17 15:53:22 housepc wpa_supplicant[801]: wlp0s20f0u13u2: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Oct 17 15:53:22 housepc kernel: RTW: ============ STA [c0:d7:aa:79:dd:ca]  ===================
Oct 17 15:53:22 housepc kernel: RTW: mac_id : 0
Oct 17 15:53:22 housepc kernel: RTW: wireless_mode : 0x44
Oct 17 15:53:22 housepc kernel: RTW: mimo_type : 2
Oct 17 15:53:22 housepc kernel: RTW: static smps : N
Oct 17 15:53:22 housepc kernel: RTW: bw_mode : 80MHz, ra_bw_mode : 80MHz
Oct 17 15:53:22 housepc kernel: RTW: rate_id : 9
Oct 17 15:53:22 housepc kernel: RTW: rssi : -1 (%), rssi_level : 0
Oct 17 15:53:22 housepc kernel: RTW: is_support_sgi : Y, is_vht_enable : Y
Oct 17 15:53:22 housepc kernel: RTW: disable_ra : N, disable_pt : N
Oct 17 15:53:22 housepc kernel: RTW: is_noisy : N
Oct 17 15:53:22 housepc kernel: RTW: txrx_state : 0
Oct 17 15:53:22 housepc kernel: RTW: curr_tx_rate : CCK_1M (L)
Oct 17 15:53:22 housepc kernel: RTW: curr_tx_bw : 20MHz
Oct 17 15:53:22 housepc kernel: RTW: curr_retry_ratio : 0
Oct 17 15:53:22 housepc kernel: RTW: ra_mask : 0x00000000fffffff0
Oct 17 15:53:22 housepc NetworkManager[548]: <info>  [1666018402.0130] device (wlp0s20f0u13u2): supplicant interface state: associating -> associated
Oct 17 15:53:22 housepc NetworkManager[548]: <info>  [1666018402.0131] device (p2p-dev-wlp0s20f0u13u2): supplicant management interface state: associating -> associated
Oct 17 15:53:22 housepc kernel: RTW: recv eapol packet 1/4
Oct 17 15:53:22 housepc kernel: RTW: send eapol packet 2/4
Oct 17 15:53:22 housepc wpa_supplicant[801]: wlp0s20f0u13u2: WPA: Key negotiation completed with c0:d7:aa:79:dd:ca [PTK=CCMP GTK=CCMP]
Oct 17 15:53:22 housepc wpa_supplicant[801]: wlp0s20f0u13u2: CTRL-EVENT-CONNECTED - Connection to c0:d7:aa:79:dd:ca completed [id=0 id_str=]
Oct 17 15:53:22 housepc wpa_supplicant[801]: bgscan simple: Failed to enable signal strength monitoring
Oct 17 15:53:22 housepc kernel: RTW: recv eapol packet 3/4
Oct 17 15:53:22 housepc kernel: RTW: send eapol packet 4/4
Oct 17 15:53:22 housepc kernel: RTW: set pairwise key camid:0, addr:c0:d7:aa:79:dd:ca, kid:0, type:AES
Oct 17 15:53:22 housepc kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f0u13u2: link becomes ready
Oct 17 15:53:22 housepc kernel: RTW: set group key camid:1, addr:c0:d7:aa:79:dd:ca, kid:1, type:AES
Oct 17 15:53:22 housepc NetworkManager[548]: <info>  [1666018402.0260] device (wlp0s20f0u13u2): supplicant interface state: associated -> completed
Oct 17 15:53:22 housepc NetworkManager[548]: <info>  [1666018402.0260] device (wlp0s20f0u13u2): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network >
Oct 17 15:53:22 housepc NetworkManager[548]: <info>  [1666018402.0261] device (p2p-dev-wlp0s20f0u13u2): supplicant management interface state: associated -> completed
Oct 17 15:53:22 housepc NetworkManager[548]: <info>  [1666018402.0264] device (wlp0s20f0u13u2): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 17 15:53:22 housepc NetworkManager[548]: <info>  [1666018402.0267] dhcp4 (wlp0s20f0u13u2): activation: beginning transaction (timeout in 45 seconds)
Oct 17 15:53:22 housepc NetworkManager[548]: <info>  [1666018402.1846] dhcp4 (wlp0s20f0u13u2): state changed new lease, address=192.168.1.128
Oct 17 15:53:22 housepc NetworkManager[548]: <info>  [1666018402.1853] policy: set 'BT-TGCP67' (wlp0s20f0u13u2) as default for IPv4 routing and DNS
Oct 17 15:53:22 housepc NetworkManager[548]: <info>  [1666018402.1963] device (wlp0s20f0u13u2): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Oct 17 15:53:22 housepc NetworkManager[548]: <info>  [1666018402.1970] device (wlp0s20f0u13u2): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Oct 17 15:53:22 housepc NetworkManager[548]: <info>  [1666018402.1970] device (wlp0s20f0u13u2): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Oct 17 15:53:22 housepc NetworkManager[548]: <info>  [1666018402.1971] manager: NetworkManager state is now CONNECTED_SITE
Oct 17 15:53:22 housepc NetworkManager[548]: <info>  [1666018402.1972] device (wlp0s20f0u13u2): Activation: successful, device activated.
Oct 17 15:53:22 housepc NetworkManager[548]: <info>  [1666018402.3863] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 17 15:53:24 housepc NetworkManager[548]: <info>  [1666018404.2575] dhcp6 (wlp0s20f0u13u2): activation: beginning transaction (timeout in 45 seconds)
Oct 17 15:53:24 housepc NetworkManager[548]: <info>  [1666018404.2584] policy: set 'BT-TGCP67' (wlp0s20f0u13u2) as default for IPv6 routing and DNS
Oct 17 15:53:24 housepc NetworkManager[548]: <info>  [1666018404.2637] dhcp6 (wlp0s20f0u13u2): state changed new lease
Oct 17 15:53:25 housepc systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Oct 17 15:53:25 housepc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?>
Oct 17 15:53:25 housepc kernel: audit: type=1131 audit(1666018405.399:129): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/syste>
Oct 17 15:53:26 housepc goa-daemon[1222]: goa_ews_client_autodiscover() failed: 2 — Error resolving “autodiscover.outlook.office365.com”: Name or service not known
Oct 17 15:53:26 housepc goa-daemon[1222]: /org/gnome/OnlineAccounts/Accounts/account_1651134248_0: Setting AttentionNeeded to FALSE because EnsureCredentials() succeded

EDIT: I have just detected that when the wifi goes off, the bluetooth (keyboard) also goes off.

Last edited by joanmanel (2022-10-17 16:27:27)

Offline

#35 2022-10-18 21:10:11

hkall
Member
Registered: 2019-11-11
Posts: 18

Re: [SOLVED] Random freeze issue

AER errors (PCIe errors) may be caused by ASPM incompatibilities. So it's worth testing with ASPM disabled. There are different ways to do it, dynamically you can disable selected ASPM states using the sysfs attributes in the following directory:
/sys/class/net/<if>/device/link

Offline

Pages: 1 2

Board footer

Powered by FluxBB