Mint 18 - connection lost

[ennoborg]

This happened in the beta, and I see it in the release version too. I have a Medion desktop PC, connected via ethernet, and occasionally I seem to lose the ethernet connection after an update or something. A restart helps in that case, but I have never seen this phenomenon in 17.3.

My PC has wifi too, but I don't use that.

Any ideas? It's definitely new, and I haven't checked whether ubuntu 16.04 has the same problem, or not. I test that in VirtualBox.

[ennoborg]

Follow-up: I have this with LMDE Betsy too.

[Georgia boy]

When I first tried LMDE after they went stable I had same issue basically. Only it saw my wifi for about two minutes. Was able to get on but not later. Got peed and tossed on an old version of Wheezy then later Mint. So just this weekend I installed LMDE2 Betsy Mate just for hell of it to see what would happen. During this time I was hooked up with cable. Did the upgrades. Was worried what would happen. Disconnected my cable after all the upgrades were done. It saw my wifi along with several others to choose from. I got it running and haven't had any issues since then. So, I'm wondering and probably a stupid question to toss at you but were you hooked to the cable first and got all the upgrades after install?

[eatenimpinia]

This is my 3rd day after a clean install from Linux Mint 17.3 Cinnamon to 18. Today, I'm seeing the same thing as the OP with my wired Ethernet connection. I rebooted 4 times this morning and Mint only saw the Ethernet connection on two of them. Any suggestions on where to start troubleshooting this?

Code: Select all

inxi -Fxz
System:    Host: dave-gryphon Kernel: 4.4.0-31-generic x86_64 (64 bit gcc: 5.3.1)
           Desktop: Cinnamon 3.0.7 (Gtk 3.18.9-1ubuntu3.1) Distro: Linux Mint 18 Sarah
Machine:   System: ASUS product: All Series
           Mobo: ASUSTeK model: GRYPHON Z97 v: Rev 1.xx Bios: American Megatrends v: 1304 date: 07/11/2014
