From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 16 00:10:05 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 D5EDB405; Wed, 16 Jan 2013 00:10:05 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id A697D761; Wed, 16 Jan 2013 00:10:05 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.16]) by ltcfislmsgpa04.fnfis.com (8.14.5/8.14.5) with ESMTP id r0G09vTs030606 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 15 Jan 2013 18:09:57 -0600 Received: from dtwin (10.14.152.6) by smtp.fisglobal.com (10.132.206.16) with Microsoft SMTP Server (TLS) id 14.2.309.2; Tue, 15 Jan 2013 18:09:56 -0600 From: Devin Teske To: , "'Ian Lepore'" References: <09b701cdf367$12737530$375a5f90$@freebsd.org> <1358291098.32417.134.camel@revolution.hippie.lan> <0a0001cdf375$60ddbc40$229934c0$@freebsd.org> In-Reply-To: <0a0001cdf375$60ddbc40$229934c0$@freebsd.org> Subject: RE: kgzip(1) is broken Date: Tue, 15 Jan 2013 16:10:40 -0800 Message-ID: <0a2301cdf37d$ebe705a0$c3b510e0$@fisglobal.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQEm08A5EfxbuxwhGQZ5y0RK5HyMsQIlPdpzAkHCD8uZdhJgUA== Content-Language: en-us X-Originating-IP: [10.14.152.6] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.9.8327, 1.0.431, 0.0.0000 definitions=2013-01-15_07:2013-01-15,2013-01-15,1970-01-01 signatures=0 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: Wed, 16 Jan 2013 00:10:05 -0000 > -----Original Message----- > From: Devin Teske [mailto:devin.teske@fisglobal.com] On Behalf Of > dteske@freebsd.org > Sent: Tuesday, January 15, 2013 3:10 PM > To: 'Ian Lepore' > Cc: freebsd-hackers@freebsd.org; dteske@freebsd.org > Subject: RE: kgzip(1) is broken > > > > > -----Original Message----- > > From: Ian Lepore [mailto:freebsd@damnhippie.dyndns.org] > > Sent: Tuesday, January 15, 2013 3:05 PM > > To: dteske@freebsd.org > > Cc: freebsd-hackers@freebsd.org > > Subject: Re: kgzip(1) is broken > > > > 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 > > > > Thanks Ian! > > I'll test each one individually to see if regressing any one (or all) addresses > the problem. Progress... Looks like I found the culprit. Turns out it's a back-ported bxe(4) driver (back-ported from 9 -- where kgzip seems to never work). I wonder why back-porting bxe(4) from stable/9 to releng/8.3 would cause kgzip to produce non-working kernels. I'm emailing the maintainers (davidch + other Broadcom folk) -- Devin _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.