LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
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, 26 Mar 2018 10:33:55 -0500	[thread overview]
Message-ID: <95efbba35c3389015d4919a59f8d01bc2d375a19.camel@redhat.com> (raw)
In-Reply-To: <20180325061927.GA2148@amd>

On Sun, 2018-03-25 at 08:19 +0200, Pavel Machek wrote:
> > > > 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.

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

nmcli gen help

> root@amd:/data/pavel# nmcli gen log level
> Error: value for 'level' argument is required.
> root@amd:/data/pavel# nmcli gen log level debug

This should be OK.

> root@amd:/data/pavel# cat /var/log/sys/log

It routes it to whatever the syslog 'daemon' facility logs to (however
that's configured on your system).  Usually /var/log/messages or
/var/log/daemon.log or sometimes your distro configures it to
/var/log/NetworkManager.log.

Or if you're using a systemd-based distro, it would probably be in the
systemd journal so "journalctl -b -u NetworkManager"

> Where do I get the logs? I don't see much in the syslog...

> And.. It seems that it is "every other suspend". One resume results
> in
> broken network, one in working one, one in broken one...

Does your distro use pm-utils, upower, or systemd for suspend/resume
handling?

Dan

  reply	other threads:[~2018-03-26 15:34 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
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 [this message]
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=95efbba35c3389015d4919a59f8d01bc2d375a19.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 \
    --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).