This discussion is archived
19208 Views 63 Replies Latest reply: Sep 1, 2009 6:38 PM by nkocharh
Currently Being ModeratedAug 3, 2009 6:48 PM (in response to theycallmefreddy)I have the exact same problem, except I only hear the HD parking sound when I move the entire body of my 15" MBP. I have the freezing problem though from time to time. When playing a song, the hang will cause the song to loop a small section of the song.MacBook Pro 15" (June 2009), Mac OS X (10.5.7), iPod touch 2G (3.0 Software)
Yet another "me too" I'm afraid. I have exactly the same symptoms on my new 2.66GHz 15' MacBook Pro. I was fine for the first two weeks, then the unexplained spinning beachball usually in Safari or Finder, but I have seen it in other programs. I thought it was because I had installed Greasekit on my system so I temporarily removed it, but the problem persisted. I went ahead and reinstalled it. Interestingly, I haven't experienced the problem in about a week, but my computer has been on a stand connected to my 30in Cinema Display that whole time. I don't hear the drive head parking while its on the desk, but when I use it on my lap I have noticed that my new MacBook Pro is much more sensitive to the sudden motion sensor than my previous early 2008 Penryn model. The slightest motion will cause the drive to click. It would be nice to get this fixed for good.MacBook Pro 15" 2.66GHz unibody mid-2009, Mac mini 2.16GHz C2D, Mac OS X (10.5.7), Intuos2 tablet, aluminum BT keyboard, MX Revolution BT mouse, 30in ACD
You know there is already a topic about this problem at this address:
Just 70 pages and 103,096 viewvs.MacBookPro5,2, Mac OS X (10.5.7)
Currently Being ModeratedAug 4, 2009 2:03 AM (in response to theycallmefreddy)I just got the 17" 2.8 ghz with the 500gb 5400 drive and I have had the same freezes and beach balls but no clicks or beeps. I thought for sure it was just me until I saw an article on the internet that linked to this discussion. I hope Apple figures this one out soon!17" Intel MBP 2.8 Ghz unibody and lovin' it!, Mac OS X (10.5.1)
I'm afraid I have to add my "me too"
Have the MacBookPro since it was released in Germany in March 2009.
Buildt to order faster harddrive. Have second user account since day one. MacBookPro sits on the desk and is not moved but I still have the problem.MacBookPro, 17", 4 GB Ram, 320 GB Seagate Momentur HD, Mac OS X (10.5.7)
FYI, I figured out the cause, at least for me: Google Quick Search Box. And the SSD, actually -- it's pretty bad. Just kill QSB and make sure it's not running at login. Go back to Quicksilver. Plus replace the SSD with HDD for an extra boost.
I was running on a 17" with SSD, and it would regularly beach ball and was basically unusable. Some people helping out noticed that a new profile worked much better, but when I built a new profile from scratch it started off running okay but quickly went sour somewhere along the way. I replaced the SSD drive with a regular hard drive and although I/O was slow, it was at least usable again.
Then later on, somebody else using a new system installed QSB after I suggested it, and everything went bad. We both took it off, and I/O is much much better.17" unibody MBP, Mac OS X (10.5.7)
Hey all...just adding my 2 cents in here as I have experienced similar problems with my 13.3" MPB. It started off being just a few seconds here and there, maybe once every 10 minutes or so. After reading a bit about it, I saw a thread saying that it was the Sudden Motion Sensor which was acting up and causing the hard drive to stop for a few seconds. So I typed "sudo pmset -a sms 0" into the command line (to disable the SMS) and restarted.
This seemed to fix the problem -- at first. I after about a month, it started happening again, getting worse and worse, the lag getting longer and longer. Then, this past weekend, the lag got unbearable (30 seconds +) and very frequent (every minute or so), until I restarted the Mac... and then... nothing. I couldn't get past the gray apple screen with the spinning gear. My HDD is dying a slow, terrible death. I tried an archive and install, and that got me back into my mac temporarily. I couldn't back up to Time Machine without freezing, and I couldn't use the mac for more than a few minutes before it seized up on me.
Fortunately, I was able to start the Mac in Target mode and copy some critical information to a co-worker's machine. Currently I'm waiting for my replacement drive to arrive to the Apple Store. Until then, I'm stuck working on office iScrapBooks.
Moral of the story: if you don't back up your data to Time Machine regularly, start now! Especially if you're experiencing this issue. Back up now, and back up often!MacBook Pro, Mac OS X (10.5.7)
I had the same problem with my new MBP 13 too (awful performance, long boot time, impossible to watch a movie and copy files simultaneously, etc). I've verified the problem with the AJA System Test (you can find it here, http://www.aja.com/products/software/).
The test creates a new file and then reads it (try it 512mb or bigger files).
The writing process was OK, about 60MB/s constant, but when it had to read it, it did ok for a few seconds and dropped to 2MB/S for a few seconds, then went back to 60MB/s and so on.
I took it to the Apple store, they told me that it was OK, I showed them this test and asked them to run it in any Mac, I don't care about the average speed, just to show them that it should be a constant speed.
And I was right, we ran the test on a few macs in the store and all of them had a constant speed, from 40MB/S to 70MB/S depending on the model.
Bottom line, they agreed that there was a problem, verified the laptop again and finally changed the hard drive. They don't know what the problem was, but with the new HD works just fine.
Hope this help you, guys.
good luck.MBP 13'' 2.53GHz, Mac OS X (10.5.7)
Currently Being ModeratedAug 4, 2009 7:11 PM (in response to theycallmefreddy)Why do any of these things have background processes? (save ituneshelper -- I know what that does.)
geektool? I forget what that is.. but if it's running in the background, I'm suspicious it's doing something low-level.
Transmission? It's an FTP client. It should not be running at login unless it's running a server.
I have the same issue of unmotivated hanging on my MacBook Pro 17", completely built by Apple without any hardware changes on my side. It is definitely related to the hard disk, because I can hear the hard disk parking when this happens. It happens frequently enough to be noticeable, but fortunately not often enough to render the computer completely unusable. But it is extremely annoying, because the freeze lasts for up to 30 seconds. In such a freeze, the cursor tends to continue to work for about 15 seconds, before even it freezes, and nothing happens on the screen anymore.
It seems to be not related to any software I am using, can happen anytime, anywhere.
The only interesting part I have found is that the Console log is overflowing with one message in case of such a hang:
/usr/libexec/hidd IOHIDEventQueueEnqueue: Error enqueuing memory. (0xe00002e8)
One hang can easily generate 600+ times this message.MacBook Pro, Mac OS X (10.5.7)
Currently Being ModeratedAug 6, 2009 11:11 AM (in response to theycallmefreddy)A lot of people are saying things like "it started when I did this" or "it seems to stop when I do this." Let's be clear here, if you read what others have posted, there isn't any pattern regarding software, attached hardware, use in a lap, use on a desk, etc. This issue is occurring in too many different variations to attribute the problem to anything that we're doing. Personally, I've had this problem regardless of what I'm doing, what apps are open or not open, etc.
As I see it, the only denominator in this is the laptops themselves, which seems to suggest that it's something with the internal hardware or firmware.