Date: Thu, 15 Jul 1999 00:33:34 -0700 From: Doug <Doug@gorean.org> To: Mike Smith <mike@smith.net.au> Cc: freebsd-hackers@freebsd.org Subject: Re: more amd hangs: problem really in syslog? Message-ID: <378D8ECE.80424336@gorean.org> References: <199907150556.WAA00543@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. OK, sent under different cover. > Specifically, it'd be handy to know why amd felt it was > necessary to open the console. Yeah, I'm kind of curious myself. BTW, I was going to work on this some more today, but the boss thought that putting the box into production was more important. The good news is that under real world load my freebsd box had 20-40% free cpu and a load average of 1.5. With load as equal as the switch could make it, the linux box had no free cpu and a load average of 8. :) I also (finally) got the approval to install freebsd on the fourth box (there are already two linux machines up) so A) I'm making progress in the office, and B) I should have a chance to pound on the syslog stuff tomorrow. Happy, Doug 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?378D8ECE.80424336>