Kernel Panic on El Capitan (Broadwell CPU)

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
cedric108
Posts: 2
Joined: 4. Oct 2015, 15:30

Kernel Panic on El Capitan (Broadwell CPU)

Post by cedric108 »

Hello,

I experienced 5 kernel panics yesterday in 4 hours, while simulating a virtual network with GNS3 and 4 Linux VMs (Slitaz distribution, VB 5.0.4 and 5.0.6).
I was running El Capitan (build 15A284) on the latest MacBook Pro 13 Retina (Broadwell CPU).

I will try to be as detailed as possible.

----

Panic Rapport 1: VB 5.0.4

Code: Select all

Sat Oct  3 20:16:18 2015

*** Panic Report ***
panic(cpu 1 caller 0xffffff80077d6a9a): Kernel trap at 0xffffff8007c3cedc, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x0000000000000089, CR3: 0x000000044ebcd107, CR4: 0x00000000003627e0
RAX: 0x0000000000000039, RBX: 0xffffff802cabd3c0, RCX: 0x0000000000000001, RDX: 0x00000000ffffffff
RSP: 0xffffff91faacb970, RBP: 0xffffff91faacb980, RSI: 0x0000000000000000, RDI: 0xffffff802f3d2c40
R8:  0x0000000000000001, R9:  0xffffff8031c6d380, R10: 0x0000000000000000, R11: 0x0000000000000000
R12: 0x0000000000000004, R13: 0xffffff8035974000, R14: 0x0000000000000000, R15: 0xffffff91faacbeb0
RFL: 0x0000000000050246, RIP: 0xffffff8007c3cedc, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000000000089, Error code: 0x0000000000000000, Fault CPU: 0x1, PL: 0

Backtrace (CPU 1), Frame : Return Address
0xffffff91faacb600 : 0xffffff80076e5357 
0xffffff91faacb680 : 0xffffff80077d6a9a 
0xffffff91faacb860 : 0xffffff80077f4093 
0xffffff91faacb880 : 0xffffff8007c3cedc 
0xffffff91faacb980 : 0xffffff7f8a1e096b 
0xffffff91faacb9c0 : 0xffffff7f8a1741f6 
0xffffff91faacb9f0 : 0xffffff7f8a165da8 
0xffffff91faacbaa0 : 0xffffff7f8a173e34 
0xffffff91faacbb40 : 0xffffff7f8a1740ec 
0xffffff91faacbb60 : 0xffffff800793fe92 
0xffffff91faacbba0 : 0xffffff800792df7e 
0xffffff91faacbc30 : 0xffffff8007922faa 
0xffffff91faacbe20 : 0xffffff8007b8a11b 
0xffffff91faacbe50 : 0xffffff8007bcae7d 
0xffffff91faacbf60 : 0xffffff8007c2ace1 
0xffffff91faacbfb0 : 0xffffff80077f4896 
      Kernel Extensions in backtrace:
         org.virtualbox.kext.VBoxDrv(5.0.4)[12E71258-55C7-3F50-873E-0A6026F04E7E]@0xffffff7f8a15f000->0xffffff7f8a1befff
         com.apple.driver.IOBluetoothHIDDriver(4.4f4)[15D8F318-F67A-3FE4-AEF5-0539C621C5DE]@0xffffff7f8a1db000->0xffffff7f8a1ecfff
            dependency: com.apple.iokit.IOHIDFamily(2.0.0)[353AFBA9-8775-34E3-BF8B-40D7AD2C500A]@0xffffff7f88581000
            dependency: com.apple.iokit.IOBluetoothFamily(4.4.0f4)[C3AABC55-532C-3C00-BA10-6DAA0FF4F681]@0xffffff7f88a68000

BSD process name corresponding to current thread: VirtualBoxVM
Panic Report 2: This one is quite interesting, I got another KP (graphic issue), while rebooting the computer after the first KP. I assume it wasn't a coincidence. And by the way, I was using two external displays before the fifth panic.

Code: Select all

Sat Oct  3 20:16:48 2015

