iwl4965 regression since 2.6.24

iwl4965 regression since 2.6.24

[Lukas Hejtmanek]

Hello,

as of 2.6.25 kernel, the intel driver iwl4965 has serious troubles to
associate with AP. I must many times set essid till the association is done.

Moreover, it seems that it is unable to associate with different AP (using the
same SSID). I must remove the module completly to be able to associate to the
different AP. I think it is big regression.

-- 
Lukáš Hejtmánek

RE: iwl4965 regression since 2.6.24

[Chatre, Reinette]

On , linux-wireless-owner@vger.kernel.org  wrote:

> Hello,
> 
> as of 2.6.25 kernel, the intel driver iwl4965 has serious troubles to
> associate with AP. I must many times set essid till the
> association is done.
> 
> Moreover, it seems that it is unable to associate with
> different AP (using the
> same SSID). I must remove the module completly to be able to
> associate to the different AP. I think it is big regression.
> 

Could you please send us some logs that can help us debug this problem?
Please load the driver with debugging (modprobe iwl4965 debug=0x43ffb)
to get detailed logs and add a detailed description about what you are
trying to do with the driver as the logs are created. Also, please
consider filing a bug at http://www.intellinuxwireless.org/bugzilla/
with these logs attached.

Thanks

Reinette

Re: iwl4965 regression since 2.6.24

[Lukas Hejtmanek]

On Wed, Apr 23, 2008 at 02:29:14PM -0700, Chatre, Reinette wrote:
> Could you please send us some logs that can help us debug this problem?
> Please load the driver with debugging (modprobe iwl4965 debug=0x43ffb)
> to get detailed logs and add a detailed description about what you are
> trying to do with the driver as the logs are created. Also, please
> consider filing a bug at http://www.intellinuxwireless.org/bugzilla/
> with these logs attached.

done at:
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1659

-- 
Lukáš Hejtmánek

Re: iwl4965 regression since 2.6.24

[Tomas Winkler]

2008/4/24 Lukas Hejtmanek <xhejtman@ics.muni.cz>:> On Wed, Apr 23, 2008 at 02:29:14PM -0700, Chatre, Reinette wrote:>  > Could you please send us some logs that can help us debug this problem?>  > Please load the driver with debugging (modprobe iwl4965 debug=0x43ffb)>  > to get detailed logs and add a detailed description about what you are>  > trying to do with the driver as the logs are created. Also, please>  > consider filing a bug at http://www.intellinuxwireless.org/bugzilla/>  > with these logs attached.>>  done at:>  http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1659>>  -->  Lukáš Hejtmánek>  -->  To unsubscribe from this list: send the line "unsubscribe linux-wireless" in>
ThanksSince we moved association process out of the driver and relaying onmac80211 association, it lookslike disassociation is not handled properly and previous configurationis not cleared correctly.  Probably in both levelsmac and the driver.Investigating....
ThanksTomas
> the body of a message to majordomo@vger.kernel.org>  More majordomo info at  http://vger.kernel.org/majordomo-info.html>˙ôčş{.nÇ+‰ˇŸŽ‰­†+%ŠË˙ąéÝś\x17ĽŠw˙ş{.nÇ+‰ˇĽŠ{ąţGŤé˙Š{ayş\x1dʇڙë,j\a­˘fŁ˘ˇhšďę˙‘ęçz_čŽ\x03(­éšŽŠÝ˘j"ú\x1aś^[m§˙˙ž\aŤţGŤé˙˘¸?™¨č­Ú&Łř§~áśiO•ćŹzˇšvŘ^\x14\x04\x1aś^[m§˙˙Ă\f˙śě˙˘¸?–IĽ

Re: iwl4965 regression since 2.6.24

[Lukas Hejtmanek]

On Wed, Apr 23, 2008 at 12:16:34PM -0400, Chris Hallinan wrote:
> I tried associating manually using the AP address itself, to all the
> cells I could see, but could not get past the "Link Quality: 0" issue.
> 
> Windows XP on this same laptop connected immediately and worked. :(

I found out that iwconfig wlan0 ap auto (which according to the man page
should reassociate with the strongest AP) does nothing at all. 

It seems that once associated with AP, the mac or iwl4965 driver (do not know
which one) is unable to associate with a different AP.

-- 
Lukáš Hejtmánek

Re: iwl4965 regression since 2.6.24

[Joel Becker]

On Wed, Apr 23, 2008 at 02:41:06PM +0200, Lukas Hejtmanek wrote:
> as of 2.6.25 kernel, the intel driver iwl4965 has serious troubles to
> associate with AP. I must many times set essid till the association is done.
> 
> Moreover, it seems that it is unable to associate with different AP (using the
> same SSID). I must remove the module completly to be able to associate to the
> different AP. I think it is big regression.

	I am experiencing the same problems on 2.6.24.  I have also
noticed that it cannot recover association after waking from sleep.  I
must set the essid before it will talk to the AP.  I always see this in
dmesg at the time:

  ADDRCONF(NETDEV_UP): wlan0: link is not ready

After I explicitly re-specify the ssid, I see this in dmesg:

  ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

	To clarify: when the interface comes up after boot or wake, it
associates but will not actually send data (Destination Host
Unreachable).  I must run "iwconfig wlan0 essid <ssid>".  After that, it
works.  When I move to a new network with a different access point, I
must unload and reload the module.
	Hopefully, I'll get a chance to run with debugging and send
along some logs.

Thinkpad x61s,
03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)


Joel

-- 

"One of the symptoms of an approaching nervous breakdown is the
 belief that one's work is terribly important."
         - Bertrand Russell 

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127