Date: Sat, 28 Jul 2001 16:28:50 -1000 (HST) From: Vincent Poy <vince@oahu.WURLDLINK.NET> To: matt <matt-l@pacbell.net> Cc: <current@FreeBSD.ORG> Subject: Re: -current kernel panicing Message-ID: <20010728161828.P7031-100000@oahu.WURLDLINK.NET> In-Reply-To: <000a01c1174b$2f637dc0$6503c23f@XGforce.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Interesting... I'm running on a cvsup of July 25, 2001 17:00GMT except because of Ian Dowse mentioning in the message thread: SIGCHLD changes causing fault on nofault entry panics, I reverted back to src/sys/kern/kern_exit.c 1.130 and src/sys/kern/kern_sig.c 1.124 to test. Sometimes it will just hang. I noticed that sometimes it will say when it hangs solid: swap_pager: out of swap space swap_pager_getswapspace:failed And this machine does have 512Megs of ram and only 64 is used most of the time. Even swapinfo indicates that it's not using the swap yet. root@pele [4:23pm][/usr/home/vince] >> swapinfo Device 1K-blocks Used Avail Capacity Type /dev/da0s1b 262016 0 262016 0% Interleaved From the following output, it seems like nfs code is at fault but we're not even using nfs at all root@pele [4:24pm][/usr/home/vince] >> nm -n /boot/kernel/kernel | grep da041d9c root@pele [4:25pm][/usr/home/vince] >> nm -n /boot/kernel/kernel | grep da041d9 root@pele [4:25pm][/usr/home/vince] >> nm -n /boot/kernel/kernel | grep da041d root@pele [4:25pm][/usr/home/vince] >> nm -n /boot/kernel/kernel | grep da041 root@pele [4:25pm][/usr/home/vince] >> nm -n /boot/kernel/kernel | grep da04 c02bda04 T nfs_curusec root@pele [4:25pm][/usr/home/vince] >> nm -n /boot/kernel/kernel | grep c118de00 root@pele [4:27pm][/usr/home/vince] >> nm -n /boot/kernel/kernel | grep c118de0 root@pele [4:27pm][/usr/home/vince] >> nm -n /boot/kernel/kernel | grep c118de root@pele [4:27pm][/usr/home/vince] >> nm -n /boot/kernel/kernel | grep c118d root@pele [4:27pm][/usr/home/vince] >> nm -n /boot/kernel/kernel | grep c118 c03dc118 ? __set_sysuninit_set_sym_M_IFADDR_uninit_sys_uninit c03ec118 d twed_twe_driver_list 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 On Sat, 28 Jul 2001, matt wrote: > Something wrong in the fs lock code. > > ====================================== > WWW.XGFORCE.COM > The Next Generation Load Balance and > Fail Safe Server Clustering Software > for the Internet. > ====================================== > ----- Original Message ----- > From: "Vincent Poy" <vince@oahu.WURLDLINK.NET> > To: <current@FreeBSD.ORG> > Sent: Saturday, July 28, 2001 2:49 AM > Subject: -current kernel panicing > > > > 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 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010728161828.P7031-100000>