Bug 2642 - dmesg errors on emenlow sato sdk image
Summary: dmesg errors on emenlow sato sdk image
Status: VERIFIED INVALID
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-intel (show other bugs)
Version: 1.2
Hardware: E-Menlow Multiple
: Medium normal
Target Milestone: 1.3 M3
Assignee: Nitin Kamble
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-06-21 13:43 UTC by Alexandru Georgescu
Modified: 2012-08-01 10:43 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandru Georgescu 2012-06-21 13:43:51 UTC 
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:~#
Comment 1 Alexandru Palalau 2012-06-21 15:13:12 UTC 
Also on FRI2 core-image-sato-sdk
Comment 2 Darren Hart 2012-06-25 18:29:15 UTC 
Tom, are you familiar with this? I presume this is an emgd 1.10 related error message?
Comment 3 Tom Zanussi 2012-06-25 18:36:18 UTC 
I don't think it's emgd-related since it happens on emenlow.  Looks like a harmless debug-related message (that happens only on sdk images?).
Comment 4 yilong, sun 2012-06-26 07:23:58 UTC 
we just check this case, but i can'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
Comment 6 Alexandru Georgescu 2012-07-10 12:19:33 UTC 
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
Comment 7 Alexandru Georgescu 2012-07-12 14:43:31 UTC 
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
Comment 8 Darren Hart 2012-07-17 20:26:09 UTC 
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.
Comment 9 Nitin Kamble 2012-07-18 05:23:31 UTC 
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 ?
Comment 10 Nitin Kamble 2012-07-19 09:47:04 UTC 
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.
Comment 11 Alexandru Georgescu 2012-08-01 10:43:08 UTC 
I will open separate issues for different bsps.

Thanks,
Alex.