On 01/08/18 13:40, Johannes Thumshirn wrote:
On Wed, Aug 01, 2018 at 01:37:17PM +0100, Guillaume Tucker wrote:
The kernel images I used have the git revision in their file name
to make it clear where they came from, they were built with
x86_64_defconfig. The links to the kernel and ramdisks can be
found in the job definition:
https://lava.collabora.co.uk/scheduler/job/1215154/definition
Please let me know if you need any more details. I'm happy to
run other boot tests on that same setup if that helps verifying
things (such as enabling some VIRTIO configs...).
Yes, can you please enable CONFIG_BLK_DEV_RAM? See my other mails in
this thread for details.
Sure, although it didn't make any apparent difference, still on
next-20180731:
https://lava.collabora.co.uk/scheduler/job/1215417
The .config file I used is available here, with just
CONFIG_BLK_DEV_RAM=y on top of defconfig:
https://people.collabora.com/~gtucker/lava/boot/debug/bzImage-85eac382fa06-blk-dev.config
Best wishes,
Guillaume
--
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
