From: "Justin P. Mattock" <justinmattock@gmail.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: using mce_inject I get: RIP 10:<ffffffffa012c909> {ttm_bo_unref+0xf/0x45 [ttm]}
Date: Sat, 27 Aug 2011 08:03:06 -0700 [thread overview]
Message-ID: <4E59072A.5040108@gmail.com> (raw)
In-Reply-To: <987664A83D2D224EAE907B061CE93D5301EA5B717B@orsmsx505.amr.corp.intel.com>
On 08/23/2011 01:15 PM, Luck, Tony wrote:
>> its easily fixable, but not sure its a good idea due to bisect going
>> through commits(afraid I might go astray with the bisect if I add any
>> patches).
>
> Rather than fixing a bad build - you can try moving to a nearby commit
> (use "gitk" to get a view of the structure around the commit that git
> bisect suggested). In the early stages of a bisection, it doesn't really
> matter much if you build the mid-point that bisect provided, or some
> nearby on - just be sure to mark good/bad the commit you actually built.
>
> -Tony
>
>
well.. after bisecting(with no results), I found that something in my
.config was causing this, so after looking through, I found that having
X86_MCE_INJECT = y causes the pauses when the timeouts occur
let me know if I need to supply any info.
Justin P. Mattock
next prev parent reply other threads:[~2011-08-27 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-21 2:31 using mce_inject I get: RIP 10:<ffffffffa012c909> {ttm_bo_unref+0xf/0x45 [ttm]} Justin P. Mattock
2011-08-21 22:16 ` Andi Kleen
2011-08-21 23:08 ` Justin P. Mattock
2011-08-23 18:01 ` Justin P. Mattock
2011-08-23 20:15 ` Luck, Tony
2011-08-24 3:36 ` Justin P. Mattock
2011-08-27 15:03 ` Justin P. Mattock [this message]
2011-08-27 15:12 ` Andi Kleen
2011-08-30 1:07 ` huang ying
2011-08-30 15:38 ` Justin P. Mattock
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=4E59072A.5040108@gmail.com \
--to=justinmattock@gmail.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.