Bug 768997

Summary: Screen randomly goes black FX 370 nouveau
Product: [Fedora] Fedora Reporter: William H. Haller <bill>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-20 23:57:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
xdpyinfo
none
lspci
none
messages none

Description William H. Haller 2011-12-19 16:05:18 UTC
Created attachment 548625 [details]
xdpyinfo

Description of problem: The latest kernel causes the screen to randomly go black while logged on in graphical, dual screen, high res. Both screens are affected.


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


How reproducible: Always


Steps to Reproduce:
1. Log in on graphical screen
2. Use system with normal konsole windows, thunderbird, and konqueror
3. Move mouse and it recovers, but repeats.
  
Actual results: Black screen


Expected results: Visible screen


Additional info: 3.1.5-2.fc16.x86_64 works fine. All updates that came out at the same time as 3.1.5-6 was released are applied, but since 5-2 seems to work with them, I assume it is kernel related. There are no messages that I can see that are relevant in messages, no WW/EE in Xorg.0.log save the usual falling back to old probe method for vesa/fbdev

Comment 1 William H. Haller 2011-12-19 16:06:25 UTC
Created attachment 548626 [details]
lspci

Comment 2 William H. Haller 2011-12-19 16:13:23 UTC
Created attachment 548631 [details]
messages

This is a partial dump of the messages at boot. If I missed something strategic, let me know and I'll add it.

Comment 3 William H. Haller 2011-12-20 23:57:11 UTC
We ran hardware diagnostics on the box today and found a RAM chip failing that wasn't picked up by the standard BIOS diagnostics on boot.

I'm not sure how 3.1.5-6 vs. 3.1.5-2 changed the access through memory which triggered the blacking, but since I've run 3.1.5-6 on nouveau today without apparent problems I'm closing the bug. Sorry for the inconvenience.