Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.system > #29908 > unrolled thread

Hot MacBookPro Retina

Back to article view | Back to comp.sys.mac.system

Contents

  Hot MacBookPro Retina qubit <qubit@quandoveloce.com> - 2012-08-23 00:27 +0930
    Re: Hot MacBookPro Retina Jolly Roger <jollyroger@pobox.com> - 2012-08-22 08:09 -0700
      Re: Hot MacBookPro Retina nospam <nospam@nospam.invalid> - 2012-08-22 08:19 -0700
      Re: Hot MacBookPro Retina qubit <qubit@quandoveloce.com> - 2012-08-23 08:57 +0930
        Re: Hot MacBookPro Retina nospam@see.signature (Richard Maine) - 2012-08-22 17:17 -0700
          Re: Hot MacBookPro Retina qubit <qubit@quandoveloce.com> - 2012-08-23 10:44 +0930
    Re: Hot MacBookPro Retina YourName@YourISP.com (Your Name) - 2012-08-23 09:10 +1200
      Re: Hot MacBookPro Retina nospam <nospam@nospam.invalid> - 2012-08-22 16:05 -0700
        Re: Hot MacBookPro Retina John McWilliams <jpmcw@comcast.net> - 2012-08-22 16:32 -0700
          Re: Hot MacBookPro Retina nospam <nospam@nospam.invalid> - 2012-08-22 17:08 -0700
      Re: Hot MacBookPro Retina Lewis <g.kreme@gmail.com.dontsendmecopies> - 2012-08-23 08:14 +0000
        Re: Hot MacBookPro Retina YourName@YourISP.com (Your Name) - 2012-08-24 08:57 +1200
          Re: Hot MacBookPro Retina Lewis <g.kreme@gmail.com.dontsendmecopies> - 2012-08-23 22:03 +0000
            Re: Hot MacBookPro Retina YourName@YourISP.com (Your Name) - 2012-08-24 13:26 +1200
    Re: Hot MacBookPro Retina Ed Anson <EdAnson@comcast.net> - 2012-08-22 18:45 -0400
      Re: Hot MacBookPro Retina John McWilliams <jpmcw@comcast.net> - 2012-08-22 16:09 -0700
      Re: Hot MacBookPro Retina qubit <qubit@quandoveloce.com> - 2012-08-23 09:35 +0930
        Re: Hot MacBookPro Retina JF Mezei <jfmezei.spamnot@vaxination.ca> - 2012-08-22 23:37 -0400
    Re: Hot MacBookPro Retina YourName@YourISP.com (Your Name) - 2012-08-26 16:32 +1200
      Re: Hot MacBookPro Retina qubit <qubit@quandoveloce.com> - 2012-08-31 09:13 +0930

#29908 — Hot MacBookPro Retina

I closed the lid on my MBP-R and left it in a thin computer type carry 
bag for a few hours this afternoon. When I removed it it was hot, not 
just warm but hot.

The fan came on when I opened it, and it took perhaps 3-5 minutes before 
drawing the desktop.

This does not seem like normal behavior. I would have thought sleep 
mode, induced from closing the lid, would have been a power hibernation.

It normally sits closed on my desk, running 2 27" displays, never 
anything than barely noticeably warm.

[toc] | [next] | [standalone]

#29909

In article <k12s19$qbh$1@speranza.aioe.org>,
 qubit <qubit@quandoveloce.com> wrote:

> I closed the lid on my MBP-R and left it in a thin computer type carry 
> bag for a few hours this afternoon. When I removed it it was hot, not 
> just warm but hot.
> 
> The fan came on when I opened it, and it took perhaps 3-5 minutes before 
> drawing the desktop.
> 
> This does not seem like normal behavior. I would have thought sleep 
> mode, induced from closing the lid, would have been a power hibernation.
> 
> It normally sits closed on my desk, running 2 27" displays, never 
> anything than barely noticeably warm.

How sure are you that it's actually going to sleep when you lose the 
lid. Have you watched it to see?

-- 
Send responses to the relevant news group rather than email to me.
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.

JR

[toc] | [prev] | [next] | [standalone]

#29910

In article <jollyroger-CA38A2.08091722082012@news.individual.net>,
Jolly Roger <jollyroger@pobox.com> wrote:

