From owner-freebsd-chat Wed Jan 8 22: 7:30 2003 Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEDC837B401; Wed, 8 Jan 2003 22:07:29 -0800 (PST) Received: from flavatown.mail.pas.earthlink.net (flavatown.mail.pas.earthlink.net [207.217.120.148]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D11E43F1E; Wed, 8 Jan 2003 22:07:29 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from stork (stork.mail.pas.earthlink.net [207.217.120.188]) by flavatown.mail.pas.earthlink.net (8.11.6+Sun/8.11.6) with ESMTP id h0963rf24148; Wed, 8 Jan 2003 22:03:53 -0800 (PST) Received: from pool0122.cvx40-bradley.dialup.earthlink.net ([216.244.42.122] helo=mindspring.com) by stork with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18WVmt-0003pT-00; Wed, 08 Jan 2003 22:03:32 -0800 Message-ID: <3E1D1013.632319C2@mindspring.com> Date: Wed, 08 Jan 2003 22:00:51 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: bmah@FreeBSD.org Cc: JacobRhoden , freebsd-chat@FreeBSD.org Subject: Re: Kernel panic on 4.7-STABLE to 5.0 RC2 upgrade. References: <3.0.32.20030108092801.01faf100@mail.wavefire.com> <3E1C708A.39A5CFE0@mindspring.com> <200301091020.34273.jrhoden@unimelb.edu.au> <3E1CD433.5666E908@mindspring.com> <200301090509.h0959eUp018743@intruder.bmah.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a40c9e35471aa313b6281ca0a7dc4f83b193caf27dac41a8fd350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org "Bruce A. Mah" wrote: > If memory serves me right, Terry Lambert wrote: > > It's actually much less of a problem, now that release engineering > > is done in P4, following a date tag. > > Only the 5.0 developer previews used P4. We still do branches in CVS > for releases. I know. The problem is a 5.0-RC2 (not 5.0-RELEASE) CDROM that can't be easily recreated so that the kernel panic that occurs during the upgrade process itself can be diagnosed. No tag == very hard to recreate an identical image, with the only change being the options DDB and BREAK_TO_DEBUGGER in the config file... One thing that would help is if the people who built the 5.0-RC2 ISO image would build another one, with those options (and symbols intact) on the kernel on the ISO floppy image used in a CDROM based boot. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message