I use vanilla 2.6.10 (from kernel.org) and drm cvs of 30/01/2005 (so it includes the recent drm fixes) on a radeon 7000. When I modprobe radeon.ko from linux-core, the machine locks up (I can still ping it, but I can't ssh in the box so it looks like it's stuck somewhere in kernel). However, it works fine if I use the linux-2.6 (non core) version. When this happens, I don't find anything in /var/log/messages after a reboot.
Actually, this is not specific to radeon. I tried insmod'ing other card-specific modules and it also lockups. Also, when I print the address for the radeon_exit function, it's the same as drm_init. So it looks like when radeon_init is called, it lockups by calling itself again and again. Still there with current drm cvs (22/04/2005), btw.
Oops, did I say radeon_exit ? I meant radeon_init has the same address as drm_init. Obviously it never makes it to radeon_exit...
Ok, thanks to Benno Schulenberg for pointing me to this : You need to have CONFIG_HOTPLUG set or the card-specific modules crash on insmod. Does this ring a bell to anyone ? What's the proper fix ? Make drm dependent on hotplug ?
Does this still occur for you in newer kernels? Please let us know.
Created attachment 4236 [details] [review] Proposed fix Looks like this might do the trick (thanks OgreBoy !)
thanks committed.. thanks be to God I never moved that into the kernel....
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.