On Mon, 2006-11-27 at 11:23 +0100, Eric Dumazet wrote: > On Sunday 26 November 2006 21:49, Andi Kleen wrote: > > I had the patch in, but had to drop it again because it makes one of my > > test system triple fault. Haven't done much investigation yet. > > > > No NUMA configuration found > > Faking a node at 0000000000000000-000000003ef30000 > > <triple fault> > > > > Well, I dont have currently an AMD64 test machine so I cannot really help. > > With previous implementation, the nimimum shift value was 20 (one megabytes) > > If a memnode had a finer range (with chunks not multiple of megabytes), some > bits of memory could be ignored. > > But with your fake node (0-3ef30000), Amul patch may give a shift value of 16. > Maybe this breaks something in the kernel...
I believe that this problem is related to a new patch that enhances the fake NUMA code (see http://article.gmane.org/gmane.linux.kernel/469457). I'll work with the submitter of said patches to make them compatible. Hopefully that will fix the problem. thanks, Amul - 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/
