Discussion:
[gem5-dev] X86 FS regression test fails on OSX with "Abort trap: 6" error
(too old to reply)
Cagdas Dirik (cdirik)
2015-06-30 19:05:58 UTC
Permalink
Hi all,

After recent updates to fix build on OSX, I gave a try to set up my gem5 development environment on OSX.
However using latest gem5 from dev branch, and running X86 and ARM regression tests, X86 full system tests are failing with "Abort trap: 6" right on/after "Initialization CPU#0".

The tests I am referring are:
build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-atomic
build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-timing

I don't have any idea where to start debugging. Does anyone have any idea what might be incompatible? Is this (running gem5 on OSX) a futile effort?

Thank you in advance!

Cagdas
Mitch Hayenga
2015-06-30 19:11:14 UTC
Permalink
On Tue, Jun 30, 2015 at 2:05 PM, Cagdas Dirik (cdirik) <***@micron.com>
wrote:

> Is this (running gem5 on OSX) a futile effort?



Unsure about the failure you're seeing, but running gem5 on OSX is not
futile at all. I've been doing so for the last 2 years just fine.
Periodically someone will break it by adding system calls OSX doesn't
support, but other than that it works just fine.
Nilay Vaish
2015-06-30 19:27:38 UTC
Permalink
On Tue, 30 Jun 2015, Mitch Hayenga wrote:

> On Tue, Jun 30, 2015 at 2:05 PM, Cagdas Dirik (cdirik) <***@micron.com>
> wrote:
>
>> Is this (running gem5 on OSX) a futile effort?
>
>
>
> Unsure about the failure you're seeing, but running gem5 on OSX is not
> futile at all. I've been doing so for the last 2 years just fine.
> Periodically someone will break it by adding system calls OSX doesn't
> support, but other than that it works just fine.


After reading some posts on stackoverflow, it seems you are getting a
sigabrt signal. A debugger should be able to help.

--
Nilay
Andreas Sandberg
2015-06-30 21:16:54 UTC
Permalink
On 30/06/2015 20:05, "Cagdas Dirik (cdirik)" <***@micron.com> wrote:

>Hi all,
>
>After recent updates to fix build on OSX, I gave a try to set up my gem5
>development environment on OSX.
>However using latest gem5 from dev branch, and running X86 and ARM
>regression tests, X86 full system tests are failing with "Abort trap: 6"
>right on/after "Initialization CPU#0".
>
>The tests I am referring are:
>build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-atomic
>build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-timing
>
>I don't have any idea where to start debugging. Does anyone have any idea
>what might be incompatible? Is this (running gem5 on OSX) a futile effort?

A SIGABRT typically means that gem5¹s internal checks failed. If you look
in the tests¹ build directories, you should find the output from the
simulator. Specifically, you¹re looking for simerr and simout. The former
should contain an error message that describes why the test case failed.

My guess is that you¹re missing one or more of the binaries to run the
tests.

//Andreas


-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
Cagdas Dirik (cdirik)
2015-06-30 22:13:49 UTC
Permalink
Thank you for suggestions Nilay and Andreas!

Andreas, I looked at the simerr and simout files, and there are no indications of a missing file. All kernel images and disk images are under $M5_PATH - I am basically using same set of files which pass regression tests under Linux. As a reference I pasted the outputs from those files at the end.

I did not find any "Initializing CPU#" messages from gem5, then I think I need to pinpoint the erroring module in the kernel.

I also tried kernel 2.6.26 and passing linux-x86.img file explicitly from command line to gem5 and got the same error message.

Cagdas

$ cat build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-atomic/simerr
warn: Sockets disabled, not accepting terminal connections
warn: Sockets disabled, not accepting gdb connections
warn: Reading current count from inactive timer.
warn: Don't know what interrupt to clear for console.

$ cat build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-atomic/simout
gem5 Simulator System. http://gem5.org
gem5 is copyrighted software; use the --copyright option for details.

gem5 compiled Jun 23 2015 13:44:27
gem5 started Jun 26 2015 10:14:40
gem5 executing on Cagdass-Mac-mini.local
command line: build/X86/gem5.opt -d build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-atomic -re /Users/cdirik/Projects/gem5/tests/run.py build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-atomic

Global frequency set at 1000000000000 ticks per second
info: kernel located at: /Users/cdirik/Projects/gem5-files/dist/m5/system/binaries/x86_64-vmlinux-2.6.22.9
0: rtc: Real-time clock set to Sun Jan 1 00:00:00 2012
info: Entering event queue @ 0. Starting simulation...

________________________________________
From: gem5-dev [gem5-dev-***@gem5.org] on behalf of Andreas Sandberg [***@arm.com]
Sent: Tuesday, June 30, 2015 2:16 PM
To: gem5 Developer List
Subject: Re: [gem5-dev] X86 FS regression test fails on OSX with "Abort trap: 6" error

