[Bug 1071209] Re: memtest86+ test #7 false positives (random number sequence error)
Bug Watch Updater
1071209 at bugs.launchpad.net
Sat Oct 28 05:24:26 UTC 2017
Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=805813.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
------------------------------------------------------------------------
On 2012-03-22T09:08:21+00:00 Karel wrote:
Description of problem:
Trying to run the latest memtest86+ on various hardware, even in qemu, the seventh test (Random number sequence) fails and reports errors for each address from 129 MiB on.
Version-Release number of selected component (if applicable):
memtest86+ 4.20 from Fedora 17 Alpha DVD
How reproducible:
always
Steps to Reproduce:
1. qemu-kvm -m 1024 -cdrom Fedora-17-Alpha-x86_64.DVD.iso
2. choose Troubleshooting => Run memory test
Actual results:
see the attached screenshot
Expected results:
no errors
Additional info:
Initially, I've run this on Intel SandyBridge hardware - Pentium B950 with some Samsung memories, and it failed this way, leading me to unjustified warranty claim ...
After that, I've verified the same memtest behaviour on T510 with Core i7 M620, and on some older desktop with Core i5 - real hardware, proven by months of service => seeing the same all the time I've tried in qemu and it fails too.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/0
------------------------------------------------------------------------
On 2012-03-22T09:09:08+00:00 Karel wrote:
Created attachment 571941
screenshot of the problem
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/1
------------------------------------------------------------------------
On 2012-03-22T14:06:12+00:00 Jaroslav wrote:
Created attachment 572002
Temporal workaround
Thanks for reporting. It seems to be related to gcc-4.7 update. Temporal workaround patch is attached (it could negatively affect performance).
Scratch build:
http://koji.fedoraproject.org/koji/taskinfo?taskID=3922148
I am working on better patch.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/2
------------------------------------------------------------------------
On 2012-03-27T09:13:39+00:00 Fedora wrote:
memtest86+-4.20-6.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/memtest86+-4.20-6.fc17
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/3
------------------------------------------------------------------------
On 2012-03-27T18:08:06+00:00 Adam wrote:
Proposing as Final blocker, though it's somewhat arguable. Criterion:
"All release media must include a standalone memory test utility. A boot
menu option to launch this utility must be present and must work
correctly. "
Also proposing as Beta NTH, it would be good to ensure the memtest in
Beta works.
--
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/4
------------------------------------------------------------------------
On 2012-03-28T05:59:57+00:00 Fedora wrote:
Package memtest86+-4.20-6.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing memtest86+-4.20-6.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-4808/memtest86+-4.20-6.fc17
then log in and leave karma (feedback).
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/5
------------------------------------------------------------------------
On 2012-03-28T21:35:11+00:00 Przemek wrote:
*** Bug 807844 has been marked as a duplicate of this bug. ***
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/6
------------------------------------------------------------------------
On 2012-03-29T00:11:05+00:00 Adam wrote:
Discussed at 2012-03-28 go/no-go meeting, acting as an NTH review
meeting. Accepted as NTH: this can't be fixed with an update, and it's
obviously visibly bad to have broken memtest on our beta images.
--
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/7
------------------------------------------------------------------------
On 2012-03-29T04:12:23+00:00 Fedora wrote:
memtest86+-4.20-6.fc17 has been pushed to the Fedora 17 stable
repository. If problems still persist, please make note of it in this
bug report.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/8
** Changed in: memtest86+
Status: Unknown => Fix Released
** Changed in: memtest86+
Importance: Unknown => Undecided
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to memtest86+ in Ubuntu.
https://bugs.launchpad.net/bugs/1071209
Title:
memtest86+ test #7 false positives (random number sequence error)
Status in Memtest86+:
Fix Released
Status in Release Notes for Ubuntu:
Invalid
Status in memtest86+ package in Ubuntu:
Fix Released
Status in memtest86+ source package in Quantal:
Fix Released
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 foundations-bugs
mailing list