From owner-freebsd-current Sun May 10 23:48:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21462 for freebsd-current-outgoing; Sun, 10 May 1998 23:48:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailman.cs.ucla.edu (Mailman.CS.UCLA.EDU [131.179.128.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA21276 for ; Sun, 10 May 1998 23:47:13 -0700 (PDT) (envelope-from scottm@mordred.cs.ucla.edu) Received: from mordred.cs.ucla.edu (mordred.cs.ucla.edu [131.179.48.34]) by mailman.cs.ucla.edu (8.8.8/UCLACS-4.0) with ESMTP id XAA07359 for ; Sun, 10 May 1998 23:47:01 -0700 (PDT) Received: (from scottm@localhost) by mordred.cs.ucla.edu (8.8.8/8.8.8) id XAA00280 for freebsd-current@freebsd.org; Sun, 10 May 1998 23:47:02 -0700 (PDT) (envelope-from scottm) Date: Sun, 10 May 1998 23:47:02 -0700 (PDT) From: Scott Michel Message-Id: <199805110647.XAA00280@mordred.cs.ucla.edu> To: freebsd-current@FreeBSD.ORG Subject: Latest kernel instability Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. -scooter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message