From: Tejun Heo <tj@kernel.org>
To: Frans Pop <elendil@planet.nl>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>
Subject: Re: bisect results of MSI-X related panic (help!)
Date: Mon, 14 Sep 2009 18:40:11 +0900 [thread overview]
Message-ID: <4AAE0F7B.5050203@kernel.org> (raw)
In-Reply-To: <200909120623.49764.elendil@planet.nl>
Frans Pop wrote:
> 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.
Sorry, the oops doesn't ring a bell, well, not yet at least. It would
be great if the bisection can be narrowed down more.
--
tejun
next prev parent reply other threads:[~2009-09-14 9:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 20:09 bisect results of MSI-X related panic (help!) Jesse Brandeburg
2009-09-11 21:05 ` Jesper Juhl
2009-09-12 4:23 ` Frans Pop
2009-09-14 9:40 ` Tejun Heo [this message]
2009-09-14 9:43 ` Tejun Heo
2009-10-10 0:24 ` Jesse Brandeburg
2009-10-11 9:24 ` Jarek Poplawski
2009-10-12 7:52 ` Tejun Heo
2009-10-12 18:00 ` Brandeburg, Jesse
2009-10-13 2:39 ` Tejun Heo
2009-10-14 22:30 ` Brandeburg, Jesse
2009-10-15 7:30 ` Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AAE0F7B.5050203@kernel.org \
--to=tj@kernel.org \
--cc=elendil@planet.nl \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox