From owner-freebsd-questions@FreeBSD.ORG Wed May 23 22:30:41 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 49CF1106566B; Wed, 23 May 2012 22:30:41 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 15FF78FC16; Wed, 23 May 2012 22:30:41 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so11375724pbb.13 for ; Wed, 23 May 2012 15:30:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=9L2OEEm7OzRSx51qsNQvE2zo3+P2eulW0CuhLkKhV2s=; b=YH2839Ku+L4mfBNa+gvGNFWwATdKQn1QtQ29lebaEW+tdVaverM20DYVkkrmZNJ4ye reAYRtwUChOQMERYdVJrbfifqMJawHBgQOK3gJ1jwSQkAi/TjmIJhgWVAjhwIy3c2kUl hefNk7nM20rHJSa+qHFylPkp9jSlNoOWKAFhxziyTzvEd3BvrRl3BqtxFug+Ldsot7z4 b2xRaanwLFfl/RLqCPQow/ocB4NP2wVuojAWtULLGKky/dYqsZlb/Pk96QAUjork+r54 YvtF/LLi6SQBVVzMiuvXts1ufdz5A6wcJ4H/RW1UuSA8Wk9C3dLqDLKlwzpB6wh/PDbz ETDw== MIME-Version: 1.0 Received: by 10.68.232.129 with SMTP id to1mr5075523pbc.27.1337812240616; Wed, 23 May 2012 15:30:40 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.142.203.2 with HTTP; Wed, 23 May 2012 15:30:40 -0700 (PDT) In-Reply-To: References: <490F2075-3E4D-4F85-9935-937CED8FB10B@averesystems.com> Date: Wed, 23 May 2012 15:30:40 -0700 X-Google-Sender-Auth: hc1bGub3x6XFJXxtcw9PwZuAOiA Message-ID: From: Adrian Chadd To: Mark Felder Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2012 22:30:41 -0000 Hi, can you please, -please- file a PR? And place all of the above information in it so we don't lose it? If this is indeed the problem then I really think we should root cause why the driver and/or interrupt handling code is getting angry with the shared interrupt. I'd also appreciate it if you and the other people who can reproduce this could work with the em/mpt driver people and root cause why this is going. I think having FreeBSD on vmware work stable out of the box without these kinds of tweaks is the way to go - who knows what else is lurking here.. I'm very very glad you've persisted with this and if I had them, I'd send you a "FreeBSD persistent bug reporter!" t-shirt. Thanks, Adrian