Hi Olof,
For some reason, the mail was addressed to your build bot, which probably explains why you didn't answer.
On Thu, Sep 25, 2014 at 02:37:46PM +0200, Maxime Ripard wrote:
Hi Olof,
On Thu, Sep 25, 2014 at 02:42:05AM -0700, Olof's autobooter wrote:
Full logs are available at http://arm-soc.lixom.net/bootlogs/next/next-20140925/
Failed boards:
colombus arm-sunxi_defconfig : FAILED 1:48.51 colombus arm-multi_v7_defconfig : FAILED 1:55.21 colombus arm-multi_lpae_defconfig : FAILED 1:54.70========================================================================
Board colombus-arm-multi_lpae_defconfig failure log:
[ 1.465039] sunxi-mmc 1c0f000.mmc: No vqmmc regulator found [ 1.471285] sunxi-mmc 1c0f000.mmc: Got CD GPIO [ 1.506868] sunxi-mmc 1c0f000.mmc: base:0xf009a000 irq:92 [ 1.512588] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.519425] usbcore: registered new interface driver usbhid [ 1.525211] usbhid: USB HID core driver [ 1.533367] TCP: cubic registered [ 1.536820] NET: Registered protocol family 17 [ 1.541470] can: controller area network core (rev 20120528 abi 9) [ 1.547957] NET: Registered protocol family 29 [ 1.552581] can: raw protocol (rev 20120528) [ 1.557020] can: broadcast manager protocol (rev 20120528 t) [ 1.562903] can: netlink gateway (rev 20130117) max_hops=1 [ 1.569038] Key type dns_resolver registered [ 1.573638] ThumbEE CPU extension supported. [ 1.578095] Registering SWP/SWPB emulation handler [ 1.584288] usb2-vbus: 5000 mV [ 1.589119] sun6i-a31-r-pinctrl 1f02c00.pinctrl: initialized sunXi PIO driver [ 1.597208] ehci-platform 1c1b000.usb: EHCI Host Controller [ 1.603026] ehci-platform 1c1b000.usb: new USB bus registered, assigned bus number 1 [ 1.611308] ehci-platform 1c1b000.usb: irq 106, io mem 0x01c1b000 [ 1.625943] ehci-platform 1c1b000.usb: USB 2.0 started, EHCI 1.00 [ 1.633117] hub 1-0:1.0: USB hub found [ 1.637046] hub 1-0:1.0: 1 port detected [ 1.641844] sun6i-rtc 1f00000.rtc: setting system clock to 1970-01-01 00:00:23 UTC (23) [ 1.653419] vcc5v0: disabling [ 1.656504] vcc3v3: disabling [ 1.659608] vcc3v0: disabling [ 1.662800] ALSA device list: [ 1.665873] No soundcards found. [ 1.670296] Waiting for root device /dev/mmcblk0p1... [ 1.957847] usb 1-1: new high-speed USB device number 2 using ehci-platform [ 42.283347] random: nonblocking pool is initialized
I just looked at this, and I'm kind of confused.
The only thing that seems to differ is that the vcc3v0 regulator seems to not be taken by the MMC core, since it's later disabled.
However, the MMC subsystem doesn't complain that vmmc (vcc3v0) is missing, and does call regulator_get on it, and doesn't log any error regarding it.
The a31 and colombus device trees haven't changed between 3.17 and linux-next, neither was our mmc driver.
I couldn't find any change that might be related to that in the regulator or mmc cores... and I'm away from this board.
Could you try to bisect it?
Plus, your arm-soc tests on this board are actually passing, so it must be something that came from another subsystem.
Thanks! Maxime