Today's next (next-20131204) has a new boot failure[1] on
ux500/snowball which bisected down to this commit.  Full boot log
attached.

Right.

Anyone not on CC (which I think you are Kevin) can follow the fun here:
  http://www.spinics.net/lists/arm-kernel/msg291374.html

It doesn't find the alsa device which in turn seems to prevent the
emmc rootfs from being mounted.  It boots fine to an initramfs.

<snip>

of_dma_request_slave_channel: dma-names property of node '/soc/msp at 80124000' missing or empty
of_dma_request_slave_channel: dma-names property of node '/soc/msp at 80124000' missing or empty
of_dma_request_slave_channel: dma-names property of node '/soc/msp at 80125000' missing or empty
mmc1: new high speed MMC card at address 0001
of_dma_request_slave_channel: dma-names property of node '/soc/msp at 80125000' missing or empty
mmcblk0: mmc1:0001  7.28 GiB 
mmcblk0boot0: mmc1:0001  partition 1 2.00 MiB
mmcblk0boot1: mmc1:0001  partition 2 2.00 MiB
mmcblk0rpmb: mmc1:0001  partition 3 128 KiB
dma dma0chan22: [d40_config_memcpy] No memcpy
dma dma0chan22: [d40_alloc_chan_resources] Failed to configure memcpy channel
ux500-msp-i2s ux500-msp-i2s.1: Missing dma channel for stream: 0
ux500-msp-i2s ux500-msp-i2s.1: ASoC: pcm constructor failed: -22
snd-soc-mop500 snd-soc-mop500.0: ASoC: can't create pcm ab8500_0 :-22
snd-soc-mop500 snd-soc-mop500.0: ASoC: failed to instantiate card -22
snd-soc-mop500 snd-soc-mop500.0: Error: snd_soc_register_card failed (-22)!
snd-soc-mop500: probe of snd-soc-mop500.0 failed with error -22

<snip>

mmci-pl18x sdi4: error during DMA transfer!
mmcblk0rpmb: error -110 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
mmcblk0rpmb: retrying using single block read

It's interesting that the MSP failure has managed to fudge the entire
DMA Controller. I have absolutely no idea how that can even happen?


-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog