On Tue 2018-03-20 21:11:54, Woody Suwalski wrote: > Woody Suwalski wrote: > >Pavel Machek wrote: > >>On Mon 2018-03-19 05:17:45, Woody Suwalski wrote: > >>>Pavel Machek wrote: > >>>>Hi! > >>>> > >>>>With recent linux-next, after resume networkmanager often claims that > >>>>"network is disabled". Sometimes suspend/resume clears that. > >>>> > >>>>Any ideas? Does it work for you? > >>>> Pavel > >>>Tried the 4.16-rc6 with nm 1.4.4 - I do not see the issue. > >>Thanks for testing... but yes, 4.16 should be ok. If not fixed, > >>problem will appear in 4.17-rc1. > >> > >Works here OK. Tried ~10 suspends, all restarted OK. > >kernel next-20180320 > >nmcli shows that Wifi always connects OK > > > >Woody > > > Contrary, it just happened to me on a 64-bit build 4.16-rc5 on T440. > I think that Dan's suspicion is correct - it is a snafu in the PM: trying to > hibernate results in a message: > Failed to hibernate system via logind: There's already a shutdown or sleep > operation in progress. > > And ps shows "Ds /lib/systemd/systemd-sleep suspend"...
Problem now seems to be in the mainline. But no, I don't see systemd-sleep in my process list :-(. I guess you can't reproduce it easily? I tried bisecting, but while it happens often enough to make v4.17 hard to use, it does not permit reliable bisect. These should be bad according to my notes b04240a33b99b32cf6fbdf5c943c04e505a0cb07 ed80dc19e4dd395c951f745acd1484d61c4cfb20 52113a0d3889d6e2738cf09bf79bc9cac7b5e1c6 4fc97ef94bbfa185d16b3e44199b7559d0668747 14ebdb2c814f508936fe178a2abc906a16a3ab48 639adbeef5ae1bb8eeebbb0cde0b885397bde192 bisection claimed c16add24522547bf52c189b3c0d1ab6f5c2b4375 is first bad commit, but I'm not sure if I trust that. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Description: Digital signature