> > I closed the lid on my MBP-R and left it in a thin computer type carry 
> > bag for a few hours this afternoon. When I removed it it was hot, not 
> > just warm but hot.
> > 
> > The fan came on when I opened it, and it took perhaps 3-5 minutes before 
> > drawing the desktop.
> > 
> > This does not seem like normal behavior. I would have thought sleep 
> > mode, induced from closing the lid, would have been a power hibernation.
> > 
> > It normally sits closed on my desk, running 2 27" displays, never 
> > anything than barely noticeably warm.
> 
> How sure are you that it's actually going to sleep when you lose the 
> lid. Have you watched it to see?

there's no way to tell. there is no pulsating led anymore.

the only way to guarantee it went to sleep is to pick sleep from the
menu and then close the lid, however, it could still wake on its own
after that.

as for the problem, contact apple and have them test it. that's not
normal.

[toc] | [prev] | [next] | [standalone]

#29926

On 23/08/12 12:39 AM, Jolly Roger wrote:
> In article <k12s19$qbh$1@speranza.aioe.org>,
>   qubit <qubit@quandoveloce.com> wrote:
>
>> I closed the lid on my MBP-R and left it in a thin computer type carry
>> bag for a few hours this afternoon. When I removed it it was hot, not
>> just warm but hot.
>>
>> The fan came on when I opened it, and it took perhaps 3-5 minutes before
>> drawing the desktop.
>>
>> This does not seem like normal behavior. I would have thought sleep
>> mode, induced from closing the lid, would have been a power hibernation.
>>
>> It normally sits closed on my desk, running 2 27" displays, never
>> anything than barely noticeably warm.
>
> How sure are you that it's actually going to sleep when you lose the
> lid. Have you watched it to see?
>


One has always assumed that closing the lid induced sleep mode. The 
Apple logo is not lit, but that of course is not an indicator, the MBP 
is running and drawing a desktop on two displays, and the lid logo is 
unlit, lid closed

[toc] | [prev] | [next] | [standalone]

#29931

qubit <qubit@quandoveloce.com> wrote:

> On 23/08/12 12:39 AM, Jolly Roger wrote:
> > In article <k12s19$qbh$1@speranza.aioe.org>,
> >   qubit <qubit@quandoveloce.com> wrote:
> >
> >> I closed the lid on my MBP-R and left it in a thin computer type carry
> >> bag for a few hours this afternoon. When I removed it it was hot, not
> >> just warm but hot.
> >>
> >> The fan came on when I opened it, and it took perhaps 3-5 minutes before
> >> drawing the desktop.
> >>
> >> This does not seem like normal behavior. I would have thought sleep
> >> mode, induced from closing the lid, would have been a power hibernation.
> >>
> >> It normally sits closed on my desk, running 2 27" displays, never
> >> anything than barely noticeably warm.
> >
> > How sure are you that it's actually going to sleep when you lose the
> > lid. Have you watched it to see?
> >
> One has always assumed that closing the lid induced sleep mode. The 
> Apple logo is not lit, but that of course is not an indicator, the MBP
> is running and drawing a desktop on two displays, and the lid logo is
> unlit, lid closed

If it is driving external displays, then it probably does *NOT* go to
sleep when you close the lid. That particular detail has changed from
model to model; I seem to recall some older Mac laptops that could not
operate that way with the lid closed. But for the most part, I'd expect
an MBP pro to stay awake when you closed the lid if external displays
were connected. There is no particular reason why closing the lid should
necessarily cause sleep mode in that case. I bet some of the other
posters skipped over the "external displays" part; I did at first
glance, but it is probably pretty relevant.

When you close the lid, do the external displays immediately go off (or
at least in their "no data being recieved" mode, which usually causes
most modern displays to power down soon thereafter)? If they stay on and
displaying normally for even a brief while, then your laptop has not
gone to sleep. Eventually, you might get the display sleep mode, but
that takes longer. If the lid closure triggers system sleep, that should
be pretty quick.

If this is your issue, then it is not a problem with your system - just
with your expectations. I'm not sure it is what is happening, but I'm
sure suspicious.

-- 
Richard Maine                    | Good judgment comes from experience;
email: last name at domain . net | experience comes from bad judgment.
domain: summertriangle           |  -- Mark Twain

[toc] | [prev] | [next] | [standalone]

#29934

On 23/08/12 9:47 AM, Richard Maine wrote:
> qubit <qubit@quandoveloce.com> wrote:
>
>> On 23/08/12 12:39 AM, Jolly Roger wrote:
>>> In article <k12s19$qbh$1@speranza.aioe.org>,
>>>    qubit <qubit@quandoveloce.com> wrote:
>>>
>>>> I closed the lid on my MBP-R and left it in a thin computer type carry
>>>> bag for a few hours this afternoon. When I removed it it was hot, not
>>>> just warm but hot.
>>>>
>>>> The fan came on when I opened it, and it took perhaps 3-5 minutes before
>>>> drawing the desktop.
>>>>
>>>> This does not seem like normal behavior. I would have thought sleep
>>>> mode, induced from closing the lid, would have been a power hibernation.
>>>>
>>>> It normally sits closed on my desk, running 2 27" displays, never
>>>> anything than barely noticeably warm.
>>>
>>> How sure are you that it's actually going to sleep when you lose the
>>> lid. Have you watched it to see?
>>>
>> One has always assumed that closing the lid induced sleep mode. The
>> Apple logo is not lit, but that of course is not an indicator, the MBP
>> is running and drawing a desktop on two displays, and the lid logo is
>> unlit, lid closed
>
> If it is driving external displays, then it probably does *NOT* go to
> sleep when you close the lid. That particular detail has changed from
> model to model; I seem to recall some older Mac laptops that could not
> operate that way with the lid closed. But for the most part, I'd expect
> an MBP pro to stay awake when you closed the lid if external displays
> were connected. There is no particular reason why closing the lid should
> necessarily cause sleep mode in that case. I bet some of the other
> posters skipped over the "external displays" part; I did at first
> glance, but it is probably pretty relevant.
>
> When you close the lid, do the external displays immediately go off (or
> at least in their "no data being recieved" mode, which usually causes
> most modern displays to power down soon thereafter)? If they stay on and
> displaying normally for even a brief while, then your laptop has not
> gone to sleep. Eventually, you might get the display sleep mode, but
> that takes longer. If the lid closure triggers system sleep, that should
> be pretty quick.
>
> If this is your issue, then it is not a problem with your system - just
> with your expectations. I'm not sure it is what is happening, but I'm
> sure suspicious.
>



Under normal operation, my MBP is run lid closed, and the connected 
displays active. So sleep mode ( or now power nap ) is not mandated by 
the lid being closed per se.

In the situation of the displays not being connected, and the act of 
closing the lid, the expectation was there that sleep/power nap would be 
invoked; the lid light is out, the screen is presumptively blank ( 
Shroedinger's cat etc.). But that is now obliviously overridden by the 
Energy Saving settings


More combinations than there used to be. I get it may be my 
misinterpretation of what should be happening, and it may be a product 
of ( as other post) the energy saver sleep settings being set = never. 
But, a combination exists where the heat ramped up substantially, and 
that  is perhaps the bottom line, there arguably should have been a trap 
somewhere to stop the heat generation, despite whatever I as the user 
may do to the configurable settings and in the normal practice of 
closing a lid ( with or without inducing sleep).

The user ( myself included) does not always follow the path of best safe 
practice, clearly ; but it does seem on reflection, there is a potential 
hole in the safety profile.

I think the take home, is that sleep is not guaranteed by closing the 
lid. A false assumption to think it is/would be.  Whether that ( close 
overrides all) is a reasonable expectation or not, is another issue. 
Probably was valid back in times of simpler combinations (PB1400 et 
all), or maybe not.

[toc] | [prev] | [next] | [standalone]

#29914

In article <k12s19$qbh$1@speranza.aioe.org>, qubit
<qubit@quandoveloce.com> wrote:
> 
> I closed the lid on my MBP-R and left it in a thin computer type carry 
> bag for a few hours this afternoon. When I removed it it was hot, not 
> just warm but hot.
> 
> The fan came on when I opened it, and it took perhaps 3-5 minutes before 
> drawing the desktop.
> 
> This does not seem like normal behavior. I would have thought sleep 
> mode, induced from closing the lid, would have been a power hibernation.
> 
> It normally sits closed on my desk, running 2 27" displays, never 
> anything than barely noticeably warm.

If you're not going to use it for "a few hours" (not to mention sticking
it in a bag), then use Shutdown - it only takes a few seconds to reboot.

[toc] | [prev] | [next] | [standalone]

#29923

In article
<YourName-2308120910340001@203-118-187-181.dsl.dyn.ihug.co.nz>, Your
Name <YourName@YourISP.com> wrote:

