Messages in this thread | | | Date | Sun, 6 Aug 2006 12:32:43 -0700 | From | Andrew Morton <> | Subject | Re: 2.6.18-rc3-g3b445eea BUG: warning at /usr/src/linux-git/kernel/cpu.c:51/unlock_cpu_hotplug() |
| |
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.. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |