[OpenAFS-devel] 1.3.79 on AIX 5.2, system dump when using token

[Horst Birthelmer]

On Feb 24, 2005, at 6:29 PM, Michael Niksch wrote:

> CRASH INFORMATION:
> CPU 0 CSA F00000002FF3A600 at time of crash, error code for LEDs: 
> 30000000
> pvthread+00AF00 STACK:
> [0062A1F8]xmalloc1+0007AC (0000000000000200, F10000E009B31000,
>    0000000000000000, F10000E009B31000, 0000000000000600, 
> F10000E029D33061,
>    0000000000000002, 0000000000409318 [??])
> [0062EB78]xmalloc+000208 (??, ??, ??)
> [088808B0]afs_osi_Alloc+00005C (??)
> [088FA298]afs_HandlePioctl+0003C0 (0000000000000000, 800C5608800C5608,
>    F00000002FF3A420, 0000000000000000, F00000002FF3A458)
> [08904ED4]afs_syscall_pioctl+000290 (0000000000000000, 
> 800C5608800C5608,
>    000000002FF22438, 0000000000000000)
> [08884F20]syscall+0001A4 (0000001400000014, 0000000000000000,
>    800C5608800C5608, 2FF224382FF22438, 0000000000000000, 
> 6F6D00006F6D0000,
>    0000008000000080)
> [08884CDC]lpioctl+000050 (0000000000000000, 800C5608800C5608,
>    000000002FF22438, 0000000000000000)
> [0000379C]sc_msr_2_point+000028 ()
> Not a valid dump data area @ 2FF22160
> (0)> q

That's an old more or less known problem.

The problem is the kernel allocation. The xmalloc call ... you can see 
that in the backtrace above.
I know that there's a problem but never had either the time to fix it 
nor any clue how to fix that since it looks pretty correct to me when a 
pioctl allocates some kernel memory.


Horst