summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/faq.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/ref-manual/faq.xml')
-rw-r--r--documentation/ref-manual/faq.xml21
1 files changed, 14 insertions, 7 deletions
diff --git a/documentation/ref-manual/faq.xml b/documentation/ref-manual/faq.xml
index 8553a40081..8884dba663 100644
--- a/documentation/ref-manual/faq.xml
+++ b/documentation/ref-manual/faq.xml
@@ -351,13 +351,20 @@
351 </question> 351 </question>
352 <answer> 352 <answer>
353 <para> 353 <para>
354 If the same build is failing in totally different and random ways, 354 If the same build is failing in totally different and random
355 the most likely explanation is that either the hardware you're running the 355 ways, the most likely explanation is:
356 build on has some problem, or, if you are running the build under virtualisation, 356 <itemizedlist>
357 the virtualisation probably has bugs. 357 <listitem><para>The hardware you are running the build on
358 The OpenEmbedded build system processes a massive amount of data causing lots of network, disk and 358 has some problem.</para></listitem>
359 CPU activity and is sensitive to even single bit failures in any of these areas. 359 <listitem><para>You are running the build under
360 True random failures have always been traced back to hardware or virtualisation issues. 360 virtualization, in which case the virtualization
361 probably has bugs.</para></listitem>
362 </itemizedlist>
363 The OpenEmbedded build system processes a massive amount of
364 data that causes lots of network, disk and CPU activity and
365 is sensitive to even single-bit failures in any of these areas.
366 True random failures have always been traced back to hardware
367 or virtualiZation issues.
361 </para> 368 </para>
362 </answer> 369 </answer>
363 </qandaentry> 370 </qandaentry>