From owner-freebsd-current Fri Oct 29 8:43:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by hub.freebsd.org (Postfix) with ESMTP id 7BED91521B for ; Fri, 29 Oct 1999 08:43:43 -0700 (PDT) (envelope-from brian@CSUA.Berkeley.EDU) Received: from smarter.than.nu (ida-89-77.Reshall.Berkeley.EDU [169.229.89.77]) by soda.CSUA.Berkeley.EDU (8.8.8/) via ESMTP id IAA15016; Fri, 29 Oct 1999 08:43:42 -0700 (PDT) env-from (brian@CSUA.Berkeley.EDU) Date: Fri, 29 Oct 1999 08:43:40 -0700 (PDT) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: Randy Bush Cc: FreeBSD Current Subject: Re: -stable to -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999, Randy Bush wrote: > o so build -current binary for config > o update kernel config file to -current > o config a -current kernel > o make a -current kernel > o install -current kernel > o reboot > o crash in init after configuring network, but was too fast to capture > o but i think that the last line of the boot tells the story, see below > > so what's the upgrade path? This sounds like its loading a kernel module (linux.ko perhaps?) built for 3-stable which isn't forwards compatible with the new kernel. Rebuild the modules and then try booting -current. If that doesn't fix it, consider building a debug kernel or booting with a serial console so you can capture the panic. -- Brian Buchanan brian@CSUA.Berkeley.EDU -------------------------------------------------------------------------- FreeBSD - The Power to Serve! http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message