From owner-freebsd-net Tue Apr 3 22:24:43 2001 Delivered-To: freebsd-net@freebsd.org Received: from vbook.express.ru (vbook.express.ru [212.24.37.106]) by hub.freebsd.org (Postfix) with ESMTP id DE8FC37B71B for ; Tue, 3 Apr 2001 22:24:39 -0700 (PDT) (envelope-from vova@vbook.express.ru) Received: (from vova@localhost) by vbook.express.ru (8.9.3/8.9.3) id VAA02813; Tue, 3 Apr 2001 21:09:45 +0400 (MSD) (envelope-from vova) From: "Vladimir B. Grebenschikov" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15050.984.351798.488677@vbook.express.ru> Date: Tue, 3 Apr 2001 21:09:44 +0400 (MSD) To: Jonathan Lemon Cc: deepak@ai.net, net@FreeBSD.ORG Subject: Re: FW: Network lockups on fxp0? In-Reply-To: <200103272253.f2RMrfG52107@prism.flugsvamp.com> References: <200103272253.f2RMrfG52107@prism.flugsvamp.com> X-Mailer: VM 6.72 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jonathan Lemon writes: > >>fxp0: SCB timeout > >>fxp0: DMA timeout > >>(repeating) > > SCB timeout comes about because the chip is refusing to accept > any more commands; in this case, it probably is wedged. Is there > any pattern to this? Do you happen to have hardware flowcontrol > enabled? Does an ifconfig up/down fix the problem? My notebook shows such diagnostic after boot under M$ Windows, so I need to turn notebook off and then on to restore ethernet function. (I have VAIO-505S with IntellEtherExpress) So, may be it is some kind of state of ethernet chip ? > Jonathan -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, vova@express.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message