From owner-freebsd-current Fri May 10 04:07:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA10163 for current-outgoing; Fri, 10 May 1996 04:07:22 -0700 (PDT) Received: from uucp.DK.net (uucp@uucp.DK.net [193.88.44.47]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA10155 for ; Fri, 10 May 1996 04:07:18 -0700 (PDT) Received: from pingnet (uucp@localhost) by uucp.DK.net (8.6.12/8.6.12) with UUCP id NAA11344; Fri, 10 May 1996 13:06:52 +0200 Received: from kyklopen by ic1.ic.dk with UUCP id AA10523 (5.65c8/IDA-1.4.4j); Fri, 10 May 1996 13:02:28 +0200 Received: (from staff@localhost) by kyklopen.ping.dk (8.7.5/8.7.3) id MAA15516; Fri, 10 May 1996 12:54:38 +0200 (MET DST) Date: Fri, 10 May 1996 12:54:33 +0200 (MET DST) From: Thomas Sparrevohn To: Christopher Yap Cc: Poul-Henning Kamp , freebsd-current@freefall.freebsd.org Subject: Re: Rebooting problem solved (NOT) In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Charset: ISO_8859-1 X-Char-Esc: 29 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 9 May 1996, Christopher Yap wrote: > > On Thu, 09 May 1996 20:37:53 +0000 Poul-Henning Kamp > wrote: > > Not for me. The 32 MB box still craps after installing > the new locore.s. I'm now rebuilding without > BOUNCE_BUFFERS ... > Unfortunately i can't reproduce it any longer all of my test kernel now boots. But i think we might have two different bugs here. You seem to be able to get the kernel up and running but it panics and then the bug i was speaking of where the kernel never even gets up because the first access to the data area triggers a double fault. If you are able to produce a kernel panic. Then try produce a debug kernel dump with the dumpon command and save core. The handbook contains a nice description of how to do this in case you hav'nt done before. Regards Thomas