You are not logged in.

Pages: 1

#1 2017-02-10 13:00:27

L1ghtmareI
Member
Registered: 2014-08-29
Posts: 96

Wired interface experiences temporary issues sporadically

I'm connected to my router both with wireless adapter and by wire. Recently the ethernet interface started failing with what looked like DNS issues (resolving host... into ERR_ADDRESS_UNREACHABLE), though everything would become unreachable, even the router's web interface page (which is accessed with plain IP). Disconnecting the interface so that wireless kicks in removes the problem. For a few minutes after that the interface fails to get address from router (apparently the unsuccessfull attempts don't even appear in router's log), but when DHCPREQUEST finally goes through, everything goes back to 'normal'.

I use NetworkManager on top of wpa_supplicant.

ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 74:d4:35:ae:3e:9d brd ff:ff:ff:ff:ff:ff
3: wlp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
    link/ether e8:94:f6:a6:33:c6 brd ff:ff:ff:ff:ff:ff
dmesg | grep eth
[    2.441161] r8169 0000:03:00.0 eth0: RTL8168evl/8111evl at 0xffffc9000199d000, 74:d4:35:ae:3e:9d, XID 0c900800 IRQ 36
[    2.441162] r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[    2.503286] r8169 0000:03:00.0 enp3s0: renamed from eth0
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
        Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet
        Flags: bus master, fast devsel, latency 0, IRQ 36
        I/O ports at d000 [size=256]
        Memory at f7900000 (64-bit, non-prefetchable) [size=4K]
        Memory at ea100000 (64-bit, prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: r8169
        Kernel modules: r8169

Thanks in advance.

edit: if anything, i'm looking for measures to log what's going on when that happens next time

Last edited by L1ghtmareI (2017-02-10 13:19:37)

Offline

#2 2017-02-10 13:31:46

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: Wired interface experiences temporary issues sporadically

Do you see any disconnect events (or any wired device related events) in the journal when the wired interface acts up? It could be a hardware issue too.

Offline

#3 2017-02-10 13:32:23

Morn
Member
Registered: 2012-09-02
Posts: 886

Re: Wired interface experiences temporary issues sporadically

I am also getting these periods of stuck DNS lookups and no working ping to the router with my wired (Homeplug) connection. Other devices that use the Homeplug connection via a wireless AP seem to be fine.

After a few minutes, the problem will usually go away, but it is still quite annoying.

$ dmesg | grep eth
[   13.529791] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) c8:9c:dc:d4:90:f7
[   13.529797] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[   13.529830] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF

Offline

#4 2017-02-10 13:52:24

L1ghtmareI
Member
Registered: 2014-08-29
Posts: 96

Re: Wired interface experiences temporary issues sporadically

Just happened right now, ip link output doesn't change, ping/drill packets don't go through.

This is the output of journalctl when that occured, pretty sure all of the lines are related to me disabling the wired interface though.

