Sun's JDK & Athlons

[Net Llama!]

Hi Pascal,
As usual, you hit the nail right on the head.  NPTL strikes again.  WHat 
caused it was me ditching Redhat's kernel for my own 2.4.26.  exporting 
LD_ASSUME_KERNEL=2.2.5 allows me to use java, but the performance is 
horrid.  Stupid java.

All of this mess is happening because i want/need XFS for the 
filesystem, and redhat's kernel doesn't have XFS support.  Now someone 
on the XFS list mentioned to me that 2.6.x kernels have NPTL by default, 
and have XFS too.  So i'm going to give that a try next, since it sounds 
like a solution to all of my problems.

argh.  i hate java.

thanks,
-Lonni

On 05/08/04 02:20, Chong Yu Meng wrote:
> Lonni,
> 
> I'm not clear on the details, because I don't use Sun's Java, but from 
> what I can remember from discussions on the Tomcat mailing list, Sun's 
> JDK (1.4) first had problems with NPTL, then it got fixed, then it broke 
> again for one release and then got fixed again.
> 
> Try setting LD_ASSUME_KERNEL=2.2.5. This may work, but may not be 
> optimal. Then try LD_ASSUME_KERNEL=2.4.1 and see if it works. 
> Alternatively, you can try using a newer version of Sun's 1.4.1 
> versions. You probably shouldn't use IBM's because of differences in the 
> class files.
> 
> It should not be a problem with the compiler, unless you are working 
> with source files instead of the compiled class files. Or if you are 
> using JSPs.
> 
> If you provided more information about the application (is it a web app 
> on Tomcat?) or the error, that might help.
> 
> Regards,
> pascal chong
> 
> 
> 
> Roger Oberholtzer wrote:
> 
>> I can say that I can run java 1.4.2-35 (from SUSE 9) on an Athlon XP-M
>> 2600+. I do not know about other version of java or other Athlon
>> processors.
>> java version "1.4.2"
>> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
>> Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)
>>
>>
>>
>>
>> On Fri, 2004-05-07 at 22:32, Net Llama! wrote:
>>  
>>
>>> I've got a real puzzler on my hands.  I've got these four shiny new dual
>>> Athlon servers.  I'm trying to use Sun's JDK-1.4.1_07 (unfortunately 
>>> Sun's
>>> is mandated for the application i'm forced to run), and it keeps 
>>> blowing up.
>>> Simply running 'java' results in a long series of errors that start 
>>> with:
>>> Unexpected Signal : 11 occurred at PC=0x0
>>>
>>> Running strace shows that its having trouble with some kind of compiler.
>>> This is happening on all four boxes, so i'm rather inclined to think it
>>> can't be a problem with the hardware, but perhaps some incompatibility
>>> between the JDK and Athlons.
>>>
>>> Has anyone else run into this before?  Any possible solutions?


-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman                       	       netllama at linux-sxs.org
Linux Step-by-step & TyGeMo: 		    http://netllama.ipfox.com

  07:45:01  up 153 days, 11:16,  1 user,  load average: 0.19, 0.08, 0.01