linux-kernel - Re: using mce_inject I get: RIP 10:<ffffffffa012c909> {ttm_bo

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4E5471C9.6030100@gmail.com>
Date:	Tue, 23 Aug 2011 20:36:41 -0700
From:	"Justin P. Mattock" <justinmattock@...il.com>
To:	"Luck, Tony" <tony.luck@...el.com>
CC:	Andi Kleen <andi@...stfloor.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: using mce_inject I get: RIP 10:<ffffffffa012c909> {ttm_bo_unref+0xf/0x45
 [ttm]}

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
>
>


yeah.. I randomly guessed a kernel with git reset v2.6* to find a good 
point(could of even have been 2.6.37/8/9) will give a try and see if I 
get anywhere with this(I have 15 rev's to test, Ill see yeah in a few 
days!!).

Justin P. Mattock
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/