Bug 901706 - Nouveau-related system crash, PGRAPH TLB flush idle timeout fail
Summary: Nouveau-related system crash, PGRAPH TLB flush idle timeout fail
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 18
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-18 20:59 UTC by Jonathan Abbey
Modified: 2014-02-05 15:14 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 15:14:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
System dmesg (67.32 KB, text/plain)
2013-01-18 21:00 UTC, Jonathan Abbey
no flags Details
grep nouveau /var/log/messages (31.03 KB, text/plain)
2013-01-18 21:02 UTC, Jonathan Abbey
no flags Details

Description Jonathan Abbey 2013-01-18 20:59:11 UTC
Description of problem:

With the latest versions of the Fedora 18 kernel and xorg-x11-drv-nouveau driver, I'm repeatedly experiencing system crashes on my Dell Optiplex 980 x86-64 system with an OEM '1 GB GeForce GT 330' video card.

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

xorg-x11-drv-nouveau: xorg-x11-drv-nouveau-1.0.3-1.fc18.x86_64
kernel: kernel-3.7.2-201.fc18.x86_64

How reproducible:

Log in to Fedora 18 with Gnome Shell using the Gallium 0.4 on NVA3 Standard
Experience, wait for system to freeze up.

I have experienced this three times now with the above versions installed.  I haven't had any other versions installed long enough since installing Fedora 18 that I can say whether or not other versions have had the same behavior.

Additional info:

After powering down the crashed system and restarting, I see things like this
in /var/log/messages:

Jan 18 14:29:50 csdpc20 kernel: [ 4253.500446] nouveau E[  PGRAPH][0000:01:00.0] PGRAPH TLB flush idle timeout fail: 0x01b00003 0x00000000 0x00001068 0x00200000
Jan 18 14:29:50 csdpc20 kernel: [ 4255.497003] nouveau E[  PGRAPH][0000:01:00.0] vm flush timeout: engine 0
Jan 18 14:29:57 csdpc20 kernel: [ 4260.489514] nouveau E[  PGRAPH][0000:01:00.0] PGRAPH TLB flush idle timeout fail: 0x01b00003 0x00000000 0x00001068 0x00200000
Jan 18 14:29:57 csdpc20 kernel: [ 4262.486066] nouveau E[  PGRAPH][0000:01:00.0] vm flush timeout: engine 0

In addition, I'm seeing some corruption of rendering in the gnome shell application shelf and the system menus.  Some images are missing, and font rendering in the system menu appears to be misshapen or having problems with alpha channel.

Comment 1 Jonathan Abbey 2013-01-18 21:00:27 UTC
Created attachment 682702 [details]
System dmesg

Dmesg log with some hardware information

Comment 2 Jonathan Abbey 2013-01-18 21:02:49 UTC
Created attachment 682703 [details]
grep nouveau /var/log/messages

All entries in /var/log/messages that grep for nouveau over the last few days

Comment 3 Jonathan Abbey 2013-01-18 21:05:10 UTC
It appears I misspoke about having three crashes.  It appears that it has only happened twice, both times today.

Comment 4 Jonathan Abbey 2013-01-18 22:07:47 UTC
Okay, now I've had three crashes.  The most recent came when I hit the left Windows key to shrink the windows into the Gnome Shell overview mode.  It crashed when I did that, leaving no logging in /var/log/messages concerning nouveau.

FWIW.

Comment 5 Ivan Mironov 2013-02-24 16:22:36 UTC
It seems that I have the same problem on NVidia 9500M GS. It appears when waking up from suspend:

...
Feb 23 11:28:22 localhost kernel: [16500.544004] nouveau E[  PGRAPH][0000:01:00.0] PGRAPH TLB flush idle timeout fail: 0x01000003 0x00000000 0x00000000 0x00200
000
Feb 23 11:28:24 localhost kernel: [16502.546007] nouveau E[  PGRAPH][0000:01:00.0] PGRAPH TLB flush idle timeout fail: 0x01000003 0x00000000 0x00000000 0x00200
000
Feb 23 11:28:26 localhost kernel: [16504.553217] nouveau E[  PGRAPH][0000:01:00.0] PGRAPH TLB flush idle timeout fail: 0x01000003 0x00000000 0x00000000 0x00200
...

Comment 6 Matthieu Pupat 2013-06-01 07:28:57 UTC
I am seeing the same issue with a GeForce GT640

Comment 7 Johan Vervloet 2013-06-05 12:39:43 UTC
I had the same problem. I switched from Gnomne to OpenBox, and now everything seems to work fine.

Comment 8 Fedora End Of Life 2013-12-21 10:32:28 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is 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  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.

Comment 9 Fedora End Of Life 2014-02-05 15:14:33 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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