Forwarding this bug from Ubuntu reporter Neil Wilson: http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/419434 [Problem] X server fails with DRI : drmRadeonCmdBuffer: -22 [Original Description] Latest update to Karmic busts the GNOME session. I see the new xsplash graphic. The cursor changes to waiting for a bit and then I'm back to the GDM login window. It looks like Xorg died: gnome-settings-daemon: Fatal IO error 104 (Connection reset by peer) on X server :0.0. gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. ----- The application 'gnome-panel' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. XIO: fatal IO error 0 (Success) on X server ":0.0" after 1159 requests (1152 known processed) with 0 events remaining. No protocol specified Window manager error: Unable to open X display :0.0 The key issue is drmRadeonCmdBuffer: -22 After which the X server fails. However it loads the GDM OK and will load the xterm default succesfully. Switching off DRI on RADEONHD and ATI allows the full gnome session to load properly. ----- Architecture: amd64 DistroRelease: Ubuntu 9.10 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire 5536 Package: xserver-xorg-video-ati 1:6.12.99+git20090629.f39cafc5-0ubuntu6 PackageArchitecture: amd64 PccardctlIdent: PccardctlStatus: ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-8-generic root=UUID=e544e0c3-bb61-4527-9393-26be9e351588 ro quiet splash ProcEnviron: PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-8.28-generic RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu5 libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu3 libdrm2 2.4.12+git20090801.45078630-0ubuntu1 xserver-xorg-video-intel 2:2.8.1-1ubuntu1 xserver-xorg-video-ati 1:6.12.99+git20090629.f39cafc5-0ubuntu6 Uname: Linux 2.6.31-8-generic x86_64 UserGroups: libvirtd XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf' dmi.bios.date: 02/27/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.03 dmi.board.name: JV50PU dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.03:bd02/27/2009:svnAcer:pnAspire5536:pvr0100:rvnAcer:rnJV50PU:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5536 dmi.product.version: 0100 dmi.sys.vendor: Acer fglrx: Not loaded system: distro: Ubuntu architecture: x86_64kernel: 2.6.31-8-generic
Created attachment 29139 [details] XorgLog.txt
Created attachment 29140 [details] XorgLogOld.txt
Created attachment 29141 [details] :0-slave.log.1
Created attachment 29142 [details] :0-greeter.log.1
Created attachment 29143 [details] :0.log.1
did anything show up in dmesg when you got the drmRadeonCmdBuffer: -22 error?
Not as far as I can tell. Dmesg are here: http://launchpadlibrarian.net/31002902/CurrentDmesg.txt http://launchpadlibrarian.net/31002900/BootDmesg.txt This bug affects Radeon HD in precisely the same way. Note that the X server does come up, and I can login with the Ubuntu GDM system, plus I can get the default xterm. It is when the GNOME session starts that the drmRadeonCmdBuffer shows up - presumably because that is when DRI starts to get used in anger. 2009/9/3 <bugzilla-daemon@freedesktop.org>: > http://bugs.freedesktop.org/show_bug.cgi?id=23664 > > > > > > --- Comment #6 from Alex Deucher <agd5f@yahoo.com> 2009-09-02 22:47:05 PST --- > did anything show up in dmesg when you got the drmRadeonCmdBuffer: -22 error? > > > -- > Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug. >
I believe this issue was due to using the new mesa r600 module without using a new enough kernel to support drm on r600. The mesa r600 module was later disabled in Ubuntu 9.10. It will be enabled again in Ubuntu 10.04 together with a newer kernel.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.