Ubuntu :: Kernel Panic - Fails To Wake Up From Suspend
Apr 21, 2011
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]
Because I am using one of the new WD disks I am trying to aling my root partition with the real sectors, as described here: [url]
So I copied all files to a temp location, deleted my partition (/dev/sda3), recreated it a few cylinders later (same name) and copied the files to the newly created partition. I updated UUIDs in grub's configuration as suggested in this thread:[url]
But now it fails to boot with the following error:
Code:
I checked the filesystem on this partition and its fine. I tried to recreate the initramfs from Knoppix:
Code:
But it didn't change anything.
How can I either fix it or install a different kernel on this drive so I could boot into it and re-install my default kernels?
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 (2.6.38.2 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), 2.6.37.0 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 2.6.36.4 works. There may be several suspend/resume bugs in different kernel versions that messed up the bisecting results.
new to Ubuntu and enjoying using it, trying out Ubuntu as an alternative to vista, the only thing i have been able to do is suspend and then wake my pc, it fails to wake, is there a workaround for this
have changed settings so pc sleeps after 1 hour, it was on never, i,m running ubuntu9.10 my pc will wake but i have a black screen with mouse icon showing but i,m unable to get any response, all well again after a reset
put pc in suspend and went out, on returning home started pc via on/off switch instead of pressing space bar (any key) hey presto Ubuntu woke up no problem
I'm running Linux Mint 9 (aka Ubuntu 10.04 + a couple of tweaks), and my machine won't wake up from suspend.It hasn't done so successfully since Ubuntu 8.04. I'm running the default graphics driver (not the proprietary NVidia one) on a quad-core Gateway FX. How can I go about figuring out the problem?
All I want to do is to be able to shut the lid on my laptop, have it go into suspend like it already does, but upon opening it again, successfully start up again. It'll sleep just fine, but if you close the lid and try to open it again later, the lights will indicate it is starting up, but the screen won't initialize, and I am left with a blank, black screen.I've tried a line of code to enter into my menu.lst file, and it seemed like it should work, but it borked my computer and I had to manually reinstate the line of code it had before.
I can Suspend or Hibernate my Gateway notebook but I have no idea how to wake it up.The power button is set to suspend or hibernate....I not sure which it does, but I can't wake the computer up.
For some reason when I wake my computer up, there is no sound. No matter what I try through the terminal, or by playing with the volume controls, no audio. I can only get audio working again by a restart.
My computer runs really well when I first switch on, and usually I'll leave it on all day, and just suspend it when I'm not using it.But since a couple of days ago, it's been playing up after waking from suspend. Everything slows to a crawl, and the system monitor shows the CPU working at 96-100% permanently, even when I'm not doing anything.It's not like I even have many apps open. Generally I'll have a few tabs going on Opera, have Thunderbird open, and Gwibber. I'll open and close gedit and gimp as I need them, and that's about it. Having said that, this new version of Thunderbird seems very slow to me compared with the previous one.
Here is the latest in my saga of me vs. Suspend in Utuntu.
Dell Studio XPS 8000 desktop i7-860 CPU 8 GB RAM swap area set to 9 GB (because I was experimenting with hibernate) nVIdia GeForce GT220 1 GB Ubuntu 10.04 64 bit, all patches, nVidia-current 195.36.24
So I was poking around in BIOS and looking at CPU Features. I have also a problem with my VMWare machines sucking up a core or 2 at 100% after suspending and waking the host. Just for the halibut I Disabled CPU Visualization. My VMWare XP guest now starts up a lot faster! (?) and I have discovered. If I do a suspend of the host BEFORE starting and LOGGING IN to a VM it seems to work great. I can wake the host and am presented with the locked screen dialog asking for my password. I have done about 20 suspend/wakes with no problems. So far, so good.
Upon further testing I find that I can start a VMWare or Virtualbox XP guest machine and still suspend/wake - at least so far with a limited number of tries. Most importantly, if I log into the guest (VMWare or Virtualbox) I find that suspend/wake fails 100% of the time. By fail I mean that the host suspends but when I attempt to wake it I find that I am logged out of the host and all programs which were running at suspend time are no longer running. Firefox restores the previous session indicating that it was shut down incorrectly or unexpectedly.
It was working in version 9, after I install the new one Ubuntu 10.0.4 LTS, it can not wake up after hibernate and suspend. I am using Dell studio Desktop
I am running 11.04. After an update about a week and a half ago, the time to wake from suspend increased from about 3 seconds to well over 40 seconds. It now, sometimes, takes me longer to wake from suspend than a normal boot takes. Has anyone else encountered this problem/found a fix or workaround?
Suspend worked before I completely reinstalled Testing from scratch. Now it seems to suspend OK, but when it tries to wake up it fails. Details here: [URL]
I have an Acer 1551 4755, with Debian Squeeze. Normally my Debian Squeeze installations and suspending work fine on my other 2 laptops. For some reason this one is troubled. I can put into sleep with "pm-suspend" or "pm-hibernate" but the thing is that my laptop never wakes up. I endup restarting.
I use my laptop connected to an external monitor, so I would like it to wake up from suspend with a wireless keyboard. I could manage to do it when the lid is open, however, when the laptop lid is closed, it doesn't. So I need to open laptop lid each time and it is annoying.
This is how I make it wake up with wireless keyboard:
Firstly, wol works fine from shutdown and hibernate; it's just suspend which doesn't work.
I've got 2 types of workstations, all running 11.1. They both have this kernel: 2.6.27.45-0.1-default #1 SMP 2010-02-22 16:49:47 +0100 x86_64 x86_64 x86_64 GNU/Linux
Type 1 is a dell optiplex 745, bios version 2.4.1. Here's the relevant bit from lspci: 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5754 Gigabit Ethernet PCI Express (rev 02) Kernel driver in use: tg3 Kernel modules: tg3
[Code]....
The fact that it's happening across two different machines makes me wonder if it is some OS setting I've missed, but then maybe neither card/driver supports it from suspend.
I'd really like to get them waking from suspend because training users to use suspend rather than hibernate would be a pain. Also, being able to configure such that it only wakes from suspend and not hibernate/shutdown, as implied in the bios, would allow me to wake machines up for backups etc only when the users are here, rather than on holiday/seconded to another department etc.
I have an USB keyboard attached to a laptop, and I can suspend the laptop via the sleep button on the keyboard. However, I can't wake the computer again by using either the connected USB mouse or the keyboard. How do I fix this? I am running Ubuntu Netbook Version 10.04.
I am trying to make my computer to wake from suspend by either pressing a key or clicking the mouse. (It doesn't by default.) I have a Logitech EX100 Cordless Desktop. I tried enabling USB1 (the port the receiver is plugged into) in /proc/acpi/wakeup, but now the computer wakes up instantly when I try to put it to sleep. Anyone know how to make it stay asleep, and then wake up when I either click the mouse or press a key?
I have openSUSE 11.4 KDE (upgraded to Tumbleweed but that's not relevant here). The computer is a Dell Optiplex. My sleep (suspend to ram) and wake (restore from ram) work very well. The box can multiboot to windows 7 as well as to Linux.
In Linux, the restore process is triggered by pressing the power button on the front of the case. No other action will bring it awake.
In windows, the restore process is triggered by the power button but also by moving the mouse or touching the Escape key, spacebar etc.
Here's the question: how do I get the computer to wake in Linux by activating a key (or mouse, whatever) instead of just the power button (which is under the desk and hard to get to)?
I'm running Ubuntu Hardy 8.04 and in the UK we changed from GMT to BST last Sunday (27th March) On GMT I was waking on LAN at 23:30, all was working fine then we changed to BST. What I usually do is leave the BIOS clock on GMT and change the Wake on Alarm to 22:30. I did this, shut down Ubuntu fine, but its not waking up at all at 22:30, or any other time I set the WOA to. I had this problem a few years ago on an old ASrock mobo and cant remember how I sorted it - maybe by blanking the bios, cant remember.
I have recompiled a few kernels, but all on 32bit systems so not sure if that has anything to do with it.
Running Arch Linux 64bit, most recent version.
Kernel Output:
Code:
My first thoughts was that it might be my grub bootloader configuration, so had a big play around with that but it didn't fix it. Also made sure support was built for filesystems. However almost all that Fstab mounts are ext3 anyway, and certainly the root and /boot are. Now thinking it may be a memory error so will run a check when I shutdown.
Dell laptop booting from a USB stick with a CentOS 5.5 minimum installation.
Uncompressing Linux...OK, booting the kernel. Red Hat nash version 4.2.1.13 starting sda: assuming drive cache: write through sda: assuming drive cache: write through mount: error 6 mounting ext3 mount: error 2 mounting none switchroot: mount failed: 22 umount /initrd-dev failed: 2 Kernel panic - no syncing: Attempted to kill init!
1. Does minimum installation not drop on a kernel or initrd with ext3 support? I can't imagine that's true, but have to ask.
2. The USB stick is single partition ext3. Maybe there is some limitation specifically related to USB stick booting that requires boot to be FAT16 or FAT32? Except the CentOS 5.5 installer refuses to let me install on either FAT.
3. How can I do the equivalent of lsmod on a linux installation that will not boot? i.e. I have CentOS x86_64 running in VirtualBox, I can plug the USB stick in there, so how do I get information on the USB stick's kernel and initrd if I can't boot from it?
4. Is it possible to rebuild the i386 based initrd on this USB stick, when the computer is not booted from that stick, with a system that's x86_64 based?
System Info: Dell Latitude i686 Laptop which has run CentOS 5.5 and Fedora 12,13,14 in the past, and boots from Fedora 14 Live CD transferred to a USB stick. So I know USB booting is possible on this machine, and this stick.
The process of creating the stick:
CentOS 5.5 i386 on a USB stick. Old Dell i686 laptop which has previously run CentOS 5.5 installed from DVD, and has successfully booted from this same USB stick holding transferred Fedora 12,13,14 Live CDs. CentOS 5.5 was installed onto the USB drive directly by the CentOS 5.5 DVD installer (running virtualized in VirtualBox 4.02 on Mac OS X 10.6.5.). No errors or complaints during installation.
For whatever reason, the installer did not do some things correctly. First Grub wasn't working correctly, I got that sorted out and have the Grub+CentOS splash screen, it finds vmlinuz and the initrd, and then I get a kernel panic.
Ext3 was built into the kernel and that's why I'm getting this message. I do not know how the installer would have dropped a kernel or initrd during instalation that that don't contain such a basic thing that obviously comes in linux kernel 2.6.18-89 EL.
I have the following strange thing with a RHEL4 installation. Since last week, the system did a reboot and now something is really fucked up. During boot we get the following messages (don't care about 'strange' typo's, my colleague typed it 'blind' from the screen)
Code:
The strange thing is that we never see a 'could not mount blabla' or similar messages. First we thought it was a failing kernel update by plesk, but even after manually updating the kernel with RHN RPM's, still the same message. Booting with rescue mode and then chroot the system works. After that we even can start things like plesk and so on.
We double checked things with another RHEL4 install, and at least two things were odd:
1: the working machine has /dev/dm-0 and /dev/dm-1, the broken one doesn't
2: some files on /dev didn't have group root, but 252
We tried to recreate the /dev/dm-X nodes with [vgmknodes -v], output:
Code:
A fdisk /dev/sda shows: /dev/sda2 XX XXX XXXXX Linux LVM (I removed the numbers because this line is from another machine, but rest was identical)
We have a copy of the boot partition so if one need more info please let me know.
grub.conf:
Code:
last part of init extracted from initrd-2.6.9-78.0.8.ELsmp.img:
I am running an Hp Pavillion dv6000 with the Broadcom card that never seems to work for Linux. I recently talked with my friend who said he found a way to get it work.following his instructions I opened Synaptic and checked the package bmcwl-kernel-source to be installed.I went through the process of it all and it said it had install successfully. I restarted the computer and when I tried to enter my operating system I got this error "Kernel panic - not syncing : VFS : Unable to mount root fs on unknown - block(8,1)" I have previous versions of Linux on my computer so I can still get in to those if need be but I don't know how to undo what I did or why it isn't working for that matter. Does anyone have any ideas as to why I am getting this error and how I can fix it?
I have one machine where I have several versions installed on different partitions. The base partition (/dev/hda1) is Slack 12.1. On a spare partition (/dev/hdc4) I had installed Slackware64-current. Last week I slackpkg upgraded and installed the 2.6.32.2 kernel, and now that partition will not boot. I know that with the new kernels the hd* designation has been removed, and have already redone that fstab (accessing it from a different boot) to reflect the sd*. Here is the slack64 section of my lilo.conf:
Code: # Linux bootable partition config begins image = /other/spare4/boot/vmlinuz
this is what i did i downloaded the latest stable kernel archive from kernel.org and extracted the archive into the download directory (i don't think that matters though) then i downloaded and installed the ncurses archive (needed for menuconfig) then i opened a terminal and navigated to the directory that was extracted from the archive and issues the floowing commands
I am running a Fedora 12 installation in my bedroom as a slave mythtv frontend. I have set it up to be able to put the PC to sleep and wake up with a MCE remote. This has been working for near on a year now with no issues. Yesterday I did a yum update and ended up with kernel 2.6.32.16-141.fc12.i686.PAE (up from 2.6.32.12-115.fc12.i686.PAE)
Now everything seems to work fine however I can put the PC to sleep with the remote but I cannot wake it up with the remote. a cat of /proc/acpi/wakeup shows
At the grub prompt if I select the old kernel 2.6.32.12-115.fc12.i686.PAE then the computer will start up with no graphical prompt (need to figure out how to work kmod-nvidia i guess), but I can use the remote to put the pc to sleep and wake it up again. Also using the old kernel and telneting into the PC I see that /proc/acpi/wakeup is no different. Does anyone have any clues on hoiw to get wakeup to work with this new kernel? Or how do I roll back everything to the older kernel and get my graphics driver back (i tried to reboot with old kernel and then yum erase kmod-nvidia-PAE and then yum install kmod-nvidia-PAE but no luck.
Another thing worth noting is that I can wake the computer with the power button, just not the USB remote. THere is also nothing in the motherboard bios for setting wake on USB.
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:
Code:
Nov 9 01:25:09 MyComputer kernel: [16615.765114] PM: Syncing filesystems ... done. Nov 9 01:25:09 MyComputer rtkit-daemon[1738]: The canary thread is apparently starving. Taking action. Nov 9 01:25:09 MyComputer kernel: [16615.767512] PM: Preparing system for mem sleep
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
