From: Christian Kujau <lists@nerdbynature.de>
To: Li Zhong <zhong@linux.vnet.ibm.com>
Cc: paulus@samba.org, linuxppc-dev@lists.ozlabs.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3.7-rc7: BUG: MAX_STACK_TRACE_ENTRIES too low!
Date: Wed, 28 Nov 2012 10:59:35 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.01.1211281051000.7378@trent.utfs.org> (raw)
In-Reply-To: <1354092082.3054.19.camel@ThinkPad-T5421.cn.ibm.com>
On Wed, 28 Nov 2012 at 16:41, Li Zhong wrote:
> Would you please help to try the following fix? I don't have a powerpc32
> machine for test...
I've just applied this to 3.7-rc7 and booted the machine. I don't know how
to trigger this bug, so it might take a while until it happens again - or
not, now with your patch applied.
It happened only 2 times so far, after ~8h and after ~20h:
Nov 5 13:28:20 alice kernel: [ 0.000000] Linux version 3.7.0-rc4
Nov 5 21:00:26 alice kernel: [27148.965634] BUG: MAX_STACK_TRACE_ENTRIES too low!
Nov 26 21:53:43 alice kernel: [ 0.000000] Linux version 3.7.0-rc7
Nov 27 17:15:29 alice kernel: [69731.388717] BUG: MAX_STACK_TRACE_ENTRIES too low!
Thanks,
Christian.
--
BOFH excuse #86:
Runt packets
next prev parent reply other threads:[~2012-11-28 18:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 3:06 3.7-rc7: BUG: MAX_STACK_TRACE_ENTRIES too low! Christian Kujau
2012-11-28 3:22 ` Christian Kujau
2012-11-28 8:41 ` Li Zhong
2012-11-28 18:59 ` Christian Kujau [this message]
2012-12-01 20:32 ` Christian Kujau
2012-12-03 2:09 ` Li Zhong
2013-01-12 20:43 ` Christian Kujau
2013-01-15 6:59 ` Li Zhong
2013-01-27 22:56 ` Christian Kujau
2013-02-04 0:38 ` Christian Kujau
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.2.01.1211281051000.7378@trent.utfs.org \
--to=lists@nerdbynature.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=zhong@linux.vnet.ibm.com \
/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