WIFI disconnects and reconnects / TP-LINK WN725 v2

p7rk · May 6, 2017, 3:30pm

Hello guys

I am new to Linux and openSUSE (I do have some experience with unix basic commands though),

I was having issues with configuring my WIFI USB dongle TP-LINK WN725 v2 but somehow I got it running. But now I don’t know why it disconnects and reconnects.

Here are the results of few commands, please could you help me:


linux-rt8t:~ #ifconfig
eth0      Linkencap:Ethernet  HWaddr D8:CB:8A:38:9C:13  
          UPBROADCAST MULTICAST  MTU:1500  Metric:1
          RXpackets:0 errors:0 dropped:0 overruns:0 frame:0
          TXpackets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000 
          RX bytes:0(0.0 b)  TX bytes:0 (0.0 b)


lo        Linkencap:Local Loopback  
          inetaddr:127.0.0.1  Mask:255.0.0.0
          UPLOOPBACK RUNNING  MTU:65536  Metric:1
          RXpackets:0 errors:0 dropped:0 overruns:0 frame:0
          TXpackets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1 
          RX bytes:0(0.0 b)  TX bytes:0 (0.0 b)


wlan1     Linkencap:Ethernet  HWaddr C4:E9:84:17:E6:A8  
          inetaddr:192.168.0.103  Bcast:192.168.0.255  Mask:255.255.255.0
          UPBROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RXpackets:106 errors:0 dropped:18 overruns:0 frame:0
          TXpackets:70 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000 
          RXbytes:30262 (29.5 Kb)  TX bytes:11525 (11.2 Kb)


linux-rt8t:~ #iwconfig
lo        nowireless extensions.


wlan1     IEEE802.11bgn  ESSID:"section9"  Nickname:"<WIFI@REALTEK>"
         Mode:Managed  Frequency:2.472 GHz  Access Point: A0:F3:C1:88:80:EE   
          BitRate:150 Mb/s   Sensitivity:0/0  
          Retry:off  RTS thr:off   Fragment thr:off
          Encryptionkey:****-****-****-****-****-****-****-****   Security mode:open
          PowerManagement:off
          LinkQuality=0/100  Signal level=2/100  Noise level=0/100
          Rx invalidnwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Txexcessive retries:0  Invalid misc:0   Missed beacon:0
                                                                                                                
eth0      nowireless extensions.                                                                                
                                                                                                                
                                           
linux-rt8t:~ # ping-c 5 google.com
PING google.com(172.217.20.206) 56(84) bytes of data.                                                           
64 bytes fromwaw02s08-in-f14.1e100.net (172.217.20.206): icmp_seq=1 ttl=57time=8.51 ms                          
64 bytes fromwaw02s08-in-f14.1e100.net (172.217.20.206): icmp_seq=2 ttl=57time=9.50 ms                          
64 bytes fromwaw02s08-in-f14.1e100.net (172.217.20.206): icmp_seq=3 ttl=57time=14.4 ms                          
64 bytes fromwaw02s08-in-f14.1e100.net (172.217.20.206): icmp_seq=4 ttl=57time=8.13 ms                          
64 bytes fromwaw02s08-in-f14.1e100.net (172.217.20.206): icmp_seq=5 ttl=57time=11.3 ms                          
                                                                                                                
--- google.com pingstatistics ---                                                                               
5 packetstransmitted, 5 received, 0% packet loss, time 4005ms                                                   
rtt min/avg/max/mdev= 8.139/10.379/14.429/2.304 ms                                                              

linux-rt8t:~ # ping-c 5 google.com                                                                              
ping: unknown hostgoogle.com                                                                                    

linux-rt8t:~ # lsusb                                                                                            
Bus 004 Device 002:ID 8087:8001 Intel Corp.                                                                     
Bus 004 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub                                                   
Bus 003 Device 002:ID 8087:8009 Intel Corp.                                                                     
Bus 003 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001:ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004:ID 0bda:8179 Realtek Semiconductor Corp. 
Bus 001 Device 003:ID 0738:1708 Mad Catz, Inc. 
Bus 001 Device 005:ID 045e:02ea Microsoft Corp. 
Bus 001 Device 002:ID 195d:2034 Itron Technology iONE 
Bus 001 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub

