Bug 23859

Summary:	panicked on sofree
Product:	Base System	Reporter:	rlegene <rlegene>
Component:	kern	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	4.2-RELEASE
Hardware:	Any
OS:	Any

Description rlegene 2000-12-26 17:20:01 UTC

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)

Comment 1 silby freebsd_committer

2002-02-26 07:29:26 UTC

State Changed
From-To: open->feedback

Can you provide more information on the system that experienced 
this problem?  Has it reoccured?

Comment 2 silby freebsd_committer

2002-02-26 16:20:52 UTC

State Changed
From-To: feedback->closed

The bug hasn't reoccured for the author, may have been related 
to the > 32768 socket panic fixed in 4.3.