From owner-freebsd-alpha Wed Jan 24 6:41: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 2C6BC37B400; Wed, 24 Jan 2001 06:41:14 -0800 (PST) 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 JAA15810; Wed, 24 Jan 2001 09:41:12 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f0OEfCm17312; Wed, 24 Jan 2001 09:41:12 -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 Date: Wed, 24 Jan 2001 09:41:11 -0500 (EST) To: John Baldwin Cc: Bernd Walter , freebsd-alpha@FreeBSD.ORG Subject: RE: -current failing on PC164 In-Reply-To: References: <20010123214322.A26643@cicely5.cicely.de> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14958.59036.411197.382347@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Baldwin writes: > > > A test kernel with some of my changes in it died with a pmap_emulate > error. When I disabled all debugging options, removed things like > INET6, gif, faith, usb, etc., I got a kernel that booted and ran ok. > It looks like we are having a problem with kernels over 4meg possibly. > Thre have been reports of similar problems on i386 as well. Bernd's problem was an unaligned access error, probably in the witness or mutex debug code. This (probably) has nothing to do with pmap problems. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message