From owner-freebsd-current@FreeBSD.ORG Sat Apr 26 12:23:43 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 044F2106566C for ; Sat, 26 Apr 2008 12:23:43 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id EC4BC8FC20 for ; Sat, 26 Apr 2008 12:23:42 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (unknown [208.65.91.234]) by elvis.mu.org (Postfix) with ESMTP id 5F72B1A4D8C; Sat, 26 Apr 2008 05:23:42 -0700 (PDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Sat, 26 Apr 2008 08:22:47 -0400 User-Agent: KMail/1.9.7 References: <200804252320.39121.naylor.b.david@gmail.com> In-Reply-To: <200804252320.39121.naylor.b.david@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200804260822.47763.jhb@freebsd.org> Cc: David Naylor Subject: Re: boot failed with gzip'ed modules X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Apr 2008 12:23:43 -0000 On Friday 25 April 2008 05:20:34 pm David Naylor wrote: > Hi, > > I have a live CD that has a GENERIC kernel and that loads some modules > before booting. They have been gzip'ed to save space however suddenly the > booting has stopped. The kernel loads and then after the first line of > the modules to load it stops: I've seen reports of problems with gzip'd modules on 7.0. You'll probably have to add debugging or look at the diffs between 6.3 and 7.0 of the boot code (sys/boot and lib/libstand) to narrow down things to try. (For example, did moving malloc up above 1MB break it somehow.) > Oh, on an aside. What is the BTX and why is the bootloader i386 even for > an amd64 system (I suspect it is because there is no need for an amd64 > bootloader [unless kernels and modules suddenly exceed 4GB 8-/ ])? 1) BTX is a mini-kernel that the boot code uses. This lets us write the boot loader as a 32-bit app in C rather than assembly. 2) Yes, the amd64 code uses the i386 bootstrap. amd64 CPUs start up in real mode just like i386 and you can't easily call the BIOS from long mode anyway, so a different bootstrap for amd64 would be rather gratuitous. -- John Baldwin