Kernel panic 4-5 Nov (i386)
-
Just to confirm, I have today's nanoBSD 4GB snapshot running on my ALIX board and it seems to reboot when navigating the WebGUI. It rebooted out of the blue when loading the page to add a new firewall rule but also when loading the interface statistics page it rebooted a couple of times. Haven't seen that before but it has now done it about 10 to 15 times in a couple of days.
I can reproduce the error by invoking the auto updater, when it gets to downloading the file approx 3% the interface freezes and the box reboots. Upgrading from a URL through SSH is fine.
I would be happy to provide logfiles when it happens again but which one would you need? I checked the system log but couldn't find anything interesting. ???
When I leave the box alone it doesn't seem to reboot regardless of the throughput..
-
Keep the serial console connected and get the output from around the time it resets. Before the reboot messages show up. It may be a panic message, or something else.
You should be able to copy/paste it out of the serial terminal.
-
Keep the serial console connected and get the output from around the time it resets. Before the reboot messages show up. It may be a panic message, or something else.
You should be able to copy/paste it out of the serial terminal.
Ok cool, I will do that now. I just updated my previous post that I can reproduce the issue.
-
Unfortunately i can only confirm the kernel panic (page fault). It happens when booting, just after the interface configuration.
I am reinstalling a this moment to see if i can get the system working again.-m4rcu5
-
Unfortunately i can only confirm the kernel panic (page fault). It happens when booting, just after the interface configuration.
I am reinstalling a this moment to see if i can get the system working again.-m4rcu5
That sounds more like the amd64 problem, this is on i386.
-
Ok, got it.. Couldn't invoke the auto updater as there is no newer snapshot.. But after randomly clicking around in the webinterface for a minute it went down when halfway through on loading "Diagnostics –> ARP Table"
Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x10317 fault code = supervisor read, page not present instruction pointer = 0x20:0xc095f46b stack pointer = 0x28:0xe2e21bc4 frame pointer = 0x28:0xe2e21bc8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0\. pres 1, def32 1, gran 1 processor eflags = interrupt enables, resume, IOPL = 0 current process = 0 (ath0 taskq) trap number = 12 panic: page fault cpuid = 0 Cannot dump. Device not defined or unavailable. Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... -
Unfortunately i can only confirm the kernel panic (page fault). It happens when booting, just after the interface configuration.
I am reinstalling a this moment to see if i can get the system working again.-m4rcu5
That sounds more like the amd64 problem, this is on i386.
jimp, i use the i386 image on a Intel core2duo.
I have the exact same fault code on the same process (only on interface em0) as pakjebakmeel. This time it happend when booted from the live cd.
-m4rcu5
-
For me it only happens when navigating the webGUI.. If I leave the GUI alone and generate massive traffic the box is rock solid.
-
Hi jimp,
Sorry for screenshots, but I use real hardware ASUS Pundit and have not serial console. Before my first post I wait panic maximum 5 minutes. Now on lasts snapshot more long, but I know differences between snappshots absent.
This panic was appear immediately after fetch command on pfSense host. -
Hi all,
Is this bug still present or can it be fixed by upgrading to a newer snapshot? 8)
Thanks!
-
It's still there. I just restarted the builder again to see if the fixes checked in yesterday made a difference. It should be done in a while but I'd still wait for an all-clear.
-
Current snap is OK:
2.0-BETA4 (amd64)
built on Tue Nov 9 17:26:01 UTC 2010 -
pfSense-Full-Update-2.0-BETA4-20101109-1641.tgz
-
Ah, well I was hoping it may be a similar issue to amd64. Looks like it may be different.
-
pfSense-Full-Update-2.0-BETA4-20101110-0504.tgz
Same balls, but side-view. It seems to me traffic generating by router is reason of crash. Without this traffic router working more long time, but attempt to fetch any by router always cause panic. -
I've been sitting here furiously loading GUI pages on my poor little ALIX running a snapshot from today and though it's gotten slow at times, I have yet to see a panic.
Is there anything else people in this thread might have in common? What kind of setups do you all have? Can you give a general idea of things that are in use? (Multi-wan, IPsec, OpenVPN, PPPoE, 3G, wireless, etc)
-
Not to cause you more frustration Jimp - but I'm seeing this GUI / Kernel Panic also.
Running 2010-11-09 (i386) on a PIII.
Reset to factory defaults yesterday & did a basic install
I've got 2 dual port intel nics.
fxp0 = WAN PPPoE
fxp0 = Opt3 DHCP private (10.x.x.x)
fxp1 = Opt1 DMZ static public
fxp2 = LAN static private (172.x.x.x.)
fxp3 = Opt2 static private (172.y.y.y)I'm running DHCP server on Lan and Opt2.
I'm logging in under a 2nd administrator account.
I'm running Captive Portal on Opt2 w/ local auth
Firewall allows web, mail, dns traffic through to the public IPs on the DMZ
I have freeswitch installed on the box, but it isn't the pfSense package. pfSense doesn't know it's there.How does this match up with what the rest of you have?
-
I've noticed the following on the kernel panic screen.
Cannot dump. Device not defined or unavailable.
Would the dump be helpful in diagnosing this? Is there a place where we can find directions on how to give it a dump device? Is it possible to dump to the local disk, or to a USB memory stick?
I do have a null modem cable & could dump to the serial port / windows terminal app if that's how it's done, but I'd need directions for that also.
-
Can it be your hardware?
Can you please install dev kernel in there? -
In case someone missed it earlier in the thread, here are instructions for installing a dev kernel:
http://doc.pfsense.org/index.php/Switching_Kernels
Afterwards, capture the panic message and also the output of typing "bt" at the debugger prompt.
