Date: Mon, 24 Dec 2012 12:28:42 +0600 From: Tsaregorodtsev Denis <telemat@extrim.it> To: Ryan Stone <rysto32@gmail.com> Cc: freebsd-net <freebsd-net@freebsd.org> Subject: Re: 'no buffer space available' after switch goes down on freeBSD 7.3 Message-ID: <50D7F61A.5020304@extrim.it> In-Reply-To: <CAFMmRNy26AvdJjW9N4zPNPYrVYn1a2Qr8W5qy9MTV_30dvCqCA@mail.gmail.com> References: <50D45282.5080708@extrim.it> <CAFMmRNy26AvdJjW9N4zPNPYrVYn1a2Qr8W5qy9MTV_30dvCqCA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you for answer. I tried to repeat the situation on a non-prodaction machine, but hadn't success. I made this steps (from thread http://freebsd.1045724.n5.nabble.com/ping-sendto-No-buffer-space-available-td5746337.html) 1. Start a ping flood: ping -f <other-machine-ip> 2. Let it run for a few seconds. 3. Disconnect the cable. 4. After a while, you should see "no buffer space" error. 5. Stop ping flood. 6. Re-connect the cable and wait 10 seconds. 7. Start a normal ping. Error messages should show up again. At the end i had 'no buffer space available', but when i started ping test machine from other machine, test machine became available and network started to work. May be there is something wrong in freebsd 7.3 em driver and updating to freebsd 9 may resolve the problem, but i would like to know exactly. Denis On 21.12.2012 22:08, Ryan Stone wrote: > > On Fri, Dec 21, 2012 at 7:13 AM, Tsaregorodtsev Denis > <telemat@extrim.it <mailto:telemat@extrim.it>> wrote: > > Hello, > > I maintenance ISP's DNS server which works under FreeBSD 7.3 and > BIND 9.9.1-P4. The network adapter is Intel(R) PRO/1000 Network > Connection, driver - em. The server is connected to a Cisco 6500 > switch. Sometimes the switch goes down (for maintenance) and is > unavailable for 10 minutes. After the switch goes up the server is > still unavailable through IP. When I open an IPMI console on the > server and enter the ping command, I receive "no buffer space > available" error message. And the network doesn't work until the > server reboot. > I tried to google this and found that the problem can be solved by > increasing nmbclusters parameter. But I want to understand why > this problem appears when the switch is rebooting . May be you can > suggest something? > > Best regards, Tsaregorodtsev Denis > > _______________________________________________ > freebsd-net@freebsd.org <mailto:freebsd-net@freebsd.org> mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to > "freebsd-net-unsubscribe@freebsd.org > <mailto:freebsd-net-unsubscribe@freebsd.org>" > > > Do you have a non-production machine you can test with? Can you > confirm that the follow (compile-tested only) patch of 7.3 resolves > the issue: > > http://people.freebsd.org/~rstone/patches/e1000_link.diff > <http://people.freebsd.org/%7Erstone/patches/e1000_link.diff>;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50D7F61A.5020304>