Skip to content

Instantly share code, notes, and snippets.

@bps
Created April 24, 2009 19:48
Show Gist options
  • Save bps/101311 to your computer and use it in GitHub Desktop.
Save bps/101311 to your computer and use it in GitHub Desktop.
Problems with my new 2 week old Unibody MacBook Pro
Unibody MacBook Pro acceptance
- Hard freezes
- No cursor movement
- Audio short loop (like stuck record)
- Only happens (so far) with 4GB RAM
- Ran for 3-4 days with stock 2GB RAM
- Ran for 10 days with 4GB RAM
- Crash on day 2
- Crashes on days 6, 7, 8, 10
- Running since 4/22 evening on 3GB RAM, no freeze yet
- Requires hard reset
- Anecdotal evidence suggests a problem with 4GB RAM
- Apple - Support - Discussions - Random Freezing ...
<http://discussions.apple.com/thread.jspa?threadID=1767718>
- Apple - Support - Discussions - Random Freezing - Continued
...
<http://discussions.apple.com/thread.jspa?threadID=1966105>
- Bluetooth devices cease working and cause crash
- Keyboard (new style Apple Bluetooth wireless keyboard) and mouse
(Logitech) ceased working
- Built-in keyboard and trackpad ceased working temporarily
- When built-in input worked again, Bluetooth peripherals were
still listed in the menu bar menu
- Trying to open Bluetooth pref pane failed
* Log at the relevant time
- Tried to close lid to force sleep (hoping for HID reset)
- Snoring light came on, but stayed bright
- Opening lid did not revive OS X
- Pinging the machine not possible
- Forced to hold power button for hard reset
- Only seen once so far, but support forum searches are not
promising
- UI freeze during "detect displays"
- Manually triggered "detect displays" due to issue below (4/26, c.
20:20)
- All UI froze, no graphics updates, no input via builtin or
external keyboard or mouse
- Was able to SSH in
- Found WindowServer at 100% CPU
- Found Terminal (last active app) at 100% CPU
- Was able to kill Terminal
- Found aslmanager at 100% CPU for a while, but it calmed down
on its own
- Would not respond to sudo reboot
- Screen dimmed at normal interval
- Had to reset via holding the power button
- Wifi drops large percentage of packets with full bars of reception
- AP (Airport Extreme c. 2003, 802.11g) mounted in basement ceiling
- Wifi works fine in family room on first floor
- In office (~15 ft. above family room), wifi drops packets at
about 30-40% rate with ping times to AP ranging from tens of ms
to 5 seconds, and a ping time standard deviation as high as 2
seconds
- Previous MacBook Pro had no trouble at all
- Very marginal improvement after turning on "interference
robustness" in AP
- Ping times improve vastly with external Firewire disk powered off
- Still losing ~5% packets and ping stats
1.607/19.083/633.947/71.655 ms
- After powering on external disk (yet not connecting), losing
17% packets and ping stats 3.047/400.926/2611.117/504.931 ms
and 2.094/8868.973/28348.734/8237.749 ms
- Proximity?
- Switching from channel 1 (autoselected) to channel 6 on the AP
seems to vastly improve things
- 6697 packets transmitted, 6689 packets received, 0% packet
loss
round-trip min/avg/max/stddev = 0.745/15.552/141.925/14.850 ms
- iPhone can't stay connected to iTunes
- Disappears from source list during sync without complaint
- Sometimes iPhone thinks it's still syncing (but not charging)
- Has happened on 2 separate occasions
- But have also had successful syncs
- Will not detect Cinema Display automatically
- Using a Mini Displayport to DVI adapter
- Main display darkens (as if doing the automatic display
detection) and returns without using the Cinema Display
- Manually pressing the "detect displays" button gets the display
detected and working properly
- No issues with automatic detection of Princeton VL2017 via
adapter at work
- Battery does not charge when plugged in
- Plug in power adapter, no LED lit
- OS X claims power source is adapter, but battery is not charging
- Has only happened rarely (twice?)
- Fixed by unplugging and re-plugging
- Left fan makes odd noise
- The left fan makes a strange noise
- Exacerbated w/high fan RPM
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment