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?
Thanks,
Johannes
--
Johannes Thumshirn Storage
[email protected] +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
