From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Roskin Date: Tue, 18 Aug 2009 17:15:58 -0400 Subject: [ath9k-devel] Disconnect problem (DMA failed to stop in 10 ms) In-Reply-To: <43e72e890908181407w2d658392w1f61b7f37beb04d1@mail.gmail.com> References: <74d457500908121816u57b86de6j8ea54f980cf7e75f@mail.gmail.com> <19075.41714.450997.244874@gargle.gargle.HOWL> <1250142042.2352.26.camel@ct> <200908182346.29416.kunal.gangakhedkar@gmail.com> <1250629490.7534.20.camel@mj> <43e72e890908181407w2d658392w1f61b7f37beb04d1@mail.gmail.com> Message-ID: <1250630158.7534.29.camel@mj> 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-08-18 at 14:07 -0700, Luis R. Rodriguez wrote: > On Tue, Aug 18, 2009 at 2:04 PM, Pavel Roskin wrote: > > On Tue, 2009-08-18 at 23:46 +0530, Kunal Gangakhedkar wrote: > >> > Note that Michael noticed the performance degradation. That's another > >> > target for bisection, whether it's related or not. > >> > >> Any way we can help debug this issue? > >> It gets really annoying when the driver goes berserk in the middle of a big > >> file transfer - even on LAN. :( > > > > If an older driver didn't have that problem, you can use the git bisect > > command to find which change introduced the slowdown, provided that you > > can detect it reliably. > > But note: wireless-testing sucks for bisecting, so you may want to > reproduce on the wireless-next-2.6 tree. > > http://git.kernel.org/?p=linux/kernel/git/linville/wireless-next-2.6.git;a=summary It's described as "Linville's 2.6.26 wireless networking development tree", but the Makefile indicates 2.6.31-rc5. Perhaps the description needs updating? Anyway, why is it better for bisecting? -- Regards, Pavel Roskin