Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 May 1999 20:24:10 -0500 (CDT)
From:      Chris Dillon <cdillon@wolves.k12.mo.us>
To:        freebsd-stable@freebsd.org
Subject:   panic: vm_object_reference: attempting to reference dead obj
Message-ID:  <Pine.BSF.4.10.9905272018140.74394-100000@mail.wolves.k12.mo.us>

next in thread | raw e-mail | index | archive | help

While attempting to gather information regarding the last crash I
encoutered, I had done a 'make -j 8 world' on this box previously,
though I forgot it only had 16MB RAM enumerated.  Swap city.  :-)

This cropped up as a result:

Script started on Thu May 27 20:10:39 1999
root@cheetah [/var/crash]# gdb -k
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd".
(kgdb) symbol-file /kernel.debug
Reading symbols from /kernel.debug...done.
(kgdb) exec-file kernel.1
(kgdb) core-file vmcore.1
IdlePTD 2613248
initial pcb at 21ee14
panicstr: vm_object_reference: attempting to reference dead obj
panic messages:
---
panic: vm_object_reference: attempting to reference dead obj

syncing disks... 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 38 giving up

dumping to dev 20401, offset 581632
dump 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 
---
#0  boot (howto=256) at ../../kern/kern_shutdown.c:285
285			dumppcb.pcb_cr3 = rcr3();
(kgdb) bt
#0  boot (howto=256) at ../../kern/kern_shutdown.c:285
#1  0xc0140aec in at_shutdown (function=0xc01fb42a <cvtbsdprot.232+52>, 
    arg=0xc04270f8, queue=-1017422012) at ../../kern/kern_shutdown.c:446
#2  0xc01b340b in vm_object_reference (object=0xc36547f8)
    at ../../vm/vm_object.c:245
#3  0xc01b6baa in vm_pageout_page_free (m=0xc04270f8)
    at ../../vm/vm_pageout.c:635
#4  0xc01b72d2 in vm_pageout_scan () at ../../vm/vm_pageout.c:1093
#5  0xc01b78d6 in vm_pageout () at ../../vm/vm_pageout.c:1382
#6  0xc0133492 in kproc_start (udata=0xc0216110) at ../../kern/init_main.c:303
#7  0xc01c701a in fork_trampoline ()
(kgdb) quit


The dmesg is in the last message from me about "panic: vinvalbuf:
dirty bufs", though I did forget to include 'uname -a' output and
mention that it was done under a very recent (as in not over 
an hour old) 3.2-STABLE world.

FreeBSD cheetah.wolves.k12.mo.us 3.2-STABLE FreeBSD 3.2-STABLE #0: Thu
May 27 19:32:28 CDT 1999
root@cheetah.wolves.k12mo.us:/usr/src/sys/compile/CHEETAH i386


Again, tell me about anything you might want me to do with this system
as far as testing goes (beat it to death, whatever), before I put it
into production (luckily these panics would seem to be unlikely in its
normal working conditions).


-- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net
   FreeBSD: The fastest and most stable server OS on the planet.
   For Intel x86 and Alpha architectures (SPARC under development).
   ( http://www.freebsd.org )

   "One should admire Windows users.  It takes a great deal of
    courage to trust Windows with your data."



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" 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.10.9905272018140.74394-100000>