linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dinh.linux@gmail.com (Dinh Nguyen)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] ARM: socfpga: L2 cache init
Date: Tue, 24 Feb 2015 17:55:05 -0600	[thread overview]
Message-ID: <CADhT+wcpWcfca6JWLAfpQm_yPHOpTRRbCpiikUEs0ha1NHq3TQ@mail.gmail.com> (raw)
In-Reply-To: <20150217222817.GS8656@n2100.arm.linux.org.uk>

On Tue, Feb 17, 2015 at 4:28 PM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Tue, Feb 17, 2015 at 04:00:47PM -0600, Dinh Nguyen wrote:
>> On Fri, Feb 13, 2015 at 2:01 AM, Steffen Trumtrar
>> <s.trumtrar@pengutronix.de> wrote:
>> > Yes, seems very likely that Russell is right.
>>
>> The bug doesn't happen if I disable the L2. Digging more...
>
> What ensures that the value written to socfpga_cpu1start_addr (by
> of_property_read_u32() in socfpga_sysmgr_init(), called at .init_irq
> time) is visible to the secondary CPU?

Yes, I was able use a JTAG debugger and can see that the
secondary CPU is not seeing socfpga_cpu1start_addr correctly when the
error occurs.

>
> From what I can see, the physical address written there is not
> guaranteed to be flushed from all levels of cache.
>
> The flush_cache_all() in socfpga_boot_secondary() won't do the job -
> that won't touch the L2C-310.
>

Do you have a recommendation on what should be done?

Thanks,
Dinh

  reply	other threads:[~2015-02-24 23:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06 10:39 [BUG] ARM: socfpga: L2 cache init Steffen Trumtrar
2015-02-06 11:05 ` Russell King - ARM Linux
2015-02-09 15:53   ` Steffen Trumtrar
2015-02-09 16:43     ` Dinh Nguyen
2015-02-09 18:58       ` Steffen Trumtrar
2015-02-09 21:30         ` Steffen Trumtrar
2015-02-12 22:39           ` Dinh Nguyen
2015-02-13  8:01             ` Steffen Trumtrar
2015-02-17 22:00               ` Dinh Nguyen
2015-02-17 22:28                 ` Russell King - ARM Linux
2015-02-24 23:55                   ` Dinh Nguyen [this message]
2015-02-25  8:21                     ` Steffen Trumtrar
2015-02-25  9:26                     ` Russell King - ARM Linux
2015-02-25 16:30                       ` Dinh Nguyen
2015-02-26  8:30                         ` Steffen Trumtrar
2015-03-04 10:23                         ` Steffen Trumtrar
2015-03-04 18:37                           ` Dinh Nguyen
2015-03-09 17:15                             ` Russell King - ARM Linux

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=CADhT+wcpWcfca6JWLAfpQm_yPHOpTRRbCpiikUEs0ha1NHq3TQ@mail.gmail.com \
    --to=dinh.linux@gmail.com \
    --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 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).