From owner-freebsd-bugs@FreeBSD.ORG Fri Jul 30 19:10:56 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 158ED16A4CE for ; Fri, 30 Jul 2004 19:10:56 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AC1543D58 for ; Fri, 30 Jul 2004 19:10:56 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i6UJAMWO070452 for ; Fri, 30 Jul 2004 19:10:22 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i6UJAIvP070413; Fri, 30 Jul 2004 19:10:18 GMT (envelope-from gnats) Date: Fri, 30 Jul 2004 19:10:18 GMT Message-Id: <200407301910.i6UJAIvP070413@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: "Morris, Joseph C" Subject: Re: kern/69158: Cisco MPI350 problems related to irq sharing X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Morris, Joseph C" List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2004 19:10:56 -0000 The following reply was made to PR kern/69158; it has been noted by GNATS. From: "Morris, Joseph C" To: Cc: Subject: Re: kern/69158: Cisco MPI350 problems related to irq sharing Date: Fri, 30 Jul 2004 13:57:46 -0500 Just a brief update. I just downloaded the latest snapshot from = 5-CURRENT (July 30, 2004). My system has not had any hard lock-ups, but = my Cisco card does go down frequently when something is plugged into = uhci2, since they both share the same irq. When running ifconfig, it = reports "status: no carrier" still. Usually unloading and reinserting = the if_an module brings it back up for a little bit, but if anything is = plugged into uhci2 the wireless connection is guaranteed to be lost at = some point. I no longer get any odd kernel messages, but the problem = still stands: if a device is using the same irq that the Cisco card is = using, the wireless connection is guaranteed to be lost. Thanks guys! jcm