Date: Tue, 13 Jul 1999 15:48:35 -0700 From: Mike Smith <mike@smith.net.au> To: Doug <Doug@gorean.org> Cc: freebsd-hackers@freebsd.org Subject: Re: more amd hangs: problem really in syslog? Message-ID: <199907132248.PAA01661@dingo.cdrom.com> In-Reply-To: Your message of "Tue, 13 Jul 1999 15:49:04 PDT." <Pine.BSF.4.05.9907131547280.18339-100000@dt054n86.san.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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? '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. -- \\ 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907132248.PAA01661>