From owner-freebsd-current@FreeBSD.ORG Tue Aug 16 14:15:57 2005 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 F1DA916A427 for ; Tue, 16 Aug 2005 14:15:56 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from aiolos.otenet.gr (aiolos.otenet.gr [195.170.0.93]) by mx1.FreeBSD.org (Postfix) with ESMTP id 344E843D49 for ; Tue, 16 Aug 2005 14:15:55 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by aiolos.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id j7GEFsu5016980; Tue, 16 Aug 2005 17:15:54 +0300 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id j7GELfrB093174; Tue, 16 Aug 2005 17:21:41 +0300 (EEST) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id j7GELfaO093173; Tue, 16 Aug 2005 17:21:41 +0300 (EEST) (envelope-from keramida@freebsd.org) Date: Tue, 16 Aug 2005 17:21:41 +0300 From: Giorgos Keramidas To: Viren Shah Message-ID: <20050816142141.GK31411@flame.pc> References: <20050816124525.GA31411@flame.pc> <6f230735050816071119a68618@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6f230735050816071119a68618@mail.gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: if_dc panics with 3Com OfficeConnect 10/100B PCI 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, 16 Aug 2005 14:15:57 -0000 On 2005-08-16 10:11, Viren Shah wrote: >On 8/16/05, Giorgos Keramidas wrote: > >> When I compile the ``dc'' driver into my kernel or load it as a module >> though, a relatively recent CURRENT (updated yesterday, 14 Aug 2005) >> panics after a port mapping failure. >> >> The same panic happens when the device is configured into the kernel or >> when I kldload if_dc. Is anyone else using ``dc'' interfaces on CURRENT >> and seeing similar problems? > > I'm running a -current kernel from today morning just fine. Cool. Thanks for the reply. I'll try to obtain a kernel backtrace, since this seems to be broken on my setup in both in-kernel and module cases.