Date: Mon, 21 Jul 2008 21:45:43 GMT From: Bruce Cran <bruce@cran.org.uk> To: freebsd-gnats-submit@FreeBSD.org Subject: i386/125843: [boot] 'load' followed by 'boot' of missing file causes panic Message-ID: <200807212145.m6LLjhuA078339@www.freebsd.org> Resent-Message-ID: <200807212150.m6LLoB5q091559@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 125843 >Category: i386 >Synopsis: [boot] 'load' followed by 'boot' of missing file causes panic >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-i386 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jul 21 21:50:11 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Bruce Cran >Release: 7.0-p1 >Organization: >Environment: FreeBSD gluon.draftnet 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #0: Sat May 17 22:56:30 BST 2008 brucec@gluon.draftnet:/usr/obj/usr/src/sys/GENERIC i386 >Description: Trying to load _or_ boot a missing kernel results in the message "can't find <name>". However, if you try to "load" then "boot" the missing file or vice versa the system panics: OK load abc can't find 'abc' OK boot abc Consoles: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS drive D: is disk2 BIOS drive E: is disk3 BIOS 639kB/1047488kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 (brucec@gluon.draftnet, Thu May 8 21:54:48 BST 2008) Can't work out which disk we are booting from. Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0: panic: free: guard1 fail @ 0x5c4ec from /usr/src/sys/boot/i386/loader/../../common/module.c:959 --> Press a key on the console to reboot <-- >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200807212145.m6LLjhuA078339>