Hi All,

I'm trying the M5 now on a 64 bit machine (I had some problems before
runinng m5 on a 32 bit machine), I got the below output (the last one, where
some reg tests passed & others failed) when doing the regression tests for
the ALPHA_SE, while when trying the tests of the SPARC either SE or FS, all
tests fail, at their output files "stdout" & "stderr" files, they seem
working but in the terminal I get the following messages (after some reading
and warnning lines):

scons: warning: The build_dir keyword has been deprecated; use the
variant_dir keyword instead.
File
"/home/NU/Desktop/Rehab/extracted/m5-stable-94c016415053/build/SPARC_SE/SConscript",
line 252, in <module>
scons: done reading SConscript files.
scons: Building targets ...
***** build/SPARC_SE/tests/debug/long/00.gzip/sparc/linux/o3-timing FAILED!

***** build/SPARC_SE/tests/debug/long/00.gzip/sparc/linux/simple-atomic
FAILED!

***** build/SPARC_SE/tests/debug/long/00.gzip/sparc/linux/simple-timing
FAILED!

***** build/SPARC_SE/tests/debug/long/10.mcf/sparc/linux/simple-atomic
FAILED!

***** build/SPARC_SE/tests/debug/long/10.mcf/sparc/linux/simple-timing
FAILED!

***** build/SPARC_SE/tests/debug/long/50.vortex/sparc/linux/simple-atomic
FAILED!

***** build/SPARC_SE/tests/debug/long/50.vortex/sparc/linux/simple-timing
FAILED!

***** build/SPARC_SE/tests/debug/long/70.twolf/sparc/linux/simple-atomic
FAILED!

***** build/SPARC_SE/tests/debug/long/70.twolf/sparc/linux/simple-timing
FAILED!

***** build/SPARC_SE/tests/debug/quick/00.hello/sparc/linux/simple-atomic
FAILED!

***** build/SPARC_SE/tests/debug/quick/00.hello/sparc/linux/simple-timing
FAILED!

***** build/SPARC_SE/tests/debug/quick/02.insttest/sparc/linux/o3-timing
FAILED!

***** build/SPARC_SE/tests/debug/quick/02.insttest/sparc/linux/simple-atomic
FAILED!

***** build/SPARC_SE/tests/debug/quick/02.insttest/sparc/linux/simple-timing
FAILED!

*****
build/SPARC_SE/tests/debug/quick/40.m5threads-test-atomic/sparc/linux/o3-timing-mp
FAILED!

*****
build/SPARC_SE/tests/debug/quick/40.m5threads-test-atomic/sparc/linux/simple-atomic-mp
FAILED!

*****
build/SPARC_SE/tests/debug/quick/40.m5threads-test-atomic/sparc/linux/simple-timing-mp
FAILED!



Below is the last part of output of the ALPHA_SE tests which has some passed
and some failed, for the failed ones I got the "gzip: stdout: Broken pipe"
in teh "stderr" file, can somebody tell me what does this means?????



===== Statistics differences =====
Maximum error magnitude: +0.000000%

                                  Reference  New Value   Abs Diff   Pct Chg
Key statistics:

  host_inst_rate                     105048      14589     -90459   -86.11%
  host_mem_usage                     203136     228992      25856   +12.73%
  sim_insts                           12773      12773          0    +0.00%
  sim_ticks                        14251500   14251500          0    +0.00%
  system.cpu.commit.COM:count::0       6403       6403          0    +0.00%
  system.cpu.commit.COM:count::1       6404       6404          0    +0.00%
  system.cpu.commit.COM:count::total      12807      12807          0
+0.00%

Largest 20 relative errors (> 0%):


***** build/ALPHA_SE/tests/debug/quick/01.hello-2T-smt/alpha/linux/o3-timing
passed.

