From owner-freebsd-current Tue May 7 19:14:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA10716 for current-outgoing; Tue, 7 May 1996 19:14:28 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA10711 for ; Tue, 7 May 1996 19:14:25 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id TAA11303; Tue, 7 May 1996 19:13:44 -0700 (PDT) To: Eric Chet cc: ejc@nasvr1.cb.att.com, freebsd-current@freebsd.org Subject: Re: -current not booting In-reply-to: Your message of "Tue, 07 May 1996 20:26:01 EDT." Date: Tue, 07 May 1996 19:13:44 -0700 Message-ID: <11301.831521624@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It may also be something to do with phk's changes to locore.s. I don't know, there are so many variables! Would it be possible for you to grab a copy of the CVS tree and roll back /sys until you get a working kernel again? That would definitely help us to figure out *when* the problem crept in. Thanks! Jordan > > Very strange, since my kernels have been booting for days. Are you > > sure this isn't a source corruption or syncronization problem? > > > > Jordan > > > Jordan > It could be a corruption or sync problem. But one of my > co-workers is having the same problem, also somebody on the net stated > the same problem. It's no trouble for me to resup everything, so > I will give it a try. > > Eric >