You are not logged in.

Pages: 1 2

#1 2023-10-15 11:23:18

Morta
Member
Registered: 2019-07-07
Posts: 660

Problem with Intel NIC

Hi,

I have problem with a Intel NIC with connection lost and Kernel 6.5.6. I have downgraded till 6.5.4 but still the same behavior.


Over KVM is not a problem. lspci shows me Intel NIC X540-AT2. I get a IP and all other devices works well in the network.

Last edited by Morta (2023-10-15 11:25:52)

Offline

#2 2023-10-15 11:47:38

loqs
Member
Registered: 2014-03-06
Posts: 18,877

Re: Problem with Intel NIC

You did not include the full system journal from a boot with the issue.  Is the KVM guest which can use the NIC running one of the kernels that has the issue on the host?  Have you tried 6.5.7.arch1-1?

Last edited by loqs (2023-10-15 11:48:00)

Offline

#3 2023-10-15 12:07:30

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: Problem with Intel NIC

journalctl -b -1

http://0x0.st/H4dP.txt

No I haven't tried 6.5.7arch1-1. I'm on it.

Last edited by Morta (2023-10-15 12:10:34)

Offline

#4 2023-10-15 12:19:06

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: Problem with Intel NIC

I have tested 6.5.7

Here a screenshot from the KVM and a error of the network. Same behavior with qbittorrent or openssh

http://0x0.st/H4dq.png

Offline

#5 2023-10-15 13:28:51

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,422

Re: Problem with Intel NIC

Oct 15 11:04:20 5erver kernel: igb: Intel(R) Gigabit Ethernet Network Driver
Oct 15 11:04:20 5erver kernel: igb: Copyright (c) 2007-2014 Intel Corporation.
Oct 15 11:04:20 5erver kernel: igb 0000:08:00.0: added PHC on eth0
Oct 15 11:04:20 5erver kernel: igb 0000:08:00.0: Intel(R) Gigabit Ethernet Network Connection
Oct 15 11:04:21 5erver kernel: igb 0000:08:00.0: eth0: (PCIe:2.5Gb/s:Width x1) 04:d9:f5:bc:8f:c6
Oct 15 11:04:21 5erver kernel: igb 0000:08:00.0: eth0: PBA No: 000300-000
Oct 15 11:04:21 5erver kernel: igb 0000:08:00.0: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)
Oct 15 11:04:21 5erver kernel: igb 0000:09:00.0: added PHC on eth1
Oct 15 11:04:21 5erver kernel: igb 0000:09:00.0: Intel(R) Gigabit Ethernet Network Connection
Oct 15 11:04:21 5erver kernel: igb 0000:09:00.0: eth1: (PCIe:2.5Gb/s:Width x1) 04:d9:f5:bc:8f:c7
Oct 15 11:04:21 5erver kernel: igb 0000:09:00.0: eth1: PBA No: 000300-000
Oct 15 11:04:21 5erver kernel: igb 0000:09:00.0: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)
Oct 15 11:04:21 5erver kernel: igb 0000:0a:00.0: added PHC on eth2
Oct 15 11:04:21 5erver kernel: igb 0000:0a:00.0: Intel(R) Gigabit Ethernet Network Connection
Oct 15 11:04:21 5erver kernel: igb 0000:0a:00.0: eth2: (PCIe:2.5Gb/s:Width x1) 04:d9:f5:bc:8f:c8
Oct 15 11:04:21 5erver kernel: igb 0000:0a:00.0: eth2: PBA No: 000300-000
Oct 15 11:04:21 5erver kernel: igb 0000:0a:00.0: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)
Oct 15 11:04:21 5erver kernel: igb 0000:0b:00.0: added PHC on eth3
Oct 15 11:04:21 5erver kernel: igb 0000:0b:00.0: Intel(R) Gigabit Ethernet Network Connection
Oct 15 11:04:21 5erver kernel: igb 0000:0b:00.0: eth3: (PCIe:2.5Gb/s:Width x1) 04:d9:f5:bc:8f:c9
Oct 15 11:04:21 5erver kernel: igb 0000:0b:00.0: eth3: PBA No: 000300-000
Oct 15 11:04:21 5erver kernel: igb 0000:0b:00.0: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)
Oct 15 11:04:21 5erver kernel: igb 0000:08:00.0 enp8s0: renamed from eth0
Oct 15 11:04:21 5erver kernel: igb 0000:09:00.0 enp9s0: renamed from eth1
Oct 15 11:04:21 5erver kernel: igb 0000:0b:00.0 enp11s0: renamed from eth3
Oct 15 11:04:21 5erver kernel: igb 0000:0a:00.0 enp10s0: renamed from eth2
Oct 15 13:10:42 5erver NetworkManager[1213]: <info>  [1697368242.4266] device (enp7s0f1): carrier: link connected
Oct 15 13:10:53 5erver NetworkManager[1213]: <info>  [1697368253.9196] device (enp7s0f0): carrier: link connected
Oct 15 13:10:54 5erver NetworkManager[1213]: <info>  [1697368254.0221] device (bond0): carrier: link connected
Oct 15 13:12:54 5erver NetworkManager[1213]: <info>  [1697368374.3671] dhcp4 (bond0): state changed new lease, address=192.168.1.100
…
Oct 15 13:14:01 5erver systemd[1]: Stopped target Network.
Oct 15 13:14:01 5erver systemd[1]: Stopping Network Manager...
Oct 15 13:14:01 5erver NetworkManager[1213]: <info>  [1697368441.6751] caught SIGTERM, shutting down normally.
Oct 15 13:14:01 5erver NetworkManager[1213]: <info>  [1697368441.6760] device (bond0): bond port enp7s0f0 was detached
Oct 15 13:14:01 5erver NetworkManager[1213]: <info>  [1697368441.6761] device (bond0): bond port enp7s0f1 was detached
…
Oct 15 13:14:01 5erver NetworkManager[1213]: <info>  [1697368441.6766] dhcp4 (bond0): state changed no lease

Inbetween the bond device getting a lease and you stopping NM there's a lot going on in the journal - what's your actual metric for "Intel NIC with connection lost"
Can you at this point still ping the _gateway? What are the outputs of "ip a; ip r" in that situation?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#6 2023-10-15 18:47:23

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: Problem with Intel NIC

[morta@5erver ~]$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp8s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 04:d9:f5:bc:8f:c6 brd ff:ff:ff:ff:ff:ff
3: enp9s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 04:d9:f5:bc:8f:c7 brd ff:ff:ff:ff:ff:ff
4: enp10s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 04:d9:f5:bc:8f:c8 brd ff:ff:ff:ff:ff:ff
5: enp11s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 04:d9:f5:bc:8f:c9 brd ff:ff:ff:ff:ff:ff
6: enp7s0f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
    link/ether 4e:b7:bc:18:c0:bf brd ff:ff:ff:ff:ff:ff permaddr 98:b7:85:89:7e:f8
