From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Tejun Heo <tj@kernel.org>
Cc: Linux/PPC Development <linuxppc-dev@ozlabs.org>,
David Miller <davem@davemloft.net>
Subject: Re: 2.6.31-git5 kernel boot hangs on powerpc
Date: Fri, 25 Sep 2009 19:48:31 +1000 [thread overview]
Message-ID: <1253872111.7103.520.camel@pasglop> (raw)
In-Reply-To: <4ABC86E0.9090807@kernel.org>
On Fri, 2009-09-25 at 18:01 +0900, Tejun Heo wrote:
> > With this patch applied the machine boots OK :-)
>
> Ah... so, the problem really is too high address. If you've got some
> time, it might be interesting to find out how far high is safe.
>
Might give me a clue about what the problem is but I think I'll just
cook up a test case that forcibly vmap something high up and see how it
goes from there. It could be a very old bug that nobody ever noticed
because our vmalloc space on 64-bit is so huge :-)
Cheers,
Ben.
next prev parent reply other threads:[~2009-09-25 9:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 12:25 2.6.31-git5 kernel boot hangs on powerpc Sachin Sant
2009-09-16 12:25 ` Sachin Sant
2009-09-17 10:51 ` Sachin Sant
2009-09-17 11:13 ` Benjamin Herrenschmidt
2009-09-17 15:53 ` Tejun Heo
2009-09-17 16:41 ` Sachin Sant
2009-09-19 8:54 ` Sachin Sant
2009-09-23 8:23 ` Sachin Sant
2009-09-23 8:34 ` Tejun Heo
2009-09-23 14:17 ` Tejun Heo
2009-09-24 7:58 ` Sachin Sant
2009-09-24 12:59 ` Tejun Heo
2009-09-24 13:23 ` Sachin Sant
2009-09-24 21:05 ` Benjamin Herrenschmidt
2009-09-25 3:22 ` Tejun Heo
2009-09-25 3:40 ` Benjamin Herrenschmidt
2009-09-25 7:15 ` Sachin Sant
2009-09-25 7:39 ` Tejun Heo
2009-09-25 7:43 ` Tejun Heo
2009-09-25 8:03 ` Sachin Sant
2009-09-25 9:01 ` Tejun Heo
2009-09-25 9:48 ` Benjamin Herrenschmidt [this message]
2009-10-05 6:54 ` Sachin Sant
2009-09-25 8:31 ` Benjamin Herrenschmidt
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=1253872111.7103.520.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=tj@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.