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

Groups > comp.sys.mac.system > #30294

Re: Hot MacBookPro Retina

Show all headers | View raw

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.

Back to comp.sys.mac.system | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

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

csiph-web