From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 10 06:06:20 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6363D16A4BF for ; Wed, 10 Sep 2003 06:06:20 -0700 (PDT) Received: from smtp.covadmail.net (mx04.covadmail.net [63.65.120.64]) by mx1.FreeBSD.org (Postfix) with SMTP id EEEA243FE0 for ; Wed, 10 Sep 2003 06:06:16 -0700 (PDT) (envelope-from strick@covad.net) Received: (covad.net 17017 invoked from network); 10 Sep 2003 13:06:12 -0000 Received: from unknown (HELO ice.nodomain) (68.164.194.1) by sun-qmail15 with SMTP; 10 Sep 2003 13:06:11 -0000 Received: from ice.nodomain (localhost [127.0.0.1]) by ice.nodomain (8.12.8p1/8.12.8) with ESMTP id h8AD6Ck5001549; Wed, 10 Sep 2003 06:06:12 -0700 (PDT) (envelope-from dan@ice.nodomain) Received: (from dan@localhost) by ice.nodomain (8.12.8p1/8.12.8/Submit) id h8AD6CaF001548; Wed, 10 Sep 2003 06:06:12 -0700 (PDT) Date: Wed, 10 Sep 2003 06:06:12 -0700 (PDT) From: Dan Strick Message-Id: <200309101306.h8AD6CaF001548@ice.nodomain> To: freebsd-hackers@FreeBSD.ORG cc: dan@ice.nodomain Subject: WINE and hyperthreaded P4s X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2003 13:06:20 -0000 I always get an error like this when I run wine on FreeBSD 5.1: % wine98 sol err:ntdll:RtlpWaitForCriticalSection section 0x5c0ebb00 "../../scheduler/syslevel.c: Win16Mutex" wait timed out in thread 000a, blocked by 0009, retrying (60 sec) My first thought was that I must have botched my kernel, but the generic kernel does the same thing. Then I double checked my kernel config options. It has all the required SYSVxxx options but not USER_LDT (which seems to have gone away in release 5.1). (Is this correct?) My next thought was that wine just didn't work on FreeBSD 5.1. Then I did a mailing list archive search and turned up a brief discussion of what people were using wine for on release 5.1. So why does wine work (more or less as usual) on other people's FreeBSD 5.1 systems but not on mine? What is different about my system? My most recent speculation, which I admit is rather speculative, is that wine somehow discovers that I have a hyperthreaded P4 cpu and tries to do some extra mutiple-threaded thing but fails since I have hyperthreading disabled in the BIOS and I don't run a multiprocessor kernel. I don't really believe this explanation, but at least it is interesting. Can anyone suggest a more likely reason for my wine failures? I guess I could just wait for release 5.2 and see if the problem goes away. Dan Strick strick@covad.net