Kernel panic 4-5 Nov (i386)

wallabybob

I swapped interfaces so vr0 was my WAN and on three restarts I've hit the same panic: syncache: mbuf too small

FisherKing

I had wondered if it was just an issue w/ intel nics. Sounds like it's not that specific. Thanks Wallabybob.

Beerman

@PJ2:

Beerman, Wallabybob, I'm curious, what nic is assigned to your WAN? Or what driver is your WAN using?

My WAN is on vr2_vlan7. (ALIX Board)

CryoGenID

Any updates on this already?

We are also facing this problem here…
We stumbled over this "bug" (or whatever it is) a few weeks ago, when we tried to update to the newest snapshot...
Normally we used to update every few days and then suddenly we got this "Fatal Trap 12"-Error during the update...

It seems to be related to the update-system of pfSense, as it occurs either when checking for a new FW or trying to
download a new FW (using the Web-Interface or the Shell doesn't matter, the Trap comes anyway).
(I have attached a screenshot of our system)

We are using pfSense on >10 boxes, all with the same HW.
We have already switched the complete HW, but the problem stays the same (so I doubt that it is related to HW).

WAN1: ste0
WAN2: ste1
LAN: vr0

Hopefully there will be a fix soon (as we want to be able to upgrade again, also because of the now fixed PPTP-Bug)...

Thanks a lot and best regards,

Christian

pfSense_ERROR.jpg_thumb

CryoGenID

Hello everybody,

are there already any news on this?
As I can on other threads here, the "kernel panic"-problem seems to be happening to a lot of people…

Is this a bug in FreeBSD itself oder pfSense?

Thanks and best regards,

Christian

eri--

I am looking into it and will post when a solution is checked in.

CryoGenID

Perfect, ermal,

thank you :)

Best regards,

Chris

FisherKing

Yeah - thanks for looking into this ermal. It's hard to to much other testing when we can't do anything w/ the GUI. :)

Let us know if you need any other information. I can probably arrange remote access to the box if you can't reproduce this on your hardware.

mbartosch

Hi,

unhappy camper as well. Using the snapshot from 2010-11-18 I tried to configure an interface group, after this I got trapped in a kernel trap - reboot loop.

Running on a Soekris 5501.

FreeBSD/i386 bootstrap loader, Revision 1.1
(sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org, Thu Nov 18 07:57:55 EST 20)
…
vlan7: changing name to 'lagg0_vlan2920'
vlan8: changing name to 'lagg0_vlan2921'
vlan9: changing name to 'lagg0_vlan2930'
vlan10: changing name to 'lagg0_vlan2931'

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x14
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc095d504
stack pointer = 0x28:0xc33fbb48
frame pointer = 0x28:0xc33fbb78
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 = 11 (swi4: clock)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 29s

eri--

Give a shot at tomorrows snapshots.

FisherKing

Wahoo! Thanks ermal!

bEsTiAn

coming from my own thread :
http://forum.pfsense.org/index.php/topic,30207.msg157592.html
Unfortunately, using latest available snaphost, the crash repeats, after 1 or 2 minutes uptime

FisherKing

Yeah - I installed the 2010-11-25 update and experienced the same thing.

Ermal - do you need a backtrace from the current snapshot, or is what you have already sufficient?

mbartosch

Hi,

doesn't look good yet, using the snapshot from yesterday (sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org, Thu Nov 25 10:39:16 EST 20).

I just created the first LAGG interface from vr2 and vr3 on my Soekris 5501. Immediately after clicking the apply button in the web interface:

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:0xc09bbc2d
stack pointer = 0x28:0xe5dbec04
frame pointer = 0x28:0xe5dbec24
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 = 11 (irq9: vr2)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 17h58m38s
Cannot dump. Device not defined or unavailable.

eri--

Hmmm sorry i thought i had pushed the patch to repo!
Just did though try with next snaps.

jlepthien

Is this probably the same issue that hits me here: http://forum.pfsense.org/index.php/topic,30465.0.html

mbartosch

Hi,

@ermal:

Hmmm sorry i thought i had pushed the patch to repo!
Just did though try with next snaps.

just to give a quick head-up: I have tried the latest snapshot and it seems to have fixed the problem. No kernel panic yes with extensive VLAN on LAGG interfaces config fiddling (but no actual traffic over these yet).

Thanks for fixing this,

Martin

bEsTiAn

same here
uptime 2 hours and increasing :)

thanks a lot once more for the hard and continuous work

jlepthien

Still not possible for me to add my second wireless interface…

See http://forum.pfsense.org/index.php/topic,30465.0.html

Still rebooting then...

eri--

Go over to your thread jlepthien do not hijack this one.