Having posted, I see that this is actually a utopic kernel that oopsed (3.16.0-71-generic)
However, the oops stack is still possible on trusty, the blk-merge code in 3.13 doesn't include the fix that appears in the vivid kernel.
On Tue, Jun 14, 2016 at 2:56 PM, Ryan Harper <email address hidden> wrote:
> Here's the qemu launch command used, in case that's useful. > > > qemu-system-x86_64 -enable-kvm -device > virtio-scsi-pci,id=virtio-scsi-xkvm -device virtio-net-pci,netdev=net00 > -netdev type=user,id=net00 -m 1024 -serial > file:/var/lib/jenkins/slaves/venonat/workspace/curtin-vmtest-venonat-devel/output/TrustyHWEUTestRaid5Bcache/logs/install-serial.log > -nographic -drive > file=/tmp/launch.Cnc0wx/boot.img,if=none,cache=unsafe,format=qcow2,id=boot,index=0 > -device virtio-blk,drive=boot -drive > file=/var/lib/jenkins/slaves/venonat/workspace/curtin-vmtest-venonat-devel/output/TrustyHWEUTestRaid5Bcache/disks/install_disk.img,if=none,cache=unsafe,format=raw,id=drv2,index=2 > -device > virtio-blk,drive=drv2,serial=dev2,logical_block_size=512,physical_block_size=512,min_io_size=512 > -drive > file=/var/lib/jenkins/slaves/venonat/workspace/curtin-vmtest-venonat-devel/output/TrustyHWEUTestRaid5Bcache/disks/extra_disk_0.img,if=none,cache=unsafe,format=raw,id=drv3,index=3 > -device > virtio-blk,drive=drv3,serial=dev3,logical_block_size=512,physical_block_size=512,min_io_size=512 > -drive > file=/var/lib/jenkins/slaves/venonat/workspace/curtin-vmtest-venonat-devel/output/TrustyHWEUTestRaid5Bcache/disks/extra_disk_1.img,if=none,cache=unsafe,format=raw,id=drv4,index=4 > -device > virtio-blk,drive=drv4,serial=dev4,logical_block_size=512,physical_block_size=512,min_io_size=512 > -drive > file=/var/lib/jenkins/slaves/venonat/workspace/curtin-vmtest-venonat-devel/output/TrustyHWEUTestRaid5Bcache/disks/extra_disk_2.img,if=none,cache=unsafe,format=raw,id=drv5,index=5 > -device > virtio-blk,drive=drv5,serial=dev5,logical_block_size=512,physical_block_size=512,min_io_size=512 > -drive > file=/var/lib/jenkins/slaves/venonat/workspace/curtin-vmtest-venonat-devel/output/TrustyHWEUTestRaid5Bcache/disks/extra_disk_3.img,if=none,cache=unsafe,format=raw,id=drv6,index=6 > -device > virtio-blk,drive=drv6,serial=dev6,logical_block_size=512,physical_block_size=512,min_io_size=512 > -kernel /srv/images/trusty/amd64/20160606/utopic/generic/boot-kernel > -initrd /srv/images/trusty/amd64/20160606/utopic/generic/boot-initrd > -append "root=/dev/vda ds=nocloud-net;seedfrom=http://10.100.0.103:40646/ > console=ttyS0 " > kvm pid=6128. my pid=6123 > QEMU 2.0.0 monitor - type 'help' for more information > (qemu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1592541 > > Title: > trusty kernel with virtio-blk oops > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592541/+subscriptions >
Having posted, I see that this is actually a utopic kernel that oopsed
(3.16.0-71-generic)
However, the oops stack is still possible on trusty, the blk-merge code in
3.13 doesn't include the fix
that appears in the vivid kernel.
On Tue, Jun 14, 2016 at 2:56 PM, Ryan Harper <email address hidden>
wrote:
> Here's the qemu launch command used, in case that's useful. scsi-pci, id=virtio- scsi-xkvm -device virtio- net-pci, netdev= net00 lib/jenkins/ slaves/ venonat/ workspace/ curtin- vmtest- venonat- devel/output/ TrustyHWEUTestR aid5Bcache/ logs/install- serial. log launch. Cnc0wx/ boot.img, if=none, cache=unsafe, format= qcow2,id= boot,index= 0 blk,drive= boot -drive lib/jenkins/ slaves/ venonat/ workspace/ curtin- vmtest- venonat- devel/output/ TrustyHWEUTestR aid5Bcache/ disks/install_ disk.img, if=none, cache=unsafe, format= raw,id= drv2,index= 2 blk,drive= drv2,serial= dev2,logical_ block_size= 512,physical_ block_size= 512,min_ io_size= 512 lib/jenkins/ slaves/ venonat/ workspace/ curtin- vmtest- venonat- devel/output/ TrustyHWEUTestR aid5Bcache/ disks/extra_ disk_0. img,if= none,cache= unsafe, format= raw,id= drv3,index= 3 blk,drive= drv3,serial= dev3,logical_ block_size= 512,physical_ block_size= 512,min_ io_size= 512 lib/jenkins/ slaves/ venonat/ workspace/ curtin- vmtest- venonat- devel/output/ TrustyHWEUTestR aid5Bcache/ disks/extra_ disk_1. img,if= none,cache= unsafe, format= raw,id= drv4,index= 4 blk,drive= drv4,serial= dev4,logical_ block_size= 512,physical_ block_size= 512,min_ io_size= 512 lib/jenkins/ slaves/ venonat/ workspace/ curtin- vmtest- venonat- devel/output/ TrustyHWEUTestR aid5Bcache/ disks/extra_ disk_2. img,if= none,cache= unsafe, format= raw,id= drv5,index= 5 blk,drive= drv5,serial= dev5,logical_ block_size= 512,physical_ block_size= 512,min_ io_size= 512 lib/jenkins/ slaves/ venonat/ workspace/ curtin- vmtest- venonat- devel/output/ TrustyHWEUTestR aid5Bcache/ disks/extra_ disk_3. img,if= none,cache= unsafe, format= raw,id= drv6,index= 6 blk,drive= drv6,serial= dev6,logical_ block_size= 512,physical_ block_size= 512,min_ io_size= 512 trusty/ amd64/20160606/ utopic/ generic/ boot-kernel trusty/ amd64/20160606/ utopic/ generic/ boot-initrd net;seedfrom=http:// 10.100. 0.103:40646/ /bugs.launchpad .net/bugs/ 1592541 /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1592541/ +subscriptions
>
>
> qemu-system-x86_64 -enable-kvm -device
> virtio-
> -netdev type=user,id=net00 -m 1024 -serial
> file:/var/
> -nographic -drive
> file=/tmp/
> -device virtio-
> file=/var/
> -device
> virtio-
> -drive
> file=/var/
> -device
> virtio-
> -drive
> file=/var/
> -device
> virtio-
> -drive
> file=/var/
> -device
> virtio-
> -drive
> file=/var/
> -device
> virtio-
> -kernel /srv/images/
> -initrd /srv/images/
> -append "root=/dev/vda ds=nocloud-
> console=ttyS0 "
> kvm pid=6128. my pid=6123
> QEMU 2.0.0 monitor - type 'help' for more information
> (qemu)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> trusty kernel with virtio-blk oops
>
> To manage notifications about this bug go to:
> https:/
>