From owner-freebsd-current@FreeBSD.ORG Tue Aug 16 13:18:07 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 6CB2B16A41F for ; Tue, 16 Aug 2005 13:18:07 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD3E843D46 for ; Tue, 16 Aug 2005 13:18:06 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by rosebud.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id j7GDI5EW014273 for ; Tue, 16 Aug 2005 16:18:05 +0300 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id j7GCjQMk031593 for ; Tue, 16 Aug 2005 15:45:26 +0300 (EEST) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id j7GCjQWY031592 for freebsd-current@freebsd.org; Tue, 16 Aug 2005 15:45:26 +0300 (EEST) (envelope-from keramida@freebsd.org) Date: Tue, 16 Aug 2005 15:45:26 +0300 From: Giorgos Keramidas To: freebsd-current@freebsd.org Message-ID: <20050816124525.GA31411@flame.pc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: 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 13:18:07 -0000 I've recently acquired a 3Com 3CSOHO100B-TX NIC, which seems to be supported by the ``dc'' driver. The output of pciconf is: % none0@pci0:10:0: class=0x020000 card=0x930010b7 chip=0x930010b7 rev=0x31 hdr=0x00 % vendor = '3COM Corp, Networking Division' % device = '3C910 Integrated Fast Ethernet Controller (3CSOHO100B-TX Compatible)' % class = network % subclass = ethernet 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? - Giorgos