From owner-freebsd-current Sat Jul 28 2:50: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by hub.freebsd.org (Postfix) with ESMTP id F124437B405 for ; Sat, 28 Jul 2001 02:49:56 -0700 (PDT) (envelope-from vince@oahu.WURLDLINK.NET) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.11.3/8.11.3) with ESMTP id f6S9nsc13360 for ; Fri, 27 Jul 2001 23:49:55 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Fri, 27 Jul 2001 23:49:54 -1000 (HST) From: Vincent Poy To: Subject: -current kernel panicing Message-ID: <20010727234011.D7031-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm getting a panic in the -current kernel with using kernels built with src/sys/kern/kern_exit.c 1.130 and src/sys/kern/kern_sig.c 1.124 as well as with src/sys/kern/kern_exit.c 1.131 and src/sys/kern/kern_sig.c 1.125. This seems to be a problem that only passwd(1) and chpass(1) seems to cause. vipw appears to work fine as well as everything else. This is what happens: root@pele [10:55pm][~] >> passwd toor Changing local password for toor. New password: Retype new password: passwd: updating the database... passwd: done root@pele [10:55pm][~] >> root@pele [10:55pm][~] >> root@pele [10:55pm][~] >> root@pele [10:55pm][~] >> root@pele [10:55pm][~] >> root@pele [10:55pm][~] >> root@pele [10:55pm][~] >> root@pele [10:55pm][~] >> After here, it just freezes solid for 1 minute then displays on the console... Jul 27 22:57:24 pele /boot/kernel/kernel: lock order reversal Jul 27 22:57:24 pele /boot/kernel/kernel: lock order reversal Jul 27 22:57:24 pele /boot/kernel/kernel: 1st 0xda041d9c process lock @ /usr/src/sys/vm/vm_glue.c:469 Jul 27 22:57:24 pele /boot/kernel/kernel: 1st 0xda041d9c process lock @ /usr/src/sys/vm/vm_glue.c:469 Jul 27 22:57:24 pele /boot/kernel/kernel: 2nd 0xc118de00 lockmgr interlock @ /usr/src/sys/kern/kern_lock.c:239 Jul 27 22:57:24 pele /boot/kernel/kernel: 2nd 0xc118de00 lockmgr interlock @ /usr/src/sys/kern/kern_lock.c:239 Then it just hangs completely, not even a db> prompt so had to hard reboot and it goes into single user mode where one would need to fsck all the slices and then I have to: cp -p /var/backups/master.passwd.bak /etc/master.passwd since the password database somehow got corrupted and then ran vipw and :wq! and then shutdown the machine where it would boot normally. Anyone have any ideas how to solve this one or what is causing it since the previous GENERIC kernel from the 6/16/2001 build of -current seemed fine. Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message