JDK-1.6.0_03-b05 (that's JDK 6, update 3 build 5) has all the
changes I know of for recent Intel chips.
I'm going to hope that the DTrace folks can figure this one
out. If they need help on the Java side of things I can help.
... peter
Naveen Nalam wrote:
>> Which version of the JRE are you running? I think older versions
>> of the logical processor code get confused on newer Intel processors.
>
> This is what I'm running at the moment:
>
> Compute server: Pentium D 3.2GHz, 8GB RAM, no dtrace problems:
> [EMAIL PROTECTED] /]# /usr/bin/java -version
> java version "1.6.0_03"
> Java(TM) SE Runtime Environment (build 1.6.0_03-b05)
> Java HotSpot(TM) Client VM (build 1.6.0_03-b05, mixed mode)
>
> Storage server: Core2Duo, 6GB RAM, has dtrace problems:
> [EMAIL PROTECTED] /]# /usr/bin/java -version
> java version "1.6.0_03"
> Java(TM) SE Runtime Environment (build 1.6.0_03-b05)
> Java HotSpot(TM) Server VM (build 1.6.0_03-b05, mixed mode)
>
>> Does "java -version" run on these storage servers, or does that hang
>> too? Or do you need DTrace on it to cause the problem? Do you have
>> any 3.2GHz Pentium D's that aren't in these storage servers? That is,
>> is it the processor or the machine configuration that's the problem.
>> I'll ask around and see if we have any of them in our labs.
>
> "java -version" runs on both the compute and storage server without
> any problems. things only hang on the storage server when running with
> the dtrace.
>
> all my Pentium D boxes are in compute servers. all my storage servers
> are Core2Duo based. I don't have any Pentium D based storage servers
> to test with.
>
> -Naveen
_______________________________________________
dtrace-discuss mailing list
[email protected]
