From: "Gregory Haskins" <ghaskins@novell.com>
To: <tglx@linutronix.de>
Cc: <jim.houston@ccur.com>, <joe.korty@ccur.com>, <mingo@elte.hu>,
<dwalker@mvista.com>, "David Bahi" <DBahi@novell.com>,
"Moiz Kohari" <MKohari@novell.com>,
"Sven Dietrich" <SDietrich@novell.com>, <dsaxena@plexity.net>,
<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 06:17:43 -0400 [thread overview]
Message-ID: <4695C7870200005A0002760F@mcclure.wal.novell.com> (raw)
On Thu, 2007-07-12 at 07:14 +0200, Thomas Gleixner wrote:
> On Wed, 2007-07-11 at 20:58 -0400, Gregory Haskins wrote:
> > Note also that we find that the resulting kernel does not boot on some
> > T60p thinkpads without "acpi=off". We are still investigating the root
> > cause here.
>
> Try "nohpet" for now. I'm investigating it on the -hrt side as well.
>
Ah, good to know others are looking at it.
On a different front, I see .21.6-rt21 came out in the last 24 hours.
Were there any fixes that went in between rt20-21 here, or was it simply
a forward port? If fixes, could you possibly share them to save me the
effort of working it out myself? I will then push the next version of
the 22-based forward port to rt21 today.
Regards,
-Greg
next reply other threads:[~2007-07-12 10:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 10:17 Gregory Haskins [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-12 16:26 Gregory Haskins
2007-07-12 16:33 ` Ingo Molnar
2007-07-12 20:21 ` Sven-Thorsten Dietrich
2007-07-13 12:52 ` Benjamin Herrenschmidt
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 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=4695C7870200005A0002760F@mcclure.wal.novell.com \
--to=ghaskins@novell.com \
--cc=DBahi@novell.com \
--cc=MKohari@novell.com \
--cc=SDietrich@novell.com \
--cc=dsaxena@plexity.net \
--cc=dwalker@mvista.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=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®