From owner-freebsd-current@FreeBSD.ORG Wed Mar 24 13:42:41 2004 Return-Path: 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 20BF916A4CE for ; Wed, 24 Mar 2004 13:42:41 -0800 (PST) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09B2F43D4C for ; Wed, 24 Mar 2004 13:42:41 -0800 (PST) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465 for ; Wed, 24 Mar 2004 13:42:40 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 1C70D5D08 for ; Wed, 24 Mar 2004 13:42:40 -0800 (PST) To: current@freebsd.org Date: Wed, 24 Mar 2004 13:42:40 -0800 From: "Kevin Oberman" Message-Id: <20040324214240.1C70D5D08@ptavv.es.net> Subject: Regression in CardBus X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 24 Mar 2004 21:42:41 -0000 I am running current as of last Saturday (3/13). On a recent trip I had to dial in to work at the airport. I inserted my trusty Xircom RBEM56G-100 combo Ethernet/modem card which I have been using for over a year on current, but have not used for several months. I get the following messages on insertion: dc0: port 0x1100-0x117f mem 0x20000000-0x200007ff,0x20000800-0x20000fff irq 11 at device 0.0 on cardbus1 miibus1: on dc0 tdkphy0: on miibus1 tdkphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:10:a4:e0:07:4f sio4: configured irq 11 not in bitmap of probed irqs 0 sio4: port may not be enabled sio4: configured irq 11 not in bitmap of probed irqs 0 sio4: port may not be enabled cardbus1: at device 0.1 (no driver attached) Huh? All PCMCIA cards share the same IRQ and to works OK for the Ethernet, but not the serial interface. It behaved just fine in the past. Due to the LONG time since I last ran it (possibly not sine last September), it will likely take me a while to track down just when it broke, so I'm hoping that someone has an idea that could save me some time. I don't recall seeing this reported, although there are reports of some problems with sio devices that might be related. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634