Mailinglist Archive: opensuse-support (80 mails)

< Previous Next >
Re: [opensuse-support] Losing network and stop jobs
  • From: Todd Rme <toddrme2178@xxxxxxxxx>
  • Date: Sat, 13 Oct 2018 16:43:16 -0400
  • Message-id: <CADb7s=tmLn11r5HrHkWF9K49naNYrR=TosmLrFyBo2V+pwGkTg@mail.gmail.com>
Thanks!

Here is the full journal for the ten minutes before the problem
occured (I was logging pings, and they stopped connecting sometimes
between 03:23:27 and 03:26:46):

Oct 13 03:20:35 linux-a5zo kernel: usb 2-2.4: reset SuperSpeed Gen 1
USB device number 3 using xhci_hcd
Oct 13 03:20:36 linux-a5zo NetworkManager[3135]: <info>
[1539415236.6562] device (enp0s20f0u2u4): carrier: link connected
Oct 13 03:20:36 linux-a5zo kernel: r8152 2-2.4:1.0 enp0s20f0u2u4: carrier on
Oct 13 03:21:44 linux-a5zo kernel: wlo1: deauthenticating from
d4:6e:0e:8d:2d:14 by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 13 03:21:44 linux-a5zo kernel: IPv6: ADDRCONF(NETDEV_UP): wlo1:
link is not ready
Oct 13 03:21:44 linux-a5zo NetworkManager[3135]: <info>
[1539415304.7270] device (wlo1): set-hw-addr: set MAC address to
B2:D0:55:62:55:CA (scanning)
Oct 13 03:21:44 linux-a5zo dhclient[2937]: receive_packet failed on
wlo1: Network is down
Oct 13 03:21:44 linux-a5zo NetworkManager[3135]: <info>
[1539415304.7910] device (wlo1): supplicant interface state: completed
-> disconnected
Oct 13 03:21:44 linux-a5zo NetworkManager[3135]: <info>
[1539415304.7968] device (wlo1): supplicant interface state:
disconnected -> scanning
Oct 13 03:21:48 linux-a5zo NetworkManager[3135]: <info>
[1539415308.0348] device (wlo1): supplicant interface state: scanning
-> disconnected
Oct 13 03:21:48 linux-a5zo kernel: wlo1: authenticate with d4:6e:0e:8d:2d:14
Oct 13 03:21:48 linux-a5zo kernel: pcieport 0000:00:1c.0: AER:
Corrected error received: 0000:00:1c.0
Oct 13 03:21:48 linux-a5zo kernel: pcieport 0000:00:1c.0: PCIe Bus
Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Oct 13 03:21:48 linux-a5zo kernel: pcieport 0000:00:1c.0: device
[8086:9d13] error status/mask=00000001/00002000
Oct 13 03:21:48 linux-a5zo kernel: pcieport 0000:00:1c.0: [ 0]
Receiver Error (First)
Oct 13 03:21:48 linux-a5zo kernel: pcieport 0000:00:1c.0: AER:
Corrected error received: 0000:00:1c.0
Oct 13 03:21:48 linux-a5zo kernel: pcieport 0000:00:1c.0: PCIe Bus
Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Oct 13 03:21:48 linux-a5zo kernel: pcieport 0000:00:1c.0: device
[8086:9d13] error status/mask=00000001/00002000
Oct 13 03:21:48 linux-a5zo kernel: pcieport 0000:00:1c.0: [ 0]
Receiver Error (First)
Oct 13 03:21:48 linux-a5zo kernel: wlo1: send auth to
d4:6e:0e:8d:2d:14 (try 1/3)
Oct 13 03:21:48 linux-a5zo kernel: wlo1: authenticated
Oct 13 03:21:48 linux-a5zo NetworkManager[3135]: <info>
[1539415308.9218] device (wlo1): supplicant interface state:
disconnected -> authenticating
Oct 13 03:21:48 linux-a5zo kernel: wlo1: associate with
d4:6e:0e:8d:2d:14 (try 1/3)
Oct 13 03:21:48 linux-a5zo kernel: wlo1: RX AssocResp from
d4:6e:0e:8d:2d:14 (capab=0x411 status=0 aid=1)
Oct 13 03:21:48 linux-a5zo kernel: wlo1: associated
Oct 13 03:21:48 linux-a5zo kernel: IPv6: ADDRCONF(NETDEV_CHANGE):
wlo1: link becomes ready
Oct 13 03:21:48 linux-a5zo NetworkManager[3135]: <info>
[1539415308.9470] device (wlo1): supplicant interface state:
authenticating -> associating
Oct 13 03:21:48 linux-a5zo NetworkManager[3135]: <info>
[1539415308.9480] device (wlo1): supplicant interface state:
associating -> 4-way handshake
Oct 13 03:21:48 linux-a5zo NetworkManager[3135]: <info>
[1539415308.9520] device (wlo1): supplicant interface state: 4-way
handshake -> completed
Oct 13 03:22:31 linux-a5zo kernel: usb 2-2.4: reset SuperSpeed Gen 1
USB device number 3 using xhci_hcd
Oct 13 03:22:32 linux-a5zo NetworkManager[3135]: <info>
[1539415352.6568] device (enp0s20f0u2u4): carrier: link connected
Oct 13 03:22:32 linux-a5zo kernel: r8152 2-2.4:1.0 enp0s20f0u2u4: carrier on
Oct 13 03:22:40 linux-a5zo kernel: usb 2-2.4: reset SuperSpeed Gen 1
USB device number 3 using xhci_hcd
Oct 13 03:22:41 linux-a5zo NetworkManager[3135]: <info>
[1539415361.8728] device (enp0s20f0u2u4): carrier: link connected
Oct 13 03:22:41 linux-a5zo kernel: r8152 2-2.4:1.0 enp0s20f0u2u4: carrier on
Oct 13 03:28:16 linux-a5zo NetworkManager[3135]: <info>
[1539415696.0447] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 13 03:28:16 linux-a5zo systemd[1]: Starting Network Manager Script
Dispatcher Service...
Oct 13 03:28:16 linux-a5zo dbus-daemon[1286]: [system] Activating via
systemd: service name='org.freedesktop.nm_dispatcher'
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.62'
(uid=0 pid=3135 comm="/usr/sbin/NetworkManager --no-daemon ")
Oct 13 03:28:16 linux-a5zo systemd[1]: Started Network Manager Script
Dispatcher Service.
Oct 13 03:28:16 linux-a5zo dbus-daemon[1286]: [system] Successfully
activated service 'org.freedesktop.nm_dispatcher'
Oct 13 03:28:16 linux-a5zo nm-dispatcher[20909]: req:1
'connectivity-change': new request (5 scripts)
Oct 13 03:28:16 linux-a5zo nm-dispatcher[20909]: req:1
'connectivity-change': start running ordered scripts...
Oct 13 03:46:13 linux-a5zo smartd[1273]: Device: /dev/sda [SAT], SMART
Usage Attribute: 190 Airflow_Temperature_Cel changed from 68 to 69
Oct 13 03:46:13 linux-a5zo smartd[1273]: Device: /dev/sda [SAT],
previous self-test completed without error
Oct 13 04:00:38 linux-a5zo systemd[1]: Started Timeline of Snapper Snapshots.
Oct 13 04:00:38 linux-a5zo dbus-daemon[1286]: [system] Activating
service name='org.opensuse.Snapper' requested by ':1.204' (uid=0
pid=21183 comm="/usr/lib/snapper/systemd-helper --timeline ") (using
servicehelper)
Oct 13 04:00:38 linux-a5zo dbus-daemon[1286]: [system] Successfully
activated service 'org.opensuse.Snapper'
Oct 13 04:06:16 linux-a5zo plasmashell[2500]: libkcups:
Renew-Subscription last error: 0 successful-ok
Oct 13 04:46:13 linux-a5zo smartd[1273]: Device: /dev/sda [SAT], SMART
Usage Attribute: 190 Airflow_Temperature_Cel changed from 69 to 70
Oct 13 05:00:38 linux-a5zo systemd[1]: Started Timeline of Snapper Snapshots.
Oct 13 05:00:38 linux-a5zo dbus-daemon[1286]: [system] Activating
service name='org.opensuse.Snapper' requested by ':1.206' (uid=0
pid=21596 comm="/usr/lib/snapper/systemd-helper --timeline ") (using
servicehelper)
Oct 13 05:00:38 linux-a5zo dbus-daemon[1286]: [system] Successfully
activated service 'org.opensuse.Snapper'
Oct 13 05:04:36 linux-a5zo plasmashell[2500]: libkcups:
Renew-Subscription last error: 0 successful-ok
Oct 13 05:46:13 linux-a5zo smartd[1273]: Device: /dev/sda [SAT], SMART
Usage Attribute: 190 Airflow_Temperature_Cel changed from 70 to 67
Oct 13 05:59:29 linux-a5zo chronyd[1361]: Can't synchronise: no
selectable sources
Oct 13 06:00:38 linux-a5zo systemd[1]: Started Timeline of Snapper Snapshots.
Oct 13 06:00:38 linux-a5zo dbus-daemon[1286]: [system] Activating
service name='org.opensuse.Snapper' requested by ':1.208' (uid=0
pid=22003 comm="/usr/lib/snapper/systemd-helper --timeline ") (using
servicehelper)
Oct 13 06:00:38 linux-a5zo dbus-daemon[1286]: [system] Successfully
activated service 'org.opensuse.Snapper'
Oct 13 06:02:56 linux-a5zo plasmashell[2500]: libkcups:
Renew-Subscription last error: 0 successful-ok
Oct 13 06:16:13 linux-a5zo smartd[1273]: Device: /dev/sda [SAT], SMART
Usage Attribute: 190 Airflow_Temperature_Cel changed from 67 to 66
Oct 13 07:00:38 linux-a5zo systemd[1]: Started Timeline of Snapper Snapshots.
Oct 13 07:00:38 linux-a5zo dbus-daemon[1286]: [system] Activating
service name='org.opensuse.Snapper' requested by ':1.210' (uid=0
pid=22412 comm="/usr/lib/snapper/systemd-helper --timeline ") (using
servicehelper)
Oct 13 07:00:38 linux-a5zo dbus-daemon[1286]: [system] Successfully
activated service 'org.opensuse.Snapper'
Oct 13 07:01:16 linux-a5zo plasmashell[2500]: libkcups:
Renew-Subscription last error: 0 successful-ok
Oct 13 07:16:13 linux-a5zo smartd[1273]: Device: /dev/sda [SAT], SMART
Usage Attribute: 190 Airflow_Temperature_Cel changed from 66 to 67
Oct 13 07:59:36 linux-a5zo plasmashell[2500]: libkcups:
Renew-Subscription last error: 0 successful-ok
Oct 13 08:00:38 linux-a5zo systemd[1]: Started Timeline of Snapper Snapshots.
Oct 13 08:00:38 linux-a5zo dbus-daemon[1286]: [system] Activating
service name='org.opensuse.Snapper' requested by ':1.212' (uid=0
pid=22820 comm="/usr/lib/snapper/systemd-helper --timeline ") (using
servicehelper)
Oct 13 08:00:38 linux-a5zo dbus-daemon[1286]: [system] Successfully
activated service 'org.opensuse.Snapper'
Oct 13 08:46:13 linux-a5zo smartd[1273]: Device: /dev/sda [SAT], SMART
Usage Attribute: 190 Airflow_Temperature_Cel changed from 67 to 69
Oct 13 08:57:56 linux-a5zo plasmashell[2500]: libkcups:
Renew-Subscription last error: 0 successful-ok

