From owner-freebsd-bugs Mon Feb 7 11:49:18 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by builder.freebsd.org (Postfix) with ESMTP id 593864075 for ; Mon, 7 Feb 2000 11:49:17 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id LAA44601; Mon, 7 Feb 2000 11:50:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Mon, 7 Feb 2000 11:50:03 -0800 (PST) Message-Id: <200002071950.LAA44601@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Torbjorn Granlund Subject: Re: kern/16568 Reply-To: Torbjorn Granlund Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/16568; it has been noted by GNATS. From: Torbjorn Granlund To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: kern/16568 Date: 07 Feb 2000 20:45:13 +0100 I have reproduced this on K6, PentiumII, and Athlon systems. (This problem originally popped up on a 3.3 system using ssh-agent from ossh-1.2.17, but Björn's tiny crash.c program only seems to crash 3.4.) To us, this problem is very critical indeed. It has made us lose two developer weeks during a very critical project. Perhaps we trust FreeBSD *too* much (we've had extremely little problems during the 4 years our business has using FreeBSD for all development and server machines). When the present problem popped up, we simply assumed it was a hardware problem. We even got ourselves a new server, which didn't make much difference... -- Torbjörn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message