From owner-freebsd-stable@FreeBSD.ORG Sun Dec 7 13:41:55 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE9CE16A4D1 for ; Sun, 7 Dec 2003 13:41:55 -0800 (PST) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97F1E43FD7 for ; Sun, 7 Dec 2003 13:41:52 -0800 (PST) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 8A01A72DB8; Sun, 7 Dec 2003 13:41:52 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 8854F72DB5; Sun, 7 Dec 2003 13:41:52 -0800 (PST) Date: Sun, 7 Dec 2003 13:41:52 -0800 (PST) From: Doug White To: denon In-Reply-To: <6.0.1.1.2.20031207022844.066a9008@mail.jon.com> Message-ID: <20031207134057.Y7085@carver.gumbysoft.com> References: <6.0.1.1.2.20031207022844.066a9008@mail.jon.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 4.8 and instabilities with Buslogic SCSI drivers in VMWare X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2003 21:41:55 -0000 On Sun, 7 Dec 2003, denon wrote: > We've been doing more work with VMware and FreeBSD lately. Overall it's > been going well, but we have a machine that's giving me grief, and I'm a > bit concerned. > > It's running 4.8-Release, with a single virtual SCSI drive. It's been > running fine for months, but as of recently, it's started locking up. When > it locks up, this is what's in the messages: > /kernel: (da0:bt0:0:0:0): CCB 0xca993340 - timed out > /kernel: bt0: btdone - Attempt to free non-active BCCB 0xca9933c0 I wonder if the vmware environment is bug-for-bug compatible with the old buslogic hardware :-) I suspect this is a bug in vmware, where the emulated driver is suffering from long-term corruption. 43-day bug, perhaps? Does stopping and starting VMware clear this up? -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org