You may want to try setting the progress interval parameter so you can see
if your system is running slowly or just deadlocked.

On Fri, Jan 7, 2011 at 10:49 AM, Jianghao Guo <[email protected]> wrote:

> I just installed M5 with SPLASH2 benchmark.
>
> There is no problem to compile ALPHA_SE or FS m5.opt binary.
>
> I tried to run SPLASH2 benchmark but it’s hanging there for over 30 hours.
> Here is the log file.
>
>
>
> [...@dhcp-10-63-4-32 m5]$ build/ALPHA_SE/m5.opt configs/splash2/run.py -d
> -n4 -b FFT --rootdir=/home/kev/m5/splash2/splash2/codes
>
> M5 Simulator System
>
>
>
> Copyright (c) 2001-2008
>
> The Regents of The University of Michigan
>
> All Rights Reserved
>
>
>
>
>
> M5 compiled Jan  5 2011 21:40:47
>
> M5 revision Unknown
>
> M5 started Jan  5 2011 21:42:31
>
> M5 executing on dhcp-10-63-4-32
>
> command line: build/ALPHA_SE/m5.opt configs/splash2/run.py -d -n4 -b FFT
> --rootdir=/home/kev/m5/splash2/splash2/codes
>
> Global frequency set at 1000000000000 ticks per second
>
> 0: system.remote_gdb.listener: listening for remote gdb #0 on port 7002
>
> 0: system.remote_gdb.listener: listening for remote gdb #1 on port 7003
>
> 0: system.remote_gdb.listener: listening for remote gdb #2 on port 7000
>
> 0: system.remote_gdb.listener: listening for remote gdb #3 on port 7001
>
> info: Entering event queue @ 0.  Starting simulation...
>
> info: Increasing stack size by one page.
>
> warn: ignoring syscall sigprocmask(3, 18446744073709551615, ...)
>
> For more information see: http://www.m5sim.org/warn/5c5b547f
>
> warn: ignoring syscall sigprocmask(3, 0, ...)
>
> For more information see: http://www.m5sim.org/warn/5c5b547f
>
> warn: ignoring syscall sigaction(8, 4831387552, ...)
>
> For more information see: http://www.m5sim.org/warn/5c5b547f
>
> warn: ignoring syscall sigaction(11, 4831387552, ...)
>
> For more information see: http://www.m5sim.org/warn/5c5b547f
>
> warn: ignoring syscall sigaction(10, 4831387552, ...)
>
> For more information see: http://www.m5sim.org/warn/5c5b547f
>
> warn: ignoring syscall sigaction(4, 4831387552, ...)
>
> For more information see: http://www.m5sim.org/warn/5c5b547f
>
> warn: ignoring syscall sigaction(7, 4831387552, ...)
>
> For more information see: http://www.m5sim.org/warn/5c5b547f
>
> warn: ignoring syscall sigaction(6, 4831387552, ...)
>
> For more information see: http://www.m5sim.org/warn/5c5b547f
>
> warn: ignoring syscall sigaction(12, 4831387552, ...)
>
> For more information see: http://www.m5sim.org/warn/5c5b547f
>
> warn: ignoring syscall sigaction(5, 4831387552, ...)
>
> For more information see: http://www.m5sim.org/warn/5c5b547f
>
> warn: ignoring syscall sigaction(13, 4831387552, ...)
>
> For more information see: http://www.m5sim.org/warn/5c5b547f
>
>
>
> _______________________________________________
> m5-users mailing list
> [email protected]
> http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
>



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

Reply via email to