7: enp7s0f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
    link/ether 4e:b7:bc:18:c0:bf brd ff:ff:ff:ff:ff:ff permaddr 98:b7:85:89:7e:f9
8: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 4e:b7:bc:18:c0:bf brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.100/24 brd 192.168.1.255 scope global dynamic noprefixroute bond0
       valid_lft 5823sec preferred_lft 5823sec
    inet6 2a02:168:a774::2222/128 scope global noprefixroute
       valid_lft forever preferred_lft forever
    inet6 fe80::23ff:3b09:6d1d:1048/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
9: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:53:98:d0:cd brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fd00::1/80 scope global tentative
       valid_lft forever preferred_lft forever
    inet6 fe80::1/64 scope link tentative
       valid_lft forever preferred_lft forever
10: br-abac02be342e: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:5e:87:6f:53 brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 brd 172.18.255.255 scope global br-abac02be342e
       valid_lft forever preferred_lft forever
    inet6 fd00:dead:beef::1/48 scope global tentative
       valid_lft forever preferred_lft forever
    inet6 fe80::1/64 scope link tentative
       valid_lft forever preferred_lft forever
[morta@5erver ~]$ ip r
default via 192.168.1.1 dev bond0 proto dhcp src 192.168.1.100 metric 300
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
172.18.0.0/16 dev br-abac02be342e proto kernel scope link src 172.18.0.1 linkdown
192.168.1.0/24 dev bond0 proto kernel scope link src 192.168.1.100 metric 300
[morta@5erver ~]$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.121 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.132 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.169 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.117 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.182 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=0.132 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=0.117 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=0.116 ms
From 192.168.1.100 icmp_seq=10 Destination Host Unreachable
From 192.168.1.100 icmp_seq=11 Destination Host Unreachable
From 192.168.1.100 icmp_seq=12 Destination Host Unreachable
From 192.168.1.100 icmp_seq=13 Destination Host Unreachable
From 192.168.1.100 icmp_seq=14 Destination Host Unreachable
From 192.168.1.100 icmp_seq=15 Destination Host Unreachable
From 192.168.1.100 icmp_seq=16 Destination Host Unreachable
ping: sendmsg: No route to host
From 192.168.1.100 icmp_seq=17 Destination Host Unreachable
From 192.168.1.100 icmp_seq=18 Destination Host Unreachable
64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=26.9 ms
64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=0.144 ms
64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=0.109 ms
64 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=0.152 ms
64 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=0.140 ms
64 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=0.157 ms
64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=0.151 ms
64 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=0.111 ms
64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=0.097 ms
64 bytes from 192.168.1.1: icmp_seq=29 ttl=64 time=0.176 ms
64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=0.198 ms

Last edited by Morta (2023-10-15 18:58:40)

Offline

#7 2023-10-15 18:50:30

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,422

Re: Problem with Intel NIC

Please use [code][/code] tags, not "quote" tags. Edit your post in this regard.

So it flickers?
What if you don't bond the NICs and try just one of them (and then the other)?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#8 2023-10-15 19:03:23

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: Problem with Intel NIC

seth wrote:

Please use [code][/code] tags, not "quote" tags. Edit your post in this regard.
Done

So it flickers?

YES

What if you don't bond the NICs and try just one of them (and then the other)?

[morta@5erver ~]$ sudo systemctl status NetworkManager
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: disabled)
     Active: active (running) since Sun 2023-10-15 20:51:48 CEST; 10min ago
       Docs: man:NetworkManager(8)
   Main PID: 1216 (NetworkManager)
      Tasks: 4 (limit: 76961)
     Memory: 30.7M
        CPU: 598ms
     CGroup: /system.slice/NetworkManager.service
             └─1216 /usr/bin/NetworkManager --no-daemon

Oct 15 21:01:26 5erver NetworkManager[1216]: <info>  [1697396486.2755] device (enp7s0f1): carrier: link connected
Oct 15 21:01:47 5erver NetworkManager[1216]: <info>  [1697396507.6371] device (enp7s0f0): carrier: link connected
Oct 15 21:01:47 5erver NetworkManager[1216]: <info>  [1697396507.6519] device (bond0): carrier: link connected
Oct 15 21:01:48 5erver NetworkManager[1216]: <info>  [1697396508.0178] device (enp7s0f1): carrier: link connected
Oct 15 21:02:08 5erver NetworkManager[1216]: <info>  [1697396528.8114] device (enp7s0f0): carrier: link connected
Oct 15 21:02:08 5erver NetworkManager[1216]: <info>  [1697396528.8953] device (bond0): carrier: link connected
Oct 15 21:02:09 5erver NetworkManager[1216]: <info>  [1697396529.0168] device (enp7s0f1): carrier: link connected
Oct 15 21:02:30 5erver NetworkManager[1216]: <info>  [1697396550.0387] device (enp7s0f0): carrier: link connected
Oct 15 21:02:30 5erver NetworkManager[1216]: <info>  [1697396550.1353] device (bond0): carrier: link connected
Oct 15 21:02:30 5erver NetworkManager[1216]: <info>  [1697396550.1796] device (enp7s0f1): carrier: link connected

Offline

#9 2023-10-15 19:08:10

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: Problem with Intel NIC

