From owner-freebsd-current Sat Dec 27 13:51:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA21681 for current-outgoing; Sat, 27 Dec 1997 13:51:04 -0800 (PST) (envelope-from owner-freebsd-current) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA21668 for ; Sat, 27 Dec 1997 13:50:58 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.8/8.8.7) with SMTP id NAA03730 for ; Sat, 27 Dec 1997 13:50:57 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Sat, 27 Dec 1997 13:50:57 -0800 (PST) From: Chris Timmons To: freebsd-current@freebsd.org Subject: no boot: config -g and options DDB Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk My world and bootblocks are from 12/17 and my kernel sources are from yesterday. I always hate bringing these things up because invariably it's me that is broken, but here goes anyways ?<: If I 'config -g GENERIC' and build/install normally I get a happily booting kernel. Add: options DDB options BREAK_TO_DEBUGGER and the kernel no longer boots; instead it starts booting and then the machine behaves as if the reset button had been pushed and the process repeats (unless -d is present, then the session ends in catatonia.) I trapped some output from the serial console from a build which did the same thing but was NOT GENERIC, rather my customized kernel: - - - - - - - - - - - - - - - (pinwheel graphics removed :) >> FreeBSD BOOT @ 0x10000: 637/31744 k of memory, serial/dual console Boot default: 0:sd(0,a)kernel boot:-d -v Booting 0:sd(0,a)kernel @ 0x100000 text=0xdd000 data=0x10000 bss=0x1a9b4 symbols=[+0x64c+0x4+0x286734+0x4+0x42762e] Can't find file kernel.config total=0x8b5d6a entry point=0x100000 [ preserving 0x6add6c bytes of kernel symbol table ] Debugger("Boot flags requested debugger") Stopped at _Debugger+0x35 [../../i386/i386/db_interface.c:58]: movb $0,_in_Debugger.98 db> next After 2 instructions (0 loads, 0 stores), Stopped at _Debugger+0x3d: ret db> next BIOS basemem (637K) != RTC basemem (640K), setting to BIOS value - - - - - - - - - - - - - - - At this point the machine is really hung and must be powered off to reset. If someone else could repeat I'll send-pr it... -Chris