Lotsa kernel panics on OS 10.6 Snow Leopard w/ MacBook

September 21, 2009 1:54 PM

Why does my MacBook keep kernel panic'ing under 10.6? Log dumps inside!

Here's /var/log/system.log:

Sep 21 15:26:03 XXXXXX-MacBook com.vmware.launchd.vmware[43]: Sending on VNet/vmnet8/192.168.192.0
Sep 21 15:26:03 XXXXXX-MacBook com.vmware.launchd.vmware[43]: Internet Software Consortium DHCP Server 2.0
Sep 21 15:26:03 XXXXXX-MacBook com.vmware.launchd.vmware[43]: Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
Sep 21 15:26:03 XXXXXX-MacBook com.vmware.launchd.vmware[43]: All rights reserved.
Sep 21 15:26:03 XXXXXX-MacBook com.vmware.launchd.vmware[43]: Please contribute if you find this software useful.
Sep 21 15:26:03 XXXXXX-MacBook com.vmware.launchd.vmware[43]: For info, please visit http://www.isc.org/dhcp-contrib.html
Sep 21 15:26:03 XXXXXX-MacBook pcscd[56]: Non-smartcard device launched pcscd [Vendor: 0X3F0, Product: 0X6C11]
Sep 21 15:26:03 XXXXXX-MacBook com.vmware.launchd.vmware[43]: Configured subnet: 192.168.43.0
Sep 21 15:26:03 XXXXXX-MacBook com.vmware.launchd.vmware[43]: Setting vmnet-dhcp IP address: 192.168.43.254
Sep 21 15:26:03 XXXXXX-MacBook com.vmware.launchd.vmware[43]: Opened:
Sep 21 15:26:03 XXXXXX-MacBook com.vmware.launchd.vmware[43]: Recving on VNet/vmnet1/192.168.43.0
Sep 21 15:26:03 XXXXXX-MacBook com.vmware.launchd.vmware[43]: Sending on VNet/vmnet1/192.168.43.0
Sep 21 15:26:03 XXXXXX-MacBook pcscd[56]: Non-smartcard device launched pcscd [Vendor: 0X3F0, Product: 0X6C11]
Sep 21 15:26:03 XXXXXX-MacBook vmnet-bridge[91]: Starting up.
Sep 21 15:26:03 XXXXXX-MacBook vmnet-bridge[91]: Examining network configuration.
Sep 21 15:26:04: --- last message repeated 1 time ---
Sep 21 15:26:04 XXXXXX-MacBook configd[13]: network configuration changed.
Sep 21 15:26:04 XXXXXX-MacBook vmnet-bridge[91]: Intf: en1
Sep 21 15:26:04 XXXXXX-MacBook vmnet-bridge[91]: Turning on bridge for: en1
Sep 21 15:26:08 XXXXXX-MacBook com.apple.SystemStarter[21]: Starting HP IO Monitor
Sep 21 15:26:08 XXXXXX-MacBook com.apple.SystemStarter[21]: Starting HP Trap Monitor
Sep 21 15:26:09 XXXXXX-MacBook loginwindow[28]: Login Window Started Security Agent
Sep 21 15:26:09 XXXXXX-MacBook loginwindow[28]: Login Window - Returned from Security Agent
Sep 21 15:26:09 XXXXXX-MacBook loginwindow[28]: USER_PROCESS: 28 console
Sep 21 15:26:09 XXXXXX-MacBook com.apple.launchd.peruser.501[132] (com.apple.ReportCrash): Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
Sep 21 15:26:11 XXXXXX-MacBook com.apple.launchd.peruser.501[132] (com.apple.Kerberos.renew.plist[160]): Exited with exit code: 1
Sep 21 15:26:14 XXXXXX-MacBook WindowServer[59]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Sep 21 15:26:14 XXXXXX-MacBook com.apple.WindowServer[59]: Mon Sep 21 15:26:14 XXXXXX-MacBook.local WindowServer[59] : kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Sep 21 15:27:12 XXXXXX-MacBook mds[26]: (/.Spotlight-V100/Store-V1/Stores/5A30616A-1C82-4B6D-BF81-EB0086574585)(Warning) IndexStore in setAttributes:Items's transaction id 7 is too low for the current index 8. Discarding oid 0.
Sep 21 15:34:03 XXXXXX-MacBook Safari[233]: CantParseData: errno 0, euid: 501, egid: 20, pathInfo: { Target path: /Users/angela/Library/Cookies/Cookies.plist, modTime: 2009-09-21 15:20:50 -0500, size: 145536, st_uid: 501, st_mode: 100644 st_flags: 0x0 acl: none parentInfo: modTime: 2009-09-21 15:20:50 -0500 st_uid: 501, st_mode: 40755 st_flags: 0x0 acl: none}
Sep 21 15:34:27 XXXXXX-MacBook com.apple.WebKit.PluginAgent[236]: Debugger() was called!

Anything else to consider? It's happening 3-4x a day now.

posted by delladlux to technology (2 comments total)

Does this only happen when running VMware (for Windows, I guess?)
posted by rokusan at 1:59 PM on September 21

A quick Google search and I found this. The solution seems to involve fixing the permissions on your root directory:

Open "Terminal" (in your Applications > Utilities folder) and type:
sudo chown root:admin /

enter your root password when prompted.

Even if this isn't the proper fix, this command should be harmless as long as you type it correctly. I recommend copy and paste.
posted by plasticbugs at 2:10 PM on September 21