On 01/08/18 12:25, Johannes Thumshirn wrote:
On Wed, Aug 01, 2018 at 11:59:19AM +0100, Mark Brown 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.
Can you give us a bit more information about you test setups? Like
Qemu command line, etc..? From you kernel config I see you're not
using virtio (as Ming already suggested). What medium are you booting
off?
Sure, sorry I should have put that in my first email.
Here's a couple of LAVA boot tests, one passing with the commit
reverted and one failing with plain next-20180731:
https://lava.collabora.co.uk/scheduler/job/1215154
https://lava.collabora.co.uk/scheduler/job/1215173
The qemu command line can be found in the log, copying it here:
/usr/bin/qemu-system-x86_64 -cpu host -enable-kvm -nographic -net nic,model=virtio,macaddr=DE:AD:BE:EF:AE:1B -net user -m 1024 -monitor none -kernel /var/lib/lava/dispatcher/tmp/1215173/deployimages-3p80s2zk/kernel/bzImage-85eac382fa06 -append "console=ttyS0,115200 root=/dev/ram0 debug verbose" -initrd /var/lib/lava/dispatcher/tmp/1215173/deployimages-3p80s2zk/ramdisk/rootfs.cpio.gz
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...).
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
