From owner-freebsd-current Mon Sep 30 20:57:35 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 437F837B401; Mon, 30 Sep 2002 20:57:34 -0700 (PDT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07B5043E81; Mon, 30 Sep 2002 20:57:34 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id D34502A88D; Mon, 30 Sep 2002 20:57:29 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Juli Mallett Cc: "M. Warner Losh" , wa1ter@hotmail.com, freebsd-current@FreeBSD.ORG Subject: Re: World broken at libkvm In-Reply-To: <20020930195101.A64978@FreeBSD.org> Date: Mon, 30 Sep 2002 20:57:29 -0700 From: Peter Wemm Message-Id: <20021001035729.D34502A88D@canning.wemm.org> 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 Juli Mallett wrote: > * De: "M. Warner Losh" [ Data: 2002-09-30 ] > [ Subjecte: Re: World broken at libkvm ] > > In message: <3D98EF44.8070803@hotmail.com> > > walt writes: > > : cc -O -pipe -mcpu=pentiumpro -DLIBC_SCCS -I/usr/src/lib/libkvm -c > > : /usr/src/lib/libkvm/kvm_proc.c -o kvm_proc.o > > : /usr/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist': > > : /usr/src/lib/libkvm/kvm_proc.c:201: structure has no member named `p_sigl ist' > > > > This has been fixed. But there's other breakages in the kernel that > > are being worked on. > > And now fixed. All we have to look out for now is someone doing something > that exposes some sort of functional difference, but I don't anticipate it. Have you dealt with the 'could sleep' stuff with witness turned on? These are *guaranteed* panics if the system is low on memory at that given instant. (Witness doesn't cause the problems, it reports fundamental problems that are already there. The system will panic regardless of whether witness is there or not.) I suggest you turn WITNESS on, and stress the system. If you get *new* 'could sleep' stuff or other lock order problems, then there are still significant regressions to be fixed. The last thing we need during the 'please stabilize 5.0' drive is newly added problems. If other folks are seeing new ones, please report them here (not to me, I already get too much email :-]). Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message