-current seems a little unstable tonight
I just cvsup'd and about 1.5h later got a crash+reboot with no dump. I think someone else mentioned problems with fsck and I saw something like that too -- it looked like the rc scripts errored out after the fsck and dropped me into single user... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -current seems a little unstable tonight
On Thu, Jul 18, 2002 at 01:28:22AM -0700, Lamont Granquist wrote: I just cvsup'd and about 1.5h later got a crash+reboot with no dump. I think someone else mentioned problems with fsck and I saw something like that too -- it looked like the rc scripts errored out after the fsck and dropped me into single user... It could have been the following which I just got. panic: vm_fault: fault on nofault entry, addr: c8856000 (kgdb) bt #0 0xc01b1900 in doadump () #1 0xc01b1d12 in boot () #2 0xc01b1ec5 in panic () #3 0xc01300cd in db_panic () #4 0xc013006c in db_command () #5 0xc013013b in db_command_loop () #6 0xc013257a in db_trap () #7 0xc02b11a0 in kdb_trap () #8 0xc02be98c in trap () #9 0xc02b2568 in calltrap () #10 0xc01b1eac in panic () #11 0xc027db53 in vm_fault () #12 0xc02beba5 in trap_pfault () #13 0xc02be741 in trap () #14 0xc02b2568 in calltrap () #15 0xc01b707f in msleep () #16 0xc01f2320 in sched_sync () #17 0xc01a1381 in fork_exit () I didn't have a kernel with debugging info so I am building that now in case it happens again. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -current seems a little unstable tonight
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, t---Type return
to continue, or q return to quit---
f_esp = -1071956576, tf_ss = -1304475416}) at /usr/src/sys/i386/i386/trap.c:445
#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 [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: -current seems a little unstable tonight
On Thu, Jul 18, 2002 at 02:00:14PM -0700, Julian Elischer wrote:
set radix 16
and then print the trap frame again.. (#12)
#12 0xc02a0ce5 in trap (frame= {tf_fs = 0xc02a0018, tf_es = 0xc0320010,
tf_ds = 0xc0310010, tf_edi = 0xc191d094, tf_esi = 0xc0bc0f00, tf_ebp =
0xc8880c8c, tf_isp = 0xc8880c3c, tf_ebx = 0x405000, tf_edx = 0xc8ebada0,
tf_ecx = 0xc191fb40, tf_eax = 0xc191fb40, tf_trapno = 0xc, tf_err = 0x0,
tf_eip = 0xc02a0050, tf_cs = 0x8, tf_eflags = 0x10246, tf_esp =
0xc01b3da0, tf_ss = 0xb23f48e8}) 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.
(kgdb) x/i 0xc02a0050
0xc02a0050 sw1b+11: cmp0x0(%edx),%ebx
Which is i386/i386/swtch.s:182 I think.
This is where the address space is switched or not. However, this goes
above my head. Hopefully this helps you.
Thanks for the response!
Mark
--
Mark Santcroos RIPE Network Coordination Centre
http://www.ripe.net/home/mark/ New Projects Group/TTM
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
