Xgl - r300 - dapper

[Daniel Robitaille]

On 2/27/06, Roland Laurès <shamox at gmail.com> wrote:
> Hi,
>
>    I just suscribe to the list to report a "little" bug that i saw reported
> only on one site (a freebsd one).
>  I tried to find a post that could match mine, in the list, and restrict my
> "customization" of my box to
>  fit to the standard powerbook G4 alu. So what happened :
>    I wanted to try Xgl and co, so i dist-upgrade my box from ubuntu breezy
> to dapper. After rebooting and checking
>  that i got the hard rendering with glxinfo, I replace /etc/X11/X ->
> /usr/bin/Xorg by /etc/X11/X -> /usr/bin/Xgl
>  as described in several urls. (i can give you the one that i follow if you
> ask, but it was on ubuntu wiki)
>  I restart X and got the clock cursor and the background of ubuntu, and a
> really white screen. I check with ssh,
>  and Xorg takes 99% of the cpu and i can't kill hum (even with -9 sig). I
> take a look on the Xorg.0.log and see
>  that the start process stop in the middle of the initialization of the
> [drm]  communication with the radeon (M10 here)
>  i take a look at the syslog and see the marvelous lines :
>  [code]
>  Feb 27 12:47:10 localhost kernel: [  564.399234]
> [drm:r300_emit_raw_packet3] *ERROR* Unknown packet3 header (0xc0059b00)
>  Feb 27 12:47:10 localhost kernel: [  564.399251] [drm:r300_emit_packet3]
> *ERROR* r300_emit_raw_packet3 failed
>  Feb 27 12:47:10 localhost kernel: [  564.399257] [drm:r300_do_cp_cmdbuf]
> *ERROR* r300_emit_packet3 failed
>  Feb 27 12:47:14 localhost gdm[4725]: gdm_slave_xioerror_handler : erreur X
> fatale - Redémarrage de :0
>  Feb 27 12:47:18 localhost gdm[4732]: gdm_slave_xioerror_handler : erreur X
> fatale - Redémarrage de :0
>  Feb 27 12:47:22 localhost gdm[4739]: gdm_slave_xioerror_handler : erreur X
> fatale - Redémarrage de :0
>  Feb 27 12:47:22 localhost gdm[4704]: deal_with_x_crashes : exécution du
> script XKeepsCrashing
>  Feb 27 12:58:49 localhost -- MARK --
>  [\code]
>
>  the system accept ssh connections and can reboot properly so it is not so
> hanguy... I saw that it was a known issue
>  of dual-screen xorg configuration on r300 boxes, but i tried it with the
> default xorg.conf file and got the same problem...
>  I attach my xorg.conf default and my old xorg.conf, i send also the
> Xorg.0.log.
>
>  If you have any idea...

The correct place to report bugs is:
  https://launchpad.net/distros/ubuntu/+filebug

After searching to make sure it hasn't been reported already, just
file a new one, and attach to the report the file you attached to this
email.


--
Daniel Robitaille