From: Andi Kleen <ak@suse.de>
To: Martin Lorenz <martin@lorenz.eu.org>
Cc: linux-kernel@vger.kernel.org, jbeulich@novell.com
Subject: Re: 2.6.19-rc3: more DWARFs and strange messages
Date: 31 Oct 2006 15:31:41 +0100 [thread overview]
Message-ID: <p73hcxklfoy.fsf@verdi.suse.de> (raw)
In-Reply-To: <20061028200151.GC5619@gimli>
Martin Lorenz <martin@lorenz.eu.org> writes:
> and quite a few of those:
>
> [18504.980000] BUG: warning at kernel/cpu.c:56/unlock_cpu_hotplug()
> [18504.980000] [<c0103bdd>] dump_trace+0x69/0x1af
> [18504.980000] [<c0103d3b>] show_trace_log_lvl+0x18/0x2c
> [18504.980000] [<c01043da>] show_trace+0xf/0x11
> [18504.980000] [<c01044dd>] dump_stack+0x15/0x17
> [18504.980000] [<c0135e94>] unlock_cpu_hotplug+0x3d/0x66
> [18504.980000] [<f92e67f3>] do_dbs_timer+0x1c2/0x229 [cpufreq_ondemand]
> [18504.980000] [<c012ccb1>] run_workqueue+0x83/0xc5
> [18504.980000] [<c012d5d5>] worker_thread+0xd9/0x10c
> [18504.980000] [<c012fb36>] kthread+0xc2/0xf0
> [18504.980000] [<c010398b>] kernel_thread_helper+0x7/0x10
> [18504.980000] DWARF2 unwinder stuck at kernel_thread_helper+0x7/0x10
What gcc / binutils version do you use?
> [18504.980000]
> [18504.980000] Leftover inexact backtrace:
> [18504.980000]
> [18504.980000] =======================
>
-Andi
next prev parent reply other threads:[~2006-10-31 14:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-28 20:01 2.6.19-rc3: more DWARFs and strange messages Martin Lorenz
2006-10-31 14:31 ` Andi Kleen [this message]
2006-10-31 16:08 ` Martin Lorenz
2006-10-31 16:28 ` Jan Beulich
2006-10-31 17:28 ` Andi Kleen
2006-11-01 15:27 ` Martin Lorenz
2006-11-02 9:37 ` Jan Beulich
2006-11-02 9:48 ` Martin Lorenz
[not found] ` <20061031170320.GA6227@gimli>
2006-11-02 10:56 ` Jan Beulich
2006-11-08 16:19 ` Jan Beulich
2006-11-06 10:54 ` Adrian Bunk
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=p73hcxklfoy.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@lorenz.eu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox