Dear Rick and Erik, Thank you for your rapid attempt to resolve the issue.
I've got the trunk, rebuild debian package, deployed on both nodes, but the problem persisted. To double-check what was running version here is strings output (could not find --version switch or smth like that in netperf): node3:/var/tmp# strings /usr/bin/netperf | grep 2.4 @(#)netlib.c (c) Copyright 1993-2006 Hewlett-Packard Company. Version 2.4.2 @(#)netsh.c (c) Copyright 1993-2004 Hewlett-Packard Company. Version 2.4.0 @(#)nettest_sctp.c (c) Copyright 2005 Hewlett-Packard Co. Version 2.4.1 @(#)netcpu_procstat.c (c) Copyright 2005. Version 2.4.0 Another note: when running with -d (debug mode) it stalls instead of segfaulting: .... remote listen done. About to start a timer for 1 seconds. proc_stat_buf cpu 3098850 1145379525 31538156 28808563 1052301 296357 1541322 0 cpu0 1631885 572241410 16902161 13707535 500678 154683 719211 0 cpu1 1466965 573138115 14) res[0] is 13707535 Another Debian-only issue: zcat /usr/share/doc/netperf/changelog.gz See the file Release_Notes.node3:/var/tmp# node3:/var/tmp# zcat /usr/share/doc/netperf/changelog.gz; echo See the file Release_Notes. node3:/var/tmp# find /usr/share/doc/netperf -iname *Release* node3:/var/tmp# So Release_Notes seems to be missing On Fri, 07 Apr 2006, Rick Jones wrote: > Erik Wenzel wrote: > >Hi Rick, > >Debian Bug Tool has received a bugreport regarding option "-c". IIRC you > >comitted a patch regarding linux and cpu utilisation yesterday. > >Did you some testing with smp kernel? Yaroslav has one running. > The patch was for netperf4 not netperf2 :) > >----- Forwarded message from Yaroslav Halchenko <[EMAIL PROTECTED]> ----- > >Subject: Bug#361135: netperf: segfaults with -c > >From: Yaroslav Halchenko <[EMAIL PROTECTED]> > >To: Debian Bug Tracking System <[EMAIL PROTECTED]> > >Date: Thu, 06 Apr 2006 16:51:05 -0400 > >Package: netperf > >Version: 2.4.1-1 > >Severity: normal > For grins, it would be good to try the top-of-trunk at > http://www.netperf.org/svn/netperf2/trunk > Since I am, one of these days, going to pull the trigger on 2.4.2. I don't > remeber exactly what-all is in there wrt differences from 2.4.1-1, > but I did just do a run of a command like the one below on a two-CPU Itanium > system running a 2.6.12-1-mckinley-smp kernel without incident. > >Tried to test new switch, installed netperf on two nodes running > >unstable (this email is written from one of them). > >While running netperf node3:~# netperf -c -H 192.168.0.4 > >TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.0.4 > >(192.168.0.4) port 0 AF_INET > >Segmentation fault > >Tail of strace on it shows: > >32470 munmap(0xb7e53000, 131072) = 0 > >32470 open("/proc/stat", O_RDONLY) = 5 > >32470 fstat64(5, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0 > >32470 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, > >0) = 0xb7fe5000 > >32470 read(5, "cpu 3005516 1145379256 30136190"..., 1024) = 762 > >32470 read(5, "", 1024) = 0 > >32470 close(5) = 0 > >32470 munmap(0xb7fe5000, 4096) = 0 > >32470 open("/proc/stat", O_RDONLY) = 5 > >32470 send(3, "\0\0\0\n\377\377\377\377\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., > >256, 0) = 256 > >32470 select(1024, [3], NULL, NULL, {120, 0}) = 1 (in [3], left {120, 0}) > >32470 recv(3, "\0\0\0\v\0\0\0\0\0\1UT\0\1UT\0\0\0\0\0\0\0\0\0\0\0\0\0"..., > >256, 0) = 256 > >32470 connect(4, {sa_family=AF_INET, sin_port=htons(32854), > >sin_addr=inet_addr("192.168.0.4")}, 16) = 0 > >32470 rt_sigaction(SIGALRM, {0x8049990, [ALRM], SA_INTERRUPT}, NULL, 8) = 0 > >32470 alarm(10) = 0 > >32470 gettimeofday({1144356537, 906917}, {0, 0}) = 0 > >32470 lseek(5, 0, SEEK_SET) = 0 > >32470 read(5, "cpu 3005516 1145379256 30136190"..., 156) = 156 > >32470 --- SIGSEGV (Segmentation fault) @ 0 (0) --- > >32470 +++ killed by SIGSEGV +++ > >Content of /proc/stat is > >node3:~# cat /proc/stat > >cpu 3005551 1145379256 30136209 15195950 1039315 71973 244080 0 > >cpu0 1582419 572241319 16182387 6885087 491846 47139 105995 0 > >cpu1 1423131 573137937 13953822 8310862 547469 24833 138084 0 > >intr 1689822233 1493734092 11 0 4 4 0 2 0 4 0 0 0 102 0 29678968 0 166409046 > >0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > >0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > >0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > >0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > >0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > >0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > >ctxt 867696694 > >btime 1138381340 > >processes 8379939 > >procs_running 1 > >procs_blocked 0 > >-- System Information: > >Debian Release: testing/unstable > > APT prefers unstable > > APT policy: (500, 'unstable') > >Architecture: i386 (i686) > >Shell: /bin/sh linked to /bin/bash > >Kernel: Linux 2.6.13.4 > >Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=locale: Cannot set > >LC_CTYPE to default locale: No such file or directory > >locale: Cannot set LC_ALL to default locale: No such file or directory > >ANSI_X3.4-1968) > >Versions of packages netperf depends on: > >ii libc6 2.3.5-9 GNU C Library: Shared libraries > >an > >netperf recommends no packages. > >-- debconf information: > >perl: warning: Setting locale failed. > >perl: warning: Please check that your locale settings: > > LANGUAGE = (unset), > > LC_ALL = (unset), > > LC_NUMERIC = "POSIX", > > LC_MESSAGES = "en_US", > > LC_COLLATE = "ru_RU.KOI8-R", > > LC_CTYPE = "ru_RU.KOI8-R", > > LC_TIME = "C", > > LANG = "ru_RU.KOI8-R" > > are supported and installed on your system. > >perl: warning: Falling back to the standard locale ("C"). > >locale: Cannot set LC_CTYPE to default locale: No such file or directory > >locale: Cannot set LC_ALL to default locale: No such file or directory > >--Yarik > >----- End forwarded message ----- -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07105 Student Ph.D. @ CS Dept. NJIT -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
