Re: [gem5-users] derivo3cpu issue

2019-11-22 Thread Abhishek Singh 
Hi,
Where did you get the config file from?
Also can you run gdb and send us the backtrace?

On Fri, Nov 22, 2019 at 9:21 PM ABD ALRHMAN ABO ALKHEEL <
abdkeel...@hotmail.com> wrote:

> Global frequency set at 1 ticks per second
> warn: DRAM device capacity (8192 Mbytes) does not match the address range
> assigned (16384 Mbytes)
> 0: system.remote_gdb: listening for remote gdb on port 7000
> info: Entering event queue @ 0.  Starting simulation...
>  REAL SIMULATION 
> info: Increasing stack size by one page.
> warn: ignoring syscall access(...)
> warn: MOVNTDQ: Ignoring non-temporal hint, modeling as cacheable!
> info: Increasing stack size by one page.
> info: Increasing stack size by one page.
> info: Increasing stack size by one page.
> info: Increasing stack size by one page.
> info: Increasing stack size by one page.
> gem5 has encountered a segmentation fault!
>
> --- BEGIN LIBC BACKTRACE ---
>
> /home/abdkhail/aa/gem5/build/X86/gem5.opt(_Z15print_backtracev+0x2c)[0x55cda9d47dac]
> /home/abdkhail/aa/gem5/build/X86/gem5.opt(+0x584e7f)[0x55cda9d59e7f]
> /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7f77bb174890]
> /lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Resume+0xcf)[0x7f77b9b137df]
>
> /home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN6X86ISA7Decoder10decodeInstENS_11ExtMachInstE+0x4e609)[0x55cda9ee8659]
>
> /home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN6X86ISA7Decoder6decodeENS_11ExtMachInstEm+0x244)[0x55cda9e63db4]
> Command: /home/abdkhail/aa/gem5/build/X86/gem5.opt
> --outdir=/home/abdkhail/aa/gem5/o1
> /home/abdkhail/aa/gem5/configs/example/spec06_config.py -I 10
> --benchmark=povray --benchmark_stdout=/home/abdkhail/aa/gem5/o1/povray.out
> --benchmark_stderr=/home/abdkhail/aa/gem5/o1/povray.err
> --cpu-type=DerivO3CPU --caches
> --
> *From:* gem5-users  on behalf of Abhishek
> Singh 
> *Sent:* Friday, November 22, 2019 11:11:38 PM
> *To:* gem5 users mailing list 
> *Cc:* gem5-users 
> *Subject:* Re: [gem5-users] derivo3cpu issue
>
> Hey,
> What is the error and what is the command line?
> Can you run gdb and paste the back trace?
> Did you made any changes to baseline gem5?
>
> On Fri, Nov 22, 2019 at 5:54 PM ABD ALRHMAN ABO ALKHEEL <
> abdkeel...@hotmail.com> wrote:
>
> Hello everyone, I am running the benchmark on gem5 and I got error when I
> use derivo3cpu . I have to use it so how I can fix the issue?
> ___
> gem5-users mailing list
> gem5-users@gem5.org
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>
> ___
> gem5-users mailing list
> gem5-users@gem5.org
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Re: [gem5-users] derivo3cpu issue

2019-11-22 Thread ABD ALRHMAN ABO ALKHEEL 
Global frequency set at 1 ticks per second
warn: DRAM device capacity (8192 Mbytes) does not match the address range 
assigned (16384 Mbytes)
0: system.remote_gdb: listening for remote gdb on port 7000
info: Entering event queue @ 0.  Starting simulation...
 REAL SIMULATION 
info: Increasing stack size by one page.
warn: ignoring syscall access(...)
warn: MOVNTDQ: Ignoring non-temporal hint, modeling as cacheable!
info: Increasing stack size by one page.
info: Increasing stack size by one page.
info: Increasing stack size by one page.
info: Increasing stack size by one page.
info: Increasing stack size by one page.
gem5 has encountered a segmentation fault!

