From: "Bjoern B. Brandenburg" <bbb@email.unc.edu>
To: sparclinux@vger.kernel.org
Subject: Re: enabling lockdep causes boot failure on a SUN T2000
Date: Fri, 09 May 2008 01:50:06 +0000 [thread overview]
Message-ID: <4823ADCE.4050009@email.unc.edu> (raw)
In-Reply-To: <48238125.7040900@email.unc.edu>
David Miller wrote:
> From: "Bjoern B. Brandenburg" <bbb@email.unc.edu>
>> I've been having a hard time getting Linux (vanilla 2.6.24 and 2.6.25)
>> to boot on our Niagara box.
>
> We know about this problem already. Thanks for reporting.
>
> This changeset below was meant to improve things, but t1000/t2000
> systems still get wedged.
Thanks for the pointer.
Based on your commit, I tried to disable stack trace support (with the
intent to get at least some output in the event of deadlock) with the
following patch:
diff --git a/kernel/lockdep.c b/kernel/lockdep.c
index e2c07ec..b468790 100644
--- a/kernel/lockdep.c
+++ b/kernel/lockdep.c
@@ -342,7 +342,9 @@ static int save_trace(struct stack_trace *trace)
trace->skip = 3;
- save_stack_trace(trace);
+ /* Work around: this doesn't work on the T2000.
+ * save_stack_trace(trace);
+ */
trace->max_entries = trace->nr_entries;
I figured that if the flushes are the root cause, then this should take
care of the problem. However, the kernel still doesn't boot.
Is there anything else that I can disable to get a partially working
lockdep?
Thanks,
Bjoern
next prev parent reply other threads:[~2008-05-09 1:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 22:39 enabling lockdep causes boot failure on a SUN T2000 Bjoern B. Brandenburg
2008-05-08 23:07 ` David Miller
2008-05-09 1:50 ` Bjoern B. Brandenburg [this message]
2008-05-09 4:21 ` David Miller
2008-05-09 4:55 ` Bjoern Brandenburg
2008-05-09 5:02 ` David Miller
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=4823ADCE.4050009@email.unc.edu \
--to=bbb@email.unc.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.