From owner-freebsd-hackers Fri Jun 28 05:22:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA00186 for hackers-outgoing; Fri, 28 Jun 1996 05:22:57 -0700 (PDT) Received: from fgate.flevel.co.uk (fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA00180 for ; Fri, 28 Jun 1996 05:22:53 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.6.12/8.6.9) with SMTP id NAA06602; Fri, 28 Jun 1996 13:23:03 +0100 Date: Fri, 28 Jun 1996 13:23:02 +0100 (BST) From: Developer To: "Jordan K. Hubbard" cc: hackers@freebsd.org Subject: Re: BSD V2.2 In-Reply-To: <25953.835816385@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 26 Jun 1996, Jordan K. Hubbard wrote: > Well, now that is different. I suspected your config file up to now > since you really have turned on some oddball combinations there (and > I'd *still* prune it drastically if this other problem weren't > occurring since it still looks more like LINT than GENERIC), but if > the kernel I supplied is broken then it does indeed look like there's > some incompatibility with your system. Can you describe your system > configuration to me in detail? Ive just tried an older 2.2 snap and found that it crashes in the same way :( I think that maybe there is something in the 2.2 kernel that doesn't like our systems. I think that it must be something quite low level as it reboots before any of the system debug messages about the devices even come up. Very strange. Thanks for your help. Regards, Trefor S.