From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "mingo@kernel.org" <mingo@kernel.org>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.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: Fri, 10 Mar 2017 17:37:32 +0000 [thread overview]
Message-ID: <1489167438.2548.3.camel@sandisk.com> (raw)
In-Reply-To: <20170310072336.GA4909@gmail.com>
On Fri, 2017-03-10 at 08:23 +0100, Ingo Molnar wrote:
> * Bart Van Assche <Bart.VanAssche@sandisk.com> wrote:
> > 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?
>
> The bisection information is really useful, if the failure mode is deterministic.
>
> It would be nice to have more bisection points, the above range is about 5,000
> commits.
Hello Ingo,
Sorry that I had mentioned such a big range of commits. The bisect process
actually pointed out a single commit as the first bad commit. I had not
mentioned that information because I did not trust it. Anyway, when I tried
to reproduce the hang this morning with the commit marked as "bad" the hang
did not occur. I think this means the hang is reproducible most of the time
but not always. That probably explains why none of my two bisect attempts so
far pointed at a commit that introduced the hang. I'll try to find a way to
reproduce the hang reliably.
Bart.
next prev parent reply other threads:[~2017-03-10 17:37 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
2017-03-10 7:23 ` Ingo Molnar
2017-03-10 17:37 ` Bart Van Assche [this message]
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=1489167438.2548.3.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.