From: Adrian Bunk <bunk@stusta.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc3: more DWARFs and strange messages
Date: Mon, 6 Nov 2006 11:54:42 +0100 [thread overview]
Message-ID: <20061106105442.GK5778@stusta.de> (raw)
In-Reply-To: <20061028200151.GC5619@gimli>
Martin, did commit 4b96b1a10cb00c867103b21f0f2a6c91b705db11 that is now
in Linus' tree fix this issue?
On Sat, Oct 28, 2006 at 10:01:51PM +0200, Martin Lorenz wrote:
> With my recent kernel pulled from git on friday I see quite some DWARFs and
> other strange messages.
>
> lots of those:
> [18038.721000] thinkpad_ec: thinkpad_ec_request_row: bad end STR3:
> (0x11:0x00)->0x80
>
> this was said to be triggered by the combination of hdaps and tp_smapi but I
> do not load the tp_smapi module ...
> hdaps is configured
>
> 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
> [18504.980000]
> [18504.980000] Leftover inexact backtrace:
> [18504.980000]
> [18504.980000] =======================
>
>
> full config and dmesg is in
> http://www.lorenz.eu.org/~mlo/kernel/config.2.6.19-rc3-e1-ie-tp-43.3+1757-g18462d6b-dirty.gz
> http://www.lorenz.eu.org/~mlo/kernel/dmesg.2.6.19-rc3-e1-ie-tp-43.3+1757-g18462d6b-dirty.boot
> http://www.lorenz.eu.org/~mlo/kernel/dmesg.2.6.19-rc3-e1-ie-tp-43.3+1757-g18462d6b-dirty.run
>
> and more
> http://www.lorenz.eu.org/~mlo/kernel/?C=M;O=D
>
> greets
> mlo
> --
> Dipl.-Ing. Martin Lorenz
>
> They that can give up essential liberty
> to obtain a little temporary safety
> deserve neither liberty nor safety.
> Benjamin Franklin
>
> please encrypt your mail to me
> GnuPG key-ID: F1AAD37D
> get it here:
> http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0xF1AAD37D
>
> ICQ UIN: 33588107
prev parent reply other threads:[~2006-11-06 10:54 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
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 [this message]
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=20061106105442.GK5778@stusta.de \
--to=bunk@stusta.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox