New Macbook Pro gets really hot in sleep mode - what should i do?

Discussion in 'MacBook Pro' started by annamac, Nov 22, 2008.

  1. annamac macrumors member

    Joined:
    Jun 13, 2008
    #1
    Hi,
    I am the proud owner of a 2.53 GHz Macbook Pro for 10 days now. and it has happened twice already, that I - after working on it for a while - close the lid, put it in a bag..... and it gets HOT!!! as in: burning hot! while in sleep mode - how can that happen? the first time it woke up immediately, started fanning and everyhting was cool... or at least cooler..
    today it did not wake up, i had to force it to shut down, and then restart it.

    should i worry and take it back, or did i do something wrong?
     
  2. richard.mac macrumors 603

    richard.mac

    Joined:
    Feb 2, 2007
    Location:
    51.50024, -0.12662
    #2
    it probably didnt get into sleep mode properly and the airflow was blocked by your bag making it hotter. in sleep mode all thats powered is the RAM and a few little components so you can resume exactly where you left off after waking. it should seem as though its off as the hard drive and fans spin down.

    give it a fresh restart and then just make sure it goes to sleep properly in the future by listening to the fans turn off and waiting for the sleep light to turn on and pulsate.

    if the same behaviour continues try resetting the PRAM by holding command-shift-P-R until the second startup chime. dont do it otherwise.
     
  3. MBPDiva macrumors regular

    Joined:
    Nov 1, 2008
    Location:
    on Orion's Belt
    #3
    He should be able to close the lid and stick it in his bag without the machine getting super hot. That's what we all do with no problems. Hey OP, there's a ton of threads about the heating issue on this board. Do a search.
     
  4. richard.mac macrumors 603

    richard.mac

    Joined:
    Feb 2, 2007
    Location:
    51.50024, -0.12662
    #4
    yeh if his (her?) MBP went to sleep normally it certainly wouldnt get hot when put in a case. it will cool down as the hottest components arent powered.

    but what im saying is sometimes a MacBook may not sleep properly (software hiccup?) and the components will continue to run (screen may turn off) causing it to heat up as the case blocks the exhaust vent at the back. its rare but can still happen, happened to a mate of mine.

    just make sure it goes to sleep properly or if it continues to not sleep reset the PRAM.
     
  5. MBPDiva macrumors regular

    Joined:
    Nov 1, 2008
    Location:
    on Orion's Belt
    #5
    ^^^^ Oops, anna is a girl. :p You're right, it could be an issue with the software as a lot of these new MBPs are having issues. And the bag block the airflow.
     
  6. macrem macrumors 65816

    macrem

    Joined:
    Mar 11, 2008
    #6
    I always make sure mine's really asleep first. It takes a few seconds in order for your MB to prepare for deep sleep in case the battery goes dead while in sleep mode. If you waited and then there is still a problem with sleep, then I'd start to worry. Who knows what happens if you start jolting the HD triggering the motion sensors or futzing with the lid while its preparing to sleep.
     
  7. annamac thread starter macrumors member

    Joined:
    Jun 13, 2008
    #7
    hi guys (girls too?),
    yep, i am a girl.
    thank you so much for your replies.. i will watch whether it really sleeps and then still gets hot... i was in a hurry yesterday, so maybe i did not really wait long enough... otherwise everything works great, so i would hate to take it back, i figure once you start exchanging stuff, it might be the beginning of endless repairs etc...
    let's hope i was just sloppy...
     
  8. macrem macrumors 65816

    macrem

    Joined:
    Mar 11, 2008
    #8
    ^ I'm not a girl, but sure do love the ladies *<8o)

    Let us know how it goes if you get a chance... Cheers!
     
  9. MBPDiva macrumors regular

    Joined:
    Nov 1, 2008
    Location:
    on Orion's Belt
    #9
    I'm a girl too. :p Maybe you were in a hurry and didn't close the lid tight? Sometimes I notice that when I'm in a hurry and close the lid, it closes but doesn't click shut.
     
  10. NC MacGuy macrumors 603

    NC MacGuy

    Joined:
    Feb 9, 2005
    Location:
    The good side of the grass.
    #10
    I posted this before in the Air forums but I had a similar thing happen to me when I first got my Air. It turns out it was opening inside my briefcase and turning on. The magnetic latch would sense it opening a little bit and initiate active mode and then it'd shut quickly because I was jostling it around and it got confused. Got a tighter briefcase.

    There's also been a few posts in the MB forums of new MB's not going into sleep mode properly when moved. Fine when stationary though.
     
  11. annamac thread starter macrumors member

    Joined:
    Jun 13, 2008
    #11
    it happened again....

    hi, i happened again. this time, i wanted to wait until it was really asleep, but it wouldnt go to sleep after closing the lid!
    so i wanted to wake it up again, to shut it down, but i couldn't bring it back to life except with a forced shutdown=restart. now everything seems fine again.
    mac os x gave me the following error report (which i don't understant... does it describe the crash or does it maybe only describe my force shutdown?):

    1` Sun Nov 23 04:27:17 2008
    Panic: Unresponsive processor
    EAX: 0xffffffff, EBX: 0x071fc200, ECX: 0x00000000, EDX: 0x680d1000
    CR2: 0x51ac3000, EBP: 0x7b767958, ESI: 0x00000010, EDI: 0x00000001
    EFL: 0x00000002, EIP: 0x0084a29d, CS: 0x00000008, DS: 0x00000010
    Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
    0x50d10f78 : 0x1af67d (0x7b7678a0 0x50cba000 0x50d10fa8 0x6d333c8)
    0x50d10f98 : 0x44957a (0x2 0x7b7678a0 0x50d10fd8 0x1382d8)
    0x50d10fd8 : 0x1a0431 (0x7b7678a0 0x0 0x131cd1 0x50cba000)
    0x7b767958 : 0x848f93 (0x71fc200 0x758d500 0x71742c4 0x0)
    0x7b767988 : 0x84af09 (0x71fc200 0x758d500 0x1 0x3ec9fc)
    0x7b7679b8 : 0x84aca2 (0x71fc200 0x758d500 0x71742c0 0x3ebe9a)
    0x7b767a08 : 0x420ec7 (0x71fc200 0x718a200 0x0 0x0)
    0x7b767a38 : 0x84899c (0x736c840 0x8489a4 0x71fc200 0x718a200)
    0x7b767a68 : 0x84253e (0x71fc200 0x718a200 0x0 0x7178da0)
    0x7b767a88 : 0xac984c (0x718a200 0x0 0x1 0x3ea811)
    Backtrace continues...
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.driver.AppleHDA(1.5.8fc46)@0xab8000->0xb1ffff
    dependency: com.apple.driver.DspFuncLib(1.5.8fc46)@0xa4d000
    dependency: com.apple.iokit.IOHDAFamily(1.5.8fc46)@0x83f000
    dependency: com.apple.iokit.IOAudioFamily(1.6.4b7)@0xa36000
    com.apple.driver.AppleHDAController(1.5.8fc46)@0x846000->0x854fff
    dependency: com.apple.iokit.IOPCIFamily(2.5)@0x5f4000
    dependency: com.apple.iokit.IOHDAFamily(1.5.8fc46)@0x83f000
    com.apple.iokit.IOHDAFamily(1.5.8fc46)@0x83f000->0x845fff
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.driver.AppleHDAController(1.5.8fc46)@0x846000->0x854fff
    dependency: com.apple.iokit.IOPCIFamily(2.5)@0x5f4000
    dependency: com.apple.iokit.IOHDAFamily(1.5.8fc46)@0x83f000

    BSD process name corresponding to current thread: kernel_task

    Mac OS version:
    9F2114

    Kernel version:
    Darwin Kernel Version 9.5.1: Fri Sep 19 16:19:24 PDT 2008; root:xnu-1228.8.30~1/RELEASE_I386
    System model name: MacBookPro5,1 (Mac-F42D86C8)
    panic(cpu 0 caller 0x00193C01): "pmap_flush_tlbs() timeout: " "cpu(s) failing to respond to interrupts, pmap=0x539600 cpus_to_respond=0x2"@/SourceCache/xnu/xnu-1228.8.30/osfmk/i386/pmap.c:4580
    Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
    0x680938b8 : 0x12b4c9 (0x45aaac 0x680938ec 0x1335ba 0x0)
    0x68093908 : 0x193c01 (0x460bdc 0x539600 0x2 0x19ec93)
    0x68093978 : 0x194d95 (0x539600 0x4a32f000 0x0 0x0)
    0x68093a18 : 0x1749a6 (0x1123a5 0x0 0x68093a88 0x19ee64)
    0x68093ab8 : 0x16a44a (0xaddc2bc 0x0 0x0 0x1000)
    0x68093bd8 : 0x16aa47 (0x4a330000 0x0 0x1 0x0)
    0x68093c18 : 0x16b99c (0x203ce0c 0x4a32f000 0x0 0x4a330000)
    0x68093cf8 : 0x12853c (0x203ce0c 0x4a32f000 0x0 0x4)
    0x68093d78 : 0x14d230 (0x6ccf730 0x2e03 0xb1089ac 0xb1089c0)
    0x68093db8 : 0x12d4dc (0x7bbfba0 0xb108990 0x0 0x0)
    0x68093df8 : 0x1265df (0x7bbfb00 0x0 0x24 0x68093ee4)
    0x68093f08 : 0x19806d (0x68093f44 0x0 0x0 0x0)
    0x68093fc8 : 0x1a0857 (0x9ca17a0 0x1 0x10 0x9ca1560)
    No mapping exists for frame pointer
    Backtrace terminated-invalid frame pointer 0xb0080ba8

    BSD process name corresponding to current thread: mdworker
     

Share This Page