Date: Wed, 27 Oct 1999 14:34:56 -0400 From: Christopher Masto <chris@netmonger.net> To: freebsd-arch@freebsd.org Subject: Re: Racing interrupts Message-ID: <19991027143456.A21292@netmonger.net> In-Reply-To: <38173AF2.BD8D6486@softweyr.com>; from Wes Peters on Wed, Oct 27, 1999 at 11:48:34AM -0600 References: <199910260105.TAA16714@mt.sri.com> <199910260221.TAA26021@usr06.primenet.com> <199910260356.VAA17204@mt.sri.com> <ybuln8ql6gk.fsf@jesup.eng.tvol.net.jesup.eng.tvol.net> <3815F2A0.FA3442F4@softweyr.com> <19991027040510.A534@netmonger.net> <38173AF2.BD8D6486@softweyr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 27, 1999 at 11:48:34AM -0600, Wes Peters wrote: > Christopher Masto wrote: > > > > 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. > > For network cards, we could certainly make "ifconfig down" put the card > into an acceptable state for eject. In fact, it probably already does. Checked that last night.. it locks up even if "ifconfig down"ed. Presumably there's a bug in the eject handling, not in the card disappearing without being disabled. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991027143456.A21292>