--- BEGIN LIBC BACKTRACE ---
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_Z15print_backtracev+0x2c)[0x55cda9d47dac]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(+0x584e7f)[0x55cda9d59e7f]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7f77bb174890]
/lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Resume+0xcf)[0x7f77b9b137df]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN6X86ISA7Decoder10decodeInstENS_11ExtMachInstE+0x4e609)[0x55cda9ee8659]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN6X86ISA7Decoder6decodeENS_11ExtMachInstEm+0x244)[0x55cda9e63db4]
Command: /home/abdkhail/aa/gem5/build/X86/gem5.opt 
--outdir=/home/abdkhail/aa/gem5/o1 
/home/abdkhail/aa/gem5/configs/example/spec06_config.py -I 10 
--benchmark=povray --benchmark_stdout=/home/abdkhail/aa/gem5/o1/povray.out 
--benchmark_stderr=/home/abdkhail/aa/gem5/o1/povray.err --cpu-type=DerivO3CPU 
--caches

From: gem5-users  on behalf of Abhishek Singh 

Sent: Friday, November 22, 2019 11:11:38 PM
To: gem5 users mailing list 
Cc: gem5-users 
Subject: Re: [gem5-users] derivo3cpu issue

Hey,
What is the error and what is the command line?
Can you run gdb and paste the back trace?
Did you made any changes to baseline gem5?

On Fri, Nov 22, 2019 at 5:54 PM ABD ALRHMAN ABO ALKHEEL 
mailto:abdkeel...@hotmail.com>> wrote:
Hello everyone, I am running the benchmark on gem5 and I got error when I use 
derivo3cpu . I have to use it so how I can fix the issue?
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Re: [gem5-users] derivo3cpu issue

2019-11-22 Thread Abhishek Singh 
Hey,
What is the error and what is the command line?
Can you run gdb and paste the back trace?
Did you made any changes to baseline gem5?

On Fri, Nov 22, 2019 at 5:54 PM ABD ALRHMAN ABO ALKHEEL <
abdkeel...@hotmail.com> wrote:

> Hello everyone, I am running the benchmark on gem5 and I got error when I
> use derivo3cpu . I have to use it so how I can fix the issue?
> ___
> gem5-users mailing list
> gem5-users@gem5.org
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

[gem5-users] derivo3cpu issue

2019-11-22 Thread ABD ALRHMAN ABO ALKHEEL 
Hello everyone, I am running the benchmark on gem5 and I got error when I use 
derivo3cpu . I have to use it so how I can fix the issue?
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Re: [gem5-users] gem5 has encountered a segmentation fault!

2019-11-22 Thread ABD ALRHMAN ABO ALKHEEL 
Thanks Gerzhoy for your email.

The code is attached here. I got the error for some of benchmarks not for all.

I used this command to run the code
/home/abdkhail/aa/gem5/build/X86/gem5.opt --outdir=/home/abdkhail/aa/gem5/o1 
/home/abdkhail/aa/gem5/configs/example/spec06_config.py -I 10 
--benchmark=povray --benchmark_stdout=/home/abdkhail/aa/gem5/o1/povray.out 
--benchmark_stderr=/home/abdkhail/aa/gem5/o1/povray.err --cpu-type=DerivO3CPU 
--caches

I observed when i changed --cpu-type=DerivO3CPU  to another CPU type it is 
working fine but i have to get the stats output of this type 
--cpu-type=DerivO3CPU .

Best Regards


From: gem5-users  on behalf of Daniel Gerzhoy 

Sent: Friday, November 22, 2019 7:05 PM
To: gem5 users mailing list 
Subject: Re: [gem5-users] gem5 has encountered a segmentation fault!

It looks like gem5 itself had a segfault.

Did you change the simulator code itself?
If so I would look at whatever code you added to see if you referenced a memory 
address you don't actually have access to.

You could run the simulator in GDB as well and add breakpoints to debug further.

best regards,

Dan Gerzhoy

On Fri, Nov 22, 2019 at 1:55 PM ABD ALRHMAN ABO ALKHEEL 
mailto:abdkeel...@hotmail.com>> wrote:
Hello Everyone,

I am currently working on running the benchmark on gem5 and some of them gave 
me the below error.

Any help in this regard? I would really appreciate  that.


Best Regards





Global frequency set at 1 ticks per second
warn: DRAM device capacity (8192 Mbytes) does not match the address range 
assigned (16384 Mbytes)
0: system.remote_gdb: listening for remote gdb on port 7000
info: Entering event queue @ 0.  Starting simulation...
 REAL SIMULATION 
