15" 2.53Ghz Core 2 Duo MacBook Pro - kernel panics about every 5 minutes after Lion upgrade

Question

Level 1

0 points

15" 2.53Ghz Core 2 Duo MacBook Pro - kernel panics about every 5 minutes after Lion upgrade

I just recently upgraded to Lion and since then have been plagued as it seems many users have been with kernel panics after the upgrade. Have repaired disk permissions, analyzed the drive with diskwarrior, swapped out the memory, unplugged all external devices, and shut down all unnecessary applications to no avail. Anyone have any idea when this is going to be fixed by Apple? My laptop is pretty much useless and formatting and going back to Snow Leopard is a rediculous option since I really do not want to spend a day or more reinstalling all of my applications just to get to a workable situation until Apple gets their "stuff" together. C'mon Apple - we expect more from you than this!

MacBook Pro, Mac OS X (10.7)

Posted on Aug 10, 2011 1:27 PM

Reply

Answer 1

Kappy

Level 10

361,741 points

Aug 10, 2011 1:33 PM in response to daZZee

Kernel panics are usually the result of something you have installed that is not compatible. However, until we see a panic log there's not much we can do to help other than recommend you do a clean install of Lion.

Mac OS X- How to log a kernel panic

Post the panic log here. Meanwhile here are two things you can try. Disconnect all your external peripherals:

Create a new user account. Log into the new user account. Do the panics stop?
Boot into Safe Mode. Doe the panics stop while in safe mode?

Reply

Answer 2

Linc Davis

Level 10

209,547 points

Aug 10, 2011 1:40 PM in response to daZZee

Please try booting in safe mode by holding down the shift key until the Apple logo appears on the display.

Reply

Answer 3

daZZee Author

Level 1

0 points

Aug 10, 2011 1:43 PM in response to Kappy

Kernel Panic Report Below... all peripherals have been disconnected long ago...

Interval Since Last Panic Report: 35640 sec

Panics Since Last Report: 5

Anonymous UUID: B6EE69D1-8F01-4E5A-95B1-2AD58536F0E8

Wed Aug 10 15:39:01 2011

panic(cpu 0 caller 0xffffff80002c268d): Kernel trap at 0xffffff800028fe90, type 14=page fault, registers:

CR0: 0x0000000080010033, CR2: 0x0000000000000428, CR3: 0x0000000060178000, CR4: 0x0000000000000660

RAX: 0x0000000000000001, RBX: 0x00000000004d0000, RCX: 0xffffff8015b9b400, RDX: 0x0000000000047371

RSP: 0xffffff80ff1db3a0, RBP: 0xffffff80ff1db3c0, RSI: 0x00000000258f96a0, RDI: 0xffffff80055609b8

R8: 0x0000000000000000, R9: 0xffffff800de95000, R10: 0x000000000005dfff, R11: 0x0000000000000000

R12: 0xffffff80055609b8, R13: 0xffffff8007a06ca0, R14: 0xffffff8018bd9680, R15: 0x0000000000000400

RFL: 0x0000000000010206, RIP: 0xffffff800028fe90, CS: 0x0000000000000008, SS: 0x0000000000000010

CR2: 0x0000000000000428, Error code: 0x0000000000000000, Faulting CPU: 0x0

Backtrace (CPU 0), Frame : Return Address

0xffffff80ff1db060 : 0xffffff8000220702

0xffffff80ff1db0e0 : 0xffffff80002c268d

0xffffff80ff1db280 : 0xffffff80002d7a3d

0xffffff80ff1db2a0 : 0xffffff800028fe90

0xffffff80ff1db3c0 : 0xffffff8000268080

0xffffff80ff1db7c0 : 0xffffff80002683f8

0xffffff80ff1db820 : 0xffffff800056e711

0xffffff80ff1db870 : 0xffffff80002fd205

0xffffff80ff1db8c0 : 0xffffff80002fce9e

0xffffff80ff1db900 : 0xffffff80002ff296

0xffffff80ff1db990 : 0xffffff80004db54c

0xffffff80ff1dba80 : 0xffffff80004e3769

0xffffff80ff1dbc30 : 0xffffff8000316994

0xffffff80ff1dbc70 : 0xffffff80002f492a

0xffffff80ff1dbcf0 : 0xffffff80002f379c

0xffffff80ff1dbd90 : 0xffffff80002e3a9e

0xffffff80ff1dbf60 : 0xffffff80005ca198

