Arch crashes and restarts after a few minutes

rafalou38 · 2022-06-13 17:45:56

I just installed arch on my computer, but I have an issue after being connected for a few minutes on XOrg or tty it freezes and crashes,
I have Nouveau driver, I tried proprietary and it also occurs

I don't know if it's relevant but I have:
4k + basic 1080p display
amd ryzen 7 3700x
geforce rtx 2060 super

Here is the end of my last logs journalctl -b -1

>
juin 13 18:57:03 arch-rafa sudo[1516]:   rafael : TTY=pts/0 ; PWD=/home/rafael ; USER=root ; COMMAND=/usr/bin/pacman -S gimp
juin 13 18:57:03 arch-rafa sudo[1516]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
juin 13 18:57:09 arch-rafa kernel: ------------[ cut here ]------------
juin 13 18:57:09 arch-rafa kernel: NETDEV WATCHDOG: enp39s0 (r8169): transmit queue 0 timed out
juin 13 18:57:09 arch-rafa kernel: WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:529 dev_watchdog+0x208/0x210
juin 13 18:57:09 arch-rafa kernel: Modules linked in: uas usb_storage hid_logitech_hidpp btusb btrtl uvcvideo btbcm videobuf2_vmalloc intel_rapl_msr btintel videobuf2_memops btmtk videobuf2_v4l2 snd_usb_audio videobuf2_common bluetooth snd_usbmidi_lib uc>
juin 13 18:57:09 arch-rafa kernel:  zram bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 usbhid nvme crc32c_intel xhci_pci nvme_core xhci_pci_renesas
juin 13 18:57:09 arch-rafa kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.18.3-arch1-1 #1 2090c6f1d9d20f39bd14c0acb6fa89ddb994d43f
juin 13 18:57:09 arch-rafa kernel: Hardware name: Micro-Star International Co., Ltd. MS-7C37/X570-A PRO (MS-7C37), BIOS H.70 01/09/2020
juin 13 18:57:09 arch-rafa kernel: RIP: 0010:dev_watchdog+0x208/0x210
juin 13 18:57:09 arch-rafa kernel: Code: ff e9 40 ff ff ff 48 89 df c6 05 04 4f 41 01 01 e8 cd 8d f9 ff 44 89 e9 48 89 de 48 c7 c7 f8 81 d6 9e 48 89 c2 e8 bc 1c 19 00 <0f> 0b e9 22 ff ff ff 90 f3 0f 1e fa 0f 1f 44 00 00 41 54 55 53 48
juin 13 18:57:09 arch-rafa kernel: RSP: 0018:ffffbda04007ce90 EFLAGS: 00010282
juin 13 18:57:09 arch-rafa kernel: RAX: 0000000000000000 RBX: ffff9e8d520d4000 RCX: 0000000000000000
juin 13 18:57:09 arch-rafa kernel: RDX: ffff9e943ea6e100 RSI: ffff9e943ea616a0 RDI: 0000000000000300
juin 13 18:57:09 arch-rafa kernel: RBP: ffff9e8d520d44c8 R08: 0000000000000000 R09: ffffbda04007cca0
juin 13 18:57:09 arch-rafa kernel: R10: 0000000000000003 R11: ffff9e945f329ee8 R12: ffff9e8d520d441c
juin 13 18:57:09 arch-rafa kernel: R13: 0000000000000000 R14: ffffffff9e1b0bd0 R15: ffff9e8d520d44c8
juin 13 18:57:09 arch-rafa kernel: FS:  0000000000000000(0000) GS:ffff9e943ea40000(0000) knlGS:0000000000000000
juin 13 18:57:09 arch-rafa kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
juin 13 18:57:09 arch-rafa kernel: CR2: 00007f6f1b416000 CR3: 00000001193e0000 CR4: 0000000000350ee0
juin 13 18:57:09 arch-rafa kernel: Call Trace:
juin 13 18:57:09 arch-rafa kernel:  <IRQ>
juin 13 18:57:09 arch-rafa kernel:  ? pfifo_fast_reset+0x130/0x130
juin 13 18:57:09 arch-rafa kernel:  call_timer_fn+0x27/0x130
juin 13 18:57:09 arch-rafa kernel:  __run_timers+0x219/0x2a0
juin 13 18:57:09 arch-rafa kernel:  run_timer_softirq+0x1d/0x40
juin 13 18:57:09 arch-rafa kernel:  __do_softirq+0xd3/0x2c6
juin 13 18:57:09 arch-rafa kernel:  ? sched_clock_cpu+0xd/0xb0
juin 13 18:57:09 arch-rafa kernel:  __irq_exit_rcu+0x8b/0xc0
juin 13 18:57:09 arch-rafa kernel:  sysvec_apic_timer_interrupt+0x72/0x90
juin 13 18:57:09 arch-rafa kernel:  </IRQ>
juin 13 18:57:09 arch-rafa kernel:  <TASK>
juin 13 18:57:09 arch-rafa kernel:  asm_sysvec_apic_timer_interrupt+0x16/0x20
juin 13 18:57:09 arch-rafa kernel: RIP: 0010:cpuidle_enter_state+0xdc/0x380
juin 13 18:57:09 arch-rafa kernel: Code: 00 00 31 ff e8 85 81 80 ff 45 84 ff 74 16 9c 58 0f 1f 40 00 f6 c4 02 0f 85 8f 02 00 00 31 ff e8 5a 56 86 ff fb 0f 1f 44 00 00 <45> 85 f6 0f 88 22 01 00 00 49 63 ce 48 8d 04 49 48 8d 04 81 49 8d
juin 13 18:57:09 arch-rafa kernel: RSP: 0018:ffffbda040167e90 EFLAGS: 00000246
juin 13 18:57:09 arch-rafa kernel: RAX: ffff9e943ea72cc0 RBX: 0000000000000002 RCX: 0000000000000000
juin 13 18:57:09 arch-rafa kernel: RDX: 000000b7173feb32 RSI: fffffff986b2be69 RDI: 0000000000000000
juin 13 18:57:09 arch-rafa kernel: RBP: ffff9e8d45ee3400 R08: 0000000000000002 R09: 00000000238e3989
juin 13 18:57:09 arch-rafa kernel: R10: 000000000001d1c1 R11: 000000000000afc8 R12: ffffffff9f551280
juin 13 18:57:09 arch-rafa kernel: R13: 000000b7173feb32 R14: 0000000000000002 R15: 0000000000000000
juin 13 18:57:09 arch-rafa kernel:  cpuidle_enter+0x2d/0x40
juin 13 18:57:09 arch-rafa kernel:  do_idle+0x1ba/0x220
lines 1789-1847/1854 100%
juin 13 18:56:48 arch-rafa rtkit-daemon[1311]: Supervising 1 threads of 1 processes of 1 users.
juin 13 18:56:49 arch-rafa rtkit-daemon[1311]: Supervising 1 threads of 1 processes of 1 users.
juin 13 18:56:49 arch-rafa rtkit-daemon[1311]: Supervising 1 threads of 1 processes of 1 users.
juin 13 18:56:49 arch-rafa rtkit-daemon[1311]: Supervising 1 threads of 1 processes of 1 users.
juin 13 18:56:49 arch-rafa rtkit-daemon[1311]: Supervising 1 threads of 1 processes of 1 users.
juin 13 18:56:49 arch-rafa rtkit-daemon[1311]: Supervising 1 threads of 1 processes of 1 users.
juin 13 18:56:49 arch-rafa rtkit-daemon[1311]: Supervising 1 threads of 1 processes of 1 users.
juin 13 18:57:03 arch-rafa dbus-daemon[471]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus->
juin 13 18:57:03 arch-rafa dbus-daemon[471]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.servi>
juin 13 18:57:03 arch-rafa audit[1516]: USER_ACCT pid=1516 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,p>
juin 13 18:57:03 arch-rafa audit[1516]: CRED_REFR pid=1516 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,>
juin 13 18:57:03 arch-rafa audit[1516]: USER_START pid=1516 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_sys>
juin 13 18:57:03 arch-rafa sudo[1516]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedeskt>
juin 13 18:57:03 arch-rafa kernel: audit: type=1101 audit(1655139423.655:95): pid=1516 uid=1000 auid=1000 ses=2 msg='op=PAM:ac>
juin 13 18:57:03 arch-rafa kernel: audit: type=1110 audit(1655139423.655:96): pid=1516 uid=1000 auid=1000 ses=2 msg='op=PAM:se>
juin 13 18:57:03 arch-rafa kernel: audit: type=1105 audit(1655139423.655:97): pid=1516 uid=1000 auid=1000 ses=2 msg='op=PAM:se>
juin 13 18:57:03 arch-rafa sudo[1516]:   rafael : TTY=pts/0 ; PWD=/home/rafael ; USER=root ; COMMAND=/usr/bin/pacman -S gimp
juin 13 18:57:03 arch-rafa sudo[1516]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
juin 13 18:57:09 arch-rafa kernel: ------------[ cut here ]------------
juin 13 18:57:09 arch-rafa kernel: NETDEV WATCHDOG: enp39s0 (r8169): transmit queue 0 timed out
juin 13 18:57:09 arch-rafa kernel: WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:529 dev_watchdog+0x208/0x210
juin 13 18:57:09 arch-rafa kernel: Modules linked in: uas usb_storage hid_logitech_hidpp btusb btrtl uvcvideo btbcm videobuf2_>
juin 13 18:57:09 arch-rafa kernel:  zram bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 usbhid nvme crc>
juin 13 18:57:09 arch-rafa kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.18.3-arch1-1 #1 2090c6f1d9d20f39bd14c0acb6fa89d>
juin 13 18:57:09 arch-rafa kernel: Hardware name: Micro-Star International Co., Ltd. MS-7C37/X570-A PRO (MS-7C37), BIOS H.70 0>
juin 13 18:57:09 arch-rafa kernel: RIP: 0010:dev_watchdog+0x208/0x210
juin 13 18:57:09 arch-rafa kernel: Code: ff e9 40 ff ff ff 48 89 df c6 05 04 4f 41 01 01 e8 cd 8d f9 ff 44 89 e9 48 89 de 48 c>
juin 13 18:57:09 arch-rafa kernel: RSP: 0018:ffffbda04007ce90 EFLAGS: 00010282
juin 13 18:57:09 arch-rafa kernel: RAX: 0000000000000000 RBX: ffff9e8d520d4000 RCX: 0000000000000000
juin 13 18:57:09 arch-rafa kernel: RDX: ffff9e943ea6e100 RSI: ffff9e943ea616a0 RDI: 0000000000000300
juin 13 18:57:09 arch-rafa kernel: RBP: ffff9e8d520d44c8 R08: 0000000000000000 R09: ffffbda04007cca0
juin 13 18:57:09 arch-rafa kernel: R10: 0000000000000003 R11: ffff9e945f329ee8 R12: ffff9e8d520d441c
juin 13 18:57:09 arch-rafa kernel: R13: 0000000000000000 R14: ffffffff9e1b0bd0 R15: ffff9e8d520d44c8
juin 13 18:57:09 arch-rafa kernel: FS:  0000000000000000(0000) GS:ffff9e943ea40000(0000) knlGS:0000000000000000
juin 13 18:57:09 arch-rafa kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
juin 13 18:57:09 arch-rafa kernel: CR2: 00007f6f1b416000 CR3: 00000001193e0000 CR4: 0000000000350ee0
juin 13 18:57:09 arch-rafa kernel: Call Trace:
juin 13 18:57:09 arch-rafa kernel:  <IRQ>
juin 13 18:57:09 arch-rafa kernel:  ? pfifo_fast_reset+0x130/0x130
juin 13 18:57:09 arch-rafa kernel:  call_timer_fn+0x27/0x130
juin 13 18:57:09 arch-rafa kernel:  __run_timers+0x219/0x2a0
juin 13 18:57:09 arch-rafa kernel:  run_timer_softirq+0x1d/0x40
juin 13 18:57:09 arch-rafa kernel:  __do_softirq+0xd3/0x2c6
juin 13 18:57:09 arch-rafa kernel:  ? sched_clock_cpu+0xd/0xb0
juin 13 18:57:09 arch-rafa kernel:  __irq_exit_rcu+0x8b/0xc0
juin 13 18:57:09 arch-rafa kernel:  sysvec_apic_timer_interrupt+0x72/0x90
juin 13 18:57:09 arch-rafa kernel:  </IRQ>
juin 13 18:57:09 arch-rafa kernel:  <TASK>
juin 13 18:57:09 arch-rafa kernel:  asm_sysvec_apic_timer_interrupt+0x16/0x20
juin 13 18:57:09 arch-rafa kernel: RIP: 0010:cpuidle_enter_state+0xdc/0x380
juin 13 18:57:09 arch-rafa kernel: Code: 00 00 31 ff e8 85 81 80 ff 45 84 ff 74 16 9c 58 0f 1f 40 00 f6 c4 02 0f 85 8f 02 00 0>
juin 13 18:57:09 arch-rafa kernel: RSP: 0018:ffffbda040167e90 EFLAGS: 00000246
juin 13 18:57:09 arch-rafa kernel: RAX: ffff9e943ea72cc0 RBX: 0000000000000002 RCX: 0000000000000000
juin 13 18:57:09 arch-rafa kernel: RDX: 000000b7173feb32 RSI: fffffff986b2be69 RDI: 0000000000000000
juin 13 18:57:09 arch-rafa kernel: RBP: ffff9e8d45ee3400 R08: 0000000000000002 R09: 00000000238e3989
juin 13 18:57:09 arch-rafa kernel: R10: 000000000001d1c1 R11: 000000000000afc8 R12: ffffffff9f551280
juin 13 18:57:09 arch-rafa kernel: R13: 000000b7173feb32 R14: 0000000000000002 R15: 0000000000000000
juin 13 18:57:09 arch-rafa kernel:  cpuidle_enter+0x2d/0x40
juin 13 18:57:09 arch-rafa kernel:  do_idle+0x1ba/0x220

