I ran some tests today to try and pinpoint it a little better, and
understand why I didn't encounter it when testing a couple days ago. For
me, the case seems to be related to the user that suspends.
I couldn't find any difference between the kernel "4.15.0-38-generic
#41-Ubuntu" and "4.15.0-39-generic #42~lp1798921", meaning that on my
tests, they both happened and didn't happen under the same
circumstances.
* Boot Computer -> login to BOB -> Suspend -> Wake -> login to BOB => NO
PROBLEMS.
No matter how many times I tried, as long as I suspended and when woke logged
back in to the same user, I never encountered the bug.
* Boot Computer -> login to BOB -> Suspend -> Wake -> Login to MARY => FAIL.
If when I returned from suspend I logged in to a different user, I always
encountered the bug.
* Boot Computer -> login to BOB -> Suspend -> Wake -> Suspend again ->
login to BOB => FAIL.
If when I woke from the first sleep, the pc went back to suspend, and only then
I logged back in to BOB, I encountered the bug 100% of the time.
* Boot Computer -> login to BOB -> Lock screen(change user) -> Login to
MARY -> Suspend -> Wake -> Login to BOB => NO PROBLEMS.
Again, once I return from suspend, logging back to the user that 'established
the connection' means I don't have any issues.
* Boot Computer -> login to BOB -> Lock screen(change user) -> Login to
MARY -> Suspend -> Wake -> Login to MARY => FAIL.
Now, if I login to a different user, even if it is the user that performed the
suspend, I always encountered the bug.
* The instance that was not clear cut is when I logged out of a
user, instead of simply changing users. So for example, login to BOB,
suspend, wake, login to BOB, logout, and then go to Mary. I very rarely
encountered issues, but it did happen a couple times, so I'm not sure on
this point.
One very important thing to note is that when the bug happens, it sticks
up no matter what. So, if I encounter the bug, and do the workaround fix
with the modprobe command, the bug will happen again in the next
suspend, no matter in which circunstance. A reboot restores things to
normal.
Not sure if my case is similar to yours kris, but hopefully this bit
helps a bit more to pinpoint the issue.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Description changed:
Bug very similar to #1752772
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but
affecting the sky2 driver instead of r8169.
After system suspend the ethernet connection stops working. The card is
still up and the modem can see it is connected, but the card doesn't get
an ip address. Ifconfig down/up and restarting network-manager does not
solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an
then "sudo modprobe sky2" solves the issue.
Relevant:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107
--------
Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
- *-network
- description: Ethernet interface
- product: 88E8040 PCI-E Fast Ethernet Controller
- vendor: Marvell Technology Group Ltd.
- physical id: 0
- bus info: pci@0000:09:00.0
- logical name: enp9s0
- version: 13
- serial: 00:23:ae:ea:23:3e
- size: 100Mbit/s
- capacity: 100Mbit/s
- width: 64 bits
- clock: 33MHz
- capabilities: pm msi pciexpress bus_master cap_list ethernet physical
tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
- configuration: autonegotiation=on broadcast=yes driver=sky2
driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted
pair speed=100Mbit/s
- resources: irq:24 memory:f68fc000-f68fffff ioport:de00(size=256)
+ *-network
+ description: Ethernet interface
+ product: 88E8040 PCI-E Fast Ethernet Controller
+ vendor: Marvell Technology Group Ltd.
+ physical id: 0
+ bus info: pci@0000:09:00.0
+ logical name: enp9s0
+ version: 13
+ serial:
+ size: 100Mbit/s
+ capacity: 100Mbit/s
+ width: 64 bits
+ clock: 33MHz
+ capabilities: pm msi pciexpress bus_master cap_list ethernet physical
tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
+ configuration: autonegotiation=on broadcast=yes driver=sky2
driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted
pair speed=100Mbit/s
+ resources: irq:24 memory:f68fc000-f68fffff ioport:de00(size=256)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798921
Title:
sky2 ethernet card don't work after returning from suspension
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
