Re: segmentation fault in numa_node_to_cpus_v1

Cliff Wickman <[email protected]>
Newsgroups org.kernel.vger.linux-numa
Message-ID <[email protected]>
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.  When I enable the NUMA-aware garbage collection algorithm, I
> get a segmentation fault as the virtual machine is initializing.  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 called
> correctly or incorrectly.  I am testing on a system that has numactl
> 2.0.5.
> 
> Thanks,
> --Michael

Hi Michael,

  I see that Scott Lundal gave you a possible fix.
  There were some important corrections added to the latest version, so
  if you could try building numactl/libnuma from numactl-2.0.6-rc3.tar.gz 
  that would be an interesting test.
  (ftp://oss.sgi.com/www/projects/libnuma/download/)
> 
> #6  <signal handler called>
> #7  0x00007f4066fb9ad0 in memcpy () from /lib64/libc.so.6
> #8  0x00007f40658d4c6a in numa_node_to_cpus_v1 (node=132, buffer=0x40112d40,
>    bufferlen=<value optimized out>) at libnuma.c:1203
> #9  0x00007f4066a85255 in os::Linux::rebuild_cpu_to_node_map() ()
>   from /usr/ue/0/mspiegel/jdk1.6.0_22/jre/lib/amd64/server/libjvm.so
> #10 0x00007f4066a8502f in os::Linux::libnuma_init() ()
>   from /usr/ue/0/mspiegel/jdk1.6.0_22/jre/lib/amd64/server/libjvm.so
> #11 0x00007f4066a86c38 in os::init_2() ()
>   from /usr/ue/0/mspiegel/jdk1.6.0_22/jre/lib/amd64/server/libjvm.so
> #12 0x00007f4066b81c4d in Threads::create_vm(JavaVMInitArgs*, bool*) ()
>   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 [email protected]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Cliff Wickman
SGI
[email protected]
(651) 683-3824
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.