From owner-freebsd-stable Thu May 24 10:28:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id D438E37B423 for ; Thu, 24 May 2001 10:28:25 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f4OHRW994688; Thu, 24 May 2001 12:27:32 -0500 (CDT) (envelope-from jlemon) Date: Thu, 24 May 2001 12:27:32 -0500 (CDT) From: Jonathan Lemon Message-Id: <200105241727.f4OHRW994688@prism.flugsvamp.com> To: forrestc@imach.com, stable@freebsd.org Subject: Re: fxp0 "sleeping" Problem (NOT NEW DRIVER RELATED) X-Newsgroups: local.mail.freebsd-stable In-Reply-To: Organization: Cc: 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 In article you write: >The symptoms are as follows: > >Several times per day the card seems to go to sleep. We cannot ping >through the interface at all (in or out), but pings to the network card ip >address from the box comes back (networking is still alive). > >I have been watching mbufs. The current output is: > >mail# netstat -m >492/3536/10240 mbufs in use (current/peak/max): > 130 mbufs allocated to data > 362 mbufs allocated to packet headers >110/2560/2560 mbuf clusters in use (current/peak/max) >6004 Kbytes allocated to network (78% of mb_map in use) >49385 requests for memory denied >3 requests for memory delayed >0 calls to protocol drain routines > >Generally I never see the clusters above 150 or so UNLESS the card is >"hung" which I suspect is a symptom and not the cause... > >We don't need to do anything to have it come back - just wait, and then >everything seems just fine like as if nothing had happened at all. >It seems to sleep about 5 minutes. I can't tell if it sleeps for a >specific length of time or not, but from the missed ping responses, it >seems like it varys from time to time. > >I am getting NO syslog or dmesg errors when this occurs. Hmm. Can you check your /etc/syslog.conf? There should be a line similar to: kern.debug /var/log/messages to capture kernel output. I'm a little hesitant to believe that there's no error output; maybe it isn't configured or syslogd isn't running. The other thing is that you're running 100mb/s; the previous lockups I've seen with this board were for 10mb/s. Can you send me a dmesg + ifconfig output? -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message