From owner-freebsd-stable Wed May 29 11:39:50 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx0.inoc.net (mx0.inoc.net [64.246.130.30]) by hub.freebsd.org (Postfix) with ESMTP id 9057E37B404 for ; Wed, 29 May 2002 11:39:41 -0700 (PDT) Received: from nimbus (unverified [10.0.0.111]) by mx0.inoc.net (Vircom SMTPRS 5.2.204) with ESMTP id ; Wed, 29 May 2002 14:39:41 -0400 From: "Robert Blayzor" To: "'Matthew Dillon'" , "'Karl M. Joch'" , "'Martin Kraemer'" , "'Justin T. Gibbs'" Cc: Subject: RE: 4.6-RC: indefinite wait buffer... (was Re: RE: Swap_pager error) Date: Wed, 29 May 2002 14:39:40 -0400 Organization: INOC, LLC Message-ID: <000201c20740$31792700$6f00000a@z0.inoc.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 Importance: Normal In-Reply-To: <200205291826.g4TIQECP062080@apollo.backplane.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I'm tying your thread into another ' 4.6-RC: indefinite > wait buffer...' > Since you appear to be having a very similar problem to the one > Martin is reporting. Thanks. If I can be of any help, let me know. I do not believe this to be exactly just a 4.6-stable issue as I've seen the problem happen on 4.5-RELEASE-p4 as well. Again, once you reboot the machine, all is well for what could be hours, days or weeks, and then eventually you just run into the problem. I'm thinking it all depends on how much you swap. On our NFS/SMB server, it has 1GB of RAM and won't swap for days, maybe weeks. Then when the server gets busy at times, and it needs to use swap, I believe that is when the problem occurs, or shortly after. But then, sometimes not at all. We were not able to log any dmesg errors as it seems that when this problem occurred /var/log/messages could not be written to. We log all kern.debug to both /var/log/messages and /dev/console. The console was littered with the messages, while /var/log contained nothing. We've fixed this by remotely logging kern.debug to another syslog server. Perhaps when this problem occurred it hosed syslogd somehow. I can do limited testing on our production boxes, and am willing to do so if it helps the cause. -- Robert Blayzor, BOFH INOC, LLC rblayzor@inoc.net A Life? Cool! Where can I download one of those from? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message