Panic occurred after kicking for more than four hours. Harshness by me included combinations such as:
- two concurrent backups of the CoreStorage encrypted JHFS+ startup volume (Time Machine to ZFS with copies=2 and compression=on on an imperfect device on FireWire, coinciding with SuperDuper! to a CoreStorage encrypted JHFS+ part of a more trusted device on the same bus)
- MacPorts building apple-gcc42 and more to that startup volume during the backups
- Windows 7 with 1 GB memory in VirtualBox writing as much and as often as possible to ZFS with compression=on on USB
- QuickTime Player with a relatively large movie (probably ~225 MB read from osxfusefs)
- Activity Monitor, Camouflage, Console, HardwareGrowler, Notes, Preview, TextExpander, TextWrangler, Wuala, System Preferences and a variety of other stuff
- Safari, which might have become sluggish under all of the above, especially when application switching or creating new tabs and windows; but the app behaved perfectly.
Flip side, the good news is that 10.8.2 with this edition of ZEVO performed exceedingly well before the panic – much more smoothly than with any previous combination.
- Code: Select all
panic(cpu 0 caller 0xffffff8005ab7bd5): Kernel trap at 0xffffff7f85fa8279, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x000000000000001d, CR3: 0x00000001441a1000, CR4: 0x0000000000000660
RAX: 0x000000000000001d, RBX: 0x000000000000001d, RCX: 0x0000000000000000, RDX: 0x0000000000000000
RSP: 0xffffff811d27bd20, RBP: 0xffffff811d27bd50, RSI: 0xffffff811d27be50, RDI: 0xffffff801bceaa30
R8: 0x0000000000000000, R9: 0x0000000000000000, R10: 0x0000000000000002, R11: 0x00007fff5fbe4770
R12: 0xffffff8019cf4000, R13: 0xffffff801bceaa30, R14: 0xffffff811d27be50, R15: 0xffffff801bceaa30
RFL: 0x0000000000010206, RIP: 0xffffff7f85fa8279, CS: 0x0000000000000008, SS: 0x0000000000000000
Fault CR2: 0x000000000000001d, Error code: 0x0000000000000000, Fault CPU: 0x0
Backtrace (CPU 0), Frame : Return Address
0xffffff811d27b9c0 : 0xffffff8005a1d626
0xffffff811d27ba30 : 0xffffff8005ab7bd5
0xffffff811d27bc00 : 0xffffff8005ace4ed
0xffffff811d27bc20 : 0xffffff7f85fa8279
0xffffff811d27bd50 : 0xffffff7f8603f9d9
0xffffff811d27be80 : 0xffffff7f86036e38
0xffffff811d27bec0 : 0xffffff8005b120af
0xffffff811d27bef0 : 0xffffff8005d40220
0xffffff811d27bfb0 : 0xffffff8005ab26b7
Kernel Extensions in backtrace:
com.getgreenbytes.filesystem.zfs(2012.9.14)[8241F82D-269B-30AD-86AB-AB7C3D520F2B]@0xffffff7f85fa5000->0xffffff7f86141fff
dependency: com.apple.iokit.IOStorageFamily(1.8)[5BA4CD36-E96D-3A9E-ADFF-A863BBD63BC7]@0xffffff7f85f78000
BSD process name corresponding to current thread: kernel_task
Boot args: -v
Mac OS version:
12C54
Kernel version:
Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
Kernel UUID: 69A5853F-375A-3EF4-9247-478FD0247333
Kernel slide: 0x0000000005800000
Kernel text base: 0xffffff8005a00000
System model name: MacBookPro5,2 (Mac-F2268EC8)
System uptime in nanoseconds: 27106418604491
last loaded kext at 334088512566: com.apple.filesystems.smbfs 1.8 (addr 0xffffff7f87fed000, size 229376)
last unloaded kext at 267799675487: com.apple.driver.AppleFileSystemDriver 3.0.1 (addr 0xffffff7f87da4000, size 8192)
Over to Wuala for the .panic file in full (plus sixty-something screenshots, which I don't expect people to browse; I began that series of shots whilst considering other users' reports of slow reads and writes).
Thoughts
Suspect that without active use of VirtualBox (4.2.0 at this time), there would have been no kernel panic. But I'm not finger-pointing, that's just a hunch.