[Bug 1071209] Re: memtest86 test #7 false positives (random number sequence error)

Launchpad Bug Tracker 1071209 at bugs.launchpad.net
Thu Dec 6 15:25:28 UTC 2012


This bug was fixed in the package memtest86+ - 4.20-1.1ubuntu3

---------------
memtest86+ (4.20-1.1ubuntu3) raring; urgency=low

  * Fix test#7 false positives due to compiler issues. (LP: #1071209)
    Original patch author Torsten Duwe <duwe at suse.com>.
 -- Chris J Arges <chris.j.arges at canonical.com>   Tue, 04 Dec 2012 16:23:35 -0600

** Changed in: memtest86+ (Ubuntu Raring)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1071209

Title:
  memtest86 test #7 false positives (random number sequence error)

Status in Memtest86+:
  Unknown
Status in Release Notes for Ubuntu:
  New
Status in “memtest86+” package in Ubuntu:
  Fix Released
Status in “memtest86+” source package in Quantal:
  In Progress
Status in “memtest86+” source package in Raring:
  Fix Released
Status in “memtest86+” package in openSUSE:
  Fix Released

Bug description:
  Trying to check the memory at newly bought notebook I found a bug in
  the memtest86+ version 4.20 in ubuntu 12.10, in ubuntu 12.04 it is ok.
  The bug is reported at least in Fedora and Opensuse. It is assumed
  that the bug is caused by the gcc-4.7.

  It is easily  reproducible - select the test #7 in memtest or just
  wait till it - starting from the 129Mb it will report a lot of errors.
  I have checked it on three different systems , two of them I use on a
  daily basis and would note if RAM is really bad.

  https://bugzilla.redhat.com/show_bug.cgi?id=805813

  http://lists.opensuse.org/opensuse-bugs/2012-09/msg04386.html

  --

  SRU Justification

  [Impact]
  Users of memtest86+ will get false positives of memory failures. This will cause users to suspect hardware and require unnecessary testing/headaches.

  [Test Case]
  Boot Ubuntu in Quantal/Raring. At GRUB select memtest86+. Wait until the 7th test. It will fail at the 7th test.

  [Regression Potential]
  The fix is just adding another register to clobber in the inline assembly routine. Because  this affects newer GCC versions, older releases aren't affected. Thus, if there are compiler changes we should re-test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/memtest86+/+bug/1071209/+subscriptions



More information about the Ubuntu-sponsors mailing list