From owner-freebsd-questions@FreeBSD.ORG Thu Jul 1 07:48:25 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24ED016A4CE for ; Thu, 1 Jul 2004 07:48:25 +0000 (GMT) Received: from mail.u4eatech.com (blackhole.u4eatech.com [195.188.241.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id F143543D1D for ; Thu, 1 Jul 2004 07:48:23 +0000 (GMT) (envelope-from richard.williamson@u4eatech.com) Received: by mail.u4eatech.com (Postfix, from userid 503) id D9DF3360468; Thu, 1 Jul 2004 08:48:13 +0100 (BST) Received: from apus.u4eatech.com (apus.degree2.com [172.30.40.129]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by mail.u4eatech.com (Postfix) with ESMTP id 8CBD3360458; Thu, 1 Jul 2004 08:48:10 +0100 (BST) Message-Id: <6.1.1.1.2.20040701083638.027e4310@cygnus> X-Sender: richard@cygnus X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1 Date: Thu, 01 Jul 2004 08:43:53 +0100 To: epilogue , freebsd-questions@freebsd.org From: "Richard P. Williamson" In-Reply-To: <20040630122433.27d99453@localhost> References: <6.1.1.1.2.20040630135552.0a8deff8@cygnus> <20040630122433.27d99453@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mail X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.63 Subject: Re: failing to boot from mfsroot.gz X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2004 07:48:25 -0000 At 17:24 30/06/2004. epilogue had this to say: >On Wed, 30 Jun 2004 14:11:07 +0100 >"Richard P. Williamson" wrote: > >> Hello all, >> >> I have a 4.8 system that booted from flash using a kernel.gz and >> mfsroot.gz. The ethernet parts were not fully supported by the fxp driver >> in 4.8, so I was testing 4.10 to see if they were with that version of >> the OS. >> >> I've replace the kernel.gz with a 4.10 version, and the mfsroot.gz >> is built using 4.10 objects. If I try to boot it, this is what I >> get: >> >> ... >> md0: Preloaded mfs_root "/mfsroot> 50331648 bytes at 0xc02b2794 >> md1: malloc disk >> ... >> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 in isa0 >> sio0: type 16550A, console >> sio1 at port 0x2f8-0x2ff irq 3 on isa0 >> sio1: type 16550A >> vga0: at port 0x3b0-0x3bb iomem 0xb0000-0xb7ffff on >> isa0 ad0: 30MB [490/4/32] at ata0-master PI01 >> Mounting root from ufs:/dev/md0c >> >> And then nothing. Nada. Zip. >> >> No kernel panic message, no prompt, nothing. >> >> Which leaves me in a bit of a pickle as to what to try. >> >> If I use a 4.10 kernel with a 4.8 mfsroot.gz, it boots, >> but tells me that proc is out of sync with the kernel. > >If i get you correctly, you're trying to run a 4.10 kernel on a 4.8 >system. (?) That'd be stoopid. No, I'm trying to run a 4.10 kernel with a 4.10 mfsroot.gz. But nothing happens. The kernel inflates the mfsroot.gz into md0, configures itself, and then attempts to mount the root filesystem on /dev/md0c . And then that's it. No further messages on the console, no panic, no nothing. When I run a 4.8 kernel with a 4.8 system, all ok. When I (accidently) ran the 4.10 kernel with the 4.8 mfsroot.gz, it ran (marginally), while complaining about things like proc size mismatch. But it did come up. >if i've misunderstand your intention, apologies. no worries. My second paragraph may have been unclear ;> What I'm looking for is 'debug methodologies', ie what can I do to try and trace where it is falling over. Assume I'm limited to printf. Is there any way to enable bizarre debugging support in the booting kernel, on a headless, embedded device... Thanks for responding, rip