On 30/06/2015 20:05, "Cagdas Dirik (cdirik)" <***@micron.com> wrote:

>Hi all,
>
>After recent updates to fix build on OSX, I gave a try to set up my gem5
>development environment on OSX.
>However using latest gem5 from dev branch, and running X86 and ARM
>regression tests, X86 full system tests are failing with "Abort trap: 6"
>right on/after "Initialization CPU#0".
>
>The tests I am referring are:
>build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-atomic
>build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-timing
>
>I don't have any idea where to start debugging. Does anyone have any idea
>what might be incompatible? Is this (running gem5 on OSX) a futile effort?

A SIGABRT typically means that gem5¹s internal checks failed. If you look
in the tests¹ build directories, you should find the output from the
simulator. Specifically, you¹re looking for simerr and simout. The former
should contain an error message that describes why the test case failed.

My guess is that you¹re missing one or more of the binaries to run the
tests.

//Andreas


-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782

_______________________________________________
gem5-dev mailing list
gem5-***@gem5.org
http://m5sim.org/mailman/listinfo/gem5-dev
Andreas Sandberg
2015-07-06 13:40:31 UTC
Permalink
Cagdas,

I just tried to run the quick x86 regressions using a gem5 compiled with
clang 3.5 on Linux and ran into a similar problem. In my case, the tests
segfault, but all the other symptoms seem identical. An interesting
observation is that /all/ the other backends run their quick regressions
just fine, so I'm inclined to say that this is an x86-specific issue
that is triggered by clang (I'm assuming you're using clang since you're
on MacOS).

//Andreas

On 30/06/2015 23:13, Cagdas Dirik (cdirik) wrote:
> Thank you for suggestions Nilay and Andreas!
>
> Andreas, I looked at the simerr and simout files, and there are no indications of a missing file. All kernel images and disk images are under $M5_PATH - I am basically using same set of files which pass regression tests under Linux. As a reference I pasted the outputs from those files at the end.
>
> I did not find any "Initializing CPU#" messages from gem5, then I think I need to pinpoint the erroring module in the kernel.
>
> I also tried kernel 2.6.26 and passing linux-x86.img file explicitly from command line to gem5 and got the same error message.
>
> Cagdas
>
> $ cat build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-atomic/simerr
> warn: Sockets disabled, not accepting terminal connections
> warn: Sockets disabled, not accepting gdb connections
> warn: Reading current count from inactive timer.
> warn: Don't know what interrupt to clear for console.
>
> $ cat build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-atomic/simout
> gem5 Simulator System. http://gem5.org
> gem5 is copyrighted software; use the --copyright option for details.
>
> gem5 compiled Jun 23 2015 13:44:27
> gem5 started Jun 26 2015 10:14:40
> gem5 executing on Cagdass-Mac-mini.local
> command line: build/X86/gem5.opt -d build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-atomic -re /Users/cdirik/Projects/gem5/tests/run.py build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-atomic
>
> Global frequency set at 1000000000000 ticks per second
> info: kernel located at: /Users/cdirik/Projects/gem5-files/dist/m5/system/binaries/x86_64-vmlinux-2.6.22.9
> 0: rtc: Real-time clock set to Sun Jan 1 00:00:00 2012
> info: Entering event queue @ 0. Starting simulation...
>
> ________________________________________
> From: gem5-dev [gem5-dev-***@gem5.org] on behalf of Andreas Sandberg [***@arm.com]
> Sent: Tuesday, June 30, 2015 2:16 PM
> To: gem5 Developer List
> Subject: Re: [gem5-dev] X86 FS regression test fails on OSX with "Abort trap: 6" error
>
> On 30/06/2015 20:05, "Cagdas Dirik (cdirik)" <***@micron.com> wrote:
>
>> Hi all,
>>
>> After recent updates to fix build on OSX, I gave a try to set up my gem5
>> development environment on OSX.
>> However using latest gem5 from dev branch, and running X86 and ARM
>> regression tests, X86 full system tests are failing with "Abort trap: 6"
>> right on/after "Initialization CPU#0".
>>
>> The tests I am referring are:
>> build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-atomic
>> build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-timing
>>
>> I don't have any idea where to start debugging. Does anyone have any idea
>> what might be incompatible? Is this (running gem5 on OSX) a futile effort?
> A SIGABRT typically means that gem5¹s internal checks failed. If you look
> in the tests¹ build directories, you should find the output from the
> simulator. Specifically, you¹re looking for simerr and simout. The former
> should contain an error message that describes why the test case failed.
>
> My guess is that you¹re missing one or more of the binaries to run the
> tests.
>
> //Andreas
>
>
> -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
>
> ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590
> ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
>
> _______________________________________________
> gem5-dev mailing list
> gem5-***@gem5.org
> http://m5sim.org/mailman/listinfo/gem5-dev
> _______________________________________________
> gem5-dev mailing list
> gem5-***@gem5.org
> http://m5sim.org/mailman/listinfo/gem5-dev


