Kernel Panic
-
I've changed to the SMP kernel and updated to the latest snapshots as of 15 minutes ago, and my machine seems to be automatically rebooting and generating proper crash reports now. Thanks jimp!
Unfortunately, I am still able to crash my system at will the same way I have been from the get go - by accessing the web gui through the VPN. I sent the (now useful!) crash report via the web gui, is there anything I can/should do beyond that at this point?
-
When the next snapshot comes out later this evening/tonight, update to it and try to reproduce it again.
-
JimP, who exactly were you talking to? or was it just a general reference to everyone?
-
just in general for anyone still getting crashes… hopefully it's more stable.
-
I won't get to testing that box (p4 dell gonna kick it in the parking lot) till tomorrow morning, so I'll have to get back to you on the test.
-
The snapshot with the fixes Jim mentioned is now up, I've upgraded all my systems to it and no issues. Granted I wasn't seeing any panics previously either, so those who can replicate issues, please test.
-
So far so good using this morning's build - tinkered around with the web gui for awhile with no crashes (couldn't even log in before…), did the same with a shell connection (which always crashed after a few minutes before) and am 1/4 of the way through transferring a 1.25GB file through the vpn to the pfSense box via SCP with no crashes so far. (It has always been communication directly with the remote pfSense box through the VPN that triggered crashes for me). Fingers crossed...
I am curious though - and I'll (dis)qualify this by saying that I am not a developer, nor do I pretend to fully understand much of the goings on in the git repository, but - I don't see anything in the list of commits since the last snapshot I tried that I would have expected to have an impact on this particular issue. Any idea as to what was causing the panics in the first place?
-
I am curious though - and I'll (dis)qualify this by saying that I am not a developer, nor do I pretend to fully understand much of the goings on in the git repository, but - I don't see anything in the list of commits since the last snapshot I tried that I would have expected to have an impact on this particular issue. Any idea as to what was causing the panics in the first place?
Look at the commits to the tools repo, not just the pfSense code repo. The tools repo is where things like kernel patches and builder changes happen.
-
Thanks, jimp, I had no idea! Adds a whole new level of excitement to the daily snapshots, doesn't it…
FYI, I have at this point - in addition to trying everything else that previously caused an instant panic - transferred a couple of gigs through the VPN to what I would have called my 'sick' pfsense box, and everything seems to be working and happy.
-
Thanks, jimp, I had no idea! Adds a whole new level of excitement to the daily snapshots, doesn't it…
Yeah, those are the main two. There are also others that are used but they change much less often, if at all (like the freesbie2 stuff).
FYI, I have at this point - in addition to trying everything else that previously caused an instant panic - transferred a couple of gigs through the VPN to what I would have called my 'sick' pfsense box, and everything seems to be working and happy.
Sounds very promising. Keep trying to kill it, see what happens. :-)
-
Crashed again, after about 3 days I think…
2.0-BETA5 (i386)
built on Sun Feb 6 23:54:00 EST 2011
-
Crashed again, after about 3 days I think…
2.0-BETA5 (i386)
built on Sun Feb 6 23:54:00 EST 2011Update to the 9th or later, it should be stable from that point on.
-
Yep did that just now, will keep an eye on it. Thanks.
-
Ran for 2 hours then everything just hung. No panic, nothing in /var/crash and no crash message after reboot. Keyboard / everything was frozen, no traffic was allowed through the device.
-
Any idea what you were doing at the time? FTP? PPTP?
-
I had a VPN connection open (PPTP), but not really much data transfer. Not much more - I was not doing anything other than the IMAP/SMTP/SSH/HTTP traffic.
-
1 hour, crashed:
2.0-BETA5 (i386)
built on Wed Feb 9 01:34:47 EST 2011
-
Just reporting my experiences -
Running 2.0-BETA5 (i386) built on Wed Feb 9 00:54:34 EST 2011 on both machines. (Did a clean install)
uptime = 7+ hoursTesting CARP & failover, FTP traffic, OpenVPN client/server setup.
No crashes so far, and they used to be pretty easy to produce.
This is only a simple test environment, so it doesn't get regular traffic, only a single client at a time for now.
-
I'm getting a panic in today's snapshot, 2.0-BETA5 (amd64)
built on Wed Feb 9 19:39:50 EST 2011 . This was caused I believe by syncing to slave. I was in the process of setting up a new interface on the master and configuring a vpn to it.Andy
-
This is master or slave?
That seems like an impossible trace but i will look at it after the information.
