From owner-freebsd-current@FreeBSD.ORG Tue Sep 20 19:24:29 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88C8616A41F for ; Tue, 20 Sep 2005 19:24:29 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F8CC43D45 for ; Tue, 20 Sep 2005 19:24:29 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j8KJN7R5040867; Tue, 20 Sep 2005 13:23:15 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 20 Sep 2005 13:23:26 -0600 (MDT) Message-Id: <20050920.132326.76562879.imp@bsdimp.com> To: haro@h4.dion.ne.jp From: "M. Warner Losh" In-Reply-To: <20050921.013052.74756148.haro@h4.dion.ne.jp> References: <20050921.013052.74756148.haro@h4.dion.ne.jp> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Tue, 20 Sep 2005 13:23:17 -0600 (MDT) Cc: current@freebsd.org Subject: Re: Panic with recent PCcard changes 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: Tue, 20 Sep 2005 19:24:29 -0000 In message: <20050921.013052.74756148.haro@h4.dion.ne.jp> Munehiro Matsuda writes: : pccard1: <16-bit PCCard bus> on cbb1 ========^===== 1 : panic: make_dev() by driver pccard on pre-existing device (min=0, : name=pccard0.cis) =============^==== 0 I wonder why sc->cisdev = make_dev(&pccard_cdevsw, 0, 0, 0, 0666, "pccard%u.cis", device_get_unit(sc->dev)); device_get_unit is returning 0 instead of 1 for the second device. haro-san, if you could add some debugging information to try to find out why this is the case, that would be helpful. My laptop only has one pccard/cardbus slot, so I didn't run into this or even think it would be a problem... Warner