From owner-freebsd-questions  Sun Nov  5 15:12:35 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id PAA20154
          for questions-outgoing; Sun, 5 Nov 1995 15:12:35 -0800
Received: from rainbow-jr.dreaming.org (rainbow-jr.dreaming.org [199.166.238.138])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA20126
          for <freebsd-questions@freebsd.org>; Sun, 5 Nov 1995 15:12:26 -0800
Received: (from scrappy@localhost) by rainbow-jr.dreaming.org (8.7.1/8.7.1) id SAA01906; Sun, 5 Nov 1995 18:09:36 -0500 (EST)
Date: Sun, 5 Nov 1995 18:09:32 -0500 (EST)
From: "Marc G. Fournier" <scrappy@hub.org>
X-Sender: scrappy@rainbow-jr.dreaming.org
To: Paul Reece <paul@jazz.trumpet.com.au>
cc: freebsd-questions@freebsd.org
Subject: Re: weird problem with 2.0.5
In-Reply-To: <Pine.BSF.3.91.951106095349.2596A-100000@jazz>
Message-ID: <Pine.BSF.3.91.951105180631.237C-100000@rainbow-jr.dreaming.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
Precedence: bulk

On Mon, 6 Nov 1995, Paul Reece wrote:

> Hi all.
> 
> I've been having a weird problem with a box running FreeBSD 2.0.5.
> 
> For some odd reason, the machine basically locks up totally with no warning
> and needs a reset to recover..  No crash dumps or anything of any kind - it
> just.. well.. stops!
> 
> The machine is a VESA 486DX4/100 with 64MB of ram and 2 IDE drives.
> 
> Anyone got any ideas as to what exactly may be causing this?
> (stop laughing Iain!)
> 
> Unusually this has only started to happen recently and as for the machine,
> I've never seen the loadave hit 1.
>

	You aren't running SLIP or anything like that, are you?  I know
that with 2.0R, I had an intermediate problem where SLIP would hang,
and if I SIGINT'd the slattach process, the machine itself would hang.
Haven't seen it with 2.0.5R yet, one of the reasons I upgraded, but
I've only been running it for a few days now...

	...the hang in that case reminded me of an error I had with
multi-port serial boards running under a much older version of BSDi,
where the bug had something to do with interrupt looping, or something 
like that.

> Also, anyone know why I can't copy a new kernel into place? (says 
> Operation Not Permitted).. I've done it before but for some odd reason
> it won't do it now (even in single-user mode)
> 
	Did you, by any chance, use chflags on your kernel last time?
An "ls -lo /kernel" should tell you if any of the settings are turned
on that would cause this.

Marc G. Fournier | Knowledge, Information and Communications, Inc (ki.net)
scrappy@hub.org  |
 soon to be:     | 
scrappy@ki.net   | For more information, send me email.