From: Pavel Machek <pavel@ucw.cz>
To: Woody Suwalski <terraluna977@gmail.com>
Cc: "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: Sun, 22 Apr 2018 21:22:53 +0200 [thread overview]
Message-ID: <20180422192253.GA5174@amd> (raw)
In-Reply-To: <01331018-8c62-30b2-673c-11b0bcd38c0e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
Hi!
> >I guess you can't reproduce it easily? I tried bisecting, but while it
> >happens often enough to make v4.17 hard to use, it does not permit
> >reliable bisect.
> >
> >These should be bad according to my notes
> >
> >b04240a33b99b32cf6fbdf5c943c04e505a0cb07
> > ed80dc19e4dd395c951f745acd1484d61c4cfb20
> > 52113a0d3889d6e2738cf09bf79bc9cac7b5e1c6
> > 4fc97ef94bbfa185d16b3e44199b7559d0668747
> > 14ebdb2c814f508936fe178a2abc906a16a3ab48
> > 639adbeef5ae1bb8eeebbb0cde0b885397bde192
> >
> >bisection claimed
> >
> >c16add24522547bf52c189b3c0d1ab6f5c2b4375
> >
> >is first bad commit, but I'm not sure if I trust that.
> > Pavel
> It has not happen on any of my systems in the last month. Good, but bad for
> getting more info :-(
My current theory is that it only happens if you suspend your machine
for > ten minutes, or something like that.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2018-04-22 19:22 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
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 [this message]
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=20180422192253.GA5174@amd \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.