To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Dave Jones <davej@codemonkey.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: agpgart.ko can't be unloaded
References: <m3acf2i05d.fsf@defiant.localdomain>
	<m31x0ehz8m.fsf@defiant.localdomain>
	<1134783072.7402.2.camel@localhost.localdomain>
From: Krzysztof Halasa <khc@pm.waw.pl>
Date: Sat, 17 Dec 2005 16:16:27 +0100
In-Reply-To: <1134783072.7402.2.camel@localhost.localdomain> (Rusty
 Russell's message of "Sat, 17 Dec 2005 12:31:12 +1100")
Message-ID: <m3d5jvda9g.fsf@defiant.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 668
Lines: 19

Rusty Russell <rusty@rustcorp.com.au> writes:

> That can happen; "rmmod -w" will block until it's no longer used.  Still
> used, still waiting.
>
> Looks from these refcounts that intel_agp is being used.  Who is holding
> the refcount?

That's another story - they have deadlocked wrt refcounts, that's why
rmmod is waiting so hard.

I'd expect the rmmod to be interruptible, though. Thanks for info.
-- 
Krzysztof Halasa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/