i've released the 2.6.18-rc6-rt0 tree, which can be downloaded from the
usual place:
http://redhat.com/~mingo/realtime-preempt/
i also started an -rt YUM repository for Fedora Core 6, which can be
activated via:
cd /etc/yum.repos.d
wget http://people.redhat.com/~mingo/realtime-preempt/rt.repo
yum update kernel
-rt0 is a rebase of -rt to 2.6.19-rc6, with lots of updates and fixes
included. It includes the latest -hrt-dynticks tree and more.
to build a 2.6.19-rc6-rt0 tree, the following patches should be applied:
http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.18.tar.bz2
http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.19-rc6.bz2
http://redhat.com/~mingo/realtime-preempt/patch-2.6.19-rc6-rt0
as usual, bugreports, fixes and suggestions are welcome,
Ingo
On Thu, 2006-11-16 at 16:35 +0100, Ingo Molnar wrote:
> -rt0 is a rebase of -rt to 2.6.19-rc6, with lots of updates and fixes
> included. It includes the latest -hrt-dynticks tree and more.
Does the zero carry and meaning or did you just decide start using zero
instead of one?
Daniel
* Daniel Walker <[email protected]> wrote:
> > -rt0 is a rebase of -rt to 2.6.19-rc6, with lots of updates and
> > fixes included. It includes the latest -hrt-dynticks tree and more.
>
> Does the zero carry and meaning or did you just decide start using
> zero instead of one?
no real meaning other than zero better signals the first -rc port's
relative freshness.
Ingo
On Thu, 16 Nov 2006, Daniel Walker wrote:
> On Thu, 2006-11-16 at 16:35 +0100, Ingo Molnar wrote:
>
>> -rt0 is a rebase of -rt to 2.6.19-rc6, with lots of updates and fixes
>> included. It includes the latest -hrt-dynticks tree and more.
>
>
> Does the zero carry and meaning or did you just decide start using zero
> instead of one?
>
> Daniel
0 bugs?
Esben
On Thu, 2006-11-16 at 22:12 +0100, Esben Nielsen wrote:
> On Thu, 16 Nov 2006, Daniel Walker wrote:
>
> > On Thu, 2006-11-16 at 16:35 +0100, Ingo Molnar wrote:
> >
> >> -rt0 is a rebase of -rt to 2.6.19-rc6, with lots of updates and fixes
> >> included. It includes the latest -hrt-dynticks tree and more.
> >
> >
> > Does the zero carry and meaning or did you just decide start using zero
> > instead of one?
> >
> > Daniel
>
> 0 bugs?
I already know there's a few. Should we start a known regression list?
Daniel
* Daniel Walker <[email protected]> wrote:
> [...] Should we start a known regression list?
please resend the bugs that still trigger for you with 2.6.19-rt0.
Ingo
On Thu, 2006-11-16 at 23:07 +0100, Ingo Molnar wrote:
> * Daniel Walker <[email protected]> wrote:
>
> > [...] Should we start a known regression list?
>
> please resend the bugs that still trigger for you with 2.6.19-rt0.
Did you look at the BKL reacquire issue I sent? Just looking over the
code briefly, it looks like it's still there.
Daniel
On Thu, 2006-11-16 at 16:35 +0100, Ingo Molnar wrote:
> cd /etc/yum.repos.d
> wget http://people.redhat.com/~mingo/realtime-preempt/rt.repo
> yum update kernel
I follow the instructions on my x86_64 with FC6, that you already know
(http://bugzilla.kernel.org/show_bug.cgi?id=6419#c47),
hangs on boot with or without notsc.
I would like try just the part of tglx (hrtimers dyntick)
cause PREEMPT part never works well on my computer (with spontaneous
reboots)
Thanks,
--
S?rgio M.B.
* Daniel Walker <[email protected]> wrote:
> On Thu, 2006-11-16 at 23:07 +0100, Ingo Molnar wrote:
> > * Daniel Walker <[email protected]> wrote:
> >
> > > [...] Should we start a known regression list?
> >
> > please resend the bugs that still trigger for you with 2.6.19-rt0.
>
> Did you look at the BKL reacquire issue I sent? Just looking over the
> code briefly, it looks like it's still there.
yeah, will do that. It's quite low-prio, evidently no-one in the past
couple of months even attempted to build a !PREEMPT_RT && !PREEMPT_BKL
(!) kernel.
Ingo
* Ingo Molnar <[email protected]> wrote:
>
> * Ingo Molnar <[email protected]> wrote:
>
> > > Did you look at the BKL reacquire issue I sent? Just looking over
> > > the code briefly, it looks like it's still there.
> >
> > yeah, will do that. It's quite low-prio, evidently no-one in the past
> > couple of months even attempted to build a !PREEMPT_RT && !PREEMPT_BKL
> > (!) kernel.
>
> doh - i have re-read your report and the problem should hit PREEMPT_RT
> too. I'm looking at it.
actually, it should only hit CONFIG_SPINLOCK_BKL, which is an option
no-one should be using these days. I'll disable that option for now.
Ingo
* Ingo Molnar <[email protected]> wrote:
> > Did you look at the BKL reacquire issue I sent? Just looking over
> > the code briefly, it looks like it's still there.
>
> yeah, will do that. It's quite low-prio, evidently no-one in the past
> couple of months even attempted to build a !PREEMPT_RT && !PREEMPT_BKL
> (!) kernel.
doh - i have re-read your report and the problem should hit PREEMPT_RT
too. I'm looking at it.
Ingo
* Ingo Molnar <[email protected]> wrote:
> actually, it should only hit CONFIG_SPINLOCK_BKL, which is an option
> no-one should be using these days. I'll disable that option for now.
i fixed it instead - fix should show up in 2.6.19-rt1.
Ingo
* Sergio Monteiro Basto <[email protected]> wrote:
> On Thu, 2006-11-16 at 16:35 +0100, Ingo Molnar wrote:
> > cd /etc/yum.repos.d
> > wget http://people.redhat.com/~mingo/realtime-preempt/rt.repo
> > yum update kernel
>
> I follow the instructions on my x86_64 with FC6, that you already know
> (http://bugzilla.kernel.org/show_bug.cgi?id=6419#c47),
> hangs on boot with or without notsc.
hm - could you try the -rt1 package i just uploaded? It fixes a boot
crash, amongst other bugfixes.
Ingo
On Thu, 2006-11-16 at 23:07 +0100, Ingo Molnar wrote:
> * Daniel Walker <[email protected]> wrote:
>
> > [...] Should we start a known regression list?
>
> please resend the bugs that still trigger for you with 2.6.19-rt0.
I'm working with the developers of the 64Studio distro who are
attempting to ship a stable -rt kernel so I have access to lots of good
bug reports. Oops on boot is by far the most common. I'll post details
once we've retested with 2.6.19-rt0.
Lee
* Lee Revell <[email protected]> wrote:
> On Thu, 2006-11-16 at 23:07 +0100, Ingo Molnar wrote:
> > * Daniel Walker <[email protected]> wrote:
> >
> > > [...] Should we start a known regression list?
> >
> > please resend the bugs that still trigger for you with 2.6.19-rt0.
>
> I'm working with the developers of the 64Studio distro who are
> attempting to ship a stable -rt kernel so I have access to lots of
> good bug reports. Oops on boot is by far the most common. I'll post
> details once we've retested with 2.6.19-rt0.
thanks, please do that. Right now i have no open boot-crash regression
left that i can reproduce.
Ingo
On Fri, 2006-11-17 at 17:17 +0100, Ingo Molnar wrote:
> * Lee Revell <[email protected]> wrote:
>
> > On Thu, 2006-11-16 at 23:07 +0100, Ingo Molnar wrote:
> > > * Daniel Walker <[email protected]> wrote:
> > >
> > > > [...] Should we start a known regression list?
> > >
> > > please resend the bugs that still trigger for you with 2.6.19-rt0.
> >
> > I'm working with the developers of the 64Studio distro who are
> > attempting to ship a stable -rt kernel so I have access to lots of
> > good bug reports. Oops on boot is by far the most common. I'll post
> > details once we've retested with 2.6.19-rt0.
>
> thanks, please do that. Right now i have no open boot-crash regression
> left that i can reproduce.
Should we pull in Steve's patch for these, or are you just grabbing
Jeff's tree? I noticed they aren't always commented "shut up gcc" .
--- linux.orig/arch/i386/kernel/efi.c
+++ linux/arch/i386/kernel/efi.c
@@ -271,7 +271,7 @@ void efi_memmap_walk(efi_freemem_callbac
struct range {
unsigned long start;
unsigned long end;
- } prev, curr;
+ } prev = { } /* shut up gcc */ , curr = { } /* shut up gcc */ ;
efi_memory_desc_t *md;
unsigned long start, end;
void *p;
On Fri, 2006-11-17 at 17:17 +0100, Ingo Molnar wrote:
> thanks, please do that. Right now i have no open boot-crash regression
> left that i can reproduce.
Possibly old news, but with 2.6.18-rt7 this user gets an Oops in
read_hpet() if high res timers are enabled.
http://ubuntuforums.org/showthread.php?t=292071
Lee
* Lee Revell <[email protected]> wrote:
> On Fri, 2006-11-17 at 17:17 +0100, Ingo Molnar wrote:
> > thanks, please do that. Right now i have no open boot-crash regression
> > left that i can reproduce.
>
> Possibly old news, but with 2.6.18-rt7 this user gets an Oops in
> read_hpet() if high res timers are enabled.
>
> http://ubuntuforums.org/showthread.php?t=292071
hm, that bug could still be around - does the patch below fix it? I've
uploaded -rt3 and soon there will be -rt3 rpms in the YUM repository
too.
Ingo
Index: linux/drivers/char/hpet.c
===================================================================
--- linux.orig/drivers/char/hpet.c
+++ linux/drivers/char/hpet.c
@@ -909,9 +909,7 @@ int hpet_alloc(struct hpet_data *hdp)
hpetp->hp_delta = hpet_calibrate(hpetp);
if (!hpet_clocksource_p) {
-#ifdef CONFIG_IA64
- clocksource_hpet.fsys_mmio_ptr = hpet_mc_ptr = &hpetp->hp_hpet->hpet_mc;
-#endif
+ hpet_mc_ptr = &hpetp->hp_hpet->hpet_mc;
clocksource_hpet.mult = clocksource_hz2mult(hpetp->hp_tick_freq,
clocksource_hpet.shift);
clocksource_register(&clocksource_hpet);
On Fri, 2006-11-17 at 10:22 +0100, Ingo Molnar wrote:
> * Sergio Monteiro Basto <[email protected]> wrote:
>
> > On Thu, 2006-11-16 at 16:35 +0100, Ingo Molnar wrote:
> > > cd /etc/yum.repos.d
> > > wget http://people.redhat.com/~mingo/realtime-preempt/rt.repo
> > > yum update kernel
> >
> > I follow the instructions on my x86_64 with FC6, that you already know
> > (http://bugzilla.kernel.org/show_bug.cgi?id=6419#c47),
> > hangs on boot with or without notsc.
>
> hm - could you try the -rt1 package i just uploaded? It fixes a boot
> crash, amongst other bugfixes.
2.6.18-1.0003.fc7rt4 boots without lost tickets in dmesg because use as
clocksource: acpi_pm , but boot without notsc option still hangs on
boot, with a long oops.
Thanks,
--
S?rgio M.B.
* Daniel Walker <[email protected]> wrote:
> [...] are you just grabbing Jeff's tree? I noticed they aren't always
> commented "shut up gcc" .
> - } prev, curr;
> + } prev = { } /* shut up gcc */ , curr = { } /* shut up gcc */ ;
i just do them by hand every time i hit one.
Ingo