Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762715AbZCQHvo (ORCPT ); Tue, 17 Mar 2009 03:51:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755126AbZCQHvc (ORCPT ); Tue, 17 Mar 2009 03:51:32 -0400 Received: from xc.sipsolutions.net ([83.246.72.84]:44408 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754121AbZCQHvb (ORCPT ); Tue, 17 Mar 2009 03:51:31 -0400 Subject: Re: 2.6.29-rc8: Reported regressions from 2.6.28 From: Johannes Berg To: Jeff Chua Cc: Linus Torvalds , Ingo Molnar , "Rafael J. Wysocki" , Linux Kernel Mailing List , Adrian Bunk , Andrew Morton , Kernel Testers List , Network Development , "John W. Linville" In-Reply-To: (sfid-20090317_005551_652269_7D5AC813) References: <1237140665.24621.2.camel@johannes.local> <1237143683.24621.7.camel@johannes.local> <20090315202603.GA9077@elte.hu> (sfid-20090317_005551_652269_7D5AC813) Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-lkT8FdbDuHdh8xzkiIpe" Date: Tue, 17 Mar 2009 08:50:12 +0100 Message-Id: <1237276212.18086.11.camel@johannes.local> Mime-Version: 1.0 X-Mailer: Evolution 2.24.5 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2935 Lines: 69 --=-lkT8FdbDuHdh8xzkiIpe Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2009-03-17 at 07:55 +0800, Jeff Chua wrote: > > IOW, if you've pinpointed 71c11fb57b924c160297ccd9e1761db598d00ac2 as > > being bad, then you should go back and double-check that its parent > > (in this case 4607816f608b42a5379aca97ceed08378804c99f) is good. > > Because if it's parent is also bad, then that just means that you made > > some mistake in "git bisect". > > In this case, it really sounds like maybe you marked the parent good, e= ven > > though you should have marked it bad. >=20 > I should have been more careful, just got thrown off during the last > few steps of the bisect. But with the bad association to the AP after > a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9 (iwlwifi: remove implicit > direct scan), can someone suggest where to go from here? That actually makes some sense, though I'm convinced the code I removed there is actually wrong that doesn't mean it couldn't have had positive side effects too. I'll take a look at it, in the meantime your time would be better spent trying to capture what's going on on the air instead of bisecting again. If you don't have a second device to monitor, you can also create a monitor interface as such: iw dev wlan0 interface add moni0 type monitor flags none and run tcpdump on the resulting 'moni0' interface while you try to associate etc. Write the packets to files and send them to me. Due to this implicit scan modification in the driver that I removed, however, I won't see scans in that file, so it won't be all that useful, a capture made on a second device would be much better. johannes --=-lkT8FdbDuHdh8xzkiIpe Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Comment: Johannes Berg (powerbook) iQIcBAABAgAGBQJJv1YyAAoJEKVg1VMiehFYxv4P/3qk3ba1W7WeZDxeSWe5lzXw 7d4LuKDgw8TEpfZBZgcf4eZuZsmuXBZGa29LPEheLHMbICrGIxLbOlPFJ0xzv49+ FThedraa26mmAGU1Y1m/9Kpo8SKFNmfsVxi5rgjWUixA8HPk+038tABwQDdKkbS6 /cx1F3Au5RKsSXMMIebI6/7EF9z8Znv3TD7ymVdp5q5kXPgDRVJJisDg6eXaoVHg gJaJrkFnwXKVV/oAdAPbmjNpbtOrxA68VTxxtmAkGs+LuW9B1p4R9YFb3cnfBiCj IXwOLPG6DzMqU/txXIWo0Z79Y0F4LKysIX5+NtnAKh2KXv9QntAHtcCAYju8uc0S KZTbwSkWGWnfFRtdIoe0dbZ831OPSToCeEz1a1AdLkI2wksrvc0U12ZyfJ7orRnz JvcorvGT/zKclXMegdL0aX9UAq+K47WjeX/oJ4wvbRuEkdai+lJ66VYDzzu1RsTj wBWeJLcn14adDWa0mWqfOdmgkJ4CtmnpMPq30GN47E8lV2/mhRXOOHjnQbwaQPmc 1Q9GhSjRLQI08gmJctO+qAizmt4CDgxYTHxiN2DQMRriHVlzJ2fGsKp58kXYWa4k Nh0BphA2dKPci7ZLcumBN9oP9X3FCE5SYXiI/sDkQ1Klz6tngXj7JeobjfqxW61P YAE5sRPTNvhTqV6e+Cfi =iPZ1 -----END PGP SIGNATURE----- --=-lkT8FdbDuHdh8xzkiIpe-- -- 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/