archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <>
To: Ingo Molnar <>
Cc: Mariusz Kozlowski <>,
	Adrian Bunk <>,,,
	Andrew Morton <>,, Gregory Haskins <>
Subject: Re: spontaneous reboots and hangs on x86_64
Date: Sat, 17 May 2008 13:23:17 +1000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]

Hi Ingo,

On Fri, 16 May 2008 20:53:36 +0200 Mariusz Kozlowski <> wrote:
> Ok I got bisection working finally, now I'm at d5be23e2 I have something like 80 revisions left and
> I'm stuck with this:
> In file included from kernel/sched.c:1861:
> kernel/sched_rt.c: In function 'check_preempt_curr_rt':
> kernel/sched_rt.c:653: error: implicit declaration of function 'cpupri_find'
> kernel/sched_rt.c:653: error: 'struct root_domain' has no member named 'cpupri'
> make[1]: *** [kernel/sched.o] Error 1
> make: *** [kernel] Error 2

This error is caused by commit 677ceea32cf1d8ba9a4870bc58079cd7e7f77558
("sched: prioritize non-migratable tasks over migratable ones") in the
sched tree (sched/for-akpm).  This commit is either just wrong, is was
misrebased, or is just badly out of order.  It introduces a use of
cpupri_find, but the function is not defined until commit
ea9b3c95b7c666d4658a139b88587269e5baa647 ("sched: use a 2-d bitmap for
searching lowest-pri CPU") about 146 commits later ...

Stephen Rothwell          

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

       reply	other threads:[~2008-05-17  3:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
     [not found]   ` <>
     [not found]     ` <>
2008-05-17  3:23       ` Stephen Rothwell [this message]
2008-05-24 16:11         ` spontaneous reboots and hangs on x86_64 Mariusz Kozlowski

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).