Nouveau - Oct 2009 - [Bug 24820] New: [nv15] Vertical screen corruption in X when KMS is enabled

http://bugs.freedesktop.org/show_bug.cgi?id=24820

           Summary: [nv15] Vertical screen corruption in X when KMS is
                    enabled
           Product: xorg
           Version: git
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau at lists.freedesktop.org
        ReportedBy: johannesobermayr at gmx.de
         QAContact: xorg-team at lists.x.org


Hardware: Geforce2 GTS
Drivers, Mesa, kernel modules: git20091029

If I boot with nouveau.modeset=1 X/KDE4 looks like this:

http://www.freeimagehosting.net/uploads/ea8ad8c8cc.jpg

Console (init 3) looks fine.

dmesg and Xorg.0.log follow...


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #1 from Johannes Obermayr <johannesobermayr at gmx.de> 
2009-10-30 13:33:14 PST ---
Created an attachment (id=30847)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=30847)
dmesg


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #2 from Johannes Obermayr <johannesobermayr at gmx.de> 
2009-10-30 13:33:57 PST ---
Created an attachment (id=30848)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=30848)
Xorg.0.log


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #3 from Pekka Paalanen <pq at iki.fi>  2009-10-30 15:44:22 PST
---
Just in case, could you reproduce this without nouveau_dri.so?
Thanks.

I'm actually surprised X does not die a horrible death instantly.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #4 from Johannes Obermayr <johannesobermayr at gmx.de> 
2009-10-30 17:22:38 PST ---
Created an attachment (id=30860)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=30860)
Xorg.0.log.diff

Yes, same behavior without nouveau_dri.so.