*** Panic Report ***
panic(cpu 0 caller 0xffffff8002dd6a9a): Kernel trap at 0xffffff7f8517905e, type 13=general protection, registers:
CR0: 0x0000000080010033, CR2: 0x0000000112fcfac0, CR3: 0x00000004487b201d, CR4: 0x00000000003627e0
RAX: 0x280f00452c58402d, RBX: 0x00000000e00002bc, RCX: 0x00000000000003fe, RDX: 0x000000000000000a
RSP: 0xffffff91f02e37c0, RBP: 0xffffff91f02e3800, RSI: 0x0000000000000002, RDI: 0xffffff81a2219000
R8:  0xffffff8026d0b600, R9:  0xffffff91f02e3a00, R10: 0xffffff7f8362c8d0, R11: 0xffffff91f02e3b98
R12: 0xffffff81a2219000, R13: 0xffffff80266936c8, R14: 0xffffff81a2642000, R15: 0xffffff8026d0b600
RFL: 0x0000000000010246, RIP: 0xffffff7f8517905e, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000112fcfac0, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0

Backtrace (CPU 0), Frame : Return Address
0xffffff81c2af4c50 : 0xffffff8002ce5357 
0xffffff81c2af4cd0 : 0xffffff8002dd6a9a 
0xffffff81c2af4eb0 : 0xffffff8002df4093 
0xffffff81c2af4ed0 : 0xffffff7f8517905e 
0xffffff91f02e3800 : 0xffffff7f8518cb14 
0xffffff91f02e38a0 : 0xffffff7f8518d0cd 
0xffffff91f02e38c0 : 0xffffff80032b56ae 
0xffffff91f02e3900 : 0xffffff7f8518d138 
0xffffff91f02e3950 : 0xffffff7f85141d90 
0xffffff91f02e3970 : 0xffffff7f85141c86 
0xffffff91f02e39b0 : 0xffffff7f85141ed2 
0xffffff91f02e3a30 : 0xffffff80032b56ae 
0xffffff91f02e3a70 : 0xffffff7f855b098e 
0xffffff91f02e3ac0 : 0xffffff7f85141c86 
0xffffff91f02e3b00 : 0xffffff7f85141ed2 
0xffffff91f02e3b80 : 0xffffff7f85141627 
0xffffff91f02e3be0 : 0xffffff80032e1657 
0xffffff91f02e3d20 : 0xffffff8002da0780 
0xffffff91f02e3e30 : 0xffffff8002ce9af3 
0xffffff91f02e3e60 : 0xffffff8002ccd448 
0xffffff91f02e3ea0 : 0xffffff8002cdcfc5 
0xffffff91f02e3f10 : 0xffffff8002dc135a 
0xffffff91f02e3fb0 : 0xffffff8002df48b6 
      Kernel Extensions in backtrace:
         com.apple.AppleGraphicsDeviceControl(3.11.31)[05B2D9D7-B6CE-335F-9E70-CCB4BD29242C]@0xffffff7f85141000->0xffffff7f85146fff
         com.apple.driver.AppleIntelBDWGraphicsFramebuffer(10.0.8)[F58545E5-A6E0-31F4-92FD-8108C3740178]@0xffffff7f85147000->0xffffff7f8519cfff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[668E3DEE-F98E-3456-92D6-F4FEEA355A72]@0xffffff7f8352d000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[CBAE26D8-0ACB-3C1F-8347-FDCA67EC40B3]@0xffffff7f83c08000
            dependency: com.apple.iokit.IOAcceleratorFamily2(203.7.1)[5178DF8C-1F96-3D87-8BD4-46B996C4184A]@0xffffff7f850c7000
            dependency: com.apple.iokit.IOReportFamily(31)[00ECF188-29A2-3C48-B4DD-B155077F7B3C]@0xffffff7f83f0a000
            dependency: com.apple.AppleGraphicsDeviceControl(3.11.31)[05B2D9D7-B6CE-335F-9E70-CCB4BD29242C]@0xffffff7f85141000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[48AC8EA9-BD3C-3FDC-908D-09850215AA32]@0xffffff7f83608000
         com.apple.driver.AppleGraphicsDevicePolicy(3.7.7)[FED5C294-FFC8-3504-8F1F-CF85914A47DB]@0xffffff7f855ab000->0xffffff7f855b2fff
            dependency: com.apple.driver.AppleGraphicsControl(3.11.31)[1302F5C4-F57D-3810-9205-9803402BB462]@0xffffff7f85587000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[CBAE26D8-0ACB-3C1F-8347-FDCA67EC40B3]@0xffffff7f83c08000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[668E3DEE-F98E-3456-92D6-F4FEEA355A72]@0xffffff7f8352d000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[48AC8EA9-BD3C-3FDC-908D-09850215AA32]@0xffffff7f83608000
            dependency: com.apple.AppleGraphicsDeviceControl(3.11.31)[05B2D9D7-B6CE-335F-9E70-CCB4BD29242C]@0xffffff7f85141000

