On Thu, Jun 12, 2003 at 08:07:59AM -0400, Trevor Woerner wrote:
> Thanks for your (and everyone's suggestions) I'll have a look at this
> today. I put a printk in kernel/proc.c:sys_sysinfo() so that's the one
> being called. I also put another printk in
> arch/mips64/mm/init.c:si_meminfo() (??? i think...) and it was being
> called from 'sys_info()'. I don't remember seeing sys32_sysinfo() but
> I'll look again.
sys32_sysinfo calls sys_sysinfo. So if you see a direct call to
sys_sysinfo this might proof something is using the wrong syscall.
Strace is your friend ... Oh, and verify that your kernel has Andrew's
patch from my previous mail applied.