Menu
▾
▴
Re: [Dri-users] savage snapshot won't compile
|
From: Massimiliano M. <mas...@in...> - 2006-02-19 07:59:51
|
Alle 01:20, domenica 19 febbraio 2006, Felix K=C3=BChling ha scritto: > Please keep the thread on the mailing list. > > DmaMode "None" should help if Dma is responsible for lockups. Setting > DmaMode to "Command" or "Vertex" would help narrowing down whether > command or vertex DMA is problematic. Alternatively (without a DmaType > option) try DmaType "PCI" (you already did) or BusType "PCI". That may > help if you experience lockups after a suspend/resume cycle. > Well, I tried with "None" and "Command" and in both cases X causes lockups. When I tried with "Vertex" that was the result: =2D------------------------------------------------------ massi@mirabell2:~$ glxgears Killed (!!!) massi@mirabell2:~$ glxgears =2D------------------------------------------------------ Using DmaType doesn't help. On lockup Xorg.0.log reports: =2D------------------------------------------------------ (II) SAVAGE(0): [drm] removed 1 reserved context for kernel (II) SAVAGE(0): [drm] unmapping 8192 bytes of SAREA 0xeea8c000 at 0xb07b5000 (EE) SAVAGE(0): restarting S3 graphics engine reset 1 ... (EE) SAVAGE(0): restarting S3 graphics engine reset 2 ... (EE) SAVAGE(0): restarting S3 graphics engine reset 3 ... (EE) SAVAGE(0): restarting S3 graphics engine reset 4 ... (EE) SAVAGE(0): restarting S3 graphics engine reset 5 ... (EE) SAVAGE(0): restarting S3 graphics engine reset 6 ... (EE) SAVAGE(0): restarting S3 graphics engine reset 7 ... (EE) SAVAGE(0): restarting S3 graphics engine reset 8 ... (EE) SAVAGE(0): restarting S3 graphics engine reset 9 ... =2D------------------------------------------------------- Maybe helps. regards, Massimiliano |