Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
network dropouts
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
curmudgeon
Veteran
Veteran


Joined: 08 Aug 2003
Posts: 1589

PostPosted: Sat Jan 11, 2020 8:43 pm    Post subject: network dropouts Reply with quote

Aside from my many other problems I have encountered on this install, the following certainly hasn't kept things moving. I get this pinging the router at the other end of the cable.

Code:

# ping 192.168.0.254
PING 192.168.0.254 (172.28.228.62) 56(84) bytes of data.
64 bytes from 192.168.0.254: icmp_seq=1 ttl=64 time=1.06 ms
ping: sendmsg: Network is unreachable
64 bytes from 192.168.0.254: icmp_seq=3 ttl=64 time=0.984 ms
64 bytes from 192.168.0.254: icmp_seq=4 ttl=64 time=0.514 ms
64 bytes from 192.168.0.254: icmp_seq=5 ttl=64 time=0.505 ms
64 bytes from 192.168.0.254: icmp_seq=6 ttl=64 time=0.878 ms
64 bytes from 192.168.0.254: icmp_seq=7 ttl=64 time=0.457 ms
64 bytes from 192.168.0.254: icmp_seq=8 ttl=64 time=0.430 ms
ping: sendmsg: Network is unreachable
64 bytes from 192.168.0.254: icmp_seq=10 ttl=64 time=1.09 ms
64 bytes from 192.168.0.254: icmp_seq=11 ttl=64 time=0.495 ms
ping: sendmsg: Network is unreachable
64 bytes from 192.168.0.254: icmp_seq=13 ttl=64 time=0.922 ms
64 bytes from 192.168.0.254: icmp_seq=14 ttl=64 time=0.605 ms
ping: sendmsg: Network is unreachable
64 bytes from 192.168.0.254: icmp_seq=16 ttl=64 time=0.853 ms
64 bytes from 192.168.0.254: icmp_seq=17 ttl=64 time=0.507 ms
64 bytes from 192.168.0.254: icmp_seq=18 ttl=64 time=0.666 ms
ping: sendmsg: Network is unreachable
64 bytes from 192.168.0.254: icmp_seq=20 ttl=64 time=0.849 ms
64 bytes from 192.168.0.254: icmp_seq=21 ttl=64 time=0.439 ms
ping: sendmsg: Network is unreachable
64 bytes from 192.168.0.254: icmp_seq=23 ttl=64 time=0.945 ms
64 bytes from 192.168.0.254: icmp_seq=24 ttl=64 time=0.530 ms
ping: sendmsg: Network is unreachable
64 bytes from 192.168.0.254: icmp_seq=26 ttl=64 time=0.865 ms
64 bytes from 192.168.0.254: icmp_seq=27 ttl=64 time=0.437 ms
64 bytes from 192.168.0.254: icmp_seq=28 ttl=64 time=0.469 ms
64 bytes from 192.168.0.254: icmp_seq=29 ttl=64 time=0.870 ms
64 bytes from 192.168.0.254: icmp_seq=30 ttl=64 time=0.501 ms
^C
--- 192.168.0.254 ping statistics ---
30 packets transmitted, 23 received, 23.3333% packet loss, time 34ms
rtt min/avg/max/mdev = 0.430/0.690/1.088/0.224 ms


I have no idea what could cause this, of course (and have never seen anything like it before).
Back to top
View user's profile Send private message
Ionen
l33t
l33t


Joined: 06 Dec 2018
Posts: 698

PostPosted: Sat Jan 11, 2020 8:54 pm    Post subject: Reply with quote

Is this only with the router and gentoo together? Ping doesn't always mean much because some devices/firewalls limit ping rate to prevent abuse, router may have such setup and it's what you're observing here (Edit: if doesn't happen on another system, it may just be because it's pinging slower)
Back to top
View user's profile Send private message
curmudgeon
Veteran
Veteran


Joined: 08 Aug 2003
Posts: 1589

PostPosted: Sat Jan 11, 2020 10:31 pm    Post subject: Reply with quote

It only occurs on this machine (not with any other gentoo machines on the same network). I have tried the obvious (a different cable, connecting to a different port). The machine can only downoad about 10 Kbps (on a gigabit connection), and I definitely notice periods of delayed responsiveness when typing commands (over ssh from another machine on the same network).

It looks like a fairly standard device:

