kern/112984: [drm] Xorg 7.2 locks up with AIGLX enabled on the r300 driver.

Henry Hu hugangmail at 163.com
Thu Jul 5 08:40:09 UTC 2007


The following reply was made to PR kern/112984; it has been noted by GNATS.

From: Henry Hu <hugangmail at 163.com>
To: bug-followup at FreeBSD.org,  adamk at voicenet.com
Cc:  
Subject: Re: kern/112984: [drm] Xorg 7.2 locks up with AIGLX enabled on the
 r300 driver.
Date: Thu, 05 Jul 2007 16:12:23 +0800

 I'm using FreeBSD 6.2-STABLE, with Xorg 7.2 and Mesa 6.5.3.
 I have a radeon 7500 card, using radeon driver.
 If I turn on AIGLX and startx, the screen goes blank, and there's no
 response from the keyboard or the shutdown button. I can only use the
 RESET button to restart. And there are many messages in
 /var/log/messages, just the same as Kirchhoff's.
 If I run X -configure and X -config ~/xorg.conf.new, the screen will go
 blank and return, just because my fonts are still in /usr/X11R6. But I
 can get some different messages from /var/log/messages:
 ...
 (WW) AIGLX: 3D driver claims to not support visual 0x23
 (WW) AIGLX: 3D driver claims to not support visual 0x24
 (WW) AIGLX: 3D driver claims to not support visual 0x25
 (WW) AIGLX: 3D driver claims to not support visual 0x26
 (WW) AIGLX: 3D driver claims to not support visual 0x27
 (WW) AIGLX: 3D driver claims to not support visual 0x28
 (WW) AIGLX: 3D driver claims to not support visual 0x29
 (WW) AIGLX: 3D driver claims to not support visual 0x2a
 (WW) AIGLX: 3D driver claims to not support visual 0x2b
 (WW) AIGLX: 3D driver claims to not support visual 0x2c
 (WW) AIGLX: 3D driver claims to not support visual 0x2d
 (WW) AIGLX: 3D driver claims to not support visual 0x2e
 (WW) AIGLX: 3D driver claims to not support visual 0x2f
 (WW) AIGLX: 3D driver claims to not support visual 0x30
 (WW) AIGLX: 3D driver claims to not support visual 0x31
 (WW) AIGLX: 3D driver claims to not support visual 0x32
 (II) AIGLX: Loaded and initialized /usr/local/lib/dri/radeon_dri.so
 (II) GLX: Initialized DRI GL provider for screen 0
 ...
 
 Fatal server error:
 could not open default font 'fixed'
 (II) AIGLX: Suspending AIGLX clients for VT switch
 (**) RADEON(0): RADEONLeaveVT
 (EE) RADEON(0): RADEONLeaveVT: CP stop -22
 (**) RADEON(0): EngineRestore (32/32)
 (**) RADEON(0): RADEONRestore
 (**) RADEON(0): RADEONRestoreMode()
 (**) RADEON(0): RADEONRestoreMode(0x81cd130)
 (**) RADEON(0): RADEONRestoreMemMapRegisters() :
 (**) RADEON(0): MC_FB_LOCATION : 0x1fff0000
 (**) RADEON(0): MC_AGP_LOCATION : 0x27ff2000
 (**) RADEON(0): Map Changed ! Applying ...
 (**) RADEON(0): Map applied, resetting engine ...
 (**) RADEON(0): Updating display base addresses...
 (**) RADEON(0): Memory map updated.
 (**) RADEON(0): Programming CRTC2, offset: 0x00000000
 (**) RADEON(0): Wrote: 0x00000000 0x00000000 0x00000000 (0x0000a400)
 (**) RADEON(0): Wrote: rd=0, fd=0, pd=0
 (**) RADEON(0): Programming CRTC1, offset: 0x00000000
 (**) RADEON(0): Wrote: 0x00000007 0x00030057 0x00000000 (0x0000a400)
 (**) RADEON(0): Wrote: rd=7, fd=87, pd=3
 (==) RADEON(0): Write-combining range (0xa0000,0x10000) was already clear
 (**) RADEON(0): Ok, leaving now...
 
 
 
 


More information about the freebsd-bugs mailing list