The logs start getting really sparse after 03:28:16

On Fri, Oct 12, 2018 at 2:31 AM Bruno Friedmann <bruno@xxxxxxxxxxx> wrote:

On jeudi, 11 octobre 2018 17.16:33 h CEST Todd Rme wrote:
I have been having two seemingly related problems with openSUSE
TumbleWeed on my HP Envy x360 laptop, using Plasma with
NetworkManager.

At seemingly random intervals my network connection will suddenly stop
working. It still shows that it is connected, but the data transfer
rate drops to zero. I can't even ping. I can disconnect from the
network, but if I try to reconnect, Plasma freezes. If I try to
reconnect through SystemSettings, SystemSettings freezes. This
happens both with my WiFi and with two different USB ethernet ports.
If I try to switch in YaST to wicked it doesn't help. If I try to
restart NewtorkManager services it doesn't help.

If I try to shut down or restart the computer after this, the shutdown
or restart hangs. If I look at the command line output, I get a bunch
of "waiting for stop jobs" messages. The stop jobs have a timeout,
but when the timeout finishes the time limit just extends for those
jobs and more stop jobs get added. I have waited over an hour with no
shutdown occurring. This does not happen if I shutdown or restart
before the network issue occurs, the shutdown takes less than a
second.

I have no idea how to begin debugging this. I have looked at the logs
but nothing pops out as being an obvious issue. Any suggestions?

Hi Todd, I would of course check any message (warning, error, crash) in dmesg
outpout.
If you want to cross check when a trouble appear in a kind of human outpout
you can use

dmesg --human --color

While we are talking with hardware failure, check if there's any bios update
for your laptop model on hp website.

The next suspect I would also verify is the ntpd process if your computer is
still using it. When the network is not available this one is know to behave
strangely.

I'm using now from a long time (2 years) the excellent systemd-timesyncd
you can adjust the configuration to your need
/etc/systemd/timesyncd.conf


--

Bruno Friedmann
Ioda-Net Sàrl www.ioda-net.ch
Bareos Partner, openSUSE Member, fsfe supporter
GPG KEY : D5C9B751C4653227
irc: tigerfoot




--
To unsubscribe, e-mail: opensuse-support+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-support+owner@xxxxxxxxxxxx

--
To unsubscribe, e-mail: opensuse-support+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-support+owner@xxxxxxxxxxxx

< Previous Next >