Changeset 6bcd464

Timestamp:

01/23/2019 11:05:19 AM (5 years ago)

Author:

Ken Moffat <ken@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 8.4, 9.0, 9.1, bdubbs/svn, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

d0331db

Parents:

31ee0ed

Message:

Rust: I was mistaken about the Ryzen problem with the testsuite, traps and a few segfaults are normal but nobody usually looks at the syslog.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@21021 af4574ff-66df-0310-9fd7-8a98e5e911e0

Files:

• general/prog/rust.xml (modified) (1 diff)
• introduction/welcome/changelog.xml (modified) (1 diff)

general/prog/rust.xml

@@ -202 +202 @@
     </para>
 
-    <caution>
+    <note>
       <para>
-        On AMD Ryzen processors (family 17h), the non-optimized version of libstd
-        which is compiled at the start of the tests contains one or more opcodes
-        which are not implemented on this CPU family. These will be logged in the
+        The testsuite will generate some messages in the
         <phrase revision="sysv">system log</phrase>
         <phrase revision="systemd">systemd journal</phrase>
-        and will be followed a few minutes later by segmentation faults. Despite
-        that, the tests continue to run, apparently normally. But the system may
-        reboot before the tests have completed. The normal optimized libraries
-        run without this problem.
+        for traps on invalid opcodes, and for segmentation faults.
+        In themselves these are nothing to worry about, although if the
+        output from the testsuite reports tests which FAIL with such faults
+        then there may be a problem.
       </para>
-      <para>
-        A mitigation is to install gdb
-        <!-- systemd apparently handles this with systemd-coredump -->
-        <phrase revision="sysv">and to run the tests with 'ulimit -C disabled'</phrase>
-        but this does not always prevent the system rebooting.
-      </para>
-    </caution>
+    </note>
 
     <para>

introduction/welcome/changelog.xml

@@ -45 +45 @@
       <para>January 23rd, 2018</para>
       <itemizedlist>
+        <listitem>
+          <para>[ken] - Change the 'Caution' on the rustc page (about running
+          the testsuite on AMD Ryzens) to a 'Note', the reboot problem was
+          almost certainly kernel triple-faults on an -rc kernel, although
+          the testsuite seemed to reliably trigger it at that time. The
+          supposed mitigation (now removed) was clearly irrelevant, and to
+          top it all the invalid opcodes also appear on other machines, so
+          they too are probably deliberate.</para>
+        </listitem>
         <listitem>
           <para>[pierre] - Update dependencies for libtasn1 and GTK+3: