From owner-freebsd-current Sun May 10 23:59:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA22650 for freebsd-current-outgoing; Sun, 10 May 1998 23:59:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA22631 for ; Sun, 10 May 1998 23:59:21 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id BAA02117; Mon, 11 May 1998 01:59:15 -0500 (EST) (envelope-from toor) Message-Id: <199805110659.BAA02117@dyson.iquest.net> Subject: Re: Latest kernel instability In-Reply-To: <199805110647.XAA00280@mordred.cs.ucla.edu> from Scott Michel at "May 10, 98 11:47:02 pm" To: scottm@CS.UCLA.EDU (Scott Michel) Date: Mon, 11 May 1998 01:59:15 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Scott Michel said: > FWIW John, your latest updates cause wild sig 11's and sig 8's in > a kernel cvsup'd from ~9pm Pacific. Had to back out to the previous. > > And yes, this was after a 'bake world'. procfs and mfs as LKMs cause > mount to sig 11 immediately. Eventually everything else starts to > sig 11. > When telling me things like this *please* let me know the kind of machine that you are working with, and also maybe a kernel config file and dmesg output. I have been running practically this same thing on both P5, AMD and P6 machines, at work and at home for the last week. The more info the better. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message