From nobody@FreeBSD.ORG Mon Oct 11 11:38:01 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id D429615539; Mon, 11 Oct 1999 11:38:01 -0700 (PDT)
Message-Id: <19991011183801.D429615539@hub.freebsd.org>
Date: Mon, 11 Oct 1999 11:38:01 -0700 (PDT)
From: davidc@acns.ab.ca
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: Combination of aio_read(), pthread_cond_wait(), and sched_yield() kills machine.
X-Send-Pr-Version: www-1.0

>Number:         14264
>Category:       misc
>Synopsis:       Combination of aio_read(), pthread_cond_wait(), and sched_yield() kills machine.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 11 11:40:00 PDT 1999
>Closed-Date:    Wed Jun 7 12:42:12 PDT 2000
>Last-Modified:  Wed Jun  7 12:43:27 PDT 2000
>Originator:     Chad David
>Release:        3.3-stable
>Organization:
ACNS Inc.
>Environment:
FreeBSD colnta.acns.ab.ca 3.3-STABLE FreeBSD 3.3-STABLE #0: 
Mon Oct 11 12:00:46 MDT 1999     
toor@colnta.acns.ab.ca:/usr/src/sys/compile/ACNS1  i386
>Description:
After a (incorrect) call to pthread_cond_wait(), calling sched_yield()
freezes the machine instantly.
>How-To-Repeat:
Compile and run the source 
(available from http://www.guild.ab.ca/killer.tar.gz )
Once running the app is listening on TCP port 8899, telnet
to the port and the machine will freeze.

If the pthread_cond_wait() call is fixed, or sched_yield() is
removed the problem goes away.
>Fix:


>Release-Note:
>Audit-Trail:

From: jasone@canonware.com
To: FreeBSD-gnats-submit@FreeBSD.org, davidc@acns.ab.ca
Cc: jasone@freebsd.org
Subject: Re: misc/14264: Combination of aio_read(), pthread%5
Date: 28 Dec 1999 16:20:44 -0000

 I cannot reproduce this problem on a 3.3-STABLE machine from 17
 November.  Can you:
 
 1) Still produce the problem on a recent -stable box?
 
 2) Distill the program that causes the behavior down to something
    a bit smaller?
 
 I can deal with the size of the program, but since it doesn't cause
 a crash for me, I can't even guess as to what the problem might have
 been.
 
 Jason
 
 
State-Changed-From-To: open->closed 
State-Changed-By: jasone 
State-Changed-When: Wed Jun 7 12:42:12 PDT 2000 
State-Changed-Why:  
I'm unable to reproduce the problem, and the originator has not provided 
additional information that would allow the validity of this PR to be 
evaluated. 
>Unformatted:
