<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>858</bug_id>
          
          <creation_ts>2011-03-12 16:22:17 +0000</creation_ts>
          <short_desc>OProfile-viewer connect issue to oprofile-server running on qemux86-64</short_desc>
          <delta_ts>2011-05-02 19:31:58 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>6</classification_id>
          <classification>Yocto Project Subprojects</classification>
          <product>Kernel</product>
          <component>kernel-configuration</component>
          <version>1.0</version>
          <rep_platform>x86</rep_platform>
          <op_sys>x86_64</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>1.1</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Jessica">jessica.zhang</reporter>
          <assigned_to name="Bruce Ashfield">bruce.ashfield</assigned_to>
          <cc>bruce.ashfield</cc>
    
    <cc>dexuan.cui</cc>
    
    <cc>dvhart</cc>
    
    <cc>lianhao.lu</cc>
    
    <cc>sgw</cc>
    
    <cc>tom.zanussi</cc>
    
    <cc>yp.kernel.watcher</cc>
    
    <cc>yp.sdk.watcher</cc>
    
    <cc>yp.watcher</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>12525</commentid>
    <comment_count>0</comment_count>
    <who name="Jessica">jessica.zhang</who>
    <bug_when>2011-03-12 16:22:17 +0000</bug_when>
    <thetext>While testing oprofile-viewer connecting to oprofile-server running in qemux86-64, got error &quot;Error whilst spawning: opcontrol exited with error code: 1.  (note: host is 32bit Ubuntu 10.04)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>12536</commentid>
    <comment_count>1</comment_count>
    <who name="Lianhao Lu">lianhao.lu</who>
    <bug_when>2011-03-13 01:56:45 +0000</bug_when>
    <thetext>Is this caused by bug#859? This message shows the &quot;opcontrol&quot; failed on the target qemux86-64.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>12540</commentid>
    <comment_count>2</comment_count>
    <who name="Jessica">jessica.zhang</who>
    <bug_when>2011-03-13 19:10:18 +0000</bug_when>
    <thetext>One is latency top missing config in qemux86-64 kernel, this one is for oprofile, are they related?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>12541</commentid>
    <comment_count>3</comment_count>
    <who name="Lianhao Lu">lianhao.lu</who>
    <bug_when>2011-03-13 19:43:10 +0000</bug_when>
    <thetext>(In reply to comment #2)
&gt; One is latency top missing config in qemux86-64 kernel, this one is for
&gt; oprofile, are they related?

Sorry, I mis-confused oprofile with latencytop.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>12542</commentid>
    <comment_count>4</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2011-03-13 19:44:38 +0000</bug_when>
    <thetext>(In reply to comment #0)
&gt; While testing oprofile-viewer connecting to oprofile-server running in
&gt; qemux86-64, got error &quot;Error whilst spawning: opcontrol exited with error code:
&gt; 1.  (note: host is 32bit Ubuntu 10.04)

In qemux86-64 target, &quot;opcontrol --init&quot; reports:

FATAL: Module oprofile not found.
FATAL: Module oprofile not found.
Kernel doesn&apos;t support oprofile



BTW:
qemux86&apos;s workable config: 
CONFIG_OPROFILE=y
# CONFIG_OPROFILE_EVENT_MULTIPLEX is not set
CONFIG_HAVE_OPROFILE=y

qemux86-64&apos;s &quot;bad&quot; config:
CONFIG_HAVE_OPROFILE=y

So looks qemux86-64 needs CONFIG_OPROFILE=y, too.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>12544</commentid>
    <comment_count>5</comment_count>
    <who name="Lianhao Lu">lianhao.lu</who>
    <bug_when>2011-03-13 22:12:49 +0000</bug_when>
    <thetext>This is caused by the missing configuration of CONFIG_OPROFILE in x86_64 kernel configuration.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>12556</commentid>
    <comment_count>6</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2011-03-14 00:54:02 +0000</bug_when>
    <thetext>(In reply to comment #4)
&gt; (In reply to comment #0)
&gt; &gt; While testing oprofile-viewer connecting to oprofile-server running in
&gt; &gt; qemux86-64, got error &quot;Error whilst spawning: opcontrol exited with error code:
&gt; &gt; 1.  (note: host is 32bit Ubuntu 10.04)
&gt; In qemux86-64 target, &quot;opcontrol --init&quot; reports:
&gt; FATAL: Module oprofile not found.
&gt; FATAL: Module oprofile not found.
&gt; Kernel doesn&apos;t support oprofile
&gt; BTW:
&gt; qemux86&apos;s workable config: 
&gt; CONFIG_OPROFILE=y
&gt; # CONFIG_OPROFILE_EVENT_MULTIPLEX is not set
&gt; CONFIG_HAVE_OPROFILE=y
&gt; qemux86-64&apos;s &quot;bad&quot; config:
&gt; CONFIG_HAVE_OPROFILE=y
&gt; So looks qemux86-64 needs CONFIG_OPROFILE=y, too.

BTW: after &quot;bitbake -c menuconfig virtual/linux&quot; and setting CONFIG_OPROFILE=y for qemux86-64, oprofile can work in qemux86-64 target in timer interrupt mode.
So I believe qemux86-64 needs CONFIG_OPROFILE=y</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>12568</commentid>
    <comment_count>7</comment_count>
    <who name="Jessica">jessica.zhang</who>
    <bug_when>2011-03-14 15:27:49 +0000</bug_when>
    <thetext>OE Build Configuration:
BB_VERSION        = &quot;1.11.0&quot;
METADATA_BRANCH   = &quot;bernard&quot;
METADATA_REVISION = &quot;a33a2cc024f9c9147c92c5da70d8fbb631b968f9&quot;
TARGET_ARCH       = &quot;x86_64&quot;
TARGET_OS         = &quot;linux&quot;
MACHINE           = &quot;qemux86-64&quot;
DISTRO            = &quot;poky&quot;
DISTRO_VERSION    = &quot;0.9+snapshot-20110314&quot;
TARGET_FPU        = &quot;&quot;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>12573</commentid>
    <comment_count>8</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2011-03-14 15:54:16 +0000</bug_when>
    <thetext>This is missing from common-pc-64.scc

+include features/profiling/profiling.scc

We&apos;ll have to commit a fragment for qemux86-64 for now.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>12580</commentid>
    <comment_count>9</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2011-03-14 16:55:33 +0000</bug_when>
    <thetext>Temp fix until Bruce can commit to linux-yocto.

http://git.pokylinux.org/cgit.cgi/poky-contrib/commit/?h=dvhart/kernel&amp;id=cc3e525fdb480d6b86637afa7b4c8d947d32304b</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>12585</commentid>
    <comment_count>10</comment_count>
    <who name="Saul Wold">sgw</who>
    <bug_when>2011-03-14 18:36:08 +0000</bug_when>
    <thetext>
Fixed in Master and Bernard

http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/?id=50bb373d1b3956cd4877752d3811e45a93ac2e33</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>13530</commentid>
    <comment_count>11</comment_count>
    <who name="Jessica">jessica.zhang</who>
    <bug_when>2011-05-02 19:31:58 +0000</bug_when>
    <thetext>verified that the kernel config issue is fixed, but there&apos;s no oprofile data collected, I think Dexuan has another bug opened regarding it since below in the comments he said qemux86-64 only works in the timer interrupt mode</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>