| I've been trying to hold down my utter contempt for the KEXTs that Parallels installs, but I now have found three different ways to kernel panic my machine (intel 20" iMac) each variation of the kernel panic has a different set of reproduction steps, but the exact same stack trace:
panic(cpu 0 caller 0x0035BEAC): freeing free mbuf Backtrace, Format - Frame : Return Address (4 potential args on stack) 0x2513bdb8 : 0x128d1f (0x3c9540 0x2513bddc 0x131df4 0x0) 0x2513bdf8 : 0x35beac (0x3e9c7c 0x102 0x20 0x2) 0x2513be38 : 0x7194a4 (0x36ec3600 0x0 0x2513be68 0x1a1ec0) 0x2513be58 : 0xa1d454 (0x2397e000 0x36ec3600 0x0 0x2) 0x2513be88 : 0xa1bad0 (0x2397e000 0x36ec3600 0x0 0x3a7fd80) 0x2513bea8 : 0xa1ed7c (0x2397e000 0x0 0x1000000 0x133b25) 0x2513bf08 : 0x398a1f (0x2397e000 0x3a7fd80 0x1 0x3940b20) 0x2513bf58 : 0x397bf1 (0x3a7fd80 0x135ec3 0x0 0x3940b20) 0x2513bf88 : 0x397927 (0x3a79540 0x0 0x20 0xb03) 0x2513bfc8 : 0x19a74c (0x3a79540 0x0 0x19d0b5 0x46d83b4) Backtrace terminated-invalid frame pointer 0x0 Kernel loadable modules in backtrace (with dependencies): com.apple.iokit.AppleYukon(1.0.7b3)@0xa19000 dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x712000 dependency: com.apple.iokit.IOPCIFamily(2.1)@0x597000 com.apple.iokit.IONetworkingFamily(1.5.1)@0x712000
The crash obviously looks like it's coming from the Yukon driver for my Gigabit adapter, but the question I'm trying to figure out the answer to, is if it's parallels (which, painfully, I need for my day job) or if it's a bug in Apple's driver. I say parallels, because there's no other KEXTs loaded that aren't Apple's other than the parallels virtualization KEXTs.
I have a PowerBook here as well, so debugging over firewire would be an option I'd think, but I'm a bit unsure of what I should be looking for.
The kernel panics are fun and all, but its really starting to be tedious ;) Any tips?
Cheers |