From owner-freebsd-current  Sat Dec 27 17:32:21 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id RAA04125
          for current-outgoing; Sat, 27 Dec 1997 17:32:21 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA04115
          for <freebsd-current@FreeBSD.ORG>; Sat, 27 Dec 1997 17:32:16 -0800 (PST)
          (envelope-from julian@whistle.com)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id RAA18963;
	Sat, 27 Dec 1997 17:21:34 -0800 (PST)
Received: from UNKNOWN(), claiming to be "current1.whistle.com"
 via SMTP by alpo.whistle.com, id smtpd018961; Sat Dec 27 17:21:26 1997
Date: Sat, 27 Dec 1997 17:18:30 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Chris Timmons <skynyrd@opus.cts.cwu.edu>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: no boot: config -g and options DDB 
In-Reply-To: <Pine.BSF.3.96.971227133758.3334A-100000@opus.cts.cwu.edu>
Message-ID: <Pine.BSF.3.95.971227171527.22759F-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

don't try actually boot that kernel....
it often won't work (e.g. I have that problem)
do the following:
cp kernel kernel.strip
strip -d kernel.strip
cp kernel.strip /kernel.new

reboot

you can use the huge kernel against core-dumps
e.g. gdb -k kernel.huge vmcore.0

and if you have remote-gdb enabled and 2 machines, you can use it for that
too (run gdb against it)
but it often won't actually boot 
I don't know why.


On Sat, 27 Dec 1997, Chris Timmons wrote:

> 
> 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
> 
>