From owner-freebsd-current Wed Dec 10 14:23:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA24947 for current-outgoing; Wed, 10 Dec 1997 14:23:19 -0800 (PST) (envelope-from owner-freebsd-current) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA24928 for ; Wed, 10 Dec 1997 14:23:10 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id WAA25764; Wed, 10 Dec 1997 22:23:03 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id XAA23475; Wed, 10 Dec 1997 23:23:03 +0100 (MET) Message-ID: <19971210232302.35402@follo.net> Date: Wed, 10 Dec 1997 23:23:02 +0100 From: Eivind Eklund To: Kevin Day Cc: Eivind Eklund , freebsd-current@FreeBSD.ORG Subject: Re: 971208 and the nfs rollback didn't fix it... References: <867m9c4zp5.fsf@bitbox.follo.net> <199712102218.QAA09186@home.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199712102218.QAA09186@home.dragondata.com>; from Kevin Day on Wed, Dec 10, 1997 at 04:18:50PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Dec 10, 1997 at 04:18:50PM -0600, Kevin Day wrote: > > Yes. Userland programs should NEVER be able to crash the kernel, > > especially not running as users (instead of root). > > > > Now - more details :-) Do you get a kernel panic when it crash? > > 90% of the time, it's just a reboot., No crash, just jumps straight to the > memory test. The other 10% it give a 'fault on nofault entry' panic. Have you ruled out faulty hardware? Do you get the same fault if you run with the same disk on another machine? (If not: Is this something you can afford to test?) > His .cshrc is essentially empty. > [default .cshrc file removed] > > Our /etc/login.conf is untouched from our install. > > > I have the entire eggdrop directory .tar'ed if someone wants to play with > it. If you can reproduce on other hardware and other installs, it's probably best to go that way. If it isn't reproducable I'd guess at a hardware-dependent problem - that'll be much harder. It might even be just a single case of faulty hardware. Eivind.