Vadim Jukov wrote: > 15 April 2008 P3. 06:16:58 Vadim Jukov wrote: >> Also I bought D-Link DWL-AG530 for desktop PC, because someone said >> (cannot discover that letter now:( ) it's Atheros 5212-based, which is >> supported. Damned me, I messed up ral(4) and ath(4) in my mind, and >> bought a card from a manufacturer which do not support OpenBSD... :( >> And I run in a problem that either man in the letter made a typo (530 >> instead 520), or D-Link "slightly" changed chip. Novadays it's based >> on 5213, which fails to initialize or doesn't work either. Sample >> dmesg output (from different boots): >> >> ath0 at pci0 dev 11 function 0 "Atheros AR5413" rev 0x01: irq 11 >> ath0: AR5413 10.5 phy 6.1 rf 6.3, FCC2A*, address 00:1c:f0:19:aa:66 >> ath0: ath_chan_set: unable to reset channel 52 (5260 MHz) >> ath0: unable to reset hardware; hal status 3618911128 >> ath0: unable to reset hardware; hal status 3520943048 >> ath0: unable to reset hardware; hal status 3520945608 >> ath0: unable to reset hardware; hal status 3520946120 >> ath0: unable to reset hardware; hal status 0 >> ath0: unable to reset hardware; hal status 3485396992 >> ath0: unable to reset hardware; hal status 0 >> ath0: unable to reset hardware; hal status 3618274072 >> --- >> ath0 at pci0 dev 11 function 0 "Atheros AR5213 (D-Link DWL-AG530)" rev >> 0x01: irq 11 ath0: unable to attach hardware; HAL status 22 >> --- >> ath0 at pci0 dev 11 function 0 "Atheros AR5413" rev 0x01: irq 11 >> ath0: AR5413 10.5 phy 6.1 rf 6.3, FCC2A*, address 00:1c:f0:19:aa:66 >> ath0: bogus xmit rate 0x0 (idx 0x7) >> ath0: bogus xmit rate 0x0 (idx 0x7) >> ath0: bogus xmit rate 0x0 (idx 0x7) >> >> When I played with this card and driver, forcing detecting it as 5212 >> (second sample output), I saw message saying "failed to resume the >> AR5212 (again)", see sys/dev/ic/ar5212.c line 334 (I played with >> incrementing loop count and sleep time there, without luck). Do not >> remember HAL status though, but it was consistent; may try again of >> course if it's needed. >> >> A few minutes ago, while I was writing this, it freezed (no panic) >> whole PC after a few "ifconfig ath0 media xxx" and "ifconfig ath0" >> commands. I have no AP around there, so I cannot ever say, does it >> work in BSS mode, but in hostap mode it doesn't (even when status is >> "active"). But I'm newbie in Wi-Fi at all, maybe I missed something... > > Now I can "reliable" call a freeze or panic: > > boot> boot -s > <...> > # cd /etc > # sh netstart ath0 > # ^D > <...> > starting network... > <got it> > > One of the panic (not from a GENERIC kernel (I tried 2: month-old and one > build a few hours ago), they still just freeze, and I have stopped > experiments now) is at the end of letter. > > Also on madwifi.org I discovered that D-Link really changed chip in A4 or > A5 h/w revision (I have A6), from AR5212 to AR5213. Currently I'm trying > to find a replace for this card (AR5212-based at least)... > > -- > Best wishes, > Vadim Zhukov > > > (written by hand) > > ddb> trace > Debugger(d1a00000,de8d1960,d19ff030,4,1) at Debugger+0x4 > panic(d07273ad,d072748c,7,2,d7b7df00) at panic+0x63 > ieee80211_set_link_state(d19ff030,4,ffffffff,919f7) at > ieee80211_set_link_state > ath_newstate(d19ff030,4,ffffffff,ffff0064,de9eae60) at ath_newstate+0x181 > ieee80211_create_ibss(d19ff030,d19ff2ea,d0202262,d0,7f51e754) at > ieee80211_create_ibss+0x11b > ieee80211_end_scan(d19ff030,d0388db6,d1a1d2c0,de9eaed8) at > ieee80211_end_scan_0x21e > ath_next_scan(d19ff000,beaebe58,5305bdc4,0,0) at ath_next_scan+0x3d > softclock(58,10,10,10,d7bd12b0) at softclock+0x22c > Bad frame pointer: 0xde9eaef8 > ddb> ps > PID PPID PGRP UID S FLAGS WAIT COMMAND > 29743 12849 12849 0 3 0x4002 biowait perl > 23968 29279 29279 83 3 0x180 poll ntpd > 23968 29279 1 0 3 0x80 poll ntpd > 18665 1 18665 0 3 0x80 poll rpc.lock > 28214 31308 31308 0 3 0x80 nfsd nfsd > 25324 31308 31308 0 3 0x80 nfsd nfsd > 265 31308 31308 0 3 0x80 nfsd nfsd > 30325 31308 31308 0 3 0x80 nfsd nfsd > 31308 1 31308 0 3 0x80 netcon nfsd > 28807 1 28807 0 3 0x80 select mountd > 24743 19443 19443 68 3 0x180 select isakmpd > 12187 1 12187 28 3 0x180 poll portmap > 19443 1 19443 0 3 0x80 netio isakmpd > 21435 10256 10256 70 3 0x180 select named > 10256 1 10256 0 3 0x180 netio named > 27148 2629 2629 74 3 0x180 bpf pflogd > 2629 1 2629 0 3 0x80 netio pflogd > 6598 12385 12385 73 3 0x180 poll syslogd > 12385 1 12385 0 3 0x80 netio syslogd > 12849 1 12849 0 3 0x4082 pause sh > 18 0 0 0 3 0x100200 bored crypto > 17 0 0 0 3 0x100200 aiodoned aiodoned > 16 0 0 0 3 0x100200 syncer update > 15 0 0 0 3 0x100200 cleaner cleaner > 14 0 0 0 3 0x100200 reaper reaper > 13 0 0 0 3 0x100200 pgdaemon pagedaemon > 12 0 0 0 3 0x100200 pftm pfpurge > 11 0 0 0 3 0x100200 usbevt usb4 > 10 0 0 0 3 0x100200 usbevt usb3 > 9 0 0 0 3 0x100200 usbevt usb2 > 8 0 0 0 3 0x100200 usbevt usb1 > 7 0 0 0 3 0x100200 usbtsk usbtask > 6 0 0 0 3 0x100200 usbevt usb0 > 5 0 0 0 3 0x100200 apmev apm0 > 4 0 0 0 3 0x100200 bored syswq > * 3 0 0 0 7 0x100200 idle0 > 2 0 0 0 3 0x100200 kmalloc kmthread > 1 0 0 0 3 0x4080 wait init > 0 -1 0 0 3 0x80200 scheduler swapper > ddb> boot reboot > panic: wdc_exec_command: polled command not done > Stopped at Debugger+0x4: leave > RUN AT LEAST <...> > ddb> boot reboot > <rebooted>
This is a known issue, I've opened a thread here a few weeks ago. Because I thought reyk@ maybe didn't see the thread I forwarded the mail to him again, which was five days ago. So hopefully they'll have a look at this issue (maybe again).
