Native preemption is the culprit [was Re: today's CURRENT lockups]

[Ulrich Spoerlein]

On Sat, 10.07.2004 at 15:06:20 +0800, Ariff Abdullah wrote:
> I'm suspecting bad combination between threaded apps and current
> native preemption, either the preemption itself, or threads. Running
> current kernel without any threaded apps turns up nothing suspicious.
> Once the threaded apps started, it's like sending the entire system to
> the death row.
> 
> I'm reverting following files to pre-July 2 to achive solid stability:
> 
>  sys/sys/interrupt.h          - v1.27
>  sys/kern/kern_intr.c         - v1.110
>  sys/i386/i386/intr_machdep.c - v1.6
>  sys/kern/sched_ule.c         - v1.109

I tried to upgrade my kernel from 5.2.1 to -CURRENT and cvsupped
post-preemption. Running a UP-Kernel on a UP-Machine with either
SCHED_ULE or SCHED_BSD froze the machine under heavy load. It doesn't
survive a buildworld or a medium port-build.

I tried the revisions above and the machine no longer freezes under
load, but does an instant reboot :(

Is the machine expected to crash/freeze when running a -CURRENT kernel
on a 5.2R userland? I don't wanna installworld unless I get a rock-solid
kernel, that's in sync with it.

Ulrich Spoerlein
-- 
PGP Key ID: F0DB9F44				Get it while it's hot!
PGP Fingerprint: F1CE D062 0CA9 ADE3 349B  2FE8 980A C6B5 F0DB 9F44
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."	-- Benjamin Franklin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20040712/8e968440/attachment.bin