From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ryan Harper Subject: Re: Numa=on broken? Date: Thu, 3 May 2007 18:10:05 -0500 Message-ID: <20070503231005.GP27552@us.ibm.com> References: <94C8C9E8B25F564F95185BDA64AB05F605025E4C@USTR-EXCH5.na.uis.unisys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <94C8C9E8B25F564F95185BDA64AB05F605025E4C@USTR-EXCH5.na.uis.unisys.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Subrahmanian, Raj" Cc: Ryan Harper , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org * Subrahmanian, Raj [2007-05-03 17:30]: > All, > It looks like numa=on is broken. > I have tried with the tip of the tree, with the changeset 14676 (which > fixes the numa=on problem) and the two patches that Ryan sent out. > I am running with boot options acpi=on and numa=on. > I am running on an ES7000 with 2 nodes (2 cells of 8 processors and 32 > GB memory each). > > Thanks > Raj > PS. We(Unisys) are going to start running our weekly tests with default > numa=on. This weeks' tests brought out this problem. > > \ \/ /___ _ __ |___ / / _ \ _ _ _ __ ___| |_ __ _| |__ | | ___ > \ // _ \ '_ \ |_ \| | | |__| | | | '_ \/ __| __/ _` | '_ \| |/ _ \ > / \ __/ | | | ___) | |_| |__| |_| | | | \__ \ || (_| | |_) | | __/ > /_/\_\___|_| |_| |____(_)___/ \__,_|_| |_|___/\__\__,_|_.__/|_|\___| > > http://www.cl.cam.ac.uk/netos/xen > University of Cambridge Computer Laboratory > > Xen version 3.0-unstable (root@site) (gcc version 4.1.2 20070115 > (prerelease) (SUSE Linux)) Thu May 3 16:58:28 EDT 2007 > Latest ChangeSet: Thu May 03 11:22:58 2007 +0100 15007:c857bf38f015 > > (XEN) Command line: /boot/xen.gz com1=115200,8n1 apic_verbosity=debug > dom0_mem=512M acpi=on numa=on > (XEN) 0000000000000000 - 000000000009d000 (usable) > (XEN) 000000000009d800 - 00000000000a0000 (reserved) > (XEN) 00000000000ce000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 0000000037e70000 (usable) > (XEN) 0000000037e70000 - 0000000037ed8000 (ACPI data) > (XEN) 0000000037ed8000 - 0000000037f00000 (ACPI NVS) > (XEN) 0000000037f00000 - 00000000f0000000 (usable) > (XEN) 00000000f8000000 - 00000000fec00000 (reserved) > (XEN) 00000000fffc0000 - 0000000100000000 (reserved) > (XEN) 0000000100000000 - 0000001008000000 (usable) > (XEN) System RAM: 65407MB (66976820kB) > (XEN) Cannot handle page request order 0! > (XEN) Cannot handle page request order 2! > (XEN) Cannot handle page request order 0! > (XEN) Cannot handle page request order 2! > (XEN) Cannot handle page request order 0! > (XEN) Cannot handle page request order 2! > (XEN) Cannot handle page request order 0! > (XEN) Cannot handle page request order 2! > (XEN) Cannot handle page request order 0! > (XEN) Cannot handle page request order 2! what repo and what changeset? We fixed this issue a while ago, I just booted: changeset: 15020:6f37c763bc0f from http://xenbits.xensource.com/xen-3.1-testing.hg and changeset: 15009:3a5722420de7 from http://xenbits.xensource.com/xen-unstable.hg with no issues on my numa hardware. -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx (512) 838-9253 T/L: 678-9253 ryanh@us.ibm.com