-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
Cagdas Dirik (cdirik)
2015-07-06 16:14:31 UTC
Permalink
Thank you for reproducing the issue Andreas!

Any suggestions on how to get to the core of it? I have not gotten an attack plan yet, so open to any recommendations ;)

Cagdas

-----Original Message-----
From: gem5-dev [mailto:gem5-dev-***@gem5.org] On Behalf Of Andreas Sandberg
Sent: Monday, July 06, 2015 6:41 AM
To: gem5 Developer List
Subject: Re: [gem5-dev] X86 FS regression test fails on OSX with "Abort trap: 6" error

Cagdas,

I just tried to run the quick x86 regressions using a gem5 compiled with clang 3.5 on Linux and ran into a similar problem. In my case, the tests segfault, but all the other symptoms seem identical. An interesting observation is that /all/ the other backends run their quick regressions just fine, so I'm inclined to say that this is an x86-specific issue that is triggered by clang (I'm assuming you're using clang since you're on MacOS).

//Andreas

On 30/06/2015 23:13, Cagdas Dirik (cdirik) wrote:
> Thank you for suggestions Nilay and Andreas!
>
> Andreas, I looked at the simerr and simout files, and there are no indications of a missing file. All kernel images and disk images are under $M5_PATH - I am basically using same set of files which pass regression tests under Linux. As a reference I pasted the outputs from those files at the end.
>
> I did not find any "Initializing CPU#" messages from gem5, then I think I need to pinpoint the erroring module in the kernel.
>
> I also tried kernel 2.6.26 and passing linux-x86.img file explicitly from command line to gem5 and got the same error message.
>
> Cagdas
>
> $ cat
> build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-atomic/
> simerr
> warn: Sockets disabled, not accepting terminal connections
> warn: Sockets disabled, not accepting gdb connections
> warn: Reading current count from inactive timer.
> warn: Don't know what interrupt to clear for console.
>
> $ cat
> build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-atomic/
> simout
> gem5 Simulator System. http://gem5.org
> gem5 is copyrighted software; use the --copyright option for details.
>
> gem5 compiled Jun 23 2015 13:44:27
> gem5 started Jun 26 2015 10:14:40
> gem5 executing on Cagdass-Mac-mini.local command line:
> build/X86/gem5.opt -d
> build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-atomic
> -re /Users/cdirik/Projects/gem5/tests/run.py
> build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-atomic
>
> Global frequency set at 1000000000000 ticks per second
> info: kernel located at: /Users/cdirik/Projects/gem5-files/dist/m5/system/binaries/x86_64-vmlinux-2.6.22.9
> 0: rtc: Real-time clock set to Sun Jan 1 00:00:00 2012
> info: Entering event queue @ 0. Starting simulation...
>
> ________________________________________
> From: gem5-dev [gem5-dev-***@gem5.org] on behalf of Andreas
> Sandberg [***@arm.com]
> Sent: Tuesday, June 30, 2015 2:16 PM
> To: gem5 Developer List
> Subject: Re: [gem5-dev] X86 FS regression test fails on OSX with
> "Abort trap: 6" error
>
> On 30/06/2015 20:05, "Cagdas Dirik (cdirik)" <***@micron.com> wrote:
>
>> Hi all,
>>
>> After recent updates to fix build on OSX, I gave a try to set up my
>> gem5 development environment on OSX.
>> However using latest gem5 from dev branch, and running X86 and ARM
>> regression tests, X86 full system tests are failing with "Abort trap: 6"
>> right on/after "Initialization CPU#0".
>>
>> The tests I am referring are:
>> build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-atomic
>> build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-timing
>>
>> I don't have any idea where to start debugging. Does anyone have any
>> idea what might be incompatible? Is this (running gem5 on OSX) a futile effort?
> A SIGABRT typically means that gem5¹s internal checks failed. If you
> look in the tests¹ build directories, you should find the output from
> the simulator. Specifically, you¹re looking for simerr and simout. The
> former should contain an error message that describes why the test case failed.
>
> My guess is that you¹re missing one or more of the binaries to run the
> tests.
>
> //Andreas
>
>
> -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
>
> ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ,
> Registered in England & Wales, Company No: 2557590 ARM Holdings plc,
> Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in
> England & Wales, Company No: 2548782
>
> _______________________________________________
> gem5-dev mailing list
> gem5-***@gem5.org
> http://m5sim.org/mailman/listinfo/gem5-dev
> _______________________________________________
> gem5-dev mailing list
> gem5-***@gem5.org
> http://m5sim.org/mailman/listinfo/gem5-dev


-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782

_______________________________________________
gem5-dev mailing list
gem5-***@gem5.org
http://m5sim.org/mailman/listinfo/gem5-dev
Loading...