Unfortunately, they aren't completely gone. I've been able to consistently
get watchdog timeouts on 1.2.3 since Monday (including the official RC1
released yesterday) by simply browsing the web interface on the LAN side (I
usually use re2) using Internet Explorer 7 (All I ever do is just click
between options in the GUI, and I get them after 10-15 clicks). The patch
that was put in definitely helped, though (a lot). I'm still working with
Pyun (the maintainer of the FreeBSD Realtek driver) on a solution. I do have
yet to reproduce watchdog timeouts on 2.0, however, although one person has
reported that 2.0 gives him timeouts (see
http://forum.pfsense.org/index.php?topic=15669). I don't yet have an
explanation as to why I get timeouts in 1.2.3 and not in 2.0, but I'm
working on figuring out why.

Dimitri Rodis
Integrita Systems LLC 
http://www.integritasystems.com


-----Original Message-----
From: Tim Nelson [mailto:[email protected]] 
Sent: Thursday, April 23, 2009 7:43 PM
To: [email protected]
Subject: Re: [pfSense Support] Attention Firebox X Series Users - Testing
Needed

Well, I threw the latest 1.2.3-RC1 on a CF card and booted up my X500. 
I've been passing all sorts of traffic through it (WAN and OPT1 bridge) 
with no pauses in traffic or watchdog timeouts. My traffic has been 
anything from netperf tests TCP and UDP, raw FTP traffic, random web 
browsing, and some very heavy bittorrent traffic (Latest Ubuntu released 
today :-) ). In fact, I've run some of those tests concurrently.

Thus far, after saturating the 100mbit link through the bridge for 
nearly 4 hours, I've yet to see a problem. I can post any additional 
information you need, just let me know. This X500 is 100% stock with the 
exception of the CF card. The 64MB CF was a bit small so it was replaced 
with a Sandisk 256MB I had lying around.

Out of curiosity, what is the largest DIMM these units will accept? They 
come with 256MB which seems a bit light. I'd like to throw a 1GB stick 
in if possible.

--Tim

Dimitri Rodis wrote:
> Attention Firebox X500/700/1000 Users using pfSense:
> 
>  
> 
> Watchdog timeouts getting' you down? Thinkin' about throwin' that old 
> Firebox in to the fireplace? Don't do that just yet! J
> 
>  
> 
> Thanks to the pfSense devs, along with Pyun YongHyeon, the maintainer 
> for the FreeBSD Realtek network driver, it appears that we may have 
> solved the issue with the watchdog timeouts on the Realtek 8139C+ chips 
> that are used in these units. For the past couple of days, I have worked 
> with Pyun, and yesterday Pyun sent me a patch, and that patch was 
> committed to the 1.2.3 snapshot builds, as well as to the 2.0 alpha 
> snapshot builds by the pfSense devs, and is part of any snapshot build 
> as of yesterday (4/17) at 2pm Eastern time, or later.
> 
>  
> 
> Snapshot builds can be downloaded from
> 
> http://snapshots.pfsense.org/FreeBSD7/RELENG_1_2/
> 
> or
> 
> http://snapshots.pfsense.org/FreeBSD7/HEAD/
> 
>  
> 
> I have been testing a build with this patch since yesterday, and have 
> yet to see a single watchdog timeout on my interfaces-and no 
> modifications to loader.conf have been made. This is a default 
> install-no special options have been set anywhere.
> 
>  
> 
> If at all possible, please try to install a recent snapshot build on 
> your firebox units (those of you that have them) and test this patch. 
>  If you do still receive watchdog timeouts, please let me know either on 
> this list, or off-list. Either way, please try to detail what you were 
> doing when the watchdog timeout occurred so that we can try to reproduce 
> it, and Pyun can fix it.
> 
>  
> 
> Thanks to all that have helped, and thanks to those that are willing to 
> test!
> 
>  
> 
> Dimitri Rodis
> 
> Integrita Systems LLC
> 
> http://www.integritasystems.com
> 
>  
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Commercial support available - https://portal.pfsense.org

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to