Re: [hwloc-devel] Next 1.0/1.1 RC's
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/11/10 19:31, Samuel Thibault wrote: > Could you try the latest 1.1rc snapshot? There's an > additional free fixup. Still fails with 1.1rc4r2825 I'm afraid. :-( (gdb) bt full #0 0x0fb8d460 in raise () from /lib/power6x/libc.so.6 No symbol table info available. #1 0x0fb8eed4 in abort () from /lib/power6x/libc.so.6 No symbol table info available. #2 0x0fbcaa14 in __libc_message () from /lib/power6x/libc.so.6 No symbol table info available. #3 0x0fbd2304 in malloc_printerr () from /lib/power6x/libc.so.6 No symbol table info available. #4 0x0fbd3f98 in free () from /lib/power6x/libc.so.6 No symbol table info available. #5 0x1001689c in hwloc_linux_set_thisthread_membind (topology=0x10030018, nodeset=0x10031038, policy=HWLOC_MEMBIND_BIND, flags=8) at topology-linux.c:1003 fullmask = 0x10038248 max_os_index = 32 linuxmask = 0x10036af8 linuxpolicy = 1 err = -1 #6 0x1000dbcc in hwloc_set_membind_nodeset (topology=0x10030018, nodeset=0x10031038, policy=HWLOC_MEMBIND_BIND, flags=8) at bind.c:243 No locals. #7 0x1000dc7c in hwloc_set_membind (topology=0x10030018, set=0x10035e88, policy=HWLOC_MEMBIND_BIND, flags=8) at bind.c:259 nodeset = 0x100381e8 ret = 268656936 #8 0x10002e30 in testmem (nodeset=0x10035e88, policy=HWLOC_MEMBIND_BIND, flags=8, expected=1) at hwloc_bind.c:79 new_nodeset = 0x10036128 newpolicy = HWLOC_MEMBIND_FIRSTTOUCH area = 0x0 area_size = 1024 #9 0x1000361c in testmem2 (set=0x10035e88, flags=8) at hwloc_bind.c:113 No locals. #10 0x10003724 in testmem3 (set=0x10035e88) at hwloc_bind.c:128 No locals. #11 0x100039d0 in main () at hwloc_bind.c:187 set = 0x10035e88 obj = 0x10031180 str = 0x100365c0 "0x00ff" - -- Christopher Samuel - Senior Systems Administrator VLSCI - Victorian Life Sciences Computational Initiative Email: sam...@unimelb.edu.au Phone: +61 (0)3 903 55545 http://www.vlsci.unimelb.edu.au/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzsn4EACgkQO2KABBYQAh+74QCdEQ/KtODfCoIHFkVFrKHhAaNY WxsAniGEi62T2uZ6gjyyxue0c+hr+QZo =MjIg -END PGP SIGNATURE-
Re: [hwloc-devel] Next 1.0/1.1 RC's
Christopher Samuel, le Tue 23 Nov 2010 07:16:02 +0100, a écrit : > On 23/11/10 00:17, Jeff Squyres wrote: > > > I see some requests to make RC's in the middle of the > > thread with Chris, but it wasn't entirely clear to me > > that the problems had actually been fixed. > > That's correct, and 1.1rc3 also fails, Could you try the latest 1.1rc snapshot? There's an additional free fixup. Samuel
Re: [hwloc-devel] Next 1.0/1.1 RC's
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/11/10 00:17, Jeff Squyres wrote: > I see some requests to make RC's in the middle of the > thread with Chris, but it wasn't entirely clear to me > that the problems had actually been fixed. That's correct, and 1.1rc3 also fails, but I'm still wondering if this is a bug in hwloc or in glibc given that it doesn't appear anywhere else and I can't spot anything with valgrind or with dmalloc. :-( Will chat to our IBM techs when I'm back in the office tomorrow. cheers! Chris - -- Christopher Samuel - Senior Systems Administrator VLSCI - Victorian Life Sciences Computational Initiative Email: sam...@unimelb.edu.au Phone: +61 (0)3 903 55545 http://www.vlsci.unimelb.edu.au/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzrXAMACgkQO2KABBYQAh+tFwCdH5QdtuQtZ9ut/IokLTCIUr2R SuQAoIbOvvRBHJnEH+BB3EiP4KE9j4i7 =1N4a -END PGP SIGNATURE-
Re: [hwloc-devel] Next 1.0/1.1 RC's
On Nov 22, 2010, at 9:23 AM, Samuel Thibault wrote: >> It looks like Chris' latest problem (hwloc-bind test failing in a free) >> is not fixed yet. But we already have several important fixes, so maybe >> we can do rc3 anyway? > > Good for me with the r2813 fix. Ah crud, 1.1rc3 was r2811. Do you want me to make rc4 immediately? (can't put the genie back in the bottle for rc3 -- once it's published on the web/via SVN, you have no idea who may have grabbed it so it's best to just push the RC number and make another one) -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [hwloc-devel] Next 1.0/1.1 RC's
I agree on 1.0.3. Brice Goglin, le Mon 22 Nov 2010 14:26:36 +0100, a écrit : > It looks like Chris' latest problem (hwloc-bind test failing in a free) > is not fixed yet. But we already have several important fixes, so maybe > we can do rc3 anyway? Good for me with the r2813 fix. Samuel
Re: [hwloc-devel] Next 1.0/1.1 RC's
Will do. On Nov 22, 2010, at 8:26 AM, Brice Goglin wrote: > Le 22/11/2010 14:17, Jeff Squyres a écrit : >> Guys -- >> >> I see some requests to make RC's in the middle of the thread with Chris, but >> it wasn't entirely clear to me that the problems had actually been fixed. >> >> Do you still want me to make the next RC's? >> >> > > I think 1.0.3 is good to go. I don't think any recent trunk fix really > needs to be backported there. > > It looks like Chris' latest problem (hwloc-bind test failing in a free) > is not fixed yet. But we already have several important fixes, so maybe > we can do rc3 anyway? > > Brice > > ___ > hwloc-devel mailing list > hwloc-de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [hwloc-devel] Next 1.0/1.1 RC's
Le 22/11/2010 14:17, Jeff Squyres a écrit : > Guys -- > > I see some requests to make RC's in the middle of the thread with Chris, but > it wasn't entirely clear to me that the problems had actually been fixed. > > Do you still want me to make the next RC's? > > I think 1.0.3 is good to go. I don't think any recent trunk fix really needs to be backported there. It looks like Chris' latest problem (hwloc-bind test failing in a free) is not fixed yet. But we already have several important fixes, so maybe we can do rc3 anyway? Brice
[hwloc-devel] Next 1.0/1.1 RC's
Guys -- I see some requests to make RC's in the middle of the thread with Chris, but it wasn't entirely clear to me that the problems had actually been fixed. Do you still want me to make the next RC's? -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