0xffffff80ff1dbfb0 : 0xffffff80002d7f59

BSD process name corresponding to current thread: Microsoft Databa

Mac OS version:

11A511

Kernel version:

Darwin Kernel Version 11.0.0: Sat Jun 18 12:56:35 PDT 2011; root:xnu-1699.22.73~1/RELEASE_X86_64

Kernel UUID: 24CC17EB-30B0-3F6C-907F-1A9B2057AF78

System model name: MacBookPro5,4 (Mac-F22587A1)

System uptime in nanoseconds: 1203420108517

last loaded kext at 568243224289: com.apple.iokit.IOAVBFamily 1.0.0d22 (addr 0xffffff7f80792000, size 36864)

last unloaded kext at 635657744746: com.apple.iokit.IOEthernetAVBController 1.0.0d5 (addr 0xffffff7f8078d000, size 20480)

loaded kexts:

com.parallels.kext.prl_vnic 6.0 12094.676494

com.parallels.kext.prl_netbridge 6.0 12094.676494

com.parallels.kext.prl_usb_connect 6.0 12094.676494

com.parallels.kext.prl_hid_hook 6.0 12094.676494

com.parallels.kext.prl_hypervisor 6.0 12094.676494

com.apple.driver.AppleHWSensor 1.9.4d0

com.apple.driver.AppleMikeyHIDDriver 122

com.apple.driver.AudioAUUC 1.59

com.apple.driver.AppleUpstreamUserClient 3.5.9

com.apple.driver.AppleMCCSControl 1.0.24

com.apple.iokit.IOUserEthernet 1.0.0d1

com.apple.driver.AGPM 100.12.40

com.apple.driver.AppleMikeyDriver 2.1.1f11

com.apple.driver.AppleHDA 2.1.1f11

com.apple.GeForce 7.0.2

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.driver.AudioIPCDriver 1.2.0

com.apple.driver.AppleSMCLMU 2.0.1d2

com.apple.driver.SMCMotionSensor 3.0.1d2

com.apple.filesystems.autofs 3.0

com.apple.driver.ACPI_SMC_PlatformPlugin 4.7.0b2

com.apple.driver.AppleLPC 1.5.1

com.apple.driver.AppleBacklight 170.1.9

com.apple.driver.AppleUSBTCButtons 220.8

com.apple.driver.AppleUSBTCKeyboard 220.8

com.apple.driver.AppleIRController 309

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1

com.apple.BootCache 32

com.apple.driver.AppleUSBCardReader 3.0.0

com.apple.iokit.SCSITaskUserClient 3.0.0

com.apple.iokit.IOAHCIBlockStorage 2.0.0

com.apple.driver.AirPort.Brcm4331 500.20.6

com.apple.driver.AppleFWOHCI 4.8.6

com.apple.driver.AppleHPET 1.6

com.apple.driver.AppleUSBHub 4.4.0

com.apple.driver.AppleAHCIPort 2.1.8

com.apple.nvenet 2.0.17

com.apple.driver.AppleUSBOHCI 4.4.0

com.apple.driver.AppleSmartBatteryManager 161.0.0

com.apple.driver.AppleEFINVRAM 1.5.0

com.apple.driver.AppleRTC 1.4

com.apple.driver.AppleUSBEHCI 4.4.0

com.apple.driver.AppleACPIButtons 1.4

com.apple.driver.AppleSMBIOS 1.7

com.apple.driver.AppleACPIEC 1.4

com.apple.driver.AppleAPIC 1.5

com.apple.driver.AppleIntelCPUPowerManagementClient 166.0.0

com.apple.nke.applicationfirewall 3.0.30

com.apple.security.quarantine 1

com.apple.driver.AppleIntelCPUPowerManagement 166.0.0

com.apple.driver.DspFuncLib 2.1.1f11

com.apple.iokit.IOSurface 80.0

com.apple.iokit.IOBluetoothSerialManager 2.5f17

com.apple.iokit.IOSerialFamily 10.0.5

com.apple.iokit.IOAudioFamily 1.8.3fc11

com.apple.kext.OSvKernDSPLib 1.3

com.apple.nvidia.nv50hal 7.0.2

com.apple.NVDAResman 7.0.2

com.apple.kext.triggers 1.0

com.apple.iokit.IOFireWireIP 2.2.3

com.apple.driver.AppleSMBusController 1.0.10d0

com.apple.driver.AppleHDAController 2.1.1f11

com.apple.iokit.IOHDAFamily 2.1.1f11