Running test in
build/ALPHA_SE/tests/debug/quick/20.eio-short/alpha/eio/simple-atomic.
build/ALPHA_SE/m5.debug -d
build/ALPHA_SE/tests/debug/quick/20.eio-short/alpha/eio/simple-atomic -re
tests/run.py
build/ALPHA_SE/tests/debug/quick/20.eio-short/alpha/eio/simple-atomic
Redirecting stdout to
build/ALPHA_SE/tests/debug/quick/20.eio-short/alpha/eio/simple-atomic/simout
Redirecting stderr to
build/ALPHA_SE/tests/debug/quick/20.eio-short/alpha/eio/simple-atomic/simerr
scons: *** Error 1
M5 exited with non-zero status 1
***** build/ALPHA_SE/tests/debug/quick/20.eio-short/alpha/eio/simple-atomic
FAILED!

Running test in
build/ALPHA_SE/tests/debug/quick/20.eio-short/alpha/eio/simple-timing.
build/ALPHA_SE/m5.debug -d
build/ALPHA_SE/tests/debug/quick/20.eio-short/alpha/eio/simple-timing -re
tests/run.py
build/ALPHA_SE/tests/debug/quick/20.eio-short/alpha/eio/simple-timing
Redirecting stdout to
build/ALPHA_SE/tests/debug/quick/20.eio-short/alpha/eio/simple-timing/simout
Redirecting stderr to
build/ALPHA_SE/tests/debug/quick/20.eio-short/alpha/eio/simple-timing/simerr
scons: *** Error 1
M5 exited with non-zero status 1
***** build/ALPHA_SE/tests/debug/quick/20.eio-short/alpha/eio/simple-timing
FAILED!

Running test in
build/ALPHA_SE/tests/debug/quick/30.eio-mp/alpha/eio/simple-atomic-mp.
build/ALPHA_SE/m5.debug -d
build/ALPHA_SE/tests/debug/quick/30.eio-mp/alpha/eio/simple-atomic-mp -re
tests/run.py
build/ALPHA_SE/tests/debug/quick/30.eio-mp/alpha/eio/simple-atomic-mp
Redirecting stdout to
build/ALPHA_SE/tests/debug/quick/30.eio-mp/alpha/eio/simple-atomic-mp/simout
Redirecting stderr to
build/ALPHA_SE/tests/debug/quick/30.eio-mp/alpha/eio/simple-atomic-mp/simerr
scons: *** Error 1
M5 exited with non-zero status 1
***** build/ALPHA_SE/tests/debug/quick/30.eio-mp/alpha/eio/simple-atomic-mp
FAILED!

Running test in
build/ALPHA_SE/tests/debug/quick/30.eio-mp/alpha/eio/simple-timing-mp.
build/ALPHA_SE/m5.debug -d
build/ALPHA_SE/tests/debug/quick/30.eio-mp/alpha/eio/simple-timing-mp -re
tests/run.py
build/ALPHA_SE/tests/debug/quick/30.eio-mp/alpha/eio/simple-timing-mp
Redirecting stdout to
build/ALPHA_SE/tests/debug/quick/30.eio-mp/alpha/eio/simple-timing-mp/simout
Redirecting stderr to
build/ALPHA_SE/tests/debug/quick/30.eio-mp/alpha/eio/simple-timing-mp/simerr
scons: *** Error 1
M5 exited with non-zero status 1
***** build/ALPHA_SE/tests/debug/quick/30.eio-mp/alpha/eio/simple-timing-mp
FAILED!

Running test in
build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest.
build/ALPHA_SE/m5.debug -d
build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest -re
tests/run.py build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest
Redirecting stdout to
build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest/simout
Redirecting stderr to
build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest/simerr
scons: *** Error 1
M5 exited with non-zero status 1
***** build/ALPHA_SE/tests/debug/quick/30.eio-mp/alpha/eio/simple-timing-mp
FAILED!

