From owner-freebsd-mobile Sat Nov 1 18:15:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA21855 for mobile-outgoing; Sat, 1 Nov 1997 18:15:44 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA21840 for ; Sat, 1 Nov 1997 18:15:27 -0800 (PST) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id TAA04418; Sat, 1 Nov 1997 19:15:12 -0700 (MST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id TAA00954; Sat, 1 Nov 1997 19:15:11 -0700 (MST) Date: Sat, 1 Nov 1997 19:15:11 -0700 (MST) Message-Id: <199711020215.TAA00954@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Brian N. Handy" Cc: Guido van Rooij , freebsd-mobile@freebsd.org Subject: Re: card removal problems In-Reply-To: References: <199711012332.AAA01014@gvr.gvr.org> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > When I put my > 3C589D on the network, it would wedge in this same manner -- usually > beeping steadily until I powered the TP560 down. So I agree that there > are still problems out there... Some of these 'problems' are hard to get around, since interrupts are still happening when the the card is pulled, so the kernel doesn't know that the hardware doesn't exist. This causes lockups in Win95 as well as many other OS's as well, although it happens *rarely* on my box even when on the network. I may be 'disabling' in the wrong order which makes the race condition easier to find, so I'd like to find out where it's dying/hanging if possible. Nate