BSD process name corresponding to current thread: displaypolicyd
Panic report 3: as same as the first panic.

Code: Select all

Sat Oct  3 21:18:46 2015

*** Panic Report ***
panic(cpu 2 caller 0xffffff800afd6a9a): Kernel trap at 0xffffff800b4397da, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x000000010091a000, CR3: 0x00000002fa43d0f4, CR4: 0x00000000003627e0
RAX: 0xffffff803c5ab840, RBX: 0xffffff800b724110, RCX: 0xffffff802e3b1d00, RDX: 0x0000000000000000
RSP: 0xffffff91fa25b0e0, RBP: 0xffffff91fa25b0f0, RSI: 0xffffff800b724110, RDI: 0xffffff803c5abe00
R8:  0x0000000442400100, R9:  0x0000000000000002, R10: 0x0000000000000002, R11: 0x0000035cc30a9b03
R12: 0x00000000e00002bc, R13: 0xffffff802e2ce000, R14: 0xffffff803c5abe00, R15: 0x000000000000083d
RFL: 0x0000000000010286, RIP: 0xffffff800b4397da, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x000000010091a000, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 0

Backtrace (CPU 2), Frame : Return Address
0xffffff81eadc5df0 : 0xffffff800aee5357 
0xffffff81eadc5e70 : 0xffffff800afd6a9a 
0xffffff81eadc6050 : 0xffffff800aff4093 
0xffffff81eadc6070 : 0xffffff800b4397da 
0xffffff91fa25b0f0 : 0xffffff7f8c316376 
0xffffff91fa25b150 : 0xffffff7f8c31853a 
0xffffff91fa25b1e0 : 0xffffff800b4b8228 
0xffffff91fa25b250 : 0xffffff7f8c315f99 
0xffffff91fa25b280 : 0xffffff7f8bd7a848 
0xffffff91fa25b2f0 : 0xffffff7f8bd76dd6 
0xffffff91fa25bb30 : 0xffffff800b4b8228 
0xffffff91fa25bba0 : 0xffffff7f8bd75e42 
0xffffff91fa25bbe0 : 0xffffff800b4e1657 
0xffffff91fa25bd20 : 0xffffff800afa0780 
0xffffff91fa25be30 : 0xffffff800aee9af3 
0xffffff91fa25be60 : 0xffffff800aecd448 
0xffffff91fa25bea0 : 0xffffff800aedcfc5 
0xffffff91fa25bf10 : 0xffffff800afc135a 
0xffffff91fa25bfb0 : 0xffffff800aff48b6 
      Kernel Extensions in backtrace:
         com.apple.iokit.IOHIDFamily(2.0)[353AFBA9-8775-34E3-BF8B-40D7AD2C500A]@0xffffff7f8bd74000->0xffffff7f8bde9fff
            dependency: com.apple.driver.AppleFDEKeyStore(28.30)[D6FD5533-2362-3320-A475-DFAF27DA24CF]@0xffffff7f8bd69000
         com.apple.driver.IOBluetoothHIDDriver(4.4f4)[15D8F318-F67A-3FE4-AEF5-0539C621C5DE]@0xffffff7f8c312000->0xffffff7f8c323fff
            dependency: com.apple.iokit.IOHIDFamily(2.0.0)[353AFBA9-8775-34E3-BF8B-40D7AD2C500A]@0xffffff7f8bd74000
            dependency: com.apple.iokit.IOBluetoothFamily(4.4.0f4)[C3AABC55-532C-3C00-BA10-6DAA0FF4F681]@0xffffff7f8c242000

BSD process name corresponding to current thread: VirtualBoxVM
Panic Report 4: as same as the second panic.

Code: Select all

Sat Oct  3 21:19:16 2015

