On 16/07/13 12:43, Axel Stammler wrote:
> Package: gdm3
> Version: 3.4.1-8
> Severity: important
> [ 24.009] (EE) R128(0): R128DRICloseScreen: CCE stop -22
...
> [ 24.014] (WW) R128(0): Direct rendering disabled
...
> [ 24.966] (EE) R128(0): R128CCEWaitForIdle: CCE idle -9
> [ 24.966] (EE) R128(0): Idle timed out, resetting engine...
> [ 24.966] (EE) R128(0): R128CCEWaitForIdle: CCE stop -9
> [ 24.966] (EE) R128(0): R128CCEWaitForIdle: CCE start -9
> [ 24.966] (EE) R128(0): R128CCEWaitForIdle: CCE idle -9
> [ 24.966] (EE) R128(0): Idle timed out, resetting engine...
I suspect this isn't gdm3's fault, and should be reassigned to
xserver-xorg-video-r128 (or possibly the kernel, or something else in
the graphics stack). X maintainers: any ideas?
If you disable gdm3 ("sudo update-rc.d gdm3 disable"), log in using text
mode, and try using startx or similar, that might indicate whether gdm3
is somehow triggering or causing this - if you get the same errors when
X is started by startx, then it isn't gdm3's fault.
Please attach the output of "reportbug --template
/usr/lib/xorg/modules/drivers/r128_drv.so", which should contain
information on X and the R128 driver.
S
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51e53cfa.1000...@debian.org
