On 1 August 2018 at 11:59, Mark Brown <broonie@xxxxxxxxxx> wrote: > On Wed, Aug 01, 2018 at 06:51:09PM +0800, Ming Lei wrote: > >> You may have to provide some clue, such as dmesg log, boot disk, ... > >> I guess you don't use virtio-scsi/virtio-blk since both run at blk-mq >> mode at default, even though without d5038a13eca72fb. > > Boot logs and so on can be found here: > > https://kernelci.org/boot/id/5b618c9f59b514931f96ba97/ > https://kernelci.org/boot/id/5b618ca359b514904d96bac5/ > https://kernelci.org/boot/id/5b618cbc59b51492e896baad/ > > (these are today's but the symptoms are the same.) The ramdisk is > unfortunately not linked through the UI, though we don't get that far. And a full LAVA boot log from my lab http://lava.streamtester.net/scheduler/job/138067 QEMU command line here: http://lava.streamtester.net/scheduler/job/138067#L75 And a LAVA job definition, which includes the url of the ramdisk and kernel: http://lava.streamtester.net/scheduler/job/138067/definition#defline76 > > _______________________________________________ > Kernel-build-reports mailing list > Kernel-build-reports@xxxxxxxxxxxxxxxx > https://lists.linaro.org/mailman/listinfo/kernel-build-reports > -- 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
