From: Darren Stevens <darren@stevens-zone.net>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Pat Wall <pjwall@mac.com>, Alex Perez <aperez@alexperez.com>,
matthew@a-eon.com,
Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>,
R.T.Dickinson <rtd2@xtra.co.nz>,
Christian Zigotzky <chzigotzky@xenosoft.de>
Subject: Re: pasemi: Fix boot failure on 4.7-rc1
Date: Fri, 01 Jul 2016 16:29:43 +0100 (BST) [thread overview]
Message-ID: <486a5b4c86b.69ed7e66@auth.smtp.1and1.co.uk> (raw)
In-Reply-To: <CAOesGMgvNY8YBeyT3uMfD5XyQbhv0ucFtC8EVHS7gwrTmTNzGw@mail.gmail.com>
Hello Olof
On 29/06/2016, Olof Johansson wrote:
> I don't see the panic here on a Chitra, at least not on recent -next.
>
> What config are you building with when you see this?
If you are not seeing this on the Chitra, it means that our Nemo patch
is causing the problem. I don't know where, as we haven't patched the
pas_pci_init function, or any function it directly calls,
although there are patches in pasemi/pci.c to enable support for the
SB600.
The best solution would be for us to add the patch for setup.c I found to
our nemo patch.
Sorry for wasting everyones time.
> Please cc me on PA Semi related patches if you want my attention. I
> still have hardware, in fact I boot every -next release on it through
> automation.
Didn't know that, I will do so in future, just be aware that all of my
patches will be in relation to the X1000 as that is the only PA-Semi machine
I have here.
If you have the time, there is something you can check for us - we've had to
add 'PPC_PASEMI_IOMMU_DMA_FORCE' to our config since 4.4 to get the onboard
gig-e ethernet to work. We need PPC_PASEMI_IOMMU for the SB600, or we are
stuck with a kernel that will only work with 2GRam
Regards
Darren
next prev parent reply other threads:[~2016-07-01 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 20:06 [PATCH v2 RFC] pasemi: Fix boot failure on 4.7-rc1 Darren Stevens
2016-06-30 1:37 ` Aneesh Kumar K.V
2016-06-30 6:59 ` Olof Johansson
2016-06-30 8:36 ` Aneesh Kumar K.V
2016-07-01 15:29 ` Darren Stevens [this message]
2016-07-04 5:51 ` [v2,RFC] " Michael Ellerman
2016-07-04 6:58 ` Christian Zigotzky
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=486a5b4c86b.69ed7e66@auth.smtp.1and1.co.uk \
--to=darren@stevens-zone.net \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=aperez@alexperez.com \
--cc=chzigotzky@xenosoft.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matthew@a-eon.com \
--cc=olof@lixom.net \
--cc=pjwall@mac.com \
--cc=rtd2@xtra.co.nz \
/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).