Alix crash when changing interfaces



  • I'm saddened to see that there are no new snaps for FreeBSD 7_2, but I'm sure I'll get over it.

    Tried the latest snapshot for FreeBSD 8 nanobsd 512 MB CF.
    pfSense-2.0-ALPHA-ALPHA-512mb-20091019-1122-nanobsd.img.gz

    I can trigger a core dump by doing the following.

    Log into web gui of the brand new install.

    Assign interfaces, add opt 1 and switch wan to VR0 and lan to VR1 (Opt 1 is VR2)
    Click save,

    Then before clicking the apply button, going to Interfaces -> opt 1, activating it, changing name to wireless and clicking apply.

    
    Enter an option:
    
    Fatal trap 12: page fault while in kernel mode
    fault virtual address   = 0x250
    fault code              = supervisor read, page not present
    instruction pointer     = 0x20:0xc04c8b07
    stack pointer           = 0x28:0xe32b57d0
    frame pointer           = 0x28:0xe32b5a18
    code segment            = base 0x0, limit 0xfffff, type 0x1b
                            = DPL 0, pres 1, def32 1, gran 1
    processor eflags        = interrupt enabled, resume, IOPL = 0
    current process         = 60901 (dhcpd)
    trap number             = 12
    panic: page fault
    Uptime: 2m53s
    Cannot dump. Device not defined or unavailable.
    Automatic reboot in 15 seconds - press a key on the console to abort
    Rebooting…
    
    

    I'll report back if the system continues to crash during normal use.
    Josh


  • Rebel Alliance Developer Netgate

    I've been seeing this too but haven't had a chance to investigate. Seems to be a problem in general with 2.0, as I've also had a panic when simply saving settings on the interfaces page, not assigning.



  • Hi,

    Its not only on the Alix, i have the same error when changing to the lagg0_vlan1 interface on a Dell PE1650.
    I got it on the snapshot op 25-10-2009.

    Hope this helps.

    Grts, Marcus



  • Yep, me too on Dell 1740, same snap. Its not reproduceable, so difficult to find. Thread is everytime another. But its not frequent.



  • I wouldn't say it is 2.0 related, I think it must be FreeBSD 8.0 related.  I have never seen a crash when testing the 7.2 snaps.

    Update, the crash seems to happen whenever I mess around in the interfaces section.

    I went and changed the wan interface to DHCP, and now the firewall is on a perpetual crash loop.  Just keeps crashing after openvpn setup (which I am not using)

    
    mount: /dev/ufs/cf : Operation not permitted
    ** /dev/ufs/cf
    ** Last Mounted on /cf
    ** Phase 1 - Check Blocks and Sizes
    ** Phase 2 - Check Pathnames
    ** Phase 3 - Check Connectivity
    ** Phase 4 - Check Reference Counts
    ** Phase 5 - Check Cyl groups
    19 files, 1234 used, 99821 free (29 frags, 12474 blocks, 0.0% fragmentation)
    
    ***** FILE SYSTEM MARKED CLEAN *****
     done.
    Creating symlinks…...done.
    Launching the init system... done.
    Initializing....vr0: link state changed to DOWN
    vr1: link state changed to DOWN
    vr2: link state changed to DOWN
    ................ done.
    Starting device manager (devd)...done.
    Loading configuration......done.
    Updating configuration...done.
    Cleaning backup cache...done.
    Setting up extended sysctls...done.
    Setting timezone...done.
    Starting syslog...done.
    Configuring WAN interface...done.
    Configuring LAN interface...done.
    Configuring WIRELESS interface...done.
    Configuring firewall......done.
    Starting PFLOG...done.
    Setting up gateway monitors...done.
    Syncing OpenVPN settings...done.
    
    Fatal trap 12: page fault while in kernel mode
    fault virtual address   = 0x250
    fault code              = supervisor read, page not present
    instruction pointer     = 0x20:0xc04c8b07
    stack pointer           = 0x28:0xe32b57d0
    frame pointer           = 0x28:0xe32b5a18
    code segment            = base 0x0, limit 0xfffff, type 0x1b
                            = DPL 0, pres 1, def32 1, gran 1
    processor eflags        = interrupt enabled, resume, IOPL = 0
    current process         = 24710 (apinger)
    trap number             = 12
    panic: page fault
    Uptime: 22s
    Cannot dump. Device not defined or unavailable.
    Automatic reboot in 15 seconds - press a key on the console to abort
    
    

    This looks like a different crash though, the first said Process = dhcpd, this one names apinger.  I don't know anything about reading these crash reports though, to know if that is significant.  I would be happy to give more information if more is needed.
    Thanks
    Josh



  • Found out that the crashes were more frequent as i only updated a ready installation, say snap from one week ago to the latest snap every day updating. When i did a fresh install without importing the config nor importing it via the webgui then nearly no more crashes. Strange but worked for me.
    Some numbers: On the updated machine i got in between 2-10 crashes in 3 hours, mostly when poking around with configurating all.
    A new install did maybe 1 or 2 crashes on the whole day - all time configuring via WebIF. Without doing anything on the machine no crash the whole day.
    A new install with imported config made between 1 and 3 crashes a day - without doing anything on the machine.
    All time on the same hardware.



  • I'm suffering from also with the same CRASH and ERROR when I simply release the IP on my WAN interface…. I've tried this on several machines now with the 10.25 Build.



  • This problem has been fixed.


Log in to reply