Re: Reg : Understanding Kernel Panic - (panic(cpu 0 caller 0x00036B48): wait queue deadlock - wq=0x4061504, cpu=0)
site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com On Jul 29, 2007, at 7:54 PM, JanakiRam wrote: Hi Herb, Janaki, - two machine debugging - kernel debug kits - xnu sources = Mike _______________________________________________ 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 is new post for kernel panic.What you have mentioned was a kernel panic message which will be displayed when an invalid memory access happens. This is a new scenenario altogether. A little less attitude might help encourage folks to help you. Herb's suggestion amounts to "the information you need in order to interpret the panic and debug it is already available if you would just care to look". You clearly haven't spent much productive time taking advantage of the resources available to you; I would encourage you to consider the following pieces in seeking your solution: You may also simply want to look carefully at think carefully about your code. It is doing something very wrong with locks, and you may come to a solution quicker simply by looking for the mistake there. This email sent to site_archiver@lists.apple.com
participants (1)
-
Michael Smith