I plugged one cable of the NIC out. Still this behaviorism.

 
[morta@5erver ~]$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.173 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.114 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.090 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.087 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.129 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=0.117 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=0.176 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=0.095 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=0.081 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=0.134 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=0.123 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=0.119 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=0.120 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=0.153 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=0.082 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=0.153 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=0.105 ms
From 192.168.1.100 icmp_seq=18 Destination Host Unreachable
From 192.168.1.100 icmp_seq=19 Destination Host Unreachable
From 192.168.1.100 icmp_seq=20 Destination Host Unreachable
From 192.168.1.100 icmp_seq=21 Destination Host Unreachable
From 192.168.1.100 icmp_seq=22 Destination Host Unreachable
From 192.168.1.100 icmp_seq=23 Destination Host Unreachable
From 192.168.1.100 icmp_seq=24 Destination Host Unreachable
From 192.168.1.100 icmp_seq=25 Destination Host Unreachable
From 192.168.1.100 icmp_seq=26 Destination Host Unreachable
From 192.168.1.100 icmp_seq=27 Destination Host Unreachable
From 192.168.1.100 icmp_seq=28 Destination Host Unreachable
64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=519 ms
64 bytes from 192.168.1.1: icmp_seq=31 ttl=64 time=0.160 ms
64 bytes from 192.168.1.1: icmp_seq=32 ttl=64 time=0.087 ms
64 bytes from 192.168.1.1: icmp_seq=33 ttl=64 time=0.092 ms
64 bytes from 192.168.1.1: icmp_seq=34 ttl=64 time=0.101 ms
64 bytes from 192.168.1.1: icmp_seq=35 ttl=64 time=0.087 ms
64 bytes from 192.168.1.1: icmp_seq=36 ttl=64 time=0.116 ms
64 bytes from 192.168.1.1: icmp_seq=37 ttl=64 time=0.082 ms
64 bytes from 192.168.1.1: icmp_seq=38 ttl=64 time=0.177 ms
From 192.168.1.100 icmp_seq=39 Destination Host Unreachable
From 192.168.1.100 icmp_seq=40 Destination Host Unreachable
From 192.168.1.100 icmp_seq=41 Destination Host Unreachable
From 192.168.1.100 icmp_seq=42 Destination Host Unreachable
From 192.168.1.100 icmp_seq=43 Destination Host Unreachable
From 192.168.1.100 icmp_seq=44 Destination Host Unreachable
From 192.168.1.100 icmp_seq=45 Destination Host Unreachable
From 192.168.1.100 icmp_seq=46 Destination Host Unreachable
From 192.168.1.100 icmp_seq=47 Destination Host Unreachable
From 192.168.1.100 icmp_seq=48 Destination Host Unreachable
From 192.168.1.100 icmp_seq=49 Destination Host Unreachable
From 192.168.1.100 icmp_seq=50 Destination Host Unreachable
64 bytes from 192.168.1.1: icmp_seq=51 ttl=64 time=1452 ms
64 bytes from 192.168.1.1: icmp_seq=52 ttl=64 time=427 ms
ING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.173 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.114 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.090 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.087 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.129 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=0.117 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=0.176 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=0.095 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=0.081 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=0.134 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=0.123 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=0.119 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=0.120 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=0.153 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=0.082 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=0.153 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=0.105 ms
From 192.168.1.100 icmp_seq=18 Destination Host Unreachable
From 192.168.1.100 icmp_seq=19 Destination Host Unreachable
From 192.168.1.100 icmp_seq=20 Destination Host Unreachable
From 192.168.1.100 icmp_seq=21 Destination Host Unreachable
From 192.168.1.100 icmp_seq=22 Destination Host Unreachable
From 192.168.1.100 icmp_seq=23 Destination Host Unreachable
From 192.168.1.100 icmp_seq=24 Destination Host Unreachable
From 192.168.1.100 icmp_seq=25 Destination Host Unreachable
From 192.168.1.100 icmp_seq=26 Destination Host Unreachable
From 192.168.1.100 icmp_seq=27 Destination Host Unreachable
From 192.168.1.100 icmp_seq=28 Destination Host Unreachable
64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=519 ms
64 bytes from 192.168.1.1: icmp_seq=31 ttl=64 time=0.160 ms
64 bytes from 192.168.1.1: icmp_seq=32 ttl=64 time=0.087 ms
64 bytes from 192.168.1.1: icmp_seq=33 ttl=64 time=0.092 ms

Offline

#10 2023-10-15 19:09:33

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,422

Re: Problem with Intel NIC

Who said anything about unplugging cables, disable the bond.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#11 2023-10-15 20:20:19

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: Problem with Intel NIC

Ok I deleted it.

Now my server has no internet.

Last edited by Morta (2023-10-15 20:20:37)

Offline

#12 2023-10-15 20:30:45

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,422

Re: Problem with Intel NIC

seth wrote:

What if you don't bond the NICs and try just one of them (and then the other)?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#13 2023-10-16 03:33:20

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: Problem with Intel NIC

seth wrote:
seth wrote:

What if you don't bond the NICs and try just one of them (and then the other)?

If I bring each interface up then appear again a bond0 device but I don't no from where. I erase all bond device and connection at NetworkManager.

Offline

#14 2023-10-16 03:56:07

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: Problem with Intel NIC

ip link set dev enp7s0f0 up

Again display a bond0 device with two IPv6 without IPv4

Offline

#15 2023-10-16 04:50:12

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: Problem with Intel NIC

[morta@5erver ~]$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp8s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 04:d9:f5:bc:8f:c6 brd ff:ff:ff:ff:ff:ff
3: enp9s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 04:d9:f5:bc:8f:c7 brd ff:ff:ff:ff:ff:ff
4: enp10s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 04:d9:f5:bc:8f:c8 brd ff:ff:ff:ff:ff:ff
5: enp11s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 04:d9:f5:bc:8f:c9 brd ff:ff:ff:ff:ff:ff
6: enp7s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 98:b7:85:89:7e:f8 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.100/24 brd 192.168.1.255 scope global dynamic noprefixroute enp7s0f0
       valid_lft 6774sec preferred_lft 6774sec
    inet6 2a02:168:a774::2222/128 scope global noprefixroute
       valid_lft forever preferred_lft forever
    inet6 fe80::9042:6e4b:98c3:cdcb/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
7: enp7s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 98:b7:85:89:7e:f9 brd ff:ff:ff:ff:ff:ff
9: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:d7:56:7f:b3 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fd00::1/80 scope global tentative
       valid_lft forever preferred_lft forever
    inet6 fe80::1/64 scope link tentative
       valid_lft forever preferred_lft forever
10: br-abac02be342e: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:53:85:09:cf brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 brd 172.18.255.255 scope global br-abac02be342e
       valid_lft forever preferred_lft forever
    inet6 fd00:dead:beef::1/48 scope global tentative
       valid_lft forever preferred_lft forever
    inet6 fe80::1/64 scope link tentative
       valid_lft forever preferred_lft forever
[morta@5erver ~]$ ping google.ch
PING google.ch (142.250.203.99) 56(84) bytes of data.
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=1 ttl=111 time=2.77 ms
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=2 ttl=111 time=2.76 ms
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=3 ttl=111 time=2.74 ms
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=4 ttl=111 time=2.77 ms
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=5 ttl=111 time=3.01 ms
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=6 ttl=111 time=2.95 ms
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=7 ttl=111 time=2.89 ms
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=8 ttl=111 time=2.76 ms
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=9 ttl=111 time=2.94 ms
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=10 ttl=111 time=2.85 ms
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=11 ttl=111 time=2.79 ms
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=12 ttl=111 time=2.97 ms
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=13 ttl=111 time=2.97 ms
From 5erver (192.168.1.100) icmp_seq=14 Destination Host Unreachable
From 5erver (192.168.1.100) icmp_seq=15 Destination Host Unreachable
From 5erver (192.168.1.100) icmp_seq=16 Destination Host Unreachable
From 5erver (192.168.1.100) icmp_seq=17 Destination Host Unreachable
ping: sendmsg: No route to host
From 5erver (192.168.1.100) icmp_seq=18 Destination Host Unreachable
From 5erver (192.168.1.100) icmp_seq=19 Destination Host Unreachable
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=21 ttl=111 time=2.93 ms
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=22 ttl=111 time=2.79 ms
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=23 ttl=111 time=2.78 ms
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=24 ttl=111 time=2.98 ms
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=25 ttl=111 time=2.90 ms
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=26 ttl=111 time=2.92 ms
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=27 ttl=111 time=2.88 ms
64 bytes from zrh04s16-in-f3.1e100.net (142.250.203.99): icmp_seq=28 ttl=111 time=2.95 ms
^C
--- google.ch ping statistics ---
28 packets transmitted, 21 received, +6 errors, 25% packet loss, time 27113ms
rtt min/avg/max/mdev = 2.742/2.871/3.011/0.087 ms, pipe 3
[morta@5erver ~]$

