| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 30 Jul 2020 18:10:04 -0700
From: Nathan Chancellor <natechancellor@...il.com>
To: Christoph Hellwig <hch@....de>,
Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
Cc: Amit Pundir <amit.pundir@...aro.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Robin Murphy <robin.murphy@....com>,
David Rientjes <rientjes@...gle.com>,
linux-rpi-kernel@...ts.infradead.org, jeremy.linton@....com,
iommu@...ts.linux-foundation.org,
lkml <linux-kernel@...r.kernel.org>,
John Stultz <john.stultz@...aro.org>,
Sumit Semwal <sumit.semwal@...aro.org>
Subject: Re: [PATCH] dma-pool: Do not allocate pool memory from CMA
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
Powered by blists - more mailing lists