From: Christian Kujau <lists@nerdbynature.de>
To: LKML <linux-kernel@vger.kernel.org>
Subject: BUG: MAX_STACK_TRACE_ENTRIES too low!
Date: Fri, 18 Apr 2008 00:01:34 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.1.10.0804172352240.13949@sheep.housecafe.de> (raw)
Hi there,
just before upgrading from -rc9 to -final, this showed up in the logs:
BUG: MAX_STACK_TRACE_ENTRIES too low!
turning off the locking correctness validator.
Pid: 30729, comm: mv Not tainted 2.6.25-rc9 #2
[<c013a842>] save_trace+0x92/0xa0
[<c013a894>] add_lock_to_list+0x44/0xc0
[<c013cfe1>] __lock_acquire+0xec1/0xf90
[<c01756a3>] lock_rename+0x73/0xf0
[<c013d36c>] lock_release_non_nested+0x10c/0x1b0
[<c01756a3>] lock_rename+0x73/0xf0
[<c017573b>] unlock_rename+0x1b/0x60
[<c013d4a7>] lock_release+0x97/0x170
[<c04857e3>] __mutex_unlock_slowpath+0x53/0x110
[<c017573b>] unlock_rename+0x1b/0x60
[<c017827b>] sys_renameat+0x1fb/0x210
[<c0486893>] _spin_unlock_irqrestore+0x33/0x60
[<c016e7b2>] vfs_write+0x102/0x140
[<c01782b7>] sys_rename+0x27/0x30
[<c0102eb6>] sysenter_past_esp+0x5f/0xa5
=======================
A quick search on the net tells me, this has been reported around ~2.6.18,
but this was back in 2006. My box here is still running fine, and I'm not
sure how to reproduce this one - there hasn't been much I/O when the BUG
occured. I just wanted t have this reported...
Full dmesg and .config: http://nerdbynature.de/bits/2.6.25-rc9/
Thanks,
Christian.
--
BOFH excuse #339:
manager in the cable duct
next reply other threads:[~2008-04-17 22:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 22:01 Christian Kujau [this message]
2009-02-19 12:37 Geert Uytterhoeven
2009-02-19 13:16 ` Gary Thomas
2019-03-02 7:06 syzbot
2019-03-02 11:45 ` syzbot
2019-03-08 8:11 ` Christoph Hellwig
2019-03-11 13:26 ` syzbot
2019-03-11 15:19 ` Bart Van Assche
2019-03-11 17:48 ` Linus Torvalds
2019-03-11 18:17 ` Bart Van Assche
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=alpine.DEB.1.10.0804172352240.13949@sheep.housecafe.de \
--to=lists@nerdbynature.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
all inboxes | Powered by JetHome®