com.apple.driver.AppleSMBusPCI 1.0.10d0

com.apple.driver.AppleSMC 3.1.1d2

com.apple.driver.IOPlatformPluginFamily 4.7.0b2

com.apple.driver.AppleBacklightExpert 1.0.3

com.apple.iokit.IONDRVSupport 2.3

com.apple.iokit.IOGraphicsFamily 2.3

com.apple.driver.BroadcomUSBBluetoothHCIController 2.5f17

com.apple.driver.AppleUSBBluetoothHCIController 2.5f17

com.apple.iokit.IOBluetoothFamily 2.5f17

com.apple.driver.AppleUSBMultitouch 220.23

com.apple.iokit.IOUSBHIDDriver 4.4.0

com.apple.iokit.IOSCSIBlockCommandsDevice 3.0.0

com.apple.iokit.IOUSBMassStorageClass 3.0.0

com.apple.driver.AppleUSBMergeNub 4.4.0

com.apple.driver.AppleUSBComposite 3.9.0

com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.0.0

com.apple.iokit.IOBDStorageFamily 1.6

com.apple.iokit.IODVDStorageFamily 1.6

com.apple.iokit.IOCDStorageFamily 1.7

com.apple.driver.XsanFilter 403

com.apple.iokit.IOAHCISerialATAPI 2.0.0

com.apple.iokit.IOSCSIArchitectureModelFamily 3.0.0

com.apple.iokit.IO80211Family 400.40

com.apple.iokit.IOFireWireFamily 4.4.3

com.apple.iokit.IOAHCIFamily 2.0.6

com.apple.iokit.IOUSBUserClient 4.4.0

com.apple.iokit.IONetworkingFamily 2.0

com.apple.driver.NVSMU 2.2.9

com.apple.driver.AppleEFIRuntime 1.5.0

com.apple.iokit.IOUSBFamily 4.4.0

com.apple.iokit.IOHIDFamily 1.7.0

com.apple.iokit.IOSMBusFamily 1.1

com.apple.security.sandbox 165

com.apple.kext.AppleMatch 1.0.0d1

com.apple.security.TMSafetyNet 7

com.apple.driver.DiskImages 326

com.apple.iokit.IOStorageFamily 1.7

com.apple.driver.AppleKeyStore 28.18

com.apple.driver.AppleACPIPlatform 1.4

com.apple.iokit.IOPCIFamily 2.6.5

com.apple.iokit.IOACPIFamily 1.4

Model: MacBookPro5,4, BootROM MBP53.00AC.B03, 2 processors, Intel Core 2 Duo, 2.53 GHz, 8 GB, SMC 1.49f2

Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB

Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353237334248312D4346382020

Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353237334248312D4346382020

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.100.98.75.6)

Bluetooth: Version 2.5.0f17, 2 service, 19 devices, 1 incoming serial ports

Network Service: AirPort, AirPort, en1

Serial ATA Device: ST9750420AS, 750.16 GB

Serial ATA Device: MATSHITADVD-R UJ-868

USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0x24400000 / 2

USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0x26500000 / 2

USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0236, 0x04600000 / 3

USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x04500000 / 2

USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06100000 / 2

USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8213, 0x06110000 / 3

Reply

Answer 4

Linc Davis

Level 10

209,547 points

Aug 10, 2011 2:02 PM in response to daZZee

Does the panic happen in safe mode?

Reply

Answer 5

Kappy

Level 10

361,741 points

Aug 10, 2011 2:10 PM in response to daZZee

There seems a problem with the Microsoft Database. Do you have Office 2004 installed or some old MS software? You might consider uninstalling whatever it is especially if the panics cease in safe mode.

Reply

Answer 6

daZZee Author

Level 1

0 points

Aug 10, 2011 2:15 PM in response to daZZee

Panics still occur under new user created and logged in. I am using Microsoft Office 2011 so I don't think that it is because it is too old.

Am waiting to test to see if it still occurs in safe mode... will be later this evening before I can report back on that though.

Thanks for the suggestions so far

Reply

Answer 7

Linc Davis

Level 10

209,547 points

Aug 10, 2011 2:28 PM in response to Kappy

Office is not kernel code and can't cause a panic.

Reply

Answer 8

Kappy

Level 10

361,741 points

Aug 10, 2011 2:35 PM in response to Linc Davis

Then why this:

BSD process name corresponding to current thread: Microsoft Databa

Reply

Answer 9

Linc Davis

Level 10

209,547 points