Feb 10 16:45:59 AlexDesktop NetworkManager[392]: <info>  [1486734359.8138] device (enp3s0): state change: activated -> deactivating (reason 'user-requested') [100 110 39]
Feb 10 16:45:59 AlexDesktop NetworkManager[392]: <info>  [1486734359.8140] manager: NetworkManager state is now CONNECTED_LOCAL
Feb 10 16:45:59 AlexDesktop NetworkManager[392]: <info>  [1486734359.8159] audit: op="device-disconnect" interface="enp3s0" ifindex=2 pid=655 uid=1000 result="success"
Feb 10 16:45:59 AlexDesktop NetworkManager[392]: <info>  [1486734359.8162] device (enp3s0): state change: deactivating -> disconnected (reason 'user-requested') [110 30 39]
Feb 10 16:45:59 AlexDesktop NetworkManager[392]: <info>  [1486734359.8165] dhcp4 (enp3s0): canceled DHCP transaction
Feb 10 16:45:59 AlexDesktop NetworkManager[392]: <info>  [1486734359.8165] dhcp4 (enp3s0): state changed bound -> done
Feb 10 16:45:59 AlexDesktop NetworkManager[392]: <info>  [1486734359.8166] dhcp6 (enp3s0): canceled DHCP transaction
Feb 10 16:45:59 AlexDesktop NetworkManager[392]: <info>  [1486734359.8167] dhcp6 (enp3s0): state changed bound -> done
Feb 10 16:45:59 AlexDesktop NetworkManager[392]: <info>  [1486734359.8175] dns-mgr: Writing DNS information to /usr/bin/resolvconf
Feb 10 16:45:59 AlexDesktop kdeinit5[617]: plasma-nm: Unhandled active connection state change:  3
Feb 10 16:45:59 AlexDesktop NetworkManager[392]: <info>  [1486734359.8607] manager: NetworkManager state is now CONNECTED_GLOBAL
Feb 10 16:45:59 AlexDesktop NetworkManager[392]: <info>  [1486734359.8608] policy: set 'wewlad' (wlp6s0) as default for IPv6 routing and DNS
Feb 10 16:45:59 AlexDesktop NetworkManager[392]: <info>  [1486734359.8608] dns-mgr: Writing DNS information to /usr/bin/resolvconf
Feb 10 16:45:59 AlexDesktop NetworkManager[392]: <info>  [1486734359.8704] policy: set 'wewlad' (wlp6s0) as default for IPv4 routing and DNS
Feb 10 16:45:59 AlexDesktop dbus[390]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Feb 10 16:45:59 AlexDesktop systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb 10 16:45:59 AlexDesktop dbus[390]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 10 16:45:59 AlexDesktop systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 10 16:45:59 AlexDesktop nm-dispatcher[11002]: req:1 'down' [enp3s0]: new request (0 scripts)
Feb 10 16:45:59 AlexDesktop nm-dispatcher[11002]: req:1 'down' [enp3s0]: completed: no scripts
Feb 10 16:45:59 AlexDesktop kdeinit5[617]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "RxBytes"
Feb 10 16:45:59 AlexDesktop kdeinit5[617]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "TxBytes"
Feb 10 16:45:59 AlexDesktop plasmashell[655]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "RxBytes"
Feb 10 16:45:59 AlexDesktop plasmashell[655]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "TxBytes"

unfortunately i missed both uninterrupted failed state and the failure to reconnect

Offline

#5 2017-02-11 05:09:47

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: Wired interface experiences temporary issues sporadically

Hmm.. both of you are using different network cards, so a driver issue is unlikely. @Morn, are you also using NetworkManager? @both, when did this start happening?

Offline

#6 2017-02-11 10:27:24

Morn
Member
Registered: 2012-09-02
Posts: 886

Re: Wired interface experiences temporary issues sporadically

x33a wrote:

Hmm.. both of you are using different network cards, so a driver issue is unlikely. @Morn, are you also using NetworkManager? @both, when did this start happening?

No, NetworkManager is installed (as a dependency) but does not seem to run (I'm currently using KDE again), at least according to the network settings tab in Gnome Control Center.

I think it started a few months ago maybe. Initially I thought it was the DNS server of my ISP or the powerline plugs having intermittent problems, so I did not investigate this as a possible Linux issue or start a forum thread about it.

Offline

#7 2017-02-11 11:59:12

L1ghtmareI
Member
Registered: 2014-08-29
Posts: 96

Re: Wired interface experiences temporary issues sporadically

I'm using networkmanager exclusively since i reinstalled at new years. The issue started appearing less than a week ago even though i dont recall updating at that time. Our issues might be separate.

Last edited by L1ghtmareI (2017-02-11 11:59:51)

Offline

#8 2017-02-11 16:01:46

L1ghtmareI
Member
Registered: 2014-08-29
Posts: 96

Re: Wired interface experiences temporary issues sporadically

so heres what happens at the moment of the issue, have no clue what that could imply

Feb 11 18:55:45  plasmashell[11980]: QXcbConnection: XCB error: 2 (BadValue), sequence: 19816, resource id: 62914561, major code: 142 (Unknown), minor code: 3
Feb 11 18:55:45 plasmashell[11980]: QXcbConnection: XCB error: 2 (BadValue), sequence: 19817, resource id: 62914561, major code: 142 (Unknown), minor code: 3
Feb 11 18:55:45  plasmashell[11980]: QXcbConnection: XCB error: 2 (BadValue), sequence: 19818, resource id: 62914561, major code: 142 (Unknown), minor code: 3
Feb 11 18:55:45 plasmashell[11980]: QXcbConnection: XCB error: 2 (BadValue), sequence: 19819, resource id: 85983318, major code: 142 (Unknown), minor code: 3
Feb 11 18:55:45  plasmashell[11980]: QXcbConnection: XCB error: 2 (BadValue), sequence: 20025, resource id: 85983318, major code: 142 (Unknown), minor code: 3
Feb 11 18:55:45  plasmashell[11980]: QXcbConnection: XCB error: 2 (BadValue), sequence: 20026, resource id: 85983318, major code: 142 (Unknown), minor code: 3
Feb 11 18:55:45  plasmashell[11980]: QXcbConnection: XCB error: 2 (BadValue), sequence: 20027, resource id: 85983671, major code: 142 (Unknown), minor code: 3
Feb 11 18:55:58  org_kde_powerdevil[668]: powerdevil: Scheduling inhibition from ":1.984" "/usr/lib/chromium/chromium" with cookie 176 and reason "Uploading data to ***"
Feb 11 18:55:59  plasmashell[11980]: QObject::startTimer: Timers cannot be started from another thread
Feb 11 18:56:01  dolphin[17679]: Cannot creat accessible child interface for object:  PlacesView(0x1494a50)  index:  17
Feb 11 18:56:02  kdeinit5[17686]: kf5.kio.trash: listdir:  QUrl("trash:/")
Feb 11 18:56:02  dolphin[17679]: kf5.kio.core: KSambaShare: Could not find smb.conf!
Feb 11 18:56:03  kwin_x11[650]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55436, resource id: 115343360, major code: 18 (ChangeProperty), minor code: 0
Feb 11 18:56:03  kwin_x11[650]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55440, resource id: 115343361, major code: 18 (ChangeProperty), minor code: 0
Feb 11 18:56:03  org_kde_powerdevil[668]: powerdevil: Enforcing inhibition from ":1.984" "/usr/lib/chromium/chromium" with cookie 176 and reason "Uploading data to ***"
Feb 11 18:56:03 org_kde_powerdevil[668]: powerdevil: Added change screen settings
Feb 11 18:56:03  org_kde_powerdevil[668]: powerdevil: Added interrupt session
Feb 11 18:56:03  org_kde_powerdevil[668]: powerdevil: Disabling DPMS due to inhibition
Feb 11 18:56:03  org_kde_powerdevil[668]: powerdevil: Can't contact ck

Offline

#9 2017-02-13 10:20:02

L1ghtmareI
Member
Registered: 2014-08-29
Posts: 96

Re: Wired interface experiences temporary issues sporadically

failed reconnect, doesn't really say anything specific besides DHCP timeout

Feb 13 13:10:18  NetworkManager[366]: <info>  [1486980618.3245] device (enp3s0): Activation: starting connection 'Wired connection 1' (61cf701a-7029-3b2c-8356-11613a0723c5)
Feb 13 13:10:18  NetworkManager[366]: <info>  [1486980618.3246] audit: op="connection-activate" uuid="61cf701a-7029-3b2c-8356-11613a0723c5" name="Wired connection 1" pid=621 uid=1000 result="success"
Feb 13 13:10:18  NetworkManager[366]: <info>  [1486980618.3247] device (enp3s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb 13 13:10:18  NetworkManager[366]: <info>  [1486980618.3250] device (enp3s0): state change: prepare -> config (reason 'none') [40 50 0]
Feb 13 13:10:18  NetworkManager[366]: <info>  [1486980618.3255] device (enp3s0): state change: config -> ip-config (reason 'none') [50 70 0]
Feb 13 13:10:18  NetworkManager[366]: <info>  [1486980618.3257] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
Feb 13 13:10:18  kdeinit5[578]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "RxBytes"
Feb 13 13:10:18  kdeinit5[578]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "TxBytes"
Feb 13 13:10:18  kdeinit5[578]: plasma-nm: Unhandled active connection state change:  1
Feb 13 13:10:18  plasmashell[621]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "RxBytes"
Feb 13 13:10:18  plasmashell[621]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "TxBytes"
Feb 13 13:10:21  plasmashell[621]: QXcbConnection: XCB error: 2 (BadValue), sequence: 3350, resource id: 79691862, major code: 142 (Unknown), minor code: 3
Feb 13 13:10:21  plasmashell[621]: QXcbConnection: XCB error: 2 (BadValue), sequence: 3352, resource id: 79692148, major code: 142 (Unknown), minor code: 3
Feb 13 13:10:22  plasmashell[621]: QXcbConnection: XCB error: 2 (BadValue), sequence: 3444, resource id: 50331653, major code: 142 (Unknown), minor code: 3
Feb 13 13:10:25  kwin_x11[607]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 50564, resource id: 77594624, major code: 18 (ChangeProperty), minor code: 0
Feb 13 13:10:25  kwin_x11[607]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 50568, resource id: 77594625, major code: 18 (ChangeProperty), minor code: 0
Feb 13 13:10:27  kdeconnectd[618]: kdeconnect.core: Broadcasting identity packet
Feb 13 13:11:03  NetworkManager[366]: <warn>  [1486980663.7906] dhcp4 (enp3s0): request timed out
Feb 13 13:11:03  NetworkManager[366]: <info>  [1486980663.7907] dhcp4 (enp3s0): state changed unknown -> timeout
Feb 13 13:11:03  NetworkManager[366]: <info>  [1486980663.8108] dhcp4 (enp3s0): canceled DHCP transaction
Feb 13 13:11:03  NetworkManager[366]: <info>  [1486980663.8108] dhcp4 (enp3s0): state changed timeout -> done
Feb 13 13:11:03  NetworkManager[366]: <info>  [1486980663.8111] device (enp3s0): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Feb 13 13:11:03  NetworkManager[366]: <warn>  [1486980663.8130] device (enp3s0): Activation: failed for connection 'Wired connection 1'
Feb 13 13:11:03  NetworkManager[366]: <info>  [1486980663.8136] device (enp3s0): state change: failed -> disconnected (reason 'none') [120 30 0]
Feb 13 13:11:03  NetworkManager[366]: <info>  [1486980663.8153] policy: auto-activating connection 'Wired connection 1'
Feb 13 13:11:03  NetworkManager[366]: <info>  [1486980663.8162] device (enp3s0): Activation: starting connection 'Wired connection 1' (61cf701a-7029-3b2c-8356-11613a0723c5)
Feb 13 13:11:03  NetworkManager[366]: <info>  [1486980663.8163] device (enp3s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb 13 13:11:03  NetworkManager[366]: <info>  [1486980663.8165] device (enp3s0): state change: prepare -> config (reason 'none') [40 50 0]
Feb 13 13:11:03  NetworkManager[366]: <info>  [1486980663.8168] device (enp3s0): state change: config -> ip-config (reason 'none') [50 70 0]
Feb 13 13:11:03  NetworkManager[366]: <info>  [1486980663.8170] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
Feb 13 13:11:03  kdeinit5[578]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "TxBytes"
Feb 13 13:11:03  kdeinit5[578]: plasma-nm: Unhandled active connection state change:  1
Feb 13 13:11:03  plasmashell[621]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "TxBytes"
Feb 13 13:11:13  org_kde_powerdevil[642]: powerdevil: Releasing inhibition with cookie  199
Feb 13 13:11:13  org_kde_powerdevil[642]: powerdevil: Restoring DPMS features after inhibition release
Feb 13 13:11:13  org_kde_powerdevil[642]: powerdevil: Can't contact ck
Feb 13 13:11:17  org_kde_powerdevil[642]: powerdevil: Scheduling inhibition from ":1.10" "/usr/lib/chromium/chromium" with cookie 200 and reason "Playing video"
Feb 13 13:11:17  org_kde_powerdevil[642]: powerdevil: Scheduling inhibition from ":1.465" "/usr/lib/chromium/chromium" with cookie 201 and reason "Playing video"
Feb 13 13:11:17  org_kde_powerdevil[642]: powerdevil: Scheduling inhibition from ":1.466" "/usr/lib/chromium/chromium" with cookie 202 and reason "Playing audio"
Feb 13 13:11:22  org_kde_powerdevil[642]: powerdevil: Enforcing inhibition from ":1.10" "/usr/lib/chromium/chromium" with cookie 200 and reason "Playing video"
Feb 13 13:11:22  org_kde_powerdevil[642]: powerdevil: Added change screen settings
Feb 13 13:11:22  org_kde_powerdevil[642]: powerdevil: Added interrupt session
Feb 13 13:11:22  org_kde_powerdevil[642]: powerdevil: Disabling DPMS due to inhibition
Feb 13 13:11:22  org_kde_powerdevil[642]: powerdevil: Enforcing inhibition from ":1.465" "/usr/lib/chromium/chromium" with cookie 201 and reason "Playing video"
Feb 13 13:11:22  org_kde_powerdevil[642]: powerdevil: Added change screen settings
Feb 13 13:11:22  org_kde_powerdevil[642]: powerdevil: Added interrupt session
Feb 13 13:11:22  org_kde_powerdevil[642]: powerdevil: Enforcing inhibition from ":1.466" "/usr/lib/chromium/chromium" with cookie 202 and reason "Playing audio"
Feb 13 13:11:22  org_kde_powerdevil[642]: powerdevil: Added change screen settings
Feb 13 13:11:22  org_kde_powerdevil[642]: powerdevil: Added interrupt session
Feb 13 13:11:22  org_kde_powerdevil[642]: powerdevil: Can't contact ck
Feb 13 13:11:22  org_kde_powerdevil[642]: powerdevil: Can't contact ck
Feb 13 13:11:22  org_kde_powerdevil[642]: powerdevil: Can't contact ck
Feb 13 13:11:31  org_kde_powerdevil[642]: powerdevil: Releasing inhibition with cookie  202
Feb 13 13:11:31  org_kde_powerdevil[642]: powerdevil: Can't contact ck
Feb 13 13:11:37  plasmashell[621]: QXcbConnection: XCB error: 2 (BadValue), sequence: 5605, resource id: 69206017, major code: 142 (Unknown), minor code: 3
Feb 13 13:11:38  plasmashell[621]: QXcbConnection: XCB error: 2 (BadValue), sequence: 5715, resource id: 50331653, major code: 142 (Unknown), minor code: 3
Feb 13 13:11:38  plasmashell[621]: QXcbConnection: XCB error: 2 (BadValue), sequence: 5754, resource id: 79691862, major code: 142 (Unknown), minor code: 3
Feb 13 13:11:38  plasmashell[621]: QXcbConnection: XCB error: 2 (BadValue), sequence: 5772, resource id: 50331653, major code: 142 (Unknown), minor code: 3
Feb 13 13:11:38  plasmashell[621]: QXcbConnection: XCB error: 2 (BadValue), sequence: 5819, resource id: 77594630, major code: 142 (Unknown), minor code: 3
Feb 13 13:11:38  plasmashell[621]: QXcbConnection: XCB error: 2 (BadValue), sequence: 5923, resource id: 69206017, major code: 142 (Unknown), minor code: 3
Feb 13 13:11:39  plasmashell[621]: QXcbConnection: XCB error: 2 (BadValue), sequence: 5949, resource id: 77594630, major code: 142 (Unknown), minor code: 3
Feb 13 13:11:39  plasmashell[621]: QXcbConnection: XCB error: 2 (BadValue), sequence: 6120, resource id: 50331653, major code: 142 (Unknown), minor code: 3
Feb 13 13:11:43  plasmashell[621]: QXcbConnection: XCB error: 2 (BadValue), sequence: 6254, resource id: 79691862, major code: 142 (Unknown), minor code: 3
Feb 13 13:11:48  NetworkManager[366]: <warn>  [1486980708.7883] dhcp4 (enp3s0): request timed out
Feb 13 13:11:48  NetworkManager[366]: <info>  [1486980708.7884] dhcp4 (enp3s0): state changed unknown -> timeout
Feb 13 13:11:48  NetworkManager[366]: <info>  [1486980708.8106] dhcp4 (enp3s0): canceled DHCP transaction
Feb 13 13:11:48  NetworkManager[366]: <info>  [1486980708.8107] dhcp4 (enp3s0): state changed timeout -> done
Feb 13 13:11:48  NetworkManager[366]: <info>  [1486980708.8109] device (enp3s0): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Feb 13 13:11:48  NetworkManager[366]: <warn>  [1486980708.8112] device (enp3s0): Activation: failed for connection 'Wired connection 1'
Feb 13 13:11:48  NetworkManager[366]: <info>  [1486980708.8115] device (enp3s0): state change: failed -> disconnected (reason 'none') [120 30 0]
Feb 13 13:11:48  NetworkManager[366]: <info>  [1486980708.8130] policy: auto-activating connection 'Wired connection 1'
Feb 13 13:11:48  NetworkManager[366]: <info>  [1486980708.8139] device (enp3s0): Activation: starting connection 'Wired connection 1' (61cf701a-7029-3b2c-8356-11613a0723c5)
Feb 13 13:11:48  NetworkManager[366]: <info>  [1486980708.8149] device (enp3s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb 13 13:11:48  kdeinit5[578]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "TxBytes"
Feb 13 13:11:48  NetworkManager[366]: <info>  [1486980708.8169] device (enp3s0): state change: prepare -> config (reason 'none') [40 50 0]
Feb 13 13:11:48  NetworkManager[366]: <info>  [1486980708.8179] device (enp3s0): state change: config -> ip-config (reason 'none') [50 70 0]
Feb 13 13:11:48  NetworkManager[366]: <info>  [1486980708.8184] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
Feb 13 13:11:48  kdeinit5[578]: plasma-nm: Unhandled active connection state change:  1
Feb 13 13:11:48  plasmashell[621]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "TxBytes"
Feb 13 13:11:56  plasmashell[621]: QXcbConnection: XCB error: 2 (BadValue), sequence: 6375, resource id: 69206017, major code: 142 (Unknown), minor code: 3
Feb 13 13:11:56  plasmashell[621]: QXcbConnection: XCB error: 2 (BadValue), sequence: 6393, resource id: 50331653, major code: 142 (Unknown), minor code: 3
Feb 13 13:11:57  plasmashell[621]: KActivities: Database connection:  "kactivities_db_resources_139919135053824_readonly" 
                                                  query_only:          QVariant(qlonglong, 1) 
                                                  journal_mode:        QVariant(QString, "wal") 
                                                  wal_autocheckpoint:  QVariant(qlonglong, 100) 
                                                  synchronous:         QVariant(qlonglong, 0)
Feb 13 13:11:57  plasmashell[621]: Closing SQL connection:  "kactivities_db_resources_139919135053824_readonly"
Feb 13 13:11:59  kwin_x11[607]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 45120, resource id: 39846302, major code: 2 (ChangeWindowAttributes), minor code: 0
Feb 13 13:11:59  plasmashell[621]: QXcbConnection: XCB error: 2 (BadValue), sequence: 6810, resource id: 79691862, major code: 142 (Unknown), minor code: 3
Feb 13 13:12:00  plasmashell[621]: QXcbConnection: XCB error: 2 (BadValue), sequence: 6916, resource id: 69206017, major code: 142 (Unknown), minor code: 3
Feb 13 13:12:00  plasmashell[621]: QXcbConnection: XCB error: 2 (BadValue), sequence: 6939, resource id: 50331653, major code: 142 (Unknown), minor code: 3
Feb 13 13:12:02  plasmashell[621]: KActivities: Database connection:  "kactivities_db_resources_139919135053824_readonly" 
                                                  query_only:          QVariant(qlonglong, 1) 
                                                  journal_mode:        QVariant(QString, "wal") 
                                                  wal_autocheckpoint:  QVariant(qlonglong, 100) 
                                                  synchronous:         QVariant(qlonglong, 0)
Feb 13 13:12:02  plasmashell[621]: Closing SQL connection:  "kactivities_db_resources_139919135053824_readonly"
Feb 13 13:12:04  plasmashell[621]: QXcbConnection: XCB error: 2 (BadValue), sequence: 7167, resource id: 79691862, major code: 142 (Unknown), minor code: 3
Feb 13 13:12:27  plasmashell[621]: QXcbConnection: XCB error: 2 (BadValue), sequence: 8368, resource id: 69206017, major code: 142 (Unknown), minor code: 3
Feb 13 13:12:33  NetworkManager[366]: <warn>  [1486980753.7873] dhcp4 (enp3s0): request timed out
Feb 13 13:12:33  NetworkManager[366]: <info>  [1486980753.7873] dhcp4 (enp3s0): state changed unknown -> timeout
Feb 13 13:12:33  NetworkManager[366]: <info>  [1486980753.8040] dhcp4 (enp3s0): canceled DHCP transaction
Feb 13 13:12:33  NetworkManager[366]: <info>  [1486980753.8040] dhcp4 (enp3s0): state changed timeout -> done
Feb 13 13:12:33  NetworkManager[366]: <info>  [1486980753.8043] device (enp3s0): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Feb 13 13:12:33  NetworkManager[366]: <warn>  [1486980753.8045] device (enp3s0): Activation: failed for connection 'Wired connection 1'
Feb 13 13:12:33  NetworkManager[366]: <info>  [1486980753.8048] device (enp3s0): state change: failed -> disconnected (reason 'none') [120 30 0]
Feb 13 13:12:33  NetworkManager[366]: <info>  [1486980753.8061] policy: auto-activating connection 'Wired connection 1'
Feb 13 13:12:33  NetworkManager[366]: <info>  [1486980753.8069] device (enp3s0): Activation: starting connection 'Wired connection 1' (61cf701a-7029-3b2c-8356-11613a0723c5)
Feb 13 13:12:33  NetworkManager[366]: <info>  [1486980753.8070] device (enp3s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb 13 13:12:33  NetworkManager[366]: <info>  [1486980753.8074] device (enp3s0): state change: prepare -> config (reason 'none') [40 50 0]
Feb 13 13:12:33  NetworkManager[366]: <info>  [1486980753.8077] device (enp3s0): state change: config -> ip-config (reason 'none') [50 70 0]
Feb 13 13:12:33  NetworkManager[366]: <info>  [1486980753.8080] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
Feb 13 13:12:33  kdeinit5[578]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "TxBytes"
Feb 13 13:12:33  kdeinit5[578]: plasma-nm: Unhandled active connection state change:  1
Feb 13 13:12:33  plasmashell[621]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "TxBytes"
Feb 13 13:13:18  NetworkManager[366]: <warn>  [1486980798.7873] dhcp4 (enp3s0): request timed out
Feb 13 13:13:18  NetworkManager[366]: <info>  [1486980798.7873] dhcp4 (enp3s0): state changed unknown -> timeout
Feb 13 13:13:18  NetworkManager[366]: <info>  [1486980798.8173] dhcp4 (enp3s0): canceled DHCP transaction
Feb 13 13:13:18  NetworkManager[366]: <info>  [1486980798.8173] dhcp4 (enp3s0): state changed timeout -> done
Feb 13 13:13:18  NetworkManager[366]: <info>  [1486980798.8176] device (enp3s0): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Feb 13 13:13:18  NetworkManager[366]: <info>  [1486980798.8177] policy: disabling autoconnect for connection 'Wired connection 1'.
Feb 13 13:13:18  NetworkManager[366]: <warn>  [1486980798.8178] device (enp3s0): Activation: failed for connection 'Wired connection 1'
Feb 13 13:13:18  NetworkManager[366]: <info>  [1486980798.8182] device (enp3s0): state change: failed -> disconnected (reason 'none') [120 30 0]
Feb 13 13:13:18  kdeinit5[578]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "TxBytes"
Feb 13 13:13:18  plasmashell[621]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "TxBytes"

contrary to what i wrote before, DHCPREQUESTs and OFFERs actually get logged, but theres no response for some reason

Feb 13 13:10:10ndhcps_WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:10:10ndhcps_WEBADMIN: sending ACK of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:10:12ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:10:13ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:10:13ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:10:14ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:10:15ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:10:15ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:10:18ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:10:18ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:10:26ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:10:27ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:10:42ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:10:42ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:10:55ndhcps_WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:10:55ndhcps_WEBADMIN: sending ACK of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:10:56ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:10:57ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:10:58ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:10:58ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:11:00ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:11:00ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:11:04ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:11:05ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:11:12ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:11:12ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:11:27ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:11:28ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:11:40ndhcps_WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:11:40ndhcps_WEBADMIN: sending ACK of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:11:43ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:11:43ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:11:46ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:11:46ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:11:49ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:11:49ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:11:53ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:11:54ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:12:02ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:12:02ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:12:18ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:12:19ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:12:25ndhcps_WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:12:25ndhcps_WEBADMIN: sending ACK of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:12:27ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:12:27ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:12:29ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:12:30ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:12:32ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:12:32ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:12:37ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:12:37ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:12:45ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:12:46ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.
Feb 13 13:13:01ndhcps_WEBADMIN: DHCPDISCOVER received  for 192.168.1.35 from 74:d4:35:ae:3e:9d.
Feb 13 13:13:02ndhcps_WEBADMIN: making OFFER of 192.168.1.35 to 74:d4:35:ae:3e:9d.

i see 2 possibilities here: either a driver bug or a plasma bug.

guess if i dont get a reply here im gonna post the issue on kde forums and see if the folks have a solution.

Offline

Pages: 1

Board footer

Powered by FluxBB