From owner-freebsd-alpha Tue Mar 27 12:48:31 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 5391337B718; Tue, 27 Mar 2001 12:48:26 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id PAA18263; Tue, 27 Mar 2001 15:48:25 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2RKltk70596; Tue, 27 Mar 2001 15:47:55 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15040.64635.737475.157879@grasshopper.cs.duke.edu> Date: Tue, 27 Mar 2001 15:47:55 -0500 (EST) To: John Baldwin Cc: obrien@FreeBSD.ORG, alpha@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: dump(8) (vfs_object_create() panics: found the problem) In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Baldwin writes: > overhaul commits of March 11. Removing 'device random' from my kernel gets rid > of the panic but breaks ssh. :( A kernel just before the Mar 11 /dev/random > commits boots fine, and one just after panics. :( Hopefully Mark can trace > down where the data corruption is coming from. I'm willing to test any patches. Removing the random device from the kernel does not fix the signal (dump, etc) segv problems. Darn. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message