Date: Sat, 12 Jul 2003 22:40:56 +0300 From: Enache Adrian <enache@rdslink.ro> To: "Scott M. Likens" <damm@fpsn.net> Cc: current@freebsd.org Subject: Re: Regarding VMWare 3.0 Port and an odd bug that i've been getting over and over again... Message-ID: <20030712194056.GA1199@ratsnest.hole> In-Reply-To: <1057983348.58611.4.camel@acheron.livid.de> References: <1057983348.58611.4.camel@acheron.livid.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030712194056.GA1199>