<?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>11802</bug_id>
          
          <creation_ts>2017-07-17 20:41:34 +0000</creation_ts>
          <short_desc>system spontaneously logs out while building core-image</short_desc>
          <delta_ts>2022-02-17 16:11:48 +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>BitBake</product>
          <component>bitbake</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>WORKSFORME</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium+</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>4.99</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Armin Kuster">akuster</reporter>
          <assigned_to name="Mingli Yu">mingli.yu</assigned_to>
          <cc>bluelightning</cc>
    
    <cc>juro.bystricky</cc>
    
    <cc>liezhi.yang</cc>
    
    <cc>mingli.yu</cc>
    
    <cc>poky.bs.watcher</cc>
    
    <cc>poky.watcher</cc>
    
    <cc>randy.macleod</cc>
    
    <cc>ranshalit</cc>
    
    <cc>rebecca.swee.fun.chang</cc>
    
    <cc>ross.burton</cc>
    
    <cc>sgw</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>75084</commentid>
    <comment_count>0</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2017-07-17 20:41:34 +0000</bug_when>
    <thetext>This is more of a place to capture information to see if we can determine a cause of this issue.

I see this issue more on laptops while building. I has happened as far back as krogoth. What happens is during a build, the desktop will log me off. No messages to be found anywhere. I has happened on two different laptops on two different Ubuntu distros.

This was discussed on the ML a few months back with no solution as far as I can tell.

Not sure how prevalent this is. I don;t know if it worth collecting info to try to understand this issue?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>75160</commentid>
    <comment_count>1</comment_count>
    <who name="Juro Bystricky">juro.bystricky</who>
    <bug_when>2017-07-19 20:28:40 +0000</bug_when>
    <thetext>What happens to me on a regular basis (on a fairly powerful desktop) is that my X server crashes, then forces me to login again. In my /var/log/syslog I see something like: 

XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server &quot;:0&quot;

followed by bunch of apps crashing due to X11 running of resources.
I can make this happen quite easily just by running two parallel core-images, typically from scratch (no SSTATE). Very annoying.
I experienced this with Ubuntu 15 &amp; 16, two different desktops (8 threads and 40 threads).</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>75174</commentid>
    <comment_count>2</comment_count>
    <who name="Saul Wold">sgw</who>
    <bug_when>2017-07-20 00:04:17 +0000</bug_when>
    <thetext>We first need to create a reproducible case, possibly by forcing, or using somekind of container spawning system to reproduce this.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>75178</commentid>
    <comment_count>3</comment_count>
      <attachid>3885</attachid>
    <who name="Rebecca Chang">rebecca.swee.fun.chang</who>
    <bug_when>2017-07-20 10:33:53 +0000</bug_when>
    <thetext>Created attachment 3885
syslog</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>75179</commentid>
    <comment_count>4</comment_count>
    <who name="Rebecca Chang">rebecca.swee.fun.chang</who>
    <bug_when>2017-07-20 10:45:55 +0000</bug_when>
    <thetext>This happen on my workstation randomly from time to time. But I was able to reproduce it 3 times in a row while building SDK.

$ bitbake core-image-minimal -c populate_sdk

Not sure what is the root cause yet, But I do get the same errors on X server failed. I also wanted to share that, my workstation was a shared machine for a few developers. The issue should be reproduce on an environment that do not has any other interference. However Stanley did tried the same command on his personal laptop but unable to reproduce with single build running.

My workstation: Ubuntu 16, 40 threads 32GB RAM</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>75268</commentid>
    <comment_count>5</comment_count>
    <who name="Paul Eggleton">bluelightning</who>
    <bug_when>2017-07-25 07:21:31 +0000</bug_when>
    <thetext>Is this the OOM killer at work in some of these cases? Anything indicative in the system logs?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>75269</commentid>
    <comment_count>6</comment_count>
    <who name="Rebecca Chang">rebecca.swee.fun.chang</who>
    <bug_when>2017-07-25 08:05:28 +0000</bug_when>
    <thetext>system log mentioned about X server failure causing chain effect to kill and restart the gnome session.
