Date: Wed, 08 Jan 2003 22:00:51 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: bmah@FreeBSD.org Cc: JacobRhoden <jrhoden@unimelb.edu.au>, freebsd-chat@FreeBSD.org Subject: Re: Kernel panic on 4.7-STABLE to 5.0 RC2 upgrade. Message-ID: <3E1D1013.632319C2@mindspring.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
"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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E1D1013.632319C2>