From owner-freebsd-current Mon Jul 8 17:39:56 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 454F137B400 for ; Mon, 8 Jul 2002 17:39:53 -0700 (PDT) Received: from warez.scriptkiddie.org (uswest-dsl-142-38.cortland.com [209.162.142.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id A902C43E54 for ; Mon, 8 Jul 2002 17:39:52 -0700 (PDT) (envelope-from lamont@scriptkiddie.org) Received: from [192.168.69.11] (unknown [192.168.69.11]) by warez.scriptkiddie.org (Postfix) with ESMTP id BFE3662D1A; Mon, 8 Jul 2002 17:39:51 -0700 (PDT) Date: Mon, 8 Jul 2002 17:45:54 -0700 (PDT) From: Lamont Granquist To: Josef Karthauser Cc: Julian Elischer , FreeBSD current users Subject: Re: KSE M-III status & junior hacker project. In-Reply-To: <20020707104638.GP2813@genius.tao.org.uk> Message-ID: <20020708174405.L5032-100000@coredump.scriptkiddie.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 7 Jul 2002, Josef Karthauser wrote: > On Sat, Jul 06, 2002 at 04:57:08PM -0700, Julian Elischer wrote: > > Well with various hints from here and there I have fixed > > the ^Z/fg problem (at least it seems fixed to me and others that > > have tested) This basically leaves only one outstanding > > problem that I know of which is a problem that Warner has with a > > particular progam. (This may also be fixed but I don't know) > > > > If anyone knows of something that was broken by the KSE commit, > > (i.e. it worked just before and not after) and is STILL > > broken please let me know because I think I can pretty much declare that > > chapter finished, and I'd like to get on with "extending" KSE > > functionality. This will be the start of Milestone IV, which would be > > add support for threads to run on multiple processors. > > Coincident with that some work should also proceed on gradually > > identifying and cleaning up places in the kernel where multithreading > > is just not ready.. e.g. which thread status do you get when you type ^T? > > I've absolutely no idea what's causing it, but I'm still having random reboots > of current after some uptime with no dumps. I'll install a new kernel > today and report back if it still happens. Maybe someone can help me to > track it down. I'm having problems like that every 1-3 days, but my build is pre-KSE-III (post-gcc-3.1 though). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message