Offline

#16 2023-10-16 06:41:10

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,422

Re: Problem with Intel NIC

_gateway, not google.ch - we don't want your ISP in the mix (yet)
Disable docker and the bridge and does enp7s0f1 provide a stable connection?
What does the system journal look like while the ping drops out ("sudo journalctl -f")

Also please don't power-post, edit your previous post to mend/extend it if nobody has replied yet, thanks.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#17 2023-10-16 07:37:14

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: Problem with Intel NIC

seth wrote:

_gateway, not google.ch - we don't want your ISP in the mix (yet)
Disable docker and the bridge and does enp7s0f1 provide a stable connection?
What does the system journal look like while the ping drops out ("sudo journalctl -f")

Also please don't power-post, edit your previous post to mend/extend it if nobody has replied yet, thanks.

[morta@5erver ~]$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp8s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 04:d9:f5:bc:8f:c6 brd ff:ff:ff:ff:ff:ff
3: enp9s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 04:d9:f5:bc:8f:c7 brd ff:ff:ff:ff:ff:ff
4: enp10s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 04:d9:f5:bc:8f:c8 brd ff:ff:ff:ff:ff:ff
5: enp11s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 04:d9:f5:bc:8f:c9 brd ff:ff:ff:ff:ff:ff
6: enp7s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 98:b7:85:89:7e:f8 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.100/24 brd 192.168.1.255 scope global dynamic noprefixroute enp7s0f0
       valid_lft 7049sec preferred_lft 7049sec
    inet6 2a02:168:a774::2000/128 scope global noprefixroute
       valid_lft forever preferred_lft forever
    inet6 fe80::9042:6e4b:98c3:cdcb/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
7: enp7s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 98:b7:85:89:7e:f9 brd ff:ff:ff:ff:ff:ff
[morta@5erver ~]$ sudo nmcli
enp7s0f0: connected to Wired connection 3
        "Intel X540-AT2"
        ethernet (ixgbe), 98:B7:85:89:7E:F8, hw, sriov, mtu 1500
        ip4 default, ip6 default
        inet4 192.168.1.100/24
        route4 default via 192.168.1.1 metric 100
        route4 192.168.1.0/24 metric 100
        inet6 fe80::9042:6e4b:98c3:cdcb/64
        inet6 2a02:168:a774::2000/128
        route6 2a02:168:a774::2000/128 metric 100
        route6 2a02:168:a774::/64 metric 100
        route6 fe80::/64 metric 1024
        route6 default via fe80::5a9c:fcff:fe10:fa2a metric 100

lo: connected (externally) to lo
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
        inet4 127.0.0.1/8
        inet6 ::1/128

enp10s0: unavailable
        "Intel I210"
        ethernet (igb), 04:D9:F5:BC:8F:C8, hw, mtu 1500

enp11s0: unavailable
        "Intel I210"
        ethernet (igb), 04:D9:F5:BC:8F:C9, hw, mtu 1500

enp7s0f1: unavailable
        "Intel X540-AT2"
        ethernet (ixgbe), 98:B7:85:89:7E:F9, hw, sriov, mtu 1500

enp8s0: unavailable
        "Intel I210"
        ethernet (igb), 04:D9:F5:BC:8F:C6, hw, mtu 1500

enp9s0: unavailable
        "Intel I210"
        ethernet (igb), 04:D9:F5:BC:8F:C7, hw, mtu 1500

