Launchpad has imported 13 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=625982.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2010-08-21T06:32:57+00:00 Mark wrote: Created attachment 440082 Xorg.log on resume Description of problem: After a successful suspend the screen and keyboard wont come up on resume. All programs come up well and i even can log in trough ssh Version-Release number of selected component (if applicable): xorg-x11-drv-nouveau-0.0.16-7.20100423git13c1043.fc13.x86_64 How reproducible: This happends always Steps to Reproduce: 1. Suspend laptop 2. Resume latop Actual results: Screen blank, no keyboard Expected results: Normal operation Additional info: Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/622238/comments/0 ------------------------------------------------------------------------ On 2010-08-21T06:34:07+00:00 Mark wrote: Created attachment 440083 Xorg.log on normall boot Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/622238/comments/1 ------------------------------------------------------------------------ On 2010-08-21T06:34:52+00:00 Mark wrote: Created attachment 440084 lshal ouput Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/622238/comments/2 ------------------------------------------------------------------------ On 2010-08-21T06:35:22+00:00 Mark wrote: Created attachment 440085 lspci output Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/622238/comments/3 ------------------------------------------------------------------------ On 2010-08-21T06:36:06+00:00 Mark wrote: Created attachment 440086 pm-suspend.log Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/622238/comments/4 ------------------------------------------------------------------------ On 2010-08-21T06:36:33+00:00 Mark wrote: Created attachment 440087 dmidecode Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/622238/comments/5 ------------------------------------------------------------------------ On 2010-08-22T22:26:40+00:00 Ben wrote: Can I see dmesg output please? Preferably from after resume, if you can manage to get it somehow. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/622238/comments/7 ------------------------------------------------------------------------ On 2010-08-23T10:00:44+00:00 Mark wrote: Created attachment 440348 dmesg after failed resume from hybernation Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/622238/comments/8 ------------------------------------------------------------------------ On 2010-08-23T22:55:04+00:00 Ben wrote: Ah, this is a known bug with your kernel. Give this a try: http://koji.fedoraproject.org/koji/buildinfo?buildID=191473 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/622238/comments/9 ------------------------------------------------------------------------ On 2010-08-24T04:31:18+00:00 Mark wrote: Created attachment 440558 Succesfull test with kernel-2.6.24.5 Thx Ben, This works great. Are there any symptoms I should look for in case of advising others with similar issues? \\ML Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/622238/comments/10 ------------------------------------------------------------------------ On 2010-08-26T06:27:23+00:00 Ben wrote: The tell-tale sign is: [drm] nouveau 0000:01:00.0: Reinitialising engines... [drm] nouveau 0000:01:00.0: Restoring GPU objects... [drm] nouveau 0000:01:00.0: Restoring mode... [drm] nouveau 0000:01:00.0: Couldn't find matching output script table [drm] nouveau 0000:01:00.0: Couldn't find matching output script table [drm] nouveau 0000:01:00.0: Couldn't find matching output script table However, not all cases where the "Couldn't find.." message are shown are indicative of a problem, it's perfectly normal in some configurations. This case though, is a bug :) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/622238/comments/11 ------------------------------------------------------------------------ On 2011-06-01T10:58:05+00:00 Bug wrote: This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/622238/comments/15 ------------------------------------------------------------------------ On 2011-06-28T14:18:27+00:00 Bug wrote: Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/622238/comments/16 ** Changed in: fedora Status: Unknown => Won't Fix ** Changed in: fedora Importance: Unknown => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/622238 Title: blank screen on resume from suspend Status in linux package in Ubuntu: Incomplete Status in Fedora: Won't Fix Bug description: Sorry, I found how to debug not working suspend or hibernate, but not how to debug not working resume ... maybe there should be an "activate resume debug" procedure. linux-image-2.6.32-23-generic works linux-image-2.6.32-24-generic resume then go screen blank and nothing works (neither ctrl-alt-del) using nouveau on nvidia geforce go 6100 (Version: 2.6.32-24.41) these are the last line in /var/log/messages (take after cold reset) Aug 21 18:46:22 daniele-laptop kernel: [28802.574557] CE: hpet increasing min_delta_ns to 22500 nsec Aug 22 11:02:10 daniele-laptop kernel: [29049.364114] PM: Syncing filesystems ... done. Aug 22 11:02:10 daniele-laptop kernel: [29049.470760] Freezing user space processes ... (elapsed 0.51 seconds) done. Aug 22 11:02:10 daniele-laptop kernel: [29049.990275] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. Aug 22 11:02:10 daniele-laptop kernel: [29049.990487] Suspending console(s) (use no_console_suspend to debug) Aug 22 11:02:10 daniele-laptop kernel: [29050.130078] sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 22 11:02:10 daniele-laptop kernel: [29050.130179] sd 0:0:0:0: [sda] Stopping disk Aug 22 11:02:10 daniele-laptop kernel: [29052.178951] PM: suspend of drv:sd dev:0:0:0:0 complete after 2048.875 msecs Aug 22 11:02:10 daniele-laptop kernel: [29052.550761] PM: suspend of drv:psmouse dev:serio4 complete after 360.691 msecs Aug 22 11:02:10 daniele-laptop kernel: [29052.650798] tifm_7xx1 0000:04:06.2: PCI INT A disabled Aug 22 11:02:10 daniele-laptop kernel: [29052.670083] b43-pci-bridge 0000:04:05.0: PCI INT A disabled Aug 22 11:02:10 daniele-laptop kernel: [29052.670375] forcedeth 0000:00:14.0: PCI INT A disabled Aug 22 11:02:10 daniele-laptop kernel: [29052.950067] HDA Intel 0000:00:10.1: PCI INT B disabled Aug 22 11:02:10 daniele-laptop kernel: [29052.970096] HDA Intel 0000:00:10.1: power state changed by ACPI to D3 Aug 22 11:02:10 daniele-laptop kernel: [29052.970102] PM: suspend of drv:HDA Intel dev:0000:00:10.1 complete after 280.055 msecs Aug 22 11:02:10 daniele-laptop kernel: [29052.970196] sata_nv 0000:00:0e.0: PCI INT A disabled Aug 22 11:02:10 daniele-laptop kernel: [29053.010057] ehci_hcd 0000:00:0b.1: PCI INT B disabled Aug 22 11:02:10 daniele-laptop kernel: [29053.010067] ohci_hcd 0000:00:0b.0: PCI INT A disabled Aug 22 11:02:10 daniele-laptop kernel: [29053.010086] [drm] nouveau 0000:00:05.0: Evicting buffers... Aug 22 11:02:10 daniele-laptop kernel: [29053.202846] [drm] nouveau 0000:00:05.0: Idling channels... Aug 22 11:02:10 daniele-laptop kernel: [29053.202955] [drm] nouveau 0000:00:05.0: Suspending GPU objects... Aug 22 11:02:10 daniele-laptop kernel: [29053.355421] [drm] nouveau 0000:00:05.0: And we're gone! Aug 22 11:02Aug 22 11:03:59 daniele-laptop kernel: imklog 4.2.0, log source = /proc/kmsg started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/622238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
