All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: "linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: Kernel crash in 2.6.32.6 / bcm1480 with 16k page size
Date: Fri, 29 Jan 2010 07:12:20 -0800	[thread overview]
Message-ID: <20100129151220.GA3882@ericsson.com> (raw)
In-Reply-To: <20100129132406.GD5685@linux-mips.org>

On Fri, Jan 29, 2010 at 08:24:07AM -0500, Ralf Baechle wrote:
> On Thu, Jan 28, 2010 at 07:55:14AM -0800, Guenter Roeck wrote:
> > 
> > I get the following kernel crash when running a 2.6.32.6 kernel on a bcm1480 cpu.
> > It only happens if I configure a page size of 16k or 64k; 4k page size is fine.
> > 
> > A similar problem was recently fixed for ppc. It turned out to be a problem in ppc
> > specific memory management code, so that fix won't help here.
> > 
> > Has anyone else seen this before ? Any idea where to start looking for the problem ?
> 
> Supposedly this was working for SB1.  I suggest you find an older kernel
> version that works for your with 16k pages then use git bisect to find
> the problem.
> 
It used to work with 2.6.27.

However, bisect won't work, because the code in question (per cpu memory allocation) was
completely rewritten since then.

The new percpu code tries to allocate memory just below VMALLOC_END. This works on sb1 for
a page size of 4k, but not for a page size of 16k and 64k. The value of VMALLOC_END depends
on the page size.

ppc had a similar problem. It had nothing to do with the new percpu memory allocation code,
but with memory alocation close to VMALLOC_END. In other words, it was a day-one bug which
was never noticed because allocating memory in that address space is highly unlikely.

I suspect the same is the case here. I could write some code for 2.6.27, to test the same
memory allocation there, but I am quite sure the problem is going to show up there as well.

So first question would be: Has anyone successfully loaded a 64 bit mips kernel with 2.6.32 
and a page size of 16k or 64k ? This would at least help me reducing the problem to sb1.

Thanks,
Guenter

  reply	other threads:[~2010-01-29 15:10 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-28 15:55 Kernel crash in 2.6.32.6 / bcm1480 with 16k page size Guenter Roeck
2010-01-29 13:24 ` Ralf Baechle
2010-01-29 15:12   ` Guenter Roeck [this message]
2010-01-29 17:11     ` David Daney
2010-01-29 18:06       ` Ralf Baechle
2010-01-29 18:21         ` Guenter Roeck
2010-01-30  2:05           ` Ralf Baechle
2010-01-30 21:34             ` Guenter Roeck
2010-01-31  3:19               ` Guenter Roeck
2010-01-29 18:39         ` Guenter Roeck
2010-01-29 18:56           ` David Daney
2010-01-29 19:25             ` Guenter Roeck
2010-01-29 19:28               ` David Daney
2010-01-29 19:58                 ` Guenter Roeck
2010-01-31  9:10                   ` Maciej W. Rozycki
2010-01-31 16:55                     ` Guenter Roeck
2010-02-01  2:18                       ` Ralf Baechle
2010-02-01 14:50                         ` Maciej W. Rozycki
2010-02-01 15:26                           ` Ralf Baechle
2010-02-01 23:11                             ` Maciej W. Rozycki
2010-02-01 15:04                         ` Guenter Roeck
2010-02-01 20:21                         ` Guenter Roeck
2010-02-01 20:49                           ` Ralf Baechle
2010-02-01 21:12                             ` Guenter Roeck
2010-01-29 20:00                 ` Guenter Roeck
2010-01-29 20:23                   ` David Daney
2010-01-29 22:19                     ` Guenter Roeck
2010-01-29 18:24       ` Guenter Roeck

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=20100129151220.GA3882@ericsson.com \
    --to=guenter.roeck@ericsson.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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.