linux-kernel - Re: BUG on 3.0-rc on commit d72bce0e67e8afc6eb959f656013cbb577426f1e

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: <1307978066.9218.71.camel@gandalf.stny.rr.com>
Date:	Mon, 13 Jun 2011 11:14:26 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	habanero@...ux.vnet.ibm.com
Cc:	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org, paulmck <paulmck@...ux.vnet.ibm.com>
Subject: Re: BUG on 3.0-rc on commit
 d72bce0e67e8afc6eb959f656013cbb577426f1e

On Mon, 2011-06-13 at 10:06 -0500, Andrew Theurer wrote:
> On Fri, 2011-06-10 at 18:27 +0200, Peter Zijlstra wrote:
> > On Fri, 2011-06-10 at 10:34 -0500, Andrew Theurer wrote:
> > > RIP: 0010:[<ffffffff8104e8c1>]  [<ffffffff8104e8c1>] find_lowest_rq+0xa1/0x150
> > 
> > If you've still got the vmlinux around, could you find out where in
> > find_lowest_rq that RIP is? 
> 
> Does this help?

A little, but could you also do the following: (if you had DEBUG_INFO
compiled in)

$ gdb vmlinux
gdb> li *0xffffffff8104e8c1

And give the output of that?

Thanks,

-- Steve


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