Re: [drm:drm_init] *ERROR* Cannot initialize the agpgart module.

[Rusty Russell]

In message <[e-mail]> you write:
> On Fri, Dec 20, 2002 at 06:29:18PM -0500, Ed Tomlinson wrote:
>  > Dave, with the pull from this morning (8am EST), it almost works modular.
>  > I get:
>  > 
>  > Dec 20 18:20:19 oscar upsd[636]: Communication established
>  > Dec 20 18:20:47 oscar kernel: Linux agpgart interface v0.100 (c) Dave Jone
s
>  > Dec 20 18:20:47 oscar kernel: agpgart: Detected VIA MVP3 chipset
>  > Dec 20 18:20:47 oscar kernel: agpgart: AGP aperture is 64M @ 0xe0000000
>  > Dec 20 18:20:58 oscar kernel: [drm] Initialized mga 3.1.0 20021029 on mino
r 0
>  > Dec 20 18:20:58 oscar kernel: Module agpgart cannot be unloaded due to uns
afe usage in drivers/char/ag
>  > p/backend.c:58
> 
> This one is due to the way AGPGART does (or has done for the last 3
> years) its module locking. It does a MOD_INC_USE_COUNT as soon as
> someone calls the acquire routines.

Which is racy under SMP, and under preempt, which is why it's
deprecated.

> (So you can't unload agpgart whilst you've a 3d using app (like X)
> open).  This seems quite sensible, but these days you can't unload
> agpgart.ko anyway because the chipset module (via-agp.ko in your
> case) already has it 'in use', so I'm tempted to drop those bits.

If this is true (it usually is), you can simply drop them.  There are
other cases where the caller is not grabbing references, so
MOD_INC_USE_COUNT is better than nothing (should the warning stay for
2.6?  Good question).

Hope that helps,
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.