On Saturday 15 July 2006 00:08, User Freebsd wrote:
> On Sat, 15 Jul 2006, Kostik Belousov wrote:
> > On Sat, Jul 15, 2006 at 12:10:29AM -0300, User Freebsd wrote:
> >> On Wed, 5 Jul 2006, Robert Watson wrote:
> >>> If you can get into DDB when the hang has occurred, output via
> >>> serial console
On 14/07/2006 6:08 PM, User Freebsd wrote:
Just in case, do you use mlocked mappings ? Also, why so huge number
of crons exist in the system ? The are all forking now. It may be (can
not say definitely without further investigation) just a fork bomb.
re: crons ... this, I'm not sure of, but my
On Sat, 15 Jul 2006, Kostik Belousov wrote:
On Sat, Jul 15, 2006 at 12:10:29AM -0300, User Freebsd wrote:
On Wed, 5 Jul 2006, Robert Watson wrote:
If you can get into DDB when the hang has occurred, output via serial
console for the following commands would be very helpful:
show pcpu
show
On Sat, Jul 15, 2006 at 12:10:29AM -0300, User Freebsd wrote:
>
>
> On Wed, 5 Jul 2006, Robert Watson wrote:
>
> >If you can get into DDB when the hang has occurred, output via serial
> >console for the following commands would be very helpful:
> >
> >show pcpu
> >show allpcpu
> >ps
> >trace
>
On Sat, 15 Jul 2006, User Freebsd wrote:
On Wed, 5 Jul 2006, Robert Watson wrote:
If you can get into DDB when the hang has occurred, output via serial
console for the following commands would be very helpful:
show pcpu
show allpcpu
ps
trace
traceall
show locks
show alllocks
show uma
show ma
