From: David Miller <davem@davemloft.net>
To: a.beregalov@gmail.com
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: Thu, 19 Jun 2008 19:00:48 -0700 (PDT) [thread overview]
Message-ID: <20080619.190048.193701955.davem@davemloft.net> (raw)
In-Reply-To: <a4423d670806190902l48c542e0i6a7380a2d3e7f520@mail.gmail.com>
From: "Alexander Beregalov" <a.beregalov@gmail.com>
Date: Thu, 19 Jun 2008 20:02:44 +0400
> I have reverted this commit and
> 2.6.26-rc6-00233-g99d3b2d works fine. It can boot.
I know what the problem is.
It's hanging because lockdep is starting to actually be used. :-)
Beforehand various bugs caused lockdep to disable itself almost
immediately. So it was never actually enabled on sparc64.
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.
Lockdep really isn't usable on sparc64 at this time and it's one of
the ongoing things I'm trying to get fully fixed. The changeset in
question fixes a real bug in stack backtrace output, so it should
stay in the tree.
FWIW, I just verified the above on my ultra5 box.
next prev parent reply other threads:[~2008-06-20 2:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 14:07 2.6.26-rc: SPARC: Sun Ultra 10 can not boot Alexander Beregalov
2008-06-19 16:02 ` Alexander Beregalov
[not found] ` <a4423d670806190902l48c542e0i6a7380a2d3e7f520-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-19 23:10 ` David Miller
2008-06-20 2:00 ` David Miller [this message]
[not found] ` <20080619.190048.193701955.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-06-20 21:19 ` Alexander Beregalov
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
[not found] ` <20080620.162135.203810660.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-06-20 23:36 ` Alexander Beregalov
[not found] ` <a4423d670806201636n4f3d107bk290ed831eb5eefb4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-07 9:19 ` Alexander Beregalov
[not found] ` <a4423d670807070219s2dd43aaia29713f5076ecd0d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-07 11:01 ` David Miller
[not found] ` <20080707.040126.178187777.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-07-07 13:05 ` Mikael Pettersson
[not found] ` <18546.5247.797478.66373-gq7oiAaKCbRt3AgVzhmPzw@public.gmane.org>
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
[not found] ` <20080808.024024.205614839.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-08-08 10:14 ` Alexander Beregalov
[not found] ` <a4423d670808080314weed9178o9f9ef52803a68501-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-08-08 10:38 ` David Miller
[not found] ` <20080808.033811.129671951.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-08-08 10:56 ` Alexander Beregalov
[not found] ` <a4423d670808080356r6573102am8a1eb9dcc83910c8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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
[not found] ` <20080813.205333.202202181.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-08-14 10:19 ` Alexander Beregalov
[not found] ` <20080808.041814.41687650.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
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=20080619.190048.193701955.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a.beregalov@gmail.com \
--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