I believe that a main problem is that people have trouble reproducing it. and despite my -somewhat- implicit question there is not more information in this thread now. Other than some symptoms. It would probably help if you posted system/software specifications and debug info to a (new) bug over at bughost.org. (modprobe iwl3945 debug=0x43fff) to allow for it to be tracked better? Because now imho we are just poking at it with a medium length stick. With the information here, I honestly have no idea where to look, others might have the same problem. ian Jens Axboe wrote: > On Thu, Nov 15 2007, John W. Linville wrote: >> On Thu, Nov 15, 2007 at 10:39:22AM +0100, Jens Axboe wrote: >>> On Thu, Nov 15 2007, Ismail Dönmez wrote: >>>> Saturday 10 November 2007 Tarihinde 04:18:27 yazm????t??: >>>>> I wonder if anybody knows something more about this issue by now, >>>>> as it appears to occur to a few people. >>>>> >>>>> I reread the thread (rather quickly) but I do not see many specifications >>>>> of driver/mac80211/kernel. The few cases that do contain specs all appear >>>>> to be using fedora (don't want to jump to conclusions). But just wondering >>>>> if anybody experienced this on any other kernel? >>>> Btw this is still not fixed in latest git (post rc2). >>> I'll second that, using todays snap still requires me to do an iwlist >>> scan before I can use the network. >>> >>> Is anyone working on this at all? This was reported a month ago, yet no >>> progress or real developer interest in fixing this is apparent. >> I don't see any pending patches that seem relevant. FWIW I'll probably >> round-up what I do have and make them available today (and probably >> in a Fedora kernel too). >> >> Does the disable_hw_scan=1 still work for you? Perhaps we should >> consider making that the default... > > disable_hw_scan=1 never worked for me - I tried it, and it made no > difference. I _have_ to do an iwlist wlan0 scan before it links with my > access point, otherwise it doesn't work. > - 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
