Kernel Panic
-
You have any ftp/pptp traffic going in?
-
@ermal:
You have any ftp/pptp traffic going in?
Only very little ftp, but that doesn't seem to trigger it.
I do, however, have quite a bit of http traffic (~300-600mbit) from a million or so clients. -
Nope, still a problem. I updated the carp backup to the latest snapshot (Jan 26, with the master still on Jan 24), added a new VIP addr on the master, and the backup immediately panic'd.
-
Hi! this is my first post on this forum.
I have been using pfsense for one year, I have installed it on a alix 2d3 an on a jetway nc9c-550lf. since 1 month pfsense rebooting itself on both installation.
The snapshot is 2.0-BETA5 (i386) built on Wed Jan 26 09:44:03 EST 2011
On screen I see this messages:
Fatal trap 12: page fault while in kernel mode
cpuid= 1; apic id= 01
fault virtual address = 0x0
fault code = supervisor read, page not present
instruction pointer = 0x20:0x0
stack pointer = 0x28:8xc5610b80
frame pointer = 0x28:8xc5610b8c
code segment = base 0x0, limit 0xfffff, type0x1b
= DPL 0, pres 1, def32 1, gran1
processor eflags= interrupt enable, resume,IOPL = 0
current process= 12(swi5: + ) -
Without the output of "bt" at that debug prompt, it's hard to say. Yours doesn't look like the other panics in this thread.
-
the next time I will try the bt command and i will post the screen.
thx
-
the next time I will try the bt command and i will post the screen.
…after you install the dev kernel. Instructions are on the wiki (for full installs) or about 2 screens back for embedded.
-
I'm working on getting text dumps working so that even people on a normal install will have the crash dump analysis left in /var/crash after an auto reboot. Hitting a couple roadblocks, though.
-
I think I am running into this issue. I do not have the dev kernel installed. Thought it was a bad hard drive, Had a lot of drive errors after rebooting a few times until it no longer booted. Replaced the drive. Machine ran fine for a couple hours off network. As soon as traffic started hitting it it quit within a few minutes. After a reboot it passed traffic a few minutes and quit again.
Had been running the Dec31 Full i386(it ran fine). Updated to Jan 21 over the weekend. Issue started yesterday. Loaded Jan 26 amd64 today and still see the same behavior.
Does this sound similar to what everyone else is seeing? Where can I find the Dec 31 snap, i must have erased it?
I have another box at the office and some spare public IP's. I can set it up for testing if any of the devs want access (when its up).
Let me know.
This is on a 5015A-EHF-D525 w/4G RAM
http://www.supermicro.com/products/system/1U/5015/SYS-5015A-EHF-D525.cfm -
Text dumps will be a nice feature. Thanks for working on that Jimp.
-
On the setup we have where secondary panics used to be replicable it's fixed now.
jnorell: can you email me a backup of your config? cmb at pfsense dot org
-
Uploaded a new kernel http://files.pfsense.org/kernel_new.gz
Beaware that you need to be updated to the latest snapshot before using this kernel otherwise you will get hangs. -
Is this just for the intel em chip fix? or will it also work on my Soekris vr chip?
-
@ermal:
Uploaded a new kernel http://files.pfsense.org/kernel_new.gz
Is that for full installs? amd64?
-
That is for full install 32bits.
It should work even on alix boards i am not sure on others since i cannot build for those now.It should fix all the panics in vr, em or other nics.
-
Should we be using this snap and later?
pfSense-Full-Update-2.0-BETA5-i386-20110126-0422.tgz 26-Jan-2011 09:47 83M -
Yes.
-
Done.
-
Will there be an amd64 version of the fix?
-
This is what I am supposed to do, correct?
/etc/rc.conf_mount_rw fetch http://files.pfsense.org/kernel_new.gz cp kernel_new.gz /boot/kernel/kernel.gz
EDIT: Modified code to reflect below change