similar to: [Bug 36090] [NV34] [NV49] terminal's visual bell is very slow with nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #12 from Ilia Mirkin <imirkin at alum.mit.edu> --- OK, by increasing the terminal size, I do indeed see that the visual bell is really rather slow. During that time, X is using up 100% CPU, so it's probably something highly unoptimal happening in the DDX. It seems like almost all of that CPU time is going into fbSolid()

https://bugs.freedesktop.org/show_bug.cgi?id=36090 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|terminal's visual bell is |[NV34] [NV49] terminal's |very slow with nouveau |visual bell is very slow

https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #3 from Harald Judt <h.judt at gmx.at> --- Thanks for your suggestion, but I can no longer call me owner of such a card and therefore am unable to test this. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugs.freedesktop.org/show_bug.cgi?id=36090 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #4 from Ilia Mirkin <imirkin at

https://bugs.freedesktop.org/show_bug.cgi?id=36090 aebenjam at opentext.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #5 from aebenjam at opentext.com --- Problem still exists

https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #6 from Ilia Mirkin <imirkin at alum.mit.edu> --- Are you on a recent version of the ddx? (xf86-video-nouveau) Also, what card do you have (G72M means nothing to me... what does nouveau say as the "Chipset" in dmesg)? -- You are receiving this mail because: You are the assignee for the bug. -------------- next part

https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #7 from aebenjam at opentext.com --- I'm not sure how to answer your question about the ddx... is this what you mean? rpm -qa |grep -i nouveau xorg-x11-drv-nouveau-1.0.7-1.fc18.i686 Re: the card, dmidecode suggests it is: Quadro NVS 110M Let me know if you need more. Thanks, Adam -- You are receiving this mail because: You

https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #8 from Ilia Mirkin <imirkin at alum.mit.edu> --- dmesg | grep -i chipset sounds like your ddx is new enough though. Can you provide detailed repro steps? I'm not even sure how to enable visual bell. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML

https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #9 from aebenjam at opentext.com --- #dmesg | grep -i chipset [ 1.887251] nouveau [ DEVICE][0000:01:00.0] Chipset: G72 (NV46) Reproduction: You can fire up an xterm with -vb to request the visual bell. You can also use control + middle-mouse-button to bring up a menu which allows you to enable/disable the visual bell. Let me

https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #10 from Ilia Mirkin <imirkin at alum.mit.edu> --- Hmmm... FWIW I couldn't reproduce any oddness with a NV42 card, kernel 3.11, and xf86-video-nouveau 1.0.9 both with and without xcompmgr running. Without a compositor, it _is_ a bit on the slow side, but like a half-second, nothing like the 3s delay mentioned in the original

https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #11 from aebenjam at opentext.com --- Interesting. So, I'm a Fedora (currently v18) user. I created a stock account, logged in to a standard Gnome environment, and fired up an xterm with visual bell running, and it doesn't have the same problem. In fact, I couldn't even SEE a visual bell. Odd. All I could tell was that

https://bugs.freedesktop.org/show_bug.cgi?id=36090 Martin Peres <martin.peres at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|REOPENED |RESOLVED --- Comment #14 from Martin Peres

From: Marcin Slusarz <marcin.slusarz at gmail.com> after this change nouveau passes all fill and blend tests of rendercheck (before: fill - 108/120, blend - 3323868/3569150) tested on NV34 Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> --- src/nv04_exa.c | 19 +++++++++---------- src/nv_accel_common.c | 5 ++++- 2 files changed, 13 insertions(+), 11

This fixes a somewhat indeterministic corruption problem on nv17 when there is stuff going on the other fifos (e.g. gallium but I've also reproduced it with an app just SIFM-ing memory around): in some cases it made the blits the X server had scheduled use the wrong pitch. Signed-off-by: Francisco Jerez <currojerez at riseup.net> --- src/nv04_exa.c | 22 ++++++++++++---------- 1

https://bugs.freedesktop.org/show_bug.cgi?id=36090 aebenjam at opentext.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aebenjam at opentext.com --- Comment #1 from aebenjam at opentext.com 2012-01-30 08:34:15 PST --- Also experienced with: 01:00.0

Hi everyone, I just finished installing the current git of the nouveau driver for my NV49 based 7950GTX. I attempted this because I've been continually frustrated by the constantly degrading 2D performance of X under the nvidia and nv drivers. Webpages that do any kind of compositing in Mozilla will burn CPU all day long. I'm happy to say that I'm writing because I didn't have

https://bugs.freedesktop.org/show_bug.cgi?id=110988 Bug ID: 110988 Summary: [NV49] Graphical issues on KDE desktop with GeForce 7950 GX2 Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component:

Hello this patch is a merge of jb17bsome's nv49 patch and mine. I have tested it for a couple of days on a nv4b and didnt get crashes. Please rewiew and apply Greetings Stephan Schmid -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: nv49_nv4b.diff Url:

Commit dceef5d87 (drm/nouveau/fb: initialise vram controller as pfb sub-object) moved some code around and introduced these null derefs. pfb->ram is set to the new ram object outside of this ctor. Reported-by: Ronald Uitermark <ronald645 at gmail.com> Tested-by: Ronald Uitermark <ronald645 at gmail.com> Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> ---

https://bugs.freedesktop.org/show_bug.cgi?id=111463 Bug ID: 111463 Summary: [NV49] MMIO write FAULT at 00c200 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: not set Priority: not set Component: Driver/nouveau Assignee: nouveau