*** Panic Report ***
panic(cpu 2 caller 0xffffff8004dd6a9a): Kernel trap at 0xffffff7f8717905e, type 13=general protection, registers:
CR0: 0x0000000080010033, CR2: 0x0000000114e57000, CR3: 0x000000044b5e6043, CR4: 0x00000000003627e0
RAX: 0x07092313121f1401, RBX: 0x00000000e00002bc, RCX: 0x00000000000003fe, RDX: 0x000000000000000a
RSP: 0xffffff91f235b7c0, RBP: 0xffffff91f235b800, RSI: 0x0000000000000002, RDI: 0xffffff81a471e000
R8:  0xffffff8027af0600, R9:  0xffffff91f235ba00, R10: 0xffffff7f8562c8d0, R11: 0xffffff91f235bb98
R12: 0xffffff81a471e000, R13: 0xffffff802821a8c8, R14: 0xffffff81a4729000, R15: 0xffffff8027af0600
RFL: 0x0000000000010246, RIP: 0xffffff7f8717905e, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000114e57000, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 0

Backtrace (CPU 2), Frame : Return Address
0xffffff81e4c35df0 : 0xffffff8004ce5357 
0xffffff81e4c35e70 : 0xffffff8004dd6a9a 
0xffffff81e4c36050 : 0xffffff8004df4093 
0xffffff81e4c36070 : 0xffffff7f8717905e 
0xffffff91f235b800 : 0xffffff7f8718cb14 
0xffffff91f235b8a0 : 0xffffff7f8718d0cd 
0xffffff91f235b8c0 : 0xffffff80052b56ae 
0xffffff91f235b900 : 0xffffff7f8718d138 
0xffffff91f235b950 : 0xffffff7f87141d90 
0xffffff91f235b970 : 0xffffff7f87141c86 
0xffffff91f235b9b0 : 0xffffff7f87141ed2 
0xffffff91f235ba30 : 0xffffff80052b56ae 
0xffffff91f235ba70 : 0xffffff7f875b098e 
0xffffff91f235bac0 : 0xffffff7f87141c86 
0xffffff91f235bb00 : 0xffffff7f87141ed2 
0xffffff91f235bb80 : 0xffffff7f87141627 
0xffffff91f235bbe0 : 0xffffff80052e1657 
0xffffff91f235bd20 : 0xffffff8004da0780 
0xffffff91f235be30 : 0xffffff8004ce9af3 
0xffffff91f235be60 : 0xffffff8004ccd448 
0xffffff91f235bea0 : 0xffffff8004cdcfc5 
0xffffff91f235bf10 : 0xffffff8004dc135a 
0xffffff91f235bfb0 : 0xffffff8004df48b6 
      Kernel Extensions in backtrace:
         com.apple.AppleGraphicsDeviceControl(3.11.31)[05B2D9D7-B6CE-335F-9E70-CCB4BD29242C]@0xffffff7f87141000->0xffffff7f87146fff
         com.apple.driver.AppleIntelBDWGraphicsFramebuffer(10.0.8)[F58545E5-A6E0-31F4-92FD-8108C3740178]@0xffffff7f87147000->0xffffff7f8719cfff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[668E3DEE-F98E-3456-92D6-F4FEEA355A72]@0xffffff7f8552d000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[CBAE26D8-0ACB-3C1F-8347-FDCA67EC40B3]@0xffffff7f85c08000
            dependency: com.apple.iokit.IOAcceleratorFamily2(203.7.1)[5178DF8C-1F96-3D87-8BD4-46B996C4184A]@0xffffff7f870c7000
            dependency: com.apple.iokit.IOReportFamily(31)[00ECF188-29A2-3C48-B4DD-B155077F7B3C]@0xffffff7f85f0a000
            dependency: com.apple.AppleGraphicsDeviceControl(3.11.31)[05B2D9D7-B6CE-335F-9E70-CCB4BD29242C]@0xffffff7f87141000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[48AC8EA9-BD3C-3FDC-908D-09850215AA32]@0xffffff7f85608000
         com.apple.driver.AppleGraphicsDevicePolicy(3.7.7)[FED5C294-FFC8-3504-8F1F-CF85914A47DB]@0xffffff7f875ab000->0xffffff7f875b2fff
            dependency: com.apple.driver.AppleGraphicsControl(3.11.31)[1302F5C4-F57D-3810-9205-9803402BB462]@0xffffff7f87587000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[CBAE26D8-0ACB-3C1F-8347-FDCA67EC40B3]@0xffffff7f85c08000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[668E3DEE-F98E-3456-92D6-F4FEEA355A72]@0xffffff7f8552d000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[48AC8EA9-BD3C-3FDC-908D-09850215AA32]@0xffffff7f85608000
            dependency: com.apple.AppleGraphicsDeviceControl(3.11.31)[05B2D9D7-B6CE-335F-9E70-CCB4BD29242C]@0xffffff7f87141000

