Date: Mon, 29 Jul 2002 05:20:04 -0700 (PDT) From: John Baldwin <jhb@FreeBSD.org> To: freebsd-doc@FreeBSD.org Subject: RE: docs/41104: Stale comment removal from pccardd(8) Message-ID: <200207291220.g6TCK4Uf044103@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR docs/41104; it has been noted by GNATS.
From: John Baldwin <jhb@FreeBSD.org>
To: Hiten Pandya <hiten@angelica.unixdaemons.com>, imp@FreeBSD.org
Cc: hiten@uk.FreeBSD.org, FreeBSD-gnats-submit@FreeBSD.org
Subject: RE: docs/41104: Stale comment removal from pccardd(8)
Date: Mon, 29 Jul 2002 08:14:34 -0400 (EDT)
On 29-Jul-2002 Hiten Pandya wrote:
>
>>Number: 41104
>>Category: docs
>>Synopsis: Stale comment removal from pccardd(8)
>>Confidential: no
>>Severity: non-critical
>>Priority: low
>>Responsible: freebsd-doc
>>State: open
>>Quarter:
>>Keywords:
>>Date-Required:
>>Class: doc-bug
>>Submitter-Id: current-users
>>Arrival-Date: Sun Jul 28 21:40:01 PDT 2002
>>Closed-Date:
>>Last-Modified:
>>Originator: Hiten Pandya
>>Release: FreeBSD 4.6-STABLE i386
>>Organization:
>>Environment:
>
> Not Applicable.
>
>>Description:
>
> The pccardd(8) manual page holds a very stale comment, which notes
> some (old) facts about how things could mess up with a driver if a
> card was removed; such as freeing the private data structures etc.
>
> This note is pre-{lkm,kld} times, so it nows needs to be removed.
>
> NOTE: There is still a note in the BUGS section, about how things
> can really fry, if system resources have been allocated, for e.g.
> Network Mounted Filesystems; I _explicitly_ did not remove this
> comment, as I was not sure about this.
>
> Please do not hesitate to comment on this patch:
> hiten@uk.FreeBSD.org
>
> Thanks.
>
> -- Hiten
> -- http://www.unixdaemons.com/~hiten
Unfortunately using KLD's does not fix this problem and it is still an
issue. I can't eject my cardbus rl0 card w/o my laptop locking up for
exactly this reason. This patch should not be committed unless Warner
(imp@, cc'd) approves.
>>Fix:
>
> Apply this patch to pccard(8), from 'src/'. This patch CAN be
> MFC'ed as it does apply to -STABLE releases as well. Heck!, it
> applies to any release which can do loadable kernel modules. :-)
>
> Index: usr.sbin/pccard/pccardd/pccardd.8
> ===================================================================
> RCS file: /home/ncvs/src/usr.sbin/pccard/pccardd/pccardd.8,v
> retrieving revision 1.26
> diff -u -r1.26 pccardd.8
> --- usr.sbin/pccard/pccardd/pccardd.8 2002/07/14 14:44:49 1.26
> +++ usr.sbin/pccard/pccardd/pccardd.8 2002/07/29 04:15:31
> @@ -110,18 +110,6 @@
> Once a card/driver instance is configured, the resources
> bound to that instance are remembered, and if the card is removed
> and reinserted, the same driver is allocated.
> -The primary reason
> -is that once a driver is associated with a card, the
> -driver's
> -.Fn probe
> -routine has been called, and this usually causes driver specific
> -data areas to be initialized with the I/O ports or memory resources
> -allocated to the card.
> -Most drivers are not designed to be
> -disassociated from the hardware and then reassociated with different
> -parameters.
> -This will change significantly when loadable kernel
> -modules are supported.
> .Pp
> SIGHUP causes
> .Nm
--
John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200207291220.g6TCK4Uf044103>