From owner-freebsd-current@FreeBSD.ORG Tue Jul 11 15:02:11 2006 Return-Path: X-Original-To: freebsd-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 6EB4216A4DA; Tue, 11 Jul 2006 15:02:11 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5F1E43D5F; Tue, 11 Jul 2006 15:02:08 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k6BF1qGd075013; Tue, 11 Jul 2006 11:02:04 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 11 Jul 2006 10:11:51 -0400 User-Agent: KMail/1.9.1 References: <20060711053000.94DB016A4E1@hub.freebsd.org> In-Reply-To: <20060711053000.94DB016A4E1@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607111011.52520.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Tue, 11 Jul 2006 11:02:07 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1591/Mon Jul 10 15:41:02 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Bill Paul Subject: Re: if_re does not work 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, 11 Jul 2006 15:02:11 -0000 On Tuesday 11 July 2006 01:30, Bill Paul wrote: > > Hi all, > > > > I have two CardBus card with RealTek 8169SB as follows: > > > > NETGEAR GA511 > > Buffalo LPC-CB-CLGT > > > > But they act up from revision 1.68 of if_re.c. > > This has nothing to do with the re(4) driver. The problem is that > the cardbus code is not allocating an interrupt resource for the device: > > > It is a log of NETGEAR GA511 inserting to ThinkPad X40. > > It sure is. > > > Jul 10 22:54:33 x40 kernel: re0: port 0x3000-0x30ff mem 0xd0211000-0xd02111ff at device 0.0 on cardbus0 > > Note that there is no 'irq' mentioned anywhere in this line, which is why > you get this error: > > > Jul 10 22:54:33 x40 kernel: re0: couldn't set up irq > > If you really think this is related to the driver, prove it: back out > the changes (while keeping the rest of your kernel the same) and see if > it works again. I don't think it will. In theory the bus_alloc_resource(.., SYS_RES_IRQ, ...) should route an interrupt for the re0 device but it won't show up in the probe line in that case since the probe line is printed before re_attach() is called. In fact, in the failing case, it wasn't bus_alloc_resource() that failed, but bus_setup_intr(). This is most likely not an re0 issue however. goto-san, can you add printf's to i386/i386/intr_machdep.c:intr_add_handler() and kern/kern_intr.c:intr_event_add_handler() to see which of the EINVAL cases is being triggered? -- John Baldwin