loqs · 2022-06-13 17:56:28

See https://bugzilla.kernel.org/show_bug.cgi?id=215708 or in a search engine use the terms: cpuidle_enter_state pfifo_fast_reset
Seems to be an unfixed issue in in the r8169 module that has been present for multiple kernel releases.

seth · 2022-06-13 19:09:08

8168 chip?

lspci

rafalou38 · 2022-06-14 15:43:03

seth wrote:

8168 chip?
lspci

here it is:

[rafael@arch-rafa ~]$ lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
00:08.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 7
01:00.0 Non-Volatile memory controller: Phison Electronics Corporation E12 NVMe Controller (rev 01)
20:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream
21:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
21:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
21:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
21:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
21:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
21:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
21:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
22:00.0 Non-Volatile memory controller: Micron/Crucial Technology Device 5407
26:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
27:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
28:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8812AE 802.11ac PCIe Wireless Network Adapter (rev 01)
2a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
2a:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
2a:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
2b:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
2c:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
2d:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] (rev a1)
2d:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio Controller (rev a1)
2d:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host Controller (rev a1)
2d:00.3 Serial bus controller: NVIDIA Corporation TU106 USB Type-C UCSI Controller (rev a1)
2e:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function
2f:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
2f:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
2f:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller
30:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
31:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)