I have recently changed my window manager to budgie desktop and the symptom no longer be reproducible. I still not sure what is the actual root cause.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>75310</commentid>
    <comment_count>7</comment_count>
    <who name="Juro Bystricky">juro.bystricky</who>
    <bug_when>2017-07-26 02:45:13 +0000</bug_when>
    <thetext>I have always (perhaps unfairly) suspected pseudo leaking resources. But I could not find a smoking gun. Now I use text console (CTRL-ALT-F1), no problems there. Also no problems in Ubuntu container, but that also runs without GUI/X11. OOM is not likely, as I have tons of unused memory.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>75516</commentid>
    <comment_count>8</comment_count>
    <who name="Juro Bystricky">juro.bystricky</who>
    <bug_when>2017-07-31 22:16:56 +0000</bug_when>
    <thetext>I should mention that replacing video cards (Nvidia/Radeon,...) and display drivers (private, open source) did not make any difference. (This being often cited as remedy when Googling).</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>75755</commentid>
    <comment_count>9</comment_count>
    <who name="Juro Bystricky">juro.bystricky</who>
    <bug_when>2017-08-08 23:34:50 +0000</bug_when>
    <thetext>So today this happened again. One thing worth mentioning is that I killed a runnning &quot;bitbake core-image-minimal&quot;  with CTRL-C running in &quot;konsole&quot;. 
Moments later I tried to re-run bitbake core-image-minimal and X server crashed practically right away.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>80643</commentid>
    <comment_count>10</comment_count>
    <who name="Mingli Yu">mingli.yu</who>
    <bug_when>2018-05-25 07:20:34 +0000</bug_when>
    <thetext>I didn&apos;t encounter this, could you help to provide the detailed reproduce steps please?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>80647</commentid>
    <comment_count>11</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2018-05-25 13:45:41 +0000</bug_when>
    <thetext>@mingli, see the previous descriptions. The challenge with this bug is that no one is sure exactly how to reproduce it. 

For anyone who reported a failure, can you describe the system (cores, ram, storage system, free -m, ulimit -a, X session or server)? I suspect but don&apos;t really have any proof that resource limits (file descriptors) are the root cause and as people suggested, the X server fails after the resources are exhausted.

I couldn&apos;t find the discussion thread that Armin mentioned so if someone could post a link to that, it might help.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>80648</commentid>
    <comment_count>12</comment_count>
    <who name="Juro Bystricky">juro.bystricky</who>
    <bug_when>2018-05-25 14:03:38 +0000</bug_when>
    <thetext>It is very easy to reproduce on my 44 or 88 core Ubuntu 16.04 systems.
All I need to do is to attempt a clean build of core-image-sato. This will eventually result in the problem as described. The problem is so common, I only build images in terminal sessions (Ctrl-Alt-Fn).</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>81662</commentid>
    <comment_count>13</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2018-09-28 00:49:42 +0000</bug_when>
    <thetext>when I saw this was via my 2 core laptop. I have not seen is a while. maybe since I stopped build morty for OE/Yocto</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>81685</commentid>
    <comment_count>14</comment_count>
    <who name="Ross Burton">ross.burton</who>
    <bug_when>2018-10-01 19:54:44 +0000</bug_when>
    <thetext>To anyone who can still replicate this: my gut feeling is the same as Randy: some resource is being limited and the X server either dies, or loses the OOM roulette and gets killed.  Watching the syslog and various resource limits during a build would be the way to debug this.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>82541</commentid>
    <comment_count>15</comment_count>
    <who name="ran">ranshalit</who>
    <bug_when>2018-12-19 22:11:15 +0000</bug_when>
    <thetext>I have the same issue:

laptop: lenovo t460p
using virtual box with ubuntu 16.04.05 LTS,  4 cores in guest, 4 in host

using sumo yocto from variscite:
repo init -u https://github.com/varigit/variscite-bsp-platform.git -b refs/tags/sumo-fslc-4.9.88-mx6-v1.2
cd var-fslc-yocto
MACHINE=var-som-mx6 DISTRO=fslc-framebuffer . setup-environment build_fb
bitbake fsl-image-qt5

At first after ~3hours it suddenly happened, and then trying to login and continue, it immediately stopped again and again.
The computer also is very heated.

The next trial, I noticed that I used the virtual box with very low memory (200M) to I increased it to ~10G.
Yet on checking with &quot;free&quot; I still see that the free memory gets quite low sometimes ( to ~100M).

I also worked in a cooler environment (might be related too?)...
Yet, it did happen after ~4 hours, and then on login and bitbake again it continued till it finished.

Thanks,</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>82542</commentid>
    <comment_count>16</comment_count>
    <who name="ran">ranshalit</who>
    <bug_when>2018-12-19 22:13:47 +0000</bug_when>
    <thetext>The &quot;next trial&quot; which I mentioned before, was done after removing the previous build and doing everything from start,

Thanks.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>82543</commentid>
    <comment_count>17</comment_count>
    <who name="ran">ranshalit</who>
    <bug_when>2018-12-19 22:20:18 +0000</bug_when>
    <thetext>One last comment:
If someone tries to reproduce it, I suggest to try to use virtualbox with low memory and see if it happens.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>82544</commentid>
    <comment_count>18</comment_count>
    <who name="ran">ranshalit</who>
    <bug_when>2018-12-20 09:36:18 +0000</bug_when>
    <thetext>It seems like a temperature issue, not ram issue. Thank you.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>86439</commentid>
    <comment_count>19</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2020-02-13 20:38:37 +0000</bug_when>
    <thetext>May be the same issue as reported here:
https://stackoverflow.com/questions/60211165/yocto-project-ubuntu-16-04-lts-keeps-crashing-when-running-bitbake-fsl-image-g</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>92579</commentid>
    <comment_count>20</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2022-02-17 16:11:48 +0000</bug_when>
    <thetext>This hasn&apos;t been seen in ages. If it&apos;s still a problem, please re-open.</thetext>
  </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="0"
              isprivate="0"
          >
            <attachid>3885</attachid>
            <date>2017-07-20 10:33:53 +0000</date>
            <delta_ts>2017-07-20 10:33:53 +0000</delta_ts>
            <desc>syslog</desc>
            <filename>new 1.txt</filename>
            <type>text/plain</type>
            <size>2270</size>
            <attacher name="Rebecca Chang">rebecca.swee.fun.chang</attacher>
            
              <data encoding="base64">SnVsIDIwIDEwOjU0OjA3IHJlYmVjY2FzIG9yZy5hMTF5LmF0c3BpLlJlZ2lzdHJ5Wzg0NjI5XTog
