From owner-freebsd-net@FreeBSD.ORG Mon Jan 22 13:57:03 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BA00B16A507 for ; Mon, 22 Jan 2007 13:57:03 +0000 (UTC) (envelope-from lists@qwirky.net) Received: from public.aci.on.ca (aci.on.ca [205.207.148.251]) by mx1.freebsd.org (Postfix) with ESMTP id 7C26013C428 for ; Mon, 22 Jan 2007 13:57:03 +0000 (UTC) (envelope-from lists@qwirky.net) Received: from (invalid client hostname: host address literal does not match remote client address)[127.0.0.1] (xtreme-156-171.dyn.aci.on.ca[69.17.156.171] port=1086) by public.aci.on.ca([205.207.148.252] port=25) via TCP with esmtp (3162 bytes) (sender: ) id for ; Mon, 22 Jan 2007 08:39:20 -0500 (EST) (Smail-3.2.0.122-Pre 2005-Nov-17 #1 built 2006-Feb-21) Message-ID: <45B4BE90.20602@qwirky.net> Date: Mon, 22 Jan 2007 08:39:28 -0500 From: Jeff Royle User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <1458229821.20070120234257@velnet.ru> <45B28F37.7040100@delphij.net> <1651695163.20070122010957@velnet.ru> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 0704-1, 22/01/2007), Outbound message X-Antivirus-Status: Clean Subject: Re: reproducible watchdog timeout in bge X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lists@qwirky.net List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 13:57:03 -0000 MQ wrote: > 2007/1/22, Wishmaster : >> >> Hello LI, >> >> Sunday, January 21, 2007, 12:52:55 AM, you wrote: >> >> LX> Wishmaster wrote: >> >> Hi, >> >> >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/92090 >> >> LX> Have you tried this one? >> >> LX> http://people.freebsd.org/~delphij/misc/patch-bge-releng62 >> >> LX> Cheers, >> >> Yes, i tried, but have no effect. >> >> after reboot interface works, but if i try to ping with packet for >> example 1500 bytes and interval 0.01s it looks like >> >> answer >> answer >> answer >> .... >> ..... over 50 or less icmp answers then >> ping: sendto: No buffer space available >> ping: sendto: No buffer space available >> ping: sendto: No buffer space available >> ping: sendto: No buffer space available >> ping: sendto: No buffer space available >> ping: sendto: No buffer space available >> ping: sendto: No buffer space available >> >> in dmesg: >> bge0: watchdog timeout -- resetting >> bge0: link state changed to DOWN >> bge0: link state changed to UP >> >> -- >> Best regards, >> Wishmaster mailto:wishmaster@velnet.ru >> > > What about other NIC chips from Broadcom? And how about the packets other > than icmp under the same load? > _______________________________________________ I have been unable to produce time outs with my current setup in 6.2-Release. bge0@pci3:0:0: class=0x020000 card=0x81491043 chip=0x165914e4 rev=0x11 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5750A1 NetXtreme Gigabit Ethernet PCI Express' class = network subclass = ethernet Reading the PR, I attempted triggering this through CVSing and through the above mentioned ping tests. So far nothing. The only issue I have seen using these NICs in 6.2R is if I nail up the NIC at 100baseTX full-duplex I sometimes loose connectivity. Nothing in the logs indicate watchdog timeouts or any other issue. I simply brought the NIC back down to auto-neg and all seems fine. I am assuming this is a incompatibility between the BGE and my switch, RS8000. I have a Asus P5MT-S with dual BGE NIC's Cheers, Jeff