Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!triceratops.cis.ohio-state.edu!karl From: karl@triceratops.cis.ohio-state.edu (Karl Kleinpaste) Newsgroups: comp.sys.pyramid Subject: Re: how to force a dump? Message-ID: Date: 28 Apr 89 14:16:24 GMT References: <8904272154.AA00226@era.ucar.edu.UCAR.EDU> <45696@tut.cis.ohio-state.edu> <68019@pyramid.pyramid.com> Sender: news@tut.cis.ohio-state.edu Organization: OSU Lines: 15 In-reply-to: csg@pyramid.pyramid.com's message of 28 Apr 89 08:34:14 GMT The suggestions for building a kernel w/debugger and then hitting ^@ to get control of it thereby, followed by a `pa' command, are fine...if the system is listening to the console. We had some problems with an early release of 4.4 where heavy network traffic caused the system to lock up so tight that it ignored the console - typing anything was rewarded with CPU BUSY in SSL #3, which usually says nothing more exciting than CPU[0]. It was necessary during these events to put the sort of operation which Chris Lott described to use. It worked, fortunately, and we did get usable core dumps out of it. The bugs causing the lockup were fixed months ago, of course. We're going to be upgrading several of our other 4.0 machines to 4.4 Real Soon Now. --Karl