Skip to contentSkip to conversation

2.6.19-rc6-rt0, -rt YUM repository

DISCUSSION Ingo Molnar 5 participants 20 messages Nov 16, 2006 – Nov 21, 2006

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

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

#1 lore raw
Quoted 2 lines · Ingo Molnar

-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

#2 lore raw
Quoted 5 lines · Daniel Walker
Quoted 2 lines

-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

#3 lore raw
In reply to Daniel Walker
Quoted 10 lines · Daniel Walker
Quoted 2 lines · Ingo Molnar

-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

#4 lore raw
Quoted 8 lines · Esben Nielsen
Quoted 6 lines · Daniel Walker
Quoted 2 lines · Ingo Molnar

-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.

Quoted 6 lines
Quoted 4 lines

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

#5 lore raw
Quoted 1 line · Daniel Walker

[...] Should we start a known regression list?

please resend the bugs that still trigger for you with 2.6.19-rt0.

Ingo

#6 lore raw
Quoted 5 lines · Ingo Molnar
Quoted 1 line · Daniel Walker

[...] 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

#17 lore raw
In reply to Ingo Molnar
Quoted 3 lines · Ingo Molnar

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,

Signature · 1 line
Sérgio M.B.
#7 lore raw
In reply to Daniel Walker
Quoted 9 lines · Daniel Walker
Quoted 5 lines · Ingo Molnar
Quoted 1 line · Daniel Walker

[...] 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

#9 lore raw
In reply to Ingo Molnar
Quoted 6 lines · Ingo Molnar
Quoted 3 lines · Ingo Molnar
Quoted 2 lines

Did you look at the BKL reacquire issue I sent? Just looking over the code briefly, it looks like it's still there.

Quoted 6 lines
Quoted 3 lines

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

#8 lore raw
In reply to Ingo Molnar
Quoted 6 lines · Ingo Molnar
Quoted 2 lines

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

#10 lore raw
In reply to Ingo Molnar
Quoted 2 lines · Ingo Molnar

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

#18 lore raw
In reply to Sergio Monteiro Basto
Quoted 8 lines · Sergio Monteiro Basto
Quoted 3 lines · Ingo Molnar

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

#11 lore raw
In reply to Ingo Molnar
Quoted 5 lines · Ingo Molnar
Quoted 1 line · Daniel Walker

[...] 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

#12 lore raw
Quoted 11 lines · Lee Revell
Quoted 5 lines · Ingo Molnar
Quoted 1 line · Daniel Walker

[...] 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

#13 lore raw
Quoted 9 lines · Ingo Molnar
Quoted 7 lines · Lee Revell
Quoted 5 lines · Ingo Molnar
Quoted 1 line · Daniel Walker

[...] Should we start a known regression list?

please resend the bugs that still trigger for you with 2.6.19-rt0.

Quoted 7 lines
Quoted 4 lines

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" .

arch/i386/kernel/efi.c +1 -1
@@ -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;
#16 lore raw
Quoted 8 lines · Lee Revell
Quoted 2 lines · Ingo Molnar

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

drivers/char/hpet.c +1 -3
Index: 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);
#19 lore raw
In reply to Ingo Molnar
Quoted 7 lines · Ingo Molnar
Quoted 5 lines · Sergio Monteiro Basto
Quoted 3 lines · Ingo Molnar

cd /etc/yum.repos.d
wget http://people.redhat.com/~mingo/realtime-preempt/rt.repo
yum update kernel

Quoted 6 lines
Quoted 3 lines

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,

Signature · 1 line
Sérgio M.B.
#14 lore raw
In reply to Daniel Walker

arch/i386/kernel/efi.c void efi_memmap_walk(efi_freemem_callbac · line 274

Quoted 5 lines · Daniel Walker

[...] are you just grabbing Jeff's tree? I noticed they aren't always commented "shut up gcc" .

arch/i386/kernel/efi.c +1 -1
-       } prev, curr;
+       } prev = { } /* shut up gcc */ , curr = { } /* shut up gcc */ ;

i just do them by hand every time i hit one.

Ingo