From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Roskin Date: Tue, 03 Feb 2009 17:56:58 -0500 Subject: [ath9k-devel] ath9k in 2.6.28.3 still does not work properly In-Reply-To: References: Message-ID: <1233701818.17258.27.camel@dv> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On Tue, 2009-02-03 at 23:40 +0100, Tomek Grzechowski [k3o] wrote: > I've read on SMP problems here: > > http://www.mail-archive.com/ath9k-devel at lists.ath9k.org/msg00884.html > http://www.mail-archive.com/ath9k-devel at lists.ath9k.org/msg00929.html > > and have to admitt I'm using quad core cpu, so I'm likely to be an > example of SMP problem .. if it is really SMP problem. You can enable only one CPU by adding "maxcpus=1" to the kernel command line. This way, you'll see if the problem is SMP related. If the problem persists, you can recompile the kernel for a non-SMP configuration. This will not just disable other processors, but also the spinlocks. > I have read on "Loss of connectivity after large file transfer on > 2.6.28" at max bottom of > http://linuxwireless.org/en/users/Drivers/ath9k and its fixture in > 2.6.28.1. No need to worry about problems fixed in older kernels. They should not affect you. If you believe that the fix was wrong, please provide evidence (that is, comparison of the performance data with and without the patch). Speculations are not useful here. > I'm using my wifi mainly to connect to my router and do some use of > my internet connection which is round 10Mb/s, so im mainly not > exceeding 1.1MB/s. Anyway .. its freezing, dependin on my usage and > butterfly effect .. every minute or every few minutes, sometimes I can > work for like 20 minutes or an hour, but it is very rare. > > This is making me mad .. if I can help you testing it, debuging and so > on .. please feel free to let me know what to do, and what information > do you need to make this wifi configuration work. You could see if there are any kernel messages from the driver by running "dmesg". That may be useful. Also, it may be helpful if you provide some information about your AP, the output of "iwconfig" and the part of "iwlist wlan0 scan" pertinent to the AP. -- Regards, Pavel Roskin