This content has been marked as final. Show 4 replies
what do you mean with 'crashes'? If you send me the complete Vdbench output directory to email@example.com I'll take a look at it.
Thanks so much Henk, I have sent you a mail. The output from the java interpreter was as follows:
stdout/stderr for slave=localhost-0
23:01:05.770 23:01:05.769 SlaveJvm execution parameter: '-m localhost'
23:01:05.771 23:01:05.770 SlaveJvm execution parameter: '-n localhost-10-110525-23.01.04.385'
23:01:05.771 23:01:05.770 SlaveJvm execution parameter: '-l localhost-0'
23:01:05.771 23:01:05.770 SlaveJvm execution parameter: '-p 5570'
23:01:05.771 23:01:05.770 SlaveJvm positional parameter: 'SlaveJvm'
23:01:05.812 23:01:05.812 successfully connected to master localhost
23:01:05.812 23:01:05.812 Connection to localhost using port 5570 successful
23:01:06.083 23:01:06.082 execute(): /home/vmdemo/tools/linux/linux_clock.suse
23:01:06.119 23:01:06.118 ticks_per_second: 100
23:01:06.124 23:01:06.123 Setting shared library to: /home/vmdemo/tools/linux/linux64.so
23:01:06.124 # A fatal error has been detected by the Java Runtime Environment:
23:01:06.124 # SIGSEGV (0xb) at pc=0x0000003290e79b60, pid=6371, tid=1089771840
23:01:06.124 # JRE version: 6.0_17-b17
23:01:06.125 # Java VM: OpenJDK 64-Bit Server VM (14.0-b16 mixed mode linux-amd64 )
23:01:06.125 # Derivative: IcedTea6 1.7.10
23:01:06.125 # Distribution: Custom build (Thu Apr 7 12:51:17 EDT 2011)
23:01:06.125 # Problematic frame:
23:01:06.125 # C [libc.so.6+0x79b60] strlen+0x10
23:01:06.125 # An error report file with more information is saved as:
23:01:06.125 # /home/vmdemo/tools/hs_err_pid6371.log
23:01:06.128 # If you would like to submit a bug report, please include
23:01:06.128 # instructions how to reproduce the bug and visit:
23:01:06.128 # http://icedtea.classpath.org/bugzilla
23:01:06.128 # The crash happened outside the Java Virtual Machine in native code.
23:01:06.129 # See problematic frame for where to report the bug.
We are using the IcedTea jdk, don't know if that matters - have seen problems before with IcedTea. We can always install the proper java jdk if needs be.
The opening of the raw device failed, causing Vdbench to use the strerror() function which likely returned a non-null terminated string, causing this failure. Problem is fixed in vdbench503rc11 from vdbench.org
Ultimately, this is a problem with writing to the device:
chmod 777 /dev/sda
fixes the problem
Edited by: user517177 on May 26, 2011 5:18 AM