From owner-freebsd-hackers@FreeBSD.ORG  Thu Mar 29 13:56:10 2012
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 355C3106566B;
	Thu, 29 Mar 2012 13:56:10 +0000 (UTC) (envelope-from feld@feld.me)
Received: from feld.me (unknown [IPv6:2607:f4e0:100:300::2])
	by mx1.freebsd.org (Postfix) with ESMTP id EF3648FC19;
	Thu, 29 Mar 2012 13:56:09 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me;
	s=blargle; 
	h=In-Reply-To:Message-Id:From:Mime-Version:Date:References:Subject:To:Content-Type;
	bh=+6ASjC/RmnMRE2uUuT/vjGeoKDHxS+fN++4yds1bt0w=; 
	b=Zxo5WDY3XmbsXrR5Ei71FCY/wCPwFXoIlbyY9Ct8r9PjSWCVtwIOWZssDov1JkqkDN82wFZFHzz7JTVLRXAD39HqsMo7dJ7LBz2htuQi98bnqmfve8HQGLg2dhxT95td;
Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org)
	by feld.me with esmtp (Exim 4.77 (FreeBSD))
	(envelope-from <feld@feld.me>)
	id 1SDFpc-000EHe-H3; Thu, 29 Mar 2012 08:56:09 -0500
Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4)
	with esmtpa id 1333029358-20726-20725/5/10; Thu, 29 Mar 2012 13:55:58
	+0000
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
To: freebsd-questions@FreeBSD.org, freebsd-hackers@freebsd.org
References: <op.wbwe9s0k34t2sn@tech304>
	<CAJ-VmonqPbD1dPxBFF6sSSnSHP4H-VHcLJHziCrjTqscv4PV9A@mail.gmail.com>
Date: Thu, 29 Mar 2012 08:55:57 -0500
Mime-Version: 1.0
From: Mark Felder <feld@feld.me>
Message-Id: <op.wbxqbjx534t2sn@tech304>
In-Reply-To: <CAJ-VmonqPbD1dPxBFF6sSSnSHP4H-VHcLJHziCrjTqscv4PV9A@mail.gmail.com>
User-Agent: Opera Mail/11.62 (FreeBSD)
X-SA-Score: -1.5
Cc: 
Subject: Re: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Mar 2012 13:56:10 -0000

On Wed, 28 Mar 2012 18:31:38 -0500, Adrian Chadd <adrian@freebsd.org>  
wrote:

> * have you filed a PR?

No

> * is the crash easily reproducable?

Unfortunately not. It's totally random. Some servers will "get the bug"  
and crash daily, some will crash weekly, some might seem to be fine but 3  
months later hit this crash.

> * are you able to boot some ramdisk-only FreeBSD-8.2 images (eg create
> a ramdisk image using nanobsd?) and do some stress testing inside
> that?

That's a plan I'd like to execute but my free time for building that  
environment is rather short at the moment :(

> I'm not that
> cluey on ESXi, but there may be some PIC/APIC/ACPI change between 7.x
> and 8.0 which has caused this to surface.

Was there a setting to revert ACPI behavior from 8.x to 7.x? I thought I  
read about that at one point.... or perhaps this was something available  
back in the dev cycle when 8 was -CURRENT. *shrug* I know 9.0 and onward  
has even more ACPI changes so assuming it truly is an ACPI bug I guess we  
could cross our fingers and hope that the bug has mysteriously vanished?