[Madwifi-users] Plenty of VAP problems 0.9.3.1 on openSuSE 10.2

[Raimund E. <ra...@cs...>]

Hi,

I recently bought an atheros based card (Proxim 8470-WD), chipset 5212. lspci 
says:

Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

I've got an updated openSuSE kernel (vmlinuz-2.6.18.8-0.1-default), for that 
reason I built madwifi packages from the provided openSuSE 10.2 src rpm and 
installed them with rpm -Uhv. No problems so far.

When I reboot the box, I get to see ath0 and wifi0 as new wireless interfaces. 
ath0 is in station mode. I rather want it in ap mode, so I did the following:

wlanconfig ath0 destroy

While the interface does disappear, I get to see this in dmesg:

BUG: warning at fs/proc/generic.c:732/remove_proc_entry()
 [<c0193a94>] remove_proc_entry+0x143/0x19e
 [<e93a33fa>] ieee80211_sysctl_vdetach+0x63/0xc7 [wlan]
 [<e938c09a>] ieee80211_vap_detach+0x83/0xd4 [wlan]
 [<e93a081a>] ieee80211_ioctl+0x0/0x420 [wlan]
 [<e93fa2c3>] ath_vap_delete+0x13b/0x2ae [ath_pci]
 [<e939b3bd>] ieee80211_stop+0x47/0xb4 [wlan]
 [<e93a081a>] ieee80211_ioctl+0x0/0x420 [wlan]
 [<e93a0889>] ieee80211_ioctl+0x6f/0x420 [wlan]
 [<c01314ee>] autoremove_wake_function+0x0/0x35
 [<e907052c>] do_journal_end+0xb9b/0xbc4 [reiserfs]
 [<c01789b4>] __d_lookup+0x98/0xdb
 [<e9069168>] pathrelse+0x18/0x2b [reiserfs]
 [<c01314ee>] autoremove_wake_function+0x0/0x35
 [<e907052c>] do_journal_end+0xb9b/0xbc4 [reiserfs]
 [<e9070684>] journal_end+0xc2/0xc9 [reiserfs]
 [<e9061c43>] reiserfs_dirty_inode+0x78/0x7e [reiserfs]
 [<c018252a>] __mark_inode_dirty+0x2a/0x178
 [<c01249f4>] current_fs_time+0x4f/0x5b
 [<c017ae5d>] touch_atime+0x60/0x8f
 [<c014db4a>] get_page_from_freelist+0x2f1/0x371
 [<c01c2cad>] vsnprintf+0x44f/0x48b
 [<c01497bc>] find_get_page+0x18/0x38
 [<e93a081a>] ieee80211_ioctl+0x0/0x420 [wlan]
 [<c025412d>] dev_ifsioc+0x376/0x391
 [<c0249d3c>] sock_ioctl+0x0/0x1bc
 [<c02546df>] dev_ioctl+0x3d1/0x462
 [<c0154c7b>] __handle_mm_fault+0x47c/0x871
 [<c01659a9>] get_empty_filp+0x99/0x164
 [<c016306f>] get_unused_fd+0x57/0xbd
 [<c0249d3c>] sock_ioctl+0x0/0x1bc
 [<c017430f>] do_ioctl+0x1f/0x63
 [<c017459d>] vfs_ioctl+0x24a/0x25c
 [<c01745fb>] sys_ioctl+0x4c/0x65
 [<c0103dc7>] syscall_call+0x7/0xb

All attempts setting up a new VAP in station or ap mode with wlanconfig after 
this fail:

# wlanconfig ath create wlandev wifi0 wlanmode ap
wlanconfig: ioctl: Input/output error
# wlanconfig ath create wlandev wifi0 wlanmode sta
wlanconfig: ioctl: Input/output error

However, monitor mode is no problem:

# wlanconfig ath create wlandev wifi0 wlanmode monitor
ath0
# iwconfig ath0
ath0      IEEE 802.11g  ESSID:""  Nickname:"box"
          Mode:Monitor  Frequency:2.437 GHz  Access Point: 00:20:A3:5A:B1:C0
          Bit Rate:0 kb/s   Tx-Power:17 dBm   Sensitivity=0/3
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=0/94  Signal level=-92 dBm  Noise level=-92 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0


I assume this is not the way it ought to be.

Can anyone here tell me how to get a vap in ap mode? Is the Bug dump above 
critical? After all it says only "warning" at the top.

Cheers,
Raimund