On 05/18/11 17:17, Borislav Petkov wrote: > First of all, please hit "reply-to-all" next time so that all recipients > can receive your mail and not find it by chance when looking thru the > new lkml messages. > > On Wed, May 18, 2011 at 04:41:52PM -0400, James wrote: >> Here is what I did: >> >> $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.37.y.git >> $ cd linux-2.6.37.y >> $ git checkout v2.6.36 >> build and boot kernel > what does that mean? Is .36 ok? Yes, no problems. >> $ cd linux-2.6.37.y >> $ git bisect start >> $ git bisect good v2.6.36 >> $ git bisect bad v2.6.37.6 > Also, is .37.6 bad? Yes, it is bad. >> build and boot kernel >> git bisect good|bad >> repeat >> >> 3044100e58c84e133791c8b60a2f5bef69d732e4 is the first bad commit. > Which is a merge commit and it means that you most likely made a mistake > during bisection. Am I doing it right? boot kernel, cd to git source, git bisect good or bad, compile new kernel and copy it to /boot, repeat > What is actually the problem you're experiencing with .37.6? > > .. > >> How do I find out what change causes the problem? >> The problem causes my wireless card not to work. > Ah, here it is. > >> Other people have similar cards that do work so the problem seems >> isolated to my hardware but kernel-2.6.36 works so I don't think my >> hardware is faulty. > Which card is that? (adding linux-wireless) D-Link dwa552 ieee80211 phy0: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81 mem=0xffffc90000140 000, irq=16 Other people have this card working so it is probably my system configuration that is causing an obscure bug. > Please, describe in a very detailed way how your problem incarnates > itself: dmesg, error messages, what exactly do you do to trigger it? It seems to be 100% that if "ath: Failed to stop TX DMA in 100 msec after killing last frame ath: Failed to stop TX DMA!" shows up in dmesg that scans don't return any APs or 1-3 (iwlist wlan0 scan | grep SSID). If there is a different way to scan, I'll try that. > Also, can you test whether 38.6 works for ya - it could've been fixed in > the meantime. You can also test .39 which will be released any minute > now. 38.6 does NOT work and compat-wireless-2011-05-11 works on kernel-2.6.36 which is why I think it is the kernel and not the wireless code. > I think that should be enough for now. > -- 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
