From nemesis!uhclem@fw.ast.com  Sun Apr  9 13:13:58 1995
Received: from relay1.UU.NET (relay1.UU.NET [192.48.96.5])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA01137
          for <FreeBSD-gnats-submit@freebsd.org>; Sun, 9 Apr 1995 13:13:56 -0700
Received: from ast.com by relay1.UU.NET with SMTP 
	id QQyktk25433; Sun, 9 Apr 1995 16:13:50 -0400
Received: from trsvax.fw.ast.com (fw.ast.com) by ast.com with SMTP id AA08924
  (5.67b/IDA-1.5 for uunet!freebsd.org!FreeBSD-gnats-submit); Sun, 9 Apr 1995 13:17:57 -0700
Received: by trsvax.fw.ast.com (/\=-/\ Smail3.1.18.1 #18.1)
	id <m0ry3FJ-0000HfC@trsvax.fw.ast.com>; Sun, 9 Apr 95 15:06 CDT
Received: by nemesis.lonestar.org (Smail3.1.27.1 #18)
	id m0ry2ZM-0004upC; Sun, 9 Apr 95 14:22 CDT
Message-Id: <m0ry2ZM-0004upC@nemesis.lonestar.org>
Date: Sun, 9 Apr 95 14:22 CDT
From: uhclem%nemesis@fw.ast.com
Reply-To: uhclem%nemesis@fw.ast.com
To: FreeBSD-gnats-submit@freebsd.org
Cc: uhclem@nemesis.lonestar.org
Subject: Checking for -c kernel changes randomly hangs		FDIV023
X-Send-Pr-Version: 3.2

>Number:         328
>Category:       bin
>Synopsis:       Checking for -c kernel changes randomly hangs		FDIV023
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs (FreeBSD bugs mailing list)
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Apr  9 13:21:02 1995
>Closed-Date:    Sat Jun 24 08:37:54 PDT 1995
>Last-Modified:
>Originator:     Frank Durda IV
>Release:        FreeBSD 2.0.0-SNAP950322 i386
>Organization:
>Environment:

FreeBSD 2.0.0-SNAP950322 i386
Stock kernel, "make world" kernel, or custom kernel.


>Description:

[FDIV023]

From time to time during the normal boot process, it will hang immediately
after the message:

	check for kernel -c changes

After waiting a minute or so to make sure it is hung, if you press CTRL-C,
the system will proceed with:

	clearing /tmp

and continue to boot normally.

This may be related to booting a kernel named something other than /kernel,
but it seemed more random than that.  As mentioned above, I tried several
different kernels (including the distribution "stocl" kernel) and
tried naming them different things and it didn't seem to matter.  There
didn't seem to be a pattern to the failures.


>How-To-Repeat:

Let the system boot normally, although you have to specify a kernel name
(due to boot block bug).   If it doesn't hang, shut down and try again.
It would hang probably four or five times out of ten boots.


>Fix:
	
*END*

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: jkh 
State-Changed-When: Sat Jun 24 08:37:54 PDT 1995 
State-Changed-Why:  
author of this PR hasn't seen the problem since. 
>Unformatted:



