Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161418AbWI2F0J (ORCPT ); Fri, 29 Sep 2006 01:26:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161419AbWI2F0J (ORCPT ); Fri, 29 Sep 2006 01:26:09 -0400 Received: from py-out-1112.google.com ([64.233.166.179]:43459 "EHLO py-out-1112.google.com") by vger.kernel.org with ESMTP id S1161418AbWI2F0F (ORCPT ); Fri, 29 Sep 2006 01:26:05 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=EGtlzjExxn+leFXM02ygneJFO0qB/X2CFiJj45NYRoJD6+yfFzX97W33UI/eW3G8iOLq4FhX8boEJwZpZDYWEet5q4jE5jeTwsE9qJHN2OgW3DeS1FQUx+WOzJAaVQem9u3k6FxZH20S19A2Jmkwlkfq5BwH9wCLusLerrsX+qM= Message-ID: Date: Thu, 28 Sep 2006 22:26:03 -0700 From: "Miles Lane" To: "Andrew Morton" Subject: Re: 2.6.18-mm2 -- EIP: [] klist_node_init+0x2b/0x3a SS:ESP 0068:f63a5f80 Cc: "Greg KH" , LKML , "James P. Ketrenos" , jgarzik@pobox.com In-Reply-To: <20060928221648.cbeb6889.akpm@osdl.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060928200431.8f7f3fea.akpm@osdl.org> <20060928214910.a3be37ea.akpm@osdl.org> <20060928221648.cbeb6889.akpm@osdl.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2034 Lines: 53 On 9/28/06, Andrew Morton wrote: > On Thu, 28 Sep 2006 22:04:00 -0700 > "Miles Lane" wrote: > > > > > but either ipw2200 or > > > > NetworkManager is still not working. I am running Fedora development > > > > (rawhide). For some reason, NM still cannot establish a connection > > > > with this kernel build (this failed with 2.6.18-mm2 previously, but I > > > > thought it was related to the BUG). "iwlist scan" can corrently > > > > detect my access point. Also, I can use iwconfig and dhclient to > > > > establish a working connection. NM fails with this output in the > > > > message log (I'll try getting a more detailed debug log out of NM): > > > > > > Another reporter mentioned that he could only get his wireless to associate > > > with his AP by using essid "any". But that was a different type of card. > > > > > > ipw2200 works OK for me, fwiw. > > > > Shall I send you my .config? > > argh. I'm afraid my head pointer keeps on wrapping past my tail pointer > recently. > > But what the heck, yes please. I'm sure James will appreciate it ;) Okay, I'll send it directly. > > > There's a largeish ipw2200 update in mainline now. That'd be worth testing. > > > > > > It looks like that ipw2200 update was in 2.6.18-mm1 though. Did that work? > > > > Yes, it did. My main problem with mm1 was the broken CPUFreq, which > > is still busted in mm2. > > Oh. Is anyone looking into that? I asked David Jones about it. He said he is in a push to get FC6 out the door and there are more pressing TODO items. > > I am rebuilding with debugging enabled in the > > ipw2200 driver. I'll see if I can capture any useful information when > > I try to associate using NM. > > Testing mainline would be useful. Will do. Miles - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/