linux-rt8t:~ #/usr/sbin/iwconfig wlan1 | grep Mb
          BitRate:150 Mb/s   Sensitivity:0/0  

linux-rt8t:~ #iwconfig scan
scan      No suchdevice

linux-rt8t:~ # lsusb
Bus 004 Device 002:ID 8087:8001 Intel Corp. 
Bus 004 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002:ID 8087:8009 Intel Corp. 
Bus 003 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001:ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004:ID 0bda:8179 Realtek Semiconductor Corp. 
Bus 001 Device 003:ID 0738:1708 Mad Catz, Inc. 
Bus 001 Device 002:ID 195d:2034 Itron Technology iONE 
Bus 001 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub

output from journalctl


May06 15:19:14 linux-rt8t kernel: R8188EU: ERRORlinked_status_chk(wlan1) disconnect or roaming 
May06 15:19:16 linux-rt8t kernel: R8188EU: ERROR assoc success 
May06 15:19:21 linux-rt8t kernel: SFW2-INext-DROP-DEFLTIN=wlan1 OUT= MAC= SRC=fe80:0000:0000:0000:c6e9:84ff:fe17
:e6a8DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=88 TC=0 HOPLIMIT=1FLOWLBL=868069 PROTO=UDP SPT=5353 DPT=535
3 LEN=48 
May06 15:19:21 linux-rt8t kernel: SFW2-INext-DROP-DEFLTIN=wlan1 OUT= MAC= SRC=fe80:0000:0000:0000:c6e9:84ff:fe17
:e6a8DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=88 TC=0 HOPLIMIT=1FLOWLBL=868069 PROTO=UDP SPT=5353 DPT=535
3 LEN=48 
May06 15:19:52 linux-rt8t kernel: R8188EU: ERRORlinked_status_chk(wlan1) disconnect or roaming 
May 06 15:19:54linux-rt8t kernel: R8188EU: ERROR assoc success 
May 06 15:19:59linux-rt8t kernel: SFW2-INext-DROP-DEFLTIN=wlan1 OUT= MAC= SRC=fe80:0000:0000:0000:c6e9:84ff:fe17
:e6a8DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=88 TC=0 HOPLIMIT=1FLOWLBL=868069 PROTO=UDP SPT=5353 DPT=535
3 LEN=48 
May06 15:20:02 linux-rt8t kernel: SFW2-INext-DROP-DEFLTIN=wlan1 OUT= MAC= SRC=fe80:0000:0000:0000:c6e9:84ff:fe17
:e6a8DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=88 TC=0 HOPLIMIT=1FLOWLBL=868069 PROTO=UDP SPT=5353 DPT=535
3 LEN=48

I search some forums here but I wasn’t able to find that solution so sorry if this is a post which has already been solved…

Cheers!

deano_ferrari · May 7, 2017, 12:09am

Welcome to openSUSE Forums p7rk. From the output supplied I see that this device is using the r8188eu driver. My first suggestion might be to try disabling power management in case that is impacting here. (There are a few Ubuntu and R.Pi threads around discussing similar behaviour.) This can be done by adding a custom file to the /etc/modprobe.d/ directory eg /etc/modprobe.d/8188eu.conf

options 8188eu rtw_power_mgnt=0 rtw_enusbss=0

Then unload and reload the driver for it to take effect.

If that doesn’t help, then maybe either compiling a newer version of the driver from here or upgrading to a newer kernel might do the trick, as this driver has undergone a lot of development over the past year or so, (as you’ll see if you check out the github link).

Fraser_Bell · May 7, 2017, 1:14am

After running updates last night on one of my other laptops, I am also seeing this, or very similar.

I even saw this flooding the screen when I booted to runlevel 3, so much so that I could not even use Vi, because the output was obliterating the onscreen type of the file I was trying to edit.

This was, however, getting close to 3 a.m., way past bedtime, so I left that alone. I plan to go to that machine and check it out later today, get the exact output and other relevant information.

So, later, I will update this with confirmation whether I am seeing similar or related issue.

Note that, among the updates, there was a kernel update, though it could have been one of the other updates involved.

