From owner-freebsd-current@FreeBSD.ORG  Mon Nov 15 14:05:37 2004
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 D89F616A4E6; Mon, 15 Nov 2004 14:05:37 +0000 (GMT)
Received: from mail.imp.ch (ns1.imp.ch [157.161.1.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 3345843D31; Mon, 15 Nov 2004 14:05:37 +0000 (GMT)
	(envelope-from mb@imp.ch)
Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9])
	by mail.imp.ch (8.12.9p2/8.12.3) with ESMTP id iAFE5TXY017816;
	Mon, 15 Nov 2004 15:05:30 +0100 (CET)
	(envelope-from Martin.Blapp@imp.ch)
Date: Mon, 15 Nov 2004 15:05:29 +0100 (CET)
From: Martin Blapp <mb@imp.ch>
To: current@freebsd.org
In-Reply-To: <20041115145739.B53544@cvs.imp.ch>
Message-ID: <20041115150229.U53544@cvs.imp.ch>
References: <20041115145739.B53544@cvs.imp.ch>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checksum: ab3a2afb9801f9b47bf2a82dccb2f73d
X-Virus-Message-Status: No
X-Virus-Status: No, scantime="0.0012 seconds"
X-Spam-Status: No, hits=-4.9 required=5 scantime="3.7275 seconds"
	tests=BAYES_00
X-Scanned-By: MIMEDefang 2.48 on 192.168.0.2
Subject: vmware 3.x broken on FreeBSD 5.x / 6.x with IDE devices
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: Mon, 15 Nov 2004 14:05:38 -0000


Hi,

Since FreeBSD 5.2.1 we get the following error:

> Nov 15 14:54:39: VMX|OPROM: OpromPowerOff
> Nov 15 14:54:39: VMX|AIOPowerOff ide0:0

It looks like ad0 gets disconnected by vmware.
It is still not clear how this can happen. Of
course this leads to a deadlock if ad0 is the
root disk.

rtc: 100 > kern.hz: Timing will be inaccurate, please increase hz.
ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=5724133
ad0: FAILURE - ATA_IDENTIFY timed out
ad0: FAILURE - ATA_IDENTIFY timed out
ad0: WARNING - removed from configuration
ata0-master: FAILURE - WRITE_DMA timed out
swap_pager: I/O error - pagein failed; blkno 2,size 4096, error 0
vm_fault: pager read error, pid 2882 (amd)
vm_fault: pager read error, pid 2767 (vmware-mks)
Nov 15 15:01:10 chohira kernel: pid 2882 (amd), uid 0: exited on signal 11
Nov 15 15:01:10 chohira amd[411]: Process 2882 exited with signal 11
Nov 15 15:01:10 chohira amd[411]: mount for /host/nbs got signal 11
initiate_write_filepage: already started

Martin