CPU:       Quad core Intel Core i5-4590S (-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 23986
           clock speeds: max: 3700 MHz 1: 3009 MHz 2: 3004 MHz 3: 3000 MHz 4: 3000 MHz
Graphics:  Card: NVIDIA GM204 [GeForce GTX 970] bus-ID: 01:00.0
           Display Server: X.Org 1.18.3 drivers: nvidia (unloaded: fbdev,vesa,nouveau)
           Resolution: 1920x1200@59.95hz
           GLX Renderer: GeForce GTX 970/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 361.42 Direct Rendering: Yes
Audio:     Card-1 NVIDIA GM204 High Definition Audio Controller driver: snd_hda_intel bus-ID: 01:00.1
           Card-2 Intel 9 Series Family HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
           Card-3 Texas Instruments Audio Codec driver: USB Audio usb-ID: 003-002
           Card-4 C-Media CM108 Audio Controller driver: USB Audio usb-ID: 003-004
           Sound: Advanced Linux Sound Architecture v: k4.4.0-31-generic
Network:   Card: Intel Ethernet Connection (2) I218-V driver: e1000e v: 3.2.6-k port: f040 bus-ID: 00:19.0
           IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 496.1GB (13.2% used) ID-1: /dev/sda model: Samsung_SSD_850 size: 256.1GB
           ID-2: /dev/sdb model: SanDisk_SDSSDXP2 size: 240.1GB
Partition: ID-1: / size: 152G used: 11G (8%) fs: ext4 dev: /dev/sda5
           ID-2: swap-1 size: 8.53GB used: 0.00GB (0%) fs: swap dev: /dev/sda6
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 0.0:54C
           Fan Speeds (in rpm): cpu: 0
Info:      Processes: 194 Uptime: 9 min Memory: 1312.9/7926.9MB Init: systemd Gcc sys: 5.4.0
           Client: Shell (bash 4.3.421) inxi: 2.2.35 

[rhY]

Can confirm. I'm running Mint 18 mate from an upgrade of 17.3 (64 bit).

Everything works fine, I come back some hours later, and suddenly I have no internet. Wifi still shows connected in the tray by the clock, but I can't ping out, surf, no upstream connectivity at all.

I have to reboot. Every. Day.

Pretty annoying. Devuan does not have this issue, so I'm guessing it's more upstream systemd bull%&@.

Let me know if there's a solution, or a more stable version of mint without systemd. My other Mint 18 machine occasionally crashes too, which has never happened before.

I noticed the same instability and broken stuff in Debian 8 when they took the d. So I'm not at all surprised. Just: Disappointed.

[JeremyB]

Post results for

Code: Select all

lspci -nnk | grep -iA2 net; iwconfig

[pvdeynse]

this is still happening for me
i'm using Intel WiFi Link 5100

inxi -Fxz
System: Host: pvdeynse-Aspire-7738 Kernel: 4.4.0-21-generic x86_64 (64 bit gcc: 5.3.1)
Desktop: Xfce 4.12.3 (Gtk 2.24.28) Distro: Linux Mint 18 Sarah
Machine: System: Acer (portable) product: Aspire 7738 v: 0100
Mobo: Acer model: JM70 v: Rev Bios: Phoenix v: V1.11 date: 08/18/2009
CPU: Dual core Intel Core2 Duo T6600 (-MCP-) cache: 2048 KB
flags: (lm nx sse sse2 sse3 sse4_1 ssse3) bmips: 8778
clock speeds: max: 2200 MHz 1: 1600 MHz 2: 2200 MHz
Graphics: Card: NVIDIA GT216M [GeForce GT 240M] bus-ID: 01:00.0
Display Server: X.Org 1.18.3 drivers: nvidia (unloaded: fbdev,vesa,nouveau)
Resolution: 1600x900@60.08hz
GLX Renderer: GeForce GT 240M/PCIe/SSE2 GLX Version: 3.3.0 NVIDIA 340.96 Direct Rendering: Yes
Audio: Card-1 NVIDIA GT216 HDMI Audio Controller driver: snd_hda_intel bus-ID: 01:00.1
Card-2 Intel 82801I (ICH9 Family) HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
Sound: Advanced Linux Sound Architecture v: k4.4.0-21-generic
Network: Card-1: Broadcom NetLink BCM5784M Gigabit Ethernet PCIe driver: tg3 v: 3.137 bus-ID: 02:00.0
IF: eth0 state: down mac: <filter>
Card-2: Intel WiFi Link 5100 driver: iwlwifi bus-ID: 03:00.0
IF: wlan0 state: up mac: <filter>
Drives: HDD Total Size: 1000.2GB (2.8% used) ID-1: /dev/sda model: Hitachi_HTS54505 size: 500.1GB temp: 40C
ID-2: /dev/sdb model: Hitachi_HTS54505 size: 500.1GB temp: 33C
Partition: ID-1: / size: 193G used: 23G (13%) fs: ext4 dev: /dev/sdb5
ID-2: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sdb6
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 50.0C mobo: 49.0C gpu: 0.0:48C
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 210 Uptime: 55 min Memory: 1476.6/3947.3MB Init: systemd runlevel: 5 Gcc sys: 5.4.0
Client: Shell (bash 4.3.421) inxi: 2.2.35



here some info from my system

lspci -nnk | grep -iA2 net; iwconfig
02:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM5784M Gigabit Ethernet PCIe [14e4:1698] (rev 10)
Subsystem: Acer Incorporated [ALI] NetLink BCM5784M Gigabit Ethernet PCIe [1025:0207]
Kernel driver in use: tg3
Kernel modules: tg3
03:00.0 Network controller [0280]: Intel Corporation WiFi Link 5100 [8086:4232]
Subsystem: Intel Corporation WiFi Link 5100 AGN [8086:1201]
Kernel driver in use: iwlwifi
eth0 no wireless extensions.

wlan0 IEEE 802.11abgn ESSID:"telenet-7CCA0"
Mode:Managed Frequency:5.24 GHz Access Point: 5C:35:3B:47:CC:A6
Bit Rate=135 Mb/s Tx-Power=15 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
Link Quality=60/70 Signal level=-50 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:1042 Missed beacon:0

lo no wireless extensions.

[felemur]

Just found this thread.

Can confirm the same for me - no issue with 17.3, but with 18 randomly no internet, restart fixes it for days. My system never shuts off.

Not my router or modem as it keeps working with my other computer. Have not found solution other than a restart.

[JeremyB]

Just found this thread.

Can confirm the same for me - no issue with 17.3, but with 18 randomly no internet, restart fixes it for days. My system never shuts off.

Not my router or modem as it keeps working with my other computer. Have not found solution other than a restart.

Is this is a wifi issue post the result for

Code: Select all

lshw -c net; iwconfig

[felemur]

Just found this thread.

Can confirm the same for me - no issue with 17.3, but with 18 randomly no internet, restart fixes it for days. My system never shuts off.

Not my router or modem as it keeps working with my other computer. Have not found solution other than a restart.

Is this is a wifi issue post the result for

Code: Select all

lshw -c net; iwconfig

No, Ethernet to Router for my desktop.

But here it is anyway:

Code: Select all

david@david-OptiPlex-7010 ~ $ lshw -c net; iwconfig
WARNING: you should run this program as super-user.
  *-network               
       description: Ethernet interface
       product: 82579LM Gigabit Network Connection
       vendor: Intel Corporation
       physical id: 19
       bus info: pci@0000:00:19.0
       logical name: eno1
       version: 04
       serial: 90:b1:1c:6f:05:ee
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.13-4 ip=192.168.1.2 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:28 memory:f7c00000-f7c1ffff memory:f7c39000-f7c39fff ioport:f080(size=32)
WARNING: output may be incomplete or inaccurate, you should run this program as super-user.
lo        no wireless extensions.

eno1      no wireless extensions.

david@david-OptiPlex-7010 ~ $ 

[JeremyB]

Since a few of the posters with ethernet issues are using the same driver e1000e, someone might want to try installing the latest from Intel
http://www.intel.com/content/www/us/en/ ... 05480.html

[pvdeynse]

Since a few of the posters with ethernet issues are using the same driver e1000e, someone might want to try installing the latest from Intel
http://www.intel.com/content/www/us/en/ ... 05480.html

I'm using the latest e1000e driver from Intel and the problem still persists, after a while we lose IPv4 connectivity, IPv6 is still active and operational. After a restart of the network services both IPv4 and IPv6 are again operational. I can be wrong but have the impression that after a network services restart IPv4 keeps operational for a longer time, cannot test since i shutdown my laptop every day, also from time to time i'm using Windows10 which is also installed on the same laptop but on another physical hard drive(2 hard drives in this laptop)

I cannot do further tests since i currently have no access to my laptop.

[JeremyB]

Are you using TLP or UFW? TLP is a power management program and UFW is a firewall program

[pvdeynse]

Are you using TLP or UFW? TLP is a power management program and UFW is a firewall program

i'm currently abroad, have no access to my laptop for the next two weeks, will answer once returned, thanks.

[felemur]

Are you using TLP or UFW? TLP is a power management program and UFW is a firewall program

Well I can answer that - Yes I am using UFW. Why? Do you think that may be interfering? Just as a FYI, I was using UFW in 17.3 and never had the issue.

Also, just as a side note, I have not had the problem crop up since I updated to the 4.4.0-45.66 kernel. Thing is, the problem would happen so rarely (many days could go by without a disconnect) that it is impossible to know if the new kernel actually dealt with the issue.

[JeremyB]

Watch the dmesg logs for items concerning UFW

Code: Select all

dmesg | grep -i ufw

I have seen UFW block necessary traffic and cause issues

[felemur]

Watch the dmesg logs for items concerning UFW

Code: Select all

dmesg | grep -i ufw

I have seen UFW block necessary traffic and cause issues

There are hundreds upon hundreds of messages about UFW when I do that command in terminal. Here is just a tiny fraction of the output I get:

Code: Select all

david@david-OptiPlex-7010 ~ $ dmesg | grep -i ufw
[379881.066516] [UFW BLOCK] IN=eno1 OUT= MAC=90:b1:1c:6f:05:ee:e4:f4:c6:0a:26:5e:08:00 SRC=122.169.101.16 DST=192.168.1.2 LEN=129 TOS=0x00 PREC=0x00 TTL=117 ID=9612 PROTO=UDP SPT=53329 DPT=14444 LEN=109 
[379898.123669] [UFW BLOCK] IN=eno1 OUT= MAC= SRC=0000:0000:0000:0000:0000:0000:0000:0001 DST=ff15:0000:0000:0000:0000:0000:efc0:988f LEN=186 TC=0 HOPLIMIT=1 FLOWLBL=1026685 PROTO=UDP SPT=36553 DPT=6771 LEN=146 
[379901.679926] [UFW BLOCK] IN=eno1 OUT= MAC=90:b1:1c:6f:05:ee:e4:f4:c6:0a:26:5e:08:00 SRC=121.22.249.95 DST=192.168.1.2 LEN=58 TOS=0x00 PREC=0x00 TTL=26 ID=0 PROTO=UDP SPT=1075 DPT=14444 LEN=38 
[379904.124187] [UFW BLOCK] IN=eno1 OUT= MAC= SRC=0000:0000:0000:0000:0000:0000:0000:0001 DST=ff15:0000:0000:0000:0000:0000:efc0:988f LEN=186 TC=0 HOPLIMIT=1 FLOWLBL=1026685 PROTO=UDP SPT=36553 DPT=6771 LEN=146 
[379924.928967] [UFW BLOCK] IN=eno1 OUT= MAC=90:b1:1c:6f:05:ee:e4:f4:c6:0a:26:5e:08:00 SRC=108.184.3.71 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=116 ID=1067 DF PROTO=TCP SPT=65166 DPT=14444 WINDOW=8192 RES=0x00 SYN URGP=0 
[379933.124799] [UFW BLOCK] IN=eno1 OUT= MAC= SRC=0000:0000:0000:0000:0000:0000:0000:0001 DST=ff15:0000:0000:0000:0000:0000:efc0:988f LEN=186 TC=0 HOPLIMIT=1 FLOWLBL=1026685 PROTO=UDP SPT=36553 DPT=6771 LEN=146 

No idea what that means.

I have not had a disconnect in many days now BTW.

[pvdeynse]

Are you using TLP or UFW? TLP is a power management program and UFW is a firewall program

i'm currently abroad, have no access to my laptop for the next two weeks, will answer once returned, thanks.

i have UFW installed but not active, i don't have TLP installed.
I've lost IPv4 connectivity only once a couple of days ago, last 2 days all is working fine, have to admit that lot of packages have been updated recently, i'm also running latest kernel now Version: 4.4.0-47.68

will monitor and give feedback

[felemur]

I haven't had it happen since the 4.4.0-45.66 kernel. Not sure if that is coincidence or cause and effect, but either way the issue seems done with.

[pvdeynse]

I've finally solved my IP connection lost problem. I was able to reproduce every time just by booting first in Windows 10 followed by a restart in Mint 18, after a while Mint looses IP connectivity.

Mint 18 maintains the hardware clock (RTC, real time clock) in universal time (UTC) by default while Windows maintains the clock in local time, thus causing time conflicts between Mint and Windows.

To fix it, make Windows uses UTC.
boot into Windows 10, when you’re in, do:

go to Start Menu, search for and launch cmd as Administrator.
When the command console opens, paste below command to create a DWORD value to the registry:
Reg add HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation /v RealTimeIsUniversal /t REG_DWORD /d 1

For 64-bit Windows, use a QWORD value instead:
Reg add HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation /v RealTimeIsUniversal /t REG_QWORD /d 1

I've been using the following Ubuntu Howto document:
http://ubuntuhandbook.org/index.php/201 ... indows-10/

Now the hardware clock is always set to UTC by Mint and Windows 10
Due to above fix Mint 18 does no longer loose IP connectivity