p7rk · May 7, 2017, 12:02pm

Hello

I did


linux-rt8t:/etc/modprobe.d# cat > 8188eu.conf
options 8188eurtw_power_mgnt=0 rtw_enusbss=0

Among the modules Ifound these:


p7rk-lx@linux-rt8t:/etc/modprobe.d>lsmod
Module                 Size  Used by
r8188eu              487424  0 
cfg80211             614400  1 r8188eu
rfkill                28672  5 cfg80211

So I ran


p7rk-lx@linux-rt8t:/etc/modprobe.d>sudo modprobe -r r8188eu
p7rk-lx@linux-rt8t:/etc/modprobe.d>sudo modprobe r8188eu

in journal I havethis output:


May 07 11:38:22linux-rt8t kernel: usbcore: deregistering interface driver r8188eu
May 07 11:38:22linux-rt8t kernel: R8188EU: ERROR indicate disassoc
May 07 11:38:22linux-rt8t wickedd-dhcp4[1118]: ni_dhcp4_device_close: timer activefor wlan1
May 07 11:38:22linux-rt8t avahi-daemon[1024]: Interface wlan1.IPv6 no longerrelevant for mDNS.
May 07 11:38:22linux-rt8t avahi-daemon[1024]: Leaving mDNS multicast group oninterface wlan1.IPv6 with address fe80::c6e9:84ff:fe17:e6a8.
May 07 11:38:22linux-rt8t systemd-udevd[534]: Network interface NamePolicy= disabledby default.
May 07 11:38:22linux-rt8t wickedd[1124]: wlan1: Ignoring attempt to reset existinginterface link type from wireless to ethernet
May 07 11:38:22linux-rt8t wickedd-nanny[1127]: device wlan1: device has been deleted
May 07 11:38:22linux-rt8t avahi-daemon[1024]: Interface wlan1.IPv4 no longerrelevant for mDNS.
May 07 11:38:22linux-rt8t avahi-daemon[1024]: Leaving mDNS multicast group oninterface wlan1.IPv4 with address 192.168.0.103.
May 07 11:38:22linux-rt8t avahi-daemon[1024]: Withdrawing address record forfe80::c6e9:84ff:fe17:e6a8 on wlan1.
May 07 11:38:22linux-rt8t avahi-daemon[1024]: Withdrawing address record for192.168.0.103 on wlan1.
May 07 11:38:22linux-rt8t avahi-daemon[1024]: Joining mDNS multicast group oninterface wlan1.IPv6 with address fe80::c6e9:84ff:fe17:e6a8.
May 07 11:38:22linux-rt8t avahi-daemon[1024]: IPV6_ADD_MEMBERSHIP failed: No suchdevice
May 07 11:38:22linux-rt8t avahi-daemon[1024]: Joining mDNS multicast group oninterface wlan1.IPv4 with address 192.168.0.103.
May 07 11:38:22linux-rt8t avahi-daemon[1024]: IP_ADD_MEMBERSHIP failed: No suchdevice
May 07 11:38:22linux-rt8t avahi-daemon[1024]: Registering new address record forfe80::c6e9:84ff:fe17:e6a8 on wlan1.*.
May 07 11:38:22linux-rt8t avahi-daemon[1024]: Registering new address record for192.168.0.103 on wlan1.IPv4.
May 07 11:38:22linux-rt8t avahi-daemon[1024]: Withdrawing address record forfe80::c6e9:84ff:fe17:e6a8 on wlan1.
May 07 11:38:22linux-rt8t avahi-daemon[1024]: Withdrawing address record for192.168.0.103 on wlan1.
May 07 11:38:22linux-rt8t kernel: usb 3-3: reset high-speed USB device number 4using xhci_hcd
May 07 11:38:22linux-rt8t sudo[3716]: pam_unix(sudo:session): session closed foruser root
May 07 11:38:30linux-rt8t sudo[3752]:  p7rk-lx : TTY=pts/2 ; PWD=/etc/modprobe.d ;USER=root ; COMMAND=/usr/sbin/modprobe r8188eu
May 07 11:38:30linux-rt8t sudo[3752]: pam_unix(sudo:session): session opened foruser root by p7rk-lx(uid=0)
May 07 11:38:30linux-rt8t sudo[3752]: pam_systemd(sudo:session): Cannot createsession: Already running in a session
May 07 11:38:30linux-rt8t kernel: r8188eu: module is from the staging directory, thequality is unknown, you have been warned.
May 07 11:38:30linux-rt8t kernel: Chip Version Info:CHIP_8188E_Normal_Chip_TSMC_D_CUT_1T1R_RomVer(0)
May 07 11:38:30linux-rt8t kernel: cfg80211: World regulatory domain updated:
May 07 11:38:30linux-rt8t kernel: cfg80211:  DFS Master region: unset
May 07 11:38:30linux-rt8t kernel: cfg80211:   (start_freq - end_freq @ bandwidth),(max_antenna_gain, max_eirp), (dfs_cac_time)
May 07 11:38:30linux-rt8t kernel: cfg80211:   (2402000 KHz - 2472000 KHz @ 40000KHz), (N/A, 2000 mBm), (N/A)
May 07 11:38:30linux-rt8t kernel: cfg80211:   (2457000 KHz - 2482000 KHz @ 20000KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A)
May 07 11:38:30linux-rt8t kernel: cfg80211:   (2474000 KHz - 2494000 KHz @ 20000KHz), (N/A, 2000 mBm), (N/A)
May 07 11:38:30linux-rt8t kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 80000KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
May 07 11:38:30linux-rt8t kernel: cfg80211:   (5250000 KHz - 5330000 KHz @ 80000KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
May 07 11:38:30linux-rt8t kernel: cfg80211:   (5490000 KHz - 5730000 KHz @ 160000KHz), (N/A, 2000 mBm), (0 s)
May 07 11:38:30linux-rt8t kernel: cfg80211:   (5735000 KHz - 5835000 KHz @ 80000KHz), (N/A, 2000 mBm), (N/A)
May 07 11:38:30linux-rt8t kernel: cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000KHz), (N/A, 0 mBm), (N/A)
May 07 11:38:30linux-rt8t kernel: usbcore: registered new interface driver r8188eu
May 07 11:38:30linux-rt8t sudo[3752]: pam_unix(sudo:session): session closed foruser root
May 07 11:38:30linux-rt8t kernel: r8188eu 3-3:1.0 wlan1: renamed from wlan0
May 07 11:38:30linux-rt8t wpa_supplicant[1443]: ioctl[SIOCSIWAP]: Operation notpermitted
May 07 11:38:30linux-rt8t kernel: MAC Address = c4:e9:84:17:e6:a8
May 07 11:38:30linux-rt8t kernel: IPv6: ADDRCONF(NETDEV_UP): wlan1: link is notready
May 07 11:38:32linux-rt8t kernel: R8188EU: ERROR assoc success
May 07 11:38:32linux-rt8t kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomesready
May 07 11:38:34linux-rt8t avahi-daemon[1024]: Joining mDNS multicast group oninterface wlan1.IPv6 with address fe80::c6e9:84ff:fe17:e6a8.
May 07 11:38:34linux-rt8t avahi-daemon[1024]: New relevant interface wlan1.IPv6 formDNS.
May 07 11:38:34linux-rt8t avahi-daemon[1024]: Registering new address record forfe80::c6e9:84ff:fe17:e6a8 on wlan1.*.
May 07 11:38:34linux-rt8t kernel: SFW2-INext-DROP-DEFLT IN=wlan1 OUT= MAC=SRC=fe80:0000:0000:0000:c6e9:84ff:fe17:e6a8DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=322 TC=0 HOPLIMIT=255FLOWLBL=312306 PROTO=UDP SPT=5353 DPT=5353 LEN=282 
May 07 11:38:34linux-rt8t kernel: SFW2-INext-DROP-DEFLT IN=wlan1 OUT= MAC=SRC=fe80:0000:0000:0000:c6e9:84ff:fe17:e6a8DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=186 TC=0 HOPLIMIT=255FLOWLBL=312306 PROTO=UDP SPT=5353 DPT=5353 LEN=146 
May 07 11:38:41linux-rt8t kernel: SFW2-INext-DROP-DEFLT IN=wlan1 OUT= MAC=SRC=fe80:0000:0000:0000:c6e9:84ff:fe17:e6a8DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=88 TC=0 HOPLIMIT=1FLOWLBL=312306 PROTO=UDP SPT=5353 DPT=5353 LEN=48


