From: Ingo Molnar <mingo@elte.hu>
To: Jan Beulich <jbeulich@novell.com>
Cc: Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: -rc6, "DWARF2 unwinder stuck at" ...
Date: Thu, 16 Nov 2006 18:16:14 +0100 [thread overview]
Message-ID: <20061116171614.GA4575@elte.hu> (raw)
In-Reply-To: <45351782.76E4.0078.0@novell.com>
Jan,
in 2.6.19-rc6 i'm getting frequent unwinder failures, like:
[<c0104eb5>] dump_trace+0x69/0x1b0
[<c0105013>] show_trace_log_lvl+0x17/0x2b
[<c034e6c4>] __func__.18297+0xf3fd/0x3ccf5
DWARF2 unwinder stuck at __func__.18297+0xf3fd/0x3ccf5
Leftover inexact backtrace:
[<c010534b>] show_trace+0xf/0x11
[<c0105360>] dump_stack+0x13/0x15
[<c01419e9>] __lock_acquire+0x6fe/0x98a
[<c0175956>] cache_alloc_refill+0x8f/0x534
[<c0141f14>] lock_acquire+0x5b/0x77
[<f0a32963>] __ip_ct_refresh_acct+0x123/0x15b [ip_conntrack]
[<f0a32963>] __ip_ct_refresh_acct+0x123/0x15b [ip_conntrack]
[<f0a34acc>] udp_packet+0x9e/0xaa [ip_conntrack]
[<f0a33437>] ip_conntrack_in+0x385/0x479 [ip_conntrack]
[<c01215d8>] try_to_wake_up+0x3ea/0x3f4
[<c0324300>] netlbl_mgmt_listall_cb+0xc8/0x1bd
[<c02dfe28>] nf_iterate+0x38/0x6a
[<c02e4dbf>] ip_rcv_finish+0x0/0x271
[<c02dfeac>] nf_hook_slow+0x52/0xc9
[<c02e4dbf>] ip_rcv_finish+0x0/0x271
[<c02e564f>] ip_rcv+0x1fc/0x491
[<c02e4dbf>] ip_rcv_finish+0x0/0x271
[<c02c1f2a>] sock_queue_rcv_skb+0xd5/0xdc
[<c02e5453>] ip_rcv+0x0/0x491
[<c02cac42>] netif_receive_skb+0x339/0x366
[<c02cad04>] process_backlog+0x95/0xed
[<c02c909e>] net_rx_action+0xad/0x1da
[<c012bfdc>] ksoftirqd+0x107/0x1e0
[<c012bed5>] ksoftirqd+0x0/0x1e0
[<c0139520>] kthread+0xbf/0xeb
[<c0139461>] kthread+0x0/0xeb
[<c0104c23>] kernel_thread_helper+0x7/0x10
=======================
it's quite an annoyance, i rarely see the unwinder getting a stackdump
right, without 'falling back' to the inexact backtrace ...
Ingo
next prev parent reply other threads:[~2006-11-16 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060928192048.GA17436@elte.hu>
2006-10-17 15:48 ` [PATCH] Re: UNWIND_INFO slowdown in -mm1 Jan Beulich
2006-10-18 8:45 ` Ingo Molnar
2006-10-18 10:50 ` Andi Kleen
2006-10-18 11:01 ` Ingo Molnar
2006-11-16 17:16 ` Ingo Molnar [this message]
2006-11-17 4:57 ` [patch] x86_64: stack unwinder crash fix Ingo Molnar
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=20061116171614.GA4575@elte.hu \
--to=mingo@elte.hu \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome