> Colegrove<j.wholesalesupply@xxxxxxxxx> wrote: > > Thanks bob for the reply. I did not mean to shout, but someone else > > told me that I should make it very clear that I was not subscribed. > > But, now I am so it doesn't matter :) No worries, but whoever said that is wrong as far as vger.kernel.org mailing lists go, as everyone just does reply-all. (Also, top-posting is frowned upon.) > I have found the bad commit. > $ git bisect good > 1e3e6e8fe2f422f75619b1110f78bb638ae905b9 is first bad commit > commit 1e3e6e8fe2f422f75619b1110f78bb638ae905b9 > Author: Nick Kossifidis <mick@xxxxxxxxxxxxxxxxxxx> > Date: Mon Feb 9 06:15:42 2009 +0200 > > ath5k: Disable BMISS interrupts Hmm, so that's a pretty weird commit to end up with. Can you now try whatever your baseline kernel was, with just this patch reverted and see if it works for you? We don't actually do anything with BMISS yet so the only thing it could do is slow down your computer. Another possibility is that something happened between that commit and your last good ath5k commit, elsewhere in the tree, so a bisect would need to be done over the whole tree instead of just the ath5k directory. A third possibility is the issue comes and goes, or is timing related, in which case bisection really isn't useful. > Do you still think it would be wise to file a bug report for this > issue. I have yet to try the latest compat-wireless. Give 2.6.30.1 a shot as it includes a couple of fixes, otherwise bugzilla is probably the best bet. -- Bob Copeland %% www.bobcopeland.com -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
