From: Roland Dreier <rdreier@cisco.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: Please report all left over "DWARF2 unwinder stucks"
Date: Mon, 02 Oct 2006 12:05:25 -0700 [thread overview]
Message-ID: <adazmcev8qy.fsf@cisco.com> (raw)
In-Reply-To: <200610012201.20544.ak@suse.de> (Andi Kleen's message of "Sun, 1 Oct 2006 22:01:20 +0200")
Hi Andi, I just got this with Linus's -git updated as of this morning
(head is 95f3eff6997ae4a6754c1d874ec0a414d97c44d1). The soft lockup
is a bug in code I was testing but I was only touching drivers/infiniband,
so it shouldn't make a difference for this.
Let me know if there's any more info you need.
[ 971.926760] BUG: soft lockup detected on CPU#0!
[ 971.940287]
[ 971.940288] Call Trace:
[ 971.952076] [<ffffffff8026018f>] show_trace+0x34/0x47
[ 971.967433] [<ffffffff802601b4>] dump_stack+0x12/0x17
[ 971.982793] [<ffffffff80294a10>] softlockup_tick+0xdb/0xed
[ 971.999517] [<ffffffff8027e49e>] update_process_times+0x42/0x68
[ 972.017521] [<ffffffff802677d0>] smp_local_timer_interrupt+0x23/0x47
[ 972.036770] [<ffffffff80267c7a>] smp_apic_timer_interrupt+0x38/0x3e
[ 972.055761] [<ffffffff80254ce6>] apic_timer_interrupt+0x66/0x70
[ 972.073697] DWARF2 unwinder stuck at apic_timer_interrupt+0x66/0x70
[ 972.092424]
[ 972.096886] Leftover inexact backtrace:
[ 972.096887]
[ 972.112815] <IRQ> [<ffffffff802596dc>] _spin_unlock_irqrestore+0x8/0x9
[ 972.132905] [<ffffffff880a628e>] :ib_ipath:ipath_req_notify_cq+0x4b/0x55
[ 972.153190] [<ffffffff88227e02>] :ib_ipoib:ipoib_poll+0x4a0/0x540
[ 972.171661] [<ffffffff8020b4c1>] net_rx_action+0xa4/0x161
[ 972.188056] [<ffffffff8020f953>] __do_softirq+0x55/0xc4
[ 972.203933] [<ffffffff80316df1>] end_msi_irq_wo_maskbit+0x9/0x16
[ 972.222146] [<ffffffff8025523c>] call_softirq+0x1c/0x30
[ 972.238023] [<ffffffff8026116a>] do_softirq+0x2c/0x7e
[ 972.253382] [<ffffffff80261135>] do_IRQ+0x61/0x6a
[ 972.267703] [<ffffffff8025fa18>] default_idle+0x0/0x47
[ 972.283321] [<ffffffff80254631>] ret_from_intr+0x0/0xa
[ 972.298938] <EOI> [<ffffffff8025fa41>] default_idle+0x29/0x47
[ 972.316688] [<ffffffff802418a4>] cpu_idle+0x50/0x6f
[ 972.331525] [<ffffffff80520682>] start_kernel+0x211/0x216
[ 972.347924] [<ffffffff8052015a>] _sinittext+0x15a/0x15e
next prev parent reply other threads:[~2006-10-02 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 20:01 Please report all left over "DWARF2 unwinder stucks" Andi Kleen
2006-10-01 21:14 ` [discuss] " Dave Jones
2006-10-02 10:03 ` Andi Kleen
2006-10-02 19:05 ` Roland Dreier [this message]
2006-10-02 19:50 ` [discuss] " Andi Kleen
2006-10-02 23:12 ` Sergio Monteiro Basto
2006-10-04 14:23 ` Sergio Monteiro Basto
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=adazmcev8qy.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
/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.