<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>12570</bug_id>
          
          <creation_ts>2018-02-25 16:25:39 +0000</creation_ts>
          <short_desc>[stable/pyro-next] nightly-x86-64-lsb fails</short_desc>
          <delta_ts>2018-03-08 13:20:12 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>OE-Core</product>
          <component>core</component>
          <version>2.3.4</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc>https://autobuilder.yocto.io/builders/nightly-x86-64-lsb/builds/806/steps/Running%20Sanity%20Tests/logs/stdio</bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>High</priority>
          <bug_severity>critical</bug_severity>
          <target_milestone>2.3.4</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Armin Kuster">akuster</reporter>
          <assigned_to name="Armin Kuster">akuster</assigned_to>
          <cc>juro.bystricky</cc>
    
    <cc>meta.mr.watcher</cc>
    
    <cc>meta.watcher</cc>
    
    <cc>stephano</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>Don&apos;t know</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>79591</commentid>
    <comment_count>0</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2018-02-25 16:25:39 +0000</bug_when>
    <thetext>selftest failed for unknown reason on debian8.yocto.io

NOTE: core-image-lsb-sdk-1.0-r0 do_testimage: Sending SIGTERM to runqemu
ERROR: core-image-lsb-1.0-r0 do_testimage: testimage received SIGTERM, shutting down...
ERROR: core-image-lsb-1.0-r0 do_testimage: core-image-lsb - FAILED - tests were interrupted during execution
ERROR: core-image-lsb-1.0-r0 do_testimage: Function failed: do_testimage
ERROR: Logfile of failure stored in: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64-lsb/build/build/tmp/work/qemux86_64-poky-linux/core-image-lsb/1.0-r0/temp/log.do_testimage.55682
NOTE: recipe core-image-lsb-1.0-r0: task do_testimage: Failed
ERROR: Task (/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64-lsb/build/meta/recipes-extended/images/core-image-lsb.bb:do_testimage) failed with exit code &apos;1&apos;
ERROR: core-image-lsb-sdk-1.0-r0 do_testimage: testimage received SIGTERM, shutting down...
ERROR: core-image-lsb-sdk-1.0-r0 do_testimage: core-image-lsb-sdk - FAILED - tests were interrupted during execution
ERROR: core-image-lsb-sdk-1.0-r0 do_testimage: Function failed: do_testimage
ERROR: Logfile of failure stored in: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64-lsb/build/build/tmp/work/qemux86_64-poky-linux/core-image-lsb-sdk/1.0-r0/temp/log.do_testimage.55681
NOTE: recipe core-image-lsb-sdk-1.0-r0: task do_testimage: Failed
ERROR: Task (/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64-lsb/build/meta/recipes-extended/images/core-image-lsb-sdk.bb:do_testimage) failed with exit code &apos;1&apos;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79592</commentid>
    <comment_count>1</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2018-02-25 16:26:19 +0000</bug_when>
    <thetext>Can not reproduce on Ubuntu 17. I don&apos;t see any errors in console output.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79629</commentid>
    <comment_count>2</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2018-02-28 18:53:43 +0000</bug_when>
    <thetext>backported several runqemu logging patches
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=stable/pyro-next

I get more debug out but it did not fix this issue nor is it giving more info.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79630</commentid>
    <comment_count>3</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2018-02-28 18:54:13 +0000</bug_when>
    <thetext>on the build host.

