site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com Hello Fellow Kernel Folks, I'm looking for ideas for how to deduce what is causing a kernel panic. Here is some background. First panic: 0x1b3ebd98 : 0x4257ac (0xe 0xbd0048 0x88a40010 0x10) Second panic: 0x212c7d78 : 0x1423090 (0xe 0x48 0x26d0010 0x26f0010) Thanks, ...Duane _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com Enclosed are two kernel panics, while they look very different at first, a closer inspection shows that the panic cause is the same. Suggestions on how to interpret these panics and how I might locate the cause would be great. Both panics are random/inconsistent. They are located by repeatedly restarting the computer. After 20-40 (sometimes more) restarts the panic will occur. On some machines the panic never occurs (>200 restarts). The problem occurs on Leopard and Snow Leopard. The examples are from Leopard. The first panic (involving IOUSBFamily.kext) occurs with our standard kext. The second panic is now occurring as I have been removing sections of code trying to narrow down the culprit. This last change, affected the timing, a lot. (A dependency on another kext was removed.) I find the similarity that both kinds of panics include this in the backtrace at the point of the panic: This is the location of the kernel panic. The 0xe seems significant. I am also suspicious of the 0x48, and two 0x10. It's just a pattern but it's in each panic. The return address of the first panic (0x4257ac ) happens to be IOEventSource::openGate(). But the 0xe make no sense as a "this" pointer. The return address in the second trace (0x1423090 ) appears to be unmapped (I can't find a kext in that address space.) I'm slowly working towards finding this problem , but any hints, tips, or ideas are all quite welcome! 2010-02-25-143823.panic 2010-02-25-172012.panic PGP.sig