Here's a panic log, if that helps. Although, every report I have received, has a different stack.
Sun Mar 16 00:12:40 2008
panic(cpu 1 caller 0x001A8C8A): Kernel trap at 0x561292a6, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x69546c69, CR3: 0x01430000, CR4: 0x00000660
EAX: 0x00000276, EBX: 0x561fac10, ECX: 0x69546c61, EDX: 0x561546c4
CR2: 0x69546c69, EBP: 0x2eb33ba8, ESI: 0x56154600, EDI: 0x04a393b0
EFL: 0x00010297, EIP: 0x561292a6, CS: 0x00000008, DS: 0x00000010
Error code: 0x00000000
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2eb33988 : 0x12b0e1 (0x457024 0x2eb339bc 0x13321a 0x0)
0x2eb339d8 : 0x1a8c8a (0x460550 0x561292a6
0xe 0x45fd00)
0x2eb33ab8 : 0x19eb67 (0x2eb33ad0 0x54238cc 0x2eb33ba8 0x561292a6)
0x2eb33ac8 : 0x561292a6 (0xe 0x48 0x10 0x10)
0x2eb33ba8 : 0x56111e7c (0x56154600 0x4a393b0 0x0 0x5)
0x2eb33bd8 : 0x561138bc (0x2eb33ebc 0x539504 0xb 0x2)
0x2eb33d78 : 0x1f5131 (0x2eb33dac 0x246 0x2eb33dd8 0x1d9207)
0x2eb33dd8 : 0x1eb98f (0x4a393b0 0x2eb33ebc 0x1 0x2eb33f54)
0x2eb33e68 : 0x38a35e (0x4923b10 0x2eb33ebc 0x0 0x2eb33f54)
0x2eb33f18 : 0x38a656 (0x2eb33f54 0x4923b10 0x803200 0x0)
0x2eb33f78 : 0x3dbe77 (0x44b8560 0x48d9520 0x48d9564 0xffffffff)
0x2eb33fc8 : 0x19f084 (0x48cfb00 0x0 0x1a20b5 0x48cfb00)
No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb0102b98
Kernel loadable modules in backtrace (with dependencies):
com.effigent.kext.fpnew(1.0b8)@0x56110000->0x56151fff
----- Original Message ----
From: Ratheesh Ramachandran <email@hidden>
To: Darwin-Kernel List <email@hidden>
Sent: Friday, 14 March, 2008 2:48:16 PM
Subject: kernel panic on wakeup from hibernation
I am this generic kext (set up as character device), which panics sometimes when system comes back from hibernation. This seems to happen on machines with hibernatemode 3 (although, not sure).
My question is: Do kexts have to do something to handle/allow hibernation gracefully ? What happens to existing threads (in different states) when hibernation starts/ends ?
My kext accepts ioctl commands and uses semaphores quite a lot. Just before the panic occurs, semaphore waits seem to end with
KERN_ABORTED.
Thoughts/suggestions ?
Thanks
Ratheesh
Save all your chat conversations.
Find them online.-----Inline Attachment Follows-----
_______________________________________________
Do
not
post
admin
requests
to
the
list.
They
will
be
ignored.
Darwin-kernel
mailing
list
(
email@hidden)
Help/Unsubscribe/Update
your
email
sent
to
email@hidden