Re: kldunload DIAGNOSTIC idea...

From: Poul-Henning Kamp (phk_at_phk.freebsd.dk)
Date: 07/21/04

  • Next message: Julian Elischer: "Re: kldunload DIAGNOSTIC idea..." 
    To: David Schultz <das@FreeBSD.ORG>
Date: Wed, 21 Jul 2004 08:44:33 +0200

    In message <20040720203739.GA72252@VARK.homeunix.com>, David Schultz writes:

    >> Looking for sleep addresses inside the module might make sense too.
    >
    >But this is just a heuristic that may sometimes fail. The module
    >might be holding resources or locks, it could have callbacks, etc.
    >If we're going to offer a forcible unload option, [...]

    This has _nothing_ to do with forcible unload.

    Please read the subject, again if necessary.

    This is an idea for a debug tool which may help people properly
    debug and implement unload *in general*. 

    -- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
  • Next message: Julian Elischer: "Re: kldunload DIAGNOSTIC idea..."