<?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>2642</bug_id>
          
          <creation_ts>2012-06-21 13:43:51 +0000</creation_ts>
          <short_desc>dmesg errors on emenlow sato sdk image</short_desc>
          <delta_ts>2012-08-01 10:43:08 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>BSPs</product>
          <component>bsps-meta-intel</component>
          <version>1.2</version>
          <rep_platform>E-Menlow</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>VERIFIED</bug_status>
          <resolution>INVALID</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>1.3 M3</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Alexandru Georgescu">alexandru.c.georgescu</reporter>
          <assigned_to name="Nitin Kamble">nitin.a.kamble</assigned_to>
          <cc>alexandrux.palalau</cc>
    
    <cc>meta.mr.watcher</cc>
    
    <cc>meta.watcher</cc>
    
    <cc>sgw</cc>
    
    <cc>tom.zanussi</cc>
    
    <cc>yilongx.y.sun</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>22469</commentid>
    <comment_count>0</comment_count>
    <who name="Alexandru Georgescu">alexandru.c.georgescu</who>
    <bug_when>2012-06-21 13:43:51 +0000</bug_when>
    <thetext>Image used: 
   core-image-sato-sdk-emenlow-20120608013610.hddimg
BSP:
   emenlow

STEPS:
After booting the installed image(above) in the emenlow BSP, the following error appears in dmesg log:

root@emenlow:~# dmesg | grep -i error
[drm:psb_do_init] *ERROR* Debug is 0x000000ff
root@emenlow:~#</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>22471</commentid>
    <comment_count>1</comment_count>
    <who name="Alexandru Palalau">alexandrux.palalau</who>
    <bug_when>2012-06-21 15:13:12 +0000</bug_when>
    <thetext>Also on FRI2 core-image-sato-sdk</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>22560</commentid>
    <comment_count>2</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2012-06-25 18:29:15 +0000</bug_when>
    <thetext>Tom, are you familiar with this? I presume this is an emgd 1.10 related error message?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>22561</commentid>
    <comment_count>3</comment_count>
    <who name="Tom Zanussi">tom.zanussi</who>
    <bug_when>2012-06-25 18:36:18 +0000</bug_when>
    <thetext>I don&apos;t think it&apos;s emgd-related since it happens on emenlow.  Looks like a harmless debug-related message (that happens only on sdk images?).</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>22586</commentid>
    <comment_count>4</comment_count>
    <who name="yilong, sun">yilongx.y.sun</who>
    <bug_when>2012-06-26 07:23:58 +0000</bug_when>
    <thetext>we just check this case, but i can&apos;t find this error message.

Image used:
http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20120608-1/machines/fri2/core-image-sato-sdk-fri2-20120608013703.hddimg 

BSP:
   FIR2</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>22831</commentid>
    <comment_count>5</comment_count>
    <who name="Alexandru Georgescu">alexandru.c.georgescu</who>
    <bug_when>2012-07-05 11:46:03 +0000</bug_when>
    <thetext>it reproduces with this image: 
http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20120704-1/machines/sugarbay/core-image-sato-sugarbay-20120704205134.hddimg</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>22942</commentid>
    <comment_count>6</comment_count>
    <who name="Alexandru Georgescu">alexandru.c.georgescu</who>
    <bug_when>2012-07-10 12:19:33 +0000</bug_when>
    <thetext>Hi,
I on this image http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20120705-4/machines/emenlow/core-image-sato-sdk-emenlow-20120705234932.hddimg installed on e-Menlow BSP, I have this errors:

root@emenlow:~/weekly# ./05_dmesg_log.sh 
[drm:psb_do_init] *ERROR* Debug is 0x000000ff
[drm:msvdx_get_fw] *ERROR* MSVDX: msvdx_fw.bin request_firmware failed: Reason -22
[drm:psb_setup_fw] *ERROR* psb: No valid msvdx_fw.bin firmware found.
[drm:LVDSI2CSetBacklight] *ERROR* msg: i2c_transfer error</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>23054</commentid>
    <comment_count>7</comment_count>
    <who name="Alexandru Georgescu">alexandru.c.georgescu</who>
    <bug_when>2012-07-12 14:43:31 +0000</bug_when>
    <thetext>This message appears on CROWNBAY. I suppose it is because there is no Power button installed on the BSP.


ACPI Error: Could not enable PowerButton event (20110623/evxfevnt-199)
button: probe of LNXPWRBN:00 failed with error -22</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>23176</commentid>
    <comment_count>8</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2012-07-17 20:26:09 +0000</bug_when>
    <thetext>So which image on which hardware is producing which error message? The above is very confusing as at least 3 BSPs are mentioned.

Assigning to Nitin as emenlow was the first mentioned.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>23198</commentid>
    <comment_count>9</comment_count>
    <who name="Nitin Kamble">nitin.a.kamble</who>
    <bug_when>2012-07-18 05:23:31 +0000</bug_when>
    <thetext>Alexandru,
 As Darren says, I also find the information on this bug very confusing. Please open separate bugs for separate issues. 

  psb error on sugarbay bsp image, does not make sense at all. sugarbay does not have the psb driver.

Questions for QA:
1. Does the error on comment #6 of this bug, happen with non-sdk images ?

2. Is the error/warning reproducible consistently ?

3. Which BSP images give exact same error ?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>23249</commentid>
    <comment_count>10</comment_count>
    <who name="Nitin Kamble">nitin.a.kamble</who>
    <bug_when>2012-07-19 09:47:04 +0000</bug_when>
    <thetext>I hear from Alexandru Palalau that the bug is not reproducible on FRI2 anymore. I would like to close this bug as it is very confusing with too many errors reported here.
  if the emenlow, fri2 or sugarbay errors still present, then please open separate bugs for every error for separate for each bsp.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>23704</commentid>
    <comment_count>11</comment_count>
    <who name="Alexandru Georgescu">alexandru.c.georgescu</who>
    <bug_when>2012-08-01 10:43:08 +0000</bug_when>
    <thetext>I will open separate issues for different bsps.

Thanks,
Alex.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>