Bug 9892

(In reply to comment #0)
> > how can i further help with this issue? 

It would be best if you could start the X server from gdb and get a full backtrace from the crash. Note that you can only do this from a remote login.

Other than that, it might also be useful if you could isolate the change that caused this with git-bisect.

additional log from 32bit installation 
(i cut the boring stuff out)

------------------------------------------------------
(**) RADEON(0): RADEONSaveScreen(2)
(**) RADEON(0): RADEONCloseScreen
(**) RADEON(0): RADEONDRIStop
(**) RADEON(0): EngineRestore (32/32)
(**) RADEON(0): RADEONDisplayPowerManagementSet(0,0x0)

Backtrace:
0: X(xf86SigHandler+0x81) [0x80c56b1]
1: [0xa7f78420]
2: /usr/lib/xorg/modules/drivers//radeon_drv.so(RADEONDisplayPowerManagementSet+0x122) [0xa7bb0af2]
3: /usr/lib/xorg/modules/drivers//radeon_drv.so [0xa7b9f0c9]
4: X [0x81526d6]
5: X [0x80db91c]
6: X [0x80d7b97]
7: X [0x812b488]
8: X [0x814f555]
9: X(main+0x502) [0x806e632]
10: /lib/libc.so.6(__libc_start_main+0xef) [0xa7cdd87f]
----------------------------------------------------------

right now i'm trying to figure out the git-bisect thing you mentioned.

okay i think i got it.

i started with 
git-bisect start
git-bisect good ati_6_6_3
git-bisect bad

after each git-bisect good/bad i did
./autogen.sh
./configure --prefix=/usr
make
make install 

and tested.

------------------------------------------------------------
218cb7f8db35d0ce8f9fc4ece72bd5ec3f52106f is first bad commit
commit 218cb7f8db35d0ce8f9fc4ece72bd5ec3f52106f
Author: Dave Airlie <airlied@linux.ie>
Date:   Sun Dec 3 09:53:35 2006 +1100

    radeon: dynamically allocate connectors

:040000 040000 b4ce69d956bf595903d2ef3a6113ad2207e6f810 1159ce3a6908370f70bf66260704eb9deb60000a M      src

Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.

i tried recently with new snapshot (just built, a couple of minutes ago).

i used drm modules from 2.6.22.1 kernel with gentoo-patches. 

i'm using xorg-server-1.3.0.0, and mesa 6.5.3 (but that doesn't matter much, does it?).

after modprobing drm modules : (dmesg)
[  773.704733] [drm] Initialized drm 1.1.0 20060810
[  773.706819] [drm] Initialized radeon 1.27.0 20060524 on minor 0

symptoms, as before - my lcd goes into powersaving mode with "No Signal" message. when launching X.

Backtrace:
0: X(xf86SigHandler+0x81) [0x80c7141]
1: [0xb7f7c420]
2: /usr/lib/xorg/modules/drivers//radeon_drv.so(RADEONDisplayPowerManagementSet+0x122) [0xb7b9ec22]
3: /usr/lib/xorg/modules/drivers//radeon_drv.so [0xb7b8cce8]
4: X [0x8160ad0]
5: X [0x80dd3cc]
6: X [0x80d9627]
7: X [0x813a878]
8: X [0x815e405]
9: X(main+0x503) [0x8070303]
10: /lib/libc.so.6(__libc_start_main+0xef) [0xb7d5e9ff]

[pressed ctrl+atl+bksp]

Fatal server error:
Caught signal 11.  Server aborting

(II) RADEON(0): RADEONRestoreMemMapRegisters() :
(II) RADEON(0):   MC_FB_LOCATION   : 0x1fff0000
(II) RADEON(0):   MC_AGP_LOCATION  : 0x27ff2000

and i was lucky enough to return to the console.

do i need to upgrade additional x.org components to git snapshots as well?

using gcc-4.1.2 if that matters (seems that 4.2 caused a lot of kernel breakage recently).

*** This bug has been marked as a duplicate of bug 10772 ***

6.6.193 fixed segfaults and crashes, but i'm still not getting anything on screen.

how do i investigate further? unfortunately i only have one pc, so i can't use remote debugging, as suggested previously :/

i think i got the problem. 

i'll open a new bug and close this one, because it's quite a different problem.