Dummynet - kernel crash: Fatal trap 12, 26th apr snapshot



  • Hello,

    pfSense 2.0 generates a kernel crash in this situation:

    Snapshot: 26th apr 2010
    Hardware: Celeron 430 1.8ghz - 1GB RAM (tested) - 80GB HDD
    NICs: 1x ale Atheros gigabit, 1x rl Realtek 100mbps

    Relevant Configuration:
    pfsense SMP kernel
    WAN: PPPoe
    LAN: Static, DHCP, limiter dummynet enabled with per-host mask, Some traffic shaper rules enabled also

    Crash message, copied from the console:

    fatal trap 12: page fault while in kernel mode
    cpuid = 0; apic id = 00
    fault virtual address = 0xc
    fault code = supervisor read, page not present
    instruction pointer = 0x20:0xc0a02296
    stack pointer = 0x28:0xed20cb30
    frame pointer = 0x28:0xed20cb5c
    code segment = base 0x0, limit 0xfffff, type 0x1b
    	= DPL 0, pres 1 , def32 1, gran 1
    processor eflags = interrupt enabled, resume, IOPL = 0
    [b]current process = 0 (dummynet)[/b]
    [thread]
    Stopped at m_copym+0x36: movl 0xc(%esi), %eax
    
    Some relevant information:
    · When ale0 (Atheros NIC) is configured as LAN, the GUI sometimes fails to load or load parcially, one or more refreshes solve the problem
    · When rl0 (Realtek NIC) is LAN, the GUI works ok all the time.
    · Connecting just one PC to LAN doesn't trigger the issue, when two or more PC are on LAN, it crashes one or two minutes after boot
    · When booting, after the "Boot up complete" message, and speaker tune, pfsense doesn't show the "pfSense console setup" menu on console, but the system works ok one or two minutes and crash if more than one PC is in LAN.
    · The same configuration in an older PC (Pentium II) with rl0 and dc0 NIC drivers and a late-march snapshot work ok with no crash.[/thread]
    


  • can you do a 'bt' at the debugger prompt?



  • This is a picture of 'bt' at the debug prompt:




  • Should be fixed on latest snapshots.



  • Thanks, what was the cause of this issue?



  • i also have a kernel crash with the rt2860, but this was not be fixed by the last snapshot :(




  • Its a driver issue yours.
    You will have more luck on forums.freebsd.org



  • I tried to debug this with the people who made the driver..

    he said this problem shouldnt occur, i think there must be a problem with the version of freebsd8.. are there any restrictions in freebsd for pfsense?

    i had to take the src-> base, sys from freebsd 8.0-release, because i couldnt find them for releng_8, is this a possible reason for this problem? are there any possibilities to get this distributions for the right version?


Locked