From owner-freebsd-questions@FreeBSD.ORG Tue Jun 21 17:07:54 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E8EB16A41C for ; Tue, 21 Jun 2005 17:07:54 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out3.blueyonder.co.uk (smtp-out3.blueyonder.co.uk [195.188.213.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1316843D49 for ; Tue, 21 Jun 2005 17:07:51 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [82.41.37.55] ([82.41.37.55]) by smtp-out3.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Tue, 21 Jun 2005 18:08:31 +0100 Message-ID: <42B84964.6070909@dial.pipex.com> Date: Tue, 21 Jun 2005 18:07:48 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.8) Gecko/20050530 X-Accept-Language: en, en-us, pl MIME-Version: 1.0 To: Tuc at T-B-O-H References: <200506211529.j5LFTu2n097940@himinbjorg.tucs-beachin-obx-house.com> In-Reply-To: <200506211529.j5LFTu2n097940@himinbjorg.tucs-beachin-obx-house.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 21 Jun 2005 17:08:31.0453 (UTC) FILETIME=[D9AA30D0:01C57683] Cc: freebsd-questions@freebsd.org Subject: Re: Problems since 5.3-RELEASE-p15 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2005 17:07:54 -0000 Tuc at T-B-O-H wrote: >>> Yes. I have a 2 part process I run : >>>[process elided] >>> I guess I could re-run it and see if it continues. >>> >>> > I took the plunge and am now at 5.4-RELEASE-p2.... I >upgraded my Nvidia driver too. > > So far I saw : > >Jun 21 01:24:17 himinbjorg kernel: pid 5693 (javac), uid 0: exited on signal 11 (core dumped) >Jun 21 01:24:17 himinbjorg kernel: Jun 21 01:24:17 himinbjorg kernel: pid 5693 (javac), uid 0: exited on signal 11 (core dumped) >Jun 21 01:25:28 himinbjorg kernel: pid 14996 (javac), uid 0: exited on signal 11 (core dumped) >Jun 21 01:25:28 himinbjorg kernel: Jun 21 01:25:28 himinbjorg kernel: pid 14996 (javac), uid 0: exited on signal 11 (core dumped) >Jun 21 01:25:29 himinbjorg kernel: pid 15016 (java), uid 0: exited on signal 11 (core dumped) >Jun 21 01:25:29 himinbjorg kernel: Jun 21 01:25:29 himinbjorg kernel: pid 15016 (java), uid 0: exited on signal 11 (core dumped) > > > Which I don't understand because I don't know what I was doing that >needed java. I think it might have been part of upgrading the nvidia driver. > > I wouldn't have thought so. If I do: % cd /usr/ports/x11/nvidia-driver % make pretty-print-build-depends-list % make pretty-print-run-depends-list This port requires package(s) "gettext-0.14.5 libiconv-1.9.2_1 linux-XFree86-libs-4.3.99.902_3 linux-expat-1.95.5_3 linux-fontconfig-2.1_3 linux_base-8-8.0_6 popt-1.7 rpm-3.0.6_10" to run. There's no mention of java. I wouldn't say it definitively rules it out though. Are you sure that java wasn't left over from 4.X? One thing to try is: % pkg_info | egrep -i java javavmwrapper-2.0_4 Wrapper script for various Java Virtual Machines jdk-1.4.2p7_1 Java Development Kit 1.4.2 linux-sun-jdk-1.4.2.08_2 Sun Java Development Kit 1.4 for Linux vnc-4.1.1 Display X and Win32 desktops on remote X/Win32/Java display % pkg_info -R jdk-1.4.2p7_1 Information for jdk-1.4.2p7_1: % pkg_info -R linux-sun-jdk-1.4.2.08_2 Information for linux-sun-jdk-1.4.2.08_2: Which shows that nothing on my system positively requires java (though mozilla et al. use it). I doubt it's a browser as javac is the compiler rather than the runtime environment (which has always seemed to crash at irregular intervals for me). >>If the problem is intermittent then I would suspect the hardware (I >>know, everyone always says that, but I really have used a brand new >>server which segfaulted randomly and it really was a memory problem). >>Try building a memtest86 CD from the ports (from a different machine >>perhaps) and running it for at least several hours, though it might not >>take that long. Your BIOS might also support extended memory tests (try >>disabling quick POST) though they are supposed to be less effective than >>memtest86. >> >> >> > Ok, will try that. I run SETI so I think I'm constantly stressing >the machine. But I'll give it a try. > *If* there are intermittent memory errors, then it could be that SETI always happens to get them in the data it is dealing with, in which case it might run perfectly happily but just produce the wrong results. Memtest is dull, and stops you using your PC, but like Windows virus scans, it seems like a necessary evil in this case. --Alex