Aug 10, 2011 2:44 PM in response to Kappy

That's the process that was executing when the panic occurred, but it's not the cause of the panic. It is absolutely impossible for a bug in userland code to cause a panic by itself. On the other hand, it's quite possible for userland code to trigger a panic. The analogy I use is this: Suppose someone plants a bomb in your car, wired to the ignition switch. You put the key in the ignition, and the car explodes. What caused the explosion: the key, or the bomb?

Reply

Answer 10

Kappy

Level 10

361,741 points

Aug 10, 2011 2:52 PM in response to Linc Davis

Technically, the "cause" was the ignition switch because it triggered the bomb. Using that analogy one can argue that the BSD process triggered the kernel panic and, therefore, is the "cause." It's simply not the process that exploded. 🙂

Regardless, the fact that the BSD process triggered the panic or was the process that panicked, is not entriely relevant. Whatever triggered the panic may be what must be "removed" to prevent it from triggering more panics.

Booting into safe mode would indeed be helpful which is why I suggested it to begin with in the hope of at least narrowing down what may be causing the panic such as an incompatible extension. So, I think we are in general agreement with respect to trying to identify the root of the problem. Yes?

Reply

Answer 11

Linc Davis

Level 10

209,547 points

Aug 10, 2011 3:12 PM in response to Kappy

Regardless, the fact that the BSD process triggered the panic or was the process that panicked, is not entriely relevant. Whatever triggered the panic may be what must be "removed" to prevent it from triggering more panics.

That's just the point. Processes don't panic at all, ever. They crash. The kernel (which is not a process) panics. It panics because a sequence of events, usually starting with something that happens in the address space of a process, leads to a state in which the kernel doesn't have a valid instruction to execute next. The process that started that sequence of events is completely innocent. No matter how hard you try, you can't write an application that will cause a panic unless you know of a kernel-space bug to take advantage of.

Now, it might happen that a certain application is the only one that triggers a particular panic. In that case, you could work around the problem by not running that application. But the application is not at fault.

The OP is running an application that many others are also running on Lion without the same issue.

Kernel Extension Programming Topics: Deciding Whether to Create a Kernel Extension

Reply

Answer 12

Kappy

Level 10

361,741 points

Aug 10, 2011 3:22 PM in response to Linc Davis

In any event, I actually started off saying there was a possible problem arising out of the BSD process identified in the panic log. I don't thing we actually know what the OP is running since he hasn't stated that specifically. Office 2011 works fine. Office 2008 may or may not and Office 2004 definitely does not work.

We are lacking all the information needed including whether the panics cease in safe mode, so I believe we must wait until the OP provides more information.

Otherwise, I don't see that you and I are in any disagreement.

Reply

Answer 13

daZZee Author

Level 1

0 points

Aug 10, 2011 10:39 PM in response to Kappy

OK - so far tonight it seems to run without a panic under safe mode. Also - in terms of Office - it is 2011.

Reply

Answer 14

Kappy

Level 10

361,741 points

Aug 10, 2011 10:46 PM in response to daZZee

OK. That means something that is disabled in safe mode is probably causing the trouble.

Starting up into Safe Mode does several things:

It forces a directory check of the startup volume.
It loads only required kernel extensions (some of the items in /System/Library/Extensions).
It disables all fonts other than those in /System/Library/Fonts (Mac OS X v10.4 or later).
It moves to the Trash all font caches normally stored in /Library/Caches/com.apple.ATS/(uid)/, where (uid) is a user ID number such as 501 (Mac OS X v10.4 or later).
It disables all startup items and login items (Mac OS X v10.4 or later).
Mac OS X v10.5.6 or later: A Safe Boot deletes the dynamic loader shared cache at (/var/db/dyld/). A cache with issues may cause a blue screen on startup, particularly after a Software Update. Restarting normally recreates this cache.

So the next thing to do is reboot normally to see if the cache fixes helped. Otherwise, you will need to look for the third-party items disabled in safe mode as well as look for a corrupted system font (Font Book may be helpful.)

Reply

Answer 15

Linc Davis

Level 10

209,547 points

Aug 11, 2011 5:34 AM in response to daZZee

If the panics stop in safe mode, then they're caused either by Parallels or by a bug in one of the built-in kernel extensions that are disabled in that mode. Try uninstalling Parallels and rebooting as usual (not in safe mode.) There's no chance whatsoever that a corrupted font is responsible -- fonts are not kernel code and cannot cause a panic.

Reply