From owner-freebsd-current Tue Nov 30 7:14:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id C49441591F for ; Tue, 30 Nov 1999 07:14:16 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id IAA08822; Tue, 30 Nov 1999 08:14:14 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id IAA02251; Tue, 30 Nov 1999 08:14:49 -0700 (MST) Message-Id: <199911301514.IAA02251@harmony.village.org> To: Nick Hibma Cc: FreeBSD CURRENT Mailing List In-reply-to: Your message of "Tue, 30 Nov 1999 13:02:08 +0100." References: Date: Tue, 30 Nov 1999 08:14:49 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Nick Hibma writes: : The system freezes on powering down a PCCARD slot. From memory the : location is putb1 called from pcic_disable. The freeze is easy to : reproduce, just remove the card. When stepping through the code, even : the debugger prompt does not return after the outb for PCIC_POWER on : line 698 of pcic.c. My first guess was that the driver was getting interrupts at this point. This is true as far as it goes. This likely means that the driver hasn't detached by this point. You might try looking down that path to see if the device_delete_children is really being called, and if so on what. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message