Date: Thu, 18 Jul 2002 14:00:14 -0700 (PDT) From: Julian Elischer <julian@elischer.org> To: Mark Santcroos <marks@ripe.net> Cc: freebsd-current@FreeBSD.ORG Subject: Re: -current seems a little unstable tonight Message-ID: <Pine.BSF.4.21.0207181352410.84569-100000@InterJet.elischer.org> In-Reply-To: <20020718204321.GA1131@laptop.6bone.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
if you have ddb it would be instructive to ss what IT thinks the stack
looks like: heres' what I think is line 557 of kern_synch.c is:
554 if (td->td_wchan != NULL) {
555 p->p_stats->p_ru.ru_nvcsw++;
556 td->td_state = TDS_SLP;
557 mi_switch();
558 }
so we need to see where in mi_switch() if your file is the same as mine...
also:
do:
set radix 16
and then print the trap frame again.. (#12)
On Thu, 18 Jul 2002, Mark Santcroos wrote:
> On Thu, Jul 18, 2002 at 10:48:09AM +0200, Mark Santcroos wrote:
> > panic: vm_fault: fault on nofault entry, addr: c8856000
> >
> > (kgdb) bt
>
> <backtrace without debug symbols>
>
> > I didn't have a kernel with debugging info so I am building that now in
> > case it happens again.
>
> Catched it again and now with debugging kernel.
>
> panic: vm_fault: fault on nofault entry, addr: c8eba000
>
> #9 0xc01ae5f1 in panic () at /usr/src/sys/kern/kern_shutdown.c:493
> #10 0xc02629fb in vm_fault (map=0xc0832000, vaddr=3370885120,
> fault_type=1 '\001', fault_flags=0) at /usr/src/sys/vm/vm_fault.c:259
> #11 0xc02a1149 in trap_pfault (frame=0xc8880c10, usermode=0, eva=3370888608)
> at /usr/src/sys/i386/i386/trap.c:747
> #12 0xc02a0ce5 in trap (frame=
> {tf_fs = -1070989288, tf_es = -1070465008, tf_ds = -1070530544,
> tf_edi = -1047408492, tf_esi = -1061417216, tf_ebp = -930607988,
> tf_isp = -930608068, tf_ebx = 4214784, tf_edx = -924078688, tf_ecx =
> -1047397568, tf_eax = -1047397568, tf_trapno = 12, tf_err = 0, tf_eip
> = -1070989232, tf_cs = 8, tf_eflags = 66118, tf_esp = -1071956576, tf_ss =
> -1304475416}) at /usr/src/sys/i386/i386/trap.c:445
then try use x/i on the contents of tf_eip to find where the actual fault
was. Use 'disassemble' on that function to figure out where in the file
you were.
theoretically addr2line(1) can give you this but in my experience it
doesn't work at the moment.
> #13 0xc0294ae8 in
> calltrap () at {standard input}:98 #14 0xc01b37ab in msleep
> (ident=0xc031708c, mtx=0x0, priority=104, wmesg=0x0,
> timo=0) at /usr/src/sys/kern/kern_synch.c:557
> #15 0xc01eea4c in sched_sync () at /usr/src/sys/kern/vfs_subr.c:1503
> #16 0xc019daad in fork_exit (callout=0xc01ee878 <sched_sync>, arg=0x0,
> frame=0xc8880d48) at /usr/src/sys/kern/kern_fork.c:861
>
> I will try to find what's going on. Anyone any pointers?
>
> Thanks
>
> Mark
>
> --
> Mark Santcroos RIPE Network Coordination Centre
> http://www.ripe.net/home/mark/ New Projects Group/TTM
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0207181352410.84569-100000>