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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 20 Mar 2018 08:12:48 -0500
From:   Dan Williams <dcbw@...hat.com>
To:     Pavel Machek <pavel@....cz>
Cc:     Woody Suwalski <terraluna977@...il.com>,
        "Rafael J. Wysocki" <rjw@...ysocki.net>,
        kernel list <linux-kernel@...r.kernel.org>,
        Linux-pm mailing list <linux-pm@...r.kernel.org>,
        Netdev list <netdev@...r.kernel.org>
Subject: Re: linux-next on x60: network manager often complains "network is
 disabled" after resume

On Tue, 2018-03-20 at 09:03 +0100, Pavel Machek wrote:
> On Mon 2018-03-19 12:45:49, Dan Williams wrote:
> > On Mon, 2018-03-19 at 18:33 +0100, Pavel Machek wrote:
> > > On Mon 2018-03-19 10:40:08, Dan Williams wrote:
> > > > On Mon, 2018-03-19 at 10:21 +0100, 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.
> > > > 
> > > > Where does the complaint occur?  In the GUI, or with nmcli, or
> > > > somewhere else?  Also, what's the output of "nmcli dev" after
> > > > resume?
> > > 
> > > In the GUI. I click in place where I'd select access point, and
> > > menu
> > > does not show up, telling me that "network is disabled".
> > 
> > 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.

Dan

> pavel@amd:~$ nmcli radio
> WIFI-HW  WIFI     WWAN-HW  WWAN
> enabled  enabled  enabled  enabled
> pavel@amd:~$ uname -a
> Linux amd 4.16.0-rc5-next-20180314+ #31 SMP Thu Mar 15 14:27:19 CET
> 2018 i686 GNU/Linux
> 
> Let me suspend/resume. I was lucky and got it into working state:
> 
> pavel@amd:~$ nmcli dev
> DEVICE  TYPE      STATE        CONNECTION
> wlan0   wifi      connected    openwireless.org
> eth1    ethernet  unavailable  --
> lo      loopback  unmanaged    --
> pavel@amd:~$ nmcli radio
> WIFI-HW  WIFI     WWAN-HW  WWAN
> enabled  enabled  enabled  enabled
> paveamd:~$
> 
> Best regards,
> 									
> Pavel
>