| Summary: | Lockup using linux-core on radeon | ||||||
|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Stephane Marchesin <marchesin> | ||||
| Component: | DRM/other | Assignee: | Default DRI bug account <dri-devel> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | high | ||||||
| Version: | DRI git | ||||||
| Hardware: | x86 (IA32) | ||||||
| OS: | Linux (All) | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
|
Description
Stephane Marchesin
2005-01-29 16:30:10 UTC
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.