linux-rt8t:/etc/modprobe.d# iwconfig
lo        nowireless extensions.


wlan1     IEEE802.11bgn  ESSID:"section9"  Nickname:"<WIFI@REALTEK>"
         Mode:Managed  Frequency:2.472 GHz  Access Point: A0:F3:C1:88:80:EE   
          BitRate:150 Mb/s   Sensitivity:0/0  
          Retry:off  RTS thr:off   Fragment thr:off
          Encryptionkey:****-****-****-****-****-****-****-****   Security mode:open
          PowerManagement:off
          LinkQuality:0  Signal level:0  Noise level:0
          Rx invalidnwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Txexcessive retries:0  Invalid misc:0   Missed beacon:0


eth0      nowireless extensions.


linux-rt8t:/etc/modprobe.d# ifconfig
eth0      Linkencap:Ethernet  HWaddr D8:CB:8A:38:9C:13  
          UPBROADCAST MULTICAST  MTU:1500  Metric:1
          RXpackets:0 errors:0 dropped:0 overruns:0 frame:0
          TXpackets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000 
          RX bytes:0(0.0 b)  TX bytes:0 (0.0 b)


lo        Linkencap:Local Loopback  
          inetaddr:127.0.0.1  Mask:255.0.0.0
          inet6addr: ::1/128 Scope:Host
          UPLOOPBACK RUNNING  MTU:65536  Metric:1
          RXpackets:187 errors:0 dropped:0 overruns:0 frame:0
          TXpackets:187 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1 
          RXbytes:25097 (24.5 Kb)  TX bytes:25097 (24.5 Kb)