Running test in
build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest.
build/ALPHA_SE/m5.debug -d
build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest -re
tests/run.py build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest
Redirecting stdout to
build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest/simout
Redirecting stderr to
build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest/simerr
diff -ubr -I '^command line:' -I '^M5 compiled ' -I '^M5 started ' -I '^M5
executing on ' -I '^Simulation complete at' -I '^Listening for' -I
'listening for remote gdb' --exclude=stats.txt --exclude=outdiff
tests/quick/50.memtest/ref/alpha/linux/memtest
build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest >
build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest/outdiff
scons: *** Error 1
===== Output differences =====
diff -ubr -I '^command line:' -I '^M5 compiled ' -I '^M5 started ' -I '^M5
executing on ' -I '^Simulation complete at' -I '^Listening for' -I
'listening for remote gdb' --exclude=stats.txt --exclude=outdiff
tests/quick/50.memtest/ref/alpha/linux/memtest/simout
build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest/simout
--- tests/quick/50.memtest/ref/alpha/linux/memtest/simout       2009-07-06
02:07:09.000000000 +0300
+++
build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest/simout
2010-07-06 14:23:29.000000000 +0300
@@ -5,11 +5,11 @@
 All Rights Reserved


-M5 compiled Apr 22 2009 06:58:26
-M5 revision ce26a627c841 6126 default qtip tip stats_no_compat.diff
-M5 started Apr 22 2009 07:17:27
-M5 executing on maize
-command line: build/ALPHA_SE/m5.fast -d
build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest -re
tests/run.py build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest
+M5 compiled Jul  6 2010 13:51:17
+M5 revision Unknown
+M5 started Jul  6 2010 14:03:13
+M5 executing on lab2105t7nf4j.student.nileu
+command line: build/ALPHA_SE/m5.debug -d
build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest -re
tests/run.py build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest
 Global frequency set at 1000000000000 ticks per second
 info: Entering event queue @ 0.  Starting simulation...
 Exiting @ tick 268915439 because maximum number of loads reached

===== Statistics differences =====
Maximum error magnitude: +0.000000%

                                  Reference  New Value   Abs Diff   Pct Chg
Key statistics:

  host_mem_usage                     328320     354260      25940    +7.90%
  sim_ticks                       268915439  268915439          0    +0.00%

Largest 20 relative errors (> 0%):


***** build/ALPHA_SE/tests/debug/quick/50.memtest/alpha/linux/memtest
passed.

scons: done building targets.



////////////////////////////////////


the output at the file
m5-stable-94c016415053/tests/quick/20.eio-short/ref/alpha/eio/simple-atomic/simerr

warn: Sockets disabled, not accepting gdb connections
For more information see: http://www.m5sim.org/warn/d946bea6
hack: be nice to actually delete the event here

gzip: stdout: Broken pipe

& at simout

M5 Simulator System

Copyright (c) 2001-2008
The Regents of The University of Michigan
All Rights Reserved


M5 compiled Apr 21 2009 16:38:39
M5 revision e6dd09514462 6117 default qtip tip stats-update
M5 started Apr 21 2009 16:57:23
M5 executing on zizzer
command line: build/ALPHA_SE/m5.fast -d
build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-atomic -re
tests/run.py
build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-atomic
Global frequency set at 1000000000000 ticks per second
info: Entering event queue @ 0.  Starting simulation...
main dictionary has 1245 entries
49508 bytes wasted
>Exiting @ tick 250015500 because a thread reached the max instruction count



& @
m5-stable-94c016415053/tests/quick/30.eio-mp/ref/alpha/eio/simple-timing-mp

warn: Sockets disabled, not accepting gdb connections
For more information see: http://www.m5sim.org/warn/d946bea6
hack: be nice to actually delete the event here

gzip: stdout: Broken pipe

gzip: stdout: Broken pipe

gzip: stdout: Broken pipe

gzip: stdout: Broken pipe


what does that mean???


Thanks a lot in advance...

-- 
Rehab H. Massoud
[email protected]
_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users

Reply via email to