On 10/11/2016 03:19 AM, Mark Brown wrote:
On Mon, Oct 10, 2016 at 12:47:43PM -0700, Guenter Roeck wrote:
On Mon, Oct 10, 2016 at 09:11:23PM +0200, Mark Brown wrote:
My connection doesn't have IPv6 and is a bit spotty right now so it's a
bit difficult for me to check by lab but today's -next jobs are working
for me as well... looking at the log for the failed stable boots:
Can you send me (or point me to) the qemu command lines you are using ?
Managed to get things running long enough to pull the log:
qemu-system-arm -M vexpress-a15 -no-reboot -show-cursor -no-reboot -nographic -m 256 -net user -kernel /var/lib/lava/dispatcher/tmp/tmpZBxic8/.zImage -append "root=/dev/ram0 rw console=ttyAMA0 115200 ip=dhcp mem=256M" -initrd /var/lib/lava/dispatcher/tmp/tmpxoFsPn/ramdisk.cpio.gz -dtb /var/lib/lava/dispatcher/tmp/tmpMN1a1R/vexpress-v2p-ca15_a7.dtb
Boots for me, though I have to specify
-append "rdinit=/sbin/init console=ttyAMA0,115200"
or, when using a root file system,
-drive file=core-image-minimal-qemuarm.ext3,format=raw,if=sd \
-append "root=/dev/mmcblk0 rootwait rw console=ttyAMA0,115200"
I do get the warning about the wrong CPU id, but looks like that is as expected.
I tried with qemu 2.5, 1.6, and 2.7, and the mainline kernel as well as v4.7.
Guenter
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html