Hi all,

I just noticed a 'famd' process running on my box consuming ~100% of CPU.
When I did 'kill <pid>' (as a regular user), the system completely froze
(well, it entered ddb, because I typed 'sync' and it properly saved a
core).  I was under X, so I couldn't see anything else.

Now, analyzing the kcore, I see the following:

(gdb) bt
#0  0x1fefc000 in ?? ()
#1  0xc02a0942 in cpu_reboot (howto=3D256, bootstr=3D0x0)
    at /usr/src/sys/arch/i386/i386/machdep.c:751
#2  0xc01f3824 in db_sync_cmd (addr=3D1, have_addr=3D0, count=3D-1070753826=
,=20
    modif=3D0xcbe5db44 "\200\210=3D=C0[=DB=E5=CB\001") at /usr/src/sys/ddb/=
db_command.c:750
#3  0xc01f3273 in db_command (last_cmdp=3D0xc039e53c, cmd_table=3D0xc033662=
0)
    at /usr/src/sys/ddb/db_command.c:464
#4  0xc01f2f86 in db_command_loop () at /usr/src/sys/ddb/db_command.c:255
#5  0xc01f6078 in db_trap (type=3D6, code=3D0) at /usr/src/sys/ddb/db_trap.=
c:101
#6  0xc029e0aa in kdb_trap (type=3D6, code=3D0, regs=3D0xcbe5dd88)
    at /usr/src/sys/arch/i386/i386/db_interface.c:225
#7  0xc02a87b0 in trap (frame=3D0xcbe5dd88)
    at /usr/src/sys/arch/i386/i386/trap.c:270
#8  0xc010ae6f in calltrap ()
#9  0xc021318d in fdfree (p=3D0xca72ce5c)
    at /usr/src/sys/kern/kern_descrip.c:1284
#10 0xc0217141 in exit1 (l=3D0xca72ba50, rv=3D15)
    at /usr/src/sys/kern/kern_exit.c:267
#11 0xc0226052 in postsig (signum=3D15) at /usr/src/sys/kern/kern_sig.c:1849
#12 0xc02a8a74 in trap (frame=3D0xcbe5dfa8) at /usr/src/sys/sys/userret.h:93

Any idea?  Anyone want to debug?

BTW, I have updated to current today after a month running 2.99.10 (which
was rock solid).  Dunno if it's a problem introduced recently or what (if
so, I guess it will happen again).

Thanks,

--=20
Julio M. Merino Vidal <jmmv@menta.net>
http://www.livejournal.com/users/jmmv/
The NetBSD Project - http://www.NetBSD.org/