[Bug 1071209] Re: memtest86 test #7 fails (random number sequence error)
Bug Watch Updater
1071209 at bugs.launchpad.net
Thu Nov 8 21:30:18 UTC 2012
Launchpad has imported 25 comments from the remote bug at
https://bugzilla.novell.com/show_bug.cgi?id=773569.
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-07-29T13:40:48+00:00 Abittner wrote:
User-Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/536.11
(KHTML, like Gecko) Chrome/20.0.1132.57 Safari/536.11
I was building a new test system described in my other bug over at
https://bugzilla.novell.com/show_bug.cgi?id=773565
smolts is:
http://www.smolts.org/client/show/pub_73920daf-1fba-42ec-be09-adb113ce053d
and I first thought I had serious hardware trouble as the memtest test
number 7 resulted in endless errors. Changing ram modules, using only
single modules or completely different ones for example different in
speed and latencies always resulted in the same test number 7 failing
seriously
I was using the memtest+ 4.20 from the 12.2/rc1/x86 image written to a
usb key / usb stick and booted from that stick on that uefi system from
above.
Eventually I used my older 12.1/x86 dvd iso booting via dvd rom drive and dvd rom, also having memtest+ version 4.20 and this now runs flawlessly on this same uefi machine, same configuration, only booting the memtest entry from the initial boot menu at pre-installation.
This machine has uefi, but maybe there is a problem with booting the
later generation iso image from usb keys / usb sticks in general at suse
or maybe this is slightly a different memtest+ 4.20 and not really
identical on 12.1 and 12.2 iso images?
I am not really sure what to make of this behavior and where to pinpoint
the source for this bug.
maybe related bugs:
http://bugzilla.novell.com/show_bug.cgi?id=773565
http://bugzilla.novell.com/show_bug.cgi?id=753574
maybe there is even some relation to:
http://bugzilla.novell.com/show_bug.cgi?id=771552
Thanks and regards.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/0
------------------------------------------------------------------------
On 2012-08-18T01:09:13+00:00 Upscope wrote:
I ran into this yesterday after experiencing some system errors with no
explanation. This system is a Intel motherboard with 8GB RAM (DDR3 - 4
2GB modules.
I rotated the modules, removed so4 GB, changed slots for the pairs, etc.
Always reports error at 0x08100000 even with 1 2GB module installed.
This always occurs at start of test 7.
Since this memory has worked for four years, and never had errors. I
think its a test 7 problem. Also both 12.2 RC2 and 12.1 boot and work.
openSUSE 12.2(3.4.6-1.1-desktop x86_64)|KDE 4.8.4
"release 2"|Intel core2duo 2.5 MHZ,|8GB
DDR3|GeForce 8400GS(NVIDIA-Linux-x86_64-295.71)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/1
------------------------------------------------------------------------
On 2012-08-18T01:11:06+00:00 Upscope wrote:
Ops just noticed the fact it is occuring from thumb drive version. Mine
is doing it from the iso written to DVD, memtest option on boot.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/2
------------------------------------------------------------------------
On 2012-08-18T07:40:46+00:00 Abittner wrote:
Btw, update, at that timeframe when I originally reported this bug, I
actually found some pre-release beta1 it was I think version of
memtestplus on those original developers folks forum site, there was a
beta forum there, and I think it was beta1 of 5.0.0 or so
I put that onto a usb stick and booted it and that ran flawlessly on
this system.
This version 5.0.0 has different tests though and more extensive
hardware support and detection. it didnt report errors on this same
hardware in any of its tests.
I was scared that my system was defective so I used that memtest+ 5 to
verify this rather new hardware as I had thought it was a compatibility
problem with 4.20, although it was odd.
Its still weird that the newer 4.20 of 12.2 reports problems but the
older 4.20 from the 12.1 doesnt have trouble
http://forum.memtest.org/
redirects to
http://forum.canardpc.com/forums/73-Memtest86-Official-forum
then there is thread
http://forum.canardpc.com/threads/68001-Memtest86-5.00-Beta-available-%21-Need-betatesters-%21
it can do 64bit support, and multicpucore tests and so on
greetings.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/3
------------------------------------------------------------------------
On 2012-08-18T17:08:17+00:00 Upscope wrote:
Thanks for the update. I will try the 12.1 disc version and also
download the newer version. I have a thumb drive Ill try to install it
on. Never create a bootable thumb drive , will learn.
Thanks.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/4
------------------------------------------------------------------------
On 2012-08-18T23:28:12+00:00 Felix Miata wrote:
With 176760 byte 4.20-7.1.2 this also happens on Kairo's Sandy Bridge
Intel, and a K10 @2813MHz loaded via Grub Legacy from HD. The Sandy
Bridge works fine with the memtest.org 4.20. The K10 works fine on the
180856 byte 2011/05/13 4.20 which I suppose came from 11.4.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/5
------------------------------------------------------------------------
On 2012-09-13T13:47:43+00:00 Contezero wrote:
I've the same problem with 12.2/x86 final iso image from usb key.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/6
------------------------------------------------------------------------
On 2012-09-26T06:23:05+00:00 J-koenig wrote:
(In reply to comment #6)
> I've the same problem with 12.2/x86 final iso image from usb key.
me too:-(
I just wanted to test a PC with memtest using the official dual-sided 12.2 DVD.
both 32bit and 64bit throw zillions errors for test # (random number sequence) starting at 129MB (PC has 2*2GB DIMMs).
using the memtest on official 12.1 DVD works fine -- no errors at all,
so the hw is ok and 12.2 media is broken. pitty:-((
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/7
------------------------------------------------------------------------
On 2012-09-26T16:30:34+00:00 Duwe wrote:
qemu-kvm -m 512 -kernel memtest-12.2-DVD
nicely shows the problem. Anyone who still sees a dependency on the source medium type (USB vs. DVD) please speak up now or remain silent.
There were _no_ source code changes AFAIK between 12.1 and 12.2 so we're
most likely facing a compiler bug here.
Maybe I can be more precise before handing this over to the gcc
maintainers.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/8
------------------------------------------------------------------------
On 2012-10-04T14:20:54+00:00 Duwe wrote:
Created an attachment (id=508246)
source file test.c form memtest86+-4.20
discriminating file.
compile with
gcc -S -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin -ffreestanding test.c
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/9
------------------------------------------------------------------------
On 2012-10-04T14:22:49+00:00 Duwe wrote:
Created an attachment (id=508248)
working assembler file
Built with
gcc (SUSE Linux) 4.6.2
from 12.1
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/10
------------------------------------------------------------------------
On 2012-10-04T14:24:54+00:00 Duwe wrote:
Created an attachment (id=508250)
broken assembler file
Built with
gcc (SUSE Linux) 4.7.1 20120723 [gcc-4_7-branch revision 189773]
on Factory/head
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/11
------------------------------------------------------------------------
On 2012-10-04T14:27:42+00:00 Duwe wrote:
Injecting the broken / working compiler output into the other build
environment fixes or breaks it, respectively.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/12
------------------------------------------------------------------------
On 2012-10-04T14:35:41+00:00 Duwe wrote:
<sys/io.h> and <inttypes.h> differ slightly; the test.i files are otherwise
identical.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/13
------------------------------------------------------------------------
On 2012-10-04T14:55:13+00:00 Duwe wrote:
Created an attachment (id=508256)
reverse patch, from working to broken
This patch, applied reverse, fixes a broken build.
Auto label numbers raised by 9900, to avoid clashes.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/14
------------------------------------------------------------------------
On 2012-10-05T12:55:57+00:00 Duwe wrote:
The bug is triggered by a different register allocation.
gcc-4.6 uses ebp for the volatile ulong *start (remember, -fomit-frame-pointer), where gcc-4.7 prefers ecx.
ECX is, AFAIK "caller-save" by the ABI calling convention; and the asm
inline calls rand(), which it does not declare. Rand() is free to
clobber ecx.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/15
------------------------------------------------------------------------
On 2012-10-05T12:58:59+00:00 Duwe wrote:
Created an attachment (id=508365)
Declare that the asm snippet clobbers ecx.
Suggested fix.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/16
------------------------------------------------------------------------
On 2012-10-05T13:25:55+00:00 Duwe wrote:
Applied.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/17
------------------------------------------------------------------------
On 2012-10-05T14:00:09+00:00 Bwiedemann wrote:
This is an autogenerated message for OBS integration:
This bug (773569) was mentioned in
https://build.opensuse.org/request/show/137248 Factory / memtest86+
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/18
------------------------------------------------------------------------
On 2012-10-05T14:39:13+00:00 Kairo-kairo wrote:
I hope steps are being made to contribute this fix back to the upstream.
;-)
That said, thanks for figuring this out!
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/19
------------------------------------------------------------------------
On 2012-10-05T15:20:54+00:00 Arvidjaar-s wrote:
Will there be update for 12.2? I understand that DVD won't change, but
users still have it also installed as bootloader menu.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/20
------------------------------------------------------------------------
On 2012-10-06T06:24:51+00:00 Corax2-05 wrote:
I really hope you make an update and make a new ISO!
I bought a new RAM and a new board because of this damn bug.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/21
------------------------------------------------------------------------
On 2012-10-09T12:59:25+00:00 Abittner wrote:
in 12.3/x64/milestone0 (iso image) the memtest+ still immediately fails
when directly selecting test #7
has this fix not made it into 12.3/milestone0 yet?
do we need a new bug for 12.3?
thanks.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/22
------------------------------------------------------------------------
On 2012-10-09T14:33:59+00:00 Abittner wrote:
*** Bug 784206 has been marked as a duplicate of this bug. ***
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/23
------------------------------------------------------------------------
On 2012-10-11T20:08:16+00:00 Suse-beta wrote:
It's unlikely that fixed ISOs for 12.2 are published, therefore the
next-best solution is an entry in the release notes. I just requested
this - see bug 784757.
This bug is also mentioned on the "most annoying bugs" page in the wiki,
but I doubt too many people read it...
Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/24
** Changed in: memtest86+ (openSUSE)
Status: Unknown => Fix Released
** Changed in: memtest86+ (openSUSE)
Importance: Unknown => Medium
** Bug watch added: Novell/SUSE Bugzilla #773565
https://bugzilla.novell.com/show_bug.cgi?id=773565
** Bug watch added: Novell/SUSE Bugzilla #753574
https://bugzilla.novell.com/show_bug.cgi?id=753574
** Bug watch added: Novell/SUSE Bugzilla #771552
https://bugzilla.novell.com/show_bug.cgi?id=771552
--
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 fails (random number sequence error)
Status in Memtest86+:
Unknown
Status in “memtest86+” package in Ubuntu:
Confirmed
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/memtest86+/+bug/1071209/+subscriptions
More information about the foundations-bugs
mailing list