From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@alien8.de>
Subject: Re: [GIT PULL] x86/mm changes for v4.14: PCID support, 5-level paging support, Secure Memory Encryption support
Date: Tue, 5 Sep 2017 23:40:46 +0200 [thread overview]
Message-ID: <20170905214046.ishenhbj7jrtoufc@gmail.com> (raw)
In-Reply-To: <CA+55aFy=BswnBBFQneCywMNGq-=Kp0-iBKnT6_FvHb8cA8stkw@mail.gmail.com>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Mon, Sep 4, 2017 at 2:31 AM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > Please pull the latest ... git tree from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ...
>
> Hmm. My laptop (XPS 13) doesn't resume any more. It suspends, but
> doesn't come back from resume.
>
> I immediately assumed it was the power management pulls I just did,
> but then I started bisecting, and now it's actually pointing into the
> various x86 pulls I did yesterday instead.
>
> Now, I'm reasonably early in my bisection (so literally "somewhere
> between the 'docs-next' and the 'x86-mm-for-linus' pull), and maybe
> the problem isn't even entirely repeatable and my bisection has
> already gone off the rails, but I thought I'd give at least an early
> heads-up about this thing.
>
> I'll have more as it bisects deeper into the merge window, but it
> might be a while.
Hm, just as background, there are no regression reports I'm aware of
against any of these trees, plus most of the dangerous commits have
been in linux-next for at least two weeks - the majority of them even
longer. The last 2-4 commits of x86/mm are fresher.
But it could be a regression in an older commit in x86/mm just as well,
triggered by you for the first time :-/
Does your laptop CPU have PCID support by any chance? The CPU coming
out of resume with PCID disabled and us not properly re-enabling it
might be a possible failure mode.
Thanks,
Ingo
next prev parent reply other threads:[~2017-09-05 21:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 9:31 [GIT PULL] x86/mm changes for v4.14: PCID support, 5-level paging support, Secure Memory Encryption support Ingo Molnar
2017-09-04 12:23 ` Kirill A. Shutemov
2017-09-04 13:01 ` Thomas Gleixner
2017-09-04 13:54 ` Ingo Molnar
2017-09-05 21:17 ` Linus Torvalds
2017-09-05 21:37 ` Andy Lutomirski
2017-09-05 21:44 ` Borislav Petkov
2017-09-05 21:40 ` Ingo Molnar [this message]
2017-09-05 21:45 ` Linus Torvalds
2017-09-05 22:33 ` Linus Torvalds
2017-09-05 22:35 ` Andy Lutomirski
2017-09-05 23:09 ` Linus Torvalds
2017-09-06 20:43 ` Jiri Kosina
2017-09-06 21:16 ` Jiri Kosina
2017-09-06 22:26 ` Andy Lutomirski
2017-09-05 21:50 ` Linus Torvalds
2017-09-07 8:07 ` Ingo Molnar
2017-09-07 8:13 ` Ingo Molnar
2017-09-15 11:26 ` 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=20170905214046.ishenhbj7jrtoufc@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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