info: Increasing stack size by one page.
warn: ignoring syscall access(...)
warn: MOVNTDQ: Ignoring non-temporal hint, modeling as cacheable!
info: Increasing stack size by one page.
info: Increasing stack size by one page.
info: Increasing stack size by one page.
info: Increasing stack size by one page.
info: Increasing stack size by one page.
gem5 has encountered a segmentation fault!

--- BEGIN LIBC BACKTRACE ---
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_Z15print_backtracev+0x2c)[0x55cda9d47dac]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(+0x584e7f)[0x55cda9d59e7f]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7f77bb174890]
/lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Resume+0xcf)[0x7f77b9b137df]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN6X86ISA7Decoder10decodeInstENS_11ExtMachInstE+0x4e609)[0x55cda9ee8659]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN6X86ISA7Decoder6decodeENS_11ExtMachInstEm+0x244)[0x55cda9e63db4]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN6X86ISA7Decoder6decodeERNS_7PCStateE+0x237)[0x55cda9e640b7]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN12DefaultFetchI9O3CPUImplE5fetchERb+0x941)[0x55cdaaa51301]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN12DefaultFetchI9O3CPUImplE4tickEv+0xcb)[0x55cdaaa5235b]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN9FullO3CPUI9O3CPUImplE4tickEv+0x12b)[0x55cdaaa349ab]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN10EventQueue10serviceOneEv+0xd9)[0x55cda9d4ffb9]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_Z9doSimLoopP10EventQueue+0x87)[0x55cda9d708b7]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_Z8simulatem+0xcba)[0x55cda9d7190a]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(+0xd4ea5e)[0x55cdaa523a5e]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(+0x5e6954)[0x55cda9dbb954]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x5f82)[0x7f77bb42e522]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f77bb560bf8]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6364)[0x7f77bb42e904]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f77bb560bf8]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6364)[0x7f77bb42e904]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f77bb560bf8]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6364)[0x7f77bb42e904]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f77bb560bf8]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19)[0x7f77bb428409]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x68a5)[0x7f77bb42ee45]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f77bb560bf8]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6364)[0x7f77bb42e904]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f77bb560bf8]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19)[0x7f77bb428409]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyRun_StringFlags+0x76)[0x7f77bb4d86d6]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_Z6m5MainiPPc+0x83)[0x55cda9d58a43]
/home/abdkhail/aa/gem5/
___
gem5-users mailing list
gem5

Re: [gem5-users] gem5 has encountered a segmentation fault!

2019-11-22 Thread Daniel Gerzhoy 
It looks like gem5 itself had a segfault.

Did you change the simulator code itself?
If so I would look at whatever code you added to see if you referenced a
memory address you don't actually have access to.

You could run the simulator in GDB as well and add breakpoints to debug
further.

best regards,

Dan Gerzhoy

On Fri, Nov 22, 2019 at 1:55 PM ABD ALRHMAN ABO ALKHEEL <
abdkeel...@hotmail.com> wrote:

