From owner-freebsd-bugs Sat Nov 9 02:30:07 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA18564 for bugs-outgoing; Sat, 9 Nov 1996 02:30:07 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA18553; Sat, 9 Nov 1996 02:30:04 -0800 (PST) Date: Sat, 9 Nov 1996 02:30:04 -0800 (PST) Message-Id: <199611091030.CAA18553@freefall.freebsd.org> To: freebsd-bugs Cc: From: "Thomas D.G. Sandford" Subject: Re: kern/1118 Reply-To: "Thomas D.G. Sandford" Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/1118; it has been noted by GNATS. From: "Thomas D.G. Sandford" To: "Marc G. Fournier" 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