Also, just in case it's relevant in confirming the eventual commit, I've already mentioned above that after the first suspend and kworker going to 100%, I can't suspend a second time (I get a complete freeze requiring a hard power-off), but if I instead try a soft power off rather than the second suspend, it will finally power off after a minute of scrolling this message over the console (which I grabbed from syslog):
Sep 17 21:39:40 michael-X201EP kernel: [ 100.139891] alx 0000:03:00.0: invalid PHY speed/duplex: 0xffff Sep 17 21:39:40 michael-X201EP kernel: [ 100.141169] alx 0000:03:00.0: invalid PHY speed/duplex: 0xffff Sep 17 21:39:40 michael-X201EP kernel: [ 100.142847] alx 0000:03:00.0: invalid PHY speed/duplex: 0xffff Sep 17 21:39:40 michael-X201EP kernel: [ 100.144159] alx 0000:03:00.0: invalid PHY speed/duplex: 0xffff Sep 17 21:39:40 michael-X201EP kernel: [ 100.145398] alx 0000:03:00.0: invalid PHY speed/duplex: 0xffff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
