Re: linux-next on x60: network manager often complains "network is disabled" after resume

Hi!
On Mon 2018-03-26 10:33:55, Dan Williams wrote:

On Sun, 2018-03-25 at 08:19 +0200, Pavel Machek wrote:

quoted

quoted

quoted

quoted

Ok, what does 'nmcli dev' and 'nmcli radio' show?

Broken state.

pavel@amd:~$ nmcli dev
DEVICE  TYPE      STATE        CONNECTION
eth1    ethernet  unavailable  --
lo      loopback  unmanaged    --
wlan0   wifi      unmanaged    --

If the state is "unmanaged" on resume, that would indicate a
problem
with sleep/wake and likely not a kernel network device issue.

We should probably move this discussion to the NM lists to debug
further.  Before you suspend, run "nmcli gen log level trace" to
turn
on full debug logging, then reproduce the issue, and send a pointer
to
those logs (scrubbed for anything you consider sensitive) to the NM
mailing list.

Hmm :-)

root@amd:/data/pavel# nmcli gen log level trace
Error: Unknown log level 'trace'

What NM version?  'trace' is pretty old (since 1.0 from December 2014)
so unless you're using a really, really old version of Debian I'd
expect you'd have it.  Anyway, debug would do.

...

Hmm. I also noticed now screen saver kicks in _right after I resume
the machine_. That did not use to be the case (and is a bit annoying
on its own).

Do we have any changes with time across suspend/resume in v4.17?

								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html