Kernel Bug Tracker – Bug 9032
Cannot unload agpgart module
Last modified: 2009-03-24 04:58:38 UTC
Most recent kernel where this bug did not occur: cannot say, I am trying to confirm whether bug #2913 still exists.
Hardware Environment: ASUS L3C/S laptop, P4, Radeon 7500M
Software Environment: vanilla 188.8.131.52
I went to singleuser mode, but my system picked up the modules so they got loaded and placed me into singleuser. I went to unload all the modules, in which I succeeded except two modules: agpgart and intel_agp. agpgart should be unused
but it claims it is being used. How can I find who is using it? I
Steps to reproduce:
Created attachment 12845 [details]
cannot unload agpgart nor intel_agp
Created attachment 12846 [details]
forcing agpgart unload causes oops
BTW, my HW setup is normally detected as:
Linux agpgart interface v0.102 (c) Dave Jones
agpgart: Detected an Intel 845G Chipset.
agpgart: AGP aperture is 256M @ 0xe0000000
[drm] Initialized drm 1.1.0 20060810
[drm] Initialized radeon 1.27.0 20060524 on minor 0
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
[drm] Setting GART location based on new memory map
[drm] writeback test succeeded in 2 usecs
I think there were relevant fixes made by Dave Jones since.
Martin, have you tried using recent kernel, is the problem still there?
Ping... I am tending to close this bug soon, so "silence is consent" :)
I have unloaded all modules except these two by rmmod command:
Module Size Used by
intel_agp 23316 1
agpgart 31280 1 intel_agp
I tried to force removal of agpgart but it said something about temporarily disabling of the device/module but it remained in the module list and nothing got apparently logged by syslog. I had to force removal of intel_agp and only then I have succeeded in removing agpgart (without forcing). And, no kernel crash (184.108.40.206).
Created attachment 15135 [details]
"ps -ef" and "lsof" outputs
I have no idea why I had to force unloading of intel_agp. I don't think it was opened.
Created attachment 15136 [details]
/proc/config from running kernel 220.127.116.11
Closing out old stale bugs. If this in error please re-open