> Hello Everyone,
>
> I am currently working on running the benchmark on gem5 and some of them
> gave me the below error.
>
> Any help in this regard? I would really appreciate  that.
>
>
> Best Regards
>
>
>
>
>
> Global frequency set at 1 ticks per second
> warn: DRAM device capacity (8192 Mbytes) does not match the address range
> assigned (16384 Mbytes)
> 0: system.remote_gdb: listening for remote gdb on port 7000
> info: Entering event queue @ 0.  Starting simulation...
>  REAL SIMULATION 
> info: Increasing stack size by one page.
> warn: ignoring syscall access(...)
> warn: MOVNTDQ: Ignoring non-temporal hint, modeling as cacheable!
> info: Increasing stack size by one page.
> info: Increasing stack size by one page.
> info: Increasing stack size by one page.
> info: Increasing stack size by one page.
> info: Increasing stack size by one page.
> gem5 has encountered a segmentation fault!
>
> --- BEGIN LIBC BACKTRACE ---
>
> /home/abdkhail/aa/gem5/build/X86/gem5.opt(_Z15print_backtracev+0x2c)[0x55cda9d47dac]
> /home/abdkhail/aa/gem5/build/X86/gem5.opt(+0x584e7f)[0x55cda9d59e7f]
> /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7f77bb174890]
> /lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Resume+0xcf)[0x7f77b9b137df]
>
> /home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN6X86ISA7Decoder10decodeInstENS_11ExtMachInstE+0x4e609)[0x55cda9ee8659]
>
> /home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN6X86ISA7Decoder6decodeENS_11ExtMachInstEm+0x244)[0x55cda9e63db4]
>
> /home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN6X86ISA7Decoder6decodeERNS_7PCStateE+0x237)[0x55cda9e640b7]
>
> /home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN12DefaultFetchI9O3CPUImplE5fetchERb+0x941)[0x55cdaaa51301]
>
> /home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN12DefaultFetchI9O3CPUImplE4tickEv+0xcb)[0x55cdaaa5235b]
>
> /home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN9FullO3CPUI9O3CPUImplE4tickEv+0x12b)[0x55cdaaa349ab]
>
> /home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN10EventQueue10serviceOneEv+0xd9)[0x55cda9d4ffb9]
>
> /home/abdkhail/aa/gem5/build/X86/gem5.opt(_Z9doSimLoopP10EventQueue+0x87)[0x55cda9d708b7]
>
> /home/abdkhail/aa/gem5/build/X86/gem5.opt(_Z8simulatem+0xcba)[0x55cda9d7190a]
> /home/abdkhail/aa/gem5/build/X86/gem5.opt(+0xd4ea5e)[0x55cdaa523a5e]
> /home/abdkhail/aa/gem5/build/X86/gem5.opt(+0x5e6954)[0x55cda9dbb954]
>
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x5f82)[0x7f77bb42e522]
>
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f77bb560bf8]
>
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6364)[0x7f77bb42e904]
>
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f77bb560bf8]
>
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6364)[0x7f77bb42e904]
>
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f77bb560bf8]
>
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6364)[0x7f77bb42e904]
>
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f77bb560bf8]
>
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19)[0x7f77bb428409]
>
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x68a5)[0x7f77bb42ee45]
>
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f77bb560bf8]
>
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6364)[0x7f77bb42e904]
>
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f77bb560bf8]
>
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19)[0x7f77bb428409]
>
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyRun_StringFlags+0x76)[0x7f77bb4d86d6]
>
> /home/abdkhail/aa/gem5/build/X86/gem5.opt(_Z6m5MainiPPc+0x83)[0x55cda9d58a43]
> /home/abdkhail/aa/gem5/
> ___
> gem5-users mailing list
> gem5-users@gem5.org
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

[gem5-users] gem5 has encountered a segmentation fault!

2019-11-22 Thread ABD ALRHMAN ABO ALKHEEL 
Hello Everyone,

I am currently working on running the benchmark on gem5 and some of them gave 
me the below error.

Any help in this regard? I would really appreciate  that.


Best Regards





Global frequency set at 1 ticks per second
warn: DRAM device capacity (8192 Mbytes) does not match the address range 
assigned (16384 Mbytes)
0: system.remote_gdb: listening for remote gdb on port 7000
info: Entering event queue @ 0.  Starting simulation...
 REAL SIMULATION 
info: Increasing stack size by one page.
warn: ignoring syscall access(...)
warn: MOVNTDQ: Ignoring non-temporal hint, modeling as cacheable!
info: Increasing stack size by one page.
info: Increasing stack size by one page.
info: Increasing stack size by one page.
info: Increasing stack size by one page.
info: Increasing stack size by one page.
gem5 has encountered a segmentation fault!

