From owner-freebsd-net@FreeBSD.ORG Wed Mar 6 10:00:38 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 0E850C2A for ; Wed, 6 Mar 2013 10:00:38 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (unknown [IPv6:2001:470:1f09:14c0::2]) by mx1.freebsd.org (Postfix) with ESMTP id 575CFE5D for ; Wed, 6 Mar 2013 10:00:37 +0000 (UTC) Received: from bsdrookie.norma.com. ([IPv6:fd00::726]) by elf.hq.norma.perm.ru (8.14.5/8.14.5) with ESMTP id r26A0YB7029546 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Wed, 6 Mar 2013 16:00:35 +0600 (YEKT) (envelope-from emz@norma.perm.ru) Message-ID: <513713C2.1000007@norma.perm.ru> Date: Wed, 06 Mar 2013 16:00:34 +0600 From: "Eugene M. Zheganin" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: FreeBSD 9.1-RELEASE + bge0 == watchdog timeout References: <201302241106.42477.vegeta@tuxpowered.net> <20130225082042.GB1426@michelle.cdnetworks.com> <512CF97B.8030805@norma.perm.ru> <20130227020123.GA3581@michelle.cdnetworks.com> <512DE968.4020409@quip.cz> <20130228053558.GA1474@michelle.cdnetworks.com> <5136D89D.4000902@norma.perm.ru> <20130306062658.GC1483@michelle.cdnetworks.com> In-Reply-To: <20130306062658.GC1483@michelle.cdnetworks.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (elf.hq.norma.perm.ru [IPv6:fd00::30a]); Wed, 06 Mar 2013 16:00:35 +0600 (YEKT) X-Spam-Status: No hits=-97.8 bayes=0.5 testhits RDNS_NONE=1.274, SPF_SOFTFAIL=0.972,USER_IN_WHITELIST=-100 autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on elf.hq.norma.perm.ru X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Mar 2013 10:00:38 -0000 Hi. Hi. On 06.03.2013 12:26, YongHyeon PYUN wrote: > If you were using latest stable/8, the result would be same on > CURRENT. > How frequently do you see the watchdog timeouts? Is there way to > reproduce it? > Would you show me the output of dmesg (bge(4) and brgphy(4) only) > and "pciconf -lcbv"? I upgraded one om my routers 2 days ago to 8.3-STABLE, and got today a freeze. Uptime was less than a day. I have like dozens of these IBM system x3250, all of them run various 8.2-STABLE's, that's why I worry that much. I don't know if this is triggered by some of my actions. These routers run gre/ipsec, dirrerent routing stuff (quagga, bird), proxies and pf. In 2011/early 2012 I saw similar watchdog issues on these machines, and I disabled the tso on them. I don't know whether this is a coincidence or it really helps, but after that I didn't see these watchdog issues until today. I've also discovered that this particular server is running some old bioses/firmwares including the fact that it misses some NetXtreme updates available from IBM. Would applying such updates resolve the situation ? I am ok with that fact that I cannot run ipmi/sol on these machines, but it would be nice if this watchdog issue could be somehow resolved. Furthermore, I have some spare machines that I can provide full access to, including ipkvm stuff. Since the machine is only partially freezing, I cannot even rely on the ichwd and watchdogd to reboot it. pciconf (there's two controllers in this server, I use the first, but anyway): bge0@pci0:2:0:0: class=0x020000 card=0x03781014 chip=0x165a14e4 rev=0x00 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom NetXtreme BCM5722 Gigabit (94309)' class = network subclass = ethernet bar [10] = type Memory, range 64, base 0xe8200000, size 65536, enabled cap 01[48] = powerspec 3 supports D0 D3 current D0 cap 03[50] = VPD cap 09[58] = vendor (length 120) cap 05[e8] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[d0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) speed 2.5(2.5) ecap 0001[100] = AER 1 0 fatal 0 non-fatal 2 corrected ecap 0002[13c] = VC 1 max VC0 ecap 0003[160] = Serial 1 001a64fffe21962d ecap 0004[16c] = Power Budgeting 1 bge1@pci0:3:1:0: class=0x020000 card=0x026f1014 chip=0x16c714e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5703A3 NetXtreme Gigabit Ethernet' class = network subclass = ethernet bar [10] = type Memory, range 64, base 0xe8400000, size 65536, enabled cap 07[40] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split transaction cap 01[48] = powerspec 2 supports D0 D3 current D0 cap 03[50] = VPD cap 05[58] = MSI supports 8 messages, 64 bit dmesg: bge0: mem 0xe8200000-0xe820ffff irq 16 at device 0.0 on pci2 bge0: CHIP ID 0x0000a200; ASIC REV 0x0a; CHIP REV 0xa2; PCI-E miibus0: on bge0 bge0: Ethernet address: 00:1a:64:21:96:2d bge0: [FILTER] bge1: mem 0xe8400000-0xe840ffff irq 21 at device 1.0 on pci3 bge1: CHIP ID 0x00001100; ASIC REV 0x01; CHIP REV 0x11; PCI on PCI-X 33 MHz; 32bit miibus1: on bge1 bge1: Ethernet address: 00:1a:64:21:96:2e bge1: [ITHREAD] [emz@omega:~]# cat /var/run/dmesg.boot | egrep 'bge|brg' bge0: mem 0xe8200000-0xe820ffff irq 16 at device 0.0 on pci2 bge0: CHIP ID 0x0000a200; ASIC REV 0x0a; CHIP REV 0xa2; PCI-E miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge0: Ethernet address: 00:1a:64:21:96:2d bge0: [FILTER] bge1: mem 0xe8400000-0xe840ffff irq 21 at device 1.0 on pci3 bge1: CHIP ID 0x00001100; ASIC REV 0x01; CHIP REV 0x11; PCI on PCI-X 33 MHz; 32bit miibus1: on bge1 brgphy1: PHY 1 on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge1: Ethernet address: 00:1a:64:21:96:2e bge1: [ITHREAD] Thanks. Eugene.