Arun Sharma wrote:
I just got a kernel mode page fault. I'd like to find out more
about
fault virtual address = 0xdeadc162
It looks like the address is meant to signal a particular class of
error. Which one ?
0xdeadc162 - 0xdeadc0de = 0x0084 = 132 decimal
Look for a short value
On Sun, Jun 09, 2002 at 11:40:09PM -0700, Terry Lambert wrote:
0xdeadc162 - 0xdeadc0de = 0x0084 = 132 decimal
Look for a short value that's getting set to 132.
As I said in another email, I think this is td1-td_priority in
kern_mutex.c:510.
-Arun
To Unsubscribe: send mail to
I just got a kernel mode page fault. I'd like to find out more
about
fault virtual address = 0xdeadc162
It looks like the address is meant to signal a particular class of
error. Which one ?
-Arun
Background fsck:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic.id
For debugging purposes kernel memory which has been freed is
filled with the pattern 0xdeadc0de (hex). So if you get
a VM fault on something similar then something in the system
has tried to reference a structure that is sitting in memory which
has been freed. A no-no to be
In message [EMAIL PROTECTED], Arun Sharma writes:
I just got a kernel mode page fault. I'd like to find out more
about
fault virtual address = 0xdeadc162
0xdeadcode is used to fill freed memory.
It looks like the address is meant to signal a particular class of
error. Which one ?
5 matches
Mail list logo