From owner-freebsd-current@FreeBSD.ORG Thu Sep 20 17:47:04 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C64C91065672; Thu, 20 Sep 2012 17:47:03 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 9A42D8FC15; Thu, 20 Sep 2012 17:47:03 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id BA289B9A6; Thu, 20 Sep 2012 13:47:02 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org, mexas@bristol.ac.uk Date: Thu, 20 Sep 2012 08:50:05 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <201209200853.q8K8rULv012675@mech-cluster241.men.bris.ac.uk> In-Reply-To: <201209200853.q8K8rULv012675@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201209200850.05063.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 20 Sep 2012 13:47:02 -0400 (EDT) Cc: freebsd-ia64@freebsd.org Subject: Re: ia64 panic: make_dev_credv: bad si_name (error=17, si_name=pass3) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 20 Sep 2012 17:47:04 -0000 On Thursday, September 20, 2012 4:53:30 am Anton Shterenlikht wrote: > On ia64 r235474 I added another > disk and did "camcontrol rescan all" > to see it. I got this panic: > > panic: make_dev_credv: bad si_name (error=17, si_name=pass3) 17 is EEXIST. It seems you still had a pass3 device present (that is the root cause of this panic). Presumably you pulled a disk first and that didn't get cleaned up properly? Either that or CAM is trying to use the same name for two devices for some reason. -- John Baldwin