Submitting crashdump
-
I would like to submit a crash report, where I can upload the file? I also need to remove the hostname from crashdump.
Hardware is Netgate SG-2220.
-
Post it here on the forum, there is no private submission mechanism any longer.
-
I have removed physical addresses and the hostname.
-
It was an issue in the ath NIC/driver:
db:0:kdb.enter.default> show pcpu cpuid = 1 dynamic pcpu = 0xfffffe007dbff380 curthread = 0xfffff80004436740: pid 12 tid 100044 "irq16: ath0" curpcb = 0xfffff80004436ce0 fpcurthread = none idlethread = 0xfffff8000418d740: tid 100004 "idle: cpu1" curpmap = 0xffffffff8368d5a8 tssp = 0xffffffff83717688 commontssp = 0xffffffff83717688 rsp0 = 0xfffffe00185afe00 kcr3 = 0x3d05000 ucr3 = 0xffffffffffffffff scr3 = 0x7874d000 gs32p = 0xffffffff8371dea0 ldt = 0xffffffff8371dee0 tss = 0xffffffff8371ded0 tlb gen = 60618 curvnet = 0 db:0:kdb.enter.default> bt Tracing pid 12 tid 100044 td 0xfffff80004436740 kdb_enter() at kdb_enter+0x37/frame 0xfffffe00185af830 vpanic() at vpanic+0x197/frame 0xfffffe00185af880 panic() at panic+0x43/frame 0xfffffe00185af8e0 trap_fatal() at trap_fatal+0x391/frame 0xfffffe00185af940 trap_pfault() at trap_pfault+0x4f/frame 0xfffffe00185af990 trap() at trap+0x286/frame 0xfffffe00185afaa0 calltrap() at calltrap+0x8/frame 0xfffffe00185afaa0 --- trap 0xc, rip = 0xffffffff80f1f3bc, rsp = 0xfffffe00185afb70, rbp = 0xfffffe00185afbc0 --- ieee80211_beacon_update() at ieee80211_beacon_update+0x7ac/frame 0xfffffe00185afbc0 ath_beacon_generate() at ath_beacon_generate+0x46/frame 0xfffffe00185afc10 ath_beacon_proc() at ath_beacon_proc+0x241/frame 0xfffffe00185afc60 ath_intr() at ath_intr+0x4b8/frame 0xfffffe00185afc90 ithread_loop() at ithread_loop+0x23c/frame 0xfffffe00185afcf0 fork_exit() at fork_exit+0x7e/frame 0xfffffe00185afd30 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00185afd30 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- db:0:kdb.enter.default> ps
No time stamps on the console buffer, how long after the upgrade did that happen?
The reported pfSense version is still 2.5.0 so maybe it didn't complete the upgrade as expected.
Have you been using the wifi card for some time?
Steve
-
I'm not sure when I had done the update, but I could swear I also logged in several times after the crashdump time stamp and didn't ever see this. Is it possible that this is something older before the update? Is it possible to reinstall the update?
-
I have checked the email notifications, the latest system upgrade message is from 16.04.21:
Notifications in this message: 1 ================================ 13:32:29 System is going to be upgraded. Rebooting in 10 seconds.
Crashdump is from 19:11:03 several hours after the update it seems.
-
It's possible, but unlikely, nothing was logged to the console since then until the crash.
That the first crash you've seen there?
Crashes that infrequent make testing difficult.
Steve
-
@gmipf The wifi card is my main wlan here, so it is always in use. (But pretty poor performance)
-
Its the first crash since this update.
-
Hmm, I'm not aware of anything there that actually causes a kernel panic.
You see any errors in the wireless logs?
You might try a 2.5.2 snapshot. Or 2.6 even. But if this is the first time you've seen an issue since April it's almost impossible to know if it makes any difference.
Steve