From: "Miles Lane" <miles.lane@gmail.com>
To: "Andrew Morton" <akpm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: 2.6.18-rc5-mm1 + all hotfixes -- BUG: MAX_STACK_TRACE_ENTRIES too low!
Date: Sat, 2 Sep 2006 20:03:46 -0700 [thread overview]
Message-ID: <a44ae5cd0609022003i2b3157a2kb8bcd6f4f778b6c9@mail.gmail.com> (raw)
Sorry Andrew. I don't see clues here to help me target the report to
a maintainer.
I hope this helps.
BUG: MAX_STACK_TRACE_ENTRIES too low!
turning off the locking correctness validator.
[<c1003c97>] dump_trace+0x69/0x1b7
[<c1003dfa>] show_trace_log_lvl+0x15/0x28
[<c10040f5>] show_trace+0x16/0x19
[<c1004110>] dump_stack+0x18/0x1d
[<c102d4d0>] save_trace+0xbb/0xc8
[<c102d53c>] add_lock_to_list+0x5f/0x7d
[<c102f3ce>] __lock_acquire+0x93b/0x9f8
[<c102f75e>] lock_acquire+0x56/0x74
[<c11dcdb0>] _spin_lock+0x24/0x32
[<c105471f>] anon_vma_prepare+0x46/0xce
[<c1050014>] __handle_mm_fault+0xed/0x804
[<c1012c1a>] do_page_fault+0x214/0x4c1
[<c11dd629>] error_code+0x39/0x40
DWARF2 unwinder stuck at error_code+0x39/0x40
Leftover inexact backtrace:
[<c1003dfa>] show_trace_log_lvl+0x15/0x28
[<c10040f5>] show_trace+0x16/0x19
[<c1004110>] dump_stack+0x18/0x1d
[<c102d4d0>] save_trace+0xbb/0xc8
[<c102d53c>] add_lock_to_list+0x5f/0x7d
[<c102f3ce>] __lock_acquire+0x93b/0x9f8
[<c102f75e>] lock_acquire+0x56/0x74
[<c11dcdb0>] _spin_lock+0x24/0x32
[<c105471f>] anon_vma_prepare+0x46/0xce
[<c1050014>] __handle_mm_fault+0xed/0x804
[<c1012c1a>] do_page_fault+0x214/0x4c1
[<c11dd629>] error_code+0x39/0x40
[<c105fe67>] do_sync_read+0xb8/0xf2
[<c10601e1>] vfs_read+0xa7/0x149
[<c1060a81>] sys_read+0x3a/0x61
[<c1002d41>] sysenter_past_esp+0x56/0x8d
=======================
--
VGER BF report: H 0.0999452
next reply other threads:[~2006-09-03 3:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-03 3:03 Miles Lane [this message]
2006-09-03 4:20 ` Andrew Morton
2006-09-03 12:54 ` Ingo Molnar
2006-09-03 17:05 ` Miles Lane
2006-09-03 18:15 ` Miles Lane
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=a44ae5cd0609022003i2b3157a2kb8bcd6f4f778b6c9@mail.gmail.com \
--to=miles.lane@gmail.com \
--cc=akpm@osdl.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 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®