From nobody  Fri Jul 24 06:14:35 1998
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA04160;
          Fri, 24 Jul 1998 06:14:35 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199807241314.GAA04160@hub.freebsd.org>
Date: Fri, 24 Jul 1998 06:14:35 -0700 (PDT)
From: philipv@cs.mun.ca
To: freebsd-gnats-submit@freebsd.org
Subject: Core dump during 2.2.6 -> 2.2.7 upgrade.
X-Send-Pr-Version: www-1.0

>Number:         7390
>Category:       i386
>Synopsis:       Core dump during 2.2.6 -> 2.2.7 upgrade.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    jkh
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jul 24 06:20:00 PDT 1998
>Closed-Date:    Mon Sep 7 20:03:26 PDT 1998
>Last-Modified:  Mon Sep  7 20:05:03 PDT 1998
>Originator:     Philip van Ulden
>Release:        2.2.6
>Organization:
Memorial University
>Environment:
FreeBSD zeus 2.2.6-RELEASE FreeBSD 2.2.6-RELEASE #0: Tue Jul 14 19:38:53 NDT 1998     philipv@zeus:/usr/src/sys/compile/ZEUS  i386
>Description:
After a custom distribution set was installed while running
a remote upgrade from 2.2.6 to 2.2.7 the following happened:

Saving any boot -c changes to new kernel...Memory fault (core dumped)

The same thing occured when an attempt was made to upgrade again.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->jkh 
Responsible-Changed-By: phk 
Responsible-Changed-When: Mon Jul 27 06:16:25 PDT 1998 
Responsible-Changed-Why:  
over to the release engineer 
State-Changed-From-To: open->closed 
State-Changed-By: jkh 
State-Changed-When: Mon Sep 7 20:03:26 PDT 1998 
State-Changed-Why:  
I cannot reproduce this, nor is there enough information about 
the supplied failure (no stack trace, just indication that it died) 
to debug dset even if a bug were to exist there.  I can only posit that 
the kernel and dset were out of sync enough to cause this error as 
an anomaly. 
>Unformatted:
