MBP Freezing when joining network

Discussion in 'MacBook Pro' started by gusanitoverde, Aug 10, 2009.

  1. gusanitoverde macrumors 6502

    gusanitoverde

    Joined:
    Jun 12, 2003
    Location:
    Northern California
    #1
    Horrible. In all my mac user life I have seen Macs freezing as Windows freeze. I use my macbook Pro at work and at home. It is when I join either of the two wireless signals, when I get a freeze (about 5 minutes after joining.)

    I looked at the system profiler >logs>system for anything significant. I can't find anything.

    I remember messing with network configurations to change a DNS setting. About that time things started happening. So this morning I deleted my Airport configuration and rebuild a new one at the network preferences.

    Anyone has an idea why this happens?

    Thanks.
     
  2. gusanitoverde thread starter macrumors 6502

    gusanitoverde

    Joined:
    Jun 12, 2003
    Location:
    Northern California
    #2
    This I got from the last crash:

    Aug 10 15:50:21 Macintosh kernel[0]: jnl: disk1s2: journal replay done.
    Aug 10 15:50:21 Macintosh fseventsd[28]: event logs in /Volumes/Job's BD/.fseventsd out of sync with volume. destroying old logs. (283027 2 283117)
    Aug 10 15:50:21 Macintosh fseventsd[28]: log dir: /Volumes/Job's BD/.fseventsd getting new uuid: (Letters in caps I am not pasting)
    Aug 10 15:50:58 Macintosh mdworker[152]: (Error) SyncInfo: Boot-cache avoidance timed out!

    Anything interesting?
     
  3. gusanitoverde thread starter macrumors 6502

    gusanitoverde

    Joined:
    Jun 12, 2003
    Location:
    Northern California
    #3
    One more interesting detail...

    I thought this was hardware related. I have a MacBook Pro 2.33 Ghz. By now it is 3+ years old. Researching, I saw everything from freezes caused by graphics card all the way to RAM and Motherboard issues.

    Freaked out, I did a hardware checkup with my MBP original disks. No problems.

    Still my macbook would freeze every time I would join a network.

    So I clean installed Leopard. All was well... I guess... I don't know... So I loaded all my tons of files and all was still well...
    I synchronize my computer with Mobile me.
    It was when I synchronized my mobile me preferences, bookmarks, keychains, mailboxes, calendars, etc. when I started with the freeze ups again. Now I would get freeze ups more often. After joining a network and 5 minutes after.

    So, I was forced to flush again my OS and clean install Leopard. This time I have not synchronized Mobile Me yet. Did I catched a trojan? Malware? If it's trapped in Mobile me, What do I do?

    Thanks!
     
  4. gusanitoverde thread starter macrumors 6502

    gusanitoverde

    Joined:
    Jun 12, 2003
    Location:
    Northern California
    #4
    Reset Mobile me Sync items...

    Freeze up joining a wireless network in a hotel room.

    Latest data from system profiler:

    Aug 12 21:44:44-macbook-pro-17 mDNSResponder[22]: KQ SSLHandshake failed: -9806
    Aug 12 21:44:54: --- last message repeated 2 times ---
    Aug 12 21:44:54-macbook-pro-17 aosnotifyd[111]: Stream:streamCallback - an error occurred on CFReadStream: Operation could not be completed. Operation timed out
    Aug 12 21:45:59-macbook-pro-17 mDNSResponder[22]: KQ SSLHandshake failed: -9806
     
  5. gusanitoverde thread starter macrumors 6502

    gusanitoverde

    Joined:
    Jun 12, 2003
    Location:
    Northern California
    #5
    Went to Apple Store.

    Scratching their heads. Could not figure out how the OS could crash when switching wireless networks. Happened 3 times in front of the Genius. I called Apple Care. They don't know either. Found articles in the apple forums about this subject.

    I am not alone.

    They told me it was hardware related. I did not believe them, since I have Vista in bootcamp and its running perfectly. No crashes.

    It's MAC OS X!!!


    Now, here is another interesting message I made to recover from the console at the time of the crash:

    Aug 15 02:09:37 localhost mDNSResponder[22]: Couldn't read user-specified Computer Name; using default “MacBookPro-000000000000” instead
    Aug 15 02:09:37 localhost mDNSResponder[22]: Couldn't read user-specified local hostname; using default “MacBookPro-000000000000.local” instead
    Aug 15 02:09:37 localhost mDNSResponder[22]: User updated Computer Name from MacBookPro-0017F2CDBD9F to MacBookPro-000000000000
    Aug 15 02:09:37 localhost mDNSResponder[22]: User updated Local Hostname from MacBookPro-0017F2CDBD9F to MacBookPro-000000000000
    Aug 15 02:09:37 localhost com.embraceware.awaken[756]: Sat Aug 15 02:09:37 localhost com.embraceware.awaken[756] <Info>: Starting up
    Aug 15 02:09:37 localhost com.embraceware.awaken[756]: Sat Aug 15 02:09:37 localhost com.embraceware.awaken[756] <Debug>: Request started
    Aug 15 02:09:37 localhost com.embraceware.awaken[756]: Sat Aug 15 02:09:37 localhost com.embraceware.awaken[756] <Debug>: Command callback succeeded
    Aug 15 02:09:37 localhost kernel[0]: hibernate image path: /var/vm/sleepimage
    Aug 15 02:09:37 localhost kernel[0]: sizeof(IOHibernateImageHeader) == 512
    Aug 15 02:09:37 localhost AwakenHelper[156]: {\n SchedulePowerEventResult = "AWAKEN TOOL ERROR";\n "com.embraceware.awaken.error" = 0;\n}
    Aug 15 02:09:37 localhost kernel[0]: Opened file /var/vm/sleepimage, size 3221225472, partition base 0xc805000, maxio 400000
    Aug 15 02:09:37 localhost kernel[0]: hibernate image major 14, minor 2, blocksize 512, pollers 4
    Aug 15 02:09:37 localhost kernel[0]: hibernate_alloc_pages flags 00000000, gobbling 0 pages
    Aug 15 02:09:37 localhost com.embraceware.awaken[756]: Sat Aug 15 02:09:37 localhost com.embraceware.awaken[756] <Debug>: Request finished
    Aug 15 02:09:37 localhost com.embraceware.awaken[756]: Sat Aug 15 02:09:37 localhost com.embraceware.awaken[756] <Debug>: Request started
    Aug 15 02:09:37 localhost com.embraceware.awaken[756]: Sat Aug 15 02:09:37 localhost com.embraceware.awaken[756] <Debug>: Command callback succeeded
    Aug 15 02:09:37 localhost com.embraceware.awaken[756]: Sat Aug 15 02:09:37 localhost com.embraceware.awaken[756] <Debug>: Request finished
    Aug 15 02:09:38 localhost kernel[0]: AirPort: Link Down on en1
    Aug 15 02:09:38 localhost kernel[0]: vmnet: bridge-en1: interface en is going DOWN
    Aug 15 02:09:39 localhost kernel[0]: AppleYukon2: 00000000,3501b000 sky2 - HardwareNotResponding, marking offline
    Aug 15 02:09:39 localhost kernel[0]: AppleYukon2: 00000000,00000000 skqueue - SkEventDispatcher - ignoring event queue, hardware is not responding
    Aug 15 02:09:39 localhost kernel[0]: vmmon: powerStateDidChange flags=0x4 (state 2)
    Aug 15 02:09:39 localhost kernel[0]: System SafeSleep
    Aug 15 02:10:10 localhost kernel[0]: hibernate_page_list_setall start
    Aug 15 02:10:10 localhost mDNSResponder[22]: Couldn't read user-specified Computer Name; using default “MacBookPro-000000000000” instead
    Aug 15 02:10:10 localhost kernel[0]: hibernate_page_list_setall time: 165 ms
    Aug 15 02:10:10 localhost kernel[0]: pages 320952, wire 70892, act 60788, inact 2, spec 4, zf 0, throt 1681, could discard act 42837 inact 43194 purgeable 1722 spec 99832
    Aug 15 02:10:10 localhost kernel[0]: hibernate_page_list_setall found pageCount 133367
    Aug 15 02:10:10 localhost kernel[0]: IOHibernatePollerOpen, ml_get_interrupts_enabled 0
    Aug 15 02:10:10 localhost kernel[0]: IOHibernatePollerOpen(0)
    Aug 15 02:10:10 localhost kernel[0]: writing 132545 pages
    Aug 15 02:10:10 localhost kernel[0]: image1Size 128361472
    Aug 15 02:10:10 localhost kernel[0]: all time: 4808 ms, comp time: 895 ms, deco time: 0 ms,
    Aug 15 02:10:10 localhost kernel[0]: image 255224832, uncompressed 542904320 (132545), compressed 251407904 (46%), sum1 aea966a4, sum2 7cfce4a5
    Aug 15 02:10:10 localhost kernel[0]: hibernate_write_image done(0)
    Aug 15 02:10:10 localhost mDNSResponder[22]: Couldn't read user-specified local hostname; using default “MacBookPro-000000000000.local” instead
    Aug 15 02:10:10 localhost kernel[0]: sleep
    Aug 15 02:10:10 localhost kernel[0]: Wake reason = EC LID0
    Aug 15 02:10:10 localhost kernel[0]: System Wake
    Aug 15 02:10:10 localhost vmnet-bridge[102]: Examining network configuration.
    Aug 15 02:10:10 localhost kernel[0]: vmmon: powerStateDidChange flags=0x82 (state 4)
    Aug 15 02:10:10 localhost kernel[0]: Previous Sleep Cause: 0
    Aug 15 02:10:10 localhost kernel[0]: vmnet: VMNetDisconnect called for port 0xab0d900
    Aug 15 02:10:10 localhost vmnet-bridge[102]: Turning off bridge for: en1
    Aug 15 02:10:10 localhost kernel[0]: vmnet: bridge-en1: filter detached
    Aug 15 02:10:10 localhost kernel[0]: vmnet: bridge-en1: down
    Aug 15 02:10:10 localhost kernel[0]: vmnet: bridge-en1: detached
    Aug 15 02:10:10 localhost kernel[0]: vmnet: Freeing hub at 0x6a0b800.
    Aug 15 02:10:10 localhost aosnotifyd[163]: Stream:streamCallback - an error occurred on CFReadStream: Operation could not be completed. Socket is not connected
    Aug 15 02:10:10 localhost mDNSResponder[22]: Couldn't read user-specified Computer Name; using default “MacBookPro-0017F2CDBD9F” instead
    Aug 15 02:10:10 localhost mDNSResponder[22]: Couldn't read user-specified local hostname; using default “MacBookPro-0017F2CDBD9F.local” instead
    Aug 15 02:10:10 localhost mDNSResponder[22]: User updated Computer Name from MacBookPro-000000000000 to MacBookPro-0017F2CDBD9F
    Aug 15 02:10:10 localhost mDNSResponder[22]: User updated Local Hostname from MacBookPro-000000000000 to MacBookPro-0017F2CDBD9F
    Aug 15 02:10:11 localhost kernel[0]: 11D beacon causing regdomain change to CC 840
    Aug 15 02:10:11 localhost kernel[0]: en1: 802.11d country code set to 'US'.
    Aug 15 02:10:11 localhost kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
    Aug 15 02:10:12 localhost kernel[0]: AirPort: Link Up on en1
    Aug 15 02:10:12 localhost vmnet-bridge[102]: Examining network configuration.
    Aug 15 02:10:12 localhost vmnet-bridge[102]: Intf: en1
    Aug 15 02:10:12 localhost kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0xab0cf00.
    Aug 15 02:10:12 localhost vmnet-bridge[102]: Turning on bridge for: en1
    Aug 15 02:10:12 localhost kernel[0]: vmnet: VMNetConnect: returning port 0xab0cf00
    Aug 15 02:10:12 localhost kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
    Aug 15 02:10:12 localhost kernel[0]: vmnet: Allocated hub 0x6a0b800 for hubNum 0.
    Aug 15 02:10:12 localhost kernel[0]: vmnet: VMNET_SO_BINDTOHUB: port: paddr 00:50:56:ff:2c:da
    Aug 15 02:10:12 localhost kernel[0]: vmnet: Hub 0
    Aug 15 02:10:12 localhost kernel[0]: vmnet: Port 0
    Aug 15 02:10:12 localhost kernel[0]: vmnet: bridge-en1: got dev 0x5bf2404
    Aug 15 02:10:12 localhost kernel[0]: vmnet: bridge-en1: wireless interface detected.
    Aug 15 02:10:12 localhost kernel[0]: vmnet: bridge-en1: up
    Aug 15 02:10:12 localhost kernel[0]: vmnet: bridge-en1: attached
    Aug 15 02:10:12 localhost kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0xab0cf00.
    Aug 15 02:10:12 localhost mDNSResponder[22]: Couldn't read user-specified Computer Name; using default “MacBookPro-0017F2CDBD9F” instead
    Aug 15 02:10:12 localhost mDNSResponder[22]: Couldn't read user-specified local hostname; using default “MacBookPro-0017F2CDBD9F.local” instead
    Aug 15 02:10:12 localhost mDNSResponder[22]: Couldn't read user-specified Computer Name; using default “MacBookPro-0017F2CDBD9F” instead
    Aug 15 02:10:12 localhost mDNSResponder[22]: Couldn't read user-specified local hostname; using default “MacBookPro-0017F2CDBD9F.local” instead
    Aug 15 02:10:13 localhost mDNSResponder[22]: Double NAT (external NAT gateway address 192.168.1.64 is also a private RFC 1918 address)
    Aug 15 02:10:15 localhost mDNSResponder[22]: Couldn't read user-specified Computer Name; using default “MacBookPro-0017F2CDBD9F” instead
    Aug 15 02:10:15 localhost mDNSResponder[22]: Couldn't read user-specified local hostname; using default “MacBookPro-0017F2CDBD9F.local” instead


    Anyone has any ideas???
     
  6. gusanitoverde thread starter macrumors 6502

    gusanitoverde

    Joined:
    Jun 12, 2003
    Location:
    Northern California
    #6
    Fixed

    Update 10.5.8 had the issue. A bad update when the Mac did it on its own. I needed to download the combo update and apply it manually. My MBP is back to normal!
     
  7. MKSinSA macrumors regular

    MKSinSA

    Joined:
    Aug 1, 2009
    Location:
    Alamo City, Lone Star State
    #7
    Way to push through

    Glad you're back on track. Cheers! :cool:
     
  8. ChrisMcD macrumors newbie

    Joined:
    Dec 28, 2006
    Location:
    Harrogate
    #8
    I suspect Airport

    My MBP takes up to 20 seconds to connect via Airport when starting from sleep overnight.

    Any attempt to speed it up simply makes Airport hang and means that I have to force a restart.

    10.5.8 seems to have reduced the problem, but it still occurs.

    So, now I simply wait patiently for the 'black' radar waves every morning reciting 'insanely great' to myself.
     
  9. gusanitoverde thread starter macrumors 6502

    gusanitoverde

    Joined:
    Jun 12, 2003
    Location:
    Northern California
    #9
    Thank you MKSinSA!!!

    I had suffered so much with this.

    ChrisMcD, why don't you try to manually reinstall the update? I hope you get better results...
     
  10. gusanitoverde thread starter macrumors 6502

    gusanitoverde

    Joined:
    Jun 12, 2003
    Location:
    Northern California
    #10
    THE FREEZES are back!!!!

    I am disheartened. It is a known issue all over, but so scattered that there is not enough weight for Apple to fix it?

    I highly doubt it is a hardware issue.

    I did memory test, all is well. Clean installed the OS for the 4th time.

    Snow leopard arrives today. Hopefully that will fix it.


    :( SO sad...
     
  11. gusanitoverde thread starter macrumors 6502

    gusanitoverde

    Joined:
    Jun 12, 2003
    Location:
    Northern California
    #11
    No more freezes... at the moment.

    Would it be possible that Snow Leopard did fix something?

    I will take my laptop to places today and will enter wireless networks...

    See if it freezes...

    :confused:
     

Share This Page