[    3.096996] EXT4-fs (vda): couldn&apos;t mount as ext3 due to feature incompatibilities
[    3.098375] EXT4-fs (vda): couldn&apos;t mount as ext2 due to feature incompatibilities
[    3.101180] EXT4-fs (vda): mounted filesystem with ordered data mode. Opts: (null)
[    3.103241] VFS: Mounted root (ext4 filesystem) on device 253:0.
[    3.104504] devtmpfs: mounted
[    3.105734] Freeing unused kernel memory: 1356K
[    3.106475] Write protecting the kernel read-only data: 14336k
[    3.107815] Freeing unused kernel memory: 588K
[    3.108786] Freeing unused kernel memory: 368K
INIT: version 2.88 booting
INIT: PANIC: segmentation violation! sleeping for 30 seconds.
INIT: PANIC: segmentation violation! sleeping for 30 seconds.
INIT: PANIC: segmentation violation! sleeping for 30 seconds.
INIT: PANIC: segmentation violation! sleeping for 30 seconds.
[  100.320053] random: nonblocking pool is initialized
INIT: PANIC: segmentation violation! sleeping for 30 seconds.
INIT: PANIC: segmentation violation! sleeping for 30 seconds.
INIT: PANIC: segmentation violation! sleeping for 30 seconds.
INIT: PANIC: segmentation violation! sleeping for 30 seconds.
INIT: PANIC: segmentation violation! sleeping for 30 seconds.
INIT: PANIC: segmentation violation! sleeping for 30 seconds.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79631</commentid>
    <comment_count>4</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2018-02-28 19:07:35 +0000</bug_when>
    <thetext>Command run:
 Running tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin//qemu-system-x86_64 -device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:02 -netdev tap,id=net0,ifname=tap0,script=no,downscript=no -drive file=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64-lsb/build/build/tmp/deploy/images/qemux86-64/core-image-lsb-qemux86-64.ext4,if=virtio,format=raw -vga vmware -show-cursor -usb -usbdevice tablet -device virtio-rng-pci  -serial tcp:127.0.0.1:59521 -pidfile pidfile_29068  -cpu core2duo -enable-kvm -m 256 -serial tcp:127.0.0.1:59231 -snapshot -kernel tmp/deploy/images/qemux86-64/bzImage--4.1.49+git0+4e12cb8f8e_a315195324-r0.2-qemux86-64-20180224035021.bin -append &apos;root=/dev/vda rw highres=off  mem=256M ip=192.168.7.2::192.168.7.1:255.255.255.0 vga=0 uvesafb.mode_option=640x480-32 oprofile.timer=1 uvesafb.task_timeout=-1 console=tty1 console=ttyS0,115200n8 printk.time=1&apos;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79632</commentid>
    <comment_count>5</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2018-02-28 19:21:14 +0000</bug_when>
    <thetext>I just reproduced this at home:

I see it if QEMU_USE_KVM = &quot;True&quot;


