From owner-freebsd-arch Wed Oct 27 1: 5:37 1999 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 67B9D152C4 for ; Wed, 27 Oct 1999 01:05:31 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id KAA02802 for ; Wed, 27 Oct 1999 10:05:29 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id KAA24983 for freebsd-arch@freebsd.org; Wed, 27 Oct 1999 10:05:28 +0200 (MET DST) Received: from habanero.netmonger.net (host2.elkay.on.yiff.net [209.54.22.163]) by hub.freebsd.org (Postfix) with ESMTP id 0130015321 for ; Wed, 27 Oct 1999 01:05:11 -0700 (PDT) (envelope-from chris@habanero.netmonger.net) Received: (from chris@localhost) by habanero.netmonger.net (8.9.3/8.9.3) id EAA00606 for freebsd-arch@freebsd.org; Wed, 27 Oct 1999 04:05:10 -0400 (EDT) (envelope-from chris) Date: Wed, 27 Oct 1999 04:05:10 -0400 From: Christopher Masto To: freebsd-arch@freebsd.org Subject: Re: Racing interrupts Message-ID: <19991027040510.A534@netmonger.net> References: <199910260105.TAA16714@mt.sri.com> <199910260221.TAA26021@usr06.primenet.com> <199910260356.VAA17204@mt.sri.com> <3815F2A0.FA3442F4@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <3815F2A0.FA3442F4@softweyr.com>; from Wes Peters on Tue, Oct 26, 1999 at 12:27:44PM -0600 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Given where we are right now in -current, would it be sensible to consider finding a way to disable devices before ejecting them? I'm plenty willing to have to "shut down" a card before removing it, but having no way to do so at the moment, I will shortly be fully shutting down the laptop I'm writing this on just so I can put it away. To put it another way.. whether the problem is impossible to solve or just very very hard to solve, if a solution is not imminent, it may be time to at least find a workaround. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message