Activity log for bug #300304

Date Who What changed Old value New value Message
2008-11-20 13:15:07 Risto H. Kurppa bug added bug
2008-11-20 13:15:07 Risto H. Kurppa bug added attachment 'Xorg.0.log' (X crashing)
2008-11-20 13:19:03 Risto H. Kurppa None: bugtargetdisplayname Ubuntu xorg (Ubuntu)
2008-11-20 13:19:03 Risto H. Kurppa None: bugtargetname ubuntu xorg (Ubuntu)
2008-11-20 13:19:03 Risto H. Kurppa None: statusexplanation Change of the package to xorg.. Feel free to change if you know better..
2008-11-20 13:19:03 Risto H. Kurppa None: title Bug #300304 in Ubuntu: "Intrepid X crashes on start (ATI 9200SE RV280)" Bug #300304 in xorg (Ubuntu): "Intrepid X crashes on start (ATI 9200SE RV280)"
2008-11-21 20:47:21 Burger King bug added attachment 'Xorg.0.log.old' (Xorg log for the system based on Radeon 9600)
2008-11-23 12:48:01 Burger King bug added attachment 'Xorg.0.log.redeon' (Failing Xorg.0.log with the Radeon open source driver)
2008-12-05 22:12:15 Bryce Harrington description My display adaptor: 01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (rev 01) DVI-connected Apple Studio 15" monitor Hardy/KDE3 with vesa works okay. Ubuntu/Kubuntu Intrepid live has problem #1 Alternate-installed fresh Kubuntu (w. kde 4.1.3) Intrepid has problem #1 Alternate-installed fresh Kubuntu (w. kde 4.1.3) Intrepid with xorg-driver-fglrx has #2 #1: X starts OK, I can see the cursor but the rest of the image is scrambled: Just 'random lines' all over the screen, starting from KDM. Might be some kind of a sync problem. Something like this: http://img34.picoodle.com/img/img34/4/7/22/f_screenscrewm_cac94d6.png (not my screenshot) #2: X crashes, see attachment.This is the actual bug that I'm reporting here. I don't know if it's aboug fglrx (too bad if it is..) or xorg (in which case it could be fixed eventually) My display adaptor: 01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (rev 01) DVI-connected Apple Studio 15" monitor Hardy/KDE3 with vesa works okay. Ubuntu/Kubuntu Intrepid live has problem #1 Alternate-installed fresh Kubuntu (w. kde 4.1.3) Intrepid has problem #1 Alternate-installed fresh Kubuntu (w. kde 4.1.3) Intrepid with xorg-driver-fglrx has #2 #1: X starts OK, I can see the cursor but the rest of the image is scrambled: Just 'random lines' all over the screen, starting from KDM. Might be some kind of a sync problem. Something like this: http://img34.picoodle.com/img/img34/4/7/22/f_screenscrewm_cac94d6.png (not my screenshot) #2: X crashes, see attachment.This is the actual bug that I'm reporting here. I don't know if it's aboug fglrx (too bad if it is..) or xorg (in which case it could be fixed eventually) Backtrace: 0: /usr/bin/X11/X(xf86SigHandler+0x79) [0x80c3009] 1: [0xb809a400] 2: /usr/lib/xorg/modules/drivers//radeon_drv.so [0xb7b18b07] 3: /usr/lib/xorg/modules/drivers//radeon_drv.so [0xb7ae655a] 4: /usr/lib/xorg/modules/drivers//radeon_drv.so [0xb7ae94fc] 5: /usr/bin/X11/X(InitOutput+0x96f) [0x80aac9f] 6: /usr/bin/X11/X(main+0x279) [0x8071b19] 7: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7ca0685] 8: /usr/bin/X11/X [0x8071101] Saw signal 11. Server aborting.
2008-12-05 22:13:03 Bryce Harrington xorg: status New Incomplete
2008-12-05 22:13:03 Bryce Harrington xorg: bugtargetdisplayname xorg (Ubuntu) xserver-xorg-video-ati (Ubuntu)
2008-12-05 22:13:03 Bryce Harrington xorg: bugtargetname xorg (Ubuntu) xserver-xorg-video-ati (Ubuntu)
2008-12-05 22:13:03 Bryce Harrington xorg: statusexplanation Change of the package to xorg.. Feel free to change if you know better.. Please collect a full backtrace on this crash. See http://wiki.ubuntu.com/X/Backtracing for directions.
2008-12-05 22:13:03 Bryce Harrington xorg: title Bug #300304 in xorg (Ubuntu): "Intrepid X crashes on start (ATI 9200SE RV280)" Bug #300304 in xserver-xorg-video-ati (Ubuntu): "Intrepid X crashes on start (ATI 9200SE RV280)"
2008-12-09 08:03:04 Risto H. Kurppa bug added attachment 'strace.txt' (strace)
2008-12-17 18:35:44 Bryce Harrington xserver-xorg-video-ati: status Incomplete New
2008-12-17 18:35:44 Bryce Harrington xserver-xorg-video-ati: statusexplanation Please collect a full backtrace on this crash. See http://wiki.ubuntu.com/X/Backtracing for directions.
2008-12-17 18:41:31 Bryce Harrington xserver-xorg-video-ati: status New Incomplete
2008-12-17 18:41:31 Bryce Harrington xserver-xorg-video-ati: statusexplanation Hi Risto, That's a very good start! The only other adjustment needed, is please install the debug package, xserver-xorg-video-ati-dbg, so we can get symbols on the calls #1-3.
2009-01-02 18:49:51 Bryce Harrington title Intrepid X crashes on start (ATI 9200SE RV280) [RV280 9200SE] Intrepid X crashes on start
2009-01-02 19:05:04 Bryce Harrington title [RV280 9200SE] Intrepid X crashes on start [RV280 9200SE] Intrepid X crashes in RADEONDRIGetVersion (wrong DRM library present?)
2009-01-02 19:22:24 Bryce Harrington xserver-xorg-video-ati: status Incomplete New
2009-01-02 19:22:24 Bryce Harrington xserver-xorg-video-ati: statusexplanation Hi Risto, That's a very good start! The only other adjustment needed, is please install the debug package, xserver-xorg-video-ati-dbg, so we can get symbols on the calls #1-3.
2009-01-02 19:22:40 Bryce Harrington xserver-xorg-video-ati: status New Incomplete
2009-01-02 19:22:40 Bryce Harrington xserver-xorg-video-ati: statusexplanation Thanks; that helps a lot. In the log and backtrace, it seems to be crashing when it's trying to open the DRM device: drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device or address) drmOpenDevice: open result is -1, (No such device or address) drmOpenDevice: Open failed The backtrace is pointing at this line (or a previous one) as where the crash is occuring: fd = drmOpen(RADEON_DRIVER_NAME, busId); I think part of the problem is that installing fglrx has confused your system. You commented that with #2 you're attempting to use fglrx, but from the log and backtrace it appears to be using radeon. If you have fglrx's DRM installed, then it may be causing the conflict with starting radeon. As to why it's using radeon rather than fglrx, perhaps you've not specified fglrx as the driver in your xorg.conf. Please check this. Let's focus this bug report on getting things working just with the open source radeon driver. Please completely purge fglrx and related packages, and reinstall the -ati driver (or do a fresh reinstall of Intrepid). Do not install fglrx. Attach the Xorg.0.log and xorg.conf from running that, as well as the output of lspci -vvnn.
2009-01-08 11:07:19 Risto H. Kurppa bug added attachment 'Xorg.0.log' (Xorg.0.log)
2009-01-08 11:08:00 Risto H. Kurppa bug added attachment 'lspci.txt' (lspci -vvnn)
2009-01-19 11:20:39 Risto H. Kurppa bug added attachment 'Xorg.0.log' (xorg.log from Jaunty Alpha3)
2009-02-09 08:24:12 Risto H. Kurppa xserver-xorg-video-ati: status Incomplete Confirmed
2009-02-09 08:24:12 Risto H. Kurppa xserver-xorg-video-ati: statusexplanation Thanks; that helps a lot. In the log and backtrace, it seems to be crashing when it's trying to open the DRM device: drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device or address) drmOpenDevice: open result is -1, (No such device or address) drmOpenDevice: Open failed The backtrace is pointing at this line (or a previous one) as where the crash is occuring: fd = drmOpen(RADEON_DRIVER_NAME, busId); I think part of the problem is that installing fglrx has confused your system. You commented that with #2 you're attempting to use fglrx, but from the log and backtrace it appears to be using radeon. If you have fglrx's DRM installed, then it may be causing the conflict with starting radeon. As to why it's using radeon rather than fglrx, perhaps you've not specified fglrx as the driver in your xorg.conf. Please check this. Let's focus this bug report on getting things working just with the open source radeon driver. Please completely purge fglrx and related packages, and reinstall the -ati driver (or do a fresh reinstall of Intrepid). Do not install fglrx. Attach the Xorg.0.log and xorg.conf from running that, as well as the output of lspci -vvnn. Marked as confirmed - same behaviour on several releases (Intrepid, Jaunty a4 & a5 both on DVI and VGA). Change if you don't agree.
2009-02-09 08:28:03 Risto H. Kurppa description My display adaptor: 01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (rev 01) DVI-connected Apple Studio 15" monitor Hardy/KDE3 with vesa works okay. Ubuntu/Kubuntu Intrepid live has problem #1 Alternate-installed fresh Kubuntu (w. kde 4.1.3) Intrepid has problem #1 Alternate-installed fresh Kubuntu (w. kde 4.1.3) Intrepid with xorg-driver-fglrx has #2 #1: X starts OK, I can see the cursor but the rest of the image is scrambled: Just 'random lines' all over the screen, starting from KDM. Might be some kind of a sync problem. Something like this: http://img34.picoodle.com/img/img34/4/7/22/f_screenscrewm_cac94d6.png (not my screenshot) #2: X crashes, see attachment.This is the actual bug that I'm reporting here. I don't know if it's aboug fglrx (too bad if it is..) or xorg (in which case it could be fixed eventually) Backtrace: 0: /usr/bin/X11/X(xf86SigHandler+0x79) [0x80c3009] 1: [0xb809a400] 2: /usr/lib/xorg/modules/drivers//radeon_drv.so [0xb7b18b07] 3: /usr/lib/xorg/modules/drivers//radeon_drv.so [0xb7ae655a] 4: /usr/lib/xorg/modules/drivers//radeon_drv.so [0xb7ae94fc] 5: /usr/bin/X11/X(InitOutput+0x96f) [0x80aac9f] 6: /usr/bin/X11/X(main+0x279) [0x8071b19] 7: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7ca0685] 8: /usr/bin/X11/X [0x8071101] Saw signal 11. Server aborting. My display adaptor: 01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (rev 01) Earlier I had a DVI-connected Apple Studio 15" monitor, now a DVI and VGA connected DELL 17" LCD Hardy/KDE3 with vesa works okay. Intrepid/KDE4, Jaunty Alpha4 and Alpha5/KDE4 fail: X starts OK, I can see the cursor but the rest of the image is scrambled: Just 'random lines' all over the screen, starting from KDM. Might be some kind of a sync problem. Something like this: http://img34.picoodle.com/img/img34/4/7/22/f_screenscrewm_cac94d6.png (not my screenshot) (originally the description mentioned also problems with fglrx drivers problem no. 2) but let's concentrate on the open source drivers now.. See the 'original description' for more information)
2009-02-19 03:42:37 Bryce Harrington xserver-xorg-video-ati: status Confirmed Incomplete
2009-02-19 03:42:37 Bryce Harrington xserver-xorg-video-ati: importance Undecided High
2009-02-19 03:42:37 Bryce Harrington xserver-xorg-video-ati: statusexplanation Marked as confirmed - same behaviour on several releases (Intrepid, Jaunty a4 & a5 both on DVI and VGA). Change if you don't agree.
2009-02-23 13:14:24 Risto H. Kurppa title [RV280 9200SE] Intrepid X crashes in RADEONDRIGetVersion (wrong DRM library present?) [Needs AGPMode quirk] [RV280 9200SE] Intrepid X crashes
2009-02-26 22:20:37 Bryce Harrington xserver-xorg-video-ati: status Incomplete Triaged
2009-02-26 22:20:37 Bryce Harrington xserver-xorg-video-ati: assignee bryceharrington
2009-02-26 22:20:37 Bryce Harrington xserver-xorg-video-ati: statusexplanation Thanks, we've enough info to put a quirk in for this now.
2009-02-28 01:27:23 Bryce Harrington bug assigned to xserver-xorg-driver-ati
2009-02-28 01:43:23 Bug Watch Updater xserver-xorg-driver-ati: status Unknown Fix Released
2009-02-28 02:25:45 Bryce Harrington xserver-xorg-video-ati: status Triaged Fix Committed
2009-02-28 02:25:45 Bryce Harrington xserver-xorg-video-ati: statusexplanation Thanks, we've enough info to put a quirk in for this now. Uploaded patch to Jaunty and to upstream git.
2009-02-28 02:30:06 Launchpad Janitor xserver-xorg-video-ati: status Fix Committed Fix Released
2010-01-13 04:46:11 Launchpad Janitor branch linked lp:ubuntu/xserver-xorg-video-ati
2010-09-13 22:17:08 Bug Watch Updater xserver-xorg-driver-ati: importance Unknown Medium
2011-01-25 15:15:54 Bug Watch Updater xserver-xorg-driver-ati: importance Medium Unknown
2011-02-03 20:37:30 Bug Watch Updater xserver-xorg-driver-ati: importance Unknown Medium