From: "Alexander Beregalov" <a.beregalov@gmail.com>
To: "David Miller" <davem@davemloft.net>
Cc: kernel-testers@vger.kernel.org, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.26-rc: SPARC: Sun Ultra 10 can not boot
Date: Sat, 21 Jun 2008 01:19:29 +0400 [thread overview]
Message-ID: <a4423d670806201419i2f0c0982j69eb423f9ecd239d@mail.gmail.com> (raw)
In-Reply-To: <20080619.190048.193701955.davem@davemloft.net>
2008/6/20 David Miller <davem@davemloft.net>:
> When you revert that changeset, there is a loop in the backtrace of
> all kernel threads, and therefore lockdep turns itself off when all of
> the stack backtrace slots get consumed by that loop in the backtraces.
>
> After the revert you should see a set of kernel messages like:
>
> BUG: MAX_STACK_TRACE_ENTRIES too low!
> turning off the locking correctness validator.
>
> and that would confirm my theory.
No, I do not have such messages.
Does it mean that we need different explanation?
next prev parent reply other threads:[~2008-06-20 21:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 14:07 Alexander Beregalov
2008-06-19 16:02 ` Alexander Beregalov
2008-06-19 23:10 ` David Miller
2008-06-20 2:00 ` David Miller
2008-06-20 21:19 ` Alexander Beregalov [this message]
2008-06-20 21:21 ` David Miller
[not found] ` <a4423d670806201542o5415cad7p6b9a38b67252cee1@mail.gmail.com>
2008-06-20 22:51 ` David Miller
2008-06-20 23:12 ` Alexander Beregalov
2008-06-20 23:21 ` David Miller
2008-06-20 23:36 ` Alexander Beregalov
2008-07-07 9:19 ` Alexander Beregalov
2008-07-07 11:01 ` David Miller
2008-07-07 13:05 ` Mikael Pettersson
2008-07-07 15:59 ` Alexander Beregalov
2008-08-08 6:01 ` David Miller
2008-08-08 9:31 ` Alexander Beregalov
2008-08-08 9:40 ` David Miller
2008-08-08 10:14 ` Alexander Beregalov
2008-08-08 10:38 ` David Miller
2008-08-08 10:56 ` Alexander Beregalov
2008-08-08 11:18 ` David Miller
2008-08-08 11:52 ` Alexander Beregalov
2008-08-08 23:17 ` David Miller
2008-08-14 3:53 ` David Miller
2008-08-14 10:19 ` Alexander Beregalov
2008-08-08 14:28 ` Alexander Beregalov
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=a4423d670806201419i2f0c0982j69eb423f9ecd239d@mail.gmail.com \
--to=a.beregalov@gmail.com \
--cc=davem@davemloft.net \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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®