want to see how far it gets? ... not far. this looks like the problem i just reported w/ the busy waiting and driver defunct.
On Sun, 5 Jun 2011 21:18:34 +0800 Adrian Chadd <adr...@freebsd.org> wrote: > On 5 June 2011 21:04, Camilo Mesias <cam...@mesias.co.uk> wrote: > > Hi, > > > > thanks for the suggestions. > > > > I didn't get back a stable value from that regidx/regval, I settled > > on this: > > > > [root@newt ~]# for x in $(seq 1 1000) ; do echo "0x7868" > > > /sys/kernel/debug/ieee80211/phy0/ath9k/regidx; cat > > /sys/kernel/debug/ieee80211/phy0/ath9k/regval; done|sort |uniq > > 0x02036085 > > 0x42030085 > > 0x42035885 > > 0x42036085 > > 0x82030085 > > 0x82036085 > > > > Does that trailing 5 mean anything? Here is the corresponding lspci > > output: > > It means you have an AR9285, not AR9285SE. (the last three bits have > to be 0x01, and yours is 0x5. :-) > > >> You could also try flipping the AR9285_WA_DEFAULT value and/or > >> register inivals back to the previous version? > > > > Is this a rebuild of the kernel module or configuration? > > The kernel module. > > >> So I bet it's something more subtle, like strange behaviour with > >> sleep state, powering down the PCIe bus right, etc, etc. > > > > I can trigger the hang with iwconfig wlan0 tx off, if that helps. I > > thought that sounded fairly specific to the chip... > > Have you compiled the driver with debugging? You could enable ath > debugging (set debug to 0xffffffff; I think there's a proc/sysfs > variable for this too) and then run iwconfig wlan0 tx off; see how far > it gets. It may not even be an ath9k bug.. :-) > > > Adrian > _______________________________________________ > ath9k-devel mailing list > ath9k-devel@lists.ath9k.org > https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- Lars Schotte @ Hana (F14) _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
