you can use addr2line to get info, but
at a pinch you can just use nm -n to figure out what function each address
is in.


On Sun, 14 Jul 2002, Szilveszter Adam wrote:

> Hello everybody,
> 
> I have recently finished to upgrade my system to today morning's
> -CURRENT, with sources just *before* the commit of rev 1.154 to
> src/sys/kern/kern_fork.c by Julian.
> 
> I have an UP IA32 machine, I am not using any additional kernel modules,
> and now, upon rebooting with the new kernel, as soon as I allow to
> continue from the loader prompt, the kernel greets me with this:
> 
> (No serial console, transcribed by hand, please excuse any typos)
> 
> Fatal trap 12: page fault within kernel mode
> 
> fault virtual address   = 0xbff004c0
> fault code              = supervisor read, protection violation
> instruction pointer     = 0x8:0xc035c348
> stack pointer           = 0x10:0xc0532c08
> frame pointer           = 0x10:0xc0532c10
> code segment            = base 0x0, limit 0xfffff, type 0x1b
>                         = DPL 0, pres 1, def32 1, gran 1
> processor eflags        = interrupt enabled, resume, IOPL=0
> current process         = 0 ()
> 
> kernel: type 12 trap, code=0
> Stopped at 0xc035c348:      cmpl     $0,0xbfc00000(%eax)
> 
> Unfortunately, there is preciously little I could extract from ddb after
> this.
> 
> ddb> ps
> pid  proc  addr  uid   ppid   pgrp  flag  stat  wmesg  wchan  cmd
> 0  c03f00c0 c0530000 0 0      0    000000 New 
> 
> ddb> tr
> (null)(c0418920,c0800000,537000,c0532d48,c03595bd) at 0xc035c348
> (null)(537000,0,c0532c9c,c0532ce8,10)  at 0xc035c290
> (null)(537000,c0352524,f,0,8) at 0xc03595bd
> (null)(537000) at 0xc0359fb9
> (null)() at 0xc0130c7d
> 
> An attempt to "show locks" resulted in:
> 
> witness_list: witness_cold
> 
> Fatal trap 3 breakpoint instruction fault while in kernel mode
> 
> An attempt to "show witness" resulted in:
> 
> witness_display: witness_cold
> 
> Uptime 1s
> and a complete lockup, only a power-cycle helped.
> 
> No dump was taken.
> 
> Does this ring a bell with anyone? I know that the trace may not help
> much...
> 
> I will be just too glad to offer any information or testing that may be
> needed.
> 
> -- 
> Regards:
> 
> Szilveszter ADAM
> Szombathely Hungary
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to