Bug 714800 - Very slow graphics and desktop freezes at random times.
Summary: Very slow graphics and desktop freezes at random times.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 15
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: [cat:lockup]
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-20 19:37 UTC by Alexander Volovics
Modified: 2018-04-11 19:18 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 15:36:48 UTC
Type: ---


Attachments (Terms of Use)
dmesg output after trying to provoke freeze with guake etc. (77.63 KB, application/octet-stream)
2011-07-28 09:14 UTC, Alexander Volovics
no flags Details
copy of Xorg.0.log from same time as dmesg output (42.85 KB, text/x-log)
2011-07-28 09:16 UTC, Alexander Volovics
no flags Details
dmesg output after a freeze on the dimension e520 (70.72 KB, application/octet-stream)
2011-08-04 08:27 UTC, Alexander Volovics
no flags Details
Xorg.0.log output after freeze on dimension e520 (50.86 KB, text/x-log)
2011-08-04 08:29 UTC, Alexander Volovics
no flags Details

Description Alexander Volovics 2011-06-20 19:37:01 UTC
Description of problem:

I have Dell Inspiron E520 with a Nvidia Geforce 7300 LE (NV46-G72)
graphics card. It is impossible to use this PC with Fed15/Gnome3
for any serious work.

1) the nouveau driver results in irritatingly slow graphics on
   this machine. For example using keyboard shortcuts to start
   applications gives very slowly emerging windows. First the outlines,
   then a vague ghost-like image before the window slowly takes
   solid form. Or when using the package manager to install apps
   the pop up message windows very slowly roll down and upon
   closing very slowly roll upwards again. Etc.

2) at random times the desktop freezes solid and so does the
   keyboard. The only possible way to recycle (shutdown-restart)
   is using the power button of the PC.
   I have not been able to discover any 'triggering' events.
   As this happened almost every work session lasting longer than
   2-3 hours I quit using Gnome 3 on this PC.

I group installed LXDE to be able to work with the PC
so I can easily log in to the Gnome 3 shell to check things
if necessary.


Version-Release number of selected component (if applicable):

A completely up to date Fedora 15 with Gnome 3.
xorg-x11-drv-nouveau-0.0.16-24.20110324git8378443.fc15.x86_64
mesa-libGLU-7.11-0.11.20110525.0.fc15.x86_64
mesa-dri-llvmcore-7.11-0.11.20110525.0.fc15.x86_64
mesa-libGL-7.11-0.11.20110525.0.fc15.x86_64
mesa-dri-drivers-7.11-0.11.20110525.0.fc15.x86_64
mesa-dri-filesystem-7.11-0.11.20110525.0.fc15.x86_64


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 SilvioTO 2011-07-07 15:28:00 UTC
Similar problem here with Toshiba laptop with nVidia G72M (Quadro NVS 110M/GeForce Go 7300) (rev a1).

The system is usable but slow, for example, moving a window I have to pay attention, becouse the window don't follow the mouse in time. Slow are the popup notification animations, rolling windows "save as", etc. Watching a video is a little flickering too.

No problems inside the applications: web pages in firefox are rendered quickly, no problem editing images in gimp or inkscape, for example.

Comment 2 SilvioTO 2011-07-07 15:31:24 UTC
I forget to tell you that my platform is Fedora 15 i386

Comment 3 Ben Skeggs 2011-07-08 00:02:00 UTC
Give this mesa build a try for the lagginess: http://koji.fedoraproject.org/koji/buildinfo?buildID=250343

Comment 4 Alexander Volovics 2011-07-08 10:32:23 UTC
I installed the updates:
mesa-libGL-7.11-0.15.20110626.0.fc15.x86_64
mesa-dri-filesystem-7.11-0.15.20110626.0.fc15.x86_64
mesa-dri-drivers-7.11-0.15.20110626.0.fc15.x86_64
mesa-dri-llvmcore-7.11-0.15.20110626.0.fc15.x86_64
mesa-libGLU-7.11-0.15.20110626.0.fc15.x86_64

First impressions are that the system has become much more responsive.
It is now possible to work quite comfortably with nouveau in Gnome3.
If there is no relapse I would consider the 'slowness' solved satisfactorily.

I will report back if the desktop freezes still occur.

There is one minor 'complaint'.
In some apps (for example I run mutt in a gnome-terminal for mail)
the colors have become a bit funny: 'strange' yellows, reds and greens
Everything has a yellow/orange hue.

Are the above rpm's sufficient (I only installed those I already had)
or would I need to install one or more of the other available rpm's.

Comment 5 Alexander Volovics 2011-07-08 13:25:06 UTC
The desktop freezes have not gone away!

After about 2.5 hours working the desktop froze solid again.
But now I could close apps and reboot using Cntl-Alt-F2.

A pity because the nouveau driver was working nicely, no slowness
or lagging graphics.

