From: Andrew Morton <akpm@osdl.org>
To: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
Cc: davej@redhat.com, torvalds@osdl.org,
michal.k.k.piotrowski@gmail.com, linux-kernel@vger.kernel.org,
Jan Beulich <jbeulich@novell.com>, Andi Kleen <ak@muc.de>
Subject: Re: 2.6.18-rc3-g3b445eea BUG: warning at /usr/src/linux-git/kernel/cpu.c:51/unlock_cpu_hotplug()
Date: Sun, 6 Aug 2006 12:32:43 -0700 [thread overview]
Message-ID: <20060806123243.826105fc.akpm@osdl.org> (raw)
In-Reply-To: <6bffcb0e0608060959m164436baj9c4c602496e87f5d@mail.gmail.com>
On Sun, 6 Aug 2006 18:59:54 +0200
"Michal Piotrowski" <michal.k.k.piotrowski@gmail.com> wrote:
> caller is lock_cpu_hotplug+0x25/0xc5
> [<fd95918f>] store_speed+0x36/0x9b [cpufreq_userspace]
> [<c029fa95>] store+0x37/0x48
> [<c0104007>] show_trace_log_lvl+0x58/0x159
> [<c0104765>] show_trace+0xd/0x10
> [<c010482d>] dump_stack+0x19/0x1b
> [<c01fc842>] debug_smp_processor_id+0x96/0xac
> [<c01a8197>] sysfs_write_file+0xa6/0xcc
> [<c013e0db>] lock_cpu_hotplug+0x25/0xc5
> [<fd95918f>] store_speed+0x36/0x9b [cpufreq_userspace]
> [<c029fa95>] store+0x37/0x48
> [<c01a8197>] sysfs_write_file+0xa6/0xcc
> [<c0171577>] vfs_write+0xcd/0x179
> [<c0171c20>] sys_write+0x3b/0x71
> [<c010318d>] sysenter_past_esp+0x56/0x8d
> DWARF2 unwinder stuck at sysenter_past_esp+0x56/0x8d
> Leftover inexact backtrace:
> [<c0104765>] show_trace+0xd/0x10
> [<c010482d>] dump_stack+0x19/0x1b
> [<c01fc842>] debug_smp_processor_id+0x96/0xac
> [<c013e0db>] lock_cpu_hotplug+0x25/0xc5
> [<fd95918f>] store_speed+0x36/0x9b [cpufreq_userspace]
> [<c029fa95>] store+0x37/0x48
> [<c01a8197>] [<c0171577>] vfs_write+0xcd/0x179
>
> It's from 2.6.18-rc3-mm2.
This "unwinder stuck" thing seems to be very common.
It's a false-positive in this case - the backtrace was complete. It would
be good if we could make the did-we-get-stuck detector a bit smarter. Even
special-casing "sysenter_past_esp" would stop a lot of this..
next prev parent reply other threads:[~2006-08-06 19:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 19:04 Michal Piotrowski
2006-08-04 19:24 ` Linus Torvalds
2006-08-04 22:24 ` Dave Jones
2006-08-05 0:31 ` Dave Jones
2006-08-05 2:10 ` Dave Jones
2006-08-05 2:23 ` Dave Jones
2006-08-05 2:49 ` Dave Jones
2006-08-05 6:47 ` Dave Jones
2006-08-05 7:46 ` Andrew Morton
2006-08-05 19:47 ` Dave Jones
2006-08-05 20:02 ` Andrew Morton
2006-08-06 1:12 ` Andrew Morton
2006-08-05 10:54 ` Michal Piotrowski
2006-08-05 11:11 ` Michal Piotrowski
2006-08-05 11:26 ` Michal Piotrowski
2006-08-05 18:47 ` Dave Jones
2006-08-05 21:15 ` Michal Piotrowski
2006-08-06 16:59 ` Michal Piotrowski
2006-08-06 18:05 ` Dave Jones
2006-08-06 19:32 ` Andrew Morton [this message]
2006-08-07 1:26 ` Andi Kleen
2006-08-07 8:18 ` Jan Beulich
2006-08-15 12:23 ` Jan Beulich
2006-08-05 22:14 art
2006-08-06 1:23 ` Dave Jones
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=20060806123243.826105fc.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@muc.de \
--cc=davej@redhat.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®