All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Michael Ellerman <mpe@ellerman.id.au>,
	Darren Stevens <darren@stevens-zone.net>,
	linuxppc-dev@lists.ozlabs.org
Cc: Pat Wall <pjwall@mac.com>,
	aperez@alexperez.com, matthew@a-eon.com,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	"R.T.Dickinson" <rtd2@xtra.co.nz>
Subject: [v2,RFC] pasemi: Fix boot failure on 4.7-rc1
Date: Mon, 4 Jul 2016 08:58:08 +0200	[thread overview]
Message-ID: <b48a3917-0fdb-0a04-51d3-5aa0e054af44@xenosoft.de> (raw)
In-Reply-To: <3rjbjg4fyfz9sXx@ozlabs.org>

Many thanks!

- Christian

On 04 July 2016 at 07:51 AM, Michael Ellerman wrote:
> On Wed, 2016-29-06 at 20:06:28 UTC, Darren Stevens wrote:
>> Commit:d6a9996e84ac4beb7713e9485f4563e100a9b03e (powerpc/mm:
>>      vmalloc abstraction in preparation for radix) turned kernel memory
>>      and IO addresses from #defined constants to variables initialised
>>      at runtime.
>>      
>>      On PA6T systems the setup_arch machine call initialises the onboard
>>      PCI-e root-ports, and uses pci_io_base to do this, which is now before
>>      its value has been set resulting in a panic right after 'booting
>>      linux via __start()'
>>
>>      Move the pci_io_base initialisation to the same place as vmalloc
>>      ranges are set (hash__early_init_mmu()/radix__early_init_mmu())
>>      
>>      Reported-by: Christian Zigotzky <chzigotzky@xenosoft.de>
>>      Signed-off-by: Darren Stevens <darren@stevens-zone.net>
>> Reviewed-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> Applied to powerpc fixes, thanks.
>
> https://git.kernel.org/powerpc/c/bfa37087aa04e45f56c41142df
>
> cheers
>

      reply	other threads:[~2016-07-04  6:58 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
2016-07-04  5:51 ` [v2,RFC] " Michael Ellerman
2016-07-04  6:58   ` Christian Zigotzky [this message]

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=b48a3917-0fdb-0a04-51d3-5aa0e054af44@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=aperez@alexperez.com \
    --cc=darren@stevens-zone.net \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=matthew@a-eon.com \
    --cc=mpe@ellerman.id.au \
    --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 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.