[parsec-users] Errors running Parsec benchmarks in M5

ef snorlaxgb at gmail.com
Tue Aug 18 17:04:16 EDT 2009


Ok, i fixed the bug in streamcluster. I belive the bug was one the listed
above even though I am using GCC 4.3.2. For stream cluster I disabled
LDFLAGS path (didnt use shared and static libraries), I left it blank and
added the source code of pthread libaries...glibc2.9/nptl, and recompiled,
it now works.

I am tackling this new bug for Swaptions...any ideas?:
PARSEC Benchmark Suite Version 2.1
Number of Simulations: 5000,  Number of threads: 4 Number of swaptions: 16
*** glibc detected *** ./swaptions: double free or corruption (!prev)***
glibc detected *** ./swaptions: munmap_chunk(): invalid pointer:
0x0000020008002aa0 ***
: 0x0000020008001a10 ***
======= Backtrace: =========
======= Backtrace: =========
[0x1200ba6a8]
[0x1200ba6a8]
[0x1200bc1bc]
[0x1200bb984]
[0x1200bca0c]
[0x1200bc9a4]
[0x1200005fc]
[0x1200005fc]
[0x120004e70]
[0x120004e4c]
[0x12000b184]
[0x12000b184]
[0x12000c8b8]
[0xserial8250: too much work for irq4
12000c8b8]
[0x120078eb0]
[0x120078eb0]
[0x1200d6af8]
[0x1200d6af8]
======= Memory map: ========
======= Memory map: ========
11fee4000-11ff0e000 rwxp 11ffd6000 00:00 0
[stack]
120000000-120140000 r-xp 00000000 03:01 81928
/parsec/install/bin/swaptions
12014e000-120158000 rw-p 0013e000 03:01 81928
/parsec/install/bin/swaptions
120158000-120194000 rwxp 120158000 00:00 0
[heap]
20000000000-20000002000 rw-p 20000000000 00:00 0
20000002000-20000004000 ---p 20000002000 00:00 0
20000004000-20000802000 rwxp 20000004000 00:00 0
20000802000-20000804000 ---p 20000802000 00:00 0
20000804000-20001002000 rwxp 20000804000 00:00 0
20001002000-20001004000 ---p 20001002000 00:00 0
20001004000-20001802000 rwxp 20001004000 00:00 0
20001802000-20001804000 ---p 20001802000 00:00 0
20001804000-20002002000 rwxp 20001804000 00:00 0
20004000000-20004022000 rw-p 20004000000 00:00 0
20004022000-20008000000 ---p 20004022000 00:00 0
20008000000-20008022000 rw-p 20008000000 00:00 0
20008022000-2000c000000 ---p 20008022000 00:00 0
11fee4000-11ff0e000 rwxp 11ffd6000 00:00 0
[stack]
120000000-120140000 r-xp 00000000 03:01 81928
/parsec/install/bin/swaptions
12014e000-120158000 rw-p 0013e000 03:01 81928
/parsec/install/bin/swaptions
120158000-120194000 rwxp 120158000 00:00 0
[heap]
20000000000-20000002000 rw-p 20000000000 00:00 0
20000002000-20000004000 ---p 20000002000 00:00 0
20000004000-20000802000 rwxp 20000004000 00:00 0
20000802000-20000804000 ---p 20000802000 00:00 0
20000804000-20001002000 rwxp 20000804000 00:00 0
20001002000-20001004000 ---p 20001002000 00:00 0
20001004000-20001802000 rwxp 20001004000 00:00 0
20001802000-20001804000 ---p 20001802000 00:00 0
20001804000-20002002000 rwxp 20001804000 00:00 0
20004000000-20004022000 rw-p 20004000000 00:00 0
20004022000-20008000000 ---p 20004022000 00:00 0
20008000000-20008022000 rw-p 20008000000 00:00 0
20008022000-2000c000000 ---p 20008022000 00:00 0
Aborted



2009/8/18 Christian Bienia <cbienia at cs.princeton.edu>

>  Hi Ef,
>
>
>
> That looks very strange. The first error inside streamcluster happens
> inside the pthreads library. I don’t think it’s a bug in the program. There
> is however always the chance that it’s some sort of race condition and you
> just happen to discover it.
>
>
>
> The second bug in fluidanimate happens when the program writes its output
> to disk. That’s after the ROI has ended. You can check whether the error
> also happens if you disable disk output simply by removing the last argument
> for fluidanimate in the *.runconf file in the parsec/ directory of the
> package. It specifies the output file and if nothing is given then disk
> output is disabled. Since it’s not part of the ROI it won’t affect the
> characteristics as long as our guidelines are followed and only the ROI is
> measured.
>
>
>
> If you find out more please let me know. I’m willing to help debugging any
> issues that are found in the workloads themselves.
>
>
>
> - Chris
>
>
>
>
>
> *From:* parsec-users-bounces at lists.cs.princeton.edu [mailto:
> parsec-users-bounces at lists.cs.princeton.edu] *On Behalf Of *ef
> *Sent:* Tuesday, August 18, 2009 1:56 AM
> *To:* PARSEC Users
> *Subject:* [parsec-users] Errors running Parsec benchmarks in M5
>
>
>
> Hello,
>
> At the moment I am having difficulties on the following two benchmarks:
>
>
> For streamcluster I ran into the following issue:
> PARSEC Benchmark Suite Version 2.1
> read 4096 points
> streamcluster: pthread_mutex_lock.c:82: __pthread_mutex_lock: Assertion
> `mutex->__data.__owner == 0' failed.
> Aborted
>
> Any ideas on this? I noticed a bug here:
> http://gcc.gnu.org/ml/gcc-bugs/2006-10/msg00805.html
>
> I am not sure its revelant as I am running GCC 4.3.2.
>
>
>
> For Fluid Animate I am getting the following error:
> PARSEC Benchmark Suite Version 2.1
> Loading file "/parsec/install/inputs/fluidanimate/in_35K.fluid"...
> Number of cells: 36900
> Number of particles: 35402 (1102 skipped)
> Saving file "/parsec/install/inputs/fluidanimate/out.fluid"...
> Segmentation fault
>
> I am not to sure on this error, M5 does not allow real writes to the disk
> image, however it offers a "fake layer" COW where writes can be temporarily
> written too, I am not to sure this error is related to that, I need to do
> some further debugging but I don't think the ROI region is being executed.
> as it takes around 3 hours to get the segfault which is to fast.
>
> Any Ideas on this?
>
>
> Thanks,
> EF
>
> _______________________________________________
> parsec-users mailing list
> parsec-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/parsec-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cs.princeton.edu/pipermail/parsec-users/attachments/20090818/15f6d7d4/attachment.html>


More information about the parsec-users mailing list