From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 21:03:05 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 6AD4B16A4CE for ; Thu, 11 Dec 2003 21:03:05 -0800 (PST) Received: from queue.paperwork.com (ns.place4us.com [206.8.93.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6875943D36 for ; Thu, 11 Dec 2003 21:02:59 -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 3C89E70CA0; Thu, 11 Dec 2003 23:12:25 -0600 (CST) Message-Id: <6.0.1.1.2.20031211225738.05815900@mail.jon.com> X-Sender: denon@denon.cx (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Thu, 11 Dec 2003 23:02:48 -0600 To: Doug White From: denon In-Reply-To: <20031211203621.S45532@carver.gumbysoft.com> References: <20031212000934.TAGY73768.web01-imail.rogers.com@win2000> <20031211203621.S45532@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: Fri, 12 Dec 2003 05:03:05 -0000 I agree with your analysis of the 4-year old driver, though it's funny to say it's in a difficult to reproduce environment. In all actuality, a software-based system would be one of the most controlled environments available, removing all variables of heat, flakey hardware, etc, and abstracting them from the hardware layer. VMware seems to be really robust, when the OS plays nicely. (unfortunately win2k under vmware seems to be extremely robust, even under high loads .. what luck.) This aside, I think you'll find that creating a FBSD 4.8 system in a scsi-based vmware disk will reproduce it somewhat consistently. I've spoke with several others having the same issue. You'll also take note that I'm not the guy that said this place was dead. :) Regards, -d At 10:43 PM 12/11/2003, you wrote: >On Thu, 11 Dec 2003, Mike Jakubik wrote: > > > It seems like this list is dead, and the developers don't care anymore. > > Current is where it's at. > >This is patently wrong. Please don't do this. > >Since this is an isolated report in a hard-to-reproduce environment >(vmware), its difficult to say if this is a bug in our software or a bug >in vmware. Considering the bt driver hasn't been touched in over 4 years, >I'm thinking that there may be issues in vmware. > >I'd follow up with the vmware folks. > > > > > -----Original Message----- > > From: owner-freebsd-stable@freebsd.org > > [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of denon > > Sent: Thursday, December 11, 2003 12:28 PM > > To: freebsd-stable@freebsd.org > > Subject: Re: FreeBSD 4.8 and instabilities with Buslogic SCSI drivers in > > VMWare > > > > So there are no other thoughts on this? I kinda figured people were > > interested in squashing 4.8 bugs left and right .. :) > > > > -d > > > > At 03:25 PM 12/8/2003, you wrote: > > >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 > > >_______________________________________________ > > >freebsd-stable@freebsd.org mailing list > > >http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > >-- >Doug White | FreeBSD: The Power to Serve >dwhite@gumbysoft.com | www.FreeBSD.org >_______________________________________________ >freebsd-stable@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"