Re: Debugging 64-bit kernel crashes involving tst-fork1.

On Tue, 2007-02-20 at 13:34 -0500, Carlos O'Donell wrote:
> sr00-03  00000000000e2800 00000000000e2800 0000000000000000 00000000000e2800
> sr04-07  0000000000000000 0000000000000000 0000000000000000 0000000000000000
> 
> IASQ: 0000000000000000 0000000000000000 IAOQ: 0000000040334894 0000000040334898
>  IIR: 0ec25033    ISR: 00000000000e2800  IOR: 00000000000aac8c
                         ^^^^^^^^^^^^^^^^
This clearly identifies the faulting space

>  CPU:        0   CR30: 000000009ad38000 CR31: 0000000040848000
>  ORIG_R28: 00000000407f6c00
>  IAOQ[0]: pa_memcpy+0x114/0x2d0
>  IAOQ[1]: pa_memcpy+0x118/0x2d0
>  RP(r2): copy_from_user+0x34/0x40
> Backtrace:

Which means that somehow a TLB entry got inserted for address
00000000000aac8c in space 00000000000e2800 which didn't have the correct
Access ID (which for us should have been the space 00000000000e2800).

Or, that %cr8 somehow doesn't contain the space 00000000000e2800 ... but
I think that's a bit more unlikely.

James