Comment 6 Ben Skeggs 2011-07-08 13:31:21 UTC
Do you happen to have ssh access to the machine?  If so, dmesg output from after a freeze would be excellent to try and determine what the problem is, if it is indeed nouveau.

If no, /var/log/messages from immediately after rebooting from a freeze is the second best thing.  But, a lot of the time it's missing the good stuff :)

Comment 7 Alexander Volovics 2011-07-08 22:15:07 UTC
I will configure ssh access to the machine from my laptop
so I can capture dmesg output and then report back when it
happens again.

I have already looked at /var/log/messages after rebooting but
I saw nothing suspicious, but then I might not know what to look for :)

Comment 8 Alexander Volovics 2011-07-18 10:07:20 UTC
I have found one action that triggers a desktop freeze:
opening a guake terminal.

I found this on the last output line of dmesg:
[ 5378.194850] [drm] nouveau 0000:01:00.0: Unexpected pageflip in channel 3.

I hope this information is helpfull

Comment 9 Matěj Cepl 2011-07-27 00:41:57 UTC
(In reply to comment #8)
> I have found one action that triggers a desktop freeze:
> opening a guake terminal.
> 
> I found this on the last output line of dmesg:
> [ 5378.194850] [drm] nouveau 0000:01:00.0: Unexpected pageflip in channel 3.
> 
> I hope this information is helpfull

It is, but still complete dmesg output would be even more helpful. Also /var/log/Xorg.0.log soon after the crash happens.

Thank you veryu much

Comment 10 Alexander Volovics 2011-07-28 09:14:53 UTC
Created attachment 515664 [details]
dmesg output after trying to provoke freeze with guake etc.

Comment 11 Alexander Volovics 2011-07-28 09:16:41 UTC
Created attachment 515665 [details]
copy of Xorg.0.log from same time as dmesg output

Comment 12 Alexander Volovics 2011-07-28 09:23:00 UTC
The nouveau/mesa drivers have been updated since I last posted:
mesa-libGLU-7.11-0.16.20110709.0.fc15.x86_64
mesa-dri-filesystem-7.11-0.16.20110709.0.fc15.x86_64
mesa-dri-llvmcore-7.11-0.16.20110709.0.fc15.x86_64
mesa-dri-drivers-7.11-0.16.20110709.0.fc15.x86_64
mesa-libGL-7.11-0.16.20110709.0.fc15.x86_64
xorg-x11-drv-nouveau-0.0.16-24.20110324git8378443.fc15.x86_64

I have not had a freeze this past week and now that I need one
I cannot provoke it (by using quake terminal for example)

However I am still sending you the output of dmesg and the
Xorg.0.log file as the output of dmesg regarding nouveau
does not look healthy at all!
See the last 20-30 lines of dmesg.

Comment 13 SilvioTO 2011-07-28 10:39:39 UTC
Problem is solved for me since the latest uptade mentioned above.

Comment 14 Ben Skeggs 2011-07-28 22:59:22 UTC
(In reply to comment #12)
> The nouveau/mesa drivers have been updated since I last posted:
> mesa-libGLU-7.11-0.16.20110709.0.fc15.x86_64
> mesa-dri-filesystem-7.11-0.16.20110709.0.fc15.x86_64
> mesa-dri-llvmcore-7.11-0.16.20110709.0.fc15.x86_64
> mesa-dri-drivers-7.11-0.16.20110709.0.fc15.x86_64
> mesa-libGL-7.11-0.16.20110709.0.fc15.x86_64
> xorg-x11-drv-nouveau-0.0.16-24.20110324git8378443.fc15.x86_64
> 
> I have not had a freeze this past week and now that I need one
> I cannot provoke it (by using quake terminal for example)
> 
> However I am still sending you the output of dmesg and the
> Xorg.0.log file as the output of dmesg regarding nouveau
> does not look healthy at all!
> See the last 20-30 lines of dmesg.

Yes, I'm aware of what can cause that particular problem to happen (running out of vram), a significant rework of a couple of userspace nouveau components is required to deal with that properly.

It's on my pending list, but keeps getting pre-empted by worse issues. Sigh.

Comment 15 Alexander Volovics 2011-08-04 08:27:36 UTC
Created attachment 516658 [details]
dmesg output after a freeze on the dimension e520

Comment 16 Alexander Volovics 2011-08-04 08:29:03 UTC
Created attachment 516659 [details]
Xorg.0.log output after freeze on dimension e520

Comment 17 Alexander Volovics 2011-08-04 08:32:47 UTC
A 'real' freeze/crash happened today (august 4, 2011)
I had to ssh into the pc to get the dmesg output.
The machine is completely up to date with updates and bug fixes.
I am attaching dmesg and xorg.0.log output

Comment 18 Adam Pribyl 2011-08-11 21:33:09 UTC
Looks very similar to bug #709536

Comment 19 Fedora End Of Life 2012-08-07 15:36:51 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.