Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751012AbVLOUTN (ORCPT ); Thu, 15 Dec 2005 15:19:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751015AbVLOUTN (ORCPT ); Thu, 15 Dec 2005 15:19:13 -0500 Received: from khc.piap.pl ([195.187.100.11]:15876 "EHLO khc.piap.pl") by vger.kernel.org with ESMTP id S1751012AbVLOUTM (ORCPT ); Thu, 15 Dec 2005 15:19:12 -0500 To: Dave Jones Cc: Subject: agpgart.ko can't be unloaded From: Krzysztof Halasa Date: Thu, 15 Dec 2005 21:19:10 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 963 Lines: 28 Hi, I recently noticed that agpgart.ko (and corresponding hardware driver) can't be unloaded: Module Size Used by intel_agp 19228 1 agpgart 27592 1 intel_agp The same is true for via_agp and probably for all other drivers. The problem is agpgart increases reference count of hw driver to prevent it from being unloaded, and the hw driver references agpgart so agpgart can't be unloaded either. Should agpgart be split into 2 parts, one (which would have to be unloaded first) managing the thing and the other - the library referenced by hw drivers? I wouldn't write about this but there is code to unload them so I think it's not intentional. -- 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/