seth · 2022-06-14 16:08:54

27:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

https://archlinux.org/packages/community/x86_64/r8168/

rafalou38 · 2022-06-14 16:27:59

seth wrote:

27:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

https://archlinux.org/packages/community/x86_64/r8168/

I just have to install this package to fix it ?
Do I need to enable it or do anything else to make it work ?

seth · 2022-06-14 18:17:07

I just have to install this package to fix it ?

Just installing it should™ result in the r8168 module being used instead of r8169 and given the presented traces that *might* prevent the crashes.

rafalou38 · 2022-06-14 19:41:01

I really don't know what appended, but I installed it and I think it killed my motherboard integrated Ethernet adapter

I can't use Ethernet anymore
on arch, I get something like:
eth0 cmd = 0xff, should be 0x07

and on Windows, I get the error:
Realtek PCIe GbE Family Controller has a Hardware IO error
followed by a reset of the card every 3 minutes

seth · 2022-06-14 19:46:13

The driver cannot kill the hardware (well, it should not be able to do so - that would be a massive HW bug)
Uninstalling it will get you the status quo ante, however:

and on Windows

Third link below. Mandatory.

rafalou38 · 2022-06-14 20:03:24

seth wrote:

The driver cannot kill the hardware (well, it should not be able to do so - that would be a massive HW bug)
Uninstalling it will get you the status quo ante, however:
and on Windows
Third link below. Mandatory.

