From owner-freebsd-hackers Tue Jul 13 16:13:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 9AD7C1514A for ; Tue, 13 Jul 1999 16:13:31 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id QAA18670; Tue, 13 Jul 1999 16:13:23 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Tue, 13 Jul 1999 16:13:23 -0700 (PDT) From: Doug X-Sender: doug@dt054n86.san.rr.com To: Mike Smith Cc: Doug , freebsd-hackers@freebsd.org Subject: Re: more amd hangs: problem really in syslog? In-Reply-To: <199907132248.PAA01661@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 13 Jul 1999, Mike Smith wrote: > 'siobi' is someone trying to open the serial console, for whatever > reason. Without knowing who it was that was stuck there, it's hard to > guess what is going on. D'uh, sorry. Long day. It was amd that was hung in the siobi state. No way to clear it without rebooting the box. Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message