BSD process name corresponding to current thread: displaypolicyd
Panic Report 5: No longer 5.0.4, I was using 5.0.6 and one external monitor this time, this panic was not followed by another one.

Code: Select all

Sat Oct  3 23:05:14 2015

*** Panic Report ***
panic(cpu 1 caller 0xffffff800bbd6a9a): Kernel trap at 0xffffff800c03cedc, type 13=general protection, registers:
CR0: 0x0000000080010033, CR2: 0x0000000100747000, CR3: 0x00000004018ab0b9, CR4: 0x00000000003627e0
RAX: 0xdeadbeef00000002, RBX: 0xffffff802e161e80, RCX: 0x0000000000000001, RDX: 0x00000000ffffffff
RSP: 0xffffff91ffd53970, RBP: 0xffffff91ffd53980, RSI: 0x0000000000000000, RDI: 0xffffff803e54ef00
R8:  0x0000000000000001, R9:  0xffffff802da19980, R10: 0x0000000000000000, R11: 0x0000000000000000
R12: 0x0000000000000004, R13: 0xffffff802e5cd800, R14: 0x0000000000000000, R15: 0xffffff91ffd53eb0
RFL: 0x0000000000050246, RIP: 0xffffff800c03cedc, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000100747000, Error code: 0x0000000000000000, Fault CPU: 0x1, PL: 0

Backtrace (CPU 1), Frame : Return Address
0xffffff81eb8eddf0 : 0xffffff800bae5357 
0xffffff81eb8ede70 : 0xffffff800bbd6a9a 
0xffffff81eb8ee050 : 0xffffff800bbf4093 
0xffffff81eb8ee070 : 0xffffff800c03cedc 
0xffffff91ffd53980 : 0xffffff7f8cf1796b 
0xffffff91ffd539c0 : 0xffffff7f8e55a216 
0xffffff91ffd539f0 : 0xffffff7f8e54be08 
0xffffff91ffd53aa0 : 0xffffff7f8e559e54 
0xffffff91ffd53b40 : 0xffffff7f8e55a10c 
0xffffff91ffd53b60 : 0xffffff800bd3fe92 
0xffffff91ffd53ba0 : 0xffffff800bd2df7e 
0xffffff91ffd53c30 : 0xffffff800bd22faa 
0xffffff91ffd53e20 : 0xffffff800bf8a11b 
0xffffff91ffd53e50 : 0xffffff800bfcae7d 
0xffffff91ffd53f60 : 0xffffff800c02ace1 
0xffffff91ffd53fb0 : 0xffffff800bbf4896 
      Kernel Extensions in backtrace:
         com.apple.driver.IOBluetoothHIDDriver(4.4f4)[15D8F318-F67A-3FE4-AEF5-0539C621C5DE]@0xffffff7f8cf12000->0xffffff7f8cf23fff
            dependency: com.apple.iokit.IOHIDFamily(2.0.0)[353AFBA9-8775-34E3-BF8B-40D7AD2C500A]@0xffffff7f8c974000
            dependency: com.apple.iokit.IOBluetoothFamily(4.4.0f4)[C3AABC55-532C-3C00-BA10-6DAA0FF4F681]@0xffffff7f8ce42000
         org.virtualbox.kext.VBoxDrv(5.0.6)[FB8B8CAC-638F-3853-9CF3-5A0229B47B68]@0xffffff7f8e546000->0xffffff7f8e5a4fff

BSD process name corresponding to current thread: VirtualBoxVM
Did this also happen to anyone else?

Thanks in advance for any help.
ishan
Posts: 2
Joined: 5. Oct 2015, 15:12

Re: Kernel Panic on El Capitan (Broadwell CPU)

Post by ishan »

Hi,

I frequently get kernel panics on El capitan (used to get on Yosemite too) when launching VMs through vagrant. My report:

Code: Select all

*** Panic Report ***
panic(cpu 2 caller 0xffffff800bdd6a9a): Kernel trap at 0xffffff913d65b683, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000108f0c5e0, CR3: 0x0000000051b0f10a, CR4: 0x00000000003627e0
RAX: 0x00000000000002c0, RBX: 0x0000000000000000, RCX: 0xffffff9118560f6f, RDX: 0x000000000000002c
RSP: 0xffffff9118560f48, RBP: 0xffffff9118560f50, RSI: 0x0000000000000001, RDI: 0x0000000000000016
R8:  0x000000000000002c, R9:  0x0000000108f0c5e0, R10: 0x0000000000000000, R11: 0x0000000108f0c320
R12: 0xffffff913d771000, R13: 0xffffff913d771000, R14: 0xffffff7f8e7d74c0, R15: 0xffffff9118560fc0
RFL: 0x0000000000010206, RIP: 0xffffff913d65b683, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000108f0c5e0, Error code: 0x0000000000000001, Fault CPU: 0x2 SMAP fault, PL: 0

