Summary: | Can't start compiz: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Andreas Happe <andreashappe> | ||||||
Component: | DRM/other | Assignee: | Default DRI bug account <dri-devel> | ||||||
Status: | RESOLVED FIXED | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | high | ||||||||
Version: | XOrg git | ||||||||
Hardware: | x86 (IA32) | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
Andreas Happe
2006-12-25 03:51:46 UTC
(In reply to comment #0) > [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held > [drm:drm_unlock] *ERROR* Process 2112 using kernel context 0 These are just symptoms of the DRI not being enabled. Please attached (as opposed to paste) the full X config and log files for diagnosis. Created attachment 8209 [details]
/var/log/Xorg.0.log
You were right, AGP doesn't seem to be enabled, but dmesg says:
| Linux agpgart interface v0.101 (c) Dave Jones
| [drm] Initialized drm 1.1.0 20060810
| agpgart: Detected an Intel 855PM Chipset.
| agpgart: AGP aperture is 256M @ 0xb0000000
| [drm] Initialized radeon 1.25.0 20060524 on minor 0
maybe disabling parallel pci scanning might solve this, I am testing right now.
Created attachment 8210 [details]
My xorg.conf
Okay, disabling multithreaded pci discovery in the kernel made things work again. Is this an error that should be reported to lkml or is this already the right place for this? It seems that the AGPGart module is loaded 'in parallel' with the DRI module and this explodes when Xorg tries to enable DRI. Maybe a better worded error message in the dmesg output might help others. Thanks for your help, Andreas Happe I think it would certainly be interesting to hear the kernel developers' opinion on this. It seems like that PCI multithread probing will be removed from 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.