Date: Tue, 25 Aug 1998 20:28:21 -0400 (EDT) From: Scott Drassinower <scottd@cloud9.net> To: Mike Smith <mike@smith.net.au> Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Intel 100+ troubles Message-ID: <Pine.BSF.4.02A.9808252023260.11750-100000@earl-grey.cloud9.net> In-Reply-To: <199808251717.RAA00891@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > 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? It's just really weird that the problem only seems to happen at 100 megabits. The only thing I haven't done at this point is taken out the fxp card and tried something else. -- 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-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.02A.9808252023260.11750-100000>