From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Spiegel Subject: Re: segmentation fault in numa_node_to_cpus_v1 Date: Mon, 1 Nov 2010 21:10:13 -0400 Message-ID: References: <20101101225942.GA21509@sgi.com> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=bwq+fHhr3vJ2l+9lzJjEjqwuYocm2GSNWTaMNwvpAZs=; b=w9hlyadxDsK72H/7uP6NSxk3xFaGcC3ClPUJwk1o9YEyGsetWF+xgzOQ6Y9eM2lrnY ff0M+AEkHV/QQNwMsx14+q5SExr5Uk1lIMc72/eLz36pvFHmDQvo1jRiLUEEnI4dc7YR EibmwRHhPrU8CECVLDEx3+ei70WY8vbAeMENo= In-Reply-To: <20101101225942.GA21509@sgi.com> Sender: linux-numa-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="iso-8859-1" To: linux-numa@vger.kernel.org Hi everyone, I tried the suggestions from Cliff and Scott, with no change in behavior. I tried some primitive debugging and noticed that NUMA_NUM_NODES was 128 and the node argument to numa_node_to_cpus_v1 was 132. When I changed the definition of NUMA_NUM_NODES in numa.h to 2048, I can eliminate the segmentation fault. Now I'm getting "mbind: invalid argument" errors. Thanks, --Michael On Mon, Nov 1, 2010 at 6:59 PM, Cliff Wickman wrote: > On Mon, Nov 01, 2010 at 03:52:59PM -0400, Michael Spiegel wrote: >> Hi, >> >> I'm trying to run the HotSpot Java VM on an SGI UV 1000 with 4096 >> cores. =A0When I enable the NUMA-aware garbage collection algorithm,= I >> get a segmentation fault as the virtual machine is initializing. =A0= The >> sigsegv is occurring at one of the memcpy's in numa_node_to_cpus_v1, >> although I'm afraid I can't determine whether libnuma is being calle= d >> correctly or incorrectly. =A0I am testing on a system that has numac= tl >> 2.0.5. >> >> Thanks, >> --Michael > > Hi Michael, > > =A0I see that Scott Lundal gave you a possible fix. > =A0There were some important corrections added to the latest version,= so > =A0if you could try building numactl/libnuma from numactl-2.0.6-rc3.t= ar.gz > =A0that would be an interesting test. > =A0(ftp://oss.sgi.com/www/projects/libnuma/download/) >> >> #6 =A0 >> #7 =A00x00007f4066fb9ad0 in memcpy () from /lib64/libc.so.6 >> #8 =A00x00007f40658d4c6a in numa_node_to_cpus_v1 (node=3D132, buffer= =3D0x40112d40, >> =A0 =A0bufferlen=3D) at libnuma.c:1203 >> #9 =A00x00007f4066a85255 in os::Linux::rebuild_cpu_to_node_map() () >> =A0 from /usr/ue/0/mspiegel/jdk1.6.0_22/jre/lib/amd64/server/libjvm.= so >> #10 0x00007f4066a8502f in os::Linux::libnuma_init() () >> =A0 from /usr/ue/0/mspiegel/jdk1.6.0_22/jre/lib/amd64/server/libjvm.= so >> #11 0x00007f4066a86c38 in os::init_2() () >> =A0 from /usr/ue/0/mspiegel/jdk1.6.0_22/jre/lib/amd64/server/libjvm.= so >> #12 0x00007f4066b81c4d in Threads::create_vm(JavaVMInitArgs*, bool*)= () >> =A0 from /usr/ue/0/mspiegel/jdk1.6.0_22/jre/lib/amd64/server/libjvm.= so >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-numa= " in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at =A0http://vger.kernel.org/majordomo-info.html > > -- > Cliff Wickman > SGI > cpw@sgi.com > (651) 683-3824 >