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@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Finally got to try the modprobe and it did restart the network.
sudo modprobe -r r8169
sudo modprobe r1869
So, what is my next step in finding out why this won't restart on suspend?
Robin
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
