Date: Tue, 21 Jun 2005 11:29:56 -0400 (EDT) From: Tuc at T-B-O-H <ml@t-b-o-h.net> To: xfb52@dial.pipex.com (Alex Zbyslaw) Cc: Tuc at T-B-O-H <ml@t-b-o-h.net>, freebsd-questions@freebsd.org Subject: Re: Problems since 5.3-RELEASE-p15 Message-ID: <200506211529.j5LFTu2n097940@himinbjorg.tucs-beachin-obx-house.com> In-Reply-To: <42B7553A.9070402@dial.pipex.com> from "Alex Zbyslaw" at Jun 21, 2005 12:46:02 AM
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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. > > 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. > > However, if this *is* a hardware problem then I would worry about that > first. The upgrade to 5.3-p15 (presumably from 5.3-p-something else) > could be pure coincidence. I mean, you have to be doing *something* > before getting a hardware fault! > Such is true.................. Thanks, Tuc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200506211529.j5LFTu2n097940>