From tdgsandf@prds-grn.demon.co.uk  Fri Apr  5 15:19:30 1996
Received: from relay-2.mail.demon.net (disperse.demon.co.uk [158.152.1.77])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA20736
          for <FreeBSD-gnats-submit@freebsd.org>; Fri, 5 Apr 1996 15:19:22 -0800 (PST)
Received: from post.demon.co.uk ([158.152.1.72]) by relay-2.mail.demon.net
          id ag17013; 6 Apr 96 0:19 +0100
Received: from prds-grn.demon.co.uk ([158.152.232.106])
          by relay-3.mail.demon.net id aa27814; 5 Apr 96 23:32 +0100
Received: (from tdgsandf@localhost) by prds-grn (8.6.12/8.6.12) id NAA00296; Fri, 5 Apr 1996 13:36:53 +0100
Message-Id: <199604051236.NAA00296@prds-grn>
Date: Fri, 5 Apr 1996 13:36:53 +0100
From: "Thomas D.G. Sandford" <tdgsandf@prds-grn.demon.co.uk>
Reply-To: tdgsandf@prds-grn.demon.co.uk
To: FreeBSD-gnats-submit@freebsd.org
Subject: Panic: setrunqueue encountered with Wine 
X-Send-Pr-Version: 3.2

>Number:         1118
>Category:       kern
>Synopsis:       panic: setrunqueue encountered when wine fork()'s
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Apr  5 15:20:01 PST 1996
>Closed-Date:    Tue Mar 25 18:25:17 PST 1997
>Last-Modified:  Tue Mar 25 18:25:55 PST 1997
>Originator:     Thomas D.G. Sandford
>Release:        FreeBSD 2.1-RELEASE
>Organization:
Paradise Green Technical Services
>Environment:

	FreeBSD 2.1.0-RELEASE
	Copam PC486B/25
	Wine-940324 or Wine-940331 built "out of the box" (*not* the port).

>Description:

	With the environment described above the following

		% wine nosuchfile

	causes a kernel panic with the following report

		panic: setrunqueue

	I believe the problem occurs when a fork() is executed in the
	wine source file loader/module.c

	It is probably partly symptomatic of a problem in wine itself,
	but clearly even a buggy user-mode program should not be able to
	crash the kernel.


>How-To-Repeat:

	As above.

>Fix:
	
	None known.

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: scrappy 
State-Changed-When: Mon Oct 21 23:23:30 PDT 1996 
State-Changed-Why:  

Dust off the cobwebs - Confirm Status 
State-Changed-From-To: feedback->open 
State-Changed-By: scrappy 
State-Changed-When: Mon Nov 4 06:25:41 PST 1996 
State-Changed-Why:  

Is anyone else out there using WINE that can comment on this? 

Originator is still using 2.1-RELEASE, and there have been *soo* 
many changeto the kernel in recent months/weeks... 


From: "Thomas D.G. Sandford" <tdgsandf@prds-grn.demon.co.uk>
To: "Marc G. Fournier" <scrappy@freefall.freebsd.org>
Cc:  Subject: Re: kern/1118
Date: Tue, 5 Nov 1996 01:16:49 +0000 (GMT)

 > 
 > Synopsis: panic: setrunqueue encountered when wine fork()'s
 > 
 > State-Changed-From-To: feedback->open
 > State-Changed-By: scrappy
 > State-Changed-When: Mon Nov 4 06:25:41 PST 1996
 > State-Changed-Why: 
 > 
 > Is anyone else out there using WINE that can comment on this?
 > 
 > Originator is still using 2.1-RELEASE, and there have been *soo*
 > many changeto the kernel in recent months/weeks...
 > 
 There was a brief discussion about this issue in the last week or so on
 comp.emulators.ms-windows.wine/comp.unix.bsd.freebsd.misc
 
 Another user reported the same problem with 2.1.5-RELEASE. I think someone
 else reported that 2.2-SNAP???? was OK.
 
 There was also some technical discussion, with a suggestion that the problem
 was that the user ldt's were not being copied/reset up or some such.
 
 If you have news access it would probably be well worth checking up on the
 thread. The thread title is "Wine960928 crashed FreeBSD 2.1.5" - the first
 article was dated 29th October 1996.
 
 Jordan and John Dyson have both contributed to the thread. (As they have
 probably already told you by now :-> ).
 
 -- 
 Thomas Sandford | t.d.g.sandford@prds-grn.demon.co.uk
 
State-Changed-From-To: open->closed 
State-Changed-By: mpp 
State-Changed-When: Tue Mar 25 18:25:17 PST 1997 
State-Changed-Why:  
This should already be fixed in 2.2 and 3.0-current. 
>Unformatted:
