From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 13:26:39 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 82B6E16A4CE for ; Mon, 8 Dec 2003 13:26:39 -0800 (PST) Received: from queue.paperwork.com (ns.place4us.com [206.8.93.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6401443D28 for ; Mon, 8 Dec 2003 13:26:30 -0800 (PST) (envelope-from denon@denon.cx) Received: from ONYX.denon.cx (unknown [206.8.93.100]) by queue.paperwork.com (CCS Enterprise SMTP) with ESMTP id C02E97C4D5; Mon, 8 Dec 2003 15:35:18 -0600 (CST) Message-Id: <6.0.1.1.2.20031208152409.09cfed60@mail.jon.com> X-Sender: denon@denon.cx (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Mon, 08 Dec 2003 15:25:49 -0600 To: Doug White From: denon In-Reply-To: <20031207134057.Y7085@carver.gumbysoft.com> References: <6.0.1.1.2.20031207022844.066a9008@mail.jon.com> <20031207134057.Y7085@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed 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: Mon, 08 Dec 2003 21:26:39 -0000 Responses inline: At 03:41 PM 12/7/2003, you wrote: >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 :-) Sure seems it .. though it was stable for a long time, so I don't know .. >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? Nope, apparently not .. I tried and its happened again today. Seems to happen about twice a day, but no pattern to it that I see.. -d