On Mon, Jul 6, 2009 at 11:07 PM, Bob Copeland<me@xxxxxxxxxxxxxxx> wrote: >> 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? I haven't tried this yet, but I started up gitk and realized that the last good commit was the one previous to the bad commit. They where made 3 minutes apart in the ath5k dir. So I am assuming that the "Disable BMISS interrupts was not actually at fault. It just doesn't seem logical now that i look at it. > > 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. So I started another bisect of drivers/net/. Is this the main tree you where talking about or do you think I need to go further into the main tree? If so, how far? > > A third possibility is the issue comes and goes, or is timing > related, in which case bisection really isn't useful. I don't think this is the case, Only because I haven't noticed it to be intermittent. Either wicd works on reboot of a new kernel or it doesn't. Any attempts to get it working fail until I restart with a good commit of the kernel. > >> 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. I tried this and this is where the mystery deepens. With .30.1 it seems that I can connect to my neighbors network using dhcp but I still can not hook to my own using a static IP. I have not actually tried conneting with .30.1/dhcp to my own network, but that is the next step for me if the bisect on drivers/net fails to provide any stellar results. Once again, downgrading to kernel .29 fixes everything without changing any of my other settings. I am still 110% positive this is a kernel module/driver issue. It does make sense, no? > > -- > Bob Copeland %% www.bobcopeland.com > > If you have any other bright ideas keep them coming. -- 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
