> # CONFIG_XFS_ARCH_MIPS is not set
> # CONFIG_XFS_ARCH_MULTI is not set
OK, looks like the same hang. Turning off CONFIG_PAGE_BUF_META should make
it go away.
> I think I compiled with your change:
> ak@bert:~/lsrc/sgi/linux-2.3-xfs > cvs status linux/mm/vmalloc.c
> File: vmalloc.c Status: Up-to-date
> Working revision: 1.9
> Repository revision: 1.9 /cvs/linux-2.3-xfs/linux/mm/vmalloc.c,v
> Sticky Tag: (none)
> Sticky Date: (none)
> Sticky Options: -ko
> There is no spinlock in mm/vmalloc.c
I need to check with Russell, it looks like the CVS tree is not getting
updated, there is an internal tree which is mirrored into the CVS tree
on a daily basis, revision 1.10 is what exists internally. I suspect it will
be a few hours until I see him.
> BTW, it does not boot on AMD CPUs when KDB is enabled because it uses
> Intel specific MSRs unprotected. I sent a patch a few days ago to the kdb
> list to fix this, but never got an response. You probably want to
> incorporate this patch before you announce to avoid lots of
> ``my kernel doesn't boot with XFS'' reports.
Thanks, this is good to know.