From owner-freebsd-mobile  Sat Nov  1 18:11:41 1997
Return-Path: <owner-freebsd-mobile>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA21647
          for mobile-outgoing; Sat, 1 Nov 1997 18:11:41 -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 SAA21641
          for <freebsd-mobile@freebsd.org>; Sat, 1 Nov 1997 18:11:35 -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 TAA04390;
	Sat, 1 Nov 1997 19:11:33 -0700 (MST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id TAA00945; Sat, 1 Nov 1997 19:11:32 -0700 (MST)
Date: Sat, 1 Nov 1997 19:11:32 -0700 (MST)
Message-Id: <199711020211.TAA00945@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Guido van Rooij <guido@gvr.org>
Cc: freebsd-mobile@freebsd.org
Subject: Re: card removal problems
In-Reply-To: <199711012332.AAA01014@gvr.gvr.org>
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

> Just like with the PAO release I experience problems when removing a
> card from a slot. Sometimes this results in a total lockup of the
> system, while it keeps beeping.

There is a race where it's possible that the driver in in use when you
remove it that is un-avoidable.  But, this seems to happen pretty
rarely.

> With the PAO release, the solution was to fist cut power from the card and
> then remove it. This was done via the power subcommand of pccardc.
> Wouldn;t it be wise to introduce that subcommand? Or am I the only
> one experiencing problems when removing cards?

I'd like to introduct as few things *as necessary* to the release, but
if it's necessary then we should add it.  Too many 'fixes' that went
into PAO tree that masked the real problem, so before we add the power
let's try and figure out what the problem is.


Nate