Skip to contentSkip to conversation

2.6.5-rc2-mm[34] causes drop in DRI FPS

DISCUSSION Glenn Johnson 5 participants 10 messages Mar 28, 2004

lore
Share & tools
lore
#0 lore raw

The last two iterations of -mm kernels have caused my FPS count via glxgears to drop from about 2000 fps to about 180 fps. I rebuilt X11 to see if that would help but it did not.

This is with a Radeon 9100 AGP card and an Intel 865PE based motherboard.

#1 lore raw
Quoted 7 lines · Glenn Johnson

The last two iterations of -mm kernels have caused my FPS count via glxgears to drop from about 2000 fps to about 180 fps. I rebuilt X11 to see if that would help but it did not.

This is with a Radeon 9100 AGP card and an Intel 865PE based motherboard.

It could be the AGP changes. Please do a `patch -p1 -R' of bk-agpgart.patch and retest?

#2 lore raw
Quoted 11 lines · Andrew Morton
Quoted 7 lines · Glenn Johnson

The last two iterations of -mm kernels have caused my FPS count via glxgears to drop from about 2000 fps to about 180 fps. I rebuilt X11 to see if that would help but it did not.

This is with a Radeon 9100 AGP card and an Intel 865PE based motherboard.

It could be the AGP changes. Please do a `patch -p1 -R' of bk-agpgart.patch and retest?

I reverted that patch and retested but it did not solve the problem. I am still only seeing about 180 fps with glxgears.

#3 lore raw
Quoted 5 lines · Glenn Johnson
Quoted 2 lines

It could be the AGP changes. Please do a `patch -p1 -R' of bk-agpgart.patch and retest?

I reverted that patch and retested but it did not solve the problem. I am still only seeing about 180 fps with glxgears.

what does 'glxinfo | grep rendering' show?

Ingo

#4 lore raw
Quoted 9 lines · Ingo Molnar
Quoted 5 lines · Glenn Johnson
Quoted 2 lines

It could be the AGP changes. Please do a `patch -p1 -R' of bk-agpgart.patch and retest?

I reverted that patch and retested but it did not solve the problem. I am still only seeing about 180 fps with glxgears.

what does 'glxinfo | grep rendering' show?

It shows:

direct rendering: Yes

I had checked that first thing. I also verified that the AGPgart detected the chipset, etc. Everything seems okay in the XFree86 log file as well.

--
Glenn Johnson
[email protected]

#5 lore raw

On Sunday 28 March 2004 18:17, Glenn Johnson wrote:

Hi Glenn,

Quoted 5 lines
Quoted 5 lines
Quoted 4 lines
Quoted 2 lines

It could be the AGP changes. Please do a `patch -p1 -R' of bk-agpgart.patch and retest?

I reverted that patch and retested but it did not solve the problem. I am still only seeing about 180 fps with glxgears.

what does 'glxinfo | grep rendering' show?

what about reverting "DRM-cvs-update.patch"?

ciao, Marc

#6 lore raw
Quoted 11 lines · Marc-Christian Petersen

On Sunday 28 March 2004 18:17, Glenn Johnson wrote:

Hi Glenn,

Quoted 5 lines
Quoted 5 lines
Quoted 4 lines
Quoted 2 lines

It could be the AGP changes. Please do a `patch -p1 -R' of bk-agpgart.patch and retest?

I reverted that patch and retested but it did not solve the problem. I am still only seeing about 180 fps with glxgears.

what does 'glxinfo | grep rendering' show?

what about reverting "DRM-cvs-update.patch"?

I have not tried that but has that patch been in the tree for some time now? My DRI works fine with 2.6.5-rc2-mm2, which has that patch.

--
Glenn Johnson
[email protected]

#7 lore raw
In reply to Glenn Johnson
Quoted 12 lines · Glenn Johnson
Quoted 9 lines · Ingo Molnar
Quoted 5 lines · Glenn Johnson
Quoted 2 lines