Code:

00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
        Subsystem: Dell 82579LM Gigabit Network Connection
        Flags: bus master, fast devsel, latency 0, IRQ 26
        Memory at f7c00000 (32-bit, non-prefetchable) [size=128K]
        Memory at f7c39000 (32-bit, non-prefetchable) [size=4K]
        I/O ports at f080 [size=32]
        Capabilities: [c8] Power Management version 2
        Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [e0] PCI Advanced Features
        Kernel driver in use: e1000e
        Kernel modules: e1000e
Back to top
View user's profile Send private message
Ionen
l33t
l33t


Joined: 06 Dec 2018
Posts: 698

PostPosted: Sat Jan 11, 2020 10:50 pm    Post subject: Reply with quote

Yeah, that definitely sound wrong then. While e1000e driver is pretty common I've never used it, so don't think I can help much.

What does dmesg says about the initialization?
Back to top
View user's profile Send private message
curmudgeon
Veteran
Veteran


Joined: 08 Aug 2003
Posts: 1589

PostPosted: Sat Jan 11, 2020 11:31 pm    Post subject: Reply with quote

Ionen wrote:
What does dmesg says about the initialization?


I do see something about throttling (which I don't understand) - and about an ACPI conflict (which I also don't understand):

Code:

[   12.311731] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[   12.311733] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[   12.311877] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[   12.506710] e1000e 0000:00:19.0 eth0: registered PHC clock
[   12.506713] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) b8:ca:3a:b8:1f:72
[   12.506715] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[   12.506769] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: 1011FF-0FF
[   12.506900] ACPI Warning: SystemIO range 0x000000000000F040-0x000000000000F05F conflicts with OpRegion 0x000000000000F040-0x000000000000F04F (\_SB.PCI0.SBUS.SMBI) (20160108/utaddress-255)
[   12.506905] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   12.521541] [drm] Initialized drm 1.1.0 20060810
[   12.699970] e1000e 0000:00:19.0 eno1: renamed from eth0
Back to top
View user's profile Send private message
Ionen
l33t
l33t


Joined: 06 Dec 2018
Posts: 698

PostPosted: Sun Jan 12, 2020 12:29 am    Post subject: Reply with quote

The throttling message is normal as far as I can tell. ACPI warnings/errors aren't uncommon and usually harmless, this one sounds smbus related which I don't "think" has anything to do with this.

I don't see anything wrong myself, hopefully someone else can help, I looked around a bit but most similar issues I've seen are years old and related to old drivers that aren't in use here.
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7686
Location: Saint Amant, Acadiana

PostPosted: Sun Jan 12, 2020 1:18 am    Post subject: Reply with quote

Troubleshooting checklist.

Try some live binary OS, get some BSD and put in in a USB stick for instance. Can it handle your NIC? You may get some useful clues. In case it also acts up you may have a hardware issue.
Run ethtool, it may not be directly useful, but it tells you what is going on in physical layer.
Run 'tail -f /path/to/kernel/log' and give your NIC something to do. What do you see in the log?
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
curmudgeon
Veteran
Veteran


Joined: 08 Aug 2003
Posts: 1589

PostPosted: Sun Jan 12, 2020 3:23 am    Post subject: Reply with quote

Jaglover wrote:
Run 'tail -f /path/to/kernel/log' and give your NIC something to do. What do you see in the log?


Oops.

I obviously should have looked at the log as the FIRST troubleshooting step (and I feel pretty stupid about that). I forgot to shut off NetworkManager (usually one of the first things I do), and it seems that that abomination of a program kept bringing the interface up and down every three seconds or so.

This block of messages just kept repeating over and over again.

Code:

