Re: panic at serial boot

From: <mh_at_kernel32.de>
Date: Tue, 02 Apr 2013 23:06:06 +0200
Hi again,

Am 2013-04-02 21:52, schrieb Konstantin Belousov:
> On Tue, Apr 02, 2013 at 08:23:20PM +0200, mh_at_kernel32.de wrote:
>
> Try breaking into the debugger and see where it progresses. To do 
> this,
> you would need to boot with the 'boot -d' command from the loader 
> prompt,
> then do 'w kbd_break_to_debugger 1', then ctrl-alt-esc when you want 
> to
> activate the debugger. In the debugger, start with the 'ps' command.
>

After the beastie menu I went to the loader prompt and did "boot -d".
I was sent to the debugger and did "w kbd_break_to_debugger 1".

This is the output I get.

INT 13 08: Success, count = 1, BPT = 0000:0000                          
        GDB: no debug ports present
KDB: debugger backends: ddbhift limit: 0x82
KDB: current backend: ddbt15 = f000f859  int1e = f000ef6d
KDB: enter: Boot flags requested debuggerint1e = f000ef6d
[ thread pid 0 tid 0 ] booting...
Stopped at      kdb_enter+0x3e: movq    $0,kdb_why
db> w kbd_break_to_debugger 1
Symbol not found


Where to go from now? A good pointer to documentation is okay too ;)
Sorry if asking too many questions, but although being a FreeBSD user 
since 4.0, I never had to debug or been to where I am now.
So in advance another sorry if the question sounds stupid.

A quick google for 'FreeBSD "w kbd_break_to_debugger 1" "Symbol not 
found"' didn't return anything.

a little helpless regards,
./Marian
Received on Tue Apr 02 2013 - 19:06:10 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:36 UTC