cuting &apos;/home/akuster/oss/maint/poky/build/tmp/work/qemux86_64-poky-linux/core-image-lsb-sdk/1.0-r0/recipe-sysroot-native/usr/bin/createrepo_c --update -q /home/akuster/oss/maint/poky/build/tmp/work/qemux86_64-poky-linux/core-image-lsb-sdk/1.0-r0/oe-testimage-repo/noarch&apos; ...
NOTE: core-image-lsb-1.0-r0 do_testimage: Executing &apos;/home/akuster/oss/maint/poky/build/tmp/work/qemux86_64-poky-linux/core-image-lsb/1.0-r0/recipe-sysroot-native/usr/bin/createrepo_c --update -q /home/akuster/oss/maint/poky/build/tmp/work/qemux86_64-poky-linux/core-image-lsb/1.0-r0/oe-testimage-repo/noarch&apos; ...
NOTE: core-image-lsb-sdk-1.0-r0 do_testimage: Executing &apos;/home/akuster/oss/maint/poky/build/tmp/work/qemux86_64-poky-linux/core-image-lsb-sdk/1.0-r0/recipe-sysroot-native/usr/bin/createrepo_c --update -q /home/akuster/oss/maint/poky/build/tmp/work/qemux86_64-poky-linux/core-image-lsb-sdk/1.0-r0/oe-testimage-repo/core2_64&apos; ...
NOTE: core-image-lsb-1.0-r0 do_testimage: Executing &apos;/home/akuster/oss/maint/poky/build/tmp/work/qemux86_64-poky-linux/core-image-lsb/1.0-r0/recipe-sysroot-native/usr/bin/createrepo_c --update -q /home/akuster/oss/maint/poky/build/tmp/work/qemux86_64-poky-linux/core-image-lsb/1.0-r0/oe-testimage-repo/core2_64&apos; ...
NOTE: core-image-lsb-sdk-1.0-r0 do_testimage: Executing &apos;/home/akuster/oss/maint/poky/build/tmp/work/qemux86_64-poky-linux/core-image-lsb-sdk/1.0-r0/recipe-sysroot-native/usr/bin/createrepo_c --update -q /home/akuster/oss/maint/poky/build/tmp/work/qemux86_64-poky-linux/core-image-lsb-sdk/1.0-r0/oe-testimage-repo/qemux86_64&apos; ...
NOTE: core-image-lsb-1.0-r0 do_testimage: Executing &apos;/home/akuster/oss/maint/poky/build/tmp/work/qemux86_64-poky-linux/core-image-lsb/1.0-r0/recipe-sysroot-native/usr/bin/createrepo_c --update -q /home/akuster/oss/maint/poky/build/tmp/work/qemux86_64-poky-linux/core-image-lsb/1.0-r0/oe-testimage-repo/qemux86_64&apos; ...
WARNING: core-image-lsb-sdk-1.0-r0 do_testimage: Qemu ended unexpectedly, dump data from host is in /tmp/oe-saved-tests/201802281114_qemu
WARNING: core-image-lsb-1.0-r0 do_testimage: Qemu ended unexpectedly, dump data from host is in /tmp/oe-saved-tests/201802281114_qemu
ERROR: core-image-lsb-sdk-1.0-r0 do_testimage: testimage received SIGTERM, shutting down...
ERROR: core-image-lsb-sdk-1.0-r0 do_testimage: core-image-lsb-sdk - FAILED - tests were interrupted during execution
ERROR: core-image-lsb-sdk-1.0-r0 do_testimage: Function failed: do_testimage
ERROR: Logfile of failure stored in: /home/akuster/oss/maint/poky/build/tmp/work/qemux86_64-poky-linux/core-image-lsb-sdk/1.0-r0/temp/log.do_testimage.17645
ERROR: Task (/home/akuster/oss/maint/poky/meta/recipes-extended/images/core-image-lsb-sdk.bb:do_testimage) failed with exit code &apos;1&apos;
ERROR: core-image-lsb-1.0-r0 do_testimage: testimage received SIGTERM, shutting down...
ERROR: core-image-lsb-1.0-r0 do_testimage: core-image-lsb - FAILED - tests were interrupted during execution
ERROR: core-image-lsb-1.0-r0 do_testimage: Function failed: do_testimage
ERROR: Logfile of failure stored in: /home/akuster/oss/maint/poky/build/tmp/work/qemux86_64-poky-linux/core-image-lsb/1.0-r0/temp/log.do_testimage.17646
ERROR: Task (/home/akuster/oss/maint/poky/meta/recipes-extended/images/core-image-lsb.bb:do_testimage) failed with exit code &apos;1&apos;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79633</commentid>
    <comment_count>6</comment_count>
    <who name="Juro Bystricky">juro.bystricky</who>
    <bug_when>2018-02-28 19:58:34 +0000</bug_when>
    <thetext>I am pretty sure I tried (and failed) to reproduce this with 
QEMU_ENABLE_KVM=&quot;True&quot; (Ubuntu 16.04)
I will re-try, just to make sure.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79634</commentid>
    <comment_count>7</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2018-02-28 22:36:56 +0000</bug_when>
    <thetext>This fails on my system with this simple case:
runqemu qemux86-64 kvm

without kvm, it boots fine.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79636</commentid>
    <comment_count>8</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2018-03-01 01:07:54 +0000</bug_when>
    <thetext>This appears to be released to the kernel. removing the 4.1.49 updated, things work. I now have a range of commits to look at.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79637</commentid>
    <comment_count>9</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2018-03-01 01:10:59 +0000</bug_when>
    <thetext>looks like it in the meltdown changes. commit to 4.1.49 sync works.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79675</commentid>
    <comment_count>10</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2018-03-02 16:22:25 +0000</bug_when>
    <thetext>found a fix for the 4.1. 

runny some build test sequences before I send a pull request for 4.1</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79686</commentid>
    <comment_count>11</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2018-03-05 03:17:04 +0000</bug_when>
    <thetext>kernel pull request sent.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79754</commentid>
    <comment_count>12</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2018-03-08 08:15:27 +0000</bug_when>
    <thetext>patches sent.

New build under way</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>79763</commentid>
    <comment_count>13</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2018-03-08 13:20:12 +0000</bug_when>
    <thetext>fixed. 

changes merged to pyro

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=pyro&amp;id=44d206b7a7c61250da825d25dcca1fb6a3c2e8a1</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>