All of lore.kernel.org
 help / color / mirror / Atom feed
From: gilles.chanteperdrix@xenomai.org (Gilles Chanteperdrix)
To: linux-arm-kernel@lists.infradead.org
Subject: bug with 3.4.6, 3.5.3, 3.6.1
Date: Thu, 11 Oct 2012 14:54:13 +0200	[thread overview]
Message-ID: <5076C175.1070103@xenomai.org> (raw)
In-Reply-To: <20121011103637.GC30598@mudshark.cambridge.arm.com>

On 10/11/2012 12:36 PM, Will Deacon wrote:
> On Thu, Oct 11, 2012 at 06:46:35AM +0100, Gilles Chanteperdrix wrote:
>> Hi,
> 
> Hi Gilles,
> 
>> when booting Linux v3.4.6, v3.5.3, or v3.6.1 on a pandaboard with an 
>> OMAP4430 ES2.1, compiled with the following configuration:
>> http://xenomai.org/~gch/config-panda
>>
>> I get the bug below after mounting the root filesystem.
>>
>> CONFIG_VMSPLIT_2G and CONFIG_THUMB2_KERNEL disabled seems to be the 
>> combination which triggers the bug.
>>
>> With this configuration, it seems the init_mm.mm_count incrementation
>> done at the beginning of secondary_start_kernel() is "lost" after the
>> calls to cpu_switch_mm() and local_flush_tlb().
>>
>> Modifying the secondary_startup() function in head.S to pass the 
>> swapper pgdir instead of the idmap pgdir in r4 also avoids the issue.
> 
> What's your PHYS_OFFSET? I suspect it's >= 2GB, in which case I have some
> ideas about this problem.

You mean the physical address of RAM ? I believe it is 0x80000000, will
check.

-- 
					    Gilles.

  reply	other threads:[~2012-10-11 12:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-11  5:46 bug with 3.4.6, 3.5.3, 3.6.1 Gilles Chanteperdrix
2012-10-11 10:36 ` Will Deacon
2012-10-11 12:54   ` Gilles Chanteperdrix [this message]
2012-10-11 13:32   ` Gilles Chanteperdrix
2012-10-11 13:59     ` Will Deacon
2012-10-11 14:01       ` Gilles Chanteperdrix
2012-10-11 14:03         ` Will Deacon
2012-10-11 19:50         ` Will Deacon
2012-10-11 20:58           ` Gilles Chanteperdrix

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=5076C175.1070103@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=linux-arm-kernel@lists.infradead.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.