I attach a diff for Xorg.0.log.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #5 from Francisco Jerez <currojerez at riseup.net>  2009-11-06
19:46:31 PST ---
(In reply to comment #0)
> Hardware: Geforce2 GTS
> Drivers, Mesa, kernel modules: git20091029
> 
> If I boot with nouveau.modeset=1 X/KDE4 looks like this:
> 
> http://www.freeimagehosting.net/uploads/ea8ad8c8cc.jpg
> 
Do you get the same effect with smaller resolutions/clocks? (e.g.
1024x768 at 60Hz).
> Console (init 3) looks fine.
> 
You mean it looks fine before loading nouveau.ko, right?
> dmesg and Xorg.0.log follow...
> 

-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #6 from Johannes Obermayr <johannesobermayr at gmx.de> 
2009-11-07 02:43:08 PST ---
(In reply to comment #5)
> > 
> Do you get the same effect with smaller resolutions/clocks? (e.g.
> 1024x768 at 60Hz).
Yes, it is with all resolutions.
800x600   -> 2 corrupted bars
1024x768  -> 3 corrupted bars
1280x720  -> 4 corrupted bars
1920x1080 -> 6 corrupted bars
> > Console (init 3) looks fine.
> > 
> You mean it looks fine before loading nouveau.ko, right?
No, I boot with "nouveau.modeset=1 3" and can work on a KMS enabled
console
without any problems...

I tried it with "1...2...3...3...4...5...6...7" to see whether
something is
moved to another position (as in X/KDE) -> but all is on right place...

Btw. I use git20091105

Btw2. if I use my TNT2 M64 KMS works also fine but X/kdm login manager displays
only a black background and a white (login) box...

If you want pictures/logs I will provide them...


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #7 from Francisco Jerez <currojerez at riseup.net>  2009-11-07
06:40:39 PST ---
(In reply to comment #6)
> (In reply to comment #5)
> > > 
> > Do you get the same effect with smaller resolutions/clocks? (e.g.
> > 1024x768 at 60Hz).
> 
> Yes, it is with all resolutions.
> 800x600   -> 2 corrupted bars
> 1024x768  -> 3 corrupted bars
> 1280x720  -> 4 corrupted bars
> 1920x1080 -> 6 corrupted bars
> 
Which clock frequencies were you using exactly? It would also be interesting to
know if it works at 24 bit depth or with kernel modesetting disabled.
> > > Console (init 3) looks fine.
> > > 
> > You mean it looks fine before loading nouveau.ko, right?
> 
> No, I boot with "nouveau.modeset=1 3" and can work on a KMS
enabled console
> without any problems...
> 
> I tried it with "1...2...3...3...4...5...6...7" to see whether
something is
> moved to another position (as in X/KDE) -> but all is on right place...
> 
> Btw. I use git20091105
> 
> Btw2. if I use my TNT2 M64 KMS works also fine but X/kdm login manager
displays
> only a black background and a white (login) box...
> 
Logs and config files might be helpful, but probably an unrelated bug.
> If you want pictures/logs I will provide them...
> 

-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #8 from Johannes Obermayr <johannesobermayr at gmx.de> 
2009-11-07 07:59:04 PST ---
(In reply to comment #7)
> Which clock frequencies were you using exactly? It would also be
interesting to
> know if it works at 24 bit depth or with kernel modesetting disabled.
It works with KMS disabled (16 / 24 bit depth).

It also works with 24 bit depth and KMS enabled.

Only with 16 bit and KMS enabled it does not work all time...

Tested resolutions (all 3 cases above):
800x600   @ 76 / 75 / 70.7 / 74.9 / 65.3 / 60.3 / 60 Hz
1024x768  @ 76 / 75.1 / 70.7 / 74.8 / 65.3 / 60 Hz
1280x720  @ 76 / 70.7 / 65.3 / 74.9 / 60 Hz
1920x1080 @ 60 / 59 Hz
> > Btw2. if I use my TNT2 M64 KMS works also fine but X/kdm login manager
displays
> > only a black background and a white (login) box...
> > 
> Logs and config files might be helpful, but probably an unrelated bug.
I will try it soon. If it is not also "fixed" with 24 bit depth I will
post
log/config files.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #9 from Francisco Jerez <currojerez at riseup.net>  2009-11-07
09:38:24 PST ---
Created an attachment (id=31041)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=31041)
nv15_arbitration.patch

Does the attached patch make any difference?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820


Johannes Obermayr <johannesobermayr at gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




--- Comment #10 from Johannes Obermayr <johannesobermayr at gmx.de> 
2009-11-07 11:27:09 PST ---
This patch helps.

Same tests as above -> all modes work...

Only one thing I recognized:
If you have 24 bit depth, KMS enabled and try changing resolution to a higher
one within X the screen gets corrupted.
e.g.:
1980x1080 -> 1280x720 -> 1024x768 -> 800x600 is possible without screen
corruption.
1980x1080 -> 1280x720 -> 1920x1080 or 1980x1080 -> 1024x768 ->
1280x720 cause a
screen corruption which can only be solved by pressing Ctrl+Alt+Backspace...

But this bug is solved and so I am closing it...

Thanks for your work.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #11 from Francisco Jerez <currojerez at riseup.net> 
2009-11-08 06:09:44 PST ---
(In reply to comment #10)
> This patch helps.
> 
> Same tests as above -> all modes work...
>

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #12 from Francisco Jerez <currojerez at riseup.net> 
2009-11-08 06:15:57 PST ---
Created an attachment (id=31045)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=31045)
arb_debug.patch

This patch makes the driver log the arbitration parameters it's programming
the
hardware with. Could you please attach the kernel logs you get after running X
with it?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #13 from Johannes Obermayr <johannesobermayr at gmx.de> 
2009-11-08 14:37:51 PST ---
I did not have much time to do your requests at home today and I will going on
with compiling and testing on friday.

All I can say is that 83 is without bars and 86 has bars with 1280x720 and 16
bit depth (I have reduced resolution for more speed...).

So I have to try it with 84 and 85...


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #14 from Johannes Obermayr <johannesobermayr at gmx.de> 
2009-11-14 08:10:25 PST ---
Created an attachment (id=31195)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=31195)
dmesg

(In reply to comment #11 an #12)

Your requested dmesg with a multiplier of 31.

I noticed:
A lower resolution needs a lower multiplier and
a lower frequency within a resolution needs also a lower multiplier.

With 640x480 at 60 I can go up to a multiplier of 31 without seeing bars.

Shall I detect multipliers of other resolutions/frequencies, too?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #15 from Johannes Obermayr <johannesobermayr at gmx.de> 
2009-11-14 16:12:50 PST ---
(In reply to comment #14)
> Created an attachment (id=31195)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=31195)
[details]
> dmesg
> 
> (In reply to comment #11 an #12)
> 
> Your requested dmesg with a multiplier of 31.
> 
> I noticed:
> A lower resolution needs a lower multiplier and
> a lower frequency within a resolution needs also a lower multiplier.
> 
> With 640x480 at 60 I can go up to a multiplier of 31 without seeing bars.
> 
> Shall I detect multipliers of other resolutions/frequencies, too?
> 
Oh, it is not a multiplier - it is a summand...
(I should look right before posting...)


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #16 from Francisco Jerez <currojerez at riseup.net> 
2009-11-15 14:29:08 PST ---
Created an attachment (id=31215)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=31215)
arb_debug2.patch

I'm afraid I need a bit more of information about your card. The patch
I'm
attaching should print it out to the logs, you just have to run X at
1280x720x16bpp (and the same refresh rate you were using on your previous
tests) after applying it to the DRM.

Thanks.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #17 from Johannes Obermayr <johannesobermayr at gmx.de> 
2009-11-20 08:06:33 PST ---
Created an attachment (id=31345)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=31345)
dmesg with arb_debug2.patch

It is weekend and I am at home again...

Here is your requested dmesg (1280x720x16bpp at 76Hz).

With arb_debug2.patch KMS enabled console looks also corrupted.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820


Francisco Jerez <currojerez at riseup.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #31041|0                           |1
        is obsolete|                            |




--- Comment #18 from Francisco Jerez <currojerez at riseup.net> 
2009-11-21 09:59:05 PST ---
Created an attachment (id=31374)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=31374)
nv15_arbitration2.patch

This fix is hopefully more correct, it would be interesting to know if you
still see any kind of corruption or flashing pixels at whatever
resolution/depth/refresh rate.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820


Johannes Obermayr <johannesobermayr at gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ingo_brunberg at web.de




--- Comment #19 from Johannes Obermayr <johannesobermayr at gmx.de> 
2009-11-21 12:03:53 PST ---
(In reply to comment #18)

With nv15_arbitration2.patch I can use all resolutions/frequencies without
flickering bars...

Some other corrupted pixels continue to be visible:

http://www.freeimagehosting.net/uploads/fda04aaf3c.jpg

:s below headline
.s within "white" space between selection dialog and green box  

But it was/is also without KMS enabled...
I may open a new bug for that...

I add Ingo Brunberg to CC (Bug #24800).
He may tests nv15_arbitration2.patch and posts his "experience" with
it.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #20 from Francisco Jerez <currojerez at riseup.net> 
2009-11-21 13:35:28 PST ---
(In reply to comment #19)
> (In reply to comment #18)
> Some other corrupted pixels continue to be visible:
> 
> http://www.freeimagehosting.net/uploads/fda04aaf3c.jpg
> 
> :s below headline
> .s within "white" space between selection dialog and green box  
>
That doesn't seem to be a scanout effect, can you still see the artifacts
when
you look at a screenshot?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #21 from Johannes Obermayr <johannesobermayr at gmx.de> 
2009-11-21 14:11:57 PST ---
(In reply to comment #20)
> (In reply to comment #19)
> > (In reply to comment #18)
> > Some other corrupted pixels continue to be visible:
> > 
> > http://www.freeimagehosting.net/uploads/fda04aaf3c.jpg
> > 
> > :s below headline
are mostly visible (also in other KDE apps)
> > .s within "white" space between selection dialog and green
box
are only sometimes visible
> >
> That doesn't seem to be a scanout effect, can you still see the
artifacts when
> you look at a screenshot?
> 
With a Snapshot via KSnapshot I can see the artifacts, too. (If visible on
"normal" screen at time when "KSnapshotting").


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820


Francisco Jerez <currojerez at riseup.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #31374|0                           |1
        is obsolete|                            |




--- Comment #22 from Francisco Jerez <currojerez at riseup.net> 
2009-11-23 03:57:37 PST ---
Created an attachment (id=31409)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=31409)
arb_rewrite.patch

I think I'll go with a rewrite of the involved code like the patch I'm
attaching instead of trying to fix the old code (It's nv legacy and it had
some
issues besides the one you hit). Maybe you want to give it a try?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820


Francisco Jerez <currojerez at riseup.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #31409|0                           |1
        is obsolete|                            |




--- Comment #23 from Francisco Jerez <currojerez at riseup.net> 
2009-11-23 05:09:50 PST ---
Created an attachment (id=31412)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=31412)
arb_rewrite2.patch

I suspect nv15 has a shorter CRTC FIFO, you may get a distorted output with the
last patch but this one should fix it.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #24 from Francisco Jerez <currojerez at riseup.net> 
2009-11-23 06:14:15 PST ---
(In reply to comment #21)
> (In reply to comment #20)
> > (In reply to comment #19)
> > > (In reply to comment #18)
> > > Some other corrupted pixels continue to be visible:
> > > 
> > > http://www.freeimagehosting.net/uploads/fda04aaf3c.jpg
> > > 
> > > :s below headline
> 
> are mostly visible (also in other KDE apps)
> 
> > > .s within "white" space between selection dialog and
green box
> 
> are only sometimes visible
> 
> > >
> > That doesn't seem to be a scanout effect, can you still see the
artifacts when
> > you look at a screenshot?
> > 
> 
> With a Snapshot via KSnapshot I can see the artifacts, too. (If visible on
> "normal" screen at time when "KSnapshotting").
> 
Does it go away if you set this Section "Device" option in your
xorg.conf?
> Option "EXANoComposite" "on"

-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #25 from Johannes Obermayr <johannesobermayr at gmx.de> 
2009-11-27 10:19:23 PST ---
A new friday - a new status report:

(In reply to comment #23)
> last patch but this one should fix it.
> 
I tried it with arb_rewrite2.patch and also with

[PATCH 1/3] drm/nouveau: Update the CRTC arbitration parameters on FB depth
switch
[PATCH 2/3] drm/nouveau: Clean up the arbitration parameters calculation code.
[PATCHv2 3/3] drm/nv10-nv20: CRTC arbitration code rewrite.

X works but console has flickering artifacts with both.
(see http://www.freeimagehosting.net/uploads/0f34a8e515.jpg)

(In reply to comment #24)
>> With a Snapshot via KSnapshot I can see the artifacts, too. (If visible
on
>> "normal" screen at time when "KSnapshotting").
>> 
>
>Does it go away if you set this Section "Device" option in your
xorg.conf?
>> Option "EXANoComposite" "on"
Yes, but there are other artifacts: E. g. bottom left and bottom right
"Position" line or "Gamma" with corrupted last "a"
and "Mehrere Monitore" with
corrupted last "e". 
(see http://www.freeimagehosting.net/uploads/d94750f7aa.png)

Do you need a current dmesg?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #26 from Francisco Jerez <currojerez at riseup.net> 
2009-11-28 06:16:34 PST ---
(In reply to comment #25)
> A new friday - a new status report:
> 
> (In reply to comment #23)
> > last patch but this one should fix it.
> > 
> 
> I tried it with arb_rewrite2.patch and also with
> 
> [PATCH 1/3] drm/nouveau: Update the CRTC arbitration parameters on FB depth
> switch
> [PATCH 2/3] drm/nouveau: Clean up the arbitration parameters calculation
code.
> [PATCHv2 3/3] drm/nv10-nv20: CRTC arbitration code rewrite.
> 
> X works but console has flickering artifacts with both.
> (see http://www.freeimagehosting.net/uploads/0f34a8e515.jpg)
> 
It seems your FIFOs are underflowing because of some unknown source of latency.
If you have applied the patch series I sent to the mailing list,
nouveau_calc.c:191 will read:
>         fifo->lwm = min_lwm + 5 * (max_lwm - min_lwm) / 100; /*
Empirical. */
That "5" is enough for all the cards I have, but you'll need a
higher value,
probably something within [5,40] (don't bother to find a very accurate lower
bound, a +/-5 estimate would be fine).
> (In reply to comment #24)
> >> With a Snapshot via KSnapshot I can see the artifacts, too. (If
visible on
> >> "normal" screen at time when "KSnapshotting").
> >> 
> >
> >Does it go away if you set this Section "Device" option in
your xorg.conf?
> >> Option "EXANoComposite" "on"
> 
> Yes, but there are other artifacts: E. g. bottom left and bottom right
> "Position" line or "Gamma" with corrupted last
"a" and "Mehrere Monitore" with
> corrupted last "e". 
> (see http://www.freeimagehosting.net/uploads/d94750f7aa.png)
> 
The recent changes in the acceleration code your card uses may be the cause of
this. You could try going back to the DDX commit 5587f40, keeping
EXANoComposite set (note that you'll also have to downgrade libdrm, I think
83a35b6 is old enough).
> Do you need a current dmesg?
> 
No, unless you've seen something suspicious (e.g. PGRAPH errors).


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #27 from Johannes Obermayr <johannesobermayr at gmx.de> 
2009-11-28 07:11:18 PST ---
(In reply to comment #26)
> It seems your FIFOs are underflowing because of some unknown source of
latency.
> If you have applied the patch series I sent to the mailing list,
> nouveau_calc.c:191 will read:
> 
> >         fifo->lwm = min_lwm + 5 * (max_lwm - min_lwm) / 100; /*
Empirical. */
> 
> That "5" is enough for all the cards I have, but you'll need
a higher value,
> probably something within [5,40] (don't bother to find a very accurate
lower
> bound, a +/-5 estimate would be fine).
> 
"10" works for me...

Thanks again for your work and patience...


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=24820





--- Comment #28 from Francisco Jerez <currojerez at riseup.net> 
2009-11-28 07:54:07 PST ---
(In reply to comment #27)
> (In reply to comment #26)
> > It seems your FIFOs are underflowing because of some unknown source of
latency.
> > If you have applied the patch series I sent to the mailing list,
> > nouveau_calc.c:191 will read:
> > 
> > >         fifo->lwm = min_lwm + 5 * (max_lwm - min_lwm) / 100;
/* Empirical. */
> > 
> > That "5" is enough for all the cards I have, but you'll
need a higher value,
> > probably something within [5,40] (don't bother to find a very
accurate lower
> > bound, a +/-5 estimate would be fine).
> > 
> 
> "10" works for me...
> 
> Thanks again for your work and patience...
> 
Pushed, thanks!


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.