LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Woody Suwalski <terraluna977@gmail.com>
To: Pavel Machek <pavel@ucw.cz>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	kernel list <linux-kernel@vger.kernel.org>,
	Linux-pm mailing list <linux-pm@vger.kernel.org>
Cc: 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 05:17:45 -0400	[thread overview]
Message-ID: <70721f83-344a-0f23-223b-9c81f6e9e32a@gmail.com> (raw)
In-Reply-To: <20180318104023.GA10392@amd>

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.

Woody

  reply	other threads:[~2018-03-19  9:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-18 10:40 Pavel Machek
2018-03-19  9:17 ` Woody Suwalski [this message]
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
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=70721f83-344a-0f23-223b-9c81f6e9e32a@gmail.com \
    --to=terraluna977@gmail.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 \
    --subject='Re: linux-next on x60: network manager often complains "network is disabled" after resume' \
    /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

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).