From owner-freebsd-stable Tue Aug 25 17:45:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11138 for freebsd-stable-outgoing; Tue, 25 Aug 1998 17:45:16 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d3.dialup.hilink.com.au [203.2.144.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11121 for ; Tue, 25 Aug 1998 17:45:11 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA01063; Tue, 25 Aug 1998 17:42:39 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808251742.RAA01063@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Scott Drassinower cc: stable@FreeBSD.ORG Subject: Re: Intel 100+ troubles In-reply-to: Your message of "Tue, 25 Aug 1998 20:28:21 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Aug 1998 17:42:37 +0000 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 25 Aug 1998, Mike Smith wrote: > > > There have been some serious NFS-related fixes subsequent to 2.2.6; it > > is quite possible that you're seeing the bugs that these addressed > > rather than a hardware problem. It is useful to add the 'l' flag to > > ps(1) and see what the hung processes have in their WCHAN field, as > > this gives more detail than just "disk wait". > > UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND > 0 2438 2429 0 -18 0 228 520 vmopar D p4- 0:00.02 sz > > vmopar is new to me. 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. > > If you have an opportunity, you might want to build a 2.2.7 kernel and > > see if you can reproduce the problems. If you don't have the resources > > to do this in-house, you should be able to ask on the freebsd-stable > > list for someone to generate a -stable kernel for you to try. > > Will I need a 2.2.7 system to build a 2.2.7 kernel? You should be able to build a 2.2.7-stable kernel on a 2.2.6 system. Note that a 2.2.7-release kernel will still exhibit the problem you're noticing above. (I say 'should' because I can't verify that this is the case at this point.) The best way to go about updating a test system will be to fetch the CVSup DIY package using pkg_add ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsupit.tgz You might want to read the CVSup FAQ first, see: http://www.polstra.com/projects/freeware/CVSup/ Once you have updated your sources, you should be able to build a test kernel. Please let us know how you go, and don't hesitate to ask if you run into any more problems. Note that I've redirected this discussion to the freebsd-stable list, as I don't think this is a hardware problem. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message