I should disable hibernation even if Linux and windows are not on the same SSD?

Thank you for all the help

Last edited by rafalou38 (2022-06-14 20:03:56)

seth · 2022-06-14 20:14:31

The storage location is irrelevant - it's that you're effectively running two OS at the same time (nb. that the pitfall w/ windows is that by default it doesn't really shutdown - it only hibernates and calls that "fast start")
NICs are a frequent victim to that situation so this might very well be the root of your problems.

rafalou38 · 2022-06-15 12:38:34

I uninstalled it and now the ethernet is back but I still have crashes, expect that now the logs from journalctl aren't even present after rebooting
I sometimes get
watchdog: BUG: soft lockup - CPU#(x) stuck for (x)s! [swapper/13:0]
in the tty before the crash

seth · 2022-06-15 12:53:55

Disable windows fast start and reboot windows and linux twice (voodoo reasons)
Also post the journal from a boot w/ the 8168 module.

rafalou38 · 2022-06-16 15:04:29

Ok so i did what you said:
disabled windows fast startup (already done)
Restarted Windows 2 times (restart options)
shutdown windows
unplugged power
booted linux
restarted linux 2 times ("reboot")
(i get watch dog did not stop! 2 times when rebooting)

here are the logs:

without the module: https://pastebin.com/sbsz1r6G (crash is not present because the log is not present after)
while installing the module: https://pastebin.com/PFaL4Eh5
booting with the module: https://pastebin.com/DcZx2F6X

after booting with the module it worked, and I had Ethernet for about 15 minutes until it crashed and when the system rebooted,
I had the same issue as before: no Ethernet and
enp39s0: pci link is down
enp39s0: cmd 0xff, should be 0x07
multiple times followed by crash, every time after less than 5 minutes

If I unplug the computer and boot I'm back with Ethernet, and it again works for about 15 minutes until it again crashes without any error message visible in journalctl -b -f

Last edited by rafalou38 (2022-06-16 15:29:33)

seth · 2022-06-16 19:35:25

when the system rebooted, I had the same issue as before: no ethernet

Do you have a journal of that boot?
If you can, avoid hard reboots: https://wiki.archlinux.org/title/Keyboa … el_(SysRq)
This will preserve the relevant journals.

You're btw. running on the nouveau kernel module - there's a great chance that graphical "crashes" are caused by that rather than the 8168 drivers.
(If you want to install the nvidia blob, pass "ibt=off" to the kernel, search the forum or the nvidia wiki page)

Arch Linux

#1 2022-06-13 17:45:56

Arch crashes and restarts after a few minutes

#2 2022-06-13 17:56:28

Re: Arch crashes and restarts after a few minutes

#3 2022-06-13 19:09:08

Re: Arch crashes and restarts after a few minutes

#4 2022-06-14 15:43:03

Re: Arch crashes and restarts after a few minutes

#5 2022-06-14 16:08:54

Re: Arch crashes and restarts after a few minutes

#6 2022-06-14 16:27:59

Re: Arch crashes and restarts after a few minutes

#7 2022-06-14 18:17:07

Re: Arch crashes and restarts after a few minutes

#8 2022-06-14 19:41:01

Re: Arch crashes and restarts after a few minutes

#9 2022-06-14 19:46:13

Re: Arch crashes and restarts after a few minutes

#10 2022-06-14 20:03:24

Re: Arch crashes and restarts after a few minutes

#11 2022-06-14 20:14:31

Re: Arch crashes and restarts after a few minutes

#12 2022-06-15 12:38:34

Re: Arch crashes and restarts after a few minutes

#13 2022-06-15 12:53:55

Re: Arch crashes and restarts after a few minutes

#14 2022-06-16 15:04:29

Re: Arch crashes and restarts after a few minutes

#15 2022-06-16 19:35:25

Re: Arch crashes and restarts after a few minutes

Board footer