Date: Fri, 5 Apr 1996 13:36:53 +0100 From: "Thomas D.G. Sandford" <tdgsandf@prds-grn.demon.co.uk> To: FreeBSD-gnats-submit@freebsd.org Subject: kern/1118: Panic: setrunqueue encountered with Wine Message-ID: <199604051236.NAA00296@prds-grn> Resent-Message-ID: <199604052320.PAA20795@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 1118 >Category: kern >Synopsis: panic: setrunqueue encountered when wine fork()'s >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Apr 5 15:20:01 PST 1996 >Last-Modified: >Originator: Thomas D.G. Sandford >Organization: Paradise Green Technical Services >Release: FreeBSD 2.1-RELEASE >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. >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604051236.NAA00296>