> If you're not going to use it for "a few hours" (not to mention sticking
> it in a bag), then use Shutdown - it only takes a few seconds to reboot.

the only reason to shut down is if you aren't using it for several days.

for a few hours, sleep is the way to go.

either way, something is wrong, it should not be hot.

[toc] | [prev] | [next] | [standalone]

#29927

On 8/22/12   PDT 4:05 PM, nospam wrote:
> In article
> <YourName-2308120910340001@203-118-187-181.dsl.dyn.ihug.co.nz>, Your
> Name <YourName@YourISP.com> wrote:
>
>> If you're not going to use it for "a few hours" (not to mention sticking
>> it in a bag), then use Shutdown - it only takes a few seconds to reboot.
>
> the only reason to shut down is if you aren't using it for several days.

No, there are other reasons.
>
> for a few hours, sleep is the way to go.

In some instances; not all.
>
> either way, something is wrong, it should not be hot.

Probably a process cut snorlgedated when it tried to effect Sleep, so it 
never entered Sleep fully, and never finished the process.

Of course, if this happens repeatedly, something IS wrong.

[toc] | [prev] | [next] | [standalone]

#29929

In article <k13q6n$2sb$1@dont-email.me>, John McWilliams
<jpmcw@comcast.net> wrote:

> >> If you're not going to use it for "a few hours" (not to mention sticking
> >> it in a bag), then use Shutdown - it only takes a few seconds to reboot.
> >
> > the only reason to shut down is if you aren't using it for several days.
> 
> No, there are other reasons.

ok, it's very rare that you need to shut down for short periods. sleep
is almost always what to do.

[toc] | [prev] | [next] | [standalone]

#29945

In message <YourName-2308120910340001@203-118-187-181.dsl.dyn.ihug.co.nz> 
  Your Name <YourName@YourISP.com> wrote:
> If you're not going to use it for "a few hours" (not to mention sticking
> it in a bag), then use Shutdown - it only takes a few seconds to reboot.

No. There is no reason to shutdown unless it is gong to be many days,
possibly weeks, before you use the machine again. Sleep is perfectly
good. The MBPr should not be waking up when closed and should not be hot
when removed from a bag.

-- 
'Pardon me for living, I'm sure.' NO-ONE GETS PARDONED FOR LIVING.

[toc] | [prev] | [next] | [standalone]

#29959

In article <slrnk3bpio.8tj.g.kreme@mbp55.local>, Lewis
<g.kreme@gmail.com.dontsendmecopies> wrote:
> In message <YourName-2308120910340001@203-118-187-181.dsl.dyn.ihug.co.nz> 
>   Your Name <YourName@YourISP.com> wrote:
> >
> > If you're not going to use it for "a few hours" (not to mention sticking
> > it in a bag), then use Shutdown - it only takes a few seconds to reboot.
> 
> No. There is no reason to shutdown unless it is gong to be many days,
> possibly weeks, before you use the machine again. Sleep is perfectly
> good. The MBPr should not be waking up when closed and should not be hot
> when removed from a bag.

There's no reason to not shutdown either when you know you're not going to
be using the computer for a while. The ONLY reason to not shutdown is
sheer laziness at having to wait a few extra seconds for it to reboot,
which of course is just far too long for the greedy "I want it NOW!"
generation.  :-(

[toc] | [prev] | [next] | [standalone]

#29965

In message <YourName-2408120857320001@203-118-187-155.dsl.dyn.ihug.co.nz> 
  Your Name <YourName@YourISP.com> wrote:
> In article <slrnk3bpio.8tj.g.kreme@mbp55.local>, Lewis
> <g.kreme@gmail.com.dontsendmecopies> wrote:
>> In message <YourName-2308120910340001@203-118-187-181.dsl.dyn.ihug.co.nz> 
>>   Your Name <YourName@YourISP.com> wrote:
>> >
>> > If you're not going to use it for "a few hours" (not to mention sticking
>> > it in a bag), then use Shutdown - it only takes a few seconds to reboot.
>> 
>> No. There is no reason to shutdown unless it is gong to be many days,
>> possibly weeks, before you use the machine again. Sleep is perfectly
>> good. The MBPr should not be waking up when closed and should not be hot
>> when removed from a bag.

> There's no reason to not shutdown either when you know you're not going to
> be using the computer for a while. The ONLY reason to not shutdown is
> sheer laziness at having to wait a few extra seconds for it to reboot,
> which of course is just far too long for the greedy "I want it NOW!"
> generation.  :-(

Not at all true. It may take many minutes for you to get back to the
state your computer was in before shutdown, depending on if you've done
things like disabled resume or if you have apps that don't support it.

-- 
Growing up leads to growing old, and then to dying/And dying to me don't
sound like all that much fun.

[toc] | [prev] | [next] | [standalone]

#29977

In article <slrnk3da69.f7n.g.kreme@mbp55.local>, Lewis
<g.kreme@gmail.com.dontsendmecopies> wrote:
> In message <YourName-2408120857320001@203-118-187-155.dsl.dyn.ihug.co.nz> 
>   Your Name <YourName@YourISP.com> wrote:
> > In article <slrnk3bpio.8tj.g.kreme@mbp55.local>, Lewis
> > <g.kreme@gmail.com.dontsendmecopies> wrote:
> >> In message <YourName-2308120910340001@203-118-187-181.dsl.dyn.ihug.co.nz> 
> >> Your Name <YourName@YourISP.com> wrote:
> >> >
> >> > If you're not going to use it for "a few hours" (not to mention sticking
> >> > it in a bag), then use Shutdown - it only takes a few seconds to reboot.
> >> 
> >> No. There is no reason to shutdown unless it is gong to be many days,
> >> possibly weeks, before you use the machine again. Sleep is perfectly
> >> good. The MBPr should not be waking up when closed and should not be hot
> >> when removed from a bag.
> > 
> > There's no reason to not shutdown either when you know you're not going to
> > be using the computer for a while. The ONLY reason to not shutdown is
> > sheer laziness at having to wait a few extra seconds for it to reboot,
> > which of course is just far too long for the greedy "I want it NOW!"
> > generation.  :-(
> 
> Not at all true. It may take many minutes for you to get back to the
> state your computer was in before shutdown, depending on if you've done
> things like disabled resume or if you have apps that don't support it.

Proves my point really.  :-\

[toc] | [prev] | [next] | [standalone]

#29920

On 8/22/12 10:57 AM, qubit wrote:
>
> I closed the lid on my MBP-R and left it in a thin computer type carry
> bag for a few hours this afternoon. When I removed it it was hot, not
> just warm but hot.
>
> The fan came on when I opened it, and it took perhaps 3-5 minutes before
> drawing the desktop.
>
> This does not seem like normal behavior. I would have thought sleep
> mode, induced from closing the lid, would have been a power hibernation.
>
> It normally sits closed on my desk, running 2 27" displays, never
> anything than barely noticeably warm.
>

That is not normal at all. I had mine in a bag for a few hours just this 
afternoon and it was not even noticeably warm when I took it out. 
Contact Apple to have it checked out.

/Ed

[toc] | [prev] | [next] | [standalone]

#29924

On 8/22/12   PDT 3:45 PM, Ed Anson wrote:
> On 8/22/12 10:57 AM, qubit wrote:
>>
>> I closed the lid on my MBP-R and left it in a thin computer type carry
>> bag for a few hours this afternoon. When I removed it it was hot, not
>> just warm but hot.
>>
>> The fan came on when I opened it, and it took perhaps 3-5 minutes before
>> drawing the desktop.
>>
>> This does not seem like normal behavior. I would have thought sleep
>> mode, induced from closing the lid, would have been a power hibernation.
>>
>> It normally sits closed on my desk, running 2 27" displays, never
>> anything than barely noticeably warm.
>>
>
> That is not normal at all. I had mine in a bag for a few hours just this
> afternoon and it was not even noticeably warm when I took it out.
> Contact Apple to have it checked out.

Save your time and trouble. Simply make sure all processes are done when 
you close the lid. What happened is probably and anomoly as something 
was underway the moment you shut the lid, so it never entered Sleep 
mode. Better still, the idea above: Shut it down if going into an 
enclosed space for a while.

[toc] | [prev] | [next] | [standalone]

#29928

On 23/08/12 8:15 AM, Ed Anson wrote:
> On 8/22/12 10:57 AM, qubit wrote:
>>
>> I closed the lid on my MBP-R and left it in a thin computer type carry
>> bag for a few hours this afternoon. When I removed it it was hot, not
>> just warm but hot.
>>
>> The fan came on when I opened it, and it took perhaps 3-5 minutes before
>> drawing the desktop.
>>
>> This does not seem like normal behavior. I would have thought sleep
>> mode, induced from closing the lid, would have been a power hibernation.
>>
>> It normally sits closed on my desk, running 2 27" displays, never
>> anything than barely noticeably warm.
>>
>
> That is not normal at all. I had mine in a bag for a few hours just this
> afternoon and it was not even noticeably warm when I took it out.
> Contact Apple to have it checked out.
>
> /Ed


That is what I would expect too.


I called Apple just now to log a report. Closing the lid should induce 
Power Nap. Support had me:

1. Reset the Energy Saver Computer and hard drive (SSD) settings
Both Battery and Power Adapter were = never, so that possibly may be a 
factor; but it doesn't get hot sitting on the desktop with the same 
settings and lid closed, and as heavy a usage as I put it too. The bag 
it was in is thin enough to think insulating properties would be low, 
but maybe not.

2. Also shutdown and held a key combo (shift control option power key ?) 
for 2 seconds to reset power management (I think).

So maybe anomalous, maybe not.

Anyway, a cautionary tale of sorts.

[toc] | [prev] | [next] | [standalone]

#29937

If you spill coffee on keyboard, the cafeine will prevent the Mac from
going to sleep :-)


