RE: AW: [pfSense Support] em0: Watchdog timeout -- resetting
Just thought I'd update with what I'm doing on this issue; since this list is indexed, maybe this breadcrumb trail will help out another poor sap along the way. Tomorrow, I plan to explore the following. I'm not sure why these would cause issues, but grasping at straws is good for the soul. -Checksum offloading (disable per http://downloadcenter.intel.com/Detail_Desc.aspx?agr=YProductID=2788DwnldID=11848strOSs=38OSFullName=OS%20Independentlang=eng) - TSO (disable per above link) - Polling (tweak and toggle per above link) - Try SMP Kernel (Why not?) - Update to latest BIOS (That document also mentions an 'update to the latest BIOS', and references the Linux Firmware Kit project. http://linuxfirmwarekit.org/ - the difference is only a revision code, but perhaps the fix is in there. SuperMicro's BIOS update release notes apparently require an NDA (Why!?)) Running OpenBSD latest (4.4), I discovered that I don't receive watchdog timeouts - instead, I am just seeing extremely poor performance (70kbps), where the onboard NICs deliver the expected near-wirespeed. Will update. Thank You, Nathan Eisenberg Sr. Systems Administrator Atlas Networks, LLC Atlas Networks is an Atlas Accelerator Company -Original Message- From: Nathan Eisenberg [mailto:nat...@atlasnetworks.us] Sent: Monday, January 05, 2009 5:32 PM To: 'support@pfsense.com' Subject: RE: AW: [pfSense Support] em0: Watchdog timeout -- resetting Any thoughts on a next step in troubleshooting? I'm running out of ideas. Setting the port speed and duplex has no effect. Thank You, Nathan Eisenberg Sr. Systems Administrator Atlas Networks, LLC Atlas Networks is an Atlas Accelerator Company -Original Message- From: cbuech...@gmail.com [mailto:cbuech...@gmail.com] On Behalf Of Chris Buechler Sent: Monday, January 05, 2009 5:14 PM To: support@pfsense.com Subject: Re: AW: [pfSense Support] em0: Watchdog timeout -- resetting On Mon, Jan 5, 2009 at 2:02 PM, Nathan Eisenberg nat...@atlasnetworks.us wrote: Admittedly, I did not expect to run into hardware/driver issues when I was buying these NICs. :( In fact, that's exactly the reason I went with Intel HW in the first place. Usually that's an accurate assessment. This card is newer than the driver in FreeBSD 7.0 though. And it might not be network driver related at all, might be specific to some other hardware component in relation or combination with that card. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
RE: AW: [pfSense Support] em0: Watchdog timeout -- resetting
I agree with both of your statements. The portfast option isn't a solution, but it does make debugging this issue a lot less painful. Admittedly, I did not expect to run into hardware/driver issues when I was buying these NICs. :( In fact, that's exactly the reason I went with Intel HW in the first place. Thank You, Nathan Eisenberg Sr. Systems Administrator Atlas Networks, LLC Atlas Networks is an Atlas Accelerator Company -Original Message- From: Paul Mansfield [mailto:it-admin-pfse...@taptu.com] Sent: Monday, January 05, 2009 3:01 AM To: support@pfsense.com Subject: Re: AW: [pfSense Support] em0: Watchdog timeout -- resetting Fuchs, Martin wrote: And perhaps try to set the port speed in pfsense AND the switch, e.g. 1000MBit FD... Sometimes this helps, too Once you start setting port speeds to fix rates and duplex you're going down a long and slippery slope, it's best to avoid it unless there's a proven good reason! -Ursprüngliche Nachricht- Von: apiase...@midatlanticbb.com [mailto:apiase...@midatlanticbb.com] Can't help with your pfsense problem, but it might help to configure this on your switch. spanning-tree portfast Configured on your cisco switch will change the port to a forwarding state immediately. this might help hide the symptom of the interface bouncing but isn't really a cure - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: AW: [pfSense Support] em0: Watchdog timeout -- resetting
Fuchs, Martin wrote: And perhaps try to set the port speed in pfsense AND the switch, e.g. 1000MBit FD... Sometimes this helps, too Once you start setting port speeds to fix rates and duplex you're going down a long and slippery slope, it's best to avoid it unless there's a proven good reason! -Ursprüngliche Nachricht- Von: apiase...@midatlanticbb.com [mailto:apiase...@midatlanticbb.com] Can't help with your pfsense problem, but it might help to configure this on your switch. spanning-tree portfast Configured on your cisco switch will change the port to a forwarding state immediately. this might help hide the symptom of the interface bouncing but isn't really a cure - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: AW: [pfSense Support] em0: Watchdog timeout -- resetting
On Mon, Jan 5, 2009 at 2:02 PM, Nathan Eisenberg nat...@atlasnetworks.us wrote: Admittedly, I did not expect to run into hardware/driver issues when I was buying these NICs. :( In fact, that's exactly the reason I went with Intel HW in the first place. Usually that's an accurate assessment. This card is newer than the driver in FreeBSD 7.0 though. And it might not be network driver related at all, might be specific to some other hardware component in relation or combination with that card. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
RE: AW: [pfSense Support] em0: Watchdog timeout -- resetting
Any thoughts on a next step in troubleshooting? I'm running out of ideas. Setting the port speed and duplex has no effect. Thank You, Nathan Eisenberg Sr. Systems Administrator Atlas Networks, LLC Atlas Networks is an Atlas Accelerator Company -Original Message- From: cbuech...@gmail.com [mailto:cbuech...@gmail.com] On Behalf Of Chris Buechler Sent: Monday, January 05, 2009 5:14 PM To: support@pfsense.com Subject: Re: AW: [pfSense Support] em0: Watchdog timeout -- resetting On Mon, Jan 5, 2009 at 2:02 PM, Nathan Eisenberg nat...@atlasnetworks.us wrote: Admittedly, I did not expect to run into hardware/driver issues when I was buying these NICs. :( In fact, that's exactly the reason I went with Intel HW in the first place. Usually that's an accurate assessment. This card is newer than the driver in FreeBSD 7.0 though. And it might not be network driver related at all, might be specific to some other hardware component in relation or combination with that card. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: AW: [pfSense Support] em0: Watchdog timeout -- resetting
On Mon, Jan 5, 2009 at 8:32 PM, Nathan Eisenberg nat...@atlasnetworks.us wrote: Any thoughts on a next step in troubleshooting? As I suggested earlier in this thread: http://doc.pfsense.org/index.php/Policy_on_FreeBSD_issues Most frequently these issues are driver bugs. We do not have any developers who work on drivers in FreeBSD, and cannot assist with such issues. In these cases, we suggest installing a stock FreeBSD 7.0 release on your hardware, replicating the problem, and reporting it to the appropriate FreeBSD list. This is the only way your problem will be resolved, and even at that will only be resolved in future releases. Alternatively, use different hardware. You may be able to get away with posting questions to freebsd-net using pfSense since it's close to the same as 7.0 release, with no kernel changes related to network drivers. My guess is you would be asked to try 7.1, or RELENG_7, or HEAD to see if the problems persist there. You won't be able to easily do that without running a stock FreeBSD. My guess is this is something specific to this new card that's been addressed with a newer driver, which probably isn't able to be reasonably added to a pfSense install. Hence you may be stuck for the time being. You can try 2.0, which is based on FreeBSD 7.1 and see if that makes any difference. Aside from that, I'm out of suggestions aside from going to the freebsd-net list and hoping the Intel employee who works on the em driver and posts there will offer some suggestions. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