It could be the AGP changes. Please do a `patch -p1 -R' of bk-agpgart.patch and retest?

I reverted that patch and retested but it did not solve the problem. I am still only seeing about 180 fps with glxgears.

what does 'glxinfo | grep rendering' show?

Quoted 7 lines

It shows:

direct rendering: Yes

I had checked that first thing. I also verified that the AGPgart detected the chipset, etc. Everything seems okay in the XFree86 log file as well.

I just did a diff of my XFree86 log files with the system booted using the 2.6.5-rc2-mm2 and 2.6.5-rc2-mm4 kernels, respectively. Here is the diff, so maybe this will mean something.

XFree86-2.6.5-rc2-mm4.log renamed from XFree86-2.6.5-rc2-mm2.log +4 -4
@@ -19 +19 @@
-(==) Log file: "/var/log/XFree86.0.log", Time: Sun Mar 28 10:31:22 2004
+(==) Log file: "/var/log/XFree86.0.log", Time: Sun Mar 28 10:28:32 2004
@@ -713,2 +713,2 @@
-(II) RADEON(0): [drm] added 8192 byte SAREA at 0xe188b000
-(II) RADEON(0): [drm] mapped SAREA 0xe188b000 to 0x48328000
+(II) RADEON(0): [drm] added 8192 byte SAREA at 0xe1889000
+(II) RADEON(0): [drm] mapped SAREA 0xe1889000 to 0x48328000
@@ -764 +764 @@
-(II) RADEON(0): [drm] dma control initialized, using IRQ 169
+(II) RADEON(0): [drm] dma control initialized, using IRQ 10

--
Glenn Johnson
[email protected]

#8 lore raw
Quoted 10 lines · Glenn Johnson

I just did a diff of my XFree86 log files with the system booted using the 2.6.5-rc2-mm2 and 2.6.5-rc2-mm4 kernels, respectively. Here is the diff, so maybe this will mean something.

XFree86-2.6.5-rc2-mm4.log renamed from XFree86-2.6.5-rc2-mm2.log +1 -1
@@ -19 +19 @@
-(==) Log file: "/var/log/XFree86.0.log", Time: Sun Mar 28 10:31:22 2004
+(==) Log file: "/var/log/XFree86.0.log", Time: Sun Mar 28 10:28:32 2004

XFree86-2.6.5-rc2-mm4.log line 714

Quoted 4 lines
XFree86-2.6.5-rc2-mm4.log renamed from XFree86-2.6.5-rc2-mm2.log +2 -2
@@ -713,2 +713,2 @@
-(II) RADEON(0): [drm] added 8192 byte SAREA at 0xe188b000
-(II) RADEON(0): [drm] mapped SAREA 0xe188b000 to 0x48328000
+(II) RADEON(0): [drm] added 8192 byte SAREA at 0xe1889000
+(II) RADEON(0): [drm] mapped SAREA 0xe1889000 to 0x48328000

That's just a memory allocation, so that will never be consistent.

XFree86-2.6.5-rc2-mm4.log line 764

Quoted 3 lines
XFree86-2.6.5-rc2-mm4.log renamed from XFree86-2.6.5-rc2-mm2.log +1 -1
@@ -764 +764 @@
-(II) RADEON(0): [drm] dma control initialized, using IRQ 169
+(II) RADEON(0): [drm] dma control initialized, using IRQ 10

You're not using CONFIG_PCI_USE_VECTOR in the newer kernel, but that also wouldn't make a difference.

#9 lore raw
Quoted 19 lines · Zwane Mwaikambo
Quoted 10 lines · Glenn Johnson

I just did a diff of my XFree86 log files with the system booted using the 2.6.5-rc2-mm2 and 2.6.5-rc2-mm4 kernels, respectively. Here is the diff, so maybe this will mean something.

XFree86-2.6.5-rc2-mm4.log renamed from XFree86-2.6.5-rc2-mm2.log +1 -1
@@ -19 +19 @@
-(==) Log file: "/var/log/XFree86.0.log", Time: Sun Mar 28 10:31:22 2004
+(==) Log file: "/var/log/XFree86.0.log", Time: Sun Mar 28 10:28:32 2004

XFree86-2.6.5-rc2-mm4.log line 714

Quoted 4 lines
XFree86-2.6.5-rc2-mm4.log renamed from XFree86-2.6.5-rc2-mm2.log +2 -2
@@ -713,2 +713,2 @@
-(II) RADEON(0): [drm] added 8192 byte SAREA at 0xe188b000
-(II) RADEON(0): [drm] mapped SAREA 0xe188b000 to 0x48328000
+(II) RADEON(0): [drm] added 8192 byte SAREA at 0xe1889000
+(II) RADEON(0): [drm] mapped SAREA 0xe1889000 to 0x48328000

That's just a memory allocation, so that will never be consistent.

Quoted 6 lines

XFree86-2.6.5-rc2-mm4.log line 764

Quoted 3 lines
XFree86-2.6.5-rc2-mm4.log renamed from XFree86-2.6.5-rc2-mm2.log +1 -1
@@ -764 +764 @@
-(II) RADEON(0): [drm] dma control initialized, using IRQ 169
+(II) RADEON(0): [drm] dma control initialized, using IRQ 10

You're not using CONFIG_PCI_USE_VECTOR in the newer kernel, but that also wouldn't make a difference.

Actually, I am using CONFIG_PCI_USE_VECTOR in both.