VIA Based systems - pfSense 1.2.3-release, Random reboots

  • I updated to 1.2.3-release on my VIA EPIA SP13000 and EN15000 systems - and they are rebooting at unpredictable intervals.  Snapshots from September are more stable on this VIA hardware.  I was wondering if anyone else is experiencing this.  I will gather some more info using the debug kernel.

  • It might be helpful to know what else you have in those systems.

    I have a system with 800MHz VIA C3 CPU, ath, rl, rum, udav and vr NICs. I updated to 1.2.3-RELEASE about 8.5 hours ago and it hasn't crashed yet. It was previously running a late 1.2.3 snapshot build and had an uptime of over 10 days before I upgraded to 1.2.3-RELEASE.

  • In one system, the motherboard is the VIA EPIA SP13000 (last bios: 1.04), and a dual-nic Soekris pci card (sis). It has 512 MB of RAM, 40 GIG HDD…Nothing else to report (no wireless for example).  Are there any bios level configs that I should pay attention to?

    September snapshots didn't reboot, but since then - its been rebooting.

    What do I need to do once I install the developer kernel to capture the information that would help a developer figure this one out?

  • Rebel Alliance Developer Netgate

    At some point, VIA padlock support was added back in. It's possibly related to that, but without more detail it's hard to say why.

  • How do I disable the padlock?

  • I'm having a similar problem with an older via EPIA ME6000G board (600mhz Eden, fanless) 256MB ram - onboard vr for wan, fxp PCI card for lan interface (Don't remember model)
    Running the 1.2.3 release, embedded on a 4G CF card in a CF-IDE adapter (created with physicalwrite)

    Had m0n0wall running on it for about 2 weeks (On a 128meg CF), working flawlessly.

    I get random reboots, but more often when I'm using the web interface. The firewall menu items in particular seem to trigger it.

    I figured I was doing something wrong and was going to try an HD install. Wonder if I should try one of the 2.0 betas.

  • It won't make a difference if its HDD or Flash - I've had it reboot under both circumstances.  This version should be stable for you (from jimp):

    Initially I suspected padlock, but enabled or disabled - the reboot still triggers.  Something else changed in the code, as ALL my VIA based systems are unstable even with 1.2.3-release.  We would have to use the developer kernel to gather more details, so that the pfsense team can properly identify and address this issue.

    I don't know about 2.0 beta, you might have many other issues.

  • My VIA C3 system is pretty stable. It now been up for over 3.25 days. Last reload was recovery after the electrician cut the power to install air conditioning.

    I don't have statistics but my impression is that 1.2.3 release is probably not quite as stable for me as the 1.2.3 snapshots of about 6 months ago but far more stable than the snapshots of 3 to 4 months ago.

    What sort of uptimes are you seeing?

    Are you doing something that would use the VIA padlock facility (VPNs maybe)? I'm not using VPNs and I use http for the web GUI. (Maybe https uses padlock if available; I don't know.)

  • I use both https and IPsec VPNs (AES).  IPsec does make use of padlock, I am pretty sure that https does as well (via openssl?). The most likely culprit is the padlock, but using jimp's snapshot w/padlock has proven stable thus far.

  • 1.2.3RC i had a 120 some odd  day uptime on my Via Eden C3 1Ghz.
    only time i have ever had a reboot is if i manually did the reboot, never an issue.
    Just put the 1.2.3-release on my system today and its been up for 8 hours just fine now

  • For what it's worth, I continued to have random reboots once a week or so (Using it as a home router and vpn gateway, so not a massive deal)

    .. Until I replaced the system's power supply. The system had been running of a tiny.. Something or other PSU I pulled from a defunct budget PC. The case I've got the via board in is tiny and a standard PSU doesn't fit. I come to find out there is actually a semi-standard matx psu formfactor although most matx cases ive seen use standard size PSUs) I'm planning to replace the epia with something newer anyway, like a newish atom or full-on LGA775 socket board.

    End result:
    30 bucks. 20+4 pin power connector, 4 pin 12 cpu power, sata power, everything. Even a 6+2 pin pci-e power plug if I wanted a high-end video card in my.. Er.. Router.

    Haven't had a reboot since. Don't know if the old PSU was failing, or if pfsence caused an increased load which the old PSU wasn't handling, or what. System was always stable running various flavors of linux and monowall.

  • Rebel Alliance Developer Netgate

    FreeBSD is known for pushing the limits of hardware, and even though m0n0 also uses FreeBSD, it's really stipped down (much more so than pfSense)

    It's likely it wasn't being utilized to its full potential on the other systems, and pfSense just happened to run it harder.

  • Has there been any progress on this? I have a VIA box and noticed an unexpected reboot today, after upgrading earlier this week.

Log in to reply