Hello everybody, I upgraded to today's -CURRENT and upon reboot with the new kernel, experienced a panic. Since I did not see it reported here yet, here is some info. More available on request, but I do not have a serial console and therefore had to transcribe everything by hand. Also, there was no core dump. (How can I force it?)
Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc02054bc stack pointer = 0x10:0xceb1db5c frame pointer = 0x10:0xceb1db60 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 = 48 (rm) kernel: type 12 trap, code= 0 Stopped at suser_cred+0x1c: cmpl $0,0x4(%edx) db> trace suser_cred chkiq ufs_inactive ufs_vnoperate vput unlink syscall syscall_with_err_pushed --- syscall (10, FreeBSD ELF, unlink) eip = 0x804af7b, esp = 0xbfbffc7c ebp = 0xbfbffd08 db> show locks exclusive sleep mutex Giant r= 0 (0xc03ed260) locked @ ../../../vm/vm_fault.c:202 FreeBSD fonix.adamsfamily.xx 5.0-CURRENT FreeBSD 5.0-CURRENT #46: Sat Jun 15 17:57:46 CEST 2002 [EMAIL PROTECTED]:/usr/home/cc/build/freebsd/src/sys/i386/compile/FONIX i386 dmesg is not available from the failing kernel, but the only "could sleep with..." messages came from the soundcard driver. The panic happens also in single-user mode, in my case most easily triggered with the use of rm(1). If you need any more info, just ask. -- Regards: Szilveszter ADAM Szombathely Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message