Date: Thu, 15 Jul 1999 02:36:47 -0700 From: Gregory Sutter <gsutter@pobox.com> To: Mike Smith <mike@smith.net.au> Cc: Doug <Doug@gorean.org>, freebsd-hackers@FreeBSD.ORG Subject: Re: more amd hangs: problem really in syslog? Message-ID: <19990715023647.U55060@001101.zer0.org> In-Reply-To: <199907150556.WAA00543@dingo.cdrom.com>; from Mike Smith on Wed, Jul 14, 1999 at 10:56:05PM -0700 References: <Pine.BSF.4.05.9907131612280.18339-100000@dt054n86.san.rr.com> <199907150556.WAA00543@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 14, 1999 at 10:56:05PM -0700, Mike Smith wrote: > > 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. http://www.egroups.com/group/freebsd-hackers/40590.html Greg -- Gregory S. Sutter My reality check just bounced. mailto:gsutter@pobox.com http://www.pobox.com/~gsutter/ PGP DSS public key 0x40AE3052 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?19990715023647.U55060>