Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Aug 1999 11:27:48 -0700
From:      "David Schwartz" <davids@webmaster.com>
To:        <stable@freebsd.org>
Subject:   RE: panic: timeout table full
Message-ID:  <000001bee8de$3512a270$021d85d1@youwant.to>
In-Reply-To: <000001bee883$c49b8980$021d85d1@youwant.to>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

	I just browsed for any information I could find on this problem. It seems
that my crash differs from the others reported in a few ways:

	1) I was running 3.2-STABLE from about 26 days ago.

	2) I had maxusers set to 64, not something absurd like 4.

	3) My machine was not massively loaded at the time. Pretty much all it was
doing was runnning xntpd (stratum one with over 100 clients) and compiling
libc_r.

	I raised maxusers to 128 and re-cvsupped the latest.

	DS

> 	I just had one of my servers crash with this panic from
> kern_timeout.c. The
> relevant code seems to be:
>
>         /* Fill in the next free callout structure. */
>         new = SLIST_FIRST(&callfree);
>         if (new == NULL)
>                 /* XXX Attempt to malloc first */
>                 panic("timeout table full");
>         SLIST_REMOVE_HEAD(&callfree, c_links.sle);
>
> 	I'm just curious, what might consume too many timeout
> structures? And can I
> cause it to default to more of them?
>
> 	DS



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?000001bee8de$3512a270$021d85d1>