Re: [ath5k-devel] Any idea what is going on inside the driver each 10 seconds ?

2009-03-13 Thread Sylvain Lamontagne
Thanks for the information. Do you think there is a way to optimize this recalibration task ? Sylvain On Fri, Mar 13, 2009 at 3:25 PM, Bob Copeland wrote: > 2009/3/13 Sylvain Lamontagne : > > Hi everybody > > > > I would like to know what, inside the ath5k > > driver, could cause an interrupt a

Re: [ath5k-devel] Any idea what is going on inside the driver each 10 seconds ?

2009-03-13 Thread Bob Copeland
2009/3/13 Sylvain Lamontagne : > Hi everybody > > I would like to know what, inside the ath5k > driver, could cause an interrupt at each 10 seconds. So, anybody know what > is going on in the ath5k driver each 10 seconds ? from base.c: static int ath5k_calinterval = 10; There's a timer that reca

Re: [ath5k-devel] Any idea what is going on inside the driver each 10 seconds ?

2009-03-13 Thread Sylvain Lamontagne
I forgot to mentioned that we are using the version inside the Kernel mainline 2.6.27.3. Thank you Sylvain On Fri, Mar 13, 2009 at 3:14 PM, Sylvain Lamontagne < sylvain.lamonta...@gmail.com> wrote: > Hi everybody > > We discovered that each 10 seconds (or very close to 10) the ath5k driver > is

[ath5k-devel] Any idea what is going on inside the driver each 10 seconds ?

2009-03-13 Thread Sylvain Lamontagne
Hi everybody We discovered that each 10 seconds (or very close to 10) the ath5k driver is getting more priority than our highest priority process. Since our custom board require critical timing, I would like to know what, inside the ath5k driver, could cause an interrupt at each 10 seconds. So, an

Re: [ath5k-devel] Thanks for TX power patch

2009-03-13 Thread Maxim Levitsky
On Fri, 2009-03-13 at 14:23 -0400, Bob Copeland wrote: > On Fri, Mar 13, 2009 at 6:38 AM, Maxim Levitsky > wrote: > > > > Just compiled and installed latest wireless-testing with Nick's patches, > > and your patch. > > > > System is rock solid, module reload/s2disk/s2ram/long transfers work > > j

Re: [ath5k-devel] Thanks for TX power patch

2009-03-13 Thread Nick Kossifidis
2009/3/13 Bob Copeland : > On Fri, Mar 13, 2009 at 6:38 AM, Maxim Levitsky > wrote: >> >> Just compiled and installed latest wireless-testing with Nick's patches, >> and your patch. >> >> System is rock solid, module reload/s2disk/s2ram/long transfers work >> just fine. > > Great, thanks for the

Re: [ath5k-devel] Thanks for TX power patch

2009-03-13 Thread Bob Copeland
On Fri, Mar 13, 2009 at 6:38 AM, Maxim Levitsky wrote: > > Just compiled and installed latest wireless-testing with Nick's patches, > and your patch. > > System is rock solid, module reload/s2disk/s2ram/long transfers work > just fine. Great, thanks for the test! -- Bob Copeland %% www.bobcopel

Re: [ath5k-devel] [TIP] BUG kmalloc-4096: Poison overwritten (ath5k_rx_skb_alloc)

2009-03-13 Thread Bob Copeland
On Fri, Mar 13, 2009 at 09:52:13AM +, Sitsofe Wheeler wrote: > The dmesg and trace can be found on > http://sucs.org/~sits/test/eeepc-debug/20090313/ . > > The one I'll note is that every time this issue has occurred I've been > connected to encrypted networks (bo

Re: [ath5k-devel] ath5k AP mode

2009-03-13 Thread Maxim Levitsky
On Thu, 2009-03-12 at 14:15 +0300, Owl wrote: > Hi, people! ;) > I can be an active beta-tester for ath5k in AP mode, because i really need > this functionality on my HomeServer %) > I too will be happy to play with AP code. But in my opinion IBSS is actually much better, since it is like AP, b

Re: [ath5k-devel] Thanks for TX power patch

2009-03-13 Thread Maxim Levitsky
On Fri, 2009-03-13 at 00:04 +0200, Maxim Levitsky wrote: > On Thu, 2009-03-12 at 17:33 -0400, Bob Copeland wrote: > > On Thu, Mar 12, 2009 at 5:32 PM, Bob Copeland wrote: > > > On Thu, Mar 12, 2009 at 5:25 PM, Maxim Levitsky > > > wrote: > > >> Just to be clear, I got oopses, and hangs after res

Re: [ath5k-devel] [TIP] BUG kmalloc-4096: Poison overwritten (ath5k_rx_skb_alloc)

2009-03-13 Thread Sitsofe Wheeler
27;t report any jumbo frame errors but it does mention ath5k phy0: noise floor calibration timeout about two hours before the poison is overwritten. The dmesg and trace can be found on http://sucs.org/~sits/test/eeepc-debug/20090313/ . The one I'll note is that every time this issue has occurre