wlan1     Linkencap:Ethernet  HWaddr C4:E9:84:17:E6:A8  
          inet6addr: fe80::c6e9:84ff:fe17:e6a8/64 Scope:Link
          UPBROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RXpackets:372 errors:0 dropped:21 overruns:0 frame:0
          TXpackets:24 errors:0 dropped:3 overruns:0 carrier:0
         collisions:0 txqueuelen:1000 
          RXbytes:126450 (123.4 Kb)  TX bytes:4860 (4.7 Kb)

After this the internet totally died on me

After rebooting the PC I got the same behaviour.

The weird thing is that the wifi device is showing green light all the time, but the browser looses track of what is going on.
The websites launch almost immediately after I boot the PC, but then they die.
Like minute later net comes back alive to die again after a minute.

In the output above it says Power Managment off, so maybe that is not the case of the device being switched off.

I didnt install the updates to the system yet.

I am a little afraid that I will mess the whole system when I start playing with Kernel… especially after what @Fraser_Bell posted here…

Thanks for helping me resolve this.

Sauerland · May 7, 2017, 12:20pm

options 8188eurtw_power_mgnt=0 rtw_enusbss=0

Maybe 1 typo, should it be:

options 8188eu rtw_power_mgnt=0 rtw_enusbss=0

a space between driver and rtw…

p7rk · May 7, 2017, 1:24pm

:shame: whoops! I will check this immediately

p7rk · May 7, 2017, 1:38pm

There was no space - the output was pasted incorrectly I guess.
But one weird thing happened - I just rebooted the pc and now another wlan has appeared as unconfigured (screenshot attached)https://preview.ibb.co/g8nqkk/Screenshot_20170507_133226.png](Screenshot 20170507 133226 hosted at ImgBB — ImgBB)

deano_ferrari · May 7, 2017, 10:26pm

Your journal and lsmod output mentions that you’re using the ‘r8188eu’ dirver (part of the kernel). If that is the case the the config file in /etc/modprobe.d/ needs to refer to the actual module name…

options r8188eu rtw_power_mgnt=0 rtw_enusbss=0

p7rk · May 9, 2017, 7:54pm

I have put the info in the file like you have mentioned Deano_ferrari.

I will test this for a day or two and let you guys know how it went.

