Bug 310

Summary: [eMenlow] i2c_transfer error on e-Menlow
Product: [Build System, Metadata & Runtime] Meta-yocto Reporter: Jiajun Xu <jiajun.xu>
Component: meta-yoctoAssignee: Tom Zanussi <tom.zanussi>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: Low CC: hongnax.xu, jessica.zhang, kevin.tian, kunwei.tian, poky.bs.watcher, poky.watcher, richard.purdie, sgw, wenhuax.fan
Version: 0.9   
Target Milestone: 1.1   
Hardware: E-Menlow   
OS: x86   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Jiajun Xu 2010-09-13 01:27:49 UTC
Testing Env:    
Poky gitinfo: 14830c80d5ce079a5268f233da798c3cfd277f9e
All images file from http://autobuilder.pokylinux.org/milestone/20100909-1/.

With latest images from autobuilder, there is a i2c_transfer error on eMenlow after system booting up.

#########
root@emenlow:~# dmesg | grep -i error
[drm:psb_do_init] *ERROR* Debug is 0x000000ff
[drm:LVDSI2CSetBacklight] *ERROR* msg: i2c_transfer error
#########

Reproduce Steps:
1. Download eMenlow images from autobuilder
2. Burn it into USB stick and boot from the USB stick
3. Install system onto eMenlow
4. Check error message by command dmesg
Comment 1 Saul Wold 2010-09-29 00:40:52 UTC
Maybe missing hardware, could be harmless messages that do not warrant error.
Comment 2 Tom Zanussi 2010-10-06 09:51:30 UTC
Putting some debug code into intel_lvds.c:LVDSI2CSetBacklight() shows the call to i2c_transfer() returns ENXIO (no such device).

One possibility would be to change the error message to say that instead, but I think the right thing to do would be to detect that fact and avoid the callchain altogether.
Comment 3 wenhua.fan 2011-08-26 02:09:37 UTC
This issue still exist in Yocto1.1 20110824 build.

Commit information:

Tree/Branch: Poky/Master
Poky Commit id: 2c8120d4895c1e2539df2226bae5b5f3b914cb07
Meta Branch: Master
Meta commit id: fb15cc4e1c4be75c81acaf6a1dd33675a9142975

Image location:
http://autobuilder02.yoctoproject.org/emenlow-master/nightly/20110824-1/machines/emenlow/x86_32/core-image-sato-sdk-emenlow-20110825004056.hddimg.bz2
Comment 4 wenhua.fan 2011-09-19 18:49:19 UTC
I2C issue reproduce in Yocto 1.1 M4 RC2 build, the information as below:

Tree/Branch: Poky/1.1_M4
Commit id: bb4a5c44da23a1bb363f1f081cf1644fd7975957
Meta Branch: 1.1_M4
Commit id: 49277afd9e5e510f7b1f82fd8cd10732e3bf2633

Image location:

http://autobuilder03.jf.intel.com/pub/emenlow/20110916-1/machines/emenlow/core-image-sato-sdk-emenlow-20110916085642.hddimg
Comment 5 Tom Zanussi 2011-12-21 14:48:32 UTC
I was in the process of fixing things in this area (basically the 3.0
upgrade that ended up being such a pain) and was going to get back to it
when I got the chance.  Now I think I'm just going to leave it to do
along with the 3.2/3.3 upgrade coming soon.
Comment 7 Hongna Xu 2012-05-18 05:45:25 UTC
Verify it, fixed with poky/master commitID 12b4543ac9f54c0db0ee4a7ee546a71946a051f8