Ok, I found the memory information error and fixed it in CVS, but the next error is troubling and it is due to the way we handle umasked events in PAPI. It fails on AMD because the first event has a umask. I have fixed the core dump though.
I'm attempting a fix now. Can you give her another spin? let me know how it goes. Thanks On Tue, 2006-10-31 at 10:26 -0500, William Cohen wrote: > Philip J. Mucci wrote: > > Great! > > > > Thanks for the report. I haven't tested that combo yet...Most of our > > systems at UTK are still perfctr. > > > > Phil > > Hi Phil, > > I spoke a too soon. PAPI is having problems initializing perfmon2 stuff. > Which version of perfmon did you use for this branch? I have check that the > pfmon program is working After things are installed in the local directory. > The > following papi_command_line: > > $ ./papi_command_line -help > PAPI Error: Unknown vendor in memory information call for x86.. > PAPI Error: pfm_get_full_event_name(0x7fff6d8e6740(event 0,DISPATCHED_FPU,0 > masks),0x7fff6d8e68c0,129): invalid or missing unit mask. > Failed adding: -help > because: PAPI_EINVAL > > command_line.c FAILED > Line # 64 > Error in PAPI_start: PAPI_EINVAL > > The following is from papi_cost (which also gets a segmentation fault): > > > $ ./papi_cost > Cost of execution for PAPI start/stop and PAPI read. > This test takes a while. Please be patient... > PAPI Error: Unknown vendor in memory information call for x86.. > PAPI Error: pfm_write_pmcs(3,0x2b9c80953100,2): not supported. > cost.c FAILED > Line # 182 > System error in PAPI_start: Invalid argument > > $ ./papi_native_avail > PAPI Error: Unknown vendor in memory information call for x86.. > Available native events and hardware information. > ------------------------------------------------------------------------- > Vendor string and code : AuthenticAMD (0) > Model string and code : AMD Turion(tm) 64 Mobile Technology ML-37 (16) > CPU Revision : 2.000000 > CPU Megahertz : 800.000000 > CPU's in this Node : 1 > Nodes in this System : 1 > Total CPU's : 1 > Number Hardware Counters : 4 > Max Multiplex Counters : 512 > ------------------------------------------------------------------------- > The following correspond to fields in the PAPI_event_info_t structure. > > Symbol Event Code Long Description > Register Name[n] > Register Value[n] > > PAPI Error: pfm_get_full_event_name(0x7fff444506c0(event 0,DISPATCHED_FPU,0 > masks),0x7fff44450840,129): invalid or missing unit mask. > Segmentation fault > > When running papi_cost under gdb: > > Program received signal SIGSEGV, Segmentation fault. > *__GI_strncpy (s1=0x7fff1b959ed7 "", s2=0x0, n=129) > at ../sysdeps/generic/strncpy.c:41 > 41 c = *s2++; > (gdb) where > #0 *__GI_strncpy (s1=0x7fff1b959ed7 "", s2=0x0, n=129) > at ../sysdeps/generic/strncpy.c:41 > #1 0x00000000004092d7 in _papi_hwi_get_native_event_info ( > EventCode=1073741824, info=0x7fff1b959ed0) at extras.c:643 > #2 0x0000000000401fd2 in main (argc=Variable "argc" is not available. > ) at native_avail.c:106 > > -Will > > _______________________________________________ > perfmon mailing list > [email protected] > http://www.hpl.hp.com/hosted/linux/mail-archives/perfmon/ _______________________________________________ perfmon mailing list [email protected] http://www.hpl.hp.com/hosted/linux/mail-archives/perfmon/
