Windows move/scroll slowly on a [SiS] 86C326 5598/6326 card

[Pablo Antonio]

Moving windows and scrolling eat a lot of CPU, and everything goes pretty slow. It's old hardware, but I can see the window redrawing when I write something in a terminal on GNOME; that makes me think there's a problem somewhere.

Let me show you CPU usage when moving a window:
$ vmstat 1
procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
 r b swpd free buff cache si so bi bo in cs us sy id wa
 4 0 74388 7724 9444 96560 0 1 9 5 266 98 4 1 95 0
 1 0 74388 7892 9444 96560 0 0 0 0 543 1095 35 15 49 0
 0 0 74388 7892 9444 96560 0 0 0 0 416 874 26 9 65 0
 1 0 74388 7816 9444 96596 0 0 36 0 706 1185 72 20 7 1
 1 0 74388 7816 9444 96596 0 0 0 0 688 926 82 18 0 0
 2 0 74388 7816 9444 96596 0 0 0 0 688 1029 78 22 0 0
 3 0 74388 7076 9444 96596 0 0 0 0 657 943 78 18 4 0
 1 0 74388 6988 9444 96596 0 0 0 0 738 707 85 15 0 0
 1 0 74388 6920 9444 96596 0 0 0 0 598 764 83 17 0 0
 2 0 74388 7832 9444 96596 0 0 0 0 565 1102 40 19 41 0

Information about the hardware:
$ sudo lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev 44)
00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22)
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10)
00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 10)
00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 10)
00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30)
00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 20)
00:09.0 Communication controller: Motorola SM56 PCI Modem
00:0b.0 Ethernet controller: VIA Technologies, Inc. VT6105/VT6106S [Rhine-III] (rev 8b)
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 86C326 5598/6326 (rev 0b)

I'm on Ubuntu 9.04:
$ sudo lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04

I'll attach Xorg's log file now. It seems to be using the driver for sis cards, so it looks normal to me.
---
Architecture: i386
CurrentDmesg:
 [ 172.317291] lo: Disabled Privacy Extensions
 [ 416.786701] lo: Disabled Privacy Extensions
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No existe el archivo o directorio
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Package: xorg 1:7.5+5ubuntu1
PackageArchitecture: i386
ProcCmdLine: root=UUID=3ba6bb07-a375-4c26-a13e-be891066a07c ro quiet splash
ProcEnviron:
 LANG=es_AR.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5
Tags: lucid lucid
Uname: Linux 2.6.32-24-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-24-generic

[Pablo Antonio (crazy2k)]

It's been almost a month and I didn't receive any comments on this. I'll appreciate any opinions regarding this problem. Thanks.

[Fabio Marconi (fabiomarconi)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is this bug reproducible with the latest Lucid packages ?
Tanks in advance.

[Fabio Marconi (fabiomarconi)]

 Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage .

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

[Fabio Marconi (fabiomarconi)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Fabio Marconi (fabiomarconi)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Pablo Antonio (crazy2k)]

Sorry for the delay. The issue happens on someone else's computer, and I get to use it for about two days every two months, so it's a bit hard for me to answer quickly with new information. Right now I'm using this computer again, until tomorrow night :)

The computer is effectively using Ubuntu Lucid Lynx, and the issue is still there. As an example, when I open System Monitor in GNOME, the processor's activity graph shows always 100%. Then I swtich windows and do something else in the console, for example, and then come back to the System Monitor. Now the graph shows the processor's history was not always 100%, but now that I'm looking at the graph and it's being redrawn, processor is again at 100%.

The other example is the one I talked about in my initial report. If I open a gnome-terminal and look at ``vmstat 1``, cpu's idle time is constantly around 50%. If I start moving gnome-terminal's window around, idle time suddently changes to a constant 0.

I think there's a problem with redrawing which is eating the processor and not using the video card properly. If that's the case, this bug might be easy or really hard to fix. If the problem is a setting in Xorg's conf file, then it'll be easy. But if the problem is the kernel has no good support for this card, then I guess this is almost a lost case, since the card is really old and pretty likely no one will ever attempt to fix this.

Thanks,

[Fabio Marconi (fabiomarconi)]

Hello Pablo
can you run in a terminal.
apport-collect 380413
thanks
fabio

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Pablo Antonio (crazy2k)]

apport information

[Fabio Marconi (fabiomarconi)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[bugbot (bugbot)]

We're closing this bug since there has not been a response from the original reporter. However, the issue still exists please feel free to reopen with the requested information. If you're not the original reporter, we'd prefer you file a new bug report.

Some tips:

  * Report X.org bugs via the command: `ubuntu-bug xorg`

  * Test against the latest development Ubuntu. http://cdimage.ubuntu.com/daily-live/
    Bugs marked as affecting the development version tend to get priority attention.

  * The `xdiagnose` utility has functionality for enabling debugging and
    analyzing a few common X problems.

  * Tag your bugs with the Ubuntu versions you have reproduced the issue in.

  * See https://wiki.ubuntu.com/X/Reporting for tips on writing good bug reports.