PfSense-2.0; getting kernel panics on regular basis
-
This seems to happen once a day.
Holy frig, I apologize about the size!!
I'm fairly new to FreeBSD, but am quite familiar with Linux. What kind of steps can I take to diagnose this problem? I would dump a list of hardware and drivers, but I'm not even sure how lol
-
I am getting the first part of this message once in a while (have been getting it since 1.2.3).
I do not get kernel panics though.
I was told the wifi driver as a possible reason for that maybe it is the same in your case?
Either that or your wifi card is somehow broken?
Also would check dmesg to see if you have any additional clues as to what is causing this.
My hunch it is the wifi card. -
I usually have a handfull of bmiss messages. What I will try, next time this happens, is maybe move the wifi card to another PCI slot. It's right next to the 10/100 NIC, so maybe there's some interaction going on between them.
The wifi card is shielded with a plate encompassing both sides thought, and I thought that would be enough to prevent interaction, but we'll see.
-
I'm guessing you have an atheros based chipset. Those stuck beacon messages are definitely from a Wifi Card. If you know what wireless card you have in the box that might help. From my testing I've found that my Dlink DWA-552 hates FreeBSD 8. (What 2.0 is based on) Using the 2.0 release if I even attempt to enable the card it will cause the box to lock up. I tested a while ago with FreeBSD 9 beta and that seems to work well with the card.
You can try switching channels and see if that solves the issue. The stuck beacon issue seems to be related to the amount of interference on a particular channel. If it's a wireless N card make sure that it's not attempting to use N speeds as they don't work properly yet.
-
There is one more thing I can add.
I have got a bunch of settings that were recommended to me and/or others suffering from stuck beacon issue back in the 1.2.3.
sysctl dev.ath.0.txantenna=1
sysctl dev.ath.0.rxantenna=1
sysctl dev.ath.0.diversity=0
sysctl dev.ath.0.tpc=1
sysctl dev.ath.0.tpscale=1
ifconfig ath0 txpower '12'
ifconfig ath0 mtu 1500
ifconfig ath0 bmiss 7
ifconfig ath0 bgscan
ifconfig ath0 bintval 500You are welcome to try those settings (they did help me somewhat during the 1.2.3 days) ,but I haven't tried them yet in the 2.0 as I only got one stuck beacon so far after 3 days of uptime and wifi seems to be stable so far.
I had them in a shellscript that I ran manually everytime the firewall rebooted.