From owner-freebsd-bugs  Sat Jun  6 04:01:05 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id EAA22445
          for freebsd-bugs-outgoing; Sat, 6 Jun 1998 04:01:05 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA22437
          for <freebsd-bugs@FreeBSD.org>; Sat, 6 Jun 1998 04:01:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id EAA09929;
	Sat, 6 Jun 1998 04:00:02 -0700 (PDT)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id DAA21813;
          Sat, 6 Jun 1998 03:59:35 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199806061059.DAA21813@hub.freebsd.org>
Date: Sat, 6 Jun 1998 03:59:35 -0700 (PDT)
From: gram@cdsec.com
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: misc/6873: FreeBSD 2.2.6 freezes
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         6873
>Category:       misc
>Synopsis:       FreeBSD 2.2.6 freezes
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jun  6 04:00:01 PDT 1998
>Last-Modified:
>Originator:     Graham Wheeler
>Organization:
Citadel Data Security
>Release:        2.2.6-RELEASE
>Environment:
FreeBSD fortress.cdsec.com 2.2.6-RELEASE FreeBSD 2.2.6-RELEASE #34: Fri Jun  5 16:25:33 SAT 1998     root@fortress.cdsec.com:/usr/src/sys/compile/GENERIC  i386

>Description:
We have three 2.2.6-RELEASE machines which freeze up occasionally.
When they freeze, they can be pinged, and a telnet will result in a
TCP connect but no login prompt. All three are running X: two running
the SVGA server, and one the S3 server. Two are configured to use
SysMouse for the pointer device protocol, while one uses Microsoft.
All three have NE2000 Ethernet cards. We are now stopping using X on
one of the machines to see if this makes any difference.
>How-To-Repeat:
Unknown. It just happens, sometime while working on the machine,
sometimes when we arrive in the morning and the machine has been
`idle' all night.

>Fix:
Unknown.
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message