Opened 11 years ago
Last modified 10 years ago
#13336 new defect
MacBook Pro Retina 2014 crashes when connected to Thunderbolt display
Reported by: | Kees de Kooter | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.3.14 |
Keywords: | retina | Cc: | |
Guest type: | other | Host type: | Mac OS X |
Description
MacBook Pro Retina Mid-2014, OS X Mavericks 10.9.4 crashes with a kernel panic after it is connected to the Apple Thunderbolt Display.
Here is the head of the panic log:
Fri Aug 29 19:04:48 2014 panic(cpu 0 caller 0xffffff80162dc24e): Kernel trap at 0xffffff80162a87e3, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x00000000189d2000, CR4: 0x00000000001626e0 RAX: 0x0000000000000080, RBX: 0x0000000000000000, RCX: 0xffffff80168d0320, RDX: 0xffffff80168d01c0 RSP: 0xffffff8225723c70, RBP: 0xffffff8225723d80, RSI: 0xffffff80227b8dc8, RDI: 0xffffff80168d01c0 R8: 0x0000000000000021, R9: 0x0000000000000010, R10: 0x0000000000000001, R11: 0xffffff801622fe40 R12: 0xffffff80168d0420, R13: 0x00000000003bca45, R14: 0x0000000000000001, R15: 0x0000000000000010 RFL: 0x0000000000010202, RIP: 0xffffff80162a87e3, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x0 Backtrace (CPU 0), Frame : Return Address 0xffffff8225723900 : 0xffffff8016222f79 0xffffff8225723980 : 0xffffff80162dc24e 0xffffff8225723b50 : 0xffffff80162f3746 0xffffff8225723b70 : 0xffffff80162a87e3 0xffffff8225723d80 : 0xffffff8016681300 0xffffff8225723ef0 : 0xffffff80166e1f6f 0xffffff8225723f00 : 0xffffff801669b8cc 0xffffff8225723f20 : 0xffffff801624a20a 0xffffff8225723fb0 : 0xffffff80162d7417 BSD process name corresponding to current thread: kernel_task Mac OS version: 13E28 Kernel version: Darwin Kernel Version 13.3.0: Tue Jun 3 21:27:35 PDT 2014; root:xnu-2422.110.17~1/RELEASE_X86_64 Kernel UUID: BBFADD17-672B-35A2-9B7F-E4B12213E4B8 Kernel slide: 0x0000000016000000 Kernel text base: 0xffffff8016200000 System model name: MacBookPro11,2 (Mac-3CBD00234E554E41) System uptime in nanoseconds: 3724286466644 last loaded kext at 3687521824681: com.apple.driver.AppleIntelMCEReporter 104 (addr 0xffffff7f984cc000, size 49152) last unloaded kext at 3613279530786: com.apple.driver.AppleUSBOHCI 656.4.1 (addr 0xffffff7f9854f000, size 53248) loaded kexts: org.virtualbox.kext.VBoxNetAdp 4.3.14 org.virtualbox.kext.VBoxNetFlt 4.3.14 org.virtualbox.kext.VBoxUSB 4.3.14 org.virtualbox.kext.VBoxDrv 4.3.14 com.apple.driver.AppleIntelMCEReporter 104 com.apple.driver.AppleUSBDisplays 360.8.14 com.apple.driver.AppleUSBEHCI 660.4.0 com.apple.driver.AppleFWOHCI 5.0.2 com.apple.iokit.AppleBCM5701Ethernet
Apple Support suggested to contact VirtualBox support. If I remove VB from my machine it crashes no longer.
Change History (1)
Note:
See TracTickets
for help on using tickets.
It is an Apple problem with Thunderbolt display. A lot of complaining for this crap on their tech-support web site for the last 4 years. Still Apple do not want to fix the issue.
The issue could be mitigated (works for me and whenever I know for 99% cases, 1 crash per month is still possible) if you follow these 3 steps:
1) Choose your Mac Book pro display as a primary (In a display preferences just drag and drop system menu to MacBookPro Display image)
2) When you disconnect your Thunderbolt display - power off it from wall outlet.
3) Keep clean your USB ports on Display monitor UsbHub empty.
The problems persist still on Mavericks, Yosemite. Did not checkit it with El Capitan.