Date: Sun, 9 Apr 1995 13:21:04 -0700 From: uhclem%nemesis@fw.ast.com To: freebsd-bugs Subject: bin/328: Checking for -c kernel changes randomly hangs FDIV023 Message-ID: <199504092021.NAA01491@freefall.cdrom.com> In-Reply-To: Your message of Sun, 9 Apr 95 14:22 CDT <m0ry2ZM-0004upC@nemesis.lonestar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>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: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Apr 9 13:21:02 1995 >Originator: Frank Durda IV >Organization: >Release: FreeBSD 2.0.0-SNAP950322 i386 >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* >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504092021.NAA01491>