iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Chancellor <natechancellor@gmail.com>
To: Christoph Hellwig <hch@lst.de>,
	Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Cc: Amit Pundir <amit.pundir@linaro.org>,
	lkml <linux-kernel@vger.kernel.org>,
	jeremy.linton@arm.com, iommu@lists.linux-foundation.org,
	John Stultz <john.stultz@linaro.org>,
	linux-rpi-kernel@lists.infradead.org,
	David Rientjes <rientjes@google.com>,
	Robin Murphy <robin.murphy@arm.com>,
	Sumit Semwal <sumit.semwal@linaro.org>
Subject: Re: [PATCH] dma-pool: Do not allocate pool memory from CMA
Date: Thu, 30 Jul 2020 18:10:04 -0700	[thread overview]
Message-ID: <20200731011004.GA729998@ubuntu-n2-xlarge-x86> (raw)
In-Reply-To: <20200728100918.GA26364@lst.de>

On Tue, Jul 28, 2020 at 12:09:18PM +0200, Christoph Hellwig wrote:
> Ok, I found a slight bug that wasn't intended.  I wanted to make sure
> we can always fall back to a lower pool, but got that wrong.  Should be
> fixed in the next version.

Hi Christoph and Nicolas,

Did a version of that series ever get send out? I am coming into the
conversation late but I am running into an issue with the Raspberry Pi 4
not booting on linux-next, which appears to be due to this patch now in
mainline as commit d9765e41d8e9 ("dma-pool: do not allocate pool memory
from CMA") combined with
https://lore.kernel.org/lkml/20200725014529.1143208-2-jiaxun.yang@flygoat.com/
in -next:

[    1.423163] raspberrypi-firmware soc:firmware: Request 0x00000001 returned status 0x00000000
[    1.431883] raspberrypi-firmware soc:firmware: Request 0x00030046 returned status 0x00000000
[    1.443888] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000
[    1.452527] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 0 config (-22 80)
[    1.460836] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000
[    1.469445] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 1 config (-22 81)
[    1.477735] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000
[    1.486350] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 2 config (-22 82)
[    1.494639] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000
[    1.503246] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 3 config (-22 83)
[    1.511529] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000
[    1.520131] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 4 config (-22 84)
[    1.528414] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000
[    1.537017] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 5 config (-22 85)
[    1.545299] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000
[    1.553903] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 6 config (-22 86)
[    1.562184] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000
[    1.570787] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 7 config (-22 87)
[    1.579897] raspberrypi-firmware soc:firmware: Request 0x00030030 returned status 0x00000000
[    1.589419] raspberrypi-firmware soc:firmware: Request 0x00028001 returned status 0x00000000
[    1.599391] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000
[    1.608018] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 1 config (-22 81)
[    1.616313] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000
[    1.624932] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 1 config (-22 81)
[    1.633195] pwrseq_simple: probe of wifi-pwrseq failed with error -22
[    1.643904] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000
[    1.652544] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 2 config (-22 82)
[    1.660839] raspberrypi-firmware soc:firmware: Request 0x00030041 returned status 0x00000000
[    1.669446] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 2 state (-22 82)
[    1.677727] leds-gpio: probe of leds failed with error -22
[    1.683735] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000
[    1.692346] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 6 config (-22 86)
[    1.700636] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000
[    1.709240] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 6 config (-22 86)
[    1.717496] reg-fixed-voltage: probe of sd_vcc_reg failed with error -22
[    1.725546] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000
[    1.734176] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 4 config (-22 84)
[    1.742465] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000
[    1.751072] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 4 config (-22 84)
[    1.759332] gpio-regulator: probe of sd_io_1v8_reg failed with error -22
[    1.768042] raspberrypi-firmware soc:firmware: Request 0x00028001 returned status 0x00000000
[    1.780871] ALSA device list:
[    1.783960]   No soundcards found.
[    1.787633] Waiting for root device PARTUUID=45a8dd8a-02...

I am unsure if it is related to the issue that Amit is having or
if that makes sense at all but I can reliably reproduce it.

v5.8-rc1: OK
v5.8-rc1 + d9765e41d8e9e: OK
v5.8-rc1 + "of_address: Add bus type match for pci ranges parser": OK
v5.8-rc1 + both: BROKEN

I wanted to test the series to see if this fixes anything. If you would
prefer a different thread for this or further information, please let
me know.

Cheers,
Nathan
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2020-07-31  1:10 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08 16:49 [PATCH] dma-pool: Do not allocate pool memory from CMA Nicolas Saenz Julienne
2020-07-08 16:58 ` Christoph Hellwig
2020-07-08 23:14 ` Jeremy Linton
2020-07-09 21:47 ` David Rientjes via iommu
2020-07-21  7:21 ` Amit Pundir
2020-07-21  8:39   ` Nicolas Saenz Julienne
2020-07-21  8:54     ` Amit Pundir
2020-07-21 11:15       ` Nicolas Saenz Julienne
2020-07-21 11:28         ` Christoph Hellwig
2020-07-21 11:37           ` Nicolas Saenz Julienne
2020-07-21 12:16             ` Amit Pundir
2020-07-21 12:15         ` Amit Pundir
2020-07-21 12:45           ` Nicolas Saenz Julienne
2020-07-21 15:22             ` Amit Pundir
2020-07-21 16:27               ` Nicolas Saenz Julienne
2020-07-23  5:14                 ` Amit Pundir
2020-07-24  9:36                   ` Nicolas Saenz Julienne
2020-07-24 11:06                     ` Amit Pundir
2020-07-24 13:41                       ` Christoph Hellwig
2020-07-24 16:19                         ` Amit Pundir
2020-07-24 16:27                           ` Christoph Hellwig
2020-07-27 17:56                         ` Nicolas Saenz Julienne
2020-07-28  9:13                           ` Christoph Hellwig
2020-07-28  9:30                             ` Nicolas Saenz Julienne
2020-07-28 10:09                               ` Christoph Hellwig
2020-07-31  1:10                                 ` Nathan Chancellor [this message]
2020-07-31  7:19                                   ` Amit Pundir
2020-07-31 10:09                                   ` Nicolas Saenz Julienne

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=20200731011004.GA729998@ubuntu-n2-xlarge-x86 \
    --to=natechancellor@gmail.com \
    --cc=amit.pundir@linaro.org \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jeremy.linton@arm.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=nsaenzjulienne@suse.de \
    --cc=rientjes@google.com \
    --cc=robin.murphy@arm.com \
    --cc=sumit.semwal@linaro.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).