Bug 649361 - Graphical session freezes with "GPU lockup" reported by nouveau; X process at 100% [NEEDINFO]
Summary: Graphical session freezes with "GPU lockup" reported by nouveau; X process at...
Keywords:
Status: CLOSED DUPLICATE of bug 674636
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 14
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-03 15:56 UTC by Alex G.
Modified: 2011-02-24 10:10 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-02-24 10:10:29 UTC
Type: ---
Embargoed:
mr.nuke.me: needinfo?

Attachments (Terms of Use)
output of dmesg |grep nouveau after freeze (2.91 KB, text/plain)
2010-11-03 15:58 UTC, Alex G. 		no flags Details
View All

Description Alex G. 2010-11-03 15:56:54 UTC 
Description of problem:

After few hours of usage, desktop freezes, but mouse still active. Keyboard unresponsive, pressing CapsLock does not toggle the LED.

ssh is still usable.
Checking "dmesg |grep nouveau" reveals:
[26001.520820] [drm] nouveau 0000:04:00.0: GPU lockup - switching to software fbcon
along with a few more error messages

Version-Release number of selected component (if applicable):
xorg-x11-drv-nouveau-0.0.16-11.20100826git065576d.fc14.x86_64

How reproducible:
Always. freeze happens anywhere between 30 minutes and 6 hours of use, faster with desktop effects enabled (KDE).


Steps to Reproduce:
1. Boot and log in
2. Use desktop as usual
  
Actual results:
Display freezes; only mouse is operational.

Expected results:
No freeze.

Additional info:
Dual-9800GT machine,
dual-head, both monitors connected to primary GPU
Configured with RANDR, no xorg.conf file
using KDE
Comment 1 Alex G. 2010-11-03 15:58:06 UTC 
Created attachment 457483 [details]
output of dmesg |grep nouveau after freeze
Comment 2 Alex G. 2011-02-24 10:10:29 UTC 
Closing this, as nouveau is throwing more informative error messages.

*** This bug has been marked as a duplicate of bug 674636 ***
Note You need to log in before you can comment on or make changes to this bug.