From owner-freebsd-hackers Wed Jul 14 23: 0:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles537.castles.com [208.214.165.101]) by hub.freebsd.org (Postfix) with ESMTP id DAAEC1507C for ; Wed, 14 Jul 1999 23:00:11 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id WAA00543; Wed, 14 Jul 1999 22:56:05 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907150556.WAA00543@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Cc: Mike Smith , freebsd-hackers@freebsd.org Subject: Re: more amd hangs: problem really in syslog? In-reply-to: Your message of "Tue, 13 Jul 1999 16:13:23 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Jul 1999 22:56:05 -0700 From: Mike Smith 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. Dang. Now I need that stack dump from amd that you posted and I deleted. Specifically, it'd be handy to know why amd felt it was necessary to open the console. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message