From owner-freebsd-smp Tue Jul 22 07:22:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA00972 for smp-outgoing; Tue, 22 Jul 1997 07:22:59 -0700 (PDT) Received: from weenix.guru.org (weenix.guru.org [198.82.200.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA00967 for ; Tue, 22 Jul 1997 07:22:53 -0700 (PDT) Received: (from kmitch@localhost) by weenix.guru.org (8.8.6/8.8.5) id KAA07745; Tue, 22 Jul 1997 10:22:42 -0400 (EDT) From: Keith Mitchell Message-Id: <199707221422.KAA07745@weenix.guru.org> Subject: Re: HEADS UP: major timer/APIC code changes. In-Reply-To: <199707221404.JAA00447@dyson.iquest.net> from "John S. Dyson" at "Jul 22, 97 09:04:43 am" To: toor@dyson.iquest.net (John S. Dyson) Date: Tue, 22 Jul 1997 10:22:42 -0400 (EDT) Cc: smp@freebsd.org X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > It could still be the VM code, but it would be good to understand how your > system is failing. For example, when your system "freezes" are you running > X windows? Can you still ping or telnet into it? Yes, I am running X-windows. I can't ping telnet or anything to the machine. I can't even log in via the serial console attached to the machine. The activity light on the network cards are still active though. Sometimes it occurs immediately after I log in and start typing in the xterm window. Other times it locks up while I am out and not using the computer. Twice I was using nfs at the time of the lockups. -- Keith Mitchell Head Administrator: acm.vt.edu Email: kmitch@weenix.guru.org PGP key available upon request http://weenix.guru.org/~kmitch