Anyone following the FreeBSD -current mailing list lately has seen a rash of emails regarding the recent KSE-MIII merge [earlier story]. Julian Elischer offered a status report, pointing out the largest remaining problem was related to a userland library that he didn't touch, "A libc_r imported from a system that is not yet upgraded to have KSE sources works fine. A libc_r from a KSE machine will not work correctly on the KSE machine or the pre-KSE machine."

This problem was later resolved by rolling back to earlier versions of queue.h and proc.h. Developers are now focused on signal handling issues evidently introduced by the KSE merge. In other words, -current is quickly restabalizing after the introduction of Kernel Scheduled Entities.

From: Julian Elischer
To: FreeBSD Current Users
Subject: KSE status report
Date: Tue, 2 Jul 2002 01:57:39 -0700 (PDT)

Ok so Usability for the average command line user is
very good. David Xu tracked down a problem that was 
eluding me with SMP machines. Matt is tracking down
something that may be giving some instability
but may also be related to what David found.
He however gets the award for most confusing 
debug messages when he managed to get both of his CPUs
to enter teh debugger at the same time. I thought that was
impossible, but it definitly happenned. (or it certainly
looked that way to me :-)

The big problem at the moment is that something in the 
source tree as a whole, and probably something that came in with KSE
is stopping us from successfully compiling a working libc_r.
(a bit ironic really).

A libc_r imported from a system that is not yet upgraded to have 
KSE sources works fine. A libc_r from a KSE machine
will not work correctly on the KSE machine or the pre-KSE machine.

The sources are identical, so some thing else in the tree must be
influencing its correctness.

the result of this problem is that KDE and Gnome apps that
are linked with a libc_r created on this system don't work.

The test directory in the libc sources is giving me some avenues to
work on but I must say, given allthe things that could have gone wrong
in the kernel, I'm surprised that the largest problem seems to
have come from a userland library that I haven't touched :-/

julian



From: Julian Elischer
Subject: Re: KSE status report
Date: Tue, 2 Jul 2002 02:07:07 -0700 (PDT)

BTW feel free to spend some time helping try figire out why libc_r
is bombing out. It's not an exclusive club :-)



From: Ian Dowse
Subject: Re: KSE status report 
Date: Tue, 02 Jul 2002 11:06:09 +0100

In message, Julian Elischer writes:
>The big problem at the moment is that something in the 
>source tree as a whole, and probably something that came in with KSE
>is stopping us from successfully compiling a working libc_r.
>(a bit ironic really).

Is the new

	(elm)->field.tqe_next = (void *)-1;

in TAILQ_REMOVE a likely candidate? That could easily tickle old
bugs in other code. The libc_r code does use a lot of TAILQ macros.

Ian



From: Julian Elischer
Subject: Re: KSE status report 
Date: Tue, 2 Jul 2002 09:14:26 -0700 (PDT)

Good idea.

Unforunatly someone tried to complie a libc_r with the old queue.h and it
had the same problem (or so they said).



From: Wesley Morgan
Subject: Re: KSE status report
Date: Tue, 2 Jul 2002 15:51:00 -0400 (EDT)

After reading this... I got to thinking, and I copied the old headers into
the wrong place. After rebuilding, it works fine :)... That's what I get
for doing it at 2am! My fault, you guys could have fixed this almost
immediately except for some bad info from me.



From: Julian Elischer
Subject: Re: KSE status report
Date: Tue, 2 Jul 2002 13:07:55 -0700 (PDT)

ok, so you are saying that GNOME stuff works fine?
What do yuo have running and is there still anything that does the wrong
thing?



From: Wesley Morgan
Subject: Re: KSE status report
Date: Tue, 2 Jul 2002 16:34:50 -0400 (EDT)

KDE is working fine. GIMP & GNUCash are the only two "gnome" apps I am
using, and they both work. "Everybuddy" now works... In short, it all
seems to work. I am using rev 1.225 of proc.h and 1.48 of queue.h. Last
cvsup was Jul 1 17:13 MDT.



From: Julian Elischer
Subject: Re: KSE status report
Date: Tue, 2 Jul 2002 13:42:23 -0700 (PDT)

On Tue, 2 Jul 2002, Wesley Morgan wrote:

> KDE is working fine. GIMP & GNUCash are the only two "gnome" apps I am
> using, and they both work. "Everybuddy" now works... In short, it all
> seems to work. I am using rev 1.225 of proc.h and 1.48 of queue.h. Last
> cvsup was Jul 1 17:13 MDT.
ok so cen you bring those two files back into sync,
and then recompile libc_r?
(uh, and reinstall it..)

thats 1.52 ow queue.h and 1.226 of proc.h

Hopefully  the last commit fixed it..



From: Joe Marcus Clarke
Subject: Re: KSE status report
Date: 02 Jul 2002 17:17:05 -0400

On Tue, 2002-07-02 at 16:07, Julian Elischer wrote:
> ok, so you are saying that GNOME stuff works fine?
> What do yuo have running and is there still anything that does the wrong
> thing?

I just did an update of -CURRENT about 4 hours ago, and everything in
GNOME works fine except nautilus.  Nautilus hangs indefinitely taking up
almost all of the CPU.  Once it's killed, other GNOME apps respond
again.  This is -CURRENT kernel+world minus your recent queue.h commit.

I can get a back trace if you'd like.

Joe



From: Joe Marcus Clarke
Subject: Re: KSE status report
Date: 02 Jul 2002 19:36:52 -0400

On Tue, 2002-07-02 at 16:42, Julian Elischer wrote:
> 
> 
> On Tue, 2 Jul 2002, Wesley Morgan wrote:
> 
> > KDE is working fine. GIMP & GNUCash are the only two "gnome" apps I am
> > using, and they both work. "Everybuddy" now works... In short, it all
> > seems to work. I am using rev 1.225 of proc.h and 1.48 of queue.h. Last
> > cvsup was Jul 1 17:13 MDT.
> ok so cen you bring those two files back into sync,
> and then recompile libc_r?
> (uh, and reinstall it..)
> 
> thats 1.52 ow queue.h and 1.226 of proc.h
> 
> Hopefully  the last commit fixed it..

After rebuilding world and kernel on the latest queue.h, the nautilus
problem is solved.

Joe