firmware-testing-team team mailing list archive

[Chris Van Hoof <vanhoof@xxxxxxxxxxxxx>]

On 09/24/2012 02:21 PM, Colin Ian King wrote:
> On 24/09/12 14:11, Brendan Donegan wrote:
>> On 20/09/12 16:57, Jeff Lane wrote:
>>>
>>>
>>>
>>> -------- Original Message --------
>>> Subject: Re: [Firmware-testing-team] Using FWTS for Certification
>>> Date: Wed, 19 Sep 2012 17:27:37 +0100
>>> From: Colin Ian King <colin.king@xxxxxxxxxxxxx>
>>> To: firmware-testing-team@xxxxxxxxxxxxxxxxxxx
>>>
>>> On 19/09/12 16:19, Brendan Donegan wrote:
>>>> (I hope this is the right mailing list)
>>>>
>>>> Hi,
>>>>
>>>> In Hardware Certification we have adopted FWTS for testing power
>>>> management (amongst other things), including S3, shutdown and
>>>> reboot. At
>>>> the moment it is giving us a few issues because FWTS is quite strict
>>>> about how it checks for kernel warnings and other issues. For Hardware
>>>> Certification we need to be less strict, but without ignoring any
>>>> problems which might be worthy of preventing the systems from being
>>>> certified. The purpose of this email is to kick off a dialogue about
>>>> which errors we really need to pay attention to for certification.
>>>
>>> Can you elaborate a little more about the features that are causing you
>>> problems and which ones are useful?  Maybe some examples too?
>> I'm working my way through all the failures we've seen, but just to get
>> the ball rolling, I offer this one as an example:
>>
>>      1. 00054 summary         High failures: 1
>>      2. 00055 summary          klog test, at 1 log line: 15
>>      3. 00056 summary           "HIGH Kernel message: [ 1918.822903]
>>         [Firmware Bug]: ACPI: No _BQC method, cannot determine initial
>>         brightness"
>>
>>
>> Seen when running reboot tests. I assume the net effect of this bug
>> would be to reset the brightness upon every boot? Or would it break the
>> brightness control completely?
> 
> It depends on the machine, but probably it may be the underlying reason
> why brightness controls are not working correctly.  The kernel certainly
> wasn't happy, it complained about it, so it needs investigating.
> 
> I'm not sure which version of fwts you are using, but it should produce
> some advice like:

This may be the version in Precise, if so is that advice in Quantal? ...
All the more reason to push for the Precise SRU imo :)

> _BQC (Brightness Query Current level) seems to be missing. This method
> returns the current brightness level of a built-in display output device.
> 
> 
> 
> 
> 
>>>
>>> Colin
>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~firmware-testing-team
>>>> Post to     : firmware-testing-team@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~firmware-testing-team
>>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~firmware-testing-team
>>> Post to     : firmware-testing-team@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~firmware-testing-team
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~firmware-testing-team
>> Post to     : firmware-testing-team@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~firmware-testing-team
>> More help   : https://help.launchpad.net/ListHelp
>>
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~firmware-testing-team
> Post to     : firmware-testing-team@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~firmware-testing-team
> More help   : https://help.launchpad.net/ListHelp
>