From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755266AbYDWWMo (ORCPT ); Wed, 23 Apr 2008 18:12:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752562AbYDWWMf (ORCPT ); Wed, 23 Apr 2008 18:12:35 -0400 Received: from rgminet01.oracle.com ([148.87.113.118]:20118 "EHLO rgminet01.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751765AbYDWWMe (ORCPT ); Wed, 23 Apr 2008 18:12:34 -0400 Date: Wed, 23 Apr 2008 15:11:23 -0700 From: Joel Becker To: Lukas Hejtmanek Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org Subject: Re: iwl4965 regression since 2.6.24 Message-ID: <20080423221123.GC17022@mail.oracle.com> Mail-Followup-To: Lukas Hejtmanek , linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org References: <20080423124105.GA4783@ics.muni.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080423124105.GA4783@ics.muni.cz> X-Burt-Line: Trees are cool. X-Red-Smith: Ninety feet between bases is perhaps as close as man has ever come to perfection. User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 ". 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