From owner-freebsd-questions Thu Apr 29 11:56:16 1999 Delivered-To: freebsd-questions@freebsd.org Received: from anon.lcs.mit.edu (anon.lcs.mit.edu [18.26.0.254]) by hub.freebsd.org (Postfix) with SMTP id 3FC1F1539A for ; Thu, 29 Apr 1999 11:56:13 -0700 (PDT) (envelope-from serge69@nym.alias.net) Date: 29 Apr 1999 18:56:11 -0000 Message-ID: <19990429185611.31524.qmail@nym.alias.net> From: Sergey Subject: Kernel debugging - How can I find "current" process? To: MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, All! I've experienced occasional kernel panic in 3.1-RELEASE+ports-stable-kit. How can I determine current process? (process which caused panic) ps ax doesn't help, because there are about 5 processes in 'R' state. dmesg or gdb messages, doesn't help too .... Thanks, Sergey. (proxy:crash-analyzing)# gdb -k kernel.0 vmcore.0 IdlePTD 2629632 initial pcb at 2543d4 panicstr: lockmgr: locking against myself panic messages: --- panic: lockmgr: locking against myself syncing disks... panic: lockmgr: locking against myself (kgdb) bt #0 0xf01452c3 in boot () #1 0xf0145548 in at_shutdown () #2 0xf01414a8 in lockmgr () #3 0xf0167698 in vop_stdlock () #4 0xf01ec131 in ufs_vnoperate () #5 0xf01703fb in vn_lock () #6 0xf016a027 in vget () #7 0xf01e8b67 in qsync () #8 0xf01e4359 in ffs_sync () #9 0xf016c053 in sync () #10 0xf0145109 in boot () #11 0xf0145548 in at_shutdown () #12 0xf01414a8 in lockmgr () #13 0xf0167698 in vop_stdlock () #14 0xf01ec131 in ufs_vnoperate () #15 0xf01703fb in vn_lock () #16 0xf016a0db in vrele () #17 0xf01f4529 in vm_object_vndeallocate () #18 0xf01e555f in ffs_write () #19 0xf016fd39 in vn_rdwr () #20 0xf013c4d3 in acct_process () #21 0xf013f9e1 in exit1 () #22 0xf013f74c in exit1 () #23 0xf02125cb in syscall () #24 0xf0208acc in Xint0x80_syscall () Cannot access memory at address 0xefbfd92 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message