On Sat, Feb 16, 2008 at 10:46:23PM +1100, Jeremy Fitzhardinge wrote:
>>> What does this EIP correspond to in your kernel? Also:
>>>
>>> c01687f0 c0417ab6 c040288f c040299a c0403270
>>>
>>> (as guesses of potential callers to try and work out a stack trace).
>>>
>>
> (My usual technique is use "gdb vmlinux" and "x/i 0x...." to do the
> lookup.)
Ok, my objdump didn't do a good job. With gdb I get:
0xc04040bd <xen_set_pte_at+185>: mov %edi,(%eax)
0xc01687f0: Cannot access memory at address 0xc01687f0
0xc0417ab6 <__set_fixmap+326>: pop %ecx
0xc040288f <xen_alloc_ptpage+41>: lock btsl $0x8,(%eax)
0xc040299a <xen_load_idt+74>: lock incb 0xc0766148
0xc0403270 <xen_set_pte_atomic+26>: lock cmpxchg8b (%edi)
Joel
--
Life's Little Instruction Book #139
"Never deprive someone of hope; it might be all they have."
Joel Becker
Principal Software Developer
Oracle
E-mail: [EMAIL PROTECTED]
Phone: (650) 506-8127
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
