Re: Reg : Understanding Kernel Panic - (panic(cpu 0 caller 0x00036B48): wait queue deadlock - wq=0x4061504, cpu=0)
Re: Reg : Understanding Kernel Panic - (panic(cpu 0 caller 0x00036B48): wait queue deadlock - wq=0x4061504, cpu=0)
- Subject: Re: Reg : Understanding Kernel Panic - (panic(cpu 0 caller 0x00036B48): wait queue deadlock - wq=0x4061504, cpu=0)
- From: Michael Smith <email@hidden>
- Date: Sun, 29 Jul 2007 21:14:43 -0700
On Jul 29, 2007, at 7:54 PM, JanakiRam wrote:
Hi Herb,
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.
Janaki,
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:
- two machine debugging
- kernel debug kits
- xnu sources
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.
= Mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden