Anyone Using RAM Disk?
I've used the freeware program "Make RAM Disk 1.0" with Tiger 10.4.11, and it appears that when I use this with an intensive read/write situation (say I'm creating an image of a video file) that the process is accelerated, saving me time. I was wondering a couple of things...
1) Does anybody else use this program with Tiger, and have you noticed an increase in speed with your read/write times?
2) Am I just imagining this, or does this process of making a RAM disk really work, in theory, with OSX?
Thanks!
Yes, I use one and yes it helps +a lot+ depending on what you use it for. I can't believe how negative people are about them, and why you can never get a straight answer, so here is a straightforward (mostly) complete answer.
Benefits:
Anything that uses a scratch disk will benefit form a RAM disk. Video and image processing times will be greatly improved. Rendering 3D objects will be much faster.
Any program that requires a lot of real-time disk access will benefit from faster seek times.
It reduces power consumption. If you watch a movie on a plane, put it on a RAM disk. It will save your battery life.
Security is improved. Anything on the disk at shutdown is gone forever, no need to wipe the disk.
Increases your hard disk life. The less you use your hard disks the longer they last. The more you use a RAM disk the less you use your hard disk. Hence, the more you use a RAM disk the longer your HD will last.
Risks:
It works like any other drive +so long as the computer is running+. If you lose power or shut down the machine you lose whatever was on the disk forever.
To state the obvious: it uses up some of your RAM.
Mac OS X has the ability to create a RAM disk built in just like OS 9. Unfortunately, Apple decided to remove this feature from the GUI. Here is how to do it via the command line:
diskutil erasevolume HFS+ "RAM disk" `hdiutil attach -nomount ram://4629672`
This will create a 2.2GB RAM disk, which is the maximum size (currently). If you want to create more than one replace the "RAM disk" with "RAM disk2", "RAM disk3", and so on.
If you don't like dealing with the command line you can use Esperance DV which is freeware. It also has some nice features like restoring at startup and automatically moving the Safari cache to the RAM disk.
Finally let me say there are a lot of technical details I left out, none of which affect the basic points that RAM is faster, more secure, and uses less power than a HD.
Similar Messages
-
Photoshop CS4 does NOT use RAM as scratch disk
Photoshop CS4 does NOT use RAM as scratch disk
as far as I can tell.
I have 20 GB RAM and still Photoshop uses the hard disk as scratch disk.
(OS = Win 7 64).
Can I force the use of RAM as scratch disk?
/LarryHi PECourtejoie,
I really try to understand this, please.
I don't know if 'Hitting the hard disk brings unacceptable slowdowns in my workflow'.
Because I don't know what unacceptable slowdowns are.
Any operation in Phshp takes time, and you always want it to go as fast as possible..
I know that if Phshp only worked against RAM instead of constantly saving to (and reading from) the hard drive it ought to go faster.
But I still don't know if this is the case, because there is a constant use of a tempfile on the hard drive's Scratch disk!
So far I understand that Phshp may BOTH work in RAM AND save data to the hard drive Scratch disk.
It could be possible that the writing to the hard disk happens when Phshp is idle from other tasks and that the reading only happens when data has disappeared from the Cache in RAM.
That could be a scenario where a Scratch disk on Hard drive doesn't interfere with Phshps performance, and an explanation why we should not bother about the Scratch disk on the hard drive.
But I would very much like to have some confirmation on this, IF this is the explanation of how the Scratch disk on a hard drive works without influencing Phshp's performance??
Everybody just seem to assume that Photoshop uses (some) parts of RAM as work space - I just need a better understanding of this. And some correct descriptions.
/Larry -
Anyone using non Apple ram with standard heatspreaders?
Hi,
Is anyone using non standard Apple ram with normal sized heatsink/heatspreaders and if so have you had any problems?
I can find ram for the same spec that works but they only have the standard thin silver heatspreader attached and am concerned about running temps etc.
If anyones using these modules without problems, please post here!
Thanks.Might want to read this article and it has some good information to help you decide.
-
Has anyone used an app with the new Maverick software to burn iphoto slide shows to DVDs that will play on a standard DVD player? This probably cannot be a demo app in that the amout of photos on the slideshows is large.
Thank you,
JimExport the slideshow from iPhoto, that makes a movie of it.
Do you want to use this DVD in a domestic DVD player? If so, then the disk will have to be 'authored' to make it the correct form for that. If you have iDVD then that's the app you use. However, iDVD is no longer developed or distributed by Apple. You may be able to get it on an old iLIfe install disk.
Other options:
Burn: http://macupdate.com/app/mac/21992/burn
Toast: http://macupdate.com/app/mac/6351/toast-titanium
But there are lots of others too. Search on the App Store or MacUpdate -
Hi!
My Photoshop seems to use scratch disk instead of RAM.
Here's the scenario: I open up a file, convert it to a smart object and begin tiling it in a new document.
In task manager the memory usage for Photoshop.exe doesn't grov very much, it's around 300mb when I've duplicated my picture a few times. My scratch disk however has a temp file weighing 5gb! Task manager says also that the total usage of my physical memory is only 23%.
I have 8gb of RAM installed and I have my Memory Usage Settings set to Let Photoshop Use 5.4gb.
Now why is it that Photoshop uses my scratch disk even though I have lots of free RAM available? I thought Photoshop only uses scratch disk when the RAM is full?
I have Windows 7 64-bit with Photoshop CS5.antevante wrote:
Now why is it that Photoshop uses my scratch disk even though I have lots of free RAM available? I thought Photoshop only uses scratch disk when the RAM is full?
It's unclear how big a file you are talking about-doesn't seem to be very big? Photoshop by default will always allocate scratch disk space upon launch. Whether or not it uses it depends on how much ram you have and how big the image is. Photoshop tries to keep it's operations in ram and only goes out to the scratch disk when needed.
However, Photoshop always uses scratch disk space to track history. If the history step is only a small area tile it doesn't take up much space. If it's the whole document, history can very quickly suck up the scratch disk space. By default the History is set to 20 steps, if you do something involving the entire file, the scratch disk usage could end up being 20X the original file size depending on the number of steps you have in history. Note, the History feature doesn't actually steal ram from Photoshop...it's only writing to the scratch disk but it can get real big real quick and you've found out. -
Experiencing serious problems with lion, I would like to install snow leopard instead of lion on latest macbook pro MD318 (oct.2011) Does anyone know if this is possible? If so, please tell me how. Will I have to use install-disks of previous model (eg. MC721) ? Or will retail-disks serve?
Thanks stephSnow Leopard is currently running on this MBP 15", late 2011 model, due to my need to run an old version of FileMaker.
A retail disk with 10.6.3 did not work, I restored my previous Snow Leopard install with Disk Utility.
However, it is not the shipped software and is not officially supported on this Mac. Therefore, your advice to troubleshoot Lion is the best option. -
Anyone clean their mac using the disk utility using the repair disk permissions??
anyone clean their mac using the disk utility using the repair disk permissions??
No. Threads don't hurt anything. If your computer is not functioning properly perhaps you need to try some basic maintenance. Let's start by having you do this:
Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
Next, try booting into Safe Mode then immediately restart normally. Safe mode is going to take a while so be patient. It's slow.
Next, create a new user account. Log out of your account then log into the new account. Try using iPhoto and the publishing button. Do they work now?
If you still have a problem, then do the following. If you don't want to go through the above then just start with the following and forget the others above.
Reinstall OS X without erasing the drive
1. Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Reinstall Snow Leopard
If the drive is OK then quit DU and return to the installer. Proceed with reinstalling OS X. Note that the Snow Leopard installer will not erase your drive or disturb your files. After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
Download and install Mac OS X 10.6.8 Update Combo v1.1. -
I had a hard time finnding info on RAM disks in OS X so I am posting it here for anyone it might help.
Mac OS X has the ability to create a RAM disk built in just like OS 9. Unfortunately, Apple decided to remove this feature from the GUI. Here is how to do it via the command line:
diskutil erasevolume HFS+ "RAM disk" `hdiutil attach -nomount ram://4629672`
This will create a 2.2GB RAM disk, which is the maximum size. If you want to create more than one replace the "RAM disk" with "RAM disk2", "RAM disk3", and so on.
If you don't like dealing with the command line you can use Esperance DV which is freeware. It also has some nice features like restoring at startup and automatically moving the Safari cache to the RAM disk.
Benefits:
Anything that uses a scratch disk will benefit form a RAM disk. Video and image processing times will be greatly improved. Rendering 3D objects will be much faster.
Any program that requires a lot of real-time disk access will benefit from faster seek times.
It reduces power consumption. If you watch a movie on a plane, put it on a RAM disk. It will save your battery life.
Security is improved. Anything on the disk at shutdown is gone forever, no need to wipe the disk.
Increases your hard disk life. The less you use your hard disks the longer they last. The more you use a RAM disk the less you use your hard disk. Hence, the more you use a RAM disk the longer your HD will last.
Risks:
It works like any other drive +so long as the computer is running+. If you lose power or shut down the machine you lose whatever was on the disk forever.
To state the obvious: it uses up some of your RAM.
Finally let me say there are a lot of technical details I left out in describing the benefits, none of which affect the basic points that RAM is faster, more secure, and uses less power than a HD.Slow down a bit and think this through.
CUPS on linux is nearly identical to CUPS on OS X - but there is no Mac-to-Mac Apple proprietary print sharing. Rather, on linux you are sharing the printer using standard printing protocols. Just like on the Mac (when using the standard protocols like Windows/SMB or IP printing), linux print queues expect postscript input. Try using a generic postscript driver from the mac.
And when you add the printer via Windows Printing or IP > LPD or IPP, you will need to know the queue name for that printer from the linux box. (one computer with one IP address can have multiple printers - so what's the additional address info to print to your desired printer? - queue name.)
HTH -
Has anyone used the mackeeper software?
Has anyone used the mackeeper software?
Short answer: I don't recommend it, but it's not "a scam" or malware, per se. If you use it, you may have some real performance issues.
Me: I was an actual MacKeeper user (paid version) for about two years. What follows is my experience and conclusions. I am not a paid reviewer, nor tech professional. I am an educator with about 15 years of experience using Macs. I am what most people would call a "prosumer," in that I know a good deal about my systerm, but am not a techie, anti-utility software zealot, etc. I have no affiliation with Zeobit (manufacturer of MacKeeper) nor any of its competitors.
I bought MacKeeper in 2011, and then upgraded last year. I used it to remove junk files and duplicates, and experimented with the anti-virus software. I didn't use most of the other features.
The problem: I am running a 2009 15" Macbook Pro 2.8GHZ Core 2 Duo, 4GB RAM, 512GB HDD. Over the past year, it has been having major performance issues. Slowdowns, hangups, applications quitting and more were all becoming the norm. I deleted duplicate files and ran MacKeeper a few times a month. I also ran permissions repairs regularly (disk utility). I looked for the cause of the slowdowns everywhere, from too many user accounts being open, to resource hogs. I decided that MacKeeper's Anti-Virus software was just taking up too much RAM and CPU, so I disabled it. I continued experiencing slowdowns and started monitoring my available RAM with a freeware app called Memory Clean. It often reported that I had less than 500MB available, even with very light usage, application wise. After "cleaning" memory, I could get my available RAM to about 1.5GB, max. I struggled with these issues for a year or more, and was about ready to concede defeat and buy a new machine. I figured my MBP was over four years old, and perhaps running Mountain Lion and normal wear/tear were just too much.
This morning, I noticed that the biggest resource hog on my system was a process called "MacKeeper Helper." The process relaunches even when it is forced to quit. It was consuming over 100MB of RAM and up to 99 percent of my CPU at times! I also noticed a process called "anti-virus" that also could not be quit, and was consuming over 100MB of RAM itself. I started researching how to kill these processes, and was introduced the the Great Online MacKeeper Controversy. Here is what I learned:
Some in the Mac community have pure hatred for this product (and some hate all like it).
There were numerous user reports of it slowing down systems
Zeobit seemed to be guilty of questionable ethics, particularly in its advertising.
There was no way to stop MacKeeper Helper and Anti-Virus processes from running with deleting the entire application.
I wasn't the only one annoyed by MacKeeper's system pop-ups, trying to sell me something I already bought.
The software got good professional reviews, even from well-respected publications (e.g. MacWorld)
It is often confused with Mac Defender, which WAS malware. They two are not associated.
The Decision: After researching ways of fully uninstalling MacKeeper (and considering whether or not I should), I decided to try the uninstall instructions from the manufacturer. It said that it would remove ALL traces of the application. I also didn't want to get into too much Terminal work and manually deleting things, as some users suggested doing. I followed the process (close app, drag to trash, enter password, click "uninstall"). I then ran a permissions repair and restarted.
The Results: I have been MacKeeper-free for about an hour as I write this. Put simply, my problems appear to be completely solved. MacKeeper Helper and Anti-Virus are gone. Available RAM is now up to 2.75GB. I have experienced no slowdowns or app crashes. Even bootup appeared to be considerably faster. Launching iPhoto with thousands of images now takes a few seconds instead of minutes. Everything feels faster. It's like I have my Mac back! I was ready to admit defeat and dish out another $2500+ that I didn't have. I now think that won't be necessary!
What Should Yo Do? You'll find a lot of controversy out there between professional reviews, ethically dubious paid reviews, Zeobit's own defense through public statements, and Mac users themselves. Some users like it, and swear up and down they are real people. Others are extremely angry and hate the product with the passion of 1,000 burning suns. All I can do is tell you my experience and make the following statement:
The bottom line is that I would not install MacKeeper/buy MacKeeper on my Mac. After investigating my own system's problems (which made iit nearly unusable) and concluding that MacKeeper might be the issue, I uninstalled it. Magically, all my issues went away. So...I report, you decide. Best of luck. -
I forget how to create a RAM disk in OS 7.x. Does anyone know?
How much RAM do you have installed in your Mac? Using some of it for a RAM disk may cause your Mac to run slower. Also, you should know that if you have to zap PRAM to "fix" a problem, the RAM disk contents will be erased.
Cheers, Tom -
Anyone use Citrix receiver (11.8.2) successfully on Yosemite yet?
Anyone use Citrix receiver (11.8.2) successfully on Yosemite yet?
I want to upgrade, but this is the 1 app that has to work for me before I take the leap.DrDavidW,
After seeing your failed upgrade, I decided to upgrade one of my wife's laptops that had Citrix Receiver installed. The hardware is a late 2008 Macbook Pro 15" with 2.4 GHz Intel Core 2 Duo, 8 GB 1067 MHz DDR3 RAM, and 250 GB SATA Disk that has 212.99 GB free. Citrix version is 11.8.2. I used a bootable USB Yosemite installer to do the upgrade. My wife was able to log onto her Citrix Receiver without issue. I wonder whether it is a network issue rather than a application issue. I have seen some reports of wifi connection problems with Yosemite upgraders. Maybe someone in IT can help. Are you having any trouble with using Safari accessing other sites? -
Anyone using an HP LaserJet Pro CP1525nw printer with SL?
I'm thinking of getting this printer. Can anyone using this with Snow Leopard please let me know how well it works? Any issues? Nice printer? I will be replacing a Samsung CLP-315 which prints very nicely, but doesn't work well after updating from Tiger to SL.
ThanksIt works just fine. I picked up a 1525 yesterday, configured it using Lion, and I just now configured my wife's SL laptop to work with it. No problems. Just don't install the HP disk and let OS-X grab drivers for it and you should be fine.
It's a little tricky configuring with Lion for wireless printing, but it's doable. See my post at https://discussions.apple.com/thread/3449512 for a checklist. -
right forum? first time here. none of the options seem perfect. so i guess this applies to 'setup.' i tried to describe what's happening verbosely from the start of a file transfer to completion of writing file to 2nd hard drive.
win 7 64bit home - i2600k 3.4ghz - 8gb of ram - 2hdd 1 ssd
I have this problem when transferring files between 2 internal hard drives. one is unhealthy (slow write speeds but not looking for advice to replace it because it serves its unimportant purpose). so, the unhealthy drive drops into PIO mode - that's acceptable.
however, a little over 1gb of any file transfer is cached in RAM during the file transfer. after the file transfer window closes, indicating the transfer is "complete" (HA!), it still has 1gb to write from RAM which takes about 30minutes. This would
not be a problem if it did not also earmark an additional 5gb of ram (never in use), leaving 1gb or less 'free' for programs. this needlessly causes my pc to be sluggish - moreso than a typical file transfer file between 2 healthy drives. i have windows write
caching turned off on all drives. so this is a different setting i can't figure out nor find after 2 hours of google searches.
info from taskmanager and resource monitor.
idle estimates: total 8175, cached 532, available 7218, free 6771 and the graph in taskman shows about 1gb memory in use.
at the start of a file transfer: 8175, 2661, 6070, 4511free and ~2gb of ram used in graph. No problems, yet.
however, as the transfer goes on, the free ram value drops to less than 1gb (1gb normal +1gb temporary transfer cache +5gb of unused earmarked space = ~7gb), cached value increases, but the amount of used ram remains relatively unchanged (2gb
during transfer and slowly drops to idle values as remaining bits are written to the 2nd hard drive). the free value is even slower to return to idle norms after the transfer completes writing data to 2nd hard drive from RAM. so, it's earmarking an addition
5gb of ram that are completely unused during this process. *****This is my problem*****
Is there any way to turn this function off or limit its maximum size. in addition to sluggishness, it poses risk to data integrity from system errors/power loss, and it's difficult to discern the actual time of transfer completion, which makes it difficult
to know when it's safe to shutdown my pc (any data left in ram is lost, and the file transfer is ruined - as of now i have to use resmon and look through what's writing to disk2 -> sometimes easy to forget about it when the transfer window closed 20-30minutes
ago and the file is still in the process of writing to the 2nd disk).
Any solution would be nice, and a little extra info like whether it can be applied to only 1 hard drive would be excellent.Thanks for the reply.
(Although i have an undergrad degeee in computers, it's been 15years and my vocab is terrible. so, i will try my best. keep an open mind. it's not my occupation, so i rarely have to communicate ideas regarding PCs)
It operates the same way regardless of the write-cache option being enabled. It's not using the 5gb for read/write buffer - it's merely bloating standby memory during the transfer process at a rate similar to the write speed of destination (for my situation).
at this point i don't expect a solution. i've tried to look through lists of known memory leaks but i dont have the vocabulary to be 100% certain this problem is not documented. as of now it can't affect many people - NAS's with low bandwidth networks, usb
attached storage etc. do bugs get forwarded from these forums? below i can outline the consistent and repeatable nature not only on my pc but on others' pcs as well (2012 forum post i found).
I've been testing and paying a little more attention and i can describe it better:
Just the Facts
Resmon Memory Info: "In Use" stays consistent ~1gb (idle amount and roughly the same when nothing else is running during file transfer)
"Modified" contains file transfer
data (meta data?) which remains consistent at little over 1gb (minor fluctuations due to working as a buffer). After the file transfer window closes "Modified" slowly diminishes as it finishes lazy writing (i believe that's the term). I forget idle
pc amount, but after transfer this is ony 58mb)
"Standby" as the transfer starts it immediately rises to ~2gb. I'm sure this initial jump is normal. However, it will bloat well over 5gb over time with a large enough transfer increasing at a consistent rate during the entire transfer
process. the crux of the matter.
"Free" will drop as far as 35-50megabytes over time.
as the transfer starts, the "Standby" increases by an immediate chunk then at a slow rate throughout entire transfer process(~1mb/s). once writing metadata to RAM no longer occurs, the "Modified" ram slowly (@500kb/s matching resmon disk
activity for that file write) diminishes as it finishes lazy writing, After file is 100% written to destination drive, "Standby" remains a bloated figure long after.
a 1.4gb transfer filled 3677MB of "Standby" by the time writing finished and modified ram cleared. after 20minutes, it's still bloated at 3696MB. after 30-40mins it's down to 2300mb - this is about what it jumps immediately to when transfer starts
- it now remains at this level until i reboot.
I notice the "standby" is available to programs. but they do not operate well. e.g. a 480p trailer on IMDB.com will stop-and-go every 2-3seconds (stream buffers fine/fast) - this would be during the worst case scenario of 35-50mb "Free"
ram. my pc isn't and never was the latest and greatest, but choppy video never happens even with 1 or 2 resource hogs running (video processing/encoding, games, etc).
Conjecture Below
i think it's a problem when one device is significantly slower at writing than the source device - this is the factor that i share with others having this problem. when data is written to modified ram then sent to destination, standby memory is expanded
until it completely or nearly fills all available RAM - If the transfer size is large enough relative to how slow the write speed of destination device is. otherwise it fills it up as much as the file size/write speed issue allows. the term "memory leak"
is used below but may not technically be one, but it's an apt description in layman's terms.
i saw a similar post in these forums (link at end). My problem is repeatable and consistent with others' reports. I wasn't sure if i should revive it with a reply. some of these online message boards (maybe not this one) are extremely picky
and sensitive, lol.the world will end if an old thread revives - even if for a good reason.
i can answer some of the ancillary issues. one person (Friday, September 21, 2012 8:33 PM) mentions not being able to shutdown, i asume he means stuck on the shutdown screen - this is because lazy writing has not completed - his nas write speed is significantly
slower than reading from source - the last bits of data left in ram still needs to be writen to the destination. shutdown will stall for as long as needed until the data finishes writing to destination to prevent data loss.
another person (Monday, September 24, 2012 6:31 PM) mentions the rate of the leak, but the rate is more likely a function of read speed from source relative to write speed of destination. which explains why my standby expands closer to a 1:1 ratio compared
to his 1:100 (he said 10mb per 1000mb)
we all have the same exact results/behaviour, but slightly different rates of bloating/leaking. as the file is written from from the ram to the destination, standby increases during this time - not a problem if read and write speeds are roughly equal (unless
your transfering a terabytes then i bet the problem could rear its head). when writing lags, it gives the opportunity for standby ram to bloat with no maximum except the amount of installed ram. slower the write speed, the worse the problem.
The reply on Wednesday, September 26, 2012 3:04 AM has before and after pictures of exactly what i described in
"Just the Facts". Specifically the resmon image showing the Memory Tab.
The kb2647452 hotfix seems to do some weird things relative to this problem. in the posts that mention they've applied it: after file completes it looks like the "standby" bloat is now "in use" bloat. as per info from Tuesday, October
09, 2012 10:36 PM - bobmtl in an earlier post applies the patch. compare images from earlier posts to his post on this date. seems like a worse problem. Also, his process list indicates it's very unlikely they add up to ~4gb as listed in the color coded bar.
wheres the extra gb's coming from? likely the same culprit of what filled up "standby" memory for me and others. it looks like this patch relative to this problem merely recategorizes the bloat - just changes the title it falls under.
Link:
https://social.technet.microsoft.com/Forums/windows/en-US/955b600f-976d-4c09-86dc-2ff19e726baf/memory-leak-in-windows-7-64bit-when-writing-to-a-network-shared-disk?forum=w7itpronetworking -
[SOLVED] Suspend to ram / disk not working in newer kernels
Hi all,
this puzzles me for a while:
My desktop system was able to suspend to ram / disk flawlessly in older kernels. It stopped working with 3.3. The suspend seems to work, the machine goes to standby. But when I try to resume, the machines is on but the screen stays black. Neither the console is working nor can I ssh into it. Only hard reset gets me out here
I did investigate and found many tips and hints which all led to nowhere. I even changed my filesystem back from btrfs to ext4 and my VGA module from proprietary nvidia to nouveau.
When this all failed I got to the idea to burn several install disks. One of the official 2011.08.19 (kernel 3.0.3) and one of the snapshots 2012.06.05_04-00-01 (kernel 3.3.7) and 2012.07.17_04-00-01 (kernel 3.4.4). I guess these can not be compromised by some hosed installation. I started one by one and issued the follwing command:
echo mem > /sys/power/state
which suspends the machine successfully in all three cases. With 2011.08.19 the resume is working but the other two fail. Some more info about the hardware:
1. lspci output
harvey@obelix ~ $ lspci
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11)
00:05.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 3 (rev 11)
00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11)
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and Protocol Registers (rev 11)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1a.1 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1a.2 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1a.7 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06)
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1d.1 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1d.2 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1d.3 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1d.7 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation 5 Series Chipset LPC Interface Controller (rev 06)
00:1f.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA IDE Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
00:1f.5 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 2 port SATA IDE Controller (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation G84 [GeForce 8600 GT] (rev a1)
02:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03)
03:00.0 SATA controller: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 02)
03:00.1 IDE interface: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 02)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-Core Registers (rev 04)
3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 04)
3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 04)
3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 04)
3f:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller (rev 04)
3f:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Target Address Decoder (rev 04)
3f:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Test Registers (rev 04)
3f:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Control Registers (rev 04)
3f:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Address Registers (rev 04)
3f:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Rank Registers (rev 04)
3f:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Thermal Control Registers (rev 04)
3f:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Control Registers (rev 04)
3f:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Address Registers (rev 04)
3f:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Rank Registers (rev 04)
3f:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Thermal Control Registers (rev 04)
2. lsmod output of 2012.07.17_04-00-01:
harvey@obelix ~ $ lsmod
Module Size Used by
fuse 68768 0
tun 15297 0
rfcomm 33627 8
bnep 8793 2
nfsd 246714 2
exportfs 3665 1 nfsd
btusb 11764 0
joydev 9991 0
bluetooth 190551 22 bnep,btusb,rfcomm
rfkill 15604 2 bluetooth
snd_hda_codec_realtek 60409 1
snd_hda_intel 24053 3
snd_hda_codec 94305 2 snd_hda_codec_realtek,snd_hda_intel
microcode 12185 0
i7core_edac 17477 0
snd_hwdep 6300 1 snd_hda_codec
i2c_i801 8180 0
iTCO_wdt 12813 0
snd_pcm 74958 2 snd_hda_codec,snd_hda_intel
r8169 49386 0
coretemp 5654 0
edac_core 36656 3 i7core_edac
iTCO_vendor_support 1929 1 iTCO_wdt
serio_raw 4653 0
pcspkr 1899 0
snd_page_alloc 7185 2 snd_pcm,snd_hda_intel
snd_timer 18966 1 snd_pcm
mii 4123 1 r8169
snd 58997 12 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_pcm,snd_hda_codec,snd_hda_intel
soundcore 5410 1 snd
acpi_cpufreq 5933 0
mperf 1235 1 acpi_cpufreq
evdev 9754 4
processor 26567 1 acpi_cpufreq
vboxnetadp 18387 0
vboxnetflt 16743 0
vboxdrv 1791382 2 vboxnetadp,vboxnetflt
nfs 276056 1
nfs_acl 2359 2 nfs,nfsd
lockd 62987 2 nfs,nfsd
auth_rpcgss 32327 2 nfs,nfsd
sunrpc 184998 12 nfs,nfsd,auth_rpcgss,lockd,nfs_acl
fscache 41059 1 nfs
aes_x86_64 7508 64
cryptd 8741 0
aes_generic 26138 1 aes_x86_64
xts 3101 32
gf128mul 6050 1 xts
dm_crypt 16496 4
dm_mod 70918 9 dm_crypt
sr_mod 14823 0
cdrom 35648 1 sr_mod
hid_logitech 16560 0
ff_memless 4690 1 hid_logitech
usbhid 36430 1 hid_logitech
hid 85285 2 hid_logitech,usbhid
sd_mod 29239 7
pata_jmicron 2480 0
usb_storage 44760 0
pata_acpi 3408 0
ata_piix 23160 5
crc32c_intel 1987 0
ahci 20549 0
libahci 20023 1 ahci
ata_generic 3295 0
libata 167611 6 ahci,pata_acpi,libahci,ata_generic,ata_piix,pata_jmicron
scsi_mod 132974 4 usb_storage,libata,sd_mod,sr_mod
uhci_hcd 23372 0
xhci_hcd 81440 0
ehci_hcd 40994 0
usbcore 147533 8 btusb,uhci_hcd,usb_storage,ehci_hcd,usbhid,xhci_hcd
usb_common 954 1 usbcore
floppy 58615 0
nouveau 784289 3
button 4502 1 nouveau
video 11307 1 nouveau
mxm_wmi 1425 1 nouveau
wmi 8475 2 mxm_wmi,nouveau
i2c_algo_bit 5391 1 nouveau
drm_kms_helper 33051 1 nouveau
ttm 64288 1 nouveau
drm 208926 5 ttm,drm_kms_helper,nouveau
i2c_core 20369 5 drm,i2c_i801,drm_kms_helper,i2c_algo_bit,nouveau
ext4 424175 4
crc16 1359 2 ext4,bluetooth
jbd2 73919 1 ext4
mbcache 5977 1 ext4
3. /var/log/pm-suspend.log of a not working suspend
Initial commandline parameters:
Tue Jul 17 11:21:18 CEST 2012: Running hooks for suspend.
Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
Linux obelix 3.4.5-1-ARCH #1 SMP PREEMPT Mon Jul 16 21:35:54 CEST 2012 x86_64 GNU/Linux
Module Size Used by
rfcomm 33627 8
bnep 8793 2
nfsd 246714 2
exportfs 3665 1 nfsd
ext4 424175 3
jbd2 73919 1 ext4
mbcache 5977 1 ext4
btusb 11764 0
bluetooth 190551 22 bnep,btusb,rfcomm
crc16 1359 2 ext4,bluetooth
joydev 9991 0
rfkill 15604 2 bluetooth
snd_hda_codec_realtek 60409 1
microcode 12185 0
coretemp 5654 0
serio_raw 4653 0
snd_hda_intel 24053 5
snd_hda_codec 94305 2 snd_hda_codec_realtek,snd_hda_intel
pcspkr 1899 0
snd_hwdep 6300 1 snd_hda_codec
snd_pcm 74958 3 snd_hda_codec,snd_hda_intel
snd_page_alloc 7217 2 snd_pcm,snd_hda_intel
r8169 49386 0
i7core_edac 17477 0
snd_timer 18966 1 snd_pcm
edac_core 36656 3 i7core_edac
mii 4123 1 r8169
snd 58997 15 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_pcm,snd_hda_codec,snd_hda_intel
iTCO_wdt 12813 0
i2c_i801 8180 0
soundcore 5410 1 snd
iTCO_vendor_support 1929 1 iTCO_wdt
acpi_cpufreq 5933 0
mperf 1267 1 acpi_cpufreq
evdev 9754 4
processor 26567 1 acpi_cpufreq
vboxnetadp 18387 0
vboxnetflt 16743 0
vboxdrv 1791382 2 vboxnetadp,vboxnetflt
nfs 276056 1
nfs_acl 2359 2 nfs,nfsd
lockd 62987 2 nfs,nfsd
auth_rpcgss 32327 2 nfs,nfsd
sunrpc 184998 12 nfs,nfsd,auth_rpcgss,lockd,nfs_acl
fscache 41059 1 nfs
btrfs 710578 1
libcrc32c 1002 1 btrfs
zlib_deflate 20436 1 btrfs
aes_x86_64 7508 64
cryptd 8741 0
aes_generic 26138 1 aes_x86_64
xts 3101 32
gf128mul 6050 1 xts
hid_logitech 16560 0
ff_memless 4690 1 hid_logitech
dm_crypt 16496 4
dm_mod 70918 9 dm_crypt
sr_mod 14823 0
cdrom 35648 1 sr_mod
usbhid 36430 1 hid_logitech
usb_storage 44760 0
hid 85285 2 hid_logitech,usbhid
sd_mod 29239 7
pata_jmicron 2480 0
pata_acpi 3408 0
ata_piix 23160 5
ata_generic 3295 0
uhci_hcd 23404 0
crc32c_intel 1987 1
ahci 20549 0
libahci 20023 1 ahci
libata 167611 6 ahci,pata_acpi,libahci,ata_generic,ata_piix,pata_jmicron
xhci_hcd 81472 0
ehci_hcd 41026 0
scsi_mod 132974 4 usb_storage,libata,sd_mod,sr_mod
usbcore 147565 8 btusb,uhci_hcd,usb_storage,ehci_hcd,usbhid,xhci_hcd
usb_common 954 1 usbcore
floppy 58615 0
nouveau 784321 3
button 4502 1 nouveau
video 11307 1 nouveau
mxm_wmi 1425 1 nouveau
wmi 8475 2 mxm_wmi,nouveau
i2c_algo_bit 5391 1 nouveau
drm_kms_helper 33051 1 nouveau
ttm 64320 1 nouveau
drm 208958 5 ttm,drm_kms_helper,nouveau
i2c_core 20369 5 drm,i2c_i801,drm_kms_helper,i2c_algo_bit,nouveau
total used free shared buffers cached
Mem: 8173500 884060 7289440 0 3764 405872
-/+ buffers/cache: 474424 7699076
Swap: 8386556 0 8386556
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave suspend suspend:
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub suspend suspend:
/usr/lib/pm-utils/sleep.d/01grub suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
Running hook /etc/pm/sleep.d/90alsa suspend suspend:
/etc/pm/sleep.d/90alsa suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led suspend suspend:
/usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
Kernel modesetting video driver detected, not using quirks.
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:
kernel.acpi_video_flags = 0
/usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
Tue Jul 17 11:21:18 CEST 2012: performing suspend
This seems to be a kernel bug. Any input?
Harvey
Last edited by Harey (2012-08-06 13:51:49)Another life-sign. The issue is still unsolved but I've come a little further. It seems to be a combination of more failures. The first one is USB hardware. I have a usb keyboard-mouse combo from Logitech (comfort cordless desktop). The USB bus does not wake up correctly when resuming from suspend. So my keyboard is unsuable. I put in a file /etc/pm/sleep.d/20_custom-ehci_hcd with the following content:
BUSES="0000:00:1a.7 0000:00:1d.7"
case "${1}" in
hibernate|suspend)
# Switch USB buses off
for bus in $BUSES; do
echo -n $bus | tee /sys/bus/pci/drivers/ehci_hcd/unbind
done
resume|thaw)
# Switch USB buses back on
for bus in $BUSES; do
echo -n $bus | tee /sys/bus/pci/drivers/ehci_hcd/bind
done
esac
The bus IDs were taken from /sys/bus/pci/drivers/ehci_hcd
When I start pm-suspend from a console (no X started) this seems to reanimate my keyboard while the screen stays black (with backlight on). I can type and reboot. Also I can ssh into the machine from my laptop.
Concerning the blank screen there seems to be a bug in both the proprietary nvidia modules as well as the nouveau driver. The nvidia folks have issued a new beta driver which seems to at least minimize the failures. This all concerns the nv50-family of nvidias cards. I have a GF8600GT which is one of these
I'll wait for this driver and then restart my testing. Until then - no suspend/hibernate
EDIT: Today's nvidia 304.32 is solving my issues - I can sleep again
Harvey
Last edited by Harey (2012-08-06 13:52:51) -
Suspend to ram/disk stopped working overnight
My suspend to ram/disk used to work fine, but overnight, it stopped. It is not an update issue since, I was able to suspend after the last update. I decided to update today hoping that it is going to solve the problem, but the problem persist.
Here is what happens:
$ sudo pm-suspend
or
$ sudo pm-hibernate
The computer suspends faster than usual, as if it does not take the time to complete the suspend procedure. When I turn the computer on, it starts to boot instead of resuming from suspend. In the case of hibernate, this is clearly obvious. Normally it is suppose to take 10-30 s. to save the memory data to the swap, but this time the computer shuts fast (1-2s.), and I doubt that all the data is saved to swap.
Here are the logs for each case (/var/log/pm-suspend.log):
suspend to ram:
Initial commandline parameters:
Sat Aug 25 23:16:03 EDT 2012: Running hooks for suspend.
Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
Linux gateway 3.4.9-1-ARCH #1 SMP PREEMPT Wed Aug 15 18:59:31 CEST 2012 x86_64 GNU/Linux
Module Size Used by
xt_recent 7901 3
xt_tcpudp 2471 51
ip6table_mangle 1684 0
ipt_MASQUERADE 1738 1
nf_nat_ftp 1668 0
iptable_nat 4024 1
nf_nat 15100 3 nf_nat_ftp,ipt_MASQUERADE,iptable_nat
nf_conntrack_ipv4 6871 20 nf_nat,iptable_nat
nf_defrag_ipv4 1339 1 nf_conntrack_ipv4
xt_TCPMSS 3439 5
xt_LOG 11943 48
ipt_REJECT 2281 0
iptable_mangle 1584 0
xt_multiport 1758 0
xt_state 1295 17
xt_limit 2041 51
xt_conntrack 3329 0
nf_conntrack_ftp 6261 1 nf_nat_ftp
nf_conntrack 61584 8 nf_nat_ftp,ipt_MASQUERADE,nf_nat,xt_state,xt_conntrack,nf_conntrack_ftp,iptable_nat,nf_conntrack_ipv4
ip6table_filter 1396 1
ip6_tables 18198 2 ip6table_filter,ip6table_mangle
iptable_filter 1456 1
ip_tables 16946 3 iptable_filter,iptable_mangle,iptable_nat
x_tables 16954 17 ip6table_filter,ip6table_mangle,xt_recent,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_limit,xt_state,xt_conntrack,xt_LOG,xt_multiport,iptable_filter,xt_TCPMSS,ipt_REJECT,iptable_mangle,ip6_tables,iptable_nat
adt7475 20329 0
hwmon_vid 3196 1 adt7475
arc4 1410 2
sg 25344 0
st 35573 0
uas 8823 0
rtl8187 52559 0
mxm_wmi 1425 0
wmi 8475 1 mxm_wmi
shpchp 26305 0
pci_hotplug 23564 1 shpchp
eeprom_93cx6 2175 1 rtl8187
serio_raw 4653 0
i2c_algo_bit 5391 0
ttm 64320 0
drm_kms_helper 33051 0
drm 208958 2 ttm,drm_kms_helper
tpm_tis 9074 0
tpm 13765 1 tpm_tis
tpm_bios 5121 1 tpm
video 11307 0
b43 353506 0
snd_hda_codec_realtek 60726 1
iTCO_wdt 12813 0
iTCO_vendor_support 1929 1 iTCO_wdt
snd_hda_intel 24053 0
snd_hda_codec 94305 2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 6300 1 snd_hda_codec
snd_pcm 74958 2 snd_hda_codec,snd_hda_intel
snd_page_alloc 7217 2 snd_pcm,snd_hda_intel
snd_timer 18966 1 snd_pcm
snd 58997 6 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_pcm,snd_hda_codec,snd_hda_intel
soundcore 5410 1 snd
nvidia 11182217 0
sky2 49219 0
microcode 12345 0
i2c_i801 8180 0
ssb 48803 1 b43
pcspkr 1899 0
evdev 9754 11
firewire_ohci 31709 0
intel_agp 10936 0
firewire_core 51552 1 firewire_ohci
intel_gtt 14047 1 intel_agp
crc_itu_t 1363 1 firewire_core
thermal 7959 0
fan 2426 0
button 4502 0
pcmcia 35785 2 b43,ssb
bcma 22757 1 b43
mmc_core 82070 2 b43,ssb
coretemp 5654 0
i2c_core 20369 6 drm,i2c_i801,drm_kms_helper,i2c_algo_bit,adt7475,nvidia
mac80211 395712 2 b43,rtl8187
cfg80211 170255 3 b43,mac80211,rtl8187
rfkill 15604 1 cfg80211
pcmcia_core 12253 1 pcmcia
vboxnetadp 18387 0
vboxnetflt 16871 0
vboxdrv 1792216 2 vboxnetadp,vboxnetflt
acpi_cpufreq 5933 0
mperf 1299 1 acpi_cpufreq
processor 26567 1 acpi_cpufreq
nfs 276152 0
nfs_acl 2359 1 nfs
lockd 62987 1 nfs
auth_rpcgss 32327 1 nfs
sunrpc 185190 4 nfs,auth_rpcgss,lockd,nfs_acl
fscache 41059 1 nfs
ext4 424871 6
crc16 1359 1 ext4
jbd2 73919 1 ext4
mbcache 5977 1 ext4
aes_x86_64 7508 40
cryptd 8741 0
aes_generic 26138 1 aes_x86_64
xts 3101 20
gf128mul 6050 1 xts
dm_crypt 16496 5
dm_mod 70918 11 dm_crypt
sr_mod 14823 0
cdrom 35648 1 sr_mod
sd_mod 29239 8
usbhid 36462 0
hid 85541 1 usbhid
usb_storage 44760 0
pata_jmicron 2480 0
pata_acpi 3408 0
ata_piix 23160 7
ata_generic 3295 0
uhci_hcd 23436 0
libata 167611 4 pata_acpi,ata_generic,ata_piix,pata_jmicron
scsi_mod 132736 7 sg,st,uas,usb_storage,libata,sd_mod,sr_mod
ehci_hcd 41026 0
usbcore 147661 7 uas,uhci_hcd,rtl8187,usb_storage,ehci_hcd,usbhid
usb_common 954 1 usbcore
floppy 58615 0
vfat 10119 0
fat 49739 1 vfat
nls_cp437 5953 0
total used free shared buffers cached
Mem: 4052416 174372 3878044 0 20828 36868
-/+ buffers/cache: 116676 3935740
Swap: 5122680 0 5122680
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave suspend suspend:
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub suspend suspend:
/usr/lib/pm-utils/sleep.d/01grub suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01laptop-mode suspend suspend:
/usr/lib/pm-utils/sleep.d/01laptop-mode suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/50netcfg suspend suspend:
/usr/lib/pm-utils/sleep.d/50netcfg suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
Unloading kernel module rfkill...Done.
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
Running hook /etc/pm/sleep.d/90alsa suspend suspend:
/etc/pm/sleep.d/90alsa suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led suspend suspend:
/usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
nVidia binary video drive detected, not using quirks.
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:
kernel.acpi_video_flags = 0
/usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
Sat Aug 25 23:16:04 EDT 2012: performing suspend
hibernate:
Initial commandline parameters:
Sat Aug 25 22:13:46 EDT 2012: Running hooks for hibernate.
Running hook /usr/lib/pm-utils/sleep.d/00logging hibernate hibernate:
Linux gateway 3.4.9-1-ARCH #1 SMP PREEMPT Wed Aug 15 18:59:31 CEST 2012 x86_64 GNU/Linux
Module Size Used by
xt_recent 7901 3
xt_tcpudp 2471 51
ip6table_mangle 1684 0
ipt_MASQUERADE 1738 1
nf_nat_ftp 1668 0
iptable_nat 4024 1
nf_nat 15100 3 nf_nat_ftp,ipt_MASQUERADE,iptable_nat
nf_conntrack_ipv4 6871 20 nf_nat,iptable_nat
nf_defrag_ipv4 1339 1 nf_conntrack_ipv4
xt_TCPMSS 3439 5
xt_LOG 11943 48
ipt_REJECT 2281 0
iptable_mangle 1584 0
xt_multiport 1758 0
xt_state 1295 17
xt_limit 2041 51
xt_conntrack 3329 0
nf_conntrack_ftp 6261 1 nf_nat_ftp
nf_conntrack 61584 8 nf_nat_ftp,ipt_MASQUERADE,nf_nat,xt_state,xt_conntrack,nf_conntrack_ftp,iptable_nat,nf_conntrack_ipv4
ip6table_filter 1396 1
ip6_tables 18198 2 ip6table_filter,ip6table_mangle
iptable_filter 1456 1
ip_tables 16946 3 iptable_filter,iptable_mangle,iptable_nat
x_tables 16954 17 ip6table_filter,ip6table_mangle,xt_recent,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_limit,xt_state,xt_conntrack,xt_LOG,xt_multiport,iptable_filter,xt_TCPMSS,ipt_REJECT,iptable_mangle,ip6_tables,iptable_nat
adt7475 20329 0
hwmon_vid 3196 1 adt7475
sg 25344 0
st 35573 0
uas 8823 0
rtl8187 52559 0
mxm_wmi 1425 0
wmi 8475 1 mxm_wmi
shpchp 26305 0
pci_hotplug 23564 1 shpchp
eeprom_93cx6 2175 1 rtl8187
serio_raw 4653 0
i2c_algo_bit 5391 0
ttm 64320 0
drm_kms_helper 33051 0
drm 208958 2 ttm,drm_kms_helper
tpm_tis 9074 0
tpm 13765 1 tpm_tis
tpm_bios 5121 1 tpm
video 11307 0
nvidia 11182217 0
arc4 1410 2
snd_hda_codec_realtek 60726 1
snd_hda_intel 24053 0
snd_hda_codec 94305 2 snd_hda_codec_realtek,snd_hda_intel
b43 353506 0
ssb 48803 1 b43
snd_hwdep 6300 1 snd_hda_codec
snd_pcm 74958 2 snd_hda_codec,snd_hda_intel
snd_page_alloc 7217 2 snd_pcm,snd_hda_intel
snd_timer 18966 1 snd_pcm
snd 58997 6 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_pcm,snd_hda_codec,snd_hda_intel
soundcore 5410 1 snd
sky2 49219 0
pcmcia 35785 2 b43,ssb
bcma 22757 1 b43
i2c_i801 8180 0
iTCO_wdt 12813 0
iTCO_vendor_support 1929 1 iTCO_wdt
thermal 7959 0
fan 2426 0
button 4502 0
firewire_ohci 31709 0
mmc_core 82070 2 b43,ssb
firewire_core 51552 1 firewire_ohci
intel_agp 10936 0
intel_gtt 14047 1 intel_agp
crc_itu_t 1363 1 firewire_core
i2c_core 20369 6 drm,i2c_i801,drm_kms_helper,i2c_algo_bit,adt7475,nvidia
pcspkr 1899 0
microcode 12345 0
evdev 9754 11
coretemp 5654 0
mac80211 395712 2 b43,rtl8187
cfg80211 170255 3 b43,mac80211,rtl8187
rfkill 15604 1 cfg80211
pcmcia_core 12253 1 pcmcia
vboxnetadp 18387 0
vboxnetflt 16871 0
vboxdrv 1792216 2 vboxnetadp,vboxnetflt
acpi_cpufreq 5933 0
mperf 1299 1 acpi_cpufreq
processor 26567 1 acpi_cpufreq
nfs 276152 0
nfs_acl 2359 1 nfs
lockd 62987 1 nfs
auth_rpcgss 32327 1 nfs
sunrpc 185190 4 nfs,auth_rpcgss,lockd,nfs_acl
fscache 41059 1 nfs
ext4 424871 6
crc16 1359 1 ext4
jbd2 73919 1 ext4
mbcache 5977 1 ext4
aes_x86_64 7508 40
cryptd 8741 0
aes_generic 26138 1 aes_x86_64
xts 3101 20
gf128mul 6050 1 xts
dm_crypt 16496 5
dm_mod 70918 11 dm_crypt
usbhid 36462 0
sr_mod 14823 0
hid 85541 1 usbhid
sd_mod 29239 8
cdrom 35648 1 sr_mod
pata_jmicron 2480 0
usb_storage 44760 0
pata_acpi 3408 0
uhci_hcd 23436 0
ata_piix 23160 7
ata_generic 3295 0
libata 167611 4 pata_acpi,ata_generic,ata_piix,pata_jmicron
scsi_mod 132736 7 sg,st,uas,usb_storage,libata,sd_mod,sr_mod
ehci_hcd 41026 0
usbcore 147661 7 uas,uhci_hcd,rtl8187,usb_storage,ehci_hcd,usbhid
usb_common 954 1 usbcore
floppy 58615 0
vfat 10119 0
fat 49739 1 vfat
nls_cp437 5953 0
total used free shared buffers cached
Mem: 2054092 156900 1897192 0 20680 36788
-/+ buffers/cache: 99432 1954660
Swap: 5122680 0 5122680
/usr/lib/pm-utils/sleep.d/00logging hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave hibernate hibernate:
/usr/lib/pm-utils/sleep.d/00powersave hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub hibernate hibernate:
/usr/lib/pm-utils/sleep.d/01grub hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/01laptop-mode hibernate hibernate:
/usr/lib/pm-utils/sleep.d/01laptop-mode hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth hibernate hibernate:
/usr/lib/pm-utils/sleep.d/49bluetooth hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/50netcfg hibernate hibernate:
/usr/lib/pm-utils/sleep.d/50netcfg hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules hibernate hibernate:
Unloading kernel module rfkill...Done.
/usr/lib/pm-utils/sleep.d/75modules hibernate hibernate: success.
Running hook /etc/pm/sleep.d/90alsa hibernate hibernate:
/etc/pm/sleep.d/90alsa hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock hibernate hibernate:
/usr/lib/pm-utils/sleep.d/90clock hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq hibernate hibernate:
/usr/lib/pm-utils/sleep.d/94cpufreq hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/95led hibernate hibernate:
/usr/lib/pm-utils/sleep.d/95led hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler hibernate hibernate:
nVidia binary video drive detected, not using quirks.
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/99video hibernate hibernate:
/usr/lib/pm-utils/sleep.d/99video hibernate hibernate: success.
Sat Aug 25 22:13:48 EDT 2012: performing hibernate
This seems to be too few information to pin point the exact cause of the problem.
What should I do to troubleshoot this problem ?My linux installation is actually on a harddrive using SATA on a desktop. I decided to remove this harddrive and put it into an external usb enclosure. I booted this linux installation on my laptop. When doing suspend, it works as it should, which let me think this is probably not a software issue.
If it is a hardware malfunction, which hardware malfunction can be responsible of an incomplete suspend procedure as described earlier?
Maybe you are looking for
-
How can I disable (not hide) the Boomarks Toolbar?
I have installed the "Multirow Bookmarks Toolbar Plus 1.2" extension. In the Firefox customize toolbars box I dragged the Firefox bookmarks toolbar to the right of my home button instead of where it normally is. I then Right-clicked on the toolbar an
-
FUNCTIONAL MODULE CONVERT_OTF GIVING JUNK DATA IN UNICODE SYSTEM
Hi Gurus, After Unicode conversion of our QAS server we are facing problem in PDF conversion through FM CONVERT_OTF . as it is giving all junk data . We checked the spool and in spool it is showing correct output. We checked the FM in debug mode
-
Flash player not working in IE, firefox, or chrome, on windows 7
I have used flash player in the past, up until yesterday, and today when I connected, and tried to use YouTube, firefox froze up, and after waiting for several minutes, I force closed firefox. I tried again with IE, and the same thing happened. I als
-
What is the best practice for logging runtime error or uncheked exceptions
hello my main problem is logging the nullPointerException to a file suppose I have this method public void myMethod() //..... some declaration here User user = obj.findUser("userx"); //this may return null System.out.println("user name is "+
-
We have a reuqirement of uploading employee photos thru CV01n into dms and display these photos in PA30 . How it can be achieved? Thanks, Ravindra