That means probably mbuf exhaustion.
Can you try up kern.ipc.nmbclusters="131072"





On Tue, Jun 4, 2013 at 5:04 PM, Nishant Sharma <[email protected]>wrote:

> Hi,
>
> The pfSense full install on Intel Atom D450, 4GB RAM, one re0, two em
> cards with VLANs on em1 has crashed 3-4 times in the past 3 days.
>
> I had submitted the crash reports as well, but I am not sure if it was
> considered as I am not running the latest version.
>
> I have again submitted a crash report at 1500 GMT today.
>
> Crash report's interesting parts (from my understanding) are:
>
> db:0:kdb.enter.default>  show pcpu
> cpuid        = 0
> dynamic pcpu    = 0x51d080
> curthread    = 0xc77aa280: pid 0 "em1 taskq"
> curpcb       = 0xede4ed90
> fpcurthread  = none
> idlethread   = 0xc758f780: pid 11 "idle: cpu0"
> APIC ID      = 0
> currentldt   = 0x50
>
> ====================
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; apic id = 00
> fault virtual address   = 0x420
> fault code              = supervisor read, page not present
> instruction pointer     = 0x20:0xc0515c79
> stack pointer           = 0x28:0xede4e814
> frame pointer           = 0x28:0xede4e82c
> 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         = 0 (em1 taskq)
>
> ==========================================
>
> I have made following parameters set on /boot/loader.conf.local:
>
> kern.cam.boot_delay=10000
> kern.ipc.nmbclusters="131072"
> hw.em.num_queues=1
> hw.em.fc_setting=0
>
> Is my guess correct that this seems to be problem with the em1 NIC? Or I
> should be suspecting RAM as well?
>
> Thanks in advance.
>
> Regards,
> Nishant
>
> _______________________________________________
> List mailing list
> [email protected]
> http://lists.pfsense.org/mailman/listinfo/list
>
_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list

Reply via email to