Kernel Panic
-
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.gzEDIT: Modified code to reflect below change
-
With a little correction.
The last command is cp kernel_new.gz /boot/kernel/kernel.gz@hugo,
if this results in a fix it will be included in the snapshots which will put it on amd64 snaps as well. -
And then reboot.
-
And hopefully if it all goes as planned the next snapshot should have textdump support that works in it, and when it does panic it will automatically restart and leave the crash info in /var/crash in a .tar file that we can review. Works better than cell phone pics or swapping kernels… :-)
-
:D ;D :D OMG!!! I am posting this right now via OpenVPN on my neighbors wifi. It is working on my Soekris net5501-70 board so far and I haven't been booted. Will edit this post if it crashes doing more testing.
EDIT: Able to remote into everything fine, and trying file transfers
EDIT EDIT: Haven't had any problems since 5 with the network at home (Soekris). Still am testing the "work" one (em).
-
just installed the latest snap with the kernel.
Looking good so far! :)
copied 1GB of data…no problem.going to test some more.
-
Ermal, please let us know when there will be a 64-bit kernel snap available for testing.
Jim, please let us know when there is a snap ready or in the pipe with textdump.
-
CRAP!!! It faulted out again (Soekris):
Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x20:0x0 stack pointer = 0x28:0xd553ebc0 frame pointer = 0x28:0xd553ebcc 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 = 12 (irq5: vr1) [thread] Stopped at 0: *** error reading from address 0 *** db> bt Tracing pid 12 tid 64026 td 0xc3aa4780 m_tag_delete(c4dde600,c4de0b3d) at m_tag_delete+0x32 m_tag_delete_chain(c4dde600,0,d553ec2c,c0c94f99,c4dde600,...) at m_tag_delete_chain+0x82 mb_dtor_mbuf(c4dde600,100,0,c0a9041f,c3a92000,...) at mb_dtor_mbuf+0x25 uma_zfree_arg(c1d7b000,c4dde600,0,c3a28000,d553ec70,...) at uma_zfree_arg+0x29 m_freem(c4dde600,c3debe00,c3a92000,7f,7f,...) at m_freem+0x43 vr_txeof(0,c12c69c0,d5530008,0,0,...) at vr_txeof+0x340 vr_intr(c3a28000,0,109,dbd32e12,b15,...) at vr_intr+0x1c7 intr_event_execute_handlers(c39757f8,c3972180,c0e6ba48,52d,c39721f0,...) at intr_event_execute_handlers+0x14b ithread_loop(c3a8e450,d553ed38,6000,f600001b,0,...) at ithread_loop+0x6b fork_exit(c09ae910,c3a8e450,d553ed38) at fork_exit+0x91 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xd553ed70, ebp = 0 --- db> At the time I was logged on with 2 clients. One (my netbook) was pushing pandora radio, and the other (my lappy) was working on configuration on the local network via remote desktop. The desktop handshake for security (kerbros) is when it crashed.[/thread] -
i have started facing this on my alix now using nanobsd, problem is when it crashes, webgui wont work nor does the serial console show anything so i have to simply power off and on again.
-
I can confirm the freezing on the latest build.
No indication on the console, nothing in logs, no crash dumps, nada. It's just stone dead.Only thing you can do is to power-cycle the machine.
-
so i guess im not the only one, im using the 26th jan snap and one way i could replicate is as follows:
alix booted and running and pppoe conencted, now i went to status -> interfaces -> wan interface and clicked disconnect and after some time it auto reconnects and now after say about less than 30mins and the system is dead.
-
xibpin and others please upgrade to the 27-JAN snapshot when its out.
Please do not mess this thread because it is because of another specific issue not related to the hangs which should be fixed on a 27-JAN snap.
-
@ermal:
xibpin and others please upgrade to the 27-JAN snapshot when its out.
Please do not mess this thread because it is because of another specific issue not related to the hangs which should be fixed on a 27-JAN snap.
The one that froze on me most recently was the 27-JAN snapshot ("2.0-BETA5 (amd64) built on Thu Jan 27 01:29:01 EST 2011").
-
Should I just wait till the snap comes out? I never did get an answer concerning the test/crash last night loading the stuff ermal provided. Worked great, as you can see, for quite some time.
-
ermal,
My openvpn connection is still up from last night.
Copied a good amount of data, no panicsSo i know going forward,
Do i need to apply the new kernel with the newer snaps?At what point will the new snaps contain the new working kernel?
Thanks again for all your help. (and of course jimp also) :)
-
Hello, I tried the latest snap and the latest kernel but the problem persists
-
Hi ! i jast try with latest snap and latest kernel but he problem persist.
(to everyone) Please don't just say "latest kernel" - give a timestamp, be as precise as possible.
-
@ermal:
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.the kernel is in the quote, and the snap is the latest at this time in the update manager
-
Just because that is true now doesn't mean that will be true in a couple hours. Timestamps are important.
