From owner-freebsd-current Fri May 10 04:35:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA11185 for current-outgoing; Fri, 10 May 1996 04:35:38 -0700 (PDT) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA11180 for ; Fri, 10 May 1996 04:35:36 -0700 (PDT) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0uHqTp-0003w0C; Fri, 10 May 96 04:35 PDT Received: from localhost (localhost [127.0.0.1]) by critter.tfs.com (8.7.5/8.6.12) with SMTP id LAA01898; Fri, 10 May 1996 11:35:19 GMT X-Authentication-Warning: critter.tfs.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Thomas Sparrevohn cc: Christopher Yap , freebsd-current@freefall.freebsd.org Subject: Re: Rebooting problem solved (NOT) In-reply-to: Your message of "Fri, 10 May 1996 12:54:33 +0200." Date: Fri, 10 May 1996 11:35:19 +0000 Message-ID: <1896.831728119@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > 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. Well, that access would come significantly later depending on the exact size of you kernels text section. If it doesn't come back then it's fixed :-) -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so.