Bug 7439

Summary:	[Test Case 1059] Errors found in core2_32 logs
Product:	[Build System, Metadata & Runtime] BSPs	Reporter:	Lucian Musat <georgex.l.musat>
Component:	bsps-runtime	Assignee:	Saul Wold <sgw>
Status:	RESOLVED WORKSFORME	QA Contact:	Lucian Musat <georgex.l.musat>
Severity:	normal
Priority:	Medium	CC:	sgw, yp.kernel.watcher, yp.watcher
Version:	1.8
Target Milestone:	1.8
Hardware:	E-Menlow
OS:	other
See Also:	https://bugzilla.yoctoproject.org/show_bug.cgi?id=6619
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	Regression (Found by QA test)
Verified:		Documentation change:	Don't know

Description Lucian Musat 2015-03-10 09:24:02 UTC

STATUS: FAILED
BUILD: 1.8_M3.RC3: 5c1c8af083ca7b57cc339d16ce0513b27c5dac90
ENVIRONMENT: core2-32 on eMenlow
STEPS TO REPRODUCE: 
  
 Parse dmesg log and all log files in /var/log for keywords like: "error" , "failed" , "cannot", "can't" etc.
Filter out the known and invalid errors or errors that appear in certain situations and need to be ignored.

EXPECTED OUTCOME: 
  
 No errors or fails should be present in logs

ACTUAL OUTCOME:
  
 These errors were found by the log parser:

Log: /var/log/dmesg

[    3.354542] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness


Log: /var/log//Xorg.0.log

[4281584.130] (EE) Failed to load module psb (module does not exist, 0)

[4281584.131] (EE) Failed to load module psbdrv (module does not exist, 0)

Comment 1 Bruce Ashfield 2015-03-10 12:16:21 UTC

Sending to Darren, so he can redirect this appropriately.

Comment 2 Lucian Musat 2015-03-10 14:45:04 UTC

Another dmesg error found during manual tests:

[    5.236930] gma500 0000:00:02.0: I2C transfer error

Comment 3 Saul Wold 2015-04-16 14:03:04 UTC

The gma transfer error along with the Firmware Bug message should be added to the QA whitelist since the Firmware issue will not be fixed for eMenlow and the gma I2C error is a result of the gma driver trying to check for the existence of display port that is not wired in.

I can reproduce the psb issue and need to understand better how to resolve that.

Comment 4 Saul Wold 2015-05-04 21:58:56 UTC

The psb* errors can be ignored since the modesetting driver is used and is 
correct.

This bug is fixed with the lastest kernel and xserver.  While running xserver 
will generate an error in the Xorg.0.log reporting that psb or psb_drv is not 
found, this is not a problem since the modesetting driver will be used and is 
correct. This error can be ignored, it occurs since the out-sensing code is 
first looking for the psb or psb_drv modules.  When an xorg.conf file exists 
and defines a Device this autosensing is skipped.