Jan 12 02:48:25 livecd NetworkManager[5267]: <info>  Activation (eno1) Beginning DHCPv6 transaction (timeout in 45 seconds)
Jan 12 02:48:25 livecd NetworkManager[5267]: <warn>  the dhcpcd backend does not support IPv6.
Jan 12 02:48:25 livecd NetworkManager[5267]: <info>  (eno1): device state change: activated -> failed (reason 'dhcp-start-failed') [100 120 15]
Jan 12 02:48:25 livecd NetworkManager[5267]: <info>  NetworkManager state is now CONNECTED_LOCAL
Jan 12 02:48:25 livecd NetworkManager[5267]: <info>  NetworkManager state is now DISCONNECTED
Jan 12 02:48:25 livecd NetworkManager[5267]: <warn>  (eno1): Activation: failed for connection 'Wired connection 1'
Jan 12 02:48:25 livecd NetworkManager[5267]: <info>  (eno1): device state change: failed -> disconnected (reason 'none') [120 30 0]
Jan 12 02:48:25 livecd dhcpcd[22892]: received SIGTERM, stopping
Jan 12 02:48:25 livecd dhcpcd[22892]: eno1: removing interface
Jan 12 02:48:25 livecd nm-dispatcher[14963]: Dispatching action 'down' for eno1
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>  (eno1): canceled DHCP transaction, DHCP client pid 22892
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>  (eno1): DHCPv4 state changed bound -> done
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>  Auto-activating connection 'Wired connection 1'.
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>  (eno1): Activation: starting connection 'Wired connection 1' (eb94399e-5f4d-4e5
e-9866-fa61a474f4dd)
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>  (eno1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>  NetworkManager state is now CONNECTING
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>  (eno1): device state change: prepare -> config (reason 'none') [40 50 0]
Jan 12 02:48:26 livecd NetworkManager[5267]: <warn>  (pid 22892) unhandled DHCP event for interface eno1
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>  (eno1): device state change: config -> ip-config (reason 'none') [50 70 0]
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>  Activation (eno1) Beginning DHCPv4 transaction (timeout in 45 seconds)
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>  dhcpcd started with pid 23165
Jan 12 02:48:26 livecd dhcpcd[23165]: control_open: Connection refused
Jan 12 02:48:26 livecd dhcpcd[23165]: DUID 00:00:00:00:00:00:00:00:00:00:00:00:00:00
Jan 12 02:48:26 livecd dhcpcd[23165]: eno1: IAID 00:00:00:00
Jan 12 02:48:26 livecd dhcpcd[23165]: eno1: rebinding lease of 192.168.0.2
Jan 12 02:48:26 livecd dhcpcd[23165]: eno1: leased 192.168.0.2 for 3600 seconds
Jan 12 02:48:26 livecd dhcpcd[23165]: eno1: adding route to 192.168.0.0/24
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>    address 192.168.0.2
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>    plen 24 (255.255.255.0)
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>    gateway 192.168.0.254
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>    server identifier 192.168.0.254
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>    lease time 3600
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>    nameserver '192.168.0.254'
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>    nameserver '1.1.1.1'
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>    domain name 'Home'
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>  (eno1): DHCPv4 state changed unknown -> bound
Jan 12 02:48:26 livecd dhcpcd[23165]: eno1: removing route to 192.168.0.0/24
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>  (eno1): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>  (eno1): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>  (eno1): device state change: secondaries -> activated (reason 'none') [90 100 0
]
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>  NetworkManager state is now CONNECTED_LOCAL
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>  NetworkManager state is now CONNECTED_GLOBAL
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>  Policy set 'Wired connection 1' (eno1) as default for IPv4 routing and DNS.
Jan 12 02:48:26 livecd NetworkManager[5267]: <info>  (eno1): Activation: successful, device activated.
Jan 12 02:48:26 livecd nm-dispatcher[14963]: Dispatching action 'up' for eno1
Jan 12 02:48:26 livecd /etc/init.d/NetworkManager[23301]: status: inactive
Jan 12 02:48:26 livecd /etc/init.d/NetworkManager[23332]: status: inactive


A quick '/etc/init.d/NetworkManager stop' and it works the way it should. I never use NetworkManager, but I can't believe that this represents the intended behavior (even on the older live DVD that I have).

Thanks so much for telling me what I should have done in the first place. :)

I will mark this solved (maybe in a day or so), but in the meantime await further enlightenment on NetworkManager or its configuration and functionality in this instance (I would like to understand WHY it did this).
Back to top
View user's profile Send private message
nvaert1986
n00b
n00b


Joined: 05 May 2019
Posts: 56

PostPosted: Thu Jan 16, 2020 2:04 pm    Post subject: Reply with quote

What kernel are you running? If you're running a 5.4.x kernel, then there's a bug that causes the e1000e driver to crash regularly (with me even when initializing. There's a patch for it you can apply at: https://bugzilla.kernel.org/show_bug.cgi?id=205047 or you can choose to use an older kernel.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum