On 25/03/18 17:34, Samuel Sieb wrote:
On 03/25/2018 02:49 PM, Robin Laing wrote:
I am trying to trace down a problem with a laptop that when it goes
into suspend for any reason, the network won't come back up. Only a
reboot will enable the wired network.
Have you tried unloading and reloading the kernel module?
The only indication of any issue is an error message that pops up.
kernel: do_IRQ: 7.33 No irq handler for vector.
These messages are usually benign.
I would like to find more details but if I cannot I will just file a
bug against the kernel.
Have you checked the journal for the time around the resume? Note that
the first chunk of messages at the resume time are actually from the end
of the suspend before the resume.
It would also be useful to know the network chipset. "lspci -v" will
tell you both the chipset and the kernel driver being used. After
resume, try doing "modprobe -r <modulename>", then if that was
successful, do "modprobe <modulename>" and see if that fixes it.
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
I have looked through the journal logs before but still learning journalctl.
Looking through my notes, the problem seems to start around Feb 26.
Network controller is:
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411
PCI Express Gigabit Ethernet Controller (rev 0c)
Module is:
Kernel modules: r8169
From journal
The lid closed is detected and network manager shuts down the connection.
Network name is enp4s0
Start of suspend
Mar 25 21:31:44 xx NetworkManager[7949]: <info> [1522013504.0482]
device (enp4s0): state change: activated -> deactivating (reason
'sleeping', internal state 'managed')
Mar 25 21:31:44 xx NetworkManager[7949]: <info> [1522013504.0920]
device (enp4s0): state change: deactivating -> disconnected (reason
'sleeping', internal state 'managed')
Mar 25 21:31:44 xx avahi-daemon[7862]: Withdrawing address record for
2001:56a:7680:b500:4216:7eff:fe10:e09a on enp4s0.
Mar 25 21:31:44 xx NetworkManager[7949]: <info> [1522013504.0926] dhcp6
(enp4s0): canceled DHCP transaction
Mar 25 21:31:44 xx avahi-daemon[7862]: Leaving mDNS multicast group on
interface enp4s0.IPv6 with address 2001:56a:7680:b500:4216:7eff:fe10:e09a.
Mar 25 21:31:44 xx avahi-daemon[7862]: Joining mDNS multicast group on
interface enp4s0.IPv6 with address fe80::4216:7eff:fe10:e09a.
Mar 25 21:31:44 xx avahi-daemon[7862]: Registering new address record
for fe80::4216:7eff:fe10:e09a on enp4s0.*.
Mar 25 21:31:44 xx avahi-daemon[7862]: Withdrawing address record for
fe80::4216:7eff:fe10:e09a on enp4s0.
Mar 25 21:31:44 xx avahi-daemon[7862]: Leaving mDNS multicast group on
interface enp4s0.IPv6 with address fe80::4216:7eff:fe10:e09a.
Mar 25 21:31:44 xx avahi-daemon[7862]: Interface enp4s0.IPv6 no longer
relevant for mDNS.
Mar 25 21:31:44 xx avahi-daemon[7862]: Withdrawing address record for
192.168.1.21 on enp4s0.
Mar 25 21:31:44 xx avahi-daemon[7862]: Leaving mDNS multicast group on
interface enp4s0.IPv4 with address 192.168.1.21.
Mar 25 21:31:44 xx avahi-daemon[7862]: Interface enp4s0.IPv4 no longer
relevant for mDNS.
Mar 25 21:31:44 xx NetworkManager[7949]: <info> [1522013504.0950]
device (enp4s0): state change: disconnected -> unmanaged (reason
'sleeping', internal state 'managed')
Mar 25 21:31:44 xx nm-dispatcher[9588]: req:2 'down' [enp4s0]: new
request (6 scripts)
Mar 25 21:31:44 xx nm-dispatcher[9588]: req:2 'down' [enp4s0]: start
running ordered scripts...
Start of open lid from suspend
Mar 25 21:33:45 xx NetworkManager[7949]: <info> [1522013625.9934]
device (enp4s0): state change: unmanaged -> unavailable (reason
'managed', internal state 'managed')
Mar 25 21:33:45 xx kernel: IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is
not ready
Mar 25 21:33:46 xx kernel: r8169 0000:04:00.0 enp4s0: link down
Mar 25 21:33:46 xx kernel: IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is
not ready
This laptop is using KDE and sddm. Is there a
Looking further through the log files at another suspend today I came
across this.
Mar 26 01:07:54 xx kernel: r8169 0000:04:00.0 enp4s0: link down
Also, I find this but not sure if it is related.
Mar 26 01:07:54 xx audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=NetworkManager-dispatcher comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 01:07:55 xx ModemManager[1116]: <info> Couldn't check support
for device at '/sys/devices/pci0000:00/0000:00:1c.2/0000:03:00.0': not
supported by any plugin
Mar 26 01:07:55 xx ModemManager[1116]: <info> Couldn't check support
for device at '/sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0': not
supported by any plugin
Mar 26 01:07:55 xx kernel: do_IRQ: 7.33 No irq handler for vector
Looking further into the log files, I don't seen any mention of r1869
before March 17 when I tried to make a change to the boot parameters
from something I found on the net which was almost a month after the
problem started.
pci=nomsi,noaer
I will try the modprobe when I can.
Robin
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
