From owner-freebsd-questions@FreeBSD.ORG Wed Mar 28 23:31:40 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 5F0D4106566B; Wed, 28 Mar 2012 23:31:40 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 08C138FC17; Wed, 28 Mar 2012 23:31:39 +0000 (UTC) Received: by ggnk4 with SMTP id k4so1404121ggn.13 for ; Wed, 28 Mar 2012 16:31:39 -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=1Ip4r1cb8u+Wb0t3PZzy/VB+ZEJ2ye/i0MpqylcB+mc=; b=KTHB/7mdb51aLnCUxrJGeqKlRsccRBHJolgi4cNHCSo6M34SFFiQ3cahbjV7c/tVbV 3d+0r4XgNl6TwZ72+p9McKJ8WVW28GSHi58ab8IyNzmEE5xQ9BlS76xknhFGKrjjrEH9 M9HHRj4aEUJS7SsHtiqhig1W6T4AMZyVpXXXkxXRCOB6jh1nQMGyudaXvWvxJrEuP5Ta 3U/2n5Qrg6vov0Z5QukTZkw5YSQYxB7SMASr1g39bn4vMXmA6mW0NPUJWYe7s9swHUSS mB3AJLYW1oZi8kR03S1pVmSEapXZjzu0EEstglMFnPSUkmHIVOtpdfkoDW7Rwt1gH2wU Ozcw== MIME-Version: 1.0 Received: by 10.68.240.135 with SMTP id wa7mr518086pbc.7.1332977499034; Wed, 28 Mar 2012 16:31:39 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.143.33.5 with HTTP; Wed, 28 Mar 2012 16:31:38 -0700 (PDT) In-Reply-To: References: Date: Wed, 28 Mar 2012 16:31:38 -0700 X-Google-Sender-Auth: lTqAiQP5uyDsguC_T2A8DbL3tpE 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, 28 Mar 2012 23:31:40 -0000 Hi, * have you filed a PR? * is the crash easily reproducable? * 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? It sounds like you've established it's a storage issue, or at least interrupt handling for storage issue. So I'd definitely try the ramdisk-only boot and thrash it using lighttpd/httperf or something. If that survives fine, I'd look at trying to establish whether there's something wrong in the disk driver(s) freebsd is using. 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. 2c, Adrian