From: Ingo Molnar <mingo@elte.hu>
To: Gregory Haskins <ghaskins@novell.com>
Cc: jim.houston@ccur.com, joe.korty@ccur.com, rostedt@goodmis.org,
tglx@linutronix.de, dwalker@mvista.com,
David Bahi <DBahi@novell.com>, Moiz Kohari <MKohari@novell.com>,
Sven Dietrich <SDietrich@novell.com>,
dsaxena@plexity.net, williams@redhat.com, abogani@texware.it,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: Forward port of latest RT patch (2.6.21.5-rt20) to 2.6.22 available
Date: Thu, 12 Jul 2007 18:33:41 +0200 [thread overview]
Message-ID: <20070712163341.GA9622@elte.hu> (raw)
In-Reply-To: <46961E080200005A000276AE@mcclure.wal.novell.com>
* Gregory Haskins <ghaskins@novell.com> wrote:
> For the most part, it seems you guys have resolved most of the
> issues that we ran into as well (e.g. early-flush-tlb, relocated
> die-notifier, etc, come to mind). I found one patch that was missing
> that allows debug configurations to build properly. Heres that patch:
>
> --- linux-2.6.21.orig/kernel/latency_trace.c
> +++ linux-2.6.21/kernel/latency_trace.c
> @@ -24,6 +24,7 @@
> #include <linux/utsrelease.h>
> #include <asm/uaccess.h>
> #include <asm/unistd.h>
> +#include <asm/asm-offsets.h>
i think this breaks PPC (which has no asm-offsets.h file). In any case i
saw this build breakage too and the fix is in -rt2.
> We did find a regression. I was mistaken earlier when I mentioned our
> T60p laptops couldn't boot. It turns out that issue was resolved
> somewhere along the way and our published patches based on 21.5-rt19
> do allow the laptop to boot event with acpi=on. With 22.1-rt1 the
> laptop crashes unless acpi=off. Now that we have your queue we will
> bisect this and post that fix as well.
ok. Make sure you check rt2 as well - and note that it's not fully
bisectable with PREEMPT_RT enabled (but should probably be fully
bisectable with PREEMPT_RT disabled). So check out first whether the
problem still persists with PREEMPT_RT disabled.
Ingo
next prev parent reply other threads:[~2007-07-12 16:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 16:26 Forward port of latest RT patch (2.6.21.5-rt20) to 2.6.22 available Gregory Haskins
2007-07-12 16:33 ` Ingo Molnar [this message]
2007-07-12 20:21 ` Sven-Thorsten Dietrich
2007-07-13 12:52 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2007-07-12 12:26 Gregory Haskins
2007-07-12 13:09 ` Ingo Molnar
2007-07-13 6:25 ` Peter Williams
2007-07-13 6:52 ` Thomas Gleixner
2007-07-13 8:43 ` Gene Heskett
2007-07-13 9:42 ` Thomas Gleixner
2007-07-14 0:27 ` Peter Williams
2007-07-14 0:52 ` Gene Heskett
2007-07-12 11:10 Gregory Haskins
2007-07-12 10:17 Gregory Haskins
2007-07-12 0:58 Gregory Haskins
2007-07-12 1:05 ` Daniel Walker
2007-07-12 5:14 ` Thomas Gleixner
2007-07-12 7:27 ` Alessio Igor Bogani
2007-07-12 12:07 ` Ingo Molnar
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=20070712163341.GA9622@elte.hu \
--to=mingo@elte.hu \
--cc=DBahi@novell.com \
--cc=MKohari@novell.com \
--cc=SDietrich@novell.com \
--cc=abogani@texware.it \
--cc=dsaxena@plexity.net \
--cc=dwalker@mvista.com \
--cc=ghaskins@novell.com \
--cc=jim.houston@ccur.com \
--cc=joe.korty@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=williams@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox