Date: Fri, 19 Mar 1999 16:33:25 -0800 (PST) From: Doug Ambrisko <ambrisko@whistle.com> To: ath@niksun.com (Andrew Heybey) Cc: freebsd-current@FreeBSD.org Subject: Re: deadlock in 3.1-RELEASE Message-ID: <199903200033.QAA10236@whistle.com> In-Reply-To: <199903192159.QAA15741@stiegl.niksun.com> from Andrew Heybey at "Mar 19, 99 04:59:17 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Andrew Heybey writes: | When the deadlock does occur, "ps" (in ddb) says that there are many | processes in vmwait. The pagedaemon is in an inode wait. The stack | trace is in default_halt() (which I assume just means that there are | no runnable processes). The system is not short of memory (unless | "short of memory" means that it is attempting to use it all as a disk | cache). | | A search of cvs-commiters for "vmwait deadlock" did not reveal (to my | ignorant eye, anyway) any fixes to -current that would apply to this | problem. I have an environment that triggered this in less then 1/2 hour. Julian with the help of his friends (ie Matt & Alan) have brought in some changes from -current that got rid of my problem. Getting the latest RELENG_3 stuff should fix it. My processes got stuck on vmwait. Doug A. 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?199903200033.QAA10236>