--- BEGIN LIBC BACKTRACE ---
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_Z15print_backtracev+0x2c)[0x55cda9d47dac]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(+0x584e7f)[0x55cda9d59e7f]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7f77bb174890]
/lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Resume+0xcf)[0x7f77b9b137df]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN6X86ISA7Decoder10decodeInstENS_11ExtMachInstE+0x4e609)[0x55cda9ee8659]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN6X86ISA7Decoder6decodeENS_11ExtMachInstEm+0x244)[0x55cda9e63db4]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN6X86ISA7Decoder6decodeERNS_7PCStateE+0x237)[0x55cda9e640b7]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN12DefaultFetchI9O3CPUImplE5fetchERb+0x941)[0x55cdaaa51301]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN12DefaultFetchI9O3CPUImplE4tickEv+0xcb)[0x55cdaaa5235b]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN9FullO3CPUI9O3CPUImplE4tickEv+0x12b)[0x55cdaaa349ab]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_ZN10EventQueue10serviceOneEv+0xd9)[0x55cda9d4ffb9]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_Z9doSimLoopP10EventQueue+0x87)[0x55cda9d708b7]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_Z8simulatem+0xcba)[0x55cda9d7190a]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(+0xd4ea5e)[0x55cdaa523a5e]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(+0x5e6954)[0x55cda9dbb954]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x5f82)[0x7f77bb42e522]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f77bb560bf8]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6364)[0x7f77bb42e904]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f77bb560bf8]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6364)[0x7f77bb42e904]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f77bb560bf8]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6364)[0x7f77bb42e904]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f77bb560bf8]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19)[0x7f77bb428409]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x68a5)[0x7f77bb42ee45]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f77bb560bf8]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6364)[0x7f77bb42e904]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8)[0x7f77bb560bf8]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19)[0x7f77bb428409]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyRun_StringFlags+0x76)[0x7f77bb4d86d6]
/home/abdkhail/aa/gem5/build/X86/gem5.opt(_Z6m5MainiPPc+0x83)[0x55cda9d58a43]
/home/abdkhail/aa/gem5/
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Re: [gem5-users] AMD GPU compute model run fail

2019-11-22 Thread ABD ALRHMAN ABO ALKHEEL 
I got this error ( gem5 has segmentation faults) please help me.

From: gem5-users  on behalf of Matt Sinclair 

Sent: Friday, November 22, 2019 3:48:21 PM
To: gem5 users mailing list 
Subject: Re: [gem5-users] AMD GPU compute model run fail

Hi Andrew,

Normally this error indicates that something with your ROCm setup is wrong -- 
you can look through the mailing list archive and see a few examples of people 
with the same types of errors along with the suggestions (e.g., what kind of 
traces) to get to start debugging the problem.  Why did you install ROCm 1.6.1? 
 If you look at the wiki, AMD suggests using 1.6.x instead: 
http://gem5.org/GPU_Models#ROCm_tool_chain_and_software_stack.  I can't promise 
that changing from 1.6.1 to 1.6.x will solve your problem, but it would be a 
good start/thing to check.  Also, I'm not familiar with this sample program -- 
does it assume the device is a discrete GPU?  If so, the gem5 AMD GPU model 
assumes the GPU is tightly coupled and cache coherent.  So you would need to 
remove those copies (although it appears your failure is happening sooner than 
that).

Thanks,
Matt

On Fri, Nov 15, 2019 at 2:17 AM Andrew Chu 
mailto:chuchih...@gmail.com>> wrote:
I got a GEM5 fatal error which syscall mincore was not implemented. Does anyone 
have the same experience about this?

=

Environment setting:
Host OS: Ubuntu 16.04.6 LTS
GEM5: git clone https://gem5.googlesource.com/amd/gem5 -b 
agutierr/master-gcn3-staging
ROCM: http://repo.radeon.com/rocm/archive/apt_1.6.1.tar.bz2
SE test program: 
https://github.com/ROCm-Developer-Tools/HIP-Examples/tree/master/HIP-Examples-Applications/HelloWorld
 with HIP_PLATFORM=hcc
