From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 15 23:05:00 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D643E98E; Tue, 15 Jan 2013 23:05:00 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id AFAEFAC; Tue, 15 Jan 2013 23:05:00 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.5/8.14.5) with ESMTP id r0FN50HN062529; Tue, 15 Jan 2013 16:05:00 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r0FN4w1k003937; Tue, 15 Jan 2013 16:04:58 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) Subject: Re: kgzip(1) is broken From: Ian Lepore To: dteske@freebsd.org In-Reply-To: <09b701cdf367$12737530$375a5f90$@freebsd.org> References: <09b701cdf367$12737530$375a5f90$@freebsd.org> Content-Type: text/plain; charset="us-ascii" Date: Tue, 15 Jan 2013 16:04:58 -0700 Message-ID: <1358291098.32417.134.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jan 2013 23:05:00 -0000 On Tue, 2013-01-15 at 13:27 -0800, dteske@freebsd.org wrote: > Hello, > > I have been sad of-late because kgzip(1) no longer produces a usable kernel. > > All versions of 9.x suffer this. > > And somewhere between 8.3-RELEASE-p1 and 8.3-RELEASE-p5 this recently broke in > the 8.x series. > > I haven't tried the 7 series lately, but if whatever is making the rounds gets > MFC'd that far back, I expect the problem to percolate there too. > > The symptom is that the machine reboots immediately and unexpectedly the moment > the kernel is executed by the loader. > > This is quite troubling and I am looking for someone to help find the culprit. I > don't know where to start looking. Here are some possible candidates from the things that were MFC'd to 8 in that timeframe. I haven't looked at what these do, they're just changes that affect files related to booting. r233211 r233377 r233469 r234563 -- Ian