Bug 924385 - nouveau: graphic corruption after while
Summary: nouveau: graphic corruption after while
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-21 16:19 UTC by Jaroslav Škarvada
Modified: 2015-02-17 14:53 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-17 14:53:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmidecode for the affected machine (13.84 KB, text/plain)
2013-03-21 16:25 UTC, Jaroslav Škarvada
no flags Details
an example *.emf file that triggers the screen corruption when loaded by libreoffice, as soon as the convert to pdf button is pushed. (40.35 KB, application/octet-stream)
2013-04-05 20:18 UTC, Jos de Kloe
no flags Details
Immediate corruption after login. (430.95 KB, image/jpeg)
2013-06-12 15:18 UTC, Jaroslav Škarvada
no flags Details
Later graphic corruption (379.61 KB, image/jpeg)
2013-06-12 15:18 UTC, Jaroslav Škarvada
no flags Details
lspci (27.39 KB, text/plain)
2013-06-12 16:04 UTC, Jaroslav Škarvada
no flags Details
Xorg.0.log (29.61 KB, text/plain)
2013-06-12 16:05 UTC, Jaroslav Škarvada
no flags Details
lspci (27.39 KB, text/plain)
2013-06-12 16:05 UTC, Jaroslav Škarvada
no flags Details
Xorg.1.log (27.96 KB, text/plain)
2013-06-12 16:06 UTC, Jaroslav Škarvada
no flags Details
dmesg after the crash (128.34 KB, text/plain)
2013-06-12 16:09 UTC, Jaroslav Škarvada
no flags Details
Graphic corruption (184.47 KB, image/png)
2013-06-21 08:12 UTC, Jaroslav Škarvada
no flags Details
Less graphic corruption (95.40 KB, image/png)
2013-06-21 08:20 UTC, Jaroslav Škarvada
no flags Details
dmesg (67.72 KB, text/plain)
2013-06-21 08:24 UTC, Jaroslav Škarvada
no flags Details
Xorg.0.log (28.74 KB, text/x-log)
2013-06-21 08:25 UTC, Jaroslav Škarvada
no flags Details
Xorg.1.log (28.55 KB, text/x-log)
2013-06-21 08:26 UTC, Jaroslav Škarvada
no flags Details
messages (452.50 KB, application/x-gzip)
2013-06-21 08:29 UTC, Jaroslav Škarvada
no flags Details

Description Jaroslav Škarvada 2013-03-21 16:19:59 UTC
Description of problem:
When running gnome-shell for approx. 10 minutes and longer on machine with nouveau, the graphic gets corrupted (icons and fonts become unreadable).

Version-Release number of selected component (if applicable):
gnome-shell-3.7.92-2

How reproducible:
Always

Steps to Reproduce:
1. Run gnome shell on machine with nouveau for 10 minutes or longer
  
Actual results:
Graphics get corrupted

Expected results:
No graphic corruption.

