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 18:31:45 +1000 [thread overview]
Message-ID: <1253867505.7103.515.camel@pasglop> (raw)
In-Reply-To: <4ABC73C7.20403@kernel.org>
On Fri, 2009-09-25 at 16:39 +0900, Tejun Heo wrote:
> Hello,
>
> Sachin Sant wrote:
> > <4>PERCPU: chunk 1 relocating -1 -> 18 c0000000db70fb00
> > <c0000000db70fb00:c0000000db70fb00>
> > <4>PERCPU: relocated <c000000001120320:c000000001120320>
> > <4>PERCPU: chunk 1 relocating 18 -> 16 c0000000db70fb00
> > <c000000001120320:c000000001120320>
> > <4>PERCPU: relocated <c000000001120300:c000000001120300>
> > <4>PERCPU: chunk 1, alloc pages [0,1)
> > <4>PERCPU: chunk 1, map pages [0,1)
> > <4>PERCPU: map 0xd00007fffff00000, 1 pages 53544
> > <4>PERCPU: map 0xd00007fffff80000, 1 pages 53545
> > <4>PERCPU: chunk 1, will clear 4096b/unit d00007fffff00000 d00007fffff80000
> > <3>INFO: RCU detected CPU 0 stall (t=1000 jiffies)
>
> This supports my hypothesis. This is the first area being allocated
> from a dynamic chunk and cleared. PFN 53544 and 53545 have been
> allocated and successfully mapped to 0xd00007fffff00000 and
> 0xd00007fffff80000 using map_kernel_range_noflush() but when those
> addresses are actually accessed, we end up with infinite faults. The
> fault handler probably thinks that the fault has been handled
> correctly but, when the control is returned, the processor faults
> again. Benjamin, I'm way out of my depth here, can you please help?
Definitely looks like a powerpc mm problem. I'll have a look on monday.
Cheers,
Ben.
> Oh, one more simple experiment. Sachin, does the following patch make
> any difference?
>
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index 69511e6..93d29eb 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -2102,7 +2102,8 @@ struct vm_struct **pcpu_get_vm_areas(const unsigned long *offsets,
> size_t align, gfp_t gfp_mask)
> {
> const unsigned long vmalloc_start = ALIGN(VMALLOC_START, align);
> - const unsigned long vmalloc_end = VMALLOC_END & ~(align - 1);
> + //const unsigned long vmalloc_end = VMALLOC_END & ~(align - 1);
> + const unsigned long vmalloc_end = vmalloc_start + (512 << 20);
> struct vmap_area **vas, *prev, *next;
> struct vm_struct **vms;
> int area, area2, last_area, term_area;
>
>
prev parent reply other threads:[~2009-09-25 8:32 UTC|newest]
Thread overview: 23+ 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-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
2009-10-05 6:54 ` Sachin Sant
2009-09-25 8:31 ` Benjamin Herrenschmidt [this message]
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=1253867505.7103.515.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).