Date: Thu, 23 Aug 2001 20:33:26 -0400 From: Brian McGovern <mcgovern@beta.com> To: freebsd-qa@freebsd.org Subject: More on top taking forever to start Message-ID: <200108240033.f7O0XQr11414@spoon.beta.com>
next in thread | raw e-mail | index | archive | help
Ok. It does not occur on the home 4.4RC1 system. So, it should probably be something to do with the specific machine. I did notice one thing that may be of use. On my work system, irq 5, as per systat -vmstat, is labeled "mux". On the home system, irq 5 isn't even used. I've proven its not network related. Both servers have Intel cards in them. The home system worked fine over the net and on the console. Top didn't work either on the console or over the network at the office. When I ran top at the work system, systat -vmstat didn't show much system activity until it started to display, about when I saw 508 interrupts on the mux irq. When the system is idle, I see 2-3 mux interrupts every 5-10 seconds. So what happens is this.... Low "mux" interrupts. top is started, and a few more show up (although its within the background noise). Then, when top starts displaying, there is a sudden surge. I'll take a look and see if there are any serious interrupt conflicts, although I expect there aren't any. I'll also try to see if I can link them back to top. -Brian - --f7NMot414166.998607055/sj-msg-av-2.cisco.com-- ------- End of Forwarded Message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200108240033.f7O0XQr11414>