But for now I think it is better.

p7rk · May 11, 2017, 9:19pm

Hi I’m back.

I finally had some time to test some more with my opensuse, and still I get these disconnects after some intervals

From journalctl -f:

May 11 21:10:50 linux-rt8t kernel: R8188EU: ERROR linked_status_chk(wlan1) disconnect or roaming
May 11 21:10:54 linux-rt8t kernel: R8188EU: ERROR assoc success
May 11 21:11:18 linux-rt8t kernel: R8188EU: ERROR linked_status_chk(wlan1) disconnect or roaming
May 11 21:11:22 linux-rt8t kernel: R8188EU: ERROR assoc success
May 11 21:11:44 linux-rt8t kernel: R8188EU: ERROR linked_status_chk(wlan1) disconnect or roaming
May 11 21:11:46 linux-rt8t kernel: R8188EU: ERROR assoc success
May 11 21:12:10 linux-rt8t kernel: R8188EU: ERROR linked_status_chk(wlan1) disconnect or roaming
May 11 21:12:12 linux-rt8t kernel: R8188EU: ERROR assoc success
May 11 21:12:38 linux-rt8t kernel: R8188EU: ERROR linked_status_chk(wlan1) disconnect or roaming
May 11 21:12:40 linux-rt8t kernel: R8188EU: ERROR assoc success
May 11 21:13:06 linux-rt8t kernel: R8188EU: ERROR linked_status_chk(wlan1) disconnect or roaming
May 11 21:13:08 linux-rt8t kernel: R8188EU: ERROR assoc success
May 11 21:13:34 linux-rt8t kernel: R8188EU: ERROR linked_status_chk(wlan1) disconnect or roaming
May 11 21:13:36 linux-rt8t kernel: R8188EU: ERROR assoc success

It is really hard to write even this post as I take very long time to login to the forum…,

I read on this forum that I could switch off the IPv6 to help the driver to work - I did that from General settings.

Just now output has changed:


May 11 21:15:01 linux-rt8t cron[2687]: pam_unix(crond:session): session opened for user root by (uid=0)            
May 11 21:15:01 linux-rt8t systemd[1]: Created slice User Slice of root.                                           
May 11 21:15:01 linux-rt8t systemd[1]: Starting User Manager for UID 0...                                          
May 11 21:15:01 linux-rt8t systemd[2688]: pam_unix(systemd-user:session): session opened for user root by (uid=0)  
May 11 21:15:01 linux-rt8t systemd[1]: Started Session 2 of user root.                                             
May 11 21:15:01 linux-rt8t systemd[2688]: Reached target Sockets.                                                  
May 11 21:15:01 linux-rt8t systemd[2688]: Reached target Timers.                                                   
May 11 21:15:01 linux-rt8t systemd[2688]: Reached target Paths.                                                    
May 11 21:15:01 linux-rt8t systemd[2688]: Reached target Basic System.                                             
May 11 21:15:01 linux-rt8t systemd[2688]: Reached target Default.                                                  
May 11 21:15:01 linux-rt8t systemd[2688]: Startup finished in 14ms.                                                
May 11 21:15:01 linux-rt8t systemd[1]: Started User Manager for UID 0.                                             
May 11 21:15:09 linux-rt8t dbus[1045]: **[system] Activating service name='org.opensuse.Snapper' (using servicehelpe**
r)                                                                                                                 
May 11 21:15:09 linux-rt8t dbus[1045]: **[system] Successfully activated service 'org.opensuse.Snapper'**              
May 11 21:15:26 linux-rt8t kernel: R8188EU: ERROR linked_status_chk(wlan1) disconnect or roaming                   
May 11 21:15:35 linux-rt8t kernel: R8188EU: ERROR assoc success                                                    
May 11 21:15:35 linux-rt8t kernel: BTRFS info (device sda6): qgroup scan completed (inconsistency flag cleared)    
May 11 21:15:37 linux-rt8t CRON[2687]: pam_unix(crond:session): session closed for user root                       
May 11 21:15:37 linux-rt8t systemd[1]: Stopping User Manager for UID 0...                                          
May 11 21:15:37 linux-rt8t systemd[2688]: Reached target Shutdown.                                                 
May 11 21:15:37 linux-rt8t systemd[2688]: Stopped target Default.                                                  
May 11 21:15:37 linux-rt8t systemd[2688]: Stopped target Basic System.                                             
May 11 21:15:37 linux-rt8t systemd[2688]: Stopped target Sockets.
May 11 21:15:37 linux-rt8t systemd[2688]: Stopped target Paths.
May 11 21:15:37 linux-rt8t systemd[2688]: Stopped target Timers.
May 11 21:15:37 linux-rt8t systemd[2688]: Starting Exit the Session...
May 11 21:15:37 linux-rt8t systemd[2688]: Received SIGRTMIN+24 from PID 9895 (kill).
May 11 21:15:37 linux-rt8t systemd[2691]: pam_unix(systemd-user:session): session closed for user root
May 11 21:15:37 linux-rt8t systemd[1]: Stopped User Manager for UID 0.
May 11 21:15:37 linux-rt8t systemd[1]: Removed slice User Slice of root.