Backtrace (CPU 2), Frame : Return Address
0xffffff9118560bd0 : 0xffffff800bce5357 
0xffffff9118560c50 : 0xffffff800bdd6a9a 
0xffffff9118560e30 : 0xffffff800bdf4093 
0xffffff9118560e50 : 0xffffff913d65b683 
0xffffff9118560f50 : 0xffffff913d63b584 
0xffffff9118560f80 : 0xffffff913d659fd5 
0xffffff9118560fb0 : 0xffffff913d6ec73d 
0xffffff911851b9d0 : 0xffffff913d65a25d 
0xffffff911851ba10 : 0xffffff7f8e79faec 
0xffffff911851bab0 : 0xffffff7f8e7abfc0 
0xffffff911851bb40 : 0xffffff7f8e7ac1d3 
0xffffff911851bb60 : 0xffffff800bf3fe92 
0xffffff911851bba0 : 0xffffff800bf2df7e 
0xffffff911851bc30 : 0xffffff800bf22faa 
0xffffff911851be20 : 0xffffff800c18a11b 
0xffffff911851be50 : 0xffffff800c1cae7d 
0xffffff911851bf60 : 0xffffff800c22ace1 
0xffffff911851bfb0 : 0xffffff800bdf4896 
      Kernel Extensions in backtrace:
         org.virtualbox.kext.VBoxDrv(5.0)[55D40AA5-3490-3244-8A23-D03366A3CBFB]@0xffffff7f8e799000->0xffffff7f8e7f6fff
Would be great if anyone here could help with figuring this out.

Thanks,
Ishan.
michaln
Oracle Corporation
Posts: 2973
Joined: 19. Dec 2007, 15:45
Primary OS: MS Windows 7
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Any and all
Contact:

Re: Kernel Panic on El Capitan (Broadwell CPU)

Post by michaln »

ishan wrote:Would be great if anyone here could help with figuring this out.
It might help if you provided a VBox.log.

But do you have some reason to think that this is in any way related to the OP's problem, or do you just assume that two OS X panics must be the same problem?
cedric108
Posts: 2
Joined: 4. Oct 2015, 15:30

Re: Kernel Panic on El Capitan (Broadwell CPU)

Post by cedric108 »

michaln wrote:
ishan wrote:Would be great if anyone here could help with figuring this out.
It might help if you provided a VBox.log.

But do you have some reason to think that this is in any way related to the OP's problem, or do you just assume that two OS X panics must be the same problem?
Hi,

There are 4 log files for each machine. I can't upload all of them, the attached log was created at 20h15 and I got a kernel panic at 20h16!

And these log files were uploaded on Google Drive.
https://drive.google.com/folderview?id= ... sp=sharing

Hope these informations can help you, the kernel panic is really annoying. Thank you for your help.
Attachments
VBox.log
(116.47 KiB) Downloaded 17 times
ishan
Posts: 2
Joined: 5. Oct 2015, 15:12

Re: Kernel Panic on El Capitan (Broadwell CPU)

Post by ishan »

michaln wrote:
ishan wrote:Would be great if anyone here could help with figuring this out.
It might help if you provided a VBox.log.

But do you have some reason to think that this is in any way related to the OP's problem, or do you just assume that two OS X panics must be the same problem?
Shall I open a new thread or upload virtualbox logs here?

I assumed the issues were similar because my log has several identical things.
Kieran Hall
Posts: 1
Joined: 14. Oct 2015, 14:27

Re: Kernel Panic on El Capitan (Broadwell CPU)

Post by Kieran Hall »

I have similar issues running a CentOS VM on 5.0.6. My host is OSX El Captain on a Broadwell Core i7 machine.

I also note that the VBoxClient just runs in the background consuming 94% of the VM's provisioned CPU.
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Kernel Panic on El Capitan (Broadwell CPU)

Post by socratis »

Kieran Hall wrote:I have similar issues
And apparently you did not read the guidance provided just a couple of posts before your post about posting the log files...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply