Software error or hardware error

GuloGulo · 2011-01-18, 15:42

Hi,
I'm running mprime 25.11 64-bit on ubuntu 10.04 and today mprime crashed after finding a factor in P1. This has happened several times before, but since I was running in menu mode I got some extra info.

Code:

GuloGulo/Phenom_II_X6_1055T, M53619337 has a factor: 3068239623794576992633, AID: E7349195353FF153379E68612A21F119
 [Comm thread Jan 18 14:17]
 [Comm thread Jan 18 14:17] PrimeNet success code with additional info:
 [Comm thread Jan 18 14:17] CPU credit is 5.0082 GHz-days.
 *** glibc detected *** ./mprime: free(): invalid next size (fast): 0x0000000001f94d10 ***
 ======= Backtrace: =========
 /lib/libc.so.6(+0x775b6)[0x7f5baf60b5b6]
 /lib/libc.so.6(cfree+0x73)[0x7f5baf611e83]
 ./mprime[0x426b2d]
 ./mprime[0x429ff6]
 ./mprime[0x4330be]
 ./mprime[0x4331cb]
 ./mprime[0x44770a]
 /lib/libpthread.so.0(+0x69ca)[0x7f5bafd389ca]
 /lib/libc.so.6(clone+0x6d)[0x7f5baf67a70d]

My machine is a Phenom II X6 1055T overclocked to 3.645GHz. It has been running with this overclock for months and I have never had any other errors than it crashing after finding a factor. Are these crashes still related to an overly ambitious overclock or could they be due to buggy software, libraries or mprime itself?

ckdo · 2011-01-18, 16:36

This is probably the infamous mprime P-1 segfault bug again, which has been around for ages.

GuloGulo · 2011-01-18, 21:22

OK, thanks for the quick reply! So there is nothing to do other than restart mprime? Is the bug that hard to track down?

Prime95 · 2011-01-19, 00:36

I believe this bug is fixed in version 26. Try it.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Hardware Error after 1s	StechusKaktus	Information & Answers	13	2018-02-20 07:46
Hardware Error?	Fred	Software	11	2016-03-09 19:18
Possible hardware error	kladner	Hardware	2	2011-09-01 22:13
hardware error	joblack	Hardware	13	2008-11-12 03:34
Error, hardware causing CRC error's	Unregistered	Information & Answers	3	2008-05-05 05:40

2011-01-18, 16:36	#2
ckdo Dec 2007 Cleves, Germany 1022₈ Posts	This is probably the infamous mprime P-1 segfault bug again, which has been around for ages.

2011-01-18, 21:22	#3
GuloGulo Jan 2011 Sweden 2 Posts	OK, thanks for the quick reply! So there is nothing to do other than restart mprime? Is the bug that hard to track down?

2011-01-19, 00:36	#4
Prime95 P90 years forever! Aug 2002 Yeehaw, FL 17·487 Posts	I believe this bug is fixed in version 26. Try it.