From owner-freebsd-current@FreeBSD.ORG  Sat Jul 12 12:36:02 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 167AE37B401
	for <current@freebsd.org>; Sat, 12 Jul 2003 12:36:02 -0700 (PDT)
Received: from mail.rdslink.ro (mail.rdslink.ro [193.231.236.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id 6FBAD43F3F
	for <current@freebsd.org>; Sat, 12 Jul 2003 12:36:00 -0700 (PDT)
	(envelope-from enache@rdslink.ro)
Received: (qmail 7868 invoked from network); 12 Jul 2003 19:30:10 -0000
Received: from unknown (HELO ratsnest.hole) (81.196.245.182)
  by mail.rdslink.ro with SMTP; 12 Jul 2003 19:30:10 -0000
Date: Sat, 12 Jul 2003 22:40:56 +0300
From: Enache Adrian <enache@rdslink.ro>
To: "Scott M. Likens" <damm@fpsn.net>
Message-ID: <20030712194056.GA1199@ratsnest.hole>
References: <1057983348.58611.4.camel@acheron.livid.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1057983348.58611.4.camel@acheron.livid.de>
User-Agent: Mutt/1.4i
cc: current@freebsd.org
Subject: Re: Regarding VMWare 3.0 Port and an odd bug that i've been getting
	over and over again...
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Jul 2003 19:36:02 -0000

On Fri, Jul 11, 2003 at 09:15:48PM -0700, Scott M. Likens wrote:
> Jul 11 16:45:20: ide0:0|NOT_IMPLEMENTED F(831):712
> Jul 11 16:45:20: ide0:0|AIO: ide0:0, Process 60017 panic.
> Jul 11 16:45:20: ide0:0|AIOSlave: Exit after panic.
> Jul 11 16:45:20: VMX|AIO: NOT_IMPLEMENTED F(831):712
> Jul 11 16:45:20: VMX|Panic loop

I'm pretty sure that's the nice incompatibility in recent glibc's.
vmware still thinks nice returns -1 on error, and that's no longer true:
it returns the new nice value, which could be very well -1.
The error message is totally bogus - it's probably issued by higher
layers that assume nice cannot fail.

Your only solution is to disassemble and "binary patch" vmware itself
using a hexeditor.
That may not be legal :-)

Good luck,

Adi