From owner-freebsd-hackers@FreeBSD.ORG  Thu May 24 13:47:58 2012
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 124AE106566B;
	Thu, 24 May 2012 13:47:58 +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 C8D928FC25;
	Thu, 24 May 2012 13:47:57 +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:Cc:To:Content-Type;
	bh=Dx+tidjkZx7ELxUmKjjjsoraPEkfl5PkhgQl3nNjujg=; 
	b=lVxSZQvsk8h6FKbJ5CJOG5Lgu79L7Dm6Ut89wR+yGf8P8bH/8+VvDxevBD3GuRbRE19pPTNYSFyt7S8oapiW+K5QhNOA7fZn7grFbFpYm140CDxBIQmVBTc3SR6Kov0/;
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 1SXYOO-0004kx-89; Thu, 24 May 2012 08:47:56 -0500
Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4)
	with esmtpa id 1337867266-3288-3287/5/24; Thu, 24 May 2012 13:47:46
	+0000
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
To: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org
References: <op.wbwe9s0k34t2sn@tech304> <op.wen3bwws34t2sn@tech304>
	<490F2075-3E4D-4F85-9935-937CED8FB10B@averesystems.com>
	<op.wen42clw34t2sn@tech304>
	<CAJ-Vmoneopo8xNpThbewfE2tg6HrdH74DXurO38P_aVs=YS9+A@mail.gmail.com>
Date: Thu, 24 May 2012 08:47:46 -0500
Mime-Version: 1.0
From: Mark Felder <feld@feld.me>
Message-Id: <op.wete9wbq34t2sn@tech304>
In-Reply-To: <CAJ-Vmoneopo8xNpThbewfE2tg6HrdH74DXurO38P_aVs=YS9+A@mail.gmail.com>
User-Agent: Opera Mail/11.64 (FreeBSD)
X-SA-Score: -1.5
Cc: Adrian Chadd <adrian@freebsd.org>, dene@ilovedene.com
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, 24 May 2012 13:47:58 -0000

On Wed, 23 May 2012 17:30:40 -0500, Adrian Chadd <adrian@freebsd.org>  
wrote:

> Hi,
>
> can you please, -please- file a PR? And place all of the above
> information in it so we don't lose it?
>

I'd be glad to post a PR and assist in helping to get it permanently  
fixed. I certainly don't want this data to get lost and honestly our  
business uses FreeBSD on VMWare so much that we really need a permanent  
fix as much as anyone else :-)

The reason I've hesitated to post a PR so far is that I didn't have any  
truly useful or concrete evidence of where the problem lies. After Dane  
Foster contacted me and told me he could recreate the crash on demand with  
his workload it was easier to narrow things down. The suggestion that it  
was an interrupts issue (by possibly Bjoern Zeeb?) and Dane's discovery  
that his crashes ceased when em0 and mpt0 share an IRQ, but em0 is  
completely unused was starting to prove there is some strong evidence here  
in favor of the interrupts issue.

Dane, what's the status on your end? Has your fix still been successful?  
Is it also stable if you simply set hint.mpt.0.msi_enable="1" ?


Thanks!