From: Gene Heskett <gene.heskett@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: v2.6.22.1-rt5
Date: Tue, 24 Jul 2007 11:56:03 -0400 [thread overview]
Message-ID: <200707241156.03149.gene.heskett@gmail.com> (raw)
In-Reply-To: <20070724120436.GA14466@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 1480 bytes --]
On Tuesday 24 July 2007, Ingo Molnar wrote:
>i've released the v2.6.23-rc1-rt0 kernel, which can be downloaded from
>the usual place:
>
> http://redhat.com/~mingo/realtime-preempt/
>
>as the rt0 name suggests it, this is a devel release, the first one
>after a rebase to 2.6.23-rc1. There's lots of changes and a reduction of
>50 patches (we are now at 320 patches) - so code from -rt is moving
>upstream at a steady pace. (latest bigger chunks that moved were CFS,
>lockstat, most of the -hrt queue, plus various fixes)
>
>more info about the -rt patchset can be found in the RT wiki:
>
> http://rt.wiki.kernel.org
>
>to build a 2.6.22.1-rt5 tree, the following patches should be applied:
>
> http://kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.23-rc1.tar.bz2
> http://redhat.com/~mingo/realtime-preempt/patch-2.6.23-rc1-rt0
>
> Ingo
The above stanza still needs some tlc. I built a 2.6.22.1-rt6 (rt5 wouldn't
build) using the same old config that a make oldconfig didn't fuss about, but
the reboot never completed, see the attached, heavily smunched camera shot of
the panic.
Kinda looks like hda/sda confusion, with rt3 (this boot), its hda*, what is it
now? fstab or kernel config error?
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
"Microwave oven? Whaddya mean, it's a microwave oven? I've been watching
Channel 4 on the thing for two weeks."
[-- Attachment #2: panic-20070724-2.6.22.1-rt6.jpg --]
[-- Type: image/jpeg, Size: 65588 bytes --]
next prev parent reply other threads:[~2007-07-24 15:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 12:04 v2.6.22.1-rt5 Ingo Molnar
2007-07-24 13:18 ` v2.6.22.1-rt5 Andi Kleen
2007-07-24 12:27 ` v2.6.23-rc1-rt0 Ingo Molnar
2007-07-24 15:56 ` Gene Heskett [this message]
2007-07-24 19:10 ` v2.6.22.1-rt5 Ingo Molnar
2007-07-25 1:29 ` v2.6.22.1-rt5 Gene Heskett
2007-07-25 1:36 ` v2.6.22.1-rt5 Gene Heskett
2007-07-25 7:52 ` v2.6.22.1-rt5 Ingo Molnar
2007-07-25 1:42 ` v2.6.22.1-rt5 Gene Heskett
-- strict thread matches above, loose matches on Subject: below --
2007-07-23 21:02 v2.6.22.1-rt5 Ingo Molnar
2007-07-23 21:29 ` v2.6.22.1-rt5 Rui Nuno Capela
2007-07-23 21:30 ` v2.6.22.1-rt5 Daniel Walker
2007-07-23 22:05 ` v2.6.22.1-rt5 Thomas Gleixner
2007-07-23 22:11 ` v2.6.22.1-rt5 Thomas Gleixner
2007-07-24 7:39 ` v2.6.22.1-rt5 Ingo Molnar
2007-07-24 19:34 ` v2.6.22.1-rt5 Fernando Lopez-Lezcano
2007-07-24 19:35 ` v2.6.22.1-rt5 Fernando Lopez-Lezcano
2007-07-24 20:05 ` v2.6.22.1-rt5 Ingo Molnar
2007-07-24 20:23 ` v2.6.22.1-rt5 Fernando Lopez-Lezcano
2007-07-24 20:34 ` v2.6.22.1-rt5 Ingo Molnar
2007-07-24 20:38 ` v2.6.22.1-rt5 Fernando Lopez-Lezcano
2007-07-25 7:34 ` v2.6.22.1-rt5 Alessio Igor Bogani
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=200707241156.03149.gene.heskett@gmail.com \
--to=gene.heskett@gmail.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