Ok, so my fianceés MBP is having serious sleep issues since the 10.5.7 update.
When you close the lid, it just sits there with a non-pulsing sleep light, and when you try to open it, the screen stays black and unresponsive, and a hard reset is the only option. I think that it will sleep successfully one time, before the issue surfaces, but still clearly not ideal!
Apparently this is a fairly widespread issue, and the fix that's recommended is to "toggle" ethernet active/inactive: http://www.macfixit.com/article.php?story=20090518095106449
She's tried that, and apparently it still has the problem, so I'm kinda confused!
If I compare her system.log file in Console.app to mine when we try to sleep them, they both do the same thing until the
"AirPort: Link Down on en1"
line, which doesn't appear on hers, and the next line is from the reboot. This is the last system log before the SafeSleep command, so clearly this is what's causing the problem, as indicated by the ethernet toggle (though I'm wondering if in this case she should toggle her airport rather than ethernet port?).
I've asked her to use the SmartSleep prefpane to try other sleep modes, just as a possible temporary fix, but it'd be nice to get to the bottom of the problem!
So, any ideas?
Thanks
Ben
When you close the lid, it just sits there with a non-pulsing sleep light, and when you try to open it, the screen stays black and unresponsive, and a hard reset is the only option. I think that it will sleep successfully one time, before the issue surfaces, but still clearly not ideal!
Apparently this is a fairly widespread issue, and the fix that's recommended is to "toggle" ethernet active/inactive: http://www.macfixit.com/article.php?story=20090518095106449
She's tried that, and apparently it still has the problem, so I'm kinda confused!
If I compare her system.log file in Console.app to mine when we try to sleep them, they both do the same thing until the
"AirPort: Link Down on en1"
line, which doesn't appear on hers, and the next line is from the reboot. This is the last system log before the SafeSleep command, so clearly this is what's causing the problem, as indicated by the ethernet toggle (though I'm wondering if in this case she should toggle her airport rather than ethernet port?).
I've asked her to use the SmartSleep prefpane to try other sleep modes, just as a possible temporary fix, but it'd be nice to get to the bottom of the problem!
So, any ideas?
Thanks
Ben