Who is that “Slice” user? I have only 3 instances of terminal launched (ping, journal and sudo -i for iwconfig)

Here are some pings to google:


64 bytes from cache.google.com (185.48.9.25): icmp_seq=340 ttl=60 time=4.51 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=341 ttl=60 time=3.80 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=342 ttl=60 time=4.09 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=343 ttl=60 time=3.78 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=344 ttl=60 time=4.29 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=345 ttl=60 time=4.36 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=346 ttl=60 time=3.87 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=347 ttl=60 time=4.02 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=348 ttl=60 time=4.11 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=349 ttl=60 time=4.10 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=364 ttl=60 time=6.60 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=365 ttl=60 time=4.58 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=366 ttl=60 time=5.01 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=367 ttl=60 time=3.72 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=368 ttl=60 time=3.98 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=369 ttl=60 time=4.47 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=370 ttl=60 time=4.44 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=371 ttl=60 time=2.99 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=372 ttl=60 time=3.56 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=373 ttl=60 time=3.71 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=374 ttl=60 time=3.59 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=375 ttl=60 time=4.37 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=376 ttl=60 time=3.40 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=377 ttl=60 time=4.68 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=392 ttl=60 time=6.43 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=393 ttl=60 time=4.45 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=394 ttl=60 time=5.07 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=395 ttl=60 time=4.86 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=396 ttl=60 time=4.09 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=397 ttl=60 time=4.64 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=398 ttl=60 time=6.76 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=399 ttl=60 time=5.23 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=400 ttl=60 time=4.97 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=401 ttl=60 time=3.24 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=402 ttl=60 time=3.83 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=403 ttl=60 time=4.24 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=404 ttl=60 time=3.97 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=405 ttl=60 time=4.61 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=406 ttl=60 time=3.36 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=407 ttl=60 time=5.65 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=416 ttl=60 time=4774 ms
64 bytes from cache.google.com (185.48.9.25): icmp_seq=417 ttl=60 time=3774 ms

deano_ferrari · May 12, 2017, 2:58am

A bug report might be your best option here, although I’d be tempted to try using a newer kernel as there may be applicable bug fixes already. Your ping results don’t really add value since they actually confirm connectivity at the time you executed the ping.

Fraser_Bell · May 13, 2017, 12:12am

Okay, I just saw this thread pop up again in my list, so as my promised test, I logged out and cold booted to a root console: The environment where I had a very similar problem as I posted earlier in this thread.

I no longer share the problem, or so it appears, so it apparently has disappeared since the time I experienced it.

Note that I only experienced it that one day.

Therefore, I cannot confirm nor add to the bug. Good luck.

But, of course, do as deano advised.

p7rk · May 14, 2017, 1:31pm

I did the updates which came up recently, unfortunately I have the same issue.

What do you mean by updating the kernel? Is there another version somewhere which is not available in the main package?

Thanks

deano_ferrari · May 14, 2017, 9:41pm

Yes. Try upgrading to the current stable kernel…

zypper ar -f http://download.opensuse.org/repositories/Kernel:/stable/standard/Kernel:stable.repo
zypper ref
zypper up kernel-default

then reboot.