Kernel crash on 2.0.3 when assigning interface to WIFI NIC clone

sammy2ooo

Hello everyone

I am suffering from a kernel crash here. I am running the latest stable release of pfSense on an ALIX board. I was trying to clone my WLAN interface to create a "WLAN DMZ". But when I then create a new interface within the "Interface assignments" tab and assign it to ath0_wlan1 the crash and reboot occurs. I have submitted the crash report via GUI.

Am I doing anything wrong here? ??? Any help?

Wireless clone configuration:


Parent interface: ath0 (00:0b:6b:db:1f:f1)
Mode: Access Point
Description: WLAN DMZ

[2.0.3-RELEASE][root@fw.mydomain.tld]/(21): dmesg | grep ath


ath0: <atheros 5212="">mem 0xe00c0000-0xe00cffff irq 9 at device 12.0 on pci0
ath0: [ITHREAD]
ath0: AR5212 mac 5.9 RF5112 phy 4.3</atheros>

[2.0.3-RELEASE][root@fw.mydomain.tld]/(15): pciconf -l | grep ath0


ath0@pci0:0:12:0:       class=0x020000 card=0x1012185f chip=0x0013168c rev=0x01 hdr=0x00

[2.0.3-RELEASE][root@fw.mydomain.tld]/(18): ifconfig


[...]
ath0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 2290
        ether 00:0b:6b:db:1f:f1
        media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>status: running

ath0_wlan0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
        ether 00:0b:6b:db:1f:f1
        inet6 fe80::20b:6bff:fedb:1ff1%ath0_wlan0 prefixlen 64 scopeid 0x9
        inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255
        nd6 options=43 <performnud,accept_rtadv>media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>status: running
        ssid mySSID channel 9 (2452 MHz 11g) bssid 00:0b:6b:db:1f:f1
        country US ecm authmode WPA2/802.11i privacy MIXED deftxkey 2
        AES-CCM 2:128-bit txpower 21.5 scanvalid 60 pureg protmode OFF burst
        dtimperiod 1 -dfs

ath0_wlan1: flags=8802 <broadcast,simplex,multicast>metric 0 mtu 1500
        ether 06:0b:6b:db:1f:f1
        media: IEEE 802.11 Wireless Ethernet autoselect <hostap>(autoselect <hostap>)
        status: no carrier
        ssid "" channel 9 (2452 MHz 11g)
        country US ecm authmode OPEN privacy OFF txpower 21.5 scanvalid 60
        protmode OFF wme burst dtimperiod 1 -dfs bintval 0
[...]</hostap></hostap></broadcast,simplex,multicast></hostap></performnud,accept_rtadv></up,broadcast,running,simplex,multicast></hostap></up,broadcast,running,simplex,multicast>


Crash report begins.  Anonymous machine information:

i386
8.1-RELEASE-p13
FreeBSD 8.1-RELEASE-p13 #1: Fri Apr 12 10:50:06 EDT 2013     root@snapshots-8_1-i386.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386

Crash report details:

Filename: /var/crash/bounds
1

Filename: /var/crash/info.0
Dump header from device /dev/ad0s1b
  Architecture: i386
  Architecture Version: 2
  Dump Length: 46297088B (44 MB)
  Blocksize: 512
  Dumptime: Tue Jun 11 12:41:07 2013
  Hostname: fw.mydomain.tld
  Magic: FreeBSD Kernel Dump
  Version String: FreeBSD 8.1-RELEASE-p13 #1: Fri Apr 12 10:50:06 EDT 2013
    root@snapshots-8_1-i386.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386
  Panic String: page fault
  Dump Parity: 3570754619
  Bounds: 0
  Dump Status: good

sammy2ooo

Just stumpled over this link from back in 2010:

http://redmine.pfsense.org/issues/1048

Quoting Chris Buechler

at least one Atheros chipset I have will panic like that with VAP. Driver problem, nothing we can do about it, needs to be replicated on stock FreeBSD and reported upstream.

So this still seems to be an issue…

sammy2ooo

I would like to create an upstream bug report on freebsd.org. How can I access the coredump generated by pfSense?

This chip should be reported as instable in regards to VAP on the following list.

https://docs.google.com/spreadsheet/ccc?key=0AojFUXcbH0ROdHgwYkFHbkRUdV9hVWljVWl5SXkxbFE&hl=en#gid=0

cmb

First, try it on 2.1. That may well work fine on FreeBSD 8.3.

If not, then before reporting anything upstream that will get any attention, it'll have to be tested on FreeBSD HEAD. A ton of wireless-related fixes are there that can't reasonably be back ported. We'll have 2.2 alpha snapshots out on that within a few weeks if you want to wait until then.

sammy2ooo

Thanks for replying. It's not that import for me, so I guess I am going to wait until 2.2 becomes stable, as I don't want to break my rock solid installation