From owner-freebsd-stable Mon Feb 1 07:06:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02607 for freebsd-stable-outgoing; Mon, 1 Feb 1999 07:06:02 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02554 for ; Mon, 1 Feb 1999 07:05:57 -0800 (PST) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id JAA24753; Mon, 1 Feb 1999 09:05:26 -0600 (CST) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id JAA24749; Mon, 1 Feb 1999 09:05:25 -0600 (CST) Message-ID: <011a01be4df4$5b92f830$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "Glen Foster" , Subject: Re: 3.0-STABLE breakage? Date: Mon, 1 Feb 1999 09:05:50 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No, I have seen this problem too. Saturday all was working again after a new world was built. However, networking performance has been very poor since then. What is one too do? -----Original Message----- From: Glen Foster To: stable@FreeBSD.ORG Date: Monday, February 01, 1999 8:58 AM Subject: 3.0-STABLE breakage? >Folks, > >Am I the only one for whom top and ps are broken and w/uptime and who >prints weird messages about /dev//whatever being missing? > >tbd: {303} top >kvm_open: proc size mismatch (46992 total, 680 chunks) >top: Out of memory. >tbd: {304} w >w: /dev//è´6ttyp4: No such file or directory >w: /dev//5: No such file or directory > 9:23AM up 20:13, 2 users, load averages: 1.63, 1.49, 1.42 >USER TTY FROM LOGIN@ IDLE WHAT >w: proc size mismatch (46992 total, 680 chunks): No such file or directory > >I'm guessing a problem with procfs. Both world and the running kernel >were built from sources updated Jan 28 and should not be out of sync. >I rebuilt top and w/uptime just in case and the same breakage >persists. PROCFS is in the kernel, loading the KLD makes no >difference. > >Where should I look to begin having an idea of how to fix this? Is >this a known problem? > >TIA, >Glen Foster > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message