Bug 805813 - the seventh test (random number sequence) fails at about 129 MiB
Summary: the seventh test (random number sequence) fails at about 129 MiB
Alias: None
Product: Fedora
Classification: Fedora
Component: memtest86+
Version: 17
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
Whiteboard: AcceptedNTH
: 807844 (view as bug list)
Depends On:
Blocks: F17Blocker, F17FinalBlocker F17Beta-accepted, F17BetaFreezeExcept
TreeView+ depends on / blocked
Reported: 2012-03-22 09:08 UTC by Karel Volný
Modified: 2012-03-29 04:12 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2012-03-29 04:12:23 UTC

Attachments (Terms of Use)
screenshot of the problem (25.50 KB, image/png)
2012-03-22 09:09 UTC, Karel Volný
no flags Details
Temporal workaround (1.34 KB, patch)
2012-03-22 14:06 UTC, Jaroslav Škarvada
no flags Details | Diff

Description Karel Volný 2012-03-22 09:08:21 UTC
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:

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.

Comment 1 Karel Volný 2012-03-22 09:09:08 UTC
Created attachment 571941 [details]
screenshot of the problem

Comment 2 Jaroslav Škarvada 2012-03-22 14:06:12 UTC
Created attachment 572002 [details]
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:
I am working on better patch.

Comment 3 Fedora Update System 2012-03-27 09:13:39 UTC
memtest86+-4.20-6.fc17 has been submitted as an update for Fedora 17.

Comment 4 Adam Williamson 2012-03-27 18:08:06 UTC
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

Comment 5 Fedora Update System 2012-03-28 05:59:57 UTC
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:
then log in and leave karma (feedback).

Comment 6 Przemek Klosowski 2012-03-28 21:35:11 UTC
*** Bug 807844 has been marked as a duplicate of this bug. ***

Comment 7 Adam Williamson 2012-03-29 00:11:05 UTC
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

Comment 8 Fedora Update System 2012-03-29 04:12:23 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.