DNS configuration:
        servers: 192.168.1.1
        domains: netw0rk
        interface: enp7s0f0

        servers: 2a02:168:a774::1
        domains: r0uter.net0rk
        interface: enp7s0f0

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
[morta@5erver ~]$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.120 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.090 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.124 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.095 ms
From 192.168.1.100 icmp_seq=5 Destination Host Unreachable
From 192.168.1.100 icmp_seq=6 Destination Host Unreachable
From 192.168.1.100 icmp_seq=8 Destination Host Unreachable
From 192.168.1.100 icmp_seq=9 Destination Host Unreachable
From 192.168.1.100 icmp_seq=10 Destination Host Unreachable
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=0.130 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=0.127 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=0.225 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=0.096 ms
[morta@5erver ~]$ sudo journalctl -f
Oct 16 09:35:43 5erver acme.sh[1485792]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:43 5erver acme.sh[1485798]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:43 5erver acme.sh[1485841]: [Mon Oct 16 09:35:43 AM CEST 2023] Adding txt value: RVKmxE45ORFeQw1RnYs_6aK-qEpdQfbGwF8u-l2ZS1g for domain:  _acme-challenge.joelmueller.ch
Oct 16 09:35:44 5erver systemd[1]: lunch-crashed-services.service: Scheduled restart job, restart counter is at 4449.
Oct 16 09:35:44 5erver systemd[1]: Started Execute services if crashed.
Oct 16 09:35:44 5erver systemd[1]: lunch-crashed-services.service: Deactivated successfully.
Oct 16 09:35:46 5erver dbus-daemon[1192]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.10641' (uid=0 pid=1485975 comm="sudo journalctl -f")
Oct 16 09:35:46 5erver dbus-daemon[1192]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 16 09:35:46 5erver sudo[1485975]:    morta : TTY=pts/1 ; PWD=/home/morta ; USER=root ; COMMAND=/usr/bin/journalctl -f
Oct 16 09:35:46 5erver sudo[1485975]: pam_unix(sudo:session): session opened for user root(uid=0) by morta(uid=1000)
Oct 16 09:35:46 5erver kernel: ixgbe 0000:07:00.0 enp7s0f0: NIC Link is Down
Oct 16 09:35:46 5erver jellyfin[1278]: [09:35:46] [DBG] [34] Jellyfin.Networking.Manager.NetworkManager: Network availability changed.
Oct 16 09:35:46 5erver jellyfin[1278]: [09:35:46] [DBG] [34] Jellyfin.Networking.Manager.NetworkManager: Network Address Change Event.
Oct 16 09:35:48 5erver jellyfin[1278]: [09:35:48] [DBG] [72] Jellyfin.Networking.Manager.NetworkManager: Refreshing interfaces.
Oct 16 09:35:48 5erver jellyfin[1278]: [09:35:48] [ERR] [72] Jellyfin.Networking.Manager.NetworkManager: No interfaces information available. Resolving DNS name.
Oct 16 09:35:48 5erver jellyfin[1278]: [09:35:48] [DBG] [72] Jellyfin.Networking.Manager.NetworkManager: Discovered 6 interfaces.
Oct 16 09:35:48 5erver jellyfin[1278]: [09:35:48] [DBG] [72] Jellyfin.Networking.Manager.NetworkManager: Interfaces addresses : [127.0.0.1/32,::1/32,192.168.1.100/32,2a02:168:a774::2000/32,fe80::9042:6e4b:98c3:cdcb%6/32,127.0.0.1/8]
Oct 16 09:35:48 5erver jellyfin[1278]: [09:35:48] [DBG] [72] Jellyfin.Networking.Manager.NetworkManager: Refreshing LAN information.
Oct 16 09:35:48 5erver jellyfin[1278]: [09:35:48] [DBG] [72] Jellyfin.Networking.Manager.NetworkManager: Using LAN interface addresses as user provided no LAN details.
Oct 16 09:35:48 5erver jellyfin[1278]: [09:35:48] [INF] [72] Jellyfin.Networking.Manager.NetworkManager: Defined LAN addresses : [fc00::/7,fe80::/10,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]
Oct 16 09:35:48 5erver jellyfin[1278]: [09:35:48] [INF] [72] Jellyfin.Networking.Manager.NetworkManager: Defined LAN exclusions : []
Oct 16 09:35:48 5erver jellyfin[1278]: [09:35:48] [INF] [72] Jellyfin.Networking.Manager.NetworkManager: Using LAN addresses: [fc00::/7,fe80::/10,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]
Oct 16 09:35:49 5erver OoklaServer[1538]: 2023-10-16 07:35:49 [1538 - 37] [Warning] Traceroute error: 113 => No route to host
Oct 16 09:35:49 5erver OoklaServer[1538]: 2023-10-16 07:35:49 [1538 - 37] [Information] CA bundle is empty; skipping
Oct 16 09:35:49 5erver OoklaServer[1538]: 2023-10-16 07:35:49 [1538 - 37] [Error] Failed to upload traceroute. Exception caught: DNS error: Temporary DNS error while resolving: results.speedtest.net
Oct 16 09:35:52 5erver kernel: ixgbe 0000:07:00.0 enp7s0f0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
Oct 16 09:35:52 5erver NetworkManager[1216]: <info>  [1697441752.2136] device (enp7s0f0): carrier: link connected
Oct 16 09:35:52 5erver jellyfin[1278]: [09:35:52] [DBG] [34] Jellyfin.Networking.Manager.NetworkManager: Network availability changed.
Oct 16 09:35:52 5erver jellyfin[1278]: [09:35:52] [DBG] [34] Jellyfin.Networking.Manager.NetworkManager: Network Address Change Event.
Oct 16 09:35:52 5erver acme.sh[1485841]: [Mon Oct 16 09:35:52 AM CEST 2023] invalid domain
Oct 16 09:35:52 5erver acme.sh[1485841]: [Mon Oct 16 09:35:52 AM CEST 2023] Error add txt for domain:_acme-challenge.joelmueller.ch
Oct 16 09:35:52 5erver acme.sh[1484950]: [Mon Oct 16 09:35:52 AM CEST 2023] Please add '--debug' or '--log' to check more details.
Oct 16 09:35:52 5erver acme.sh[1484950]: [Mon Oct 16 09:35:52 AM CEST 2023] See: https://github.com/acmesh-official/acme.sh/wiki/How-to-debug-acme.sh
Oct 16 09:35:52 5erver OoklaServer[1538]: 2023-10-16 07:35:52 [1538 - 548] [Information] TCP uptime: 45843 - total current: 7, queued: 0, blocked: 0, queueFull: 0, concurrent: 84, currentThreads: 9
Oct 16 09:35:53 5erver OoklaServer[1538]: 2023-10-16 07:35:53 [1538 - 553] [Warning] Exception caught: Connection reset by peer on connection on port 8080
Oct 16 09:35:53 5erver OoklaServer[1538]: 2023-10-16 07:35:53 [1538 - 558] [Information] TCP uptime: 45843 - total current: 8, queued: 0, blocked: 0, queueFull: 0, concurrent: 84, currentThreads: 11
Oct 16 09:35:53 5erver OoklaServer[1538]: 2023-10-16 07:35:53 [1538 - 558] [Information] Disconnect NetException: Connection reset by peer
Oct 16 09:35:53 5erver systemd[1]: acme.sh.service: Control process exited, code=exited, status=1/FAILURE
Oct 16 09:35:53 5erver systemd[1]: acme.sh.service: Failed with result 'exit-code'.
Oct 16 09:35:53 5erver systemd[1]: Failed to start Renew Let's Encrypt Certificates.
Oct 16 09:35:53 5erver systemd[1]: acme.sh.service: Consumed 2.977s CPU time.
Oct 16 09:35:54 5erver systemd[1]: acme.sh.service: Scheduled restart job, restart counter is at 1453.
Oct 16 09:35:54 5erver systemd[1]: Starting Renew Let's Encrypt Certificates...
Oct 16 09:35:54 5erver jellyfin[1278]: [09:35:54] [DBG] [72] Jellyfin.Networking.Manager.NetworkManager: Refreshing interfaces.
Oct 16 09:35:54 5erver jellyfin[1278]: [09:35:54] [DBG] [72] Jellyfin.Networking.Manager.NetworkManager: Discovered 5 interfaces.
Oct 16 09:35:54 5erver jellyfin[1278]: [09:35:54] [DBG] [72] Jellyfin.Networking.Manager.NetworkManager: Interfaces addresses : [192.168.1.100/24,2a02:168:a774::2000/128,fe80::9042:6e4b:98c3:cdcb%6/64,127.0.0.1/8,::1/128]
Oct 16 09:35:54 5erver jellyfin[1278]: [09:35:54] [DBG] [72] Jellyfin.Networking.Manager.NetworkManager: Refreshing LAN information.
Oct 16 09:35:54 5erver jellyfin[1278]: [09:35:54] [DBG] [72] Jellyfin.Networking.Manager.NetworkManager: Using LAN interface addresses as user provided no LAN details.
Oct 16 09:35:54 5erver jellyfin[1278]: [09:35:54] [INF] [72] Jellyfin.Networking.Manager.NetworkManager: Defined LAN addresses : [fc00::/7,fe80::/10,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]
Oct 16 09:35:54 5erver jellyfin[1278]: [09:35:54] [INF] [72] Jellyfin.Networking.Manager.NetworkManager: Defined LAN exclusions : []
Oct 16 09:35:54 5erver jellyfin[1278]: [09:35:54] [INF] [72] Jellyfin.Networking.Manager.NetworkManager: Using LAN addresses: [fc00::/7,fe80::/10,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]
Oct 16 09:35:54 5erver systemd[1]: lunch-crashed-services.service: Scheduled restart job, restart counter is at 4450.
Oct 16 09:35:54 5erver systemd[1]: Started Execute services if crashed.
Oct 16 09:35:54 5erver acme.sh[1486256]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:54 5erver acme.sh[1486261]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:54 5erver acme.sh[1486268]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:54 5erver acme.sh[1486273]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:54 5erver acme.sh[1486280]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:54 5erver acme.sh[1486285]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:54 5erver acme.sh[1486292]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:54 5erver systemd[1]: lunch-crashed-services.service: Deactivated successfully.
Oct 16 09:35:54 5erver acme.sh[1486167]: [Mon Oct 16 09:35:54 AM CEST 2023] Using CA: https://acme.zerossl.com/v2/DV90
Oct 16 09:35:54 5erver acme.sh[1486167]: [Mon Oct 16 09:35:54 AM CEST 2023] Multi domain='DNS:joelmueller.ch,DNS:speedtest.joelmueller.ch'
Oct 16 09:35:54 5erver OoklaServer[1538]: 2023-10-16 07:35:54 [1538 - 550] [Information] Disconnect NetException: Connection reset by peer
Oct 16 09:35:54 5erver OoklaServer[1538]: 2023-10-16 07:35:54 [1538 - 556] [Information] Disconnect NetException: Connection reset by peer
Oct 16 09:35:54 5erver OoklaServer[1538]: 2023-10-16 07:35:54 [1538 - 545] [Information] Disconnect NetException: Connection reset by peer
Oct 16 09:35:54 5erver OoklaServer[1538]: 2023-10-16 07:35:54 [1538 - 563] [Information] Disconnect NetException: Connection reset by peer
Oct 16 09:35:54 5erver OoklaServer[1538]: 2023-10-16 07:35:54 [1538 - 553] [Information] TCP uptime: 45845 - total current: 3, queued: 0, blocked: 0, queueFull: 0, concurrent: 84, currentThreads: 5
Oct 16 09:35:54 5erver acme.sh[1486167]: [Mon Oct 16 09:35:54 AM CEST 2023] Getting domain auth token for each domain
Oct 16 09:35:55 5erver OoklaServer[1538]: 2023-10-16 07:35:55 [1538 - 545] [Information] TCP uptime: 45845 - total current: 4, queued: 0, blocked: 0, queueFull: 0, concurrent: 84, currentThreads: 6
Oct 16 09:35:55 5erver OoklaServer[1538]: 2023-10-16 07:35:55 [1538 - 545] [Information] Disconnect NetException: Connection reset by peer
Oct 16 09:35:56 5erver acme.sh[1486692]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:56 5erver acme.sh[1486711]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:56 5erver OoklaServer[1538]: 2023-10-16 07:35:56 [1538 - 563] [Information] TCP uptime: 45847 - total current: 3, queued: 0, blocked: 0, queueFull: 0, concurrent: 84, currentThreads: 5
Oct 16 09:35:56 5erver OoklaServer[1538]: 2023-10-16 07:35:56 [1538 - 545] [Information] TCP uptime: 45847 - total current: 3, queued: 0, blocked: 0, queueFull: 0, concurrent: 84, currentThreads: 5
Oct 16 09:35:56 5erver grafana-server[1604]: logger=cleanup t=2023-10-16T09:35:56.857780482+02:00 level=info msg="Completed cleanup jobs" duration=25.402294ms
Oct 16 09:35:56 5erver acme.sh[1486793]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:56 5erver grafana-server[1604]: logger=plugins.update.checker t=2023-10-16T09:35:56.864295251+02:00 level=info msg="Update check succeeded" duration=30.649925ms
Oct 16 09:35:56 5erver grafana-server[1604]: logger=grafana.update.checker t=2023-10-16T09:35:56.881236287+02:00 level=info msg="Update check succeeded" duration=47.521372ms
Oct 16 09:35:57 5erver acme.sh[1486873]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:57 5erver acme.sh[1486167]: [Mon Oct 16 09:35:57 AM CEST 2023] Getting webroot for domain='joelmueller.ch'
Oct 16 09:35:57 5erver acme.sh[1486908]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:57 5erver acme.sh[1486925]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:57 5erver acme.sh[1486931]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:57 5erver acme.sh[1486937]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:57 5erver acme.sh[1486167]: [Mon Oct 16 09:35:57 AM CEST 2023] Getting webroot for domain='speedtest.joelmueller.ch'
Oct 16 09:35:57 5erver acme.sh[1486971]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:57 5erver acme.sh[1486977]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:57 5erver acme.sh[1486983]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:57 5erver acme.sh[1486989]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:35:57 5erver acme.sh[1487032]: [Mon Oct 16 09:35:57 AM CEST 2023] Adding txt value: jBZoHZX7pJCDDYhTYV04JIC39FBfwgHWz5P5HxFqHXU for domain:  _acme-challenge.joelmueller.ch
Oct 16 09:35:59 5erver OoklaServer[1538]: 2023-10-16 07:35:59 [1538 - 563] [Warning] Exception caught: Connection reset by peer on connection on port 8080
Oct 16 09:35:59 5erver OoklaServer[1538]: 2023-10-16 07:35:59 [1538 - 545] [Information] TCP uptime: 45849 - total current: 3, queued: 0, blocked: 0, queueFull: 0, concurrent: 84, currentThreads: 5
Oct 16 09:35:59 5erver OoklaServer[1538]: 2023-10-16 07:35:59 [1538 - 545] [Information] Disconnect NetException: Connection reset by peer
Oct 16 09:36:00 5erver acme.sh[1487032]: [Mon Oct 16 09:36:00 AM CEST 2023] invalid domain
Oct 16 09:36:00 5erver acme.sh[1487032]: [Mon Oct 16 09:36:00 AM CEST 2023] Error add txt for domain:_acme-challenge.joelmueller.ch
Oct 16 09:36:00 5erver acme.sh[1486167]: [Mon Oct 16 09:36:00 AM CEST 2023] Please add '--debug' or '--log' to check more details.
Oct 16 09:36:00 5erver acme.sh[1486167]: [Mon Oct 16 09:36:00 AM CEST 2023] See: https://github.com/acmesh-official/acme.sh/wiki/How-to-debug-acme.sh
Oct 16 09:36:00 5erver OoklaServer[1538]: 2023-10-16 07:36:00 [1538 - 563] [Information] TCP uptime: 45851 - total current: 3, queued: 0, blocked: 0, queueFull: 0, concurrent: 84, currentThreads: 5
Oct 16 09:36:00 5erver mautrix-whatsapp[1918]: Oct 16, 2023 09:36:00 DBG <iq id="208.93-519" to="s.whatsapp.net" type="get" xmlns="w:p"><ping/></iq> module=Client/Send user_id=@morta:chat.joelmueller.ch
Oct 16 09:36:00 5erver mautrix-whatsapp[1918]: Oct 16, 2023 09:36:00 DBG <iq from="s.whatsapp.net" id="208.93-519" t="1697441760" type="result"/> module=Client/Recv user_id=@morta:chat.joelmueller.ch
Oct 16 09:36:01 5erver crond[1487314]: pam_unix(crond:session): session opened for user root(uid=0) by root(uid=0)
Oct 16 09:36:01 5erver CROND[1487319]: (root) CMD (watch -n 60 /etc/rc.local)
Oct 16 09:36:01 5erver systemd[1]: acme.sh.service: Control process exited, code=exited, status=1/FAILURE
Oct 16 09:36:01 5erver crond[1487334]: sendmail: account default not found: no configuration file available
Oct 16 09:36:01 5erver CROND[1487314]: (root) MAIL (mailed 33 bytes of output but got status 0x004e
                                       )
Oct 16 09:36:01 5erver CROND[1487314]: (root) CMDEND (watch -n 60 /etc/rc.local)
Oct 16 09:36:01 5erver CROND[1487314]: pam_unix(crond:session): session closed for user root
Oct 16 09:36:01 5erver systemd[1]: acme.sh.service: Failed with result 'exit-code'.
Oct 16 09:36:01 5erver systemd[1]: Failed to start Renew Let's Encrypt Certificates.
Oct 16 09:36:01 5erver systemd[1]: acme.sh.service: Consumed 3.431s CPU time.
Oct 16 09:36:01 5erver systemd[1]: acme.sh.service: Scheduled restart job, restart counter is at 1454.
Oct 16 09:36:01 5erver systemd[1]: Starting Renew Let's Encrypt Certificates...
Oct 16 09:36:01 5erver OoklaServer[1538]: 2023-10-16 07:36:01 [1538 - 545] [Information] TCP uptime: 45851 - total current: 2, queued: 0, blocked: 0, queueFull: 0, concurrent: 84, currentThreads: 4
Oct 16 09:36:01 5erver acme.sh[1487432]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:36:01 5erver acme.sh[1487437]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:36:01 5erver acme.sh[1487442]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:36:01 5erver acme.sh[1487447]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:36:01 5erver acme.sh[1487452]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:36:01 5erver acme.sh[1487457]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:36:01 5erver acme.sh[1487462]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:36:02 5erver acme.sh[1487346]: [Mon Oct 16 09:36:02 AM CEST 2023] Using CA: https://acme.zerossl.com/v2/DV90
Oct 16 09:36:02 5erver acme.sh[1487346]: [Mon Oct 16 09:36:02 AM CEST 2023] Multi domain='DNS:joelmueller.ch,DNS:speedtest.joelmueller.ch'
Oct 16 09:36:02 5erver acme.sh[1487346]: [Mon Oct 16 09:36:02 AM CEST 2023] Getting domain auth token for each domain
Oct 16 09:36:03 5erver acme.sh[1487859]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:36:03 5erver acme.sh[1487878]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:36:03 5erver acme.sh[1487960]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:36:03 5erver acme.sh[1488040]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:36:03 5erver acme.sh[1487346]: [Mon Oct 16 09:36:03 AM CEST 2023] Getting webroot for domain='joelmueller.ch'
Oct 16 09:36:03 5erver acme.sh[1488075]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:36:03 5erver acme.sh[1488092]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:36:03 5erver acme.sh[1488098]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:36:04 5erver acme.sh[1488104]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:36:04 5erver acme.sh[1487346]: [Mon Oct 16 09:36:04 AM CEST 2023] Getting webroot for domain='speedtest.joelmueller.ch'
Oct 16 09:36:04 5erver acme.sh[1488138]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:36:04 5erver acme.sh[1488144]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:36:04 5erver acme.sh[1488150]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:36:04 5erver acme.sh[1488156]: egrep: warning: egrep is obsolescent; using grep -E
Oct 16 09:36:04 5erver acme.sh[1488199]: [Mon Oct 16 09:36:04 AM CEST 2023] Adding txt value: YjhVAJhNbhIruXjA4Z9TCNGVOM-DMEXQDXpSSFRqiyM for domain:  _acme-challenge.joelmueller.ch
Oct 16 09:36:04 5erver systemd[1]: lunch-crashed-services.service: Scheduled restart job, restart counter is at 4451.
Oct 16 09:36:05 5erver systemd[1]: Started Execute services if crashed.
Oct 16 09:36:05 5erver systemd[1]: lunch-crashed-services.service: Deactivated successfully.
Oct 16 09:36:05 5erver OoklaServer[1538]: 2023-10-16 07:36:05 [1538 - 563] [Information] TCP uptime: 45855 - total current: 2, queued: 0, blocked: 0, queueFull: 0, concurrent: 84, currentThreads: 4
Oct 16 09:36:05 5erver OoklaServer[1538]: 2023-10-16 07:36:05 [1538 - 545] [Information] TCP uptime: 45855 - total current: 2, queued: 0, blocked: 0, queueFull: 0, concurrent: 84, currentThreads: 4

