Steps to Reproduce: 1. Suspend desktop 2. Resume from suspend At this point I'm presented with a white screen and a flood of messages in dmesg. I do not know how to recover without rebooting. This fails 100% of the time; very reproducible. lspci: 01:00.0 VGA compatible controller: NVIDIA Corporation GF116 [GeForce GT 640 OEM] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 8540 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at f4000000 (32-bit, non-prefetchable) [size=32M] Region 1: Memory at e0000000 (64-bit, prefetchable) [size=128M] Region 3: Memory at e8000000 (64-bit, prefetchable) [size=64M] Region 5: I/O ports at e000 [size=128] Expansion ROM at f6000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [78] Express (v1) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 <64us ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <256ns, L1 <4us ClockPM+ Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- Capabilities: [b4] Vendor Specific Information: Len=14 <?> Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb: Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status: NegoPending- InProgress- Capabilities: [128 v1] Power Budgeting <?> Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Kernel driver in use: nouveau Relevant parts of dmesg: Jan 22 08:21:32 localhost.localdomain kernel: [drm] Initialized nouveau 1.1.1 20120801 for 0000:01:00.0 on minor 0 Jan 22 14:30:12 localhost.localdomain kernel: nouveau [ DRM] suspending display... Jan 22 14:30:12 localhost.localdomain kernel: nouveau [ DRM] unpinning framebuffer(s)... Jan 22 14:30:12 localhost.localdomain kernel: nouveau [ DRM] evicting buffers... Jan 22 14:30:12 localhost.localdomain kernel: nouveau [ DRM] waiting for kernel channels to go idle... Jan 22 14:30:12 localhost.localdomain kernel: nouveau [ DRM] suspending client object trees... Jan 22 14:30:12 localhost.localdomain kernel: nouveau [ DRM] suspending kernel object tree... Jan 22 14:30:12 localhost.localdomain kernel: nouveau [ DRM] re-enabling device... Jan 22 14:30:12 localhost.localdomain kernel: nouveau [ DRM] resuming kernel object tree... Jan 22 14:30:12 localhost.localdomain kernel: nouveau [ VBIOS][0000:01:00.0] running init tables Jan 22 14:30:12 localhost.localdomain kernel: nouveau [ DRM] resuming client object trees... Jan 22 14:30:12 localhost.localdomain kernel: nouveau [ DRM] resuming display... Jan 22 14:30:12 localhost.localdomain kernel: nouveau E[ PGRAPH][0000:01:00.0] TRAP ch 2 [0x00bfa82000 Xorg[645]] Jan 22 14:30:12 localhost.localdomain kernel: nouveau E[ PGRAPH][0000:01:00.0] SHADER 0xa004021e The last two lines get repeated indefinitely at a near constant rate.
Can I get your kernel log from before suspending please?
Created attachment 854471 [details] Kernel log
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.
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.