Additional info:
This maybe also nouveau driver error, feel free to reassign. Filled during F19 Gnome 3.8 Test Day (http://fedoraproject.org/wiki/Test_Day:2013-03-21_Gnome_3.8).

Comment 1 Jaroslav Škarvada 2013-03-21 16:25:20 UTC
Created attachment 713999 [details]
dmidecode for the affected machine

It uses nouveau and direct rendering.

Comment 2 Jaroslav Škarvada 2013-03-21 16:30:10 UTC
Probably this may be the source of the problem:

Mar 21 12:08:25 localhost kernel: [ 3802.337767] nouveau E[   PFIFO][0000:01:00.0] DMA_PUSHER - ch 6 [gnome-shell[10020]] get 0x02b67000 put 0x005d8d50 state 0x8002e8
e8 (err: INVALID_CMD) push 0x00000000
Mar 21 12:08:29 localhost kernel: [ 3806.047358] nouveau E[gnome-shell[10020]] reloc wait_idle failed: -16
Mar 21 12:08:29 localhost kernel: [ 3806.047395] nouveau E[gnome-shell[10020]] reloc apply: -16
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: kernel rejected pushbuf: Device or resource busy
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: ch0: krec 0 pushes 1 bufs 18 relocs 122
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: ch0: buf 00000000 00000002 00000004 00000004 00000000
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: ch0: buf 00000001 00000017 00000004 00000004 00000000
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: ch0: buf 00000002 0000000e 00000002 00000002 00000002
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: ch0: buf 00000003 0000001c 00000004 00000004 00000000
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: ch0: buf 00000004 00000024 00000002 00000002 00000002
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: ch0: buf 00000005 0000001e 00000004 00000004 00000000
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: ch0: buf 00000006 00000045 00000002 00000002 00000002
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: ch0: buf 00000007 00000013 00000004 00000004 00000000
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: ch0: buf 00000008 00000019 00000002 00000002 00000002
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: ch0: buf 00000009 00000011 00000002 00000002 00000002
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: ch0: buf 0000000a 00000015 00000002 00000002 00000002
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: ch0: buf 0000000b 00000016 00000002 00000002 00000002
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: ch0: buf 0000000c 000000a4 00000002 00000002 00000000
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: ch0: buf 0000000d 00000012 00000004 00000004 00000000
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: ch0: buf 0000000e 0000005f 00000004 00000004 00000000
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: ch0: buf 0000000f 0000005e 00000002 00000002 00000002
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: ch0: buf 00000010 0000001b 00000002 00000002 00000000
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: ch0: buf 00000011 00000112 00000002 00000002 00000000
Mar 21 12:08:29 localhost /etc/gdm/Xsession[9809]: nouveau: ch0: rel 00000000 0004cc9c 00000001 00000001 00000000 00000000 00000000

and much more errors follow.

Comment 3 Jaroslav Škarvada 2013-03-21 16:30:53 UTC
Reassigning to kernel, feel free to reassign if the problem is elsewhere.

Comment 4 Jos de Kloe 2013-03-30 08:57:57 UTC
I am having almost the same issue on F18 on my laptop, but not always reproducible.
-it sometimes happens when I use fvwm window manager (seems triggered after memory usage has been high, when multiple heavy applications are active in parallel). In this case only icons are corrupted, not the fonts
-it seems to happen with gnome-shell for one specific user, not for others.
-this corruption seems to be related to some state that is saved after relogin/reboot because it immediately reoccurs after a reboot/relogin for this user.

For the second case, I see this error in $HOME/.cache/gdm/session.log

...
failed to create drawable
failed to create drawable
failed to create drawable
** Message: applet now embedded in the notification area
failed to create drawable
nouveau: kernel rejected pushbuf: Cannot allocate memory
nouveau: ch0: krec 0 pushes 1 bufs 591 relocs 0
nouveau: ch0: buf 00000000 00000002 00000004 00000004 00000000
nouveau: ch0: buf 00000001 00000006 00000004 00000000 00000004
nouveau: ch0: buf 00000002 00000011 00000004 00000004 00000000
nouveau: ch0: buf 00000003 00000010 00000002 00000000 00000002
...

I'll be happy to provide more details if needed.

Comment 5 Jos de Kloe 2013-04-05 18:59:25 UTC
Just stumbled upon a reproducible way to trigger screen corruption while using the fvwm window manager (but not sure this is the same problem as mentioned above):

1) load an *.emf file in libreoffice
2) convert the picture to pdf

the screen becomes massively corrupted ...
Log off and relogin and the screen is normal again.

Details on my system:

>lspci | grep VGA
02:00.0 VGA compatible controller: NVIDIA Corporation G86 [GeForce 8400M G] (rev a1)

Running kernel: kernel-3.8.5-201.fc18.x86_64

I see this kind of errors in /var/log/messages:

Apr  5 20:39:19 laptopvanjos kernel: [  540.497949] nouveau E[  PGRAPH][0000:02:00.0] TRAP_TPDMA_2D - TP 0 - Unknown fault at address 0049f70000
Apr  5 20:39:19 laptopvanjos kernel: [  540.497960] nouveau E[  PGRAPH][0000:02:00.0] TRAP_TPDMA_2D - TP 0 - e0c: 00000000, e18: 00000000, e1c: 00000000, e20: 00000011, e24: 0c030000
Apr  5 20:39:19 laptopvanjos kernel: [  540.497964] nouveau E[  PGRAPH][0000:02:00.0]  TRAP
Apr  5 20:39:19 laptopvanjos kernel: [  540.497970] nouveau E[  PGRAPH][0000:02:00.0] ch 2 [0x000fb33000] subc 2 class 0x502d mthd 0x08dc data 0x00000000
Apr  5 20:39:19 laptopvanjos kernel: [  540.497981] nouveau E[     PFB][0000:02:00.0] trapped write at 0x0049f70000 on channel 0x0000fb33 PGRAPH/PROP/DST2D reason: PAGE_NOT_PRESENT
Apr  5 20:39:19 laptopvanjos kernel: [  540.498002] nouveau E[  PGRAPH][0000:02:00.0] TRAP_TPDMA_2D - TP 0 - Unknown fault at address 0049f8c000
Apr  5 20:39:19 laptopvanjos kernel: [  540.498005] nouveau E[  PGRAPH][0000:02:00.0] TRAP_TPDMA_2D - TP 0 - e0c: 00000000, e18: 00000000, e1c: 000001c0, e20: 00000011, e24: 0c030000

Comment 6 Jos de Kloe 2013-04-05 20:18:09 UTC
Created attachment 732005 [details]
an example *.emf file that triggers the screen corruption when loaded by libreoffice, as soon as the convert to pdf button is pushed.

Comment 7 Jos de Kloe 2013-04-06 08:41:40 UTC
even batch processing like this:
   libreoffice --headless --convert-to pdf image1.emf
triggers the bug.
Afterwards (after logoff and relogin) the produced pdf file seems corrupt, it shows a black square only.

Comment 8 Adam Williamson 2013-06-12 01:28:30 UTC
Jaroslav, can you please provide all the data requested at https://fedoraproject.org/wiki/How_to_debug_Xorg_problems ? Thanks!