Offline

#18 2023-10-16 12:12:49

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,422

Re: Problem with Intel NIC

Oct 16 09:35:46 5erver kernel: ixgbe 0000:07:00.0 enp7s0f0: NIC Link is Down
Oct 16 09:35:46 5erver jellyfin[1278]: [09:35:46] [DBG] [34] Jellyfin.Networking.Manager.NetworkManager: Network availability changed.
Oct 16 09:35:46 5erver jellyfin[1278]: [09:35:46] [DBG] [34] Jellyfin.Networking.Manager.NetworkManager: Network Address Change Event.
Oct 16 09:35:48 5erver jellyfin[1278]: [09:35:48] [DBG] [72] Jellyfin.Networking.Manager.NetworkManager: Refreshing interfaces.
Oct 16 09:35:48 5erver jellyfin[1278]: [09:35:48] [ERR] [72] Jellyfin.Networking.Manager.NetworkManager: No interfaces information available. Resolving DNS name.
Oct 16 09:35:48 5erver jellyfin[1278]: [09:35:48] [DBG] [72] Jellyfin.Networking.Manager.NetworkManager: Discovered 6 interfaces.
Oct 16 09:35:48 5erver jellyfin[1278]: [09:35:48] [DBG] [72] Jellyfin.Networking.Manager.NetworkManager: Interfaces addresses : [127.0.0.1/32,::1/32,192.168.1.100/32,2a02:168:a774::2000/32,fe80::9042:6e4b:98c3:cdcb%6/32,127.0.0.1/8]
Oct 16 09:35:48 5erver jellyfin[1278]: [09:35:48] [DBG] [72] Jellyfin.Networking.Manager.NetworkManager: Refreshing LAN information.
Oct 16 09:35:48 5erver jellyfin[1278]: [09:35:48] [DBG] [72] Jellyfin.Networking.Manager.NetworkManager: Using LAN interface addresses as user provided no LAN details.
Oct 16 09:35:48 5erver jellyfin[1278]: [09:35:48] [INF] [72] Jellyfin.Networking.Manager.NetworkManager: Defined LAN addresses : [fc00::/7,fe80::/10,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]
Oct 16 09:35:48 5erver jellyfin[1278]: [09:35:48] [INF] [72] Jellyfin.Networking.Manager.NetworkManager: Defined LAN exclusions : []
Oct 16 09:35:48 5erver jellyfin[1278]: [09:35:48] [INF] [72] Jellyfin.Networking.Manager.NetworkManager: Using LAN addresses: [fc00::/7,fe80::/10,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]
Oct 16 09:35:49 5erver OoklaServer[1538]: 2023-10-16 07:35:49 [1538 - 37] [Warning] Traceroute error: 113 => No route to host
Oct 16 09:35:49 5erver OoklaServer[1538]: 2023-10-16 07:35:49 [1538 - 37] [Information] CA bundle is empty; skipping
Oct 16 09:35:49 5erver OoklaServer[1538]: 2023-10-16 07:35:49 [1538 - 37] [Error] Failed to upload traceroute. Exception caught: DNS error: Temporary DNS error while resolving: results.speedtest.net
Oct 16 09:35:52 5erver kernel: ixgbe 0000:07:00.0 enp7s0f0: NIC Link is Up 10 Gbps, Flow Control: RX/TX

