Reg : Understanding Kernel Panic - (panic(cpu 0 caller 0x00036B48): wait queue deadlock - wq=0x4061504, cpu=0)
Reg : Understanding Kernel Panic - (panic(cpu 0 caller 0x00036B48): wait queue deadlock - wq=0x4061504, cpu=0)
- Subject: Reg : Understanding Kernel Panic - (panic(cpu 0 caller 0x00036B48): wait queue deadlock - wq=0x4061504, cpu=0)
- From: JanakiRam <email@hidden>
- Date: Sun, 29 Jul 2007 23:11:47 +0530
Hi ALL,
I'm working on a maintainance project
which has a kernel driver for handling file operations.When i run my
kext using kextload , my system will panic by showing following Panic Information.
My project has some code which calls the semaphore_wait & semaphore_signal functions.
Is this panic is happening because of the deadlock ( happening because of the semaphore calls ) ? or is there any specific reason for this kind of panic.
If not , how can i interpret the panic information and resolve the Panic. Please help me to analyze the reason for the panic.
Panic.logWed Jul 4 14:57:05 2007
panic(cpu 0 caller 0x00036B48): wait queue deadlock - wq=0x4061504, cpu=0
Latest stack backtrace for cpu 0: Backtrace:
0x00095138 0x00095650 0x00026898 0x00036B48 0x43E0D504 0x43E0D580 0x43E2F058 0x43E2FCC4 0x43E247C4 0x43E09D74 0x43E09F20 0x43E305F8 0x00091100 0x0009136C 0x00044C18 0x0002921C
0x000233F8 0x000ABAAC 0xBBD4630C Kernel loadable modules in backtrace (with dependencies):
com.yourcompany.kext.mykext(1.0.0d1)@0x43e08000Proceeding back via exception chain:
Exception state (sv=0x43ABA500)
PC=0x9000AB48; MSR=0x0000D030; DAR=0x43E420DC;
DSISR=0x40000000; LR=0x9000AA9C; R1=0xBFFFF1E0; XCP=0x00000030 (0xC00 -
System call)Kernel version:Darwin Kernel Version
8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:
xnu-792.12.6.obj~1/RELEASE_PPC*********Please help me to solve this problem. Thanks in Advance.
-JanakiRam.
_______________________________________________
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