[SOLVED] Kernel error from enp2s0

Ztjuh · 2018-09-21 08:44:39

What can I do to investigate this, I googled around a bit and disabling ipv6 didn't work.

Sep 21 10:34:48 Rampage-X kernel: enp2s0: hw csum failure
Sep 21 10:34:48 Rampage-X kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.18.8-arch1-1-ARCH #1
Sep 21 10:34:48 Rampage-X kernel: Hardware name: System manufacturer Rampage Extreme/Rampage Extreme, BIOS 1301    07/27/2009
Sep 21 10:34:48 Rampage-X kernel: Call Trace:
Sep 21 10:34:48 Rampage-X kernel:  <IRQ>
Sep 21 10:34:48 Rampage-X kernel:  dump_stack+0x5c/0x80
Sep 21 10:34:48 Rampage-X kernel:  __skb_checksum_complete+0xac/0xc0
Sep 21 10:34:48 Rampage-X kernel:  __udp4_lib_rcv+0x6b0/0xc80
Sep 21 10:34:48 Rampage-X kernel:  ? ip_route_input_rcu+0x46/0x2a0
Sep 21 10:34:48 Rampage-X kernel:  ? recalibrate_cpu_khz+0x10/0x10
Sep 21 10:34:48 Rampage-X kernel:  ip_local_deliver_finish+0xa1/0x210
Sep 21 10:34:48 Rampage-X kernel:  ip_local_deliver+0x59/0x120
Sep 21 10:34:48 Rampage-X kernel:  ? ip_rcv_finish+0xac/0x450
Sep 21 10:34:48 Rampage-X kernel:  ip_rcv+0x27e/0x3e8
Sep 21 10:34:48 Rampage-X kernel:  __netif_receive_skb_core+0x5dc/0xbb0
Sep 21 10:34:48 Rampage-X kernel:  ? udp_gro_receive+0x13d/0x180
Sep 21 10:34:48 Rampage-X kernel:  ? inet_gro_receive+0x263/0x2d0
Sep 21 10:34:48 Rampage-X kernel:  netif_receive_skb_internal+0x4a/0x140
Sep 21 10:34:48 Rampage-X kernel:  napi_gro_receive+0xd1/0xf0
Sep 21 10:34:48 Rampage-X kernel:  sky2_poll+0x74d/0xdc0 [sky2]
Sep 21 10:34:48 Rampage-X kernel:  ? resched_curr+0x23/0xd0
Sep 21 10:34:48 Rampage-X kernel:  ? check_preempt_curr+0x7a/0x90
Sep 21 10:34:48 Rampage-X kernel:  net_rx_action+0x144/0x370
Sep 21 10:34:48 Rampage-X kernel:  __do_softirq+0x10d/0x30d
Sep 21 10:34:48 Rampage-X kernel:  irq_exit+0xd9/0xf0
Sep 21 10:34:48 Rampage-X kernel:  do_IRQ+0x9d/0xf0
Sep 21 10:34:48 Rampage-X kernel:  common_interrupt+0xf/0xf
Sep 21 10:34:48 Rampage-X kernel:  </IRQ>
Sep 21 10:34:48 Rampage-X kernel: RIP: 0010:mwait_idle+0x8d/0x180
Sep 21 10:34:48 Rampage-X kernel: Code: ae f0 31 d2 65 48 8b 04 25 00 5c 01 00 48 89 d1 0f 01 c8 48 8b 00 48 c1 e8 03 83 e0 01 0f 85 d7 00 00 00 48 89 c1 fb 0f 01 c9 <e8> 5e 8d c2 ff 89 c5 66 66 66 66 90 eb 8a 65 8b 05 3e 93 a5 4d 89
Sep 21 10:34:48 Rampage-X kernel: RSP: 0018:ffffadd180ce3eb8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffdc
Sep 21 10:34:48 Rampage-X kernel: RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000
Sep 21 10:34:48 Rampage-X kernel: RDX: 0000000000000000 RSI: ffffffffb2c8d286 RDI: ffffffffb2c9523d
Sep 21 10:34:48 Rampage-X kernel: RBP: 0000000000000001 R08: ffffadd182d5fde8 R09: 0000000000000000
Sep 21 10:34:48 Rampage-X kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
Sep 21 10:34:48 Rampage-X kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Sep 21 10:34:48 Rampage-X kernel:  ? mwait_idle+0x3d/0x180
Sep 21 10:34:48 Rampage-X kernel:  do_idle+0x1d5/0x250
Sep 21 10:34:48 Rampage-X kernel:  cpu_startup_entry+0x6f/0x80
Sep 21 10:34:48 Rampage-X kernel:  start_secondary+0x1aa/0x200
Sep 21 10:34:48 Rampage-X kernel:  secondary_startup_64+0xa5/0xb0

Last edited by Ztjuh (2018-09-22 18:33:20)

seth · 2018-09-21 10:19:47

1. please wrape output in "code" tags, not "quote" tags.
2. enp2s0 is a completely generic name, your interface is driven by the sky2 module, some marvell yukon chip - check lspci/lsusb and also record your actual system (soem notebook, I guess)
3. https://www.google.com/search?q="sky2"+"hw+csum+failure" - seems a very old and very common issue
4. please provide a complete dmesg for surrounding issues

You could try the "disable_msi" parameter (as there's at least some relation to interrupts in the backtrace)

Ztjuh · 2018-09-21 15:37:14

No it's a old Asus Rampage Extreme. It has 2 ethernet ports but I guess they use the same chip...

Here is the output of lspci:

00:00.0 Host bridge: Intel Corporation 82X38/X48 Express DRAM Controller (rev 01)
00:01.0 PCI bridge: Intel Corporation 82X38/X48 Express Host-Primary PCI Express Bridge (rev 01)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 02)
00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 02)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)
00:1f.0 ISA bridge: Intel Corporation 82801IR (ICH9R) LPC Interface Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02)
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12)
04:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev c0)

lsusb:

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Also did: modprobe sky2 disable_msi=1, and rebooted.

Here is the output of dmesg

Strange thing is it didn't happen a couple of kernels ago... I don't know which kernel it was though.

Last edited by Ztjuh (2018-09-21 15:39:14)

seth · 2018-09-21 17:36:09

Try the lts kernel, also see https://wiki.archlinux.org/index.php/Ke … le_options (loading an already loaded module does nothing and whatever it would have done is void with the next reboot)

Ztjuh · 2018-09-22 18:17:38

Thank you, I will try this later on because I can't reboot the PC all the time!

For now I found out that disabling 'rx checksumming' (ethtool -K enp2s0 rx off), fixed the issue (or at least suppress the error from showing up in the journalctl).

Also made a service file to exec the command on every boot:

[Unit]
Description=Network Fix (enp2s0)
Before=NetworkManager-wait-online.service

[Service]
Type=oneshot
ExecStart=/usr/bin/ethtool -K enp2s0 rx off

Maybe not the best solution but I guess it will work

Last edited by Ztjuh (2018-09-22 18:55:57)

Arch Linux

#1 2018-09-21 08:44:39

[SOLVED] Kernel error from enp2s0

#2 2018-09-21 10:19:47

Re: [SOLVED] Kernel error from enp2s0

#3 2018-09-21 15:37:14

Re: [SOLVED] Kernel error from enp2s0

#4 2018-09-21 17:36:09

Re: [SOLVED] Kernel error from enp2s0

#5 2018-09-22 18:17:38

Re: [SOLVED] Kernel error from enp2s0

Board footer