From: Frans Pop <elendil@planet.nl>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>
Subject: Re: bisect results of MSI-X related panic (help!)
Date: Sat, 12 Sep 2009 06:23:47 +0200
User-Agent: KMail/1.9.9
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
       Ingo Molnar <mingo@elte.hu>, Tejun Heo <tj@kernel.org>
References: <1252699744.3877.15.camel@jbrandeb-hc.jf.intel.com>
In-reply-To: <1252699744.3877.15.camel@jbrandeb-hc.jf.intel.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200909120623.49764.elendil@planet.nl>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1039
Lines: 25

Jesse Brandeburg wrote:
> I've bisected, here is my bisect log, problem is that the commit
> identified is a merge commit, and *I don't know what to revert to test*.
> It appears the parent of the merge:
> 6e15cf04860074ad032e88c306bea656bbdd0f22 is marked good, but looks to be
> in a possibly related area to the panic.

That merge does contain quite a few merge fixups, so it's quite possible 
one of them is the cause of the failure.
Maybe the simplest way to verify that is to compile both parents of the 
merge to doublecheck that they work OK. Then, if a compile of the merge 
itself is bad, the problem really is in the merge commit itself.

That commit is the "percpu" merge, so I've added Tejun (author of most of 
that branch) and Ingo (merger) in CC.

Hope that helps.

Cheers,
FJP
--
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/