Maverick (64 bit) will suspend to RAM on my desktop computer immediately after I boot it up (before I start working). But after I have some programs open, it always fails to suspend. I get the typical blinking cursor in the upper right corner of a black screen. Then, after 20 seconds, the screen comes back on. The logs contain a message that "Freezing of tasks failed after 20.01 seconds." The problem task is usually listed as gnome-panel. Sometimes other tasks are listed too (such as Nautilus). Why will gnome-panel allow me to suspend soon after booting up, but not allow suspend after I start working with applications? I am not changing anything in the panel. And deleting the applets I have installed (system monitor and hardware monitor) doesn't make any difference - the problem continues. As I said, sometimes Nautilus is listed as the task that refuses to freeze.
If I switch users, I can suspend. I assume switching users just puts me in the "clean" state I have with my own user after booting up, so this doesn't really tell me anything new. I have searched all the other threads I can find. Most of the extensive suspend debugging threads are either from the 2007 era or they deal with laptops or resume issues. My issue is failure to suspend on a desktop. As you can see from the logs, I've been working on this for a month already!
Here's a typical error message:
Nov 7 01:52:59 MyComputer kernel: [ 1625.221296] Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze):
Nov 7 01:52:59 MyComputer kernel: [ 1625.221374] gnome-panel D 000000010001fdc2 0 1925 1853 0x00800004
Here's an example log showing 2 tasks that fail to freeze:
Nov 9 01:25:09 MyComputer kernel: [16615.765114] PM: Syncing filesystems ... done.
Nov 9 01:25:09 MyComputer rtkit-daemon: The canary thread is apparently starving. Taking action.
Nov 9 01:25:09 MyComputer kernel: [16615.767512] PM: Preparing system for mem sleep
I upgraded from 10.04 to 10.10 Worked fined, but suspend doesn't work anymore. When I click suspend, a tty1 terminal screen appears, exactly as you would hit ctrl+alt+F1, with the exception that no input is possible. I'm a newbie and an Ubuntu fan but I absolutely have no idea how to solve this...
It looks like something must've slipped the attention of Ubuntu developers as in the previous LTS version laptop suspension after closing the lid worked perfectly fine for me (Dell Latitude D820) while after upgrading to Meerkat it doesn't work any more....well sometimes it does sometimes it doesn't - it behaves sort of like a weather in UK/Ireland ...anyway...is there more information I could provide to you guys or is there something you could give me to point me to the right direction ?
Ubuntu Maverick (64 bit) will suspend to RAM on my desktop computer immediately after I boot it up (before I start working). But after I have some programs open, it always fails to suspend.
I get the typical blinking cursor in the upper right corner of a black screen. Then, after 20 seconds, the screen comes back on. The logs contain a message that "Freezing of tasks failed after 20.01 seconds."
The problem task is usually listed as gnome-panel. Sometimes other tasks are listed too (such as Nautilus).
Why will gnome-panel allow me to suspend soon after booting up, but not allow suspend after I start working with applications? I am not changing anything in the panel. And deleting the applets I have installed (system monitor and hardware monitor) doesn't make any difference - the problem continues. As I said, sometimes Nautilus is listed as the task that refuses to freeze.
If I switch users, I can suspend. I assume switching users just puts me in the "clean" state I have with my own user after booting up, so this doesn't really tell me anything new.
I have searched all the other threads I can find. Most of the extensive suspend debugging threads are either from the 2007 era or they deal with laptops or resume issues. My issue is failure to suspend on a desktop.
As you can see from the logs, I've been working on this for a month already!
Here's a typical error message: Nov 7 01:52:59 MyComputer kernel: [ 1625.221296] Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze): Nov 7 01:52:59 MyComputer kernel: [ 1625.221374] gnome-panel D 000000010001fdc2 0 1925 1853 0x00800004
I recently installed Ubuntu 10.04.1 LTS and have it set to dual-boot with windows 7 on my gateway tablet PC. Since installing, sometimes when I suspend or reboot, my wireless does not work. To be more clear - it is working fine, then I either suspend/reboot, then I come back and no wireless networks show up at all. I can still connect with ethernet cable though. I can solve it by rebooting multiple times (usually around 1-5 times) and then it (magically) seems to work again. I have also tried switching from network-manager to wicd, but the problem persists. With both network-manager and wicd, I've tried simulating a reboot for the wireless by using the command 'sudo modprobe -r iwl3945 && sudo modprobe iwl3945' (network-manager) and 'sudo /etc/init.d/wicd restart' (wicd), but these do not seem to work.
I've had this problem two times before and solved it once by following a guide, the other time by formatting. It always happens when it fails to wake up from suspend. Usually I am unable to even mount the drive or access the files. This one is different in that now I can actually access my files for the most part but this comes up on boot. I backed up most of my files (except it still says I don't have permission to access some of them) but I would like to get it back up and running without formatting. If I boot in recovery mode it stops at this. I took a picture but I rewrote some of it here.
Firewire_core: created device fw0: GUID 00016c000061b4b4. S4??? in/sh: cannot open ro Kernel panic - not syncing: attempted to kill init! Call Trace: [<c05c8283>] ? printk+0x2d/0x32 etc Image posted here: [URL]
I have recently updated my Ubuntu 9.10 install to Ubuntu 10.04 and the default kernel to 2.6.32-23 on my Acer Aspire 5738z laptop with 3 GB RAM and Intel GMA 4500m graphics card.
My problem is sometimes the laptop fails to resume after being Suspended to RAM. The problem is not consistent. Most of the time the system resumes properly but then some times it doesn't . It even doesn't respond to the Magic Keys. I am left with no other alternative but to keep the power button pressed till the laptop shuts down.
I have a Konica 2530DL colour laser and have used it with versions from 6.06 onwards.
However now, with 10.10 I find I cannot print at from most apps eg OpenOffice or PDFs. I get errors on video frame showing on the printer but nothing obvious on the PC.
Test print and gedit text prints works fine and so does using a VM with Lucid running on the same host prints fine too from anything.
Can't see any other comments about this problem anywhere but I know the printer is fairly common and has worked well with Linux in the past.
Using it with IP printing on port 9100 and allow the installation to detect and select the driver. Not setup anything clever and I have the same issue with a Lucid upgrade to 10.10 or a clean install. However the VM running Lucid prints fine. Must be something changed on Maverick somewhere.
I have what I think is a somewhat different failure of standby than I've seen listed on other threads, and I'm stumped.The system hangs on this for a while, then comes back to the login screen without going into standby. This ONLY HAPPENS on a SECOND standby attempt--the first standby after booting ALWAYS succeeds.The standby log doesn't indicate any failures.I had made other changes previously that temporarily got standby working consistently:/etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1"
I'm having problems with resume after suspend to RAM. The machine starts to wake up, but the screens (multi mon VGA and DVI setup) are black and the keyboard doesn't light up. After ~20 seconds there's some brief disk activity and then the computer reboots. 100% repeatable with affected kernel versions. My test method is simple, I boot the machine on the kernel's recovery option, log on as root and run "PM_DEBUG=1 pm-suspend". I haven't found anything in the logs after a failed resume.
Here's the situation: I have a SSD disk. To get TRIM support I have to use kernel 2.6.33 or later, which means that the standard kernel in Squeeze is too old.I have Nvidia graphics, and there was a change in 2.6.34 that breaks older versions of xserver-xorg-video-nouveau (version 0.0.15, used in Squeeze), I can't use Debian Squeeze with a kernel newer than 2.6.33.x.My machine (XFX GeForce 9300 motherboard) won't resume from suspend to RAM if I use a kernel newer than 2.6.36. There are no BIOS updates available.
My options: Install newer kernel from Squeeze backports (22.214.171.124 last time I tried). <--- Not doable b/c of resume problems. Upgrade to Wheezy, which uses kernel 3.0.x. <--- Not doable b/c of resume problems.Compile a vanilla kernel. So basically I'm forced to compile my own vanilla kernel, 2.6.33.x on Squeeze or 2.6.35.x on Wheezy. I won't be stuck with an unsupported kernel version in the near future, but so far I've failed miserably.
I know that the latest kernel version where everything works is 2.6.36.x (no longer maintained), 126.96.36.199 and later cause resume problems (I've tried 2.6.37, 38, 39 and 3.0.0, .0.1). I've tried doing a git bisect on the kernel, but didn't succeed, ended up on 2.6.36-rc5 which is weird considering that 188.8.131.52 works. There may be several suspend/resume bugs in different kernel versions that messed up the bisecting results.
Are there any logs that you would like me to post?
I have tried reinstalling the NV display driver via "additional drivers" in the live CD, but they do not appear to be being retained on the HD version of Ubuntu. When I go back into the live cd the driver is not installed.
How can I switch the proprietary driver back on in the hard disk when I am running the live disk.
Is there a repair system program?
If not is there a way of forcing an upgrade on an upgraded system so that missing files are reinstalled?
If that does not work what should I do next to get the GDM to load?
I have a desktop system (P55-USB3 + Core i7 + Ubuntu 10.10) that fails to suspend/resume from memory. So I'm trying to diagnose the problem. The first obstacle was easy enough --- when I put the system to sleep to memory, the computer comes back alive right away. A look at /var/log/kern.log revealed that one USB device (usb10) failed to suspend, and from there I was able to pin it down to the USB3 controller in the BIOS. Disabled that and this problem disappeared.
Now, I'm stuck with the second obstacle. The computer successfully goes into the suspend mode, but it hangs during resume. The monitor doesn't get any video signal, and it fails to respond to ping (netconsole doesn't work either.) After a forced reboot (that involves unplugging the power cable), /var/log/kern.log doesn't contain any interesting entries. All the pm_test modes from freezer to core succeed (I followed [URL] I've also tried pm_trace (https://wiki.ubuntu.com/DebuggingKernelSuspend) but again kern.log nor dmesg contains anything after the suspend. Either the write didn't survive the forced power off, or the resume is failing even before that. The motherboard doesn't have a serial port nor firewire, so getting kernel logs through them is not a possibility, either.
I've just started using OpenSuse 11.2 KDE. I have KDE4.4 installed. I had this issue with KDE 3.4 as well. My HP Multimedia DV3065 laptop is encountering an issue with suspend/restore. After restoring, the mouse is frozen. I have already tried a few things.
1. Dropping to init 1 and then back up to init 5 did not provide a temporary fix. So this is probably hardware related in some sense (kernel?) 2. I tried a grub option (cant remember what it is now). i8500-reset something like that. It made no difference. 3. I tried modifying my 99ZGrub file per another posts suggested solution. That actually locked up my laptop and I could not reboot (even after a cold boot). I pulled the battery and let it sit for a bit and it booted again
So I have several issues.. 1. I would like suspend to restore my mouse. 2. I have not figured out how to program my Sleep button to Sleep. My menu bar icon has Log Out / Restart / Turn Off. The ALT+F1 menu tab Leave has those plus Sleep and Hibernate.
I've been struggling with suspend to disk (hibernate if you prefer) for a while, it works after a fresh boot and for several days' worth of overnight hibernation as I go about my work, but eventually it stops working - it gets to the splash screen but the bar only makes it a little way to the left before stopping, and then after a timeout the system just returns to the "session locked" screen - no real error messages.
I've done my best to try to find out what's causing it to break but I'm really struggling, the suspend process doesn't appear to write anything helpful to the dmesg log or the /var/log/pm-suspend.log - the only thing that I've seen at about the right point in time is cifsd, but I can't be sure that it's a problem with cifs as hibernate continues to work immediately after mounting windows shares with cifs.
My hibernation was working out_off_the_box but now it has strange issue. This is debian testing with kernel 184.108.40.206 "hibarnation-disk" hibernate successfully ,with an error though ( seen from hibernate-disk -v2 --dry-run) hibernate-disk:Warning: Tuxonice binary signature file not found Anyhow , after executing the hibernation , on the next boot, the system boots from scratch and not from the resume image. During boot a message is displayed though Invalidating stale software suspend images I have done some google search but none of the solution work so far, including reinstalling the package itself.
I am running Squeeze on an older Compaq EVO laptop with radeon graphics.
A few months ago, after an upgrade, suspend and hibernate stopped working. The suspend or hibernate worked fine, but the resume just hung with a black screen. I finally got around to looking into it and found a workaround.
The workaround is to disable Kernel Mode Setting for the radeon. This can be done by adding the boot parameter "radeon.modeset=0" or by editing /etc/modprobe.d/radeon-kms.conf so that it includes the line "options radeon modeset=0".
If you are interested in the details, you can search for problem reports related to radeon kernel mode setting.
F12 on my aspire one (A110, the original 8Gb SSD model) works well with only one significant problem.
Suspend fails; the screen fades to black, backlight stays on, macine stops responding to keyboard/mouse/powerswitch and just hangs (for at least an hour... longest I left it). Only thing that works is a 5 second click of death on the powerswitch. Plus an FSCK on at least one occasion after reboot. I have not been able to check if SSH and shutdown possible (on vacation) plus have logs go to a tmpfs (to save my SSD) so no log info. Similarly I cannot confirm if this affects hibernate because I run without a swapfile (SSD again, i.5Gb ram installed and I have never come even close to running out of memory).
But I think I have the culprit anyway:[url]
As described there; shutdown fails if there is a mounted card in the cardreader slot (/dev/mmcblk0) My system has a 4Gb SDHC card in the LH slot with a single XFS filesystem; which has my homedir on it; if I unmount that filesystem (but do not remove the card) shutdown and restore appear to work properly. But if the filesytem is mounted I get the bsod. Linked bug suggests this is restricted to large filesystems (?SDHC?) but I have not fully confirmed, although that matches my situation.
Posting here to see if anyone has any further info/workarounds, to ensure the fedora crew are aware that this appears to affect F12 (and is a regression, F11 suspended fine) and make sure it is documented somewhere. The linked bug also states similar bad suspend activity on other netbooks.
I'll try some other variations (and see if it also happens with USB sticks/RH cardrader, and report back here.
If I suspend this toshiba satellite, and the battery is or gets low it will wake from suspend to tell me that it will need to suspend due to a critical low battery. Which is pretty dumb. I've experimented with this by plugging and unplugging the ac adapter.
Just got Ubuntu 9.10 and I'm liking it a lot, but my computer refuses to go into hibernate or suspend. I have a Dell M1530 but I don't really think it's a dell hardware issue because it's not just when I close the screen, it's also when I click suspend or hibernate from the menu.
I have a 14TB raid, file system is read-only and I am trying to run e2fsck -B -p -C -v -y /dev/sdb1, it goes through, but fails and says bad block/inode or fails to transfer, something like that.Is there a way I can get this to run successful, this is a production storage server, its critical.
I am trying to upgrade RH9 to F10. I have downloaded dvd iso image i386. The SHA1 integrity check passes. The installer fails media check due to "errors". I did an independent verification of the DVD and zero errors found. Download was from Fedora's own torrent, so files should be verified anyway. If I bypass the media check I get the message : Running anaconda 220.127.116.11 the Fedora system installer - please wait.....
I was running Ubuntu 10.04 and yesterday I decided to test drive the 10.10 beta. After updating to 10.10 and rebooting, all I now get is the login screen with all the icons displaying as an 'X' and more importantly, no actual login prompt. I know just enough about Ubuntu to properly break it, but I am at a loss as to how to fix this, since it doesn't give me the option of opening a terminal.
Today I upgraded my Lucid to Maverick. After upgrading, from "update-manager -d", I tried a couple of new programs (games, actually) and re-enabled the third party repositories. I don't have exotic things, just google chrome, transmission beta, and some more of this sort. After rebooting, the system enters in terminal instead of the regular gui. I tried to search online for possible solutions, but none worked. I tried
(1) startx output: fatal server error, no screen found. (2) sudo service gdm stop; sudo service gdm start Output: gdm start/running process 1265
(3) removing the option nomodeset from the boot. To do this I edited /etc/default/grub, the line with the GRUB_CMDLINE_LINUX and ran grub-mkconfig. After a reboot, the computer returned to the terminal.
(4) some even suggested removing /etc/X11/xorg.conf, but I don't have that file...
I have an acer timeline with initial hardware. I don't know which graphics card it has, if any... I really need to get my computer running, and I was looking for suggestions before reinstalling 10.04.