Okay, 4.9 hasn't fixed this problem for me, and I'll try to describe it as fully as possible:
In June 2010 I got Wireless PCI Adapter - Linksys WMP54G: http://homestore.cisco.com/en-us/print-server/linksys-WMP54G_stcVVproductId53934605VVcatId543809VVviewprod.htm RAL(4) says it supports it fine (in Host AP mode of course -- that's what I need), and it did. Except for 1 thing: it needed to be restarted once per ~3 days or so regularly (via cron). Until that it wasn't possible to associate with the access point. exact model (taken from dmesg @i386) is: ral0 at pci6 dev 9 function 0 "Ralink RT2561S" rev 0x00: apic 4 int 17 (irq 11), address 00:25:9c:76:05:94 ral0: MAC/BBP RT2561C, RF RT2527 But since it worked I wasn't bothered so much about those "restarts". After update to 4.8 I noticed that cron line ''sh /etc/netstart ral0`` doesn't help anymore.. After 1-2-3 days the access point just stops responding. It's visible in access point list though, but there's no way to associate with it. Tried different channels, power control options, different flags in ifconfig, switched to amd64 and back -- no luck. I'm not sure how the 80211 code of OpenBSD and NetBSD are familiar but I gave NetBSD 5.1 a try. The funny thing is that it has the same problem -- though it acts like OpenBSD <=4.7 (so cron line with restart command is needed). Haven't touched NetBSD-current. Googling helped a bit, but all of the discussions don't end with success: exactly the same symptoms: http://www.mail-archive.com/[email protected]/msg98018.html the same symptoms on pfsense: http://permalink.gmane.org/gmane.comp.security.firewalls.pfsense.support/22542 2 guys with the same problem and unanswered reports: http://www.mail-archive.com/[email protected]/msg51398.html something on FreeBSD, maybe related to this problem: http://forums.freebsd.org/showthread.php?t=17596 After update to 4.9 it still needs hardware reboot to function properly after the 1-3 days of up&&running. As of speaking about "clients", they are different: android-based mobile phone, wifi printer, linux lappies and 1 windows netbook -- all of them can't associate after such period. dmesg is silent (after ifconfig ral0 debug). I could provide full debug traces from wpa_supplicant on a linux box, compile the kernel with needed options and provide any additional information that could help to eliminate this bug. dmesg, pcidump and acpidump are attached. Thanks. -- Dont wait to die to find paradise... -- Cheerz, Vlad "Stealth" Glagolev
acpi.tgz
Description: Binary data
dmesg.txt
Description: Binary data
pcidump.txt
Description: Binary data
pgpwOua5ezaP9.pgp
Description: PGP signature
