Bug 71362

Summary: [NVC1] X hang with drop to console after some time / GPU lockup - PFIFO error and TTM error @dmesg
Product: Mesa Reporter: Torsten Krah <krah.tm>
Component: Drivers/DRI/nouveauAssignee: Nouveau Project <nouveau>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: medium    
Version: 9.2   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Xorg.0.log
lspci -nn
dmesg after dropping to fbcon
backtrace from gdb with VTSwitch
another dmesg gpu lockup log

Description Torsten Krah 2013-11-07 22:15:53 UTC
Created attachment 88851 [details]
Xorg.0.log

Just surfing around and reading the mail to 71357 X went slow and did hang finally.
Logs are attached - Ubuntu 13.10 with Mesa 9.2.1.
Comment 1 Torsten Krah 2013-11-07 22:16:14 UTC
Created attachment 88852 [details]
lspci -nn
Comment 2 Torsten Krah 2013-11-07 22:16:49 UTC
Created attachment 88853 [details]
dmesg after dropping to fbcon
Comment 3 Torsten Krah 2013-11-07 22:17:38 UTC
Created attachment 88854 [details]
backtrace from gdb with VTSwitch
Comment 4 Torsten Krah 2013-11-07 23:36:54 UTC
Created attachment 88863 [details]
another dmesg gpu lockup log
Comment 5 Ilia Mirkin 2013-11-30 06:33:21 UTC
Is this helped at all by the patch I suggested in bug 71357? It should be included in 3.11.10 and 3.12.2 as well as 3.13-rc1.
Comment 6 Ilia Mirkin 2014-01-23 18:37:33 UTC
No response from reporter in over a month. Closing as invalid.
Comment 7 Torsten Krah 2014-01-24 09:19:54 UTC
I can't trigger this with usecase XY - so i don't know if its fixed - i did only report it that it did happening, maybe you can tell me from the traces how this can be forced to happen.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.