OK, thanks.
Xuhao Chen
PhD student
School of Computer
National University of Defense Technology
Changsha, Hunan, P.R.China, 410073
Tel: +86-159-741-03340 (Mobile)
From: Nilay Vaish
Date: 2012-02-11 23:28
To: gem5 users mailing list
Subject: Re: [gem5-users] error in running gem5 ALPHA_FS with 32 cores
Since nobody replied to your previous email, it is highly likely that no
one knows where the problem might be. I think you should try to debug this
problem on your own. Get back to list when you find some thing, or you are
unable to understand some piece of code.
--
Nilay
On Sat, 11 Feb 2012, Xuhao Chen wrote:
> When I try to run gem5.opt in ALPHA_FS mode with 32 cores (the host OS is Red
> Hat Enterprise 6 and modified PAL code "tsb_osfpal" has been used to support
> up to 64 processors), there is an error:
>
> [root@cxh gem5-09b482ee9ae0]# ./build/ALPHA_FS/gem5.opt
> configs/example/fs.py -n 32 --timing
> gem5 Simulator System. http://gem5.org
> gem5 is copyrighted software; use the --copyright option for details.
>
> gem5 compiled Jan 7 2012 10:57:45
> gem5 started Feb 8 2012 17:06:37
> gem5 executing on cxh
> command line: ./build/ALPHA_FS/gem5.opt configs/example/fs.py -n 32 --timing
> Global frequency set at 1000000000000 ticks per second
> info: kernel located at: /home/m5-system/binaries/vmlinux_2.6.27-gcc_4.3.4
> Listening for system connection on port 3456
> 0: system.tsunami.io.rtc: Real-time clock set to Thu Jan 1 00:00:00 2009
> 0: system.remote_gdb.listener: listening for remote gdb #0 on port 7000
> 0: system.remote_gdb.listener: listening for remote gdb #1 on port 7001
> 0: system.remote_gdb.listener: listening for remote gdb #2 on port 7002
> 0: system.remote_gdb.listener: listening for remote gdb #3 on port 7003
> 0: system.remote_gdb.listener: listening for remote gdb #4 on port 7004
> 0: system.remote_gdb.listener: listening for remote gdb #5 on port 7005
> 0: system.remote_gdb.listener: listening for remote gdb #6 on port 7006
> 0: system.remote_gdb.listener: listening for remote gdb #7 on port 7007
> 0: system.remote_gdb.listener: listening for remote gdb #8 on port 7008
> 0: system.remote_gdb.listener: listening for remote gdb #9 on port 7009
> 0: system.remote_gdb.listener: listening for remote gdb #10 on port 7010
> 0: system.remote_gdb.listener: listening for remote gdb #11 on port 7011
> 0: system.remote_gdb.listener: listening for remote gdb #12 on port 7012
> 0: system.remote_gdb.listener: listening for remote gdb #13 on port 7013
> 0: system.remote_gdb.listener: listening for remote gdb #14 on port 7014
> 0: system.remote_gdb.listener: listening for remote gdb #15 on port 7015
> 0: system.remote_gdb.listener: listening for remote gdb #16 on port 7016
> 0: system.remote_gdb.listener: listening for remote gdb #17 on port 7017
> 0: system.remote_gdb.listener: listening for remote gdb #18 on port 7018
> 0: system.remote_gdb.listener: listening for remote gdb #19 on port 7019
> 0: system.remote_gdb.listener: listening for remote gdb #20 on port 7020
> 0: system.remote_gdb.listener: listening for remote gdb #21 on port 7021
> 0: system.remote_gdb.listener: listening for remote gdb #22 on port 7022
> 0: system.remote_gdb.listener: listening for remote gdb #23 on port 7023
> 0: system.remote_gdb.listener: listening for remote gdb #24 on port 7024
> 0: system.remote_gdb.listener: listening for remote gdb #25 on port 7025
> 0: system.remote_gdb.listener: listening for remote gdb #26 on port 7026
> 0: system.remote_gdb.listener: listening for remote gdb #27 on port 7027
> 0: system.remote_gdb.listener: listening for remote gdb #28 on port 7028
> 0: system.remote_gdb.listener: listening for remote gdb #29 on port 7029
> 0: system.remote_gdb.listener: listening for remote gdb #30 on port 7030
> 0: system.remote_gdb.listener: listening for remote gdb #31 on port 7031
> **** REAL SIMULATION ****
> info: Entering event queue @ 0. Starting simulation...
> info: Launching CPU 1 @ 17640884000
> info: Launching CPU 2 @ 17802857000
> info: Launching CPU 3 @ 18137186000
> info: Launching CPU 4 @ 18646346000
> info: Launching CPU 5 @ 18808281000
> info: Launching CPU 6 @ 19142631000
> info: Launching CPU 7 @ 19651961000
> info: Launching CPU 8 @ 19813919000
> info: Launching CPU 9 @ 20148405000
> info: Launching CPU 10 @ 20664668000
> info: Launching CPU 11 @ 20833616000
> info: Launching CPU 12 @ 21002576000
> info: Launching CPU 13 @ 21532748000
> info: Launching CPU 14 @ 22063244000
> info: Launching CPU 15 @ 22232228000
> info: Launching CPU 16 @ 22401226000
> info: Launching CPU 17 @ 22931411000
> info: Launching CPU 18 @ 23279819000
> info: Launching CPU 19 @ 23628197000
> info: Launching CPU 20 @ 24158369000
> info: Launching CPU 21 @ 24327338000
> info: Launching CPU 22 @ 24675875000
> info: Launching CPU 23 @ 25024259000
> info: Launching CPU 24 @ 25372646000
> info: Launching CPU 25 @ 25721043000
> info: Launching CPU 26 @ 26069435000
> info: Launching CPU 27 @ 26599706000
> info: Launching CPU 28 @ 26768654000
> info: Launching CPU 29 @ 27117005000
> info: Launching CPU 30 @ 27465392000
> info: Launching CPU 31 @ 27813766000
> warn: Prefetch instructions in Alpha do not do anything
> warn: Prefetch instructions in Alpha do not do anything
> gem5.opt: build/ALPHA_FS/mem/bridge.cc:173: void
> Bridge::BridgePort::nackRequest(Packet*): Assertion `sendEvent.scheduled() ||
> inRetry' failed.
> Program aborted at cycle 971682745000
> Aborted (core dumped)
> [root@cxh gem5-09b482ee9ae0]#
>
> Note that I succeeded to run ALPHA_FS/gem5.opt with 16 cores.
> Thank you.
> best,
> Xuhao Chen
> -----------------------------------
> PhD student
> School of Computer
> National University of Defense Technology
> Changsha, Hunan, P.R.China, 410073
> Tel: +86-159-741-03340 (Mobile)
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
