From: Joerg Roedel <joro@8bytes.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] x86/platform changes for v3.9
Date: Wed, 20 Feb 2013 12:12:55 +0100 [thread overview]
Message-ID: <20130220111255.GB26252@8bytes.org> (raw)
In-Reply-To: <20130220090238.GA18213@gmail.com>
On Wed, Feb 20, 2013 at 10:02:38AM +0100, Ingo Molnar wrote:
> Timers and APIC would be my leading suspect - but scheduler and
> hotplug changes might be the culprits as well.
>
> Yesterday, while preparing the trees I wanted to mention this
> x86/apic commit:
>
> 336224ba5e4f x86, apic: Mask IO-APIC and PIC unconditionally on LAPIC resume
>
> ... as a change that needs monitored because it changes the
> suspend and shutdown sequence but then skipped mentioning it
> because it seemed relatively old and proven.
Hmm, this commit only touches the resume-path. I would wonder if this
has something to do with reboot, can't rule it out, though.
> But there are other potentially dangerous commits as well - I
> suspect we won't be able to avoid a bisection :-/
Yes, I think a bisection would be best if the problem is reproducible.
Joerg
next prev parent reply other threads:[~2013-02-20 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 15:41 Ingo Molnar
2013-02-20 6:39 ` Linus Torvalds
2013-02-20 9:02 ` Ingo Molnar
2013-02-20 9:14 ` Ingo Molnar
2013-02-20 11:12 ` Joerg Roedel [this message]
2013-02-20 17:15 ` Linus Torvalds
2013-02-20 18:17 ` Dave Jones
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=20130220111255.GB26252@8bytes.org \
--to=joro@8bytes.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.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
Powered by JetHome