CMD: ./build/GCN3_X86/gem5.opt --debug-flag=GPUALL configs/example/apu_se.py -n 
2 -c tests/test-progs/hip-hello/HelloWorld
Result:
.
.
.
warn: ignoring syscall sched_yield(...)
warn: ignoring syscall sched_yield(...)
warn: ignoring syscall sched_yield(...)
warn: ignoring syscall sched_yield(...)
warn: ignoring syscall sched_yield(...)
warn: ignoring syscall sched_yield(...)
warn: ignoring syscall sched_yield(...)
warn: ignoring syscall sched_yield(...)
warn: ignoring syscall sched_yield(...)
warn: ignoring syscall sched_yield(...)
warn: ignoring syscall sched_yield(...)
warn: ignoring syscall sched_yield(...)
warn: ignoring syscall sched_yield(...)
warn: ignoring syscall sched_yield(...)
warn: ignoring syscall sched_yield(...)
fatal: syscall mincore (#27) unimplemented.

===

Once I ignore this system call, the test program will have run time error

warn: ignoring syscall mincore(...)
warn: ignoring syscall mincore(...)

Backtrace:
0x0040d941:  + 0x5
0x0040dc50:  + 0x5
0x0040db09:  + 0x5
0x00426bdd:  + 0x5
0x75f517bf:  + 0x5
0x0041b509:  + 0x5

### HCC RUNTIME ERROR: Fail to find compatible kernel at 
file:/home/jenkins/jenkins-root/workspace/compute-rocm-rel-1.6/external/hcc-tot/lib/mcwamp.cpp
 line:346
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Re: [gem5-users] AMD GPU compute model run fail

2019-11-22 Thread Matt Sinclair 
Hi Andrew,

Normally this error indicates that something with your ROCm setup is wrong
-- you can look through the mailing list archive and see a few examples of
people with the same types of errors along with the suggestions (e.g., what
kind of traces) to get to start debugging the problem.  Why did you install
ROCm 1.6.1?  If you look at the wiki, AMD suggests using 1.6.x instead:
http://gem5.org/GPU_Models#ROCm_tool_chain_and_software_stack.  I can't
promise that changing from 1.6.1 to 1.6.x will solve your problem, but it
would be a good start/thing to check.  Also, I'm not familiar with this
sample program -- does it assume the device is a discrete GPU?  If so, the
gem5 AMD GPU model assumes the GPU is tightly coupled and cache coherent.
So you would need to remove those copies (although it appears your failure
is happening sooner than that).

Thanks,
Matt

On Fri, Nov 15, 2019 at 2:17 AM Andrew Chu  wrote:

> I got a GEM5 fatal error which syscall mincore was not implemented. Does
> anyone have the same experience about this?
>
> =
>
> Environment setting:
> Host OS: Ubuntu 16.04.6 LTS
> GEM5: git clone https://gem5.googlesource.com/amd/gem5
> -b agutierr/master-gcn3-staging
> ROCM: http://repo.radeon.com/rocm/archive/apt_1.6.1.tar.bz2
> SE test program:
> https://github.com/ROCm-Developer-Tools/HIP-Examples/tree/master/HIP-Examples-Applications/HelloWorld
> with HIP_PLATFORM=hcc
> CMD: ./build/GCN3_X86/gem5.opt --debug-flag=GPUALL
> configs/example/apu_se.py -n 2 -c tests/test-progs/hip-hello/HelloWorld
> Result:
> .
> .
> .
> warn: ignoring syscall sched_yield(...)
> warn: ignoring syscall sched_yield(...)
> warn: ignoring syscall sched_yield(...)
> warn: ignoring syscall sched_yield(...)
> warn: ignoring syscall sched_yield(...)
> warn: ignoring syscall sched_yield(...)
> warn: ignoring syscall sched_yield(...)
> warn: ignoring syscall sched_yield(...)
> warn: ignoring syscall sched_yield(...)
> warn: ignoring syscall sched_yield(...)
> warn: ignoring syscall sched_yield(...)
> warn: ignoring syscall sched_yield(...)
> warn: ignoring syscall sched_yield(...)
> warn: ignoring syscall sched_yield(...)
> warn: ignoring syscall sched_yield(...)
> fatal: syscall mincore (#27) unimplemented.
>
> ===
>
> Once I ignore this system call, the test program will have run time error
>
> warn: ignoring syscall mincore(...)
> warn: ignoring syscall mincore(...)
>
> Backtrace:
> 0x0040d941:  + 0x5
> 0x0040dc50:  + 0x5
> 0x0040db09:  + 0x5
> 0x00426bdd:  + 0x5
> 0x75f517bf:  + 0x5
> 0x0041b509:  + 0x5
>
> ### HCC RUNTIME ERROR: Fail to find compatible kernel at
> file:/home/jenkins/jenkins-root/workspace/compute-rocm-rel-1.6/external/hcc-tot/lib/mcwamp.cpp
> line:346
> ___
> gem5-users mailing list
> gem5-users@gem5.org
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users