Removing JDK completely ?

[Nicolas Gieczewski]

I forgot to mention that, while my drive was in UDMA mode and I was getting those signals, data and files were getting corrupted all over the system. Object files produced by every partial build of the JDK I ran got corrupted as well, which yielded quite interesting results. Every time I built while in that state, it seemed to get less and less far down the path, until it started dying with one of those signals right after starting, just like you described.

Even after reverting my drive back to WDMA2 mode, the build kept failing there because some of the object files already produced were corrupted. Doing a `make clean' got rid of all the corrupted stuff and I could start clean (and finally succeeded without a hitch), but first I had to fix the original cause of the signals :-)

Cheers,

Nicolas Gieczewski
Nix Software Solutions
http://www.nixsoftware.com/


----- Original Message ----- 
From: "Nicolas Gieczewski" <nicolas at nixsoftware.com>
To: "Richard Shea" <freebsdQ0 at richardshea.fastmail.fm>; <freebsd-java at freebsd.org>
Sent: Friday, December 12, 2003 22:09
Subject: Re: Removing JDK completely ?


I was getting those too, more specifically signals 9, 10 and 11. These are often due to faulty memory or hardware. I used to get these signals when compiling big stuff on my older box, which turned out to have faulty RAM. You can also get them when your CPU is overclocked and unstable. I was getting these signals at random stages during my build of the JDK 1.4, and I tracked down the problem to Ultra DMA being enabled for my hard drive. It seems the old IDE controller on this old motherboard didn't like UDMA, as per syslog (which I found out much later, after trying all sorts of stuff). Reverting the hard drive to WDMA2 fixed the problem.

By the way, have you tried compiling the kernel? This is often a good way to check your system's stability. If you get these signals there as well, it's extremely likely that the culprit is your hardware.

Hope this helps you in some way.

Nicolas Gieczewski
Nix Software Solutions
http://www.nixsoftware.com/


----- Original Message ----- 
From: "Richard Shea" <freebsdQ0 at richardshea.fastmail.fm>
To: <freebsd-java at freebsd.org>
Sent: Friday, December 12, 2003 21:54
Subject: Removing JDK completely ?


Hi - I've got a problem installing the JDK on FreeBSD 4.8 (see
"/usr/ports/java/jdk13 - make all dumps - any suggestions ?" on the
FreeBSD Questions list for details) and as I don't know how to fix I was
thinking that I might completely uninstall all Java related stuff and
start again.

So far I have obtained the Linux JDK, the sources for the JDK and the
FreeBSD patchset for the JDK and done a 'make install'. In fact I've done
a make install several times as the process fell over because certain
dependencies weren't met and so I fixed those and restarted. I've now got
to a point in the make where it just says 'illegal instruction'.

So my question is what's the best way to clean every trace of Java from
the box so I can start again and (maybe) get further this time ?

thanks

richard shea