Macbook Pro sleep Problems with Time Machine and Time Capsule
I recently installed a time capsule as a Router and a Time Machine backup device for 2 macs in the house.
Unfortunately, I found that my 2011 macbook pro 15' updates the time machine backups even when the lid is closed and in sleep.
When I wake the macbook pro, it hangs and I have to reset the mac to restart.
This did not happen when I was using a firewire hard drive with the time machine.
My question is:
Is there a way to prevent the time machine to backup when the macbook pro is in sleep mode?
My mac is not equiped with power nap so it is not suppose to be doing this.
Thanks
Other info: OS Mountain Lion, regular hard drive, 8 Gig Memory
Edwin,
I assume that since the repair of the sparsebundle failed you still cannot open the sparsebundle in Finder and get the message:
The following backups could not be opened:
Imac of E.sparsebundle because there are no activatible filesystems
If the sparsebundle cannot be opened in Finder, then the chances that Time Machine can open them are nil in my opinion. Time Machine, in effect is just going to open the sparsebundle as Finder is attempting to dot, then it gives you a fnacy display, but the underlying issue with the sparesbundle is the same for both methods of access.
Do you, by chance hav a bootable backuo of your Snow Leopard system?
If so can you access the TM backups with it??
You didn't change the Time Capsules Network Password did you?? see this.
I looked to see if I could find anythng about the error codes you mentioned in your original post and so far can;t find anything about them.
Steve
Similar Messages
-
MacBook Pro sleep problems with Vista SP1
Has anyone faced sleep problems on a MacBook Pro after installing Vista SP1?
I run Boot Camp 2.0 with the latest update from Apple.
IDT finally issued a compatible Vista driver for my Sigmatel audio.
I was very happy for the first time running Vista on my Apple when I had the stupid idea to upgrade to SP1.
After days of troubleshooting with Windows support it is obvious that SP1 and my MacBook Pro are incompatible for some obscure reasons. The latest time I tried SP1 was through Windows Update, which means that Windows detected no compatibility issues, such as drivers.
I suspect Apple-in-sight driver without any evidence, just a hint.
Any ideas?
ThanksHibernation seems iffy. Have you tried disabling hibernation? and when you say sleep, what happens? won't wake or what?
Normally I don't recommend resetting NVRAM or SMU but for sleep you might want to.
And yes, trying to rule out why can be difficult. But I would not blame SP1. Maybe BC 2.1.
Do you have a book dealing with Vista? or looked for articles or forums that deal with Vista? There is one for Vista64 - assume you have 32-bit though. Google is often best way to find things in Apple discussions or knowledge base, too.
http://www.google.com/search?ie=utf8&oe=utf8&q=Vista+sleep -
My macbook pro not syncing with my ipod and ipad. What do I do?
My macbook pro not syncing with my ipod and ipad. What do I do?
iOS: Device not recognized in iTunes for Mac OS X
-
Time Machine and Time Capsule don't seem to work well together?
Reposted.
I get the feeling there are some serious problems with the combination of Time Machine and Time Capsule.
This is extremely disappointing, as the idea of a centralized backup device on the network (instead of disks attached to each and every computer we have running Leopard) seemed like such a good idea and a good way to supplement our tape-based backup that takes place with Retrospect.
In reality, it's a disaster on both Intel and PowerPC systems. All systems and the Time Capsule are fully up to date with software updates from Apple. I have two 1TB Time Capsule units. It goes something like this:
1. I have a few systems (mainly Intel) that work perfectly with the Time Capsule. There are no complaints and no issues at all. These systems just quietly run their backups as they should. They are the definite minority--maybe one or two have worked properly.
2. I have some systems that complain from time to time (mainly PowerPC) but will back up with a little encouragement. These too are the minority.
3. And finally, I have systems that are nothing but pain. These are both Intel and PowerPC systems. They are also the majority of the systems I have. The most common problem is sudden loss of the credentials needed to access the Time Capsule hardware--a user will be going along about their business when the Mac OS asks for the Time Capsule user name and password--after it's already been supplied and backups have been running. This should simply never ever happen.
Another charming behavior I've seen is corruption of the sparse disk image file that each computer creates on the Time Capsule. Time Machine will complain that it can't perform the backup, and examining the disk image file with Disk Utility shows it to be severely damaged. Turning off Time Machine, deleting the corrupted sparse image file, and starting over fixes it. For a while.
Finally, there are the machines (again, both Intel and PowerPC) that just can't seem to actually get through the first backup run. They either go so far and can't continue, or never actually manage to get started. I've checked the disks in these computers and found no problem with the hardware or file system. The installations are fresh and fully up to date.
Meanwhile, I have computers running Leopard with directly attached disks configured for use with Time Machine. One is a QuickSilver that isn't even officially supported by Leopard, with a Firewire attached disk. It doesn't skip a beat. The other is an Intel Mac mini being used with Mac OS X Server 10.5.4 and a USB external hard drive. These machines just do their thing, and I never have to babysit them.
These problems with the Time Capsule have been so severe that I've just given up on most of the computers and shut off Time Machine entirely. We have tape backups that run over the week, so it's not a huge loss. But that's not what really made me throw up my hands and say "enough"...no, that was the speed. Even with just one computer backing up to it, the Time Capsule seemed terribly slow. Watching the progress indicator was just painful.
I put in a word about all of this to my independent Apple dealer, and they say I'm definitely not the first to complain about some or all of these problems. In fact, they told me they were going to set up a test lab in their shop to see if they could duplicate these findings. I have no doubt that they can.
There are a total of seven computers backing up to one Time Capsule. They all store maybe ~40GB worth of data including the OS. There are about six computers on the other. Because of the way the network is laid out, the Time Capsule is connected to a Gigabit switch (and that is the only thing it's connected to). It cannot be used as the router, although I know Apple suggests this. The Airport section is disabled--I have no need or desire to use it. Some computers link up at 100 megabits, others at 1 gigabit. There are no network problems--we have no problems moving large amounts of data across the same network to our tape backup machine.
Is anyone else seeing these kinds of problems? Am I doing something wrong or expecting too much from Time Capsule?I may be on to something. The Time Capsules I have live in a telephone equipment room that is indoors but not directly air conditioned or heated. It doesn't ever get too hot to be comfortable in there--the highest I've ever seen the temperature was 80 degrees (F). Most of the time the temperature is between 60-78 degrees.
I happened to touch one of them the other day while it was in use, and I noticed that the casing was hot to the touch...not dangerously so I suppose, but much hotter than I would have expected.
So I turned a small fan on both Time Capsules and have left it running. And I've noticed that not only do backups seem to complete more quickly, the reliability is also better. I am going to try some of my most troublesome computers once again just to see what happens.
I know there is a fan pointed at the hard drive in the Time Capsule, but I can't see how it does much in the way of cooling things down. In my opinion, it's just surrounded by too many heat producing devices to do much good...after all, not only is there a 7200 RPM hard disk in there, but also a 500MHz Marvell processor and radio set. -
Problem with Airport extreme and Time machine
I recently purchased a 320gig external hard drive for Time machine. I connected it to my Airport extreme but it is not being recognized for some unknown reason. If I directly connect it to my iMac it works perfectly. I've updated with the latest firmware and it should work via USB with Airport extreme. Any suggestions why it is not working?
angelop wrote:
I have used the following for about two years.
-MBP, Airport Extreme, External HD (1TB) for my time machine.
You probably know, that's "iffy" and +*not supported by Apple.+* See the Using Time Machine with a USB drive connected to an Airport Extreme *User Tip,* also at the top of this forum.
To get around this issue, I have switched off the Time Machine, and am only turning on once a week or so, to grab any changes or additions I've made. I've been doing this for about 6 months now with no problems.
Now whenever I do this, (It should only be backing up an album or two from iTunes,) it tries to back up my whole system again. EVERY TIME. It did not do this before.
If you go too long between backups, Time Machine will do a new, full backup. And once it decides to do that, it will keep trying until it succeeds. There are some other possibilities as well. See #D2 in the Using Time Machine with a USB drive connected to an Airport Extreme *User Tip,* also at the top of the +Time Machine+ forum.
If none of those seem to explain it, see #A1 there; download the TM Buddy widget, copy and post the messages here.
Why are you only backing-up once a week? Time Machine was designed to back up changes hourly, as long as your Mac is awake and the TC is in range. It will protect you best that way, and unless there's a problem, those backups will usually be very quick.
But if you're only going to back up once a week or so, then Time Machine is not the best app for you. See Kappy's post on Basic Backup, complete with links to the web sites of each product. -
So I bought my MacBook Pro 13 inch with AppleCare protection about 2 weeks ago and from the moment it came out of the box I noticed that the battery was draining very quickly. Perhaps in the midst of my excitement of having a new computer I ignored it thinking it could somehow get better but obviously it has not. Average after being fully charged from being dead the batter lasts maybe an hour to an hour and a half. I'm assuming apple will take care of this seeing as it came to me like this but that's exactly my question, will they? Any information about what they cover or how to go about getting this fixed is very much appreciated!
You are covered under the 1-year warranty.
You have a 14 day grace period to exchange it for one that works.
Past that, get it looked at
Genius reservation http://www.apple.com/retail/geniusbar/
on-line https://getsupport.apple.com/GetproductgroupList.action
check warranty https://selfsolve.apple.com/agreementWarrantyDynamic.do -
Toshiba sattelite pro ( SPM30 ) problem with black screen and white cursor
I have a toshiba SPM30 from a friend and I couldn't succed to resolve the problem with black screen and white cursor.I can enter in bios using F2 and I can use F12 but is not booting, I have some CD and DVD with Win Xp but it seeams that is not booting.I've traied to change the order in boot order: first CD/DVD and after HDD but still is not working...I saw that a HDD I can see details about it but at CD/DVD I can't see...I think that the CD/DVD is not working( but I can see the light and hear the sounds when I put a bootable CD or DVD)...Please, if someoane can help me......( byt the way I've traied to remove the bios battery and still is not working...)
Try f8 and try the repair your computer options
This explains advanced start up options:
http://windows.microsoft.com/en-us/windows/advanced-startup-options-including-safe-mode#1TC=windows-...
This explains start up repair:
http://windows.microsoft.com/en-us/windows/startup-repair-faq#1TC=windows-7
A system disc can be used for these repair options also, in your case if the DVD drive is not working you can use an external dvd drive if you have one.
S70-ABT2N22 Windows 7 Pro & 8.1Pro, C55-A5180 Windows 8.1****Click on White “Kudos” STAR to say thanks!**** -
Time Machine and Time Capsule not working well.
Greetings,
I am having strange issues with Time Machine and the Time Capsule. I am using a MacBook Pro and have the 1TB Time Capsule. I am also using the Time Capsule as the wireless base station for my network.
The issue is, Time Machine has only once created a full back-up. Since then, it could not either connect to the disk or mount the image. I have tried several things like renaming my computer and renaming the Time Capsule. I have also tried copying via LAN and wireless. I even went as far as erasing the disk.
Now that the disk is erased, Time Machine cannot create an imgage on the drive. This is my latest issue.
Is this kind of trouble wide spread or very rare? Any way to fix it?
As a work-around, I am using Smart Backup instead of Time Machine to do my back-ups.Standard Lion and ML issue..
Just reboot the TC.. sometimes with ML you may need to reboot the whole network.
In Lion you can use 5.6utilty and disconnect all users.. but apple has not made 5.6 utility available for ML or not yet. Perhaps they don't know about the bug. or if you put your head deep enough in the sand you can pretend there is no such problem.. it does expose some other parts!!
Pondini has info on a work around to load 5.6 utility into ML.
Read C12 and C17
http://pondini.org/TM/Troubleshooting.html -
I recently upgraded to Snow Leopard and installed Time Capsule. I connected a Maxtor external drive to Time Capsule to enable me to access my photography library wirelessly. I have a 2nd external drive that direct connects to my Mac Book Pro. I have found the following problems:
1. Time machine shows backup files for the external drive that connects to my mac, however they are old files no longer on the drive. It does not backup the current drive but does indicate backup was successful. I would also like time machine to backup the external drive connected to time capsule.
2. I tried to delete the folder containing the old files and received a message saying I did not have permission.
3. I am experiencing problems entering Time Machine. It takes a long time to connect (including when I am connected via an ethernet cable) and after a few minutes I receive a message asking if I still want to enter time machine. Once I do have access, I typically only see mail and am not able to access folders.
Help is appreciated! Thank you.rgoodman wrote:
1. Time machine shows backup files for the external drive that connects to my mac, however they are old files no longer on the drive.
Where does it show the old files, on recent backups in the "Star Wars" display?
It does not backup the current drive but does indicate backup was successful.
Are you sure it's not backing-up the new drive? Try the procedure in item #E3 of the Time Machine - Troubleshooting *User Tip.* It's for a slightly-different situation, but should confirm which disks were backed-up on each backup.
If you're sure the new external is not being backed-up, and is not on the +Do not back up+ list, do a "full reset" of Time Machine per item #B3 of the Troubleshooting Tip.
I would also like time machine to backup the external drive connected to time capsule.
Sorry, it won't. TM will only back-up internal or directly-attached FireWire or USB drives.
You might want to review these:
Time Machine Tutorial
Time Machine 101
How to back up and restore your files
Time Machine Features
Apple - Support - Mac OSX v10.5 Leopard Time Machine
and perhaps browse the Frequently Asked Questions *User Tip.* -
Can I backup an External Hard Drive using Time Machine and Time Capsule?
I have a Powerbook G4 with Mac OS X 10.5.2 and use an external hard drive *all the time*. I'd like to use Time Machine and my new 500GB Time Capsule to back it up along with the internal hard drive. Can I do this? Thanks for your help.
I believe so; this thread indicates how. Hope this helps.
-
Problem with MyBook Live and Time Machine on MacBook Pro
Hi,
I bought recently a WD MybookLive 2 tb.
The HD is connected to the modem and make backup from Macbook Pro 15 'with Time Machine.
Previously everything worked correctly, the Mac recognizes the disc and carried outregular backups, everything started to not work after the updates that were released by Apple on November 11 with software update - firmware on the My Book Live theMyBookLive 02.10.09-124: Core F / W
I get this error:
Time Machine can not complete the backup. The disk backup is not available.
Apart from Time Machine, yes, I use the MyBook Live, I load the disk where you are within the Public folders Shared Music, Shared Pictures, Shared Videos, and Software,I can easily copy files and copy them from there into to my computer - the My Book and'set a DHCP address.
Thankstry this:
http://www.insanelymac.com/forum/index.php?showtopic=184462
or here
http://translate.google.com/translate?sl=it&tl=en&js=n&prev=_t&hl=it&ie=UTF-8&la yout=2&eotf=1&u=http%3A%2F%2Fwww.nervous.it%2F2009%2F09%2Fbackup-snowleopard-sha re-di-rete%2F&act=url -
MacBook Pro Retina Problems with Headphone jack, Speakers, USB Port, MagSafe 2 and the hard drive
I took my MacBook Pro Retina 2.6GHz i7 to the genius bar to have the headphone jack looked at. I was told they could easily fix it but had to order the part. That day I took it home and returned to the store once I was notified that the part arrived so I could drop it off for repair. 3 days after I dropped my computer off with the genius bar I missed a phone call and returned to my iphone with a new voicemail. It said something like this, "Hello Tim, I just wanted to let you know that we replaced the headphone jack but it turned out not to be the problem and the problem was actually with the logic board. Don't worry though, we went ahead and replaced that for you, however, after that was done, the speakers stopped working but the headphone jack is fixed. We have to order new speakers to put in your computer b/c we don't have those on hand either."
Long story short, they fixed the speakers but, "had to order another part to repair the USB port." So I am waiting for that to be repaired but the dang AC Power to the actual computer does not work now!!! It's not the magsafe 2 charger that I have or the outlets I tried it in b/c I tried multiple chargers and multiple outlets. I am very frustrated! I have been without my computer for almost 2 weeks and still have to take it in at least twice more to get the power working this weekend and then again next week to (hopefully) get the USB port working.
At what point should I ask for a new computer or a refund? I have been using Apple Computers my whole life, I have had 8 different mac laptop models and have not had a problem until this computer. I am very frustrated with the support I have received from Apple as a whole.Contact Apple Customer Relations and let them know that you're not happy. With the logic board replacement, everything else should have been evaluated and fixed at the same time. It sounds as if you just got a lemon. You could plead your case for a replacement unit, I would think, since your machine is being 'replaced' piecemeal...
Good luck,
Clinton -
Time Machine and Time Capsule - Failing with Network Problem
My problems with TM/TC have been ongoing for a couple of months now and I am going round in circles - need help.
This is the second post I have made, the first got lost in people suggesting the obvious - so I will try to be a little more specific if I can.
I will detail the current state first - i.e. where I am now - after I will list what I have done so far to get to this point.
Currently, my iMac (intel) is directly connected by Ethernet 1GB to the Time Capsule. The TC is then connected to a Netgear router which in turn is connected to Internet.
I have no network problems at all - internet connection is fine. the Netgear Router has the latest firmware version and is working fine. The porblems i have are nothing to do with this.
The time Capsule is in Bridge mode and getting a reserved dhcp IP address from the Netgear router.
The Time Capsule has been fully reset - i.e. power cable out, hold the reset button, plug in power cable (spark, spark), hold reset button, fast blink for 20 seconds or so, light goes out, release button.
I have re-applied the latest Time Capsule firmware.
I have renamed the disk on the Time Capsule.
I have renamed my iMac and deleted all the time capsule entries from Keychain.
I have re-installed Mac OSX and re-updated to the latest 10.5.6 release.
At the moment I have kicked off a backup with a lot of large files - like music folder, video folder etc excluded. I also have parallels and have excluded the disk image. I have 1 other 50GB disk image which is also excluded.
I am expecting the first initial backup will complete successfully.
I will then remove music and video from exclusions and allow them to backup. I am expecting this will complete no problem. (I do this because the upcoming problem will happen if I move away from the machine - and I dont want to sit there for 2 days).
So up to this point TM and TC have performed flawlessly. The issue that follows started happening before the 10.5.6 update after backing up with no issues for months. At this point I will be able to use TM to browse the backup and restore files. I will be able to mount the sparse bundle and browse files. Spotlight reports no issues and indexes quickly.
If I leave my machine after a successful backup and the hourly update kicks in it will fail with 'A Network problem' basically saying the backup has filed because of a network problem, but is not any more specific, logs show far too much to put the whole thing here, but the following is an excerpt
Dec 23 05:19:49 MickMac /System/Library/CoreServices/backupd[1499]: Backup destination mounted at path: /Volumes/Backup
Dec 23 05:19:50 MickMac hdiejectd[1519]: running
Dec 23 05:19:51 MickMac kernel[0]: jnl: disk1s2: replay_journal: from: 28864512 to: 30084096 (joffset 0x1d0f000)
Dec 23 05:21:49 MickMac kernel[0]: jnl: disk1s2: journal replay done.
Dec 23 05:21:49 MickMac /System/Library/CoreServices/backupd[1499]: Disk image /Volumes/Backup/MickMac_001ec215ce76.sparsebundle mounted at: /Volumes/Backup of MickMac
Dec 23 05:21:49 MickMac /System/Library/CoreServices/backupd[1499]: Backing up to: /Volumes/Backup of MickMac/Backups.backupdb
Dec 23 05:21:49 MickMac com.apple.launchd[1] (com.apple.netauth.sysagent[1500]): Stray process with PGID equal to this dead job: PID 1503 PPID 1 check_afp
Dec 23 05:21:55 MickMac fseventsd[38]: event logs in /Volumes/Backup of MickMac/.fseventsd out of sync with volume. destroying old logs. (3627 125 5482)
Dec 23 05:27:33 MickMac /usr/sbin/ocspd[1539]: starting
Dec 23 05:30:27 MickMac kernel[0]: ASP_TCP HoldPendingReqs: holding slot 5 reqID 5400 flags 0x9 afpCmd 34 so 0x7e78cc0
Dec 23 05:30:27 MickMac kernel[0]: ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x7e78cc0
Dec 23 05:30:27 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect started /Volumes/Backup prevTrigger 0 currTrigger 1
Dec 23 05:30:27 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Backup
Dec 23 05:30:27 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: soft mounted and hidden volume so do not notify KEA for /Volumes/Backup
Dec 23 05:30:27 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/Backup
Dec 23 05:30:27 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Backup
Dec 23 05:31:26 MickMac kernel[0]: ASP_TCP CancelOneRequest: cancelling slot -1 error 89 reqID 1 flags 0x9 afpCmd 0 so 0x7e78cc0
Dec 23 05:31:26 MickMac KernelEventAgent[34]: tid 00000000 received VQ_DEAD event (32)
Dec 23 05:31:26 MickMac KernelEventAgent[34]: tid 00000000 type 'afpfs', mounted on '/Volumes/Backup', from 'afp_0V1fqC1mgalO00mE1H0Pyetl-1.2d00000a', dead
Dec 23 05:31:26 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: Open Session failed 57 /Volumes/Backup
Dec 23 05:31:26 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: max reconnect time reached 60 > 30 /Volumes/Backup
Dec 23 05:31:26 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: posting to KEAType IO] [ErrNo 5] [IOType Read] [PBlkNum 1248] [LBlkNum 155] [FSLogMsgID 501572642] [FSLogMsgOrder First]
Dec 23 05:31:26 MickMac kernel[0]:
Dec 23 05:31:26 MickMac fseventsd[38]: failed to unlink old log file /Volumes/Backup of MickMac/.fseventsd/0000000000ccb02b (Input/output error)
Dec 23 05:31:26 MickMac kernel[0]: disk1s2: 0x14 (UNDEFINED)."
It goes on and on and is repeated every hour. For each one I get an error message on screen saying backup failed due to a network error. However I have tried a manual download over the same period set at an extremely slow rate so that it was downloading during this time and it showed no errors. I.e. the network connection from imac, through TC to netgear and out to internet - and monitored this while time machine showed these errors (i.e. at the same time) and this showed no connection problems at all and completed succesfully.
I know TM uses an internal address to do backups, but uses the same cable and network card to get the job done. I am simply removing the cable as a source of issue although I have also replaced this making no difference.
Applecare are involved and have so far been sent 2 sets of logs and so far have not been able to find the cause. New TC is on its way to try that, although they think it is something on the imac that is causing this.
Sleep mode is turned off although screen sleep is on. The tick is not in the box for putting hard drives to sleep whenever possible.
Now, after this has happened, and back at the machine. I restart both imac and TC. Try running a backup, spotlight starts to re-index - i.e. will mount the backup volume and start the index process, gets to about 90% then fails - again excerpts from log
"Dec 23 09:18:50 MickMac /System/Library/CoreServices/backupd[161]: Backing up to: /Volumes/Backup of MickMac/Backups.backupdb
Dec 23 09:18:50 MickMac mds[32]: (/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/266E0E5F-E002-4EB5-A049-9B50582510FE)(E rror) IndexCI in ContentIndexOpenBulk:Unclean shutdown of /Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/266E0E5F-E002-4EB5-A049-9B50582510FE/li ve.0.; needs recovery
Dec 23 09:18:57 MickMac com.apple.launchd[67] (com.apple.netauth.useragent[147]): Stray process with PGID equal to this dead job: PID 152 PPID 1 check_afp
Dec 23 09:19:48 MickMac mds[32]: (Error) Server: machmsgdispatch: (ipc/send) invalid destination port [msgh_id 14016]
Dec 23 09:29:35 MickMac /usr/sbin/ocspd[197]: starting
Dec 23 09:42:48 MickMac kernel[0]: ASP_TCP HoldPendingReqs: holding slot 11 reqID 3204 flags 0x9 afpCmd 60 so 0x8051b28
Dec 23 09:42:48 MickMac kernel[0]: ASP_TCP HoldPendingReqs: holding slot 12 reqID 3205 flags 0x9 afpCmd 34 so 0x8051b28
Dec 23 09:42:48 MickMac kernel[0]: ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x8051b28
Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect started /Volumes/Backup prevTrigger 0 currTrigger 1
Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Backup
Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: soft mounted and hidden volume so do not notify KEA for /Volumes/Backup
Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/Backup
Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Backup
Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Backup
Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Backup
Dec 23 09:42:49 MickMac kernel[0]: ASP_TCP CancelOneRequest: cancelling slot 11 error 35 reqID 3204 flags 0x19 afpCmd 60 so 0x8051b28
Dec 23 09:42:49 MickMac kernel[0]: ASP_TCP CancelOneRequest: cancelling slot 12 error 35 reqID 3205 flags 0x19 afpCmd 34 so 0x8051b28"
And later....
Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x39 (UNDEFINED).
Dec 23 09:45:49 MickMac KernelEventAgent[34]: tid 00000000 received VQ_DEAD event (32)
Dec 23 09:45:49 MickMac kernel[0]:
Dec 23 09:45:49: --- last message repeated 1 time ---
Dec 23 09:45:49 MickMac kernel[0]: hfs_clonefile: cluster_read failed - 5
Dec 23 09:45:49 MickMac KernelEventAgent[34]: tid 00000000 type 'afpfs', mounted on '/Volumes/Backup', from 'afp_0V1fqC1mgalO00mE1H0Pyetl-1.2d000005', dead
Dec 23 09:45:49 MickMac kernel[0]: HFS resolvelink: can't find iNode791959
Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x39 (UNDEFINED).
Dec 23 09:45:49 MickMac kernel[0]: ore-V1/Stores/6CC2B046-5E28-4179-96B7-9DFF9F7EE431/store.db] [FSLogMsgID 1580919258] [FSLogMsgOrder Last]
Dec 23 09:45:49 MickMac KernelEventAgent[34]: tid 00000000 found 1 filesystem(s) with problem(s)
Dec 23 09:45:49 MickMac kernel[0]: jnl: disk1s2: dojnlio: strategy err 0x5
Dec 23 09:45:49 MickMac kernel[0]: jnl: disk1s2: end_transaction: only wrote 0 of 49664 bytes to the journal!
Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x14 (UNDEFINED).
Dec 23 09:45:49 MickMac kernel[0]:
Dec 23 09:45:49: --- last message repeated 1 time ---
Dec 23 09:45:49 MickMac mds[32]: (/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/6CC2B046-5E28-4179-96B7-9DFF9F7EE431)(E rror) IndexSDB in dbcheckdatastore:store.db : dbgetdatastore: ERR: could not read 4096 bytes
Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x14 (UNDEFINED).
Dec 23 09:45:49 MickMac mds[32]: (/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/6CC2B046-5E28-4179-96B7-9DFF9F7EE431)(E rror) IndexCI in CIMetaInfoSync:write err: 5
Dec 23 09:45:49 MickMac kernel[0]:
Dec 23 09:45:49 MickMac mds[32]: (/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/6CC2B046-5E28-4179-96B7-9DFF9F7EE431)(E rror) IndexCI in CIMetaInfoCreate:Tried to create index when index already existed /Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/6CC2B046-5E28-4179-96B7-9DFF9F7EE431
Dec 23 09:45:49 MickMac kernel[0]:
Dec 23 09:45:49 MickMac mds[32]: (/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/266E0E5F-E002-4EB5-A049-9B50582510FE)(E rror) IndexSDB in adddirtychunk:/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/266E0E5F-E002-4EB5-A049-9B50582510FE/st ore.db : ERR: Can't write DST header (Input/output error)
Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x14 (UNDEFINED).
Dec 23 09:45:49 MickMac kernel[0]:
Dec 23 09:45:49: --- last message repeated 1 time ---
Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x14 (UNDEFINED).
Dec 23 09:45:49 MickMac kernel[0]:
Dec 23 09:45:49: --- last message repeated 1 time ---
Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x14 (UNDEFINED).
Dec 23 09:45:49 MickMac kernel[0]:
Dec 23 09:45:49: --- last message repeated 1 time ---
Dec 23 09:45:49 MickMac mds[32]: (/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/266E0E5F-E002-4EB5-A049-9B50582510FE)(E rror) IndexSDB in dbflushdatastore:/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/266E0E5F-E002-4EB5-A049-9B50582510FE/st ore.db : dbsyncdatastore: write-errors flushing cache/writing map.
Am I the only one having these problems? any help from anybody please...Got the same problem with a 3 months old TC.
The replacement TC, does it work now flawless? -
Persistent problems with Time Machine and Time Capsule
I've upgraded to the most recent firmware, the green light stays on, and from the finder's point-of-view, the drive is connected (and I can browse it, etc.). After an initial backup apparently succeeding, subsequent attempts by Time Machine fail. I've removed the file and started from scratch, but then the failures keep happening.
I've gotten both: "Unable to complete backup. An error occured while creating the backup directory." and "Backup disk image could not be mounted." I believe one of the times there was another failure message.
Is this a dud drive? A problem that is typical? I'm approaching the point of giving the drive back, which would really be too bad.
Message was edited by: jrucker1076Theoretically if the drive was a dud, it wouldn't be able to read/write files. Try dragging files onto it to see if they will stay on there and if you can access them from it. Could be a time MACHINE problem, or a problem elsewhere. If the problem persists, take it to the apple store/call apple care!
-
Retina MacBook Pro sleep problem since 10.9.2
Ever since updating to 10.9.2 earlier in the week my macbook refuses to wake from sleep each morning.
Having looked at the console logs it seems that perhaps the problem is related to it not actually managing to go to sleep properly.
I closed the lid on the computer at about 19:07 as can be seen in the first of these console dumps. I put the laptop in my bag and went home, where the laptop stayed closed in my bag all night. Apparently the computer awoke 70 minutes later. In the morning, back at the office, I left the lid open for a good 5 minutes before deciding to reboot at 9:37, so it seems that the computer was indeed turned off as there was no activity in these minutes.
06/03/2014 19:07:12.574 airportd[84]: _handleLinkEvent: WiFi is not powered. Resetting state variables.
06/03/2014 19:07:12.000 kernel[0]: Thunderbolt Self-Reset Count = 0xedefbe00
06/03/2014 19:07:12.000 kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0xf400 ****
06/03/2014 19:07:12.000 kernel[0]: AppleThunderboltNHIType2::waitForOk2Go2Sx - retries = 6
06/03/2014 19:07:12.000 kernel[0]: Wake reason: EC.SleepTimer EHC1 (SleepTimer)
06/03/2014 20:17:14.000 kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
06/03/2014 20:17:14.000 kernel[0]: Previous Sleep Cause: 5
06/03/2014 20:17:14.000 kernel[0]: The USB device HubDevice (Port 1 of Hub at 0x1d000000) may have caused a wake by issuing a remote wakeup (2)
06/03/2014 20:17:14.000 kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 0 us
06/03/2014 20:17:14.000 kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 1 milliseconds
06/03/2014 20:17:14.000 kernel[0]: The USB device HubDevice (Port 8 of Hub at 0x1d100000) may have caused a wake by issuing a remote wakeup (3)
06/03/2014 20:17:14.000 kernel[0]: The USB device BRCM20702 Hub (Port 1 of Hub at 0x1d180000) may have caused a wake by issuing a remote wakeup (3)
06/03/2014 20:17:14.000 kernel[0]: Thunderbolt Self-Reset Count = 0xedefbe00
06/03/2014 20:17:14.000 kernel[0]: IOThunderboltSwitch<0xffffff80278cbc00>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0
06/03/2014 20:18:29.000 kernel[0]: IOPPF: Sent cpu-plimit-notification last value 25 (rounded time weighted average 25)
06/03/2014 20:18:39.000 kernel[0]: process com.apple.WebKit[2556] caught causing excessive wakeups. Observed wakeups rate (per sec): 250; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 48044
06/03/2014 20:18:39.458 ReportCrash[4729]: Invoking spindump for pid=2556 wakeups_rate=250 duration=180 because of excessive wakeups
06/03/2014 20:18:45.145 netbiosd[4725]: findReachableAddress: Using port 139 family = 33
06/03/2014 20:18:45.000 kernel[0]: smb1_smb_negotiate: Support for the server SPEEDPORT.IP has been deprecated (PreXP), disconnecting
06/03/2014 20:19:16.000 kernel[0]: IOPPF: Sent gpu-external-plimit-notification last value 12 (rounded time weighted average 12)
06/03/2014 20:19:16.000 kernel[0]: IOPPF: Sent gpu-internal-plimit-notification last value 14 (rounded time weighted average 14)
06/03/2014 20:19:21.558 netbiosd[4725]: findReachableAddress: Using port 139 family = 33
06/03/2014 20:19:21.000 kernel[0]: smb1_smb_negotiate: Support for the server SPEEDPORT.IP has been deprecated (PreXP), disconnecting
06/03/2014 20:19:22.000 kernel[0]: IOPPF: Sent cpu-plimit-notification last value 26 (rounded time weighted average 26)
06/03/2014 20:19:39.000 kernel[0]: process Sequel Pro[162] caught causing excessive wakeups. Observed wakeups rate (per sec): 172; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 120353
06/03/2014 20:19:40.000 kernel[0]: IOPPF: Sent gpu-external-plimit-notification last value 12 (rounded time weighted average 12)
06/03/2014 20:19:40.000 kernel[0]: IOPPF: Sent gpu-internal-plimit-notification last value 14 (rounded time weighted average 14)
06/03/2014 20:19:54.000 kernel[0]: IOPPF: Sent gpu-external-plimit-notification last value 14 (rounded time weighted average 14)
06/03/2014 20:19:54.000 kernel[0]: IOPPF: Sent gpu-internal-plimit-notification last value 14 (rounded time weighted average 14)
06/03/2014 20:19:59.975 netbiosd[4725]: findReachableAddress: Using port 139 family = 33
06/03/2014 20:19:59.000 kernel[0]: smb1_smb_negotiate: Support for the server SPEEDPORT.IP has been deprecated (PreXP), disconnecting
06/03/2014 20:20:11.000 kernel[0]: process Google Chrome[157] caught causing excessive wakeups. Observed wakeups rate (per sec): 1738; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 901505
06/03/2014 20:20:11.792 ReportCrash[4740]: Invoking spindump for pid=157 wakeups_rate=1738 duration=26 because of excessive wakeups
06/03/2014 20:20:12.000 kernel[0]: IOPPF: Sent gpu-external-plimit-notification last value 15 (rounded time weighted average 15)
06/03/2014 20:20:12.000 kernel[0]: IOPPF: Sent gpu-internal-plimit-notification last value 14 (rounded time weighted average 14)
06/03/2014 20:20:12.000 kernel[0]: process Dropbox[418] caught causing excessive wakeups. Observed wakeups rate (per sec): 162; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 166301
06/03/2014 20:20:12.676 ReportCrash[4740]: Invoking spindump for pid=418 wakeups_rate=162 duration=278 because of excessive wakeups
06/03/2014 20:20:38.370 netbiosd[4725]: findReachableAddress: Using port 139 family = 33
06/03/2014 20:20:38.000 kernel[0]: smb1_smb_negotiate: Support for the server SPEEDPORT.IP has been deprecated (PreXP), disconnecting
06/03/2014 20:22:29.000 kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=4752[GoogleSoftwareUp] final status 0x0, allowing (remove VALID) page
07/03/2014 09:37:14.000 bootlog[0]: BOOT_TIME 1394181434 0
07/03/2014 09:37:16.000 syslogd[19]: Configuration Notice:
ASL Module "com.apple.appstore" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
07/03/2014 09:37:16.000 syslogd[19]: Configuration Notice:
ASL Module "com.apple.authd" sharing output destination "/var/log/system.log" with ASL Module "com.apple.asl".
Output parameters from ASL Module "com.apple.asl" override any specified in ASL Module "com.apple.authd".
Weird huh? Can anyone tell from these logs why it's going mad in my bag? Why would it try and wake and then crash and power-off?Similar problem 3 times since upgrading to 10.9.2. Coworker also having same issue.
Process: appProtd [459]
Path: /usr/local/McAfee/AppProtection/bin/appProtd
Identifier: appProtd
Version: ???
Code Type: X86 (Native)
Parent Process: launchd [1]
Responsible: fmpd [86]
User ID: 0
Date/Time: 2014-03-08 14:33:13.906 -0800
OS Version: Mac OS X 10.9.2 (13C64)
Report Version: 11
Anonymous UUID: 45DE248F-A51E-AE89-0EC5-C788B17FBE12
Crashed Thread: 6
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
Assertion failed: (!pthread_mutex_unlock(m)), function ~interruption_checker, file /usr/local/boost/include/boost/thread/pthread/thread_data.hpp, line 116.
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x93608102 setsockopt + 10
1 appProtd 0x000bc8a1 AppProtection::KextInterface::stopHooking() + 65
2 appProtd 0x000bc78f AppProtection::KextInterface::~KextInterface() + 111
3 appProtd 0x0009350b AppProtection::AppProtectionController::~AppProtectionController() + 779
4 appProtd 0x000931d3 AppProtection::AppProtectionController::~AppProtectionController() + 19
5 appProtd 0x00093ad9 AppProtection::AppProtectionController::releaseInstance() + 313
6 appProtd 0x000994a9 AppProtection::AppProtectionController::main(int, char**) + 1737
7 appProtd 0x0009a3fb main + 11
8 appProtd 0x00092c25 start + 53
Thread 1:
0 libsystem_kernel.dylib 0x93607046 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x940c3dcf _pthread_wqthread + 372
2 libsystem_pthread.dylib 0x940c7cce start_wqthread + 30
Thread 2:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x93607992 kevent64 + 10
1 libdispatch.dylib 0x932ee8ad _dispatch_mgr_invoke + 238
2 libdispatch.dylib 0x932ee546 _dispatch_mgr_thread + 52
Thread 3:
0 libsystem_kernel.dylib 0x93607046 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x940c3dcf _pthread_wqthread + 372
2 libsystem_pthread.dylib 0x940c7cce start_wqthread + 30
Thread 4:
0 libsystem_kernel.dylib 0x936067ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x940c4d1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x940c6c25 pthread_cond_timedwait$UNIX2003 + 71
3 appProtd 0x0009f42b bool boost::condition_variable_any::timed_wait<boost::unique_lock<boost::mutex> >(boost::unique_lock<boost::mutex>&, boost::posix_time::ptime const&) + 203
4 appProtd 0x000941fb AppProtection::AppProtectionController::popFromRequestQueue() + 1243
5 appProtd 0x00095534 AppProtection::AppProtectionController::processRequests() + 308
6 appProtd 0x0009dada boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, AppProtection::AppProtectionController>, boost::_bi::list1<boost::reference_wrapper<AppProtection::AppProtectionControll er> > > >::run() + 42
7 libboost_thread.dylib 0x004f454a thread_proxy + 170
8 libsystem_pthread.dylib 0x940c25fb _pthread_body + 144
9 libsystem_pthread.dylib 0x940c2485 _pthread_start + 130
10 libsystem_pthread.dylib 0x940c7cf2 thread_start + 34
Thread 5:
0 libsystem_kernel.dylib 0x936067ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x940c4d1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x940c6c25 pthread_cond_timedwait$UNIX2003 + 71
3 appProtd 0x0009f42b bool boost::condition_variable_any::timed_wait<boost::unique_lock<boost::mutex> >(boost::unique_lock<boost::mutex>&, boost::posix_time::ptime const&) + 203
4 appProtd 0x000941fb AppProtection::AppProtectionController::popFromRequestQueue() + 1243
5 appProtd 0x00095534 AppProtection::AppProtectionController::processRequests() + 308
6 appProtd 0x0009dada boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, AppProtection::AppProtectionController>, boost::_bi::list1<boost::reference_wrapper<AppProtection::AppProtectionControll er> > > >::run() + 42
7 libboost_thread.dylib 0x004f454a thread_proxy + 170
8 libsystem_pthread.dylib 0x940c25fb _pthread_body + 144
9 libsystem_pthread.dylib 0x940c2485 _pthread_start + 130
10 libsystem_pthread.dylib 0x940c7cf2 thread_start + 34
Thread 6 Crashed:
0 libsystem_kernel.dylib 0x93606952 __pthread_kill + 10
1 libsystem_pthread.dylib 0x940c3167 pthread_kill + 101
2 libsystem_c.dylib 0x9471329c abort + 155
3 libsystem_c.dylib 0x946de39a __assert_rtn + 347
4 appProtd 0x0009ce62 boost::detail::interruption_checker::~interruption_checker() + 242
5 appProtd 0x0009f438 bool boost::condition_variable_any::timed_wait<boost::unique_lock<boost::mutex> >(boost::unique_lock<boost::mutex>&, boost::posix_time::ptime const&) + 216
6 appProtd 0x000941fb AppProtection::AppProtectionController::popFromRequestQueue() + 1243
7 appProtd 0x00095534 AppProtection::AppProtectionController::processRequests() + 308
8 appProtd 0x0009dada boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, AppProtection::AppProtectionController>, boost::_bi::list1<boost::reference_wrapper<AppProtection::AppProtectionControll er> > > >::run() + 42
9 libboost_thread.dylib 0x004f454a thread_proxy + 170
10 libsystem_pthread.dylib 0x940c25fb _pthread_body + 144
11 libsystem_pthread.dylib 0x940c2485 _pthread_start + 130
12 libsystem_pthread.dylib 0x940c7cf2 thread_start + 34
Thread 7:
0 libsystem_kernel.dylib 0x936067ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x940c4d1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x940c6c25 pthread_cond_timedwait$UNIX2003 + 71
3 appProtd 0x0009f42b bool boost::condition_variable_any::timed_wait<boost::unique_lock<boost::mutex> >(boost::unique_lock<boost::mutex>&, boost::posix_time::ptime const&) + 203
4 appProtd 0x000941fb AppProtection::AppProtectionController::popFromRequestQueue() + 1243
5 appProtd 0x00095534 AppProtection::AppProtectionController::processRequests() + 308
6 appProtd 0x0009dada boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, AppProtection::AppProtectionController>, boost::_bi::list1<boost::reference_wrapper<AppProtection::AppProtectionControll er> > > >::run() + 42
7 libboost_thread.dylib 0x004f454a thread_proxy + 170
8 libsystem_pthread.dylib 0x940c25fb _pthread_body + 144
9 libsystem_pthread.dylib 0x940c2485 _pthread_start + 130
10 libsystem_pthread.dylib 0x940c7cf2 thread_start + 34
Thread 8:
0 libsystem_kernel.dylib 0x936067ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x940c4d1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x940c6c25 pthread_cond_timedwait$UNIX2003 + 71
3 appProtd 0x0009f42b bool boost::condition_variable_any::timed_wait<boost::unique_lock<boost::mutex> >(boost::unique_lock<boost::mutex>&, boost::posix_time::ptime const&) + 203
4 appProtd 0x000941fb AppProtection::AppProtectionController::popFromRequestQueue() + 1243
5 appProtd 0x00095534 AppProtection::AppProtectionController::processRequests() + 308
6 appProtd 0x0009dada boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, AppProtection::AppProtectionController>, boost::_bi::list1<boost::reference_wrapper<AppProtection::AppProtectionControll er> > > >::run() + 42
7 libboost_thread.dylib 0x004f454a thread_proxy + 170
8 libsystem_pthread.dylib 0x940c25fb _pthread_body + 144
9 libsystem_pthread.dylib 0x940c2485 _pthread_start + 130
10 libsystem_pthread.dylib 0x940c7cf2 thread_start + 34
Thread 9:
0 libsystem_kernel.dylib 0x936067ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x940c4d1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x940c6c25 pthread_cond_timedwait$UNIX2003 + 71
3 appProtd 0x0009f42b bool boost::condition_variable_any::timed_wait<boost::unique_lock<boost::mutex> >(boost::unique_lock<boost::mutex>&, boost::posix_time::ptime const&) + 203
4 appProtd 0x000941fb AppProtection::AppProtectionController::popFromRequestQueue() + 1243
5 appProtd 0x00095534 AppProtection::AppProtectionController::processRequests() + 308
6 appProtd 0x0009dada boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, AppProtection::AppProtectionController>, boost::_bi::list1<boost::reference_wrapper<AppProtection::AppProtectionControll er> > > >::run() + 42
7 libboost_thread.dylib 0x004f454a thread_proxy + 170
8 libsystem_pthread.dylib 0x940c25fb _pthread_body + 144
9 libsystem_pthread.dylib 0x940c2485 _pthread_start + 130
10 libsystem_pthread.dylib 0x940c7cf2 thread_start + 34
Thread 10:
0 libsystem_kernel.dylib 0x936067ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x940c4d1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x940c6c25 pthread_cond_timedwait$UNIX2003 + 71
3 appProtd 0x0009f42b bool boost::condition_variable_any::timed_wait<boost::unique_lock<boost::mutex> >(boost::unique_lock<boost::mutex>&, boost::posix_time::ptime const&) + 203
4 appProtd 0x00094797 AppProtection::AppProtectionController::popAllFromResponseQueue() + 967
5 appProtd 0x000bdd4a AppProtection::KextInterface::sendResponseToKext() + 74
6 appProtd 0x000be8ba boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, AppProtection::KextInterface>, boost::_bi::list1<boost::reference_wrapper<AppProtection::KextInterface> > > >::run() + 42
7 libboost_thread.dylib 0x004f454a thread_proxy + 170
8 libsystem_pthread.dylib 0x940c25fb _pthread_body + 144
9 libsystem_pthread.dylib 0x940c2485 _pthread_start + 130
10 libsystem_pthread.dylib 0x940c7cf2 thread_start + 34
Thread 11:
0 libsystem_kernel.dylib 0x93606ace __select + 10
1 appProtd 0x000bd188 AppProtection::KextInterface::getRequestsFromKext() + 1192
2 appProtd 0x000be8ba boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, AppProtection::KextInterface>, boost::_bi::list1<boost::reference_wrapper<AppProtection::KextInterface> > > >::run() + 42
3 libboost_thread.dylib 0x004f454a thread_proxy + 170
4 libsystem_pthread.dylib 0x940c25fb _pthread_body + 144
5 libsystem_pthread.dylib 0x940c2485 _pthread_start + 130
6 libsystem_pthread.dylib 0x940c7cf2 thread_start + 34
Thread 6 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0xa0843cf8 ecx: 0xb04208cc edx: 0x93606952
edi: 0xb0421000 esi: 0x00000006 ebp: 0xb04208e8 esp: 0xb04208cc
ss: 0x00000023 efl: 0x00000206 eip: 0x93606952 cs: 0x0000000b
ds: 0x00000023 es: 0x00000023 fs: 0x00000023 gs: 0x0000000f
cr2: 0x0049f000
Logical CPU: 0
Error Code: 0x00080148
Trap Number: 132
Binary Images:
0x92000 - 0x10fff7 +appProtd (???) <E600A460-30A5-3BCA-948D-FB3D8A071F12> /usr/local/McAfee/AppProtection/bin/appProtd
0x1a9000 - 0x2b7ffb +libenterpriseagent.dylib (0) <267CFD41-269F-30A2-AAD7-0C9E9200E4D3> /usr/local/McAfee/fmp/lib/libenterpriseagent.dylib
0x446000 - 0x450ff7 +libappProtPrefs.dylib (1) <2AA2DB03-E8D1-39BC-9BFA-C39D8AED7527> /usr/local/McAfee/AppProtection/lib/libappProtPrefs.dylib
0x465000 - 0x477ff3 +libboost_filesystem.dylib (0) <7B91B435-1244-3EE8-B0B8-89F273846411> /usr/local/McAfee/fmp/lib/libboost_filesystem.dylib
0x489000 - 0x48cfff +libboost_system.dylib (0) <2C2B17DD-C71C-3F79-B9D9-641413E3A44E> /usr/local/McAfee/fmp/lib/libboost_system.dylib
0x491000 - 0x497ff7 +libfmputils.dylib (0) <AEE94A85-5A65-3D35-A099-DC5FAE6096BE> /usr/local/McAfee/fmp/lib/libfmputils.dylib
0x4a0000 - 0x4a6ff3 +libPreferences.dylib (0) <B9C8A097-060F-383A-B590-0D0762D32A17> /usr/local/McAfee/fmp/lib/libPreferences.dylib
0x4b3000 - 0x4d2ff3 +libfmphelpers.dylib (0) <D437B994-E8EE-3F86-BF6A-E3F0FADD5907> /usr/local/McAfee/fmp/lib/libfmphelpers.dylib
0x4f3000 - 0x500ffb +libboost_thread.dylib (0) <45CFDE5F-22F7-300E-802F-7616409D0766> /usr/local/McAfee/fmp/lib/libboost_thread.dylib
0x517000 - 0x5cdff3 +libboost_regex.dylib (0) <66538A59-5573-32DE-AEF5-CEF9A56E2414> /usr/local/McAfee/fmp/lib/libboost_regex.dylib
0x643000 - 0x66dff7 +libboost_serialization.dylib (0) <6FF80133-A28B-39D5-BF6A-4637847BAA2D> /usr/local/McAfee/fmp/lib/libboost_serialization.dylib
0x6d5000 - 0x6f2ffb +libboost_wserialization.dylib (0) <2079F8BC-750A-3430-B18E-E940A2BE2976> /usr/local/McAfee/fmp/lib/libboost_wserialization.dylib
0x747000 - 0x803fef +libappProfileMgmt.dylib (1) <4647415B-59BD-355A-8A15-6A6F82109846> /usr/local/McAfee/AppProtection/lib/libappProfileMgmt.dylib
0x961000 - 0x965ffb +libboost_date_time.dylib (0) <BE2E474D-CC89-3E5C-A61A-934E916CCD38> /usr/local/McAfee/fmp/lib/libboost_date_time.dylib
0x970000 - 0xa75ff7 +libicuuc.48.dylib (48.1.1) <A4CCFD07-095C-3D8D-BC99-95E61F1F48EC> /usr/local/McAfee/fmp/lib/libicuuc.48.dylib
0xb1d000 - 0xc97ff7 +libicui18n.48.dylib (48.1.1) <03455BB8-8770-3CB0-89DF-FB320423F68B> /usr/local/McAfee/fmp/lib/libicui18n.48.dylib
0xdcc000 - 0x1f39fff +libicudata.48.1.1.dylib (48.1.1) <58656AAF-9EB3-329D-8153-3BF48F90786E> /usr/local/McAfee/fmp/lib/libicudata.48.1.1.dylib
0x8fe6d000 - 0x8fe9f417 dyld (239.4) <2E655535-479B-3E48-ADD3-6278819CA38A> /usr/lib/dyld
0x90008000 - 0x901ceffb libicucore.A.dylib (511.31) <9C25D145-E785-357B-9833-1980A1A738C9> /usr/lib/libicucore.A.dylib
0x92a8f000 - 0x92accff7 libauto.dylib (185.5) <CD008E66-4A0C-35F5-8D72-80D76A716A03> /usr/lib/libauto.dylib
0x92b40000 - 0x92b40fff libkeymgr.dylib (28) <1B097DEA-011E-3B1C-86D5-6C7FAD5C765A> /usr/lib/system/libkeymgr.dylib
0x92cc0000 - 0x92cc4ff7 libmacho.dylib (845) <D8E93E59-1F80-3413-B9CF-78B848F6E873> /usr/lib/system/libmacho.dylib
0x92d69000 - 0x92d7bfff libsystem_asl.dylib (217.1.4) <51EB17C9-9F5B-39F3-B6CD-8EF238B05B89> /usr/lib/system/libsystem_asl.dylib
0x932d7000 - 0x932dcff6 libcompiler_rt.dylib (35) <9924DF2E-D80B-3A21-920D-544A4597203F> /usr/lib/system/libcompiler_rt.dylib
0x932e8000 - 0x932eafff libquarantine.dylib (71) <EE3B510E-1AEC-3171-8A1A-D6A5A42CF35C> /usr/lib/system/libquarantine.dylib
0x932eb000 - 0x93303ffd libdispatch.dylib (339.90.1) <871AC354-D1B6-3475-889E-AF594448CF43> /usr/lib/system/libdispatch.dylib
0x93371000 - 0x93379fff liblaunch.dylib (842.90.1) <B259692D-D60B-3BCE-9E03-32F457CB5046> /usr/lib/system/liblaunch.dylib
0x935ef000 - 0x9360cff4 libsystem_kernel.dylib (2422.90.20) <C823B3BD-F818-3D7A-9FB7-9BDE00E2BEA1> /usr/lib/system/libsystem_kernel.dylib
0x938cc000 - 0x938d5fff libsystem_notify.dylib (121) <623269F5-1518-3035-A916-8AF83C972154> /usr/lib/system/libsystem_notify.dylib
0x93eba000 - 0x93f0aff7 libcorecrypto.dylib (161.1) <135FD99E-2211-3DF4-825C-C9F816107F0C> /usr/lib/system/libcorecrypto.dylib
0x93fa3000 - 0x93fbbff7 libsystem_malloc.dylib (23.10.1) <CB52555E-0F5B-31E3-A42A-FD4F930E2192> /usr/lib/system/libsystem_malloc.dylib
0x940c1000 - 0x940c8ffb libsystem_pthread.dylib (53.1.4) <8B1B7B84-1B5D-32A8-AC0D-1E689E5C8A4C> /usr/lib/system/libsystem_pthread.dylib
0x941b0000 - 0x94201ff1 libstdc++.6.dylib (60) <354F284B-2343-3810-9CA2-E28038824F6E> /usr/lib/libstdc++.6.dylib
0x942f3000 - 0x942f8ff3 libsystem_platform.dylib (24.90.1) <0613F163-9A7A-3908-B30B-AC1627503933> /usr/lib/system/libsystem_platform.dylib
0x946b6000 - 0x94748ff9 libsystem_c.dylib (997.90.3) <80D21D3D-1031-314C-B1F0-0B35B977CEFB> /usr/lib/system/libsystem_c.dylib
0x948c8000 - 0x948c9fff libDiagnosticMessagesClient.dylib (100) <B936B1D4-90BB-395D-8EA9-E1237608E7D0> /usr/lib/libDiagnosticMessagesClient.dylib
0x94e14000 - 0x94e15fff libSystem.B.dylib (1197.1.1) <E06132B8-2FD8-322D-A151-C9474B36B561> /usr/lib/libSystem.B.dylib
0x95541000 - 0x9556cff7 libsystem_network.dylib (241.3) <71EBA489-386D-3608-ADE6-CB50EBD1AB1B> /usr/lib/system/libsystem_network.dylib
0x9556d000 - 0x9556effa libsystem_sandbox.dylib (278.11) <E8BE1DF7-2F3D-3202-B807-A85C99220AB6> /usr/lib/system/libsystem_sandbox.dylib
0x955cc000 - 0x955f0ff3 libc++abi.dylib (49.1) <43A04ACF-97A5-35ED-B454-6B5C0CF0F99D> /usr/lib/libc++abi.dylib
0x95635000 - 0x95636ffd libunc.dylib (28) <22A126A1-DCFB-3BE5-A66B-C973F0A5D839> /usr/lib/system/libunc.dylib
0x957be000 - 0x95813fff libc++.1.dylib (120) <10C0A136-64F9-3CC2-9420-013247032120> /usr/lib/libc++.1.dylib
0x96b0b000 - 0x96b0dfff libsystem_configuration.dylib (596.13) <57095AFE-3FF1-3F42-A43E-ED679409B827> /usr/lib/system/libsystem_configuration.dylib
0x96e5d000 - 0x96e65fff libcopyfile.dylib (103) <1B1484BD-08B6-3BA9-94CA-A7C24B610EB3> /usr/lib/system/libcopyfile.dylib
0x96e66000 - 0x96e74ff7 libz.1.dylib (53) <858B4D9F-D87E-3D81-B07A-DF9632BD185F> /usr/lib/libz.1.dylib
0x97510000 - 0x97516ffb libunwind.dylib (35.3) <099D1A6F-A1F0-3D05-BF1C-0A7BB32D39C2> /usr/lib/system/libunwind.dylib
0x97a35000 - 0x97a40ffb libcommonCrypto.dylib (60049) <F8E60C43-22EE-3E0B-9546-3365056901F1> /usr/lib/system/libcommonCrypto.dylib
0x98ccc000 - 0x98cfdffa libsystem_m.dylib (3047.16) <28E614E8-7802-3E84-960A-AD4721EF10F7> /usr/lib/system/libsystem_m.dylib
0x9a27e000 - 0x9a36aff7 libxml2.2.dylib (26) <32040145-6FD6-3AD2-B98B-39F73BF9AC47> /usr/lib/libxml2.2.dylib
0x9a481000 - 0x9a485ffa libcache.dylib (62) <9730D7F2-D226-3F30-8D26-BF598CB781F6> /usr/lib/system/libcache.dylib
0x9a486000 - 0x9a489ff7 libdyld.dylib (239.4) <F4604F64-945B-3871-8F26-E9C55488BC27> /usr/lib/system/libdyld.dylib
0x9a90c000 - 0x9a914fff libsystem_dnssd.dylib (522.90.2) <A73663C9-CE65-3FF3-B41B-686728BBFB00> /usr/lib/system/libsystem_dnssd.dylib
0x9a91f000 - 0x9a943ff7 libxpc.dylib (300.90.2) <5ACBBE2C-74EB-3E88-BCBF-C573095318A5> /usr/lib/system/libxpc.dylib
0x9a944000 - 0x9aa34ffb libiconv.2.dylib (41) <848FEBA7-2E3E-3ECB-BD59-007F32468787> /usr/lib/libiconv.2.dylib
0x9ab8e000 - 0x9aca0ffc libsqlite3.dylib (158) <B3DB0FED-FE4C-314D-8329-CF7708C8AAF4> /usr/lib/libsqlite3.dylib
0x9ad8d000 - 0x9ad8efff libsystem_blocks.dylib (63) <2AC67D5E-ECD4-3644-A53C-9684F9B7AA33> /usr/lib/system/libsystem_blocks.dylib
0x9b789000 - 0x9b98bfff com.apple.CoreFoundation (6.9 - 855.14) <756998B3-F507-3474-AFB2-769FC9CE5263> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x9ba93000 - 0x9bc3b4af libobjc.A.dylib (551.1) <31CBE178-E972-30D1-ADC6-4B8345CAE326> /usr/lib/libobjc.A.dylib
0x9bd2a000 - 0x9bd52fff libsystem_info.dylib (449.1.3) <BB68E8CC-422F-3121-8C86-D0F766FB696D> /usr/lib/system/libsystem_info.dylib
0x9bd91000 - 0x9bd92fff libremovefile.dylib (33) <ED35EA79-EB06-3B84-A6D4-B1A9D6B8648D> /usr/lib/system/libremovefile.dylib
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 8
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 2150
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=85.5M resident=28.2M(33%) swapped_out_or_unallocated=57.2M(67%)
Writable regions: Total=87.7M written=856K(1%) resident=1248K(1%) swapped_out=0K(0%) unallocated=86.5M(99%)
REGION TYPE VIRTUAL
=========== =======
Kernel Alloc Once 4K
MALLOC 74.2M
MALLOC (admin) 32K
Stack 69.2M
VM_ALLOCATE 612K
__DATA 944K
__LINKEDIT 49.8M
__OBJC 60K
__PAGEZERO 4K
__TEXT 35.7M
__UNICODE 544K
mapped file 206.3M
shared memory 4K
=========== =======
TOTAL 437.3M
System Profile:
Model: MacBookPro10,1, BootROM MBP101.00EE.B03, 4 processors, Intel Core i7, 2.7 GHz, 16 GB, SMC 2.3f36
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 1024 MB
Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xEF), Broadcom BCM43xx 1.0 (5.106.98.100.22)
Bluetooth: Version 4.2.3f10 13477, 3 services, 15 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM768E, 751.28 GB
USB Device: Hub
USB Device: FaceTime HD Camera (Built-in)
USB Device: Hub
USB Device: Hub
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 23.4
Message was edited by: amhest
Maybe you are looking for
-
Why can't I access certain websites, such as google or facebook, in any browser?
This started last night, and it is strange. I am unable to access a few websites, such as Google, Facebook, and the sign in page for my google account. I have tried Firefox, Chrome, and Safari all with pretty much the same results. I have reset the
-
i want video chating but not sapporting flash player then chating site is not open in firefox browser
-
Has the bounce facility been removed from mail?
I want to Bounce an email back to the sender but can't find the command in Mail 5.3. Has this feature been removed since the previous version of mail?
-
Has anyone experienced any odd crashing since mavericks came out?
My computer has maybe crashed once or twice since I've owned it. I've had mavericks for three days, and I've been experiencing multiple crashes. My screens get pixelated and offset, then shuts down. Is this a Mavericks bug, or something else going on
-
ITunes 8.2.1 Window Won't Open!!!!!
I have iTunes 8.2.1 installed on a MacBook Pro (OS X (10.5.8)) and I can't get the window to open. The toolbar appears on the top and allows you to play music (with limited functionality). I can also play music using my iTunes Widget (same thing - wi