linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: p.pisati@gmail.com (Paolo Pisati)
To: linux-arm-kernel@lists.infradead.org
Subject: 3.8+, PL310_ERRATA_769419 and highbank: borked reboot
Date: Tue, 16 Apr 2013 18:55:16 +0200	[thread overview]
Message-ID: <20130416165516.GA3097@luxor.wired.org> (raw)

Scenario:

3.9-rc7 kernel, multiplatform support with highbank and imx6 selected, highbank
node -> reboot doesn't work (actually it works 1 out of 10 times)

And playing around with the config i was able to track it down to
PL310_ERRATA_769419.

-a config and kernel that reproduce the issue:

http://people.canonical.com/~ppisati/highbank_769419_reboot/config.brk

http://people.canonical.com/~ppisati/highbank_769419_reboot/zImage.brk

-a config and kernel that don't reproduce it: 

http://people.canonical.com/~ppisati/highbank_769419_reboot/0003-highbank-dbg-comment-out-PL310_ERRATA_769419.patch

http://people.canonical.com/~ppisati/highbank_769419_reboot/config.ok

http://people.canonical.com/~ppisati/highbank_769419_reboot/zImage.ok

If you are building pl330 support too, you need a patch like this one:

http://people.canonical.com/~ppisati/highbank_769419_reboot/0001-dma-of-dma-check-OF-pointer-property-before-derefere.patch

to avoid a NULL ptr oops during boot.

Same issue happens on 3.8, and due to my test environment (conserver
on top of ipmi for 'serial over lan') i was unable to sysrq and give you a
stacktrace, sorry.
-- 
bye,
p.

             reply	other threads:[~2013-04-16 16:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16 16:55 Paolo Pisati [this message]
2013-04-17  3:23 ` 3.8+, PL310_ERRATA_769419 and highbank: borked reboot Rob Herring

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=20130416165516.GA3097@luxor.wired.org \
    --to=p.pisati@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).