https://bugs.freedesktop.org/show_bug.cgi?id=46711 --- Comment #8 from Tvrtko Ursulin <tvrtko.ursulin@xxxxxxxxxxxx> 2012-04-16 08:54:47 PDT --- (In reply to comment #7) > (In reply to comment #6) > > How to investigate this potential conflict with userspace? > > > > Because, as I originally wrote, without X running monitor comes back fine. > > It's probably missing locking in the radeon kernel modesetting code. The ddx > registers an event handler in the xserver and then the desktop environment does > something with the event. See drmmode_uevent_init() and > drmmode_handle_uevents() in drmmode_display.c in xf86-video-ati. Brief look doesn't show me any locks there, I'll dig in. If relevant, we have the same symptoms with and without a "desktop environment". Meaning same thing happens with pure X, and also with our software running which does explicit output probing when nothing is connected. Problem is (seems to me) xrandr reports monitor connected when in that state. Also if relevant we do get two RandR events (RRScreenChangeNotify and RRNotify_OutputChange) when re-plugging the monitor. Unless there is no intersection between RandR and DPMS... ? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
