[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <200609010615_MC3-1-C9FA-ECE6@compuserve.com>
Date: Fri, 1 Sep 2006 06:12:51 -0400
From: Chuck Ebbert <76306.1226@...puserve.com>
To: Badari Pulavarty <pbadari@...il.com>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
Andi Kleen <ak@...e.de>, Jan Beulich <jbeulich@...ell.com>,
Andrew Morton <akpm@...l.org>
Subject: Re: Was: boot failure, "DWARF2 unwinder stuck at 0xc0100199"
In-Reply-To: <1157049193.22667.19.camel@...9047017100.beaverton.ibm.com>
On Thu, 31 Aug 2006 11:33:13 -0700, Badari Pulavarty wrote:
> As you can see from the following stack - it shows
>
> msync_interval() ->
> set_page_dirty() ->
> __set_page_dirty_buffers()
>
> But actual trace is (looking at the code):
>
> msync_interval() ->
> msync_page_range() ->
> msync_pud_range() ->
> msync_pgd_range() ->
> msync_pte_range() ->
> set_page_dirty() ->
> __set_page_dirty_buffers()
>
> Why is it skipping all msync_page/pud/pgd/pte_range() routines ?
Sometimes this is caused by tail calls, i.e. when the last line
of a function calls another function it can many times be optimized
into a jump.
You can disable this by compiling with CONFIG_FRAME_POINTER=y.
--
Chuck
-
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/
Powered by blists - more mailing lists