From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mga01.intel.com ([192.55.52.88]:29343 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753732Ab0HWOMN (ORCPT ); Mon, 23 Aug 2010 10:12:13 -0400 Subject: Re: iwlagn fails to associate on 2.6.36-rc2 From: "Guy, Wey-Yi" To: Christoph Hellwig Cc: "linux-wireless@vger.kernel.org" In-Reply-To: <20100823110247.GA3198@infradead.org> References: <20100823110247.GA3198@infradead.org> Content-Type: text/plain Date: Mon, 23 Aug 2010 07:11:21 -0700 Message-Id: <1282572681.20674.3.camel@wwguy-ubuntu> Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, 2010-08-23 at 04:02 -0700, Christoph Hellwig wrote: > I just tried to boot into 2.6.36-rc2 and now the Intel 5100 controller > in my Thinkpad T500 fails to associate with my cheap Netgear access > point. Note that this is the same setup that already has problems > staying associated for a few kernel releases unless I keep a background > ping running. > > Any good way to debug this? There haven't been any interesting messages > in the kernel log. it is kind of strange, the connection can stay if you have background ping going? could you give more description on your problem, band/channel/... you also can turn on the debug flag debug=0x43fff to capture the current status of iwlwifi. it do require you compile kernel with full debugging support. Thanks Wey