From owner-freebsd-current Tue Nov 30 10: 4:17 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 E9015159B7; Tue, 30 Nov 1999 10:03:52 -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 LAA09592; Tue, 30 Nov 1999 11:03:51 -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 LAA03491; Tue, 30 Nov 1999 11:04:27 -0700 (MST) Message-Id: <199911301804.LAA03491@harmony.village.org> To: Mike Smith Cc: Nick Hibma , FreeBSD CURRENT Mailing List In-reply-to: Your message of "Tue, 30 Nov 1999 09:40:56 PST." <199911301740.JAA02860@mass.cdrom.com> References: <199911301740.JAA02860@mass.cdrom.com> Date: Tue, 30 Nov 1999 11:04:27 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911301740.JAA02860@mass.cdrom.com> Mike Smith writes: : If I'm correct, this is just an ordering issue; the driver has to be shut : down _before_ the slot, not afterwards. Right. The code that is doing the shutdown is trying to shutdown the driver, but that doesn't seem to be happening. The other possibility is that it is happening, but the interrupt handler isn't getting removed due to a bug in that code. I sure miss my laptop.. :-<. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message