Pfsense stable crashes : kernel crash (panic)
I am having crashes lately on the latest stable platform (2.0). The pfsense reboots itself and says it detected a crash.
Link to pastebin with the crash output :
Anybody know how to troubleshoot or debug this log? It seems it has multiple copies in this pastebin (because it automaticaly displays all my crash logs.. and I have allot)
do you have S.M.A.R.T motherboard and hdd? if you do what it says
All Smart values are OK. For some reason I think it's the wifi device.. but not sure.. anybody know how to "read" or debug my crash report posted in my topic start?
ok, then i give up trying with this.. Sorry, i don't have any experience with bsd
Is your wifi device attached on usb?
No, it's built in.
Copy and paste from ifconfig :
run0_wlan0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 ether 00:0d:f0:95:91:53 inet6 fe80::20d:f0ff:fe95:9153%run0_wlan0 prefixlen 64 scopeid 0x8 inet 10.0.0.1 netmask 0xffff0000 broadcast 10.0.255.255 nd6 options=3 <performnud,accept_rtadv>media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>status: running ssid Gratis_Wifi channel 7 (2442 MHz 11g) bssid 00:0d:f0:95:91:53 country US authmode OPEN privacy OFF txpower 0 scanvalid 60 protmode OFF -apbridge dtimperiod 1 -dfs</hostap></performnud,accept_rtadv></up,broadcast,running,simplex,multicast>
But like I said, I'm not sure if it's the WIFI device. I have no clue on how to debug my crash report (see my topic start). Anybody know how?
Someone else replied in another topic of mine and he said that he also had crashes with the same hardware:
He says the problems went away after he disabled wireless.
Can anybody confirm that my crash logs in the topicstart show errors or output which belong to my wireless device? Want to see if Wireless is the problem and I would also very much like to solve it..
Quick look at the crash report:
cpuid = 0
dynamic pcpu = 0x51f880
curthread = 0xc4b71a00: pid 0 "run0 taskq"
curpcb = 0xeb1d9d90
fpcurthread = none
idlethread = 0xc4991780: pid 11 "idle: cpu0"
APIC ID = 0
currentldt = 0x50
Tracing pid 0 tid 64057 td 0xc4b71a00
run_drain_fifo(c4d72000,c4b71a00,eb1d9c90,246,0,…) at run_drain_fifo+0x5f
run_ratectl_cb(c4d72000,1,0,c12ce3fc,0,...) at run_ratectl_cb+0x5c
taskqueue_run(c4d69240,c4d69258,0,c0edc643,0,...) at taskqueue_run+0x89
taskqueue_thread_loop(c4d81074,eb1d9d38,0,0,0,...) at taskqueue_thread_loop+0x45
fork_exit(c0a77de0,c4d81074,eb1d9d38) at fork_exit+0x88
fork_trampoline() at fork_trampoline+0x8
--- trap 0, eip = 0, esp = 0xeb1d9d70, ebp = 0 ---
Immediately above is the stack at time of the panic: the instruction at or around 0x5f bytes from the start of location (probably function) run_drain_fifo is the one causing the crash condition.
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0xc587b908
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc094695f
stack pointer = 0x28:0xeb1d9c48
frame pointer = 0x28:0xeb1d9c74
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 = 0 (run0 taskq)
This summarises crash cause: run0 taskq was the running process and the system crashed because the kernel attempted to access virtual address 0xc587b908 which is in a "no access" page.
The problem is quite likely in the run driver but it could be an error somewhere else that happens to shows up in the run driver. (An example: code that frees a block of kernel dynamic memory but fails to clear a pointer to the block.)
Thanks for the feedback.
Too bad that the wireless is causing the problem, this Fit-pC2i is an awesome device for Pfsense home users as it only uses 8 watts and has great performance.
Any idea's on how to resolve this? Would very much like to use the wireless HW on this device and I'm sure allot of other users do too..
Any idea's on how to resolve this?
Do a firmware upgrade to a snapshot build of pfSense 2.1 which is based on FreeBSD 8.3, one of the current versions. If you still have problems submit a FreeBSD problem report including the pfSense crash report.
I suspect it will be difficult to persuade any of the FreeBSD maintainers to look at problems in FreeBSD 8.1 (used in pfSense 2.0.1).
If you need help with any of that ask here.
I agree they are nice units.