Description of problem: I've setup libvnc.so X module and when I connect with vncviewer server completely hangs computer. Version-Release number of selected component (if applicable): rpm -q xorg-x11-drv-ati xorg-x11-drv-ati-6.6.3-2.fc7 How reproducible: always Steps to Reproduce: 1. install vnc-server package 2. add Load "vnc" into module section in xorg.conf 3. add Option "SecurityTypes" "None" into Screen section in xorg.conf 4. start Xorg with radeon driver and be prepare for complete hang 5. run vncviewer into server Actual results: complete hang, computer must be restarted with button Expected results: vnc-ed into server Additional info: this messages are in log Jun 5 19:55:30 traged kernel: [drm:radeon_cp_start] *ERROR* radeon_cp_start called without lock held Jun 5 19:55:30 traged kernel: [drm:radeon_cp_idle] *ERROR* radeon_cp_idle called without lock held Jun 5 19:55:30 traged kernel: [drm:radeon_cp_reset] *ERROR* radeon_cp_reset called without lock held Jun 5 19:55:30 traged kernel: called without lock held
Happened on FC6 too, the first time I've tried sharing the main display
Adam, could we get your /etc/X11/xorg.conf and /var/log/Xorg.0.log as attachments to this bug, please?
Created attachment 156340 [details] My config file
Created attachment 156343 [details] Xorg log before crash
System log repetely says messages which I wrote in original bugreport Adam
The X server always takes the DRI lock when it wakes up. So I don't think that's the problem. Can you attach the dmesg output as well? I suspect foul play in the kernel.
(In reply to comment #6) > Can you attach the dmesg output as well? I suspect foul play in the kernel. I don't know how get dmesg output after hang. Computer locks immediately and I could get debuginfo only from log on disc. As I wrote upper, bunch of messages like kernel: [drm:radeon_cp_start] *ERROR* radeon_cp_start called without lock held kernel: [drm:radeon_cp_idle] *ERROR* radeon_cp_idle called without lock held kernel: [drm:radeon_cp_reset] *ERROR* radeon_cp_reset called without lock held are in log. I could remember that this works about three months ago. I tried install older kernel and this doesn't solve this problem. I didn't do anything with vnc so this looks like driver/X issue. Any hints how get more debuginfo? Adam
Created attachment 156443 [details] dmesg immediately before crash
dmesg has: CPU 0: aperture @ 1a2c000000 size 32 MB Aperture too small (32 MB) Does your BIOS have options for making the video memory aperture larger?
I have the exact same problem as Adam (and started talking to him on the vnc-list). My dmesg doesn't have that warning message. It claims instead: Linux agpgart interface v0.102 (c) Dave Jones agpgart: Detected VIA KT400/KT400A/KT600 chipset agpgart: AGP aperture is 128M @ 0xf0000000 So that may not be the problem. -- Henrique
I did some investigations around this. This is only reproducable when you start X with dri and glx modules. When those modules aren't loaded simulateously all works as expected. Btw my bios is very stupid and it's no way how can I extend video memory aperture Adam
this sounds like some missing block handler or dri lock entry points, in theory the server should always have the lock when it is running... so it must be a wierd vnc interaction..
Has anyone discovered anything on this bug? I am seeing it in a slightly different situation. I have an embedded Linux system with no native X11. I built RPM packages for it based on the Fedora 7 SRPMS. The video chip is an ATI M22. Everything works just fine when DRI is disabled, but with DRI enabled and running glxgears, I see this error message quite often. It is especially prone to happen when moving or resizing the gears window. Sometimes, glxgears just exits; other times the system locks up. The two error messages I get are: [drm:radeon_cp_idle] *ERROR* radeon_cp_idle called without lock held usually repeated several times, then [drm:radeon_irq_emit] *ERROR* radeon_irq_emit called without lock held In addition, I get an error message in the xterm running gears that says: radeonEmitIrqLocked: drmRadeonEmitIrq: -22
I should add the easiest way to reproduce this is to run multiple instances of glxgears. It doesn't show up so much with just one copy running. I upgraded from Mesa 6.5.2 to Mesa 7.0.2, to pick up a newer r300_dri.so but that didn't make any difference. Kernel is 2.6.14.7 with drm upgraded to 1.24.0. I can't use a newer drm without moving to a newer kernel, which is not an option at this time.
Bill, can you open a new bug please? this isn't the same thing you are seeing... can you attach a log to the new bug as well..
I've exactly the same errors in the system log, but in f9-rawhide. [drm:radeon_cp_reset] *ERROR* radeon_cp_reset called without lock held, held 0 owner ea000150 ea000150 [drm:radeon_cp_start] *ERROR* radeon_cp_start called without lock held, held 0 owner ea000150 ea000150 [drm:radeon_cp_idle] *ERROR* radeon_cp_idle called without lock held, held 0 owner ea000150 ea000150 If i want to log in with GDM, X (or GDM) freezes (Mouse & Keyboard). The system is still alive.
Created attachment 296029 [details] my xorg.conf
ss
oops, I can reproduce this in rawhide also as of April 4th/5th
Can anyone confirm this bug still exists in F9, please? I'm not able to reproduce it with latest vnc-server build (4.1.2-29.fc9)
Looks like fixed, closing