Date: Fri, 12 Dec 2003 22:21:36 -0300 From: "Nicolas Gieczewski" <nicolas@nixsoftware.com> To: "Nicolas Gieczewski" <nicolas@nixsoftware.com>, "Richard Shea" <freebsdQ0@richardshea.fastmail.fm>, <freebsd-java@freebsd.org> Subject: Re: Removing JDK completely ? Message-ID: <0c0601c3c117$857323f0$0200a8c0@veggy.org> References: <20031213005442.A5B787E637@server2.messagingengine.com> <0bfb01c3c115$d0ffb9c0$0200a8c0@veggy.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 -----=20 From: "Nicolas Gieczewski" <nicolas@nixsoftware.com> To: "Richard Shea" <freebsdQ0@richardshea.fastmail.fm>; = <freebsd-java@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 -----=20 From: "Richard Shea" <freebsdQ0@richardshea.fastmail.fm> To: <freebsd-java@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0c0601c3c117$857323f0$0200a8c0>