All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "tglx@linutronix.de" <tglx@linutronix.de>
Cc: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	"mingo@kernel.org" <mingo@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [GIT pull] CPU hotplug updates for 4.9
Date: Thu, 9 Mar 2017 22:48:16 +0000	[thread overview]
Message-ID: <1489099682.2597.14.camel@sandisk.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1703091829530.3521@nanos>

On Thu, 2017-03-09 at 18:43 +0100, Thomas Gleixner wrote:
> Ok, so it's random. Now it would be interesting what the rest of the system
> does when this happens. I still have no idea why that IOAT setting has any
> influence.

Hello Thomas,

The cpuhp_issue_call() hang happens during boot and before I get the chance to log
in with ssh. Can you be more specific about what information you are looking for?

Anyway, the result of a new bisect I ran is as follows:
* good: 631ddaba5905 ("Merge branches 'pm-sleep' and 'powercap'").
* good: 80f1b3dea9d4 ("Merge branch 'device-properties'").
* bad:  a67485d4bf97 ("Merge tag 'acpi-4.10-rc1' of
  git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm").

Does this make sense to you?

Thanks,

Bart.

  reply	other threads:[~2017-03-09 22:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-03 17:37 [GIT pull] CPU hotplug updates for 4.9 Thomas Gleixner
2017-03-07  1:52 ` Bart Van Assche
2017-03-07  9:30   ` Thomas Gleixner
2017-03-07 22:32     ` Bart Van Assche
2017-03-08  8:25       ` Thomas Gleixner
2017-03-08 19:32         ` Bart Van Assche
2017-03-09 10:22           ` Thomas Gleixner
2017-03-09 17:20             ` Bart Van Assche
2017-03-09 17:43               ` Thomas Gleixner
2017-03-09 22:48                 ` Bart Van Assche [this message]
2017-03-10  7:23                   ` Ingo Molnar
2017-03-10 17:37                     ` Bart Van Assche
2017-03-10 21:32                 ` Bart Van Assche
2017-03-14 15:06   ` [PATCH] cpu/hotplug: Serialize callback invocations proper Sebastian Andrzej Siewior
2017-03-14 17:38     ` Bart Van Assche
2017-03-14 17:43       ` Thomas Gleixner
2017-03-14 18:25     ` [tip:smp/urgent] " tip-bot for Sebastian Andrzej Siewior

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=1489099682.2597.14.camel@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --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 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.