Thread (5 messages) 5 messages, 3 authors, 2018-07-31

next/master boot: 171 boots: 6 failed, 162 passed with 3 offline (next-20180724)

From: Stefan Wahren <hidden>
Date: 2018-07-31 21:35:09
Also in: linux-next

Robin Murphy [off-list ref] hat am 31. Juli 2018 um 19:00 geschrieben:


On 31/07/18 16:52, Mark Brown wrote:
quoted
On Wed, Jul 25, 2018 at 05:11:51PM +0100, Mark Brown wrote:
quoted
On Tue, Jul 24, 2018 at 09:46:38AM -0700, kernelci.org bot wrote:
quoted
For a little while now the RPi B has been failing to boot using the
bcm2835 defconfig in -next:
...
quoted
It's working fine on arm64, whatever's going on appears to be specific
to this config (it's not getting booted with any other 32 bit configs).
Full info and boot logs for one of the boards here:
quoted
    https://kernelci.org/boot/id/5b58416759b514139596baae/
quoted
it looks like it hangs somewhere shortly after or during initializing
MMC so never makes it to the console, the tail of the failing logs looks
like:
This went away for a day or two but it looks like it's back again I'm
afraid:
FWIW, it looks like that blip was due to me completely breaking DMA API 
functionality for DT devices in next-20180727. Funny that that actually 
"helped" in this case (unlike all the others...), but it definitely 
reinforces Stefan's observation.

Robin.
Sorry, still not much time this week. All i can say that next-20180731 is broken, but dma-mapping/for-next is not.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help