From nobody@FreeBSD.org  Tue Dec 26 09:16:31 2000
Return-Path: <nobody@FreeBSD.org>
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id F392A37B402
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 26 Dec 2000 09:16:29 -0800 (PST)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id eBQHGTS06687;
	Tue, 26 Dec 2000 09:16:29 -0800 (PST)
	(envelope-from nobody)
Message-Id: <200012261716.eBQHGTS06687@freefall.freebsd.org>
Date: Tue, 26 Dec 2000 09:16:29 -0800 (PST)
From: rlegene@optiglobe.com.ar
Sender: nobody@FreeBSD.org
To: freebsd-gnats-submit@FreeBSD.org
Subject: panicked on sofree
X-Send-Pr-Version: www-1.0

>Number:         23859
>Category:       kern
>Synopsis:       panicked on sofree
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Dec 26 09:20:01 PST 2000
>Closed-Date:    Tue Feb 26 08:20:52 PST 2002
>Last-Modified:  Tue Feb 26 08:21:45 PST 2002
>Originator:     Robert Martin-Legene
>Release:        4.2-RELEASE
>Organization:
>Environment:
FreeBSD sandbox.optiglobe.com.ar 4.2-STABLE FreeBSD 4.2-STABLE #1: Thu Dec 21 12:54:10 ART 2000     rlegene@sandbox.optiglobe.com.ar:/usr/src/sys/compile/SANDBOX  i386

>Description:
tcp_input: could not copy policy
tcp_input: could not copy policy
tcp_input: could not copy policy
panic: sofree: not queued

Syncing disks... 12 6

(I am not sure whether the first three lines are related to the panic)

Most likely caused by running benchmark/polygraph. After a server and 
client spawned off to do IPC, the machine appeared dead after a few seconds.

Was also running net/scotty3, but it had most likely been idle for long.

When trying to reproduce the problem, polygraph was started first. Seing it didn't crash the system, tkined (scotty3) was started. Running "IP Discover" in tkined failed caused by "failed to open socket: no buffer space available". Quitting polygraph released lots of resources and tkined had subsequently no problems. Obviously polygraph is doing extensive socket operations.
>How-To-Repeat:
No "success" repeating the crash (see above)
>Fix:


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: silby 
State-Changed-When: Mon Feb 25 23:29:26 PST 2002 
State-Changed-Why:  
Can you provide more information on the system that experienced 
this problem?  Has it reoccured? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=23859 
State-Changed-From-To: feedback->closed 
State-Changed-By: silby 
State-Changed-When: Tue Feb 26 08:20:52 PST 2002 
State-Changed-Why:  
The bug hasn't reoccured for the author, may have been related 
to the > 32768 socket panic fixed in 4.3. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=23859 
>Unformatted:
