I really appreciate your help, but since the machine in question is a mission critical router in a production environment, with many housed customers connected, I cannot really experiment with its settings anymore.
Both my superiors and the customers are quite upset by the recent problems, I am sure you will understand.
We tried to reproduce the problem with identical HW and SW installation in a lab environment, but we were not successful. I apologize, but I cannot test your patch on our production router. Best Regards Daniel Ryslink On Thu, 17 Aug 2006, Pyun YongHyeon wrote:
On Thu, Aug 17, 2006 at 09:45:50AM +0200, Daniel Ryslink wrote: > > Hello, > > Thank you very much for your assistance. > > I am happy to report that we have been able to fix this problem. I just > wanted to wait a day or two to be sure that it won't resurface again. > > The last steps we did were: > > 1) Upgrade SuperMicro SS5015M-T BIOS from version 1.1 to version 1.1a > 2) Inclusion of 'debug.mpsafenet=0' into /boot/loader.conf suggested in > this mailing list. > > I would guess that the step 2 was what really solved the problem. > Hmm... I'd like to know whether my patch help or not. Step 2 you mentioned is not the way to go. We're trying very hard to remove giant locks in every places on FreeBSD. > Best Regards > Daniel Ryslink > > On Thu, 17 Aug 2006, Pyun YongHyeon wrote: > > >On Fri, Aug 11, 2006 at 10:06:00AM +0200, Daniel Ryslink wrote: > >> > >> Hello, > >> > >> We have currently upgraded one of our routers to Gigabit connectivity and > >> FreeBSD 6.1 Release. > >> > >> The hardware is Supermicro SuperServer 5015M-T - we have tried both the > >> integrated NIC and yet another external Intel NIC - specifically > >> > >> Intel PRO/1000 MT Dual Port Server Adapter > >> PWLA8492MT > >> > >> The problem is that several times a day, the following appears in > >> messages: > >> > >> Aug 11 08:41:44 b2 kernel: em0: watchdog timeout -- resetting > >> > >> accompanied with a loss of connectivity lasting for several seconds. > >> > >> We have tried using both the default driver that came with the FreeBSD > >> installation as well as the newest driver from Intel dated 2th April 2006 > >> compiled as a module, but the problem still persists. > >> > >> If anyone encountered the problem and has a solution, I would be very > >> grateful. > >> > > > >Because I can't reproduce it here and I failed to find a possible > >cause of the issue. > >As a last resort would you give attached patch a try? > >The patch was generated against latest stable. > > > >-- > >Regards, > >Pyun YongHyeon > > -- Regards, Pyun YongHyeon
_______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
