Date: Mon, 11 Oct 2010 17:02:16 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Pyun YongHyeon <pyunyh@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: recent bge(4) changes causing problems Message-ID: <20101012000216.GA1554@troutmask.apl.washington.edu> In-Reply-To: <20101011231604.GI4607@michelle.cdnetworks.com> References: <20101011225331.GA2829@troutmask.apl.washington.edu> <20101011231604.GI4607@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 11, 2010 at 04:16:04PM -0700, Pyun YongHyeon wrote: > On Mon, Oct 11, 2010 at 03:53:31PM -0700, Steve Kargl wrote: > > > > In the time that it's taken me to compose this message > > the timeout has fire again. > > > > 15:47:07 kernel: bge0: watchdog timeout -- resetting > > 15:47:07 kernel: bge0: link state changed to DOWN > > 15:47:07 kernel: Limiting icmp unreach response from 439 to 200 packets/sec > > 15:47:08 kernel: Limiting icmp unreach response from 330 to 200 packets/sec > > 15:47:11 kernel: bge0: link state changed to UP > > 15:47:12 kernel: Limiting icmp unreach response from 214 to 200 packets/sec > > 15:47:13 kernel: Limiting icmp unreach response from 202 to 200 packets/sec > > 15:47:14 kernel: Limiting icmp unreach response from 238 to 200 packets/sec > > 15:49:42 kernel: bge0: link state changed to DOWN > > 15:49:44 kernel: bge0: link state changed to UP > > > > I not seen these icmp unreach response messages. > > > > The icmp unreach has nothing to do with bge(4). Check whether a > server that listens on an UDP port is still alive on your box. > What worries me is bge(4) watchdog timeouts. It looks like your > controller is BCM5704. I also have bge(4) regression report from > marius on sparc64. He said r213945 seemed to cause the issue and > I'm working on the issue. Could you also try the attached patch? The patch did not help. In fact, the icmp (which may be a side effect of the bge0 device wedging) has become much worse. SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad6s1a bge1: link state changed to UP bge0: link state changed to UP Limiting icmp unreach response from 3433 to 200 packets/sec Limiting icmp unreach response from 2017 to 200 packets/sec Limiting icmp unreach response from 2017 to 200 packets/sec Limiting icmp unreach response from 2049 to 200 packets/sec bge0: watchdog timeout -- resetting bge0: link state changed to DOWN Limiting icmp unreach response from 1962 to 200 packets/sec Limiting icmp unreach response from 2174 to 200 packets/sec Limiting icmp unreach response from 2180 to 200 packets/sec Limiting icmp unreach response from 2163 to 200 packets/sec bge0: link state changed to UP (removing 50 or so icmp messages). I don't know if the following helps, but thought I would include it here. troutmask:sgk[204] ping hpc PING hpc.apl.washington.edu (10.208.78.111): 56 data bytes ping: sendto: No buffer space available ping: sendto: No buffer space available ping: sendto: No buffer space available ping: sendto: No buffer space available -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101012000216.GA1554>