From owner-freebsd-current Sun Jul 7 3:47:16 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 7146737B400 for ; Sun, 7 Jul 2002 03:47:10 -0700 (PDT) Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA16843E09 for ; Sun, 7 Jul 2002 03:47:09 -0700 (PDT) (envelope-from joe@tao.org.uk) Received: by tao.org.uk (Postfix, from userid 100) id 72689A8; Sun, 7 Jul 2002 11:46:38 +0100 (BST) Date: Sun, 7 Jul 2002 11:46:38 +0100 From: Josef Karthauser To: Julian Elischer Cc: FreeBSD current users Subject: Re: KSE M-III status & junior hacker project. Message-ID: <20020707104638.GP2813@genius.tao.org.uk> Mail-Followup-To: Josef Karthauser , Julian Elischer , FreeBSD current users References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.99i 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 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. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message