From owner-freebsd-current@FreeBSD.ORG Tue May 26 16:37:35 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8C009D37; Tue, 26 May 2015 16:37:35 +0000 (UTC) (envelope-from jenkins-admin@freebsd.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 7CAD6D1D; Tue, 26 May 2015 16:37:35 +0000 (UTC) (envelope-from jenkins-admin@freebsd.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id A2EB37D2; Tue, 26 May 2015 16:37:35 +0000 (UTC) Date: Tue, 26 May 2015 16:37:35 +0000 (GMT) From: jenkins-admin@freebsd.org To: jenkins-admin@FreeBSD.org, freebsd-current@freebsd.org Message-ID: <1692601331.74.1432658255624.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_HEAD-tests - Build #1061 - Unstable MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_HEAD-tests X-Jenkins-Result: UNSTABLE Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2015 16:37:35 -0000 FreeBSD_HEAD-tests - Build #1061 - Unstable: Check console output at https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1061/ to view the results. From owner-freebsd-current@FreeBSD.ORG Tue May 26 18:45:46 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 52EC1698; Tue, 26 May 2015 18:45:46 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-qg0-x230.google.com (mail-qg0-x230.google.com [IPv6:2607:f8b0:400d:c04::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0DA11278; Tue, 26 May 2015 18:45:46 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by qgfa63 with SMTP id a63so67508574qgf.0; Tue, 26 May 2015 11:45:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bIPOHBDjd5YztiLesc+4CvYK+31eP8PdBN7F0xs+1Cs=; b=ZzpVhMP4vsScx7R0Jp15pxPw8R2sY2cM6sRfsJRoIsf1uhxUirQleJ3oL48zD9iLHC O1fbW8VbW0B8+QBTsWNwu1+Y7mSRogg7wIWch22IRFql9DxUJE1fMjF9soCuu3YywIpm GFZ+jOgZUz3j8an/BEhrg/O6PqTiP8ymaWjxP/3Op3NJw5Z3fJJLwFrIIkPxaCN6pK/R hOlcvxUqklbvTz27gNANUBt5ymdRrfMxGC5CrL2AROo2kjHzkvxYKAzw3Ru5X9uUxJRA w4AMF55UThq30Bj2XxcrpNnekzgA0F62o9g686u/PrxRDQ0aWbMiMUoExf5uSPjt6I0/ 5Yiw== MIME-Version: 1.0 X-Received: by 10.55.20.136 with SMTP id 8mr44322575qku.8.1432665945203; Tue, 26 May 2015 11:45:45 -0700 (PDT) Received: by 10.140.98.73 with HTTP; Tue, 26 May 2015 11:45:45 -0700 (PDT) In-Reply-To: References: <28845361-E624-4CB9-B255-1B2C1FD0DF28@gmail.com> <4BEE0A54-3AD2-42DB-AF4E-2B0A5E34DF4E@gmail.com> <553F3CA7.9090601@FreeBSD.org> <9FBE053A-971A-433E-9B88-D62CF9273CFB@gmail.com> Date: Tue, 26 May 2015 11:45:45 -0700 Message-ID: Subject: Re: cam(4) timeouts in bhyve/kyua runs up on Jenkins? From: NGie Cooper To: Neel Natu Cc: Alexander Motin , FreeBSD Current , "freebsd-testing@freebsd.org" , Peter Grehan Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2015 18:45:46 -0000 Hi Neel, On Tue, May 26, 2015 at 9:06 AM, Neel Natu wrote: > Hi NGie, ... > Can you try to reproduce with a virtio-blk instead of ahci-hd? > > It will help narrow down the problem because both ahci-hd and > virtio-blk emulations share a common backend to read/write to the > disk. You'll have to ask Craig. I don't run BHyve at all, and I don't think that running BHyve over VMware Fusion would be the best "proof of concept" for determining whether or not there's an issue here as VMware Fusion suffers timeouts on occasion with mpt(4) under high load.. Thanks!