All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yang Shi <yang.shi@windriver.com>
To: <david.daney@cavium.com>
Cc: <linux-mips@linux-mips.org>
Subject: Does CN68XX still need DCache prefetch workaround?
Date: Mon, 22 Feb 2016 10:22:06 -0800	[thread overview]
Message-ID: <56CB51CE.6070905@windriver.com> (raw)

I David,

When I booted up 4.5-rc4 kernel on CN68xx board, both pass 1.1 and pass 
2.2 reports:

Kernel panic - not syncing: OCTEON II DCache prefetch workaround not in 
place (cfa00000).
Please build kernel with proper options (CONFIG_CAVIUM_CN63XXP1).

According to the description of he option, it should just have impact on 
63xx pass 1.x. It looks confusing.

Any hint is appreciated?

Thanks,
Yang

WARNING: multiple messages have this Message-ID (diff)
From: Yang Shi <yang.shi@windriver.com>
To: david.daney@cavium.com
Cc: linux-mips@linux-mips.org
Subject: Does CN68XX still need DCache prefetch workaround?
Date: Mon, 22 Feb 2016 10:22:06 -0800	[thread overview]
Message-ID: <56CB51CE.6070905@windriver.com> (raw)
Message-ID: <20160222182206.moIM3lKutV1nDxp58Vz97eAf_dLcQ1MeAahd3D_vqe8@z> (raw)

I David,

When I booted up 4.5-rc4 kernel on CN68xx board, both pass 1.1 and pass 
2.2 reports:

Kernel panic - not syncing: OCTEON II DCache prefetch workaround not in 
place (cfa00000).
Please build kernel with proper options (CONFIG_CAVIUM_CN63XXP1).

According to the description of he option, it should just have impact on 
63xx pass 1.x. It looks confusing.

Any hint is appreciated?

Thanks,
Yang

             reply	other threads:[~2016-02-22 18:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22 18:22 Yang Shi [this message]
2016-02-22 18:22 ` Does CN68XX still need DCache prefetch workaround? Yang Shi
2016-02-22 18:38 ` David Daney
2016-02-22 18:40   ` Yang Shi
2016-02-22 18:40     ` Yang Shi

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=56CB51CE.6070905@windriver.com \
    --to=yang.shi@windriver.com \
    --cc=david.daney@cavium.com \
    --cc=linux-mips@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.