Comment 9 Jaroslav Škarvada 2013-06-12 15:18:00 UTC
Created attachment 760206 [details]
Immediate corruption after login.

I updated the machine to the latest F19 packages and the problem seems to get worse. After the login I mostly get the weird display immediately (photo attached) and the desktops stop responding. The desktop is dead, but the machine responds to pings. Sometimes the display get weird after several seconds (I will attach another photo) and the desktop also stops responding. The quality of the photos is not good as I was not able to take the screenshots from the dead desktop and there weren't good conditions for my mobile phone camera, but the corruption is visible. It's old machine. I will provide the data as requested.

Comment 10 Jaroslav Škarvada 2013-06-12 15:18:50 UTC
Created attachment 760207 [details]
Later graphic corruption

Comment 11 Jaroslav Škarvada 2013-06-12 16:04:44 UTC
Created attachment 760250 [details]
lspci

Comment 12 Jaroslav Škarvada 2013-06-12 16:05:39 UTC
Created attachment 760251 [details]
Xorg.0.log

Comment 13 Jaroslav Škarvada 2013-06-12 16:05:46 UTC
Created attachment 760252 [details]
lspci

Comment 14 Jaroslav Škarvada 2013-06-12 16:06:49 UTC
Created attachment 760253 [details]
Xorg.1.log

Comment 15 Jaroslav Škarvada 2013-06-12 16:09:04 UTC
Created attachment 760254 [details]
dmesg after the crash

This used standard log level, I will try to reproduce later with the increased log level.

Comment 16 Adam Williamson 2013-06-12 18:10:30 UTC
I think you may have gotten unlucky with 'the latest F19 packages' and hit https://bugzilla.redhat.com/show_bug.cgi?id=973542 , which is a major showstopper. Can you check if you have the package set affected by that bug (details in the bug), and if so, update to the fixed packages, check the status after that, and re-do the logs if the corruption shows up again? Sorry for the hassle :(

Comment 17 Jaroslav Škarvada 2013-06-19 15:45:41 UTC
(In reply to Adam Williamson from comment #16)
NP. I had the affected packages, but I didn't encounter the described symptoms - GDM shows OK (mostly). I upgraded the packages, rebooted, but the problem described in this BZ persists. I will re-upload the logs.

Comment 18 Jaroslav Škarvada 2013-06-21 08:12:25 UTC
Created attachment 763693 [details]
Graphic corruption

Corruption after several minutes of gnome desktop usage.

Comment 19 Jaroslav Škarvada 2013-06-21 08:20:55 UTC
Created attachment 763697 [details]
Less graphic corruption

Less graphic corruption, see the text in the title bar and bottom bar.

Comment 20 Jaroslav Škarvada 2013-06-21 08:24:23 UTC
Created attachment 763698 [details]
dmesg

Comment 21 Jaroslav Škarvada 2013-06-21 08:25:26 UTC
Created attachment 763699 [details]
Xorg.0.log

Comment 22 Jaroslav Škarvada 2013-06-21 08:26:17 UTC
Created attachment 763700 [details]
Xorg.1.log

Comment 23 Jaroslav Škarvada 2013-06-21 08:29:21 UTC
Created attachment 763702 [details]
messages

Comment 24 Jaroslav Škarvada 2013-06-21 08:39:17 UTC
This doesn't seem to be HW fault, Fedora 14 with nouveau / direct rendering works like a charm on the machine.

Comment 25 Jaroslav Škarvada 2013-06-21 09:16:48 UTC
Also it seems to run correctly on F19 in XFCE. I also tried openarena on the machine and everything work correctly. It seems the problem appears only in the gnome-shell.

Comment 26 Adam Williamson 2013-06-21 16:11:54 UTC
Huh. That looks a lot like the corruption we get with Shell when using cirrus in KVM. Dunno if that means anything.

Comment 27 Jos de Kloe 2013-07-10 20:45:22 UTC
(In reply to Jos de Kloe from comment #7)
> even batch processing like this:
>    libreoffice --headless --convert-to pdf image1.emf
> triggers the bug.
> Afterwards (after logoff and relogin) the produced pdf file seems corrupt,
> it shows a black square only.

this week installed Fedora 19 and all problems disappeared on my machine. Everything seems to run fine again.

Comment 28 Jos de Kloe 2013-10-15 20:41:11 UTC
ok, I cheered too early. Screen corruption still occurs, but much less and only in situations with heavy memory load.
For example when loading a pdf file of over 100 MB (almost 1000 pages of scans) for preview in firefox the same corroption returns, and can only be solved by restarting the graphical system.
Try for example this pdf file:
http://www.vanbritsom.com/library/Groot%20charterboek%20Holland,%20Zeeland%20and%20de%20heeren%20van%20Vriesland/Charter1.pdf
provided by this webpage:
http://www.vanbritsom.com/library.html

Comment 29 Fedora End Of Life 2015-01-09 17:48:11 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.

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 30 Fedora End Of Life 2015-02-17 14:53:35 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.