From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751179AbeCYGTc (ORCPT ); Sun, 25 Mar 2018 02:19:32 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:54986 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751023AbeCYGTa (ORCPT ); Sun, 25 Mar 2018 02:19:30 -0400 Date: Sun, 25 Mar 2018 08:19:27 +0200 From: Pavel Machek To: Dan Williams Cc: Woody Suwalski , "Rafael J. Wysocki" , kernel list , Linux-pm mailing list , Netdev list Subject: Re: linux-next on x60: network manager often complains "network is disabled" after resume Message-ID: <20180325061927.GA2148@amd> References: <20180318104023.GA10392@amd> <70721f83-344a-0f23-223b-9c81f6e9e32a@gmail.com> <20180319092106.GA5683@amd> <1521474008.20208.2.camel@redhat.com> <20180319173356.GA28462@amd> <1521481549.20208.8.camel@redhat.com> <20180320080334.GA31772@amd> <1521551568.16848.5.camel@redhat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6TrnltStXW4iwmi0" Content-Disposition: inline In-Reply-To: <1521551568.16848.5.camel@redhat.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > > > Ok, what does 'nmcli dev' and 'nmcli radio' show? > >=20 > > Broken state. > >=20 > > pavel@amd:~$ nmcli dev > > DEVICE TYPE STATE CONNECTION > > eth1 ethernet unavailable -- > > lo loopback unmanaged -- > > wlan0 wifi unmanaged -- >=20 > If the state is "unmanaged" on resume, that would indicate a problem > with sleep/wake and likely not a kernel network device issue. >=20 > 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' root@amd:/data/pavel# nmcli gen log level help Error: Unknown log level '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 root@amd:/data/pavel# cat /var/log/sys/log 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... Thanks, Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlq3P28ACgkQMOfwapXb+vLCsQCeMf6Vl1miUZH5hRw9DG172euS lcIAnR8RW46Rh3FQuFEjjGkPvKfKKwHT =iXHh -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0--