From: Peter Zijlstra <peterz@infradead.org>
To: Greg Donald <gdonald@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>
Subject: Re: find_busiest_group divide error
Date: Wed, 16 Jul 2014 17:27:36 +0200 [thread overview]
Message-ID: <20140716152736.GD19379@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20140714165659.GA9289@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
On Mon, Jul 14, 2014 at 11:56:59AM -0500, Greg Donald wrote:
>
> [1.] One line summary of the problem:
>
> find_busiest_group divide error
>
> [2.] Full description of the problem/report:
>
> Around June 7th I found I could no longer boot a mainline kernel. I
> posted about it here on June 9th:
>
> http://lists.kernelnewbies.org/pipermail/kernelnewbies/2014-June/010914.html
>
> I bisected two complete times but never got to a commit that made any
> sense:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=77711
>
> I see a lot of kernel/sched/fair.c patching appeared in mainline on June
> 5th:
>
> https://github.com/torvalds/linux/commits/master/kernel/sched/fair.c
>
> So I tried checking out specific revisions and found
> 09dc4ab03936df5c5aa711d27c81283c6d09f495 is the latest good revision I
> can boot. The first bad revision I hit is
> 51f2176d74ace4c3f58579a605ef5a9720befb00.
>
> I have no idea how to fix it. I'm just a web developer/kernel tester :(
>
Could you confirm if reverting caffcdd8d27ba78730d5540396ce72ad022aff2c
cures things for you?
Otherwise there's two very similar issues, see also:
lkml.kernel.org/r/20140716145546.GA6922@wolff.to
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-07-16 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 16:56 find_busiest_group divide error Greg Donald
2014-07-16 15:27 ` Peter Zijlstra [this message]
2014-07-16 16:40 ` Bruno Wolff III
2014-07-16 17:52 ` Greg Donald
2014-07-16 21:31 ` Dietmar Eggemann
2014-07-16 21:47 ` Greg Donald
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=20140716152736.GD19379@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=gdonald@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
/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.