And from the prev. journal

Oct 15 13:10:37 5erver kernel: ixgbe 0000:07:00.0 enp7s0f0: NIC Link is Up 10 Gbps, Flow Control: None
Oct 15 13:10:41 5erver kernel: ixgbe 0000:07:00.0 enp7s0f0: NIC Link is Up 10 Gbps, Flow Control: None
Oct 15 13:10:48 5erver kernel: ixgbe 0000:07:00.0 enp7s0f0: NIC Link is Down
Oct 15 13:10:53 5erver kernel: ixgbe 0000:07:00.0 enp7s0f0: NIC Link is Up 10 Gbps, Flow Control: None
Oct 15 13:12:17 5erver kernel: ixgbe 0000:07:00.0 enp7s0f0: NIC Link is Down
Oct 15 13:12:22 5erver kernel: ixgbe 0000:07:00.0 enp7s0f0: NIC Link is Up 10 Gbps, Flow Control: None
Oct 15 13:12:44 5erver kernel: ixgbe 0000:07:00.0 enp7s0f0: NIC Link is Up 10 Gbps, Flow Control: None
Oct 15 13:12:59 5erver kernel: ixgbe 0000:07:00.0 enp7s0f0: NIC Link is Down
Oct 15 13:13:05 5erver kernel: ixgbe 0000:07:00.0 enp7s0f0: NIC Link is Up 10 Gbps, Flow Control: None
Oct 15 13:13:21 5erver kernel: ixgbe 0000:07:00.0 enp7s0f0: NIC Link is Down
Oct 15 13:13:26 5erver kernel: ixgbe 0000:07:00.0 enp7s0f0: NIC Link is Up 10 Gbps, Flow Control: None
Oct 15 13:13:42 5erver kernel: ixgbe 0000:07:00.0 enp7s0f0: NIC Link is Down
Oct 15 13:13:47 5erver kernel: ixgbe 0000:07:00.0 enp7s0f0: NIC Link is Up 10 Gbps, Flow Control: None
Oct 15 13:14:03 5erver kernel: ixgbe 0000:07:00.0 enp7s0f0: NIC Link is Down

Smells like powersaving (or maybe the cable, but it's too consitent in the 5s delay between down and up) and it's not b/c of the bonding (this happens when only one NIC is charged and the other one takes a nap)
Try "pcie_aspm=off", the ixgbe module doesn't seem to have power settings, but "ixgbe.debug=16" might tell why it's flickering.

What doesn't fit is that the  ping should serve as a life-line, there's no time to power down.
There're however two NICs on the same bus id (07:00.{0,1}) and one is now permanently silent hmm

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#19 2023-10-16 16:02:32

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: Problem with Intel NIC

Ok both interface are up from the NIC but still this behaviorism!

Last edited by Morta (2023-10-16 16:23:14)

Offline

#20 2023-10-16 16:14:14

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: Problem with Intel NIC

 journalctl -b -0 >> journalctl0.txt
 curl -F'file=@journalctl0.txt' http://0x0.st

http://0x0.st/HJzT.txt

Last edited by Morta (2023-10-16 16:14:28)

Offline

#21 2023-10-16 16:17:09

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: Problem with Intel NIC

[morta@5erver tmp]$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp8s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 04:d9:f5:bc:8f:c6 brd ff:ff:ff:ff:ff:ff
3: enp9s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 04:d9:f5:bc:8f:c7 brd ff:ff:ff:ff:ff:ff
4: enp10s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 04:d9:f5:bc:8f:c8 brd ff:ff:ff:ff:ff:ff
5: enp11s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 04:d9:f5:bc:8f:c9 brd ff:ff:ff:ff:ff:ff
6: enp7s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 98:b7:85:89:7e:f8 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.100/24 brd 192.168.1.255 scope global dynamic noprefixroute enp7s0f0
       valid_lft 6556sec preferred_lft 6556sec
    inet6 fe80::9042:6e4b:98c3:cdcb/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
7: enp7s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 98:b7:85:89:7e:f9 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.150/24 brd 192.168.1.255 scope global dynamic noprefixroute enp7s0f1
       valid_lft 6239sec preferred_lft 6239sec
    inet6 fe80::25d9:8c32:78c2:3149/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
8: br-abac02be342e: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:d4:39:04:59 brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 brd 172.18.255.255 scope global br-abac02be342e
       valid_lft forever preferred_lft forever
    inet6 fd00:dead:beef::1/48 scope global tentative
       valid_lft forever preferred_lft forever
    inet6 fe80::1/64 scope link tentative
       valid_lft forever preferred_lft forever

Offline

#22 2023-10-16 16:45:42

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,422

Re: Problem with Intel NIC

I don't see any problem w/ your AST VGA device, but, while that should… be unrelated to the ASPM situation, enable https://wiki.archlinux.org/title/NVIDIA … de_setting and in doubt add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#23 2023-10-16 17:18:22

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: Problem with Intel NIC

seth wrote:

I don't see any problem w/ your AST VGA device, but, while that should… be unrelated to the ASPM situation, enable https://wiki.archlinux.org/title/NVIDIA … de_setting and in doubt add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters

I have no NVIDIA card.


initcall_blacklist=simpledrm_platform_driver_init

It don't boot anymore with initcall (LTS Kernel works)

Last edited by Morta (2023-10-16 17:30:59)

Offline

#24 2023-10-16 18:49:13

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,422

Re: Problem with Intel NIC

I have no NVIDIA card.

I know, but that's irrelevant - the parameter only serves as a hack to disable the simpledrm device, please try.

LTS Kernel works

Entirely? Ie. you disable ASPM, the ethernet remains stable and you get output?
Cause the LTS kernel doesn't have the simpledrm device…

You could also try to boot nomodeset.
Since the only indication for the boot failure (as there's no output) would be the sshd failure(?) you could also test to block the simplydumb device w/o pcie_aspm

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#25 2023-10-16 18:52:08

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: Problem with Intel NIC

seth wrote:

I have no NVIDIA card.

I know, but that's irrelevant - the parameter only serves as a hack to disable the simpledrm device, please try.

LTS Kernel works

Entirely? Ie. you disable ASPM, the ethernet remains stable and you get output?
Cause the LTS kernel doesn't have the simpledrm device…

You could also try to boot nomodeset.
Since the only indication for the boot failure (as there's no output) would be the sshd failure(?) you could also test to block the simplydumb device w/o pcie_aspm

No it's boot but same behavior... I don't understand why the NIC goes down all decade of seconds....

Offline

Pages: 1 2

Board footer

Powered by FluxBB