lkml.org 
[lkml]   [2003]   [Mar]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: syslog full of kernel BUGS, frequent intermittent instability
Date
On 1 March 2003 15:21, wyleus wrote:
> Friday, Feb 28 2003
> Results of burnMMX tests
>
> command: burnMMX x; echo $?
>
> where x represents memory size parameter passed to burnMMX as
> follows;
>
> <small excerpt from cpuburn readme>
> burnBX and burnMMX are essentially very intense RAM testers. They
> can also take an optional parameter indicating the RAM size to be
> tested:
>
> A = 2 kB E = 32 kB I = 512 kB M = 8 MB
> B = 4 F = 64 J = 1 MB N = 16
> C = 8 G = 128 K = 2 O = 32
> D = 16 H = 256 L = 4 P = 64
>
> the default memsize used when none is specified is F=64k
>
> exit codes for burnMMX are as follows;
> 130 = process killed manually using ctl-c
> 254 = integer/memory error
> 255 = FP/MMX error
>
> mem runtime exit
> size (minutes) code
>
> A (2K) 26:00 130
> 28:15 130
> F (64K) 2:00 254
> 11:00 130
> 6:00 130
> 21:42 130
> G (128K) 6:00 130
> H (256K) 3:25 254
> 2:40 254
> 0:45 254 1 these
> 1:35 254 1 are
> 0:40 254 1 consecutive
> 3:45 254 1 runs
> 33:00 130 1
> 7:00 254 1
> 7:00 254 1
> 5:16 254 1
> 17:19 254 1
> I (512K) 6:00 254
> 1:48 254
> 5:34 254
>
> Sat, March 1, 2003
>
> Switched the RAM stick from the first slot (closest
> to CPU), to the middle slot;
>
> command: time burnMMX x; echo $?
>
> (using the time command, manual exits using
> ctl-c provide exit code 2, but I still list it
> here as 130 in the table for consistency)
>
> mem runtime exit
> size (minutes) code
>
> G (128K) 2:46 254
> 21:50 130
> H (256K) 20:12 130
> 33:46 130
> I (512K) 20:06 130
> 21:58 130
> J (1024K) 21:57 130
>
> Only one error so far after 7 runs, which seems much better than
> before, but still unnacceptable I guess...
>
> Where should I go from here? Try another slot? Buy new RAM? More
> testing?

You should underclock and/or overvolt your system until it runs these
tests stably.
--
vda

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:33    [W:0.130 / U:3.064 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site