Kernel crash when Ralink RT3572/3052 (ASUS N53 USB) is brought up
-
I experience the same issue than here:
https://forum.pfsense.org/index.php?topic=90558.0the box is a i810/PentiumIII with an added 4x USB 2.0 PCI card. NICs are rl0 (onboard), xl0, ed0, run0.
run0 is the ASUS N53-USB.
This box has been running FreeBSD 10.0 and then 10.1 as a gateway/router with WAN on rl0, LANs on xl0 and ed0 and wireless AP on run0.
I tried pfSense 2.2.2.
It crashes when run0 if brought up: ie. when setting the IP addresses with console menu 2) or when bringing it up from the shell:
ifconfig wlan0 up
(after wlan0 creation: ifconfig wlan0 create wlandev run0)
when I replace the pfSense kernel in /boot/kernel with the generic FreeBSD-10.1 kernel, run0 is brought up to life normally and I can set up an AP. But then routing doesn't work (on all NICs) (!?). I pulled the source for pfsense-tools and I see there are quite some patches to generic FreeBSD kernel, among others in the network stack. I tried to build a custom pfSense kernel but patching fails … -
well, I have not much time to have a closer look, and have found of the fork OPNSense. The RT3572 works without problems on it, AP included.
-
Might be similar to mine:
https://redmine.pfsense.org/issues/4722It works with extra debugging options in the kernel that slow other parts down, but not with our "optimized" kernel. You can read in the redmine entry that it happens on FreeBSD also with a pared-down kernel.
If/when OPNsense removes WITNESS and other debugging from their kernels it will likely start crashing there also until the driver is fixed in FreeBSD.
-
Might be similar to mine:
https://redmine.pfsense.org/issues/4722maybe, but different chip, the idProduct of my ASUS (idVendor 0b05) USB-N53 is 179d, MAC/BBP RT3572, RF RT3052, firmware RT3071
It works with extra debugging options in the kernel that slow other parts down, but not with our "optimized" kernel. You can read in the redmine entry that it happens on FreeBSD also with a pared-down kernel.
If/when OPNsense removes WITNESS and other debugging from their kernels it will likely start crashing there also until the driver is fixed in FreeBSD.
as is, it has been working fine since the release of FreeBSD-10.0, so for more than one year. No troubles no crashes as wireless AP. As I have never experienced slow performances nor stability issues with FreeBSD I just stay there.
Until I downloaded the source from the ESF portal, I didn't realize that pfSense is not just a configuration GUI like basically OPNSense, but also a partial kernel fork of FreeBSD.
