Kernel panic 4-5 Nov (i386)
-
Can you please test the new snapshots and see if this is fixed?
-
Will do. Thanks ermal!
Do you believe the update made it into the current builder run (looks like it started 10:40am EST), or do I need to wait for the build after this?
-
pfSense-Full-Update-2.0-BETA4-20101203-2137.tgz – 5 hours - flight normal. I hope further problems it will not be.
Thanks!
-
Ok, I've done several tests, need to do a couple more, but here's what I've discovered so far.
It appears that the GUI triggered panic may be cleared up. I'm still able to trigger a panic by calling fetch from the console under specific configuration. It appears to become a problem when CaptivePortal is enabled even though I'm not working from or through the CP interface. I'm not sure which feature in CP is the trigger, so I need to do a little more testing.
Since this thread was more related to the GUI caused kernel panic I suggest we mark this one as solved and I'll start a new thread for the CP related kernel panic once I've narrowed it down.
Ermal - Thanks again for tracking this down!
-
Unfortunately, it still doesn't work for me :-(
I just tried the December 5 Snapshot but I still get a panic when trying to update from the GUI…
I will try the most current snapshot tomorrow, just wanted to let you know ;DBest regards,
Christian
-
Trying anything but the most current snapshot would undoubtedly be problematic.
-
Update:
Tried the newest snapshot (20.12.2010) but I still get the kernel panic when I try the online update via GUI :-(Could I do s.th. to help you to figure this problem out?
Thanks and best regards,
Christian
-
Are you running captive portal?
-
PJ2,
thanks for your reply.
Actually yes, I have a CP set up… Do I have to deactivate it?Best regards,
Christian
-
turning off CP does the trick for me.
What network drivers are you using? fxp?
-
Actually yes, I have a CP set up… Do I have to deactivate it?
That's something to try, it may narrow down the issue considerably.
-
@PJ2:
I have these interfaces:
vr0 <- on-Board
ste <- 4-port 100Mbit Card (D-Link)@cmb:
I have now switched off CP and just clicked on "Auto Update". This time pfSense was able to check if there is a new version without a restart / kernel panic.
Tomorrow will be interesting, as then there'll be an update available.I will report back, if the update went OK tomorrow, or if I still got a kernel panic :-)
Thanks for your help anyway so far!!
Best regards,
Chris
-
Thanks Chris -
I've been trying to sort out what it is besides CP that makes the difference. I was hoping that switching NICs would solve the problem for me, but that doesn't seem to be the case. :-/
-
Hm… Well if CP really makes the difference, then I am sure that we can sort this, together with the dev, out somehow ;-)
They would be having the same issues if they turn on CP as well, wouldn't they? Or is it indeed coupled with the NIC-type?
I am eager to see what happens tomorrow ;-)
Best regards,
Chris
-
Update:
Tried the update today and… it worked ;DSo the problem really seems to be that I get a kernel panic with the update function if there is the CP enabled...
Strange isn't it?
Best regards
Christian
-
I was using a ver from the 2nd week of Dec. I would get a kernel panic every time I would start heavy downloading from the internet.. I updated the box to 16th ver and the kernel panics went away. Been updating the box every couple of days after and it seems stable. Only using Snort, no CP.
-
For a long time I thought I was the only one with this issue. Glad I'm not totally crazy.
-
@PJ2:
For a long time I thought I was the only one with this issue. Glad I'm not totally crazy.
I was thinking the same thing until I saw this topic. I had a good reason tho. I swapped my case back to mini-box M300 and started to mess around getting the picolcd to work again. Figured it was that at first but my panic had somthing to do with the nic irqs.
-
I don't think it's a hardware issue. 2.0-BETA4 (i386) built on Tue Nov 2 14:53:54 EDT 2010 is perfectly stable with Captive Portal active.
Automatic update -> success -> restart -> several minutes running -> kernel panic :-/
disconnect WAN iface cable -> manually update back to the Nov 2 versionI tried these:
pfSense-Full-Update-2.0-BETA4-20101107-0244.tgz
pfSense-Full-Update-2.0-BETA4-20101110-0504.tgz
pfSense-Full-Update-2.0-BETA4-20101115-1340.tgz
and auto-update from Dec 9, Dec 17, Dec 21all af them crashing in the same way.
Anybody know what has changed with CP between Nov 2 and Nov 7 ?
-
Update to the most current snapshot and try again. Many fixes have been checked in, some in the last couple days. It should be working again now without panics. (hopefully)