WElPOiAgZmF0YWwgSU8gZXJyb3IgMTEgKFJlc291cmNlIHRlbXBvcmFyaWx5IHVuYXZhaWxhYmxl
KSBvbiBYIHNlcnZlciAiOjAiDQpKdWwgMjAgMTA6NTQ6MDcgcmViZWNjYXMgb3JnLmExMXkuYXRz
cGkuUmVnaXN0cnlbODQ2MjldOiAgICAgICBhZnRlciA1NzE1IHJlcXVlc3RzICg1NzE1IGtub3du
IHByb2Nlc3NlZCkgd2l0aCAwIGV2ZW50cyByZW1haW5pbmcuDQpKdWwgMjAgMTA6NTQ6MDcgcmVi
ZWNjYXMgZ25vbWUtc2Vzc2lvbls4NDYyMF06ICh1bml0eS1mYWxsYmFjay1tb3VudC1oZWxwZXI6
ODQ3ODEpOiBHZGstV0FSTklORyAqKjogdW5pdHktZmFsbGJhY2stbW91bnQtaGVscGVyOiBGYXRh
bCBJTyBlcnJvciAxMSAoUmVzb3VyY2UgdGVtcG9yYXJpbHkgdW5hdmFpbGFibGUpIG9uIFggc2Vy
dmVyIDowLg0KSnVsIDIwIDEwOjU0OjA3IHJlYmVjY2FzIGdub21lLXNlc3Npb25bODQ2MjBdOiAo
cG9sa2l0LWdub21lLWF1dGhlbnRpY2F0aW9uLWFnZW50LTE6ODQ3ODIpOiBHZGstV0FSTklORyAq
KjogcG9sa2l0LWdub21lLWF1dGhlbnRpY2F0aW9uLWFnZW50LTE6IEZhdGFsIElPIGVycm9yIDEx
IChSZXNvdXJjZSB0ZW1wb3JhcmlseSB1bmF2YWlsYWJsZSkgb24gWCBzZXJ2ZXIgOjAuDQpKdWwg
MjAgMTA6NTQ6MDcgcmViZWNjYXMgZ25vbWUtc2Vzc2lvbls4NDYyMF06IChubS1hcHBsZXQ6ODQ3
ODQpOiBHZGstV0FSTklORyAqKjogbm0tYXBwbGV0OiBGYXRhbCBJTyBlcnJvciAxMSAoUmVzb3Vy
Y2UgdGVtcG9yYXJpbHkgdW5hdmFpbGFibGUpIG9uIFggc2VydmVyIDowLg0KSnVsIDIwIDEwOjU0
OjA3IHJlYmVjY2FzIGdub21lLXNlc3Npb25bODQ2MjBdOiAobmF1dGlsdXM6ODQ3ODcpOiBHZGst
V0FSTklORyAqKjogbmF1dGlsdXM6IEZhdGFsIElPIGVycm9yIDExIChSZXNvdXJjZSB0ZW1wb3Jh
cmlseSB1bmF2YWlsYWJsZSkgb24gWCBzZXJ2ZXIgOjAuDQpKdWwgMjAgMTA6NTQ6MDcgcmViZWNj
YXMgZ25vbWUtc2Vzc2lvbls4NDYyMF06ICh2aW5vLXNlcnZlcjo4NDc4MCk6IEdkay1XQVJOSU5H
ICoqOiB2aW5vLXNlcnZlcjogRmF0YWwgSU8gZXJyb3IgMTEgKFJlc291cmNlIHRlbXBvcmFyaWx5
IHVuYXZhaWxhYmxlKSBvbiBYIHNlcnZlciA6MC4NCkp1bCAyMCAxMDo1NDowNyByZWJlY2NhcyBn
bm9tZS1zZXNzaW9uWzg0NjIwXTogKGdub21lLXNvZnR3YXJlOjg0Nzg4KTogR2RrLVdBUk5JTkcg
Kio6IGdub21lLXNvZnR3YXJlOiBGYXRhbCBJTyBlcnJvciAxMSAoUmVzb3VyY2UgdGVtcG9yYXJp
bHkgdW5hdmFpbGFibGUpIG9uIFggc2VydmVyIDowLg0KSnVsIDIwIDEwOjU0OjA3IHJlYmVjY2Fz
IGdub21lLXNlc3Npb25bODQ2MjBdOiAodXBkYXRlLW5vdGlmaWVyOjg1Mjk1KTogR2RrLVdBUk5J
TkcgKio6IHVwZGF0ZS1ub3RpZmllcjogRmF0YWwgSU8gZXJyb3IgMTEgKFJlc291cmNlIHRlbXBv
cmFyaWx5IHVuYXZhaWxhYmxlKSBvbiBYIHNlcnZlciA6MC4NCkp1bCAyMCAxMDo1NDowNyByZWJl
Y2NhcyBvcmcuZnJlZWRlc2t0b3AuTm90aWZpY2F0aW9uc1s4NDUwNF06IChub3RpZnktb3NkOjg2
NDc0KTogR2RrLVdBUk5JTkcgKio6IG5vdGlmeS1vc2Q6IEZhdGFsIElPIGVycm9yIDExIChSZXNv
dXJjZSB0ZW1wb3JhcmlseSB1bmF2YWlsYWJsZSkgb24gWCBzZXJ2ZXIgOjAuDQpKdWwgMjAgMTA6
NTQ6MDcgcmViZWNjYXMgb3JnLmdub21lLlRlcm1pbmFsWzg0NTA0XTogKGdub21lLXRlcm1pbmFs
LXNlcnZlcjoxMDQ2MzQpOiBHZGstV0FSTklORyAqKjogZ25vbWUtdGVybWluYWwtc2VydmVyOiBG
YXRhbCBJTyBlcnJvciAxMSAoUmVzb3VyY2UgdGVtcG9yYXJpbHkgdW5hdmFpbGFibGUpIG9uIFgg
c2VydmVyIDowLg0KSnVsIDIwIDEwOjU0OjA3IHJlYmVjY2FzIGdub21lLXNlc3Npb25bODQ2MjBd
OiBGYWlsZWQgdG8gY29ubmVjdCB0byBNaXI6IEZhaWxlZCB0byBjb25uZWN0IHRvIHNlcnZlciBz
b2NrZXQ6IE5vIHN1Y2ggZmlsZSBvciBkaXJlY3RvcnkNCkp1bCAyMCAxMDo1NDowNyByZWJlY2Nh
cyBnbm9tZS1zZXNzaW9uWzg0NjIwXTogVW5hYmxlIHRvIGluaXQgc2VydmVyOiBDb3VsZCBub3Qg
Y29ubmVjdDogQ29ubmVjdGlvbiByZWZ1c2VkDQpKdWwgMjAgMTA6NTQ6MDcgcmViZWNjYXMgZ25v
bWUtc2Vzc2lvbls4NDYyMF06IChwb2xraXQtZ25vbWUtYXV0aGVudGljYXRpb24tYWdlbnQtMTox
NTYwMDQpOiBHdGstV0FSTklORyAqKjogY2Fubm90IG9wZW4gZGlzcGxheTogOjA=
</data>

          </attachment>
      

    </bug>

</bugzilla>