On Tue, Jan 11, 2011 at 6:04 AM, Mike Tancsa <m...@sentex.net> wrote:
> On 12/24/2010 5:44 PM, Jan Koum wrote: > > hi Ivan and Mike, > > > > wanted to follow up and see if you found a solid long-term solution to > this > > bug. we are still seeing this problem in our 8.2 environment with ASPM > > already disabled. here is what we have: > > > > 1. motherboard is SuperMicro X8SIE-LN4F Intel Xeon: > > > > Hi Jack, > Looks like this problem is not completely gone :( Dear Mike and Jack, sadly the problem is not gone for us either. here is what we know so far: - we are running latest e1000 drivers from 8.2 - we have ASPM disabled and we have the following bios settings: http://camel.ethereal.net/~jkb/bios/ - we have updated our BIOS and IPMI to the latest firmware available from our ISP - we added hw.em.rxd=4096 and hw.em.txd=4096 to loader.conf (thanks Sean for this tip -- these settings made problem happen much less frequently but didn't go away completely) the ONLY thing sort of saving our butts right now is this cron job that runs every minute: if /sbin/ping -q -c 10 www.google.com> /dev/null; then echo "OK" >> /tmp/em1.out else date >> /tmp/em1.out echo "broken" >> /tmp/em1.out /sbin/ifconfig em1 down sleep 3 /sbin/ifconfig em1 up fi this is obviously no way to run a high performance web servers in a long term. as mentioned in my previous emails, let us know if you need any further information or if you have any debug code you want us to run in production. we are willing to do pretty much anything to get this issue fixed thanks _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
