From owner-freebsd-hackers Tue Jul 13 15:51: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 CEB0315134 for ; Tue, 13 Jul 1999 15:51:22 -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 PAA18458; Tue, 13 Jul 1999 15:49:04 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Tue, 13 Jul 1999 15:49:04 -0700 (PDT) From: Doug X-Sender: doug@dt054n86.san.rr.com To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: more amd hangs: problem really in syslog? In-Reply-To: <199907132134.OAA01221@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: > > 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. I'm using a serial console, but I directed local7 to a file in syslog.conf. But from what you're saying it sounds like the serial console is a suspect? 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