Return-path: Received: from mail-pw0-f46.google.com ([209.85.160.46]:33789 "EHLO mail-pw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752695Ab1EGBNx (ORCPT ); Fri, 6 May 2011 21:13:53 -0400 Received: by pwi15 with SMTP id 15so1650629pwi.19 for ; Fri, 06 May 2011 18:13:53 -0700 (PDT) Message-ID: <4DC49CCD.7040906@lwfinger.net> (sfid-20110507_031356_942589_60DA2390) Date: Fri, 06 May 2011 20:13:49 -0500 From: Larry Finger MIME-Version: 1.0 To: Ben Greear CC: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= , linux-wireless@vger.kernel.org, b43-dev Subject: Re: Biescting between mainline and wireless-testing References: <4DC49386.6070503@candelatech.com> In-Reply-To: <4DC49386.6070503@candelatech.com> Content-Type: text/plain; charset=UTF-8; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On 05/06/2011 07:34 PM, Ben Greear wrote: > On 05/06/2011 04:51 PM, Rafał Miłecki wrote: >> I suspect we have some ugly (hard trackable) regression between >> mainline and wireless-testing. It sounds impossible, but this seems to >> affect Broadcom cards and looks like not related to ssb or b43. >> >> Today I've compiled 2.6.38 and 2.6.39-rc6, both work GOOD. >> I've compiled wireless-testing and it failed, BAD. >> I've reverted all recent ssb patches from top and it still fails BAD. >> >> What would be the easiest way to try bisecting? I can see >> wireless-testing merges mainline quite often. Can I use some trick on >> checkouted wireless-testing? Do I have to checkout mainline and merge >> wireless-testing into it? Something even different? >> > > git bisect can handle it...I've spent some quality time finding > bugs in ath9k with that lately... The other thing to do is to see if branching wire-testing to 2.6.38 results in a workable system. What card fails? I've been busy with Realtek hardware lately and have not run very much with Broadcom, but my 4311 worked earlier this week. Larry