From owner-freebsd-stable Mon Jan 28 9:13:10 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id EE9F937B400 for ; Mon, 28 Jan 2002 09:13:04 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id g0SHD0r52828; Mon, 28 Jan 2002 12:13:00 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20020127165021.6152b03a.ptiJo@noos.fr> References: <20020127165021.6152b03a.ptiJo@noos.fr> Date: Mon, 28 Jan 2002 12:12:58 -0500 To: ptiJo From: Garance A Drosihn Subject: Re: Possible bug in 4.5-RC1 vs VMware (linux emulation?) Cc: stable@freebsd.org, marcel@xcllnt.net, des@ofug.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Garance A Drosihn wrote: > > > I upgraded to 4.5-RC1 as it was on Wednesday (Jan 9th) at about 7pm. >> I then upgraded most (but not quite all) of my ports. On Thursday >> I needed to run VMware2 to debug some obscure problem I am seeing >> elsewhere (something not related to freebsd at all). >> >> The possible-bug part is that I get an error message when starting >> up vmware, saying "VMware was unable to read from /dev/acd0c. This >> can be caused by a Linux kernel bug...". It is saying "Linux kernel" >> because this is the Linux version of VMware2, which I am running via >> Linux emulation on freebsd. So, it thinks the host OS is linux. In > > any case, I wasn't getting this error until after those upgrades. Sigh. Well, sometime after I wrote the above message, I wrote another saying that I had upgraded and the problem was gone. I had even *read* cd's under two different virtual-system OS's without any trouble. So, I assumed that it had been fixed sometime after 4.5-RC2, but now the warning is back -- and I am not sure what I did to change things... So, I probably have to pin this down some more before claiming it is really solved. It is not much of a problem for my use, but it's just a little annoying (particularly since I don't know why it comes and goes). -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message