Bug 770092 - F16 x86_64 xorg (nouveau) freezes. Need to ssh and reboot
Summary: F16 x86_64 xorg (nouveau) freezes. Need to ssh and reboot
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-mach64
Version: 16
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: 2011-12-23 10:58 UTC by Juan Antonio Martinez
Modified: 2013-02-13 12:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 12:45:52 UTC
Type: ---


Attachments (Terms of Use)
tgz file with Xorg.0.log, lsmod, dmesg, and lspci outputs (48.46 KB, application/x-compressed-tar)
2011-12-23 10:58 UTC, Juan Antonio Martinez
no flags Details

Description Juan Antonio Martinez 2011-12-23 10:58:02 UTC
Created attachment 549330 [details]
tgz file with Xorg.0.log, lsmod, dmesg, and lspci outputs

Description of problem:

X server freezes in normal work. Can move mouse but buttons have no effect. No response from keyboard (nor alt-Fx works). ssh access is still available

Version-Release number of selected component (if applicable):
F16 installed from scratch and fully updated

How reproducible:
Randomly: Actually my system freezes twice (or more) a day, leaving it
unusable as desktop system

Steps to Reproduce:
1. Start with a new, updated F16 installation
2. Start  gnome3 session (no fallback mode)
3. Work normally until screen freezes
  
Actual results:
cannot work from console. need access by ssh and reboot

Expected results:
Normal work

Additional info:
* xorg logs shows an infinite loop error and a backtrace with some noticed input-event errors
* Using dualhead configuration in widescreen mode
* several gnome-shell extensions istalled
* Some extrange video behaviour on screen lock, but ignore if related (¿perhaps a suspend/resume related fail?)
* Attached xorg.0.log, lsmod, dmesg, and lspci info

Comment 1 Juan Antonio Martinez 2012-01-13 11:54:27 UTC
Seems same error than bug 754674

Recent updates make keyboard work, but screen is still frozen. need to change (Ctrl-Tab) to a text console and reboot / restart gdm

Comment 2 Fedora End Of Life 2013-01-16 12:28:59 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora End Of Life 2013-02-13 12:45:55 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

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.