From owner-freebsd-hackers Tue Jul 13 14:39:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id A899914DD2 for ; Tue, 13 Jul 1999 14:39:48 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id OAA01221; Tue, 13 Jul 1999 14:34:05 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907132134.OAA01221@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Cc: freebsd-hackers@freebsd.org, peter@netplex.com.au Subject: Re: more amd hangs: problem really in syslog? In-reply-to: Your message of "Tue, 13 Jul 1999 13:20:55 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Jul 1999 14:34:05 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > After pounding on this some more with today's -current (prior to > the MNT_ASYNC flag change) I got a lot more lockups that looked like > this: > > On Mon, 12 Jul 1999, Doug wrote: > > > Ok, got another hang in "siobi" state (this time after it > > successfully completed the script). Here is the trace: 'siobi' is in sioopen() in the sio driver. The callout device is already open, but the caller is trying to open it in blocking mode. It'd be useful to know what is hanging in 'siobi' here, since trying to re-open the console is a bit of a suspicious action. -- \\ 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