On 31/07/18 16:52, Mark Brown wrote:
On Wed, Jul 25, 2018 at 05:11:51PM +0100, Mark Brown wrote:
On Tue, Jul 24, 2018 at 09:46:38AM -0700, kernelci.org bot wrote:
For a little while now the RPi B has been failing to boot using the
bcm2835 defconfig in -next:
...
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:
https://kernelci.org/boot/id/5b58416759b514139596baae/
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.
https://kernelci.org/boot/id/5b604cd259b514364696baaa/
| 09:18:36.332120 [ 1.459801] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
| 09:18:36.345711 [ 1.467585] mmcblk0: mmc0:59b4 USD 7.51 GiB
| 09:18:36.346169 [ 1.474834] mmcblk0: p1
| 09:18:36.410184 [ 1.539600] random: fast init done
| 09:18:36.458065 [ 1.578056] mmc1: new high speed SDIO card at address 0001
| 09:20:39.745370 ShellCommand command timed out.: Sending # in case of corruption. Connection timeout 00:04:10, retry in 00:02:05
| 09:20:39.846848 #
but like I say the same -next boots with arm64 defconfig.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