If you have the lighted Apple logo (which is really the backlight for
the display) turn off when you close the lid, it means the Mac has
detected you are closing the lid. If it does not gosub sleep, then it
would be a different issue.

Look on the Apple web site for the magical incantation applicable to
yoru mac to reset the system management controller (SMC). You press some
keys when you power up.


Try to ping your laptop when it is supposed to be asleep. If it responds
to pings ( or owrse, allows you to connect via SSH/telnet/or whatever
you enabled, it means it isn't asleep).

The command line  way to manipulate power manegement is pmset

man pmset for the options.

There are a few more options there than are available in the GUI.

the -g argument will give you the current settings. (and there are
additional optiosn after the g possible, read the man page).

[toc] | [prev] | [next] | [standalone]

#30069

In article <k12s19$qbh$1@speranza.aioe.org>, qubit
<qubit@quandoveloce.com> wrote:
> 
> I closed the lid on my MBP-R and left it in a thin computer type carry 
> bag for a few hours this afternoon. When I removed it it was hot, not 
> just warm but hot.
> 
> The fan came on when I opened it, and it took perhaps 3-5 minutes before 
> drawing the desktop.
> 
> This does not seem like normal behavior. I would have thought sleep 
> mode, induced from closing the lid, would have been a power hibernation.
> 
> It normally sits closed on my desk, running 2 27" displays, never 
> anything than barely noticeably warm.

Assuming you don't want to actually shutdown the computer for whatever
reason, then there's various causes for a computer not going into sleep
mode. This article posted on MacWorld, which I've just stumbled across,
may or may not help track down the culprit ...
   

    Find out what's keeping your Mac awake
    --------------------------------------
    Have you ever been annoyed to find that your Mac wonąt
    go to sleep when you tell it to? Reader wjv found that, 
    in Mac OS X 10.6 and later, thereąs a simple way of 
    finding out whatąs keeping your Mac awake. To do so, 
    run the following command in your Terminal: 

        pmset -g assertions

    In the first section of output, youąll see the status
    of two kernel assertions (essentially, assumptions the 
    system makes about the state of your system) named
    PreventSystemSleep and PreventUserIdleSystemSleep. An
    accompanying status of 1 for either of these means that
    it is currently triggered. For example, hereąs what I 
    see when I run that command on my Mac mini:

        Assertion status system-wide:
          PreventUserIdleDisplaySleep    0
          PreventSystemSleep             0
          PreventUserIdleSystemSleep     1
          ExternalMedia                  1
          DisableLowPowerBatteryWarnings 0
          UserIsActive                   0
          ApplePushServiceTask           0
          BackgroundTask                 0

    Below that, youąll see something like this:

        Listed by owning process:
          pid 9165(iTunes): [0x0000000100001192] 00:18:23
PreventUserIdleSystemSleep named: "Nameless (via IOPMAssertionCreate)" 
          pid 175(coreaudiod): [0x0000000100001287] 00:12:39
NoIdleSleepAssertion named:
"com.apple.audio.'AppleHDAEngineOutput:1B,0,1,2:0'.noidlesleep" 

    This second section lists the processes which own any 
    enabled assertions, by process ID (the number after pid)
    and bundle ID (the text in parentheses after that). For
    example, above, two processes are preventing sleep: 
    iTunes (because Iąm currently listening to music) and
    coreoudiod (probably because itąs processing iTunesą
    music).

    If the bundle ID doesnąt ring a bell, you can enter:

        ps up <pid>

    at the Terminal command line, or look in Activity Monitor,
    to find the name of the command associated with that
    process. If you identify an app (such as iTunes in the
    example above), you can terminate it and put your Mac to
    sleep. If the process is something other than an app that
    you meant to run, terminating it may make your system
    unstable, which could cause it to crash ‹ which would be 
    a bit like sleeping, but not as nice. 

<http://www.macworld.com/article/1168151/find_out_whats_keeping_your_mac_awake.html>

[toc] | [prev] | [next] | [standalone]

#30294

On 26/08/12 2:02 PM, Your Name wrote:
> In article<k12s19$qbh$1@speranza.aioe.org>, qubit
> <qubit@quandoveloce.com>  wrote:
>> >
>> >I closed the lid on my MBP-R and left it in a thin computer type carry
>> >bag for a few hours this afternoon. When I removed it it was hot, not
>> >just warm but hot.
>> >
>> >The fan came on when I opened it, and it took perhaps 3-5 minutes before
>> >drawing the desktop.
>> >
>> >This does not seem like normal behavior. I would have thought sleep
>> >mode, induced from closing the lid, would have been a power hibernation.
>> >
>> >It normally sits closed on my desk, running 2 27" displays, never
>> >anything than barely noticeably warm.
> Assuming you don't want to actually shutdown the computer for whatever
> reason, then there's various causes for a computer not going into sleep
> mode. This article posted on MacWorld, which I've just stumbled across,
> may or may not help track down the culprit ...
>
>
>      Find out what's keeping your Mac awake
>      --------------------------------------
>      Have you ever been annoyed to find that your Mac won¹t
>      go to sleep when you tell it to? Reader wjv found that,
>      in Mac OS X 10.6 and later, there¹s a simple way of
>      finding out what¹s keeping your Mac awake. To do so,
>      run the following command in your Terminal:
>
>          pmset -g assertions
>
>      In the first section of output, you¹ll see the status
>      of two kernel assertions (essentially, assumptions the
>      system makes about the state of your system) named
>      PreventSystemSleep and PreventUserIdleSystemSleep. An
>      accompanying status of 1 for either of these means that
>      it is currently triggered. For example, here¹s what I
>      see when I run that command on my Mac mini:
>
>          Assertion status system-wide:
>            PreventUserIdleDisplaySleep    0
>            PreventSystemSleep             0
>            PreventUserIdleSystemSleep     1
>            ExternalMedia                  1
>            DisableLowPowerBatteryWarnings 0
>            UserIsActive                   0
>            ApplePushServiceTask           0
>            BackgroundTask                 0
>
>      Below that, you¹ll see something like this:
>
>          Listed by owning process:
>            pid 9165(iTunes): [0x0000000100001192] 00:18:23
> PreventUserIdleSystemSleep named: "Nameless (via IOPMAssertionCreate)"
>            pid 175(coreaudiod): [0x0000000100001287] 00:12:39
> NoIdleSleepAssertion named:
> "com.apple.audio.'AppleHDAEngineOutput:1B,0,1,2:0'.noidlesleep"
>
>      This second section lists the processes which own any
>      enabled assertions, by process ID (the number after pid)
>      and bundle ID (the text in parentheses after that). For
>      example, above, two processes are preventing sleep:
>      iTunes (because I¹m currently listening to music) and
>      coreoudiod (probably because it¹s processing iTunes¹
>      music).
>
>      If the bundle ID doesn¹t ring a bell, you can enter:
>
>          ps up <pid>
>
>      at the Terminal command line, or look in Activity Monitor,
>      to find the name of the command associated with that
>      process. If you identify an app (such as iTunes in the
>      example above), you can terminate it and put your Mac to
>      sleep. If the process is something other than an app that
>      you meant to run, terminating it may make your system
>      unstable, which could cause it to crash ‹ which would be
>      a bit like sleeping, but not as nice.
>
> <http://www.macworld.com/article/1168151/find_out_whats_keeping_your_mac_awake.html>
>


thanks, I have had a look at that and get what it is reporting. Next 
time it happens, (if there is a next time) I know where to look for the 
culprit.

The 1/01/70 creation stamps in some of the kernel assertions were 
interesting.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.sys.mac.system

csiph-web