From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jiang Liu <jiang.liu@linux.intel.com>
Subject: Re: [GIT PULL] x86/apic updates for v3.20
Date: Fri, 13 Feb 2015 03:06:49 +0100 [thread overview]
Message-ID: <2495969.f1SBuodJtC@vostro.rjw.lan> (raw)
In-Reply-To: <CA+55aFw-Ly4xB91TPVW9w3YWL0eS96FqH2BngzeBpqtXBh_Zmw@mail.gmail.com>
On Thursday, February 12, 2015 04:52:49 PM Linus Torvalds wrote:
> On Mon, Feb 9, 2015 at 1:15 AM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > Please pull the latest x86-apic-for-linus git tree from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-apic-for-linus
>
> Just a heads-up: I'm currently bisecting my Chromebook Pixel no longer
> suspending cleanly, and it *seems* to be narrowing down on the apic
> changes (the scheduler changes are also in play, but they would seem
> less likely).
>
> I'll update as I know more, but if somebody goes "ahh, xyzzy might
> matter for suspend/resume", then that might be worth it. Any ideas?
>
> (The exact suspend failure is that it locks up at the end of the
> suspend somewhere, and never actually shuts down the machine)
FWIW, I have a revert in my tree which is related to broken suspend. Commits
to revert are e06bf91b59d3 and 37d11391c2de in this order.
I'll be sending a pull request with that tomorrow.
Rafael
next prev parent reply other threads:[~2015-02-13 1:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 9:15 Ingo Molnar
2015-02-13 0:52 ` Linus Torvalds
2015-02-13 2:06 ` Rafael J. Wysocki [this message]
2015-02-13 2:08 ` Linus Torvalds
2015-02-13 2:50 ` Linus Torvalds
2015-02-13 5:05 ` Jiang Liu
2015-02-13 15:47 ` Joerg Roedel
2015-02-13 17:00 ` Linus Torvalds
2015-02-13 17:47 ` Jiang Liu
2015-02-16 7:22 ` Ingo Molnar
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=2495969.f1SBuodJtC@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jiang.liu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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
all inboxes | Powered by JetHome®