Topic
4 replies Latest Post - ‏2010-03-18T01:45:16Z by Yao_Qi
michael_guyver
michael_guyver
3 Posts
ACCEPTED ANSWER

Pinned topic Failed to build LKM module

‏2009-11-04T17:17:08Z |
Hi there,

I'm having trouble getting the DataCollection tools to install. Using the verbose installation option, I saw that there are errors being generated in the compilation steps - in particular that there are "too few arguments to on_each_cpu". The interesting part of the output is here: http://pastebin.com/f2b735473

Can anyone help? It's looking very promising but I can't get the Dashboard to collect any data.

Cheers

Michael

-------------8<-------------

OS : Linux
Version : 2.6.26.8-57.fc8
Architecture : x86
Platform : xi32

-------------8<-------------

  1. java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build pxi3260sr6-20090925_01(SR6))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr6-20090923_42924 (JIT enabled, AOT enabled)
J9VM - 20090923_042924
JIT - r9_20090902_1330ifx1
GC - 20090817_AA)
JCL - 20090924_01
Updated on 2010-03-18T01:45:16Z at 2010-03-18T01:45:16Z by Yao_Qi
  • michael_guyver
    michael_guyver
    3 Posts
    ACCEPTED ANSWER

    Re: Failed to build LKM module

    ‏2009-11-04T17:49:38Z  in response to michael_guyver
    /usr/include/linux/version.h:

    #define LINUX_VERSION_CODE 132634
    #define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))
    • michael_guyver
      michael_guyver
      3 Posts
      ACCEPTED ANSWER

      Re: Failed to build LKM module

      ‏2009-11-05T13:14:35Z  in response to michael_guyver
      Turns out that the preprocessor statement

      
      #
      
      if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,26)
      


      in pmc.c == 132634. I changed the evaluation to be <= and got the following messages during installation:
      
      Installing ... waiting 
      
      for chmod +x /tmp/NGS_temp_dir/bin/doMake.sh total command length 40 completed chmod +x /tmp/NGS_temp_dir/bin/doMake.sh waiting 
      
      for bash /tmp/NGS_temp_dir/bin/doMake.sh /tmp/NGS_temp_dir install -DINTEL_P6 -DOECPU4 total command length 82 Build using /tmp/NGS_temp_dir install -DINTEL_P6 -DOECPU4 Make on /home/guyverm/dev/DataCollector.v2.1.1 /tmp/NGS_temp_dir -DINTEL_P6 -DOECPU4 Copy from /tmp/NGS_temp_dir to /home/guyverm/dev/DataCollector.v2.1.1 completed bash /tmp/NGS_temp_dir/bin/doMake.sh /tmp/NGS_temp_dir install -DINTEL_P6 -DOECPU4 [THOR] JAVA_HOME is not set... output lines 6 Build using /tmp/NGS_temp_dir install -DINTEL_P6 -DOECPU4 Make on /home/guyverm/dev/DataCollector.v2.1.1 /tmp/NGS_temp_dir -DINTEL_P6 -DOECPU4 Copy from /tmp/NGS_temp_dir to /home/guyverm/dev/DataCollector.v2.1.1 [THOR] JAVA_HOME is not set... [DONE]
      

      This looks better than the previous output (see the pastebin link in the first post), but the /sbin/lsmod | grep probem still fails. However, the check

      java -agentlib:ThorAgent -version

      gives the following output after the DCServer has been started:

      
      [THOR] Version 2.0.0, Build 20090930-01:42:24 [THOR] Loading THOR agent... [THOR] DONE [THOR] Control Thread Started [THOR] Start communication
      


      I'm still unable to run an application created within a localhost workspace in the Dashboard.

      Can someone help by suggesting how I can produce some logging output from the Dashboard in Eclipse?

      Cheers

      Mike
      • Yao_Qi
        Yao_Qi
        3 Posts
        ACCEPTED ANSWER

        Re: Failed to build LKM module

        ‏2010-02-01T13:56:14Z  in response to michael_guyver
        Michael, the can you run application with dcagent, and get trace file? If you can get trace file, then, you can open it by VisualAnalzyer.

        For log of dashboard, I will check with some one else, who is writing that code, and let you know soon.
      • Yao_Qi
        Yao_Qi
        3 Posts
        ACCEPTED ANSWER

        Re: Failed to build LKM module

        ‏2010-03-18T01:45:16Z  in response to michael_guyver
        Michael,
        I checked with dashboard owner on logging issue. There is no logging in dashboard, but not hard to add it. We will evaluate this feature, and add it in the future if it is important to most of users of MSDK.