From owner-freebsd-stable Wed Aug 26 18:45:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08041 for freebsd-stable-outgoing; Wed, 26 Aug 1998 18:45:43 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from russian-caravan.cloud9.net (russian-caravan.cloud9.net [168.100.1.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08017 for ; Wed, 26 Aug 1998 18:45:31 -0700 (PDT) (envelope-from scottd@cloud9.net) Received: from earl-grey.cloud9.net (IDENT:4FJsgiO8qM+9Igtiuy93w7uDRbZxbvrT@earl-grey.cloud9.net [168.100.1.1]) by russian-caravan.cloud9.net (8.9.1a/8.9.0/rc-19980602) with SMTP id VAA07238; Wed, 26 Aug 1998 21:43:53 -0400 (EDT) Date: Wed, 26 Aug 1998 21:43:52 -0400 (EDT) From: Scott Drassinower To: Mike Smith cc: stable@FreeBSD.ORG Subject: Re: Intel 100+ troubles In-Reply-To: <199808251742.RAA01063@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998, Mike Smith wrote: > This looks like a known problem which was fixed literally just a few > days ago. It's timing sensitive, which is probably why you're only > seeing it at 100Mbps. The problem still exists. UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 100 408 395 0 -18 0 228 536 vmopar D+ p3 0:00.07 sz I upgraded the machine that this process is running on and a couple of other machines to 2.2.7-release. The machine I am running sz on has a 2.2.7-stable kernel. The machine that is serving this file via NFS is running 2.2.5-release, but is going to get 2.2.7 tomorrow probably. What exactly does vmopar mean? -- Scott M. Drassinower scottd@cloud9.net Cloud 9 Consulting, Inc. White Plains, NY +1 914 696-4000 http://www.cloud9.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message