From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: Armada XP (mvebu) PCIe memory (BAR/window) re-allocation
Date: Mon, 7 Apr 2014 10:45:36 -0600 [thread overview]
Message-ID: <20140407164536.GA9952@obsidianresearch.com> (raw)
In-Reply-To: <CAFJTrDuQv87t4N1pbw_mCZ=pZ82pX6cab+PmuhO1Fvvax==xdg@mail.gmail.com>
On Mon, Apr 07, 2014 at 02:03:55PM +0100, Matthew Minter wrote:
> However I am somewhat stumped on where to look next. I am going to
Things to try:
- Look at the PCI Interrupt Cause Register, see this message
from Thomas and the related thread:
http://www.spinics.net/lists/arm-kernel/msg318400.html
Do this before and after the faulting instruction. If it doesn't
change then the fault is generated internally to the SOC
- diff the lspci -vv output against the non-hotplug case that works
- Dump and verify all the mbus registers, not just through debugfs.
- Check if the PLX has some special sequence required
to hotplug
Cheers,
Jason
next prev parent reply other threads:[~2014-04-07 16:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFJTrDt7OrtE4B52419F2KGbmXeLR9NEcgF6yMTMUBe5vdKwfg@mail.gmail.com>
2014-03-26 17:06 ` Armada XP (mvebu) PCIe memory (BAR/window) re-allocation Thomas Petazzoni
2014-03-26 17:18 ` Jason Gunthorpe
2014-03-31 14:17 ` Matthew Minter
2014-04-01 16:41 ` Jason Gunthorpe
2014-04-03 9:31 ` Matthew Minter
[not found] ` <CAFJTrDu1=Hoa6NS3DaFphMUXgJYunybbdCoGiBVe1qKNQ4s3MA@mail.gmail.com>
2014-04-03 18:23 ` Jason Gunthorpe
2014-04-03 18:24 ` Thomas Petazzoni
2014-04-07 13:03 ` Matthew Minter
2014-04-07 16:45 ` Jason Gunthorpe [this message]
2014-04-08 10:57 ` Matthew Minter
2014-04-08 16:34 ` Jason Gunthorpe
2014-04-03 8:57 Matthew Minter
-- strict thread matches above, loose matches on Subject: below --
2014-03-26 16:54 Matthew Minter
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=20140407164536.GA9952@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.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 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.