From: Dan Williams <dcbw@redhat.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Woody Suwalski <terraluna977@gmail.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
kernel list <linux-kernel@vger.kernel.org>,
Linux-pm mailing list <linux-pm@vger.kernel.org>,
Netdev list <netdev@vger.kernel.org>
Subject: Re: linux-next on x60: network manager often complains "network is disabled" after resume
Date: Mon, 19 Mar 2018 12:45:49 -0500 [thread overview]
Message-ID: <1521481549.20208.8.camel@redhat.com> (raw)
In-Reply-To: <20180319173356.GA28462@amd>
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?
Dan
next prev parent reply other threads:[~2018-03-19 17:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-18 10:40 linux-next on x60: network manager often complains "network is disabled" after resume Pavel Machek
2018-03-19 9:17 ` Woody Suwalski
2018-03-19 9:21 ` Pavel Machek
2018-03-19 15:40 ` Dan Williams
2018-03-19 17:33 ` Pavel Machek
2018-03-19 17:45 ` Dan Williams [this message]
2018-03-20 8:03 ` Pavel Machek
2018-03-20 13:12 ` Dan Williams
2018-03-25 6:19 ` Pavel Machek
2018-03-26 15:33 ` Dan Williams
2018-04-03 8:51 ` linux-next on x60: hangs when I request suspend was " Pavel Machek
2018-04-15 16:16 ` Pavel Machek
2018-04-17 15:03 ` Dan Williams
2018-04-17 21:00 ` Pavel Machek
2018-04-12 21:09 ` Pavel Machek
2018-03-20 21:26 ` Woody Suwalski
2018-03-21 1:11 ` Woody Suwalski
2018-04-15 16:15 ` Pavel Machek
2018-04-22 12:19 ` Woody Suwalski
2018-04-22 19:22 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1521481549.20208.8.camel@redhat.com \
--to=dcbw@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=terraluna977@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).