From owner-freebsd-bugs Sun Oct 26 11:10:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA16177 for bugs-outgoing; Sun, 26 Oct 1997 11:10:03 -0800 (PST) (envelope-from owner-freebsd-bugs) Received: (from gnats@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA16168; Sun, 26 Oct 1997 11:10:01 -0800 (PST) (envelope-from gnats) Resent-Date: Sun, 26 Oct 1997 11:10:01 -0800 (PST) Resent-Message-Id: <199710261910.LAA16168@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@FreeBSD.ORG, ivar@hosteng.org Received: (from nobody@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA16083; Sun, 26 Oct 1997 11:06:39 -0800 (PST) (envelope-from nobody) Message-Id: <199710261906.LAA16083@hub.freebsd.org> Date: Sun, 26 Oct 1997 11:06:39 -0800 (PST) From: ivar@hosteng.org To: freebsd-gnats-submit@FreeBSD.ORG X-Send-Pr-Version: www-1.0 Subject: kern/4859: SMP kernel panics with timeout table full msg when running two cpu intensive programs Sender: owner-freebsd-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Number: 4859 >Category: kern >Synopsis: SMP kernel panics with timeout table full msg when running two cpu intensive programs >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Oct 26 11:10:00 PST 1997 >Last-Modified: >Originator: Ivar E. Hosteng >Organization: Merkantildata ASA >Release: 3.0-971002-SNAP >Environment: FreeBSD romulus.hosteng.org 3.0-971002-SNAP FreeBSD 3.0-971002-SNAP #0: Sun Oct 26 18:22:38 CET 1997 root@romulus.hosteng.org:/usr/src/sys/compile/erik i38 6 >Description: The kernel is bulilt with SMP enabled and is running on a 2 CPU 200Mhz PPRo system (Intel Providence motherboard) with 128 MB ram. When i run the rc5 key cracking program for the rc5 cracking contest (ftp://ftp.distributed.net/pub/rc5-64/v2.6401/rc56401-freebsd-x86-cli.tar.gz) the system panics with a 'timeout table full' followed by a 'page fault' panic. Othervise the system have been solid. >How-To-Repeat: Just let two copies of the above mentioned program run concurrently for a period of time. My record (3 trys) is 5 minutes until it panics) >Fix: >Audit-Trail: >Unformatted: