From owner-freebsd-bugs@FreeBSD.ORG  Wed Jan 14 17:41:28 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@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 6EE06F85
 for <freebsd-bugs@FreeBSD.org>; Wed, 14 Jan 2015 17:41:28 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 571ECC1
 for <freebsd-bugs@FreeBSD.org>; Wed, 14 Jan 2015 17:41:28 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t0EHfSN6018370
 for <freebsd-bugs@FreeBSD.org>; Wed, 14 Jan 2015 17:41:28 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 195349] CAM status: Command timeout since upgrade to 10.1
Date: Wed, 14 Jan 2015 17:41:23 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: nk@nk99.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-195349-8-QvryexRNQs@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-195349-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-195349-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jan 2015 17:41:28 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195349

--- Comment #28 from Nerijus <nk@nk99.org> ---
(In reply to Edward Tomasz Napierala from comment #27)
As per my comment #23
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195349#c23) I did have an
issue and it did not seem to be very predictable. :) I have one server with the
setting in loader.conf (and rebooted) and another without. Both running 10.1.
So far (a bit over 10 days) both are running without those errors. And I'm
wondering if that setting has any effect and how do I verify it is set?

-- 
You are receiving this mail because:
You are the assignee for the bug.