From owner-freebsd-bugs@FreeBSD.ORG Wed Feb 22 13:40:08 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C942516A420 for ; Wed, 22 Feb 2006 13:40:08 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29E4543D46 for ; Wed, 22 Feb 2006 13:40:08 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k1MDe7If008654 for ; Wed, 22 Feb 2006 13:40:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k1MDe7hF008653; Wed, 22 Feb 2006 13:40:07 GMT (envelope-from gnats) Date: Wed, 22 Feb 2006 13:40:07 GMT Message-Id: <200602221340.k1MDe7hF008653@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: =?ISO-8859-15?Q?Bj=F6rn_K=F6nig?= Cc: Subject: Re: misc/91719: BZ2_bzDecompress returned -3 error on loading bzipped kernel X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?ISO-8859-15?Q?Bj=F6rn_K=F6nig?= List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Feb 2006 13:40:08 -0000 The following reply was made to PR misc/91719; it has been noted by GNATS. From: =?ISO-8859-15?Q?Bj=F6rn_K=F6nig?= To: bug-followup@FreeBSD.org, linimon@freebsd.org, ruben.kerkhof@gmail.com Cc: Subject: Re: misc/91719: BZ2_bzDecompress returned -3 error on loading bzipped kernel Date: Wed, 22 Feb 2006 14:31:58 +0100 I slimmed the loader by removing some fs_ops from src/sys/boot/i386/loader/conf.c that are unnecessary for pxeboot and disabled Forth support. Under these preconditions there will be finally enough memory available to decompress a "bzip2 -1"-compressed kernel. However this might be a i386-specific problem nevertheless. I'm not aware of other architectures, but it could be that this memory related problem concerns i386 only due to architecture conditioned restrictions. Björn