On 02/09/2015 03:24 PM, Winkler, Tomas wrote:
> 
> 
>>
>> On Tue, Feb 10, 2015 at 05:37:36AM +0800, Greg Kroah-Hartman wrote:
>>> On Mon, Feb 09, 2015 at 11:27:10AM -0700, Shuah Khan wrote:
>>>> On 02/09/2015 01:33 AM, Greg Kroah-Hartman wrote:
>>>>> This is the start of the stable review cycle for the 3.18.7 release.
>>>>> There are 39 patches in this series, all will be posted as a response
>>>>> to this one.  If anyone has any issues with these being applied, please
>>>>> let me know.
>>>>>
>>>>> Responses should be made by Wed Feb 11 08:33:11 UTC 2015.
>>>>> Anything received after that time might be too late.
>>>>>
>>>>> The whole patch series can be found in one patch at:
>>>>> 	kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.18.7-rc1.gz
>>>>> and the diffstat can be found below.
>>>>>
>>>>> thanks,
>>>>>
>>>>> greg k-h
>>>>>
>>>>
>>>> Compiled and booted on my test system.
>>>>
>>>> I am seeing the following mei_me messages:
>>>>
>>>> mei_me 0000:00:16.0: version message write failed: ret = -5
>>>> mei_me 0000:00:16.0: hbm_start failed ret = -5
>>>> mei_me 0000:00:16.0: version message write failed: ret = -5
>>>> mei_me 0000:00:16.0: hbm_start failed ret = -5
>>>>
>>>> Not concerned - maybe Alexander Usyskin and Tomas Winkler
>>>> can take a look and see if this looks ok.
>>>>
>>>> Could this be related to:
>>>>
>>>> mei: clean reset bit before reset
>>>>
>>>> commit b13a65ef190e488e2761d65bdd2e1fe8a3a125f5 upstream.
>>>
>>> Odd, I wouldn't think that this commit would cause those errors to show
>>> up, if so, that's not good.
>>>
>>> Alexander, any thoughts?
>>>
>> mei_hbm_reset() is called just before the above message. Maybe the reset is not
>> complete ? The comment associated with the commit suggests that this can
>> happen.
>> If so, there should also be warning "H_RST is set = 0x%08X" in the log.
> 
> Can you please provide details of your system + lspci -vn output 
> The complete log would helpful and if you can enable dynamic debug on mei and mei_me modules it would be the best.
> 
> Thanks
> Tomas
> 

Hi Tomas,

Please see attached dmidecode output, the original dmesg from when
I saw the problem, and dmesg after enabling dynamic debug on mei.
I can't reproduce the problem with dynamic debug enabled, tried a
couple of reboots.

Please let me know you need more information.

thanks,
-- Shuah


-- 
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@osg.samsung.com | (970) 217-8978