I would like to direct your attention to this bug report from the arch linux tracker:
Essentially the X server crashes when using nouveau with multiple monitors. Whenever an xrandr command is issued the server crashes. This is particularly irksome since this seems to send the monitors into power-saving mode (i.e. no more signals are sent) so that the problem can't even be resolved from a shell.
I am not the author of the bug report above, I merely googled the error
/usr/bin/Xorg.bin: symbol lookup error: /usr/lib/xorg/modules/drivers/nouveau_drv.so: undefined symbol: exaGetPixmapDriverPrivate
So this seems to affect multiple users. I am currently running debian jessie using version 1.0.11 of xserver-xorg-video-nouveau and version 7.7+3~deb7u1 of xorg-xserver but I ran into the same problem with arch a couple of weeks ago.
I would very much appreciate any help with this. This bug *really* breaks my setup.
extern _X_EXPORT void *exaGetPixmapDriverPrivate(PixmapPtr p);
and in the actual server:
So... that seems odd. Please provide your xorg log, preferably which includes that error. You can usually find a backed up log in /var/log/Xorg.0.log.old.
Oh, I bet you're using GLAMOR? Don't do that :) [Unless you have a Maxwell, in which case you're sunk.]
I'm seeing the same symptoms on my machine. For me, the issue gets triggered by a kernel update. 4.0 (with or without stable patches on top of that) works. When running one of the 4.1 RCs the X server crashes on xrandr(1) (to enable multi-monitor), printing the above symbol lookup error message to the console.
The attached log gives some hints as to why that might happen:
[ 80.374] (EE) NOUVEAU(0): Failed to initialise context object: M2MF_NVC0 (0)
[ 80.374] (EE) NOUVEAU(0): Error initialising acceleration. Falling back to NoAccel
[ 80.374] (**) NOUVEAU(0): [COPY] acceleration disabled
So it's not necessarily that the original reporter is using GLAMOR, it might also be the case that acceleration isn't enabled at all.
Any idea on what's causing this? I can try to pin down the earliest failing commit but it'll take some time until I get to it.
Should I file a new report? OP doesn't state anything regarding kernel version, so the issues might or might not be related.
kernel v4.1-rc3-284-g92752b5 (i.e. Linus' current tree as of now)
Created attachment 115845 [details]
Created attachment 115846 [details]
Turns out the issue was introduced with:
Author: Ben Skeggs <email@example.com>
Date: Thu Mar 26 09:18:32 2015 +1000
drm/nouveau/gr/gf100-: add symbolic names for classes
Signed-off-by: Ben Skeggs <firstname.lastname@example.org>
It seems that one of the added constants got hit by a typo. I sent
a patch to the list (CCed to Ben).
Now, that fixes things for me. The original report could still be an unrelated problem.