lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52790988.3090101@rosalab.ru>
Date:	Tue, 05 Nov 2013 19:06:48 +0400
From:	Eugene Shatokhin <eugene.shatokhin@...alab.ru>
To:	"Winkler, Tomas" <tomas.winkler@...el.com>,
	"Usyskin, Alexander" <alexander.usyskin@...el.com>
CC:	Nicolò Costanza <abitrules@...oo.it>,
	Alex Burmashev <alex.burmashev@...alab.ru>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: mei: cancel stall timers in mei_reset

On 11/05/2013 03:49 PM, Winkler, Tomas wrote:
> This patches only catch the error, our goal is to discover why it is failing.

I have just applied these error-handling-related patches to kernel 
3.10.15 (without commenting out schedule_delayed_work(&dev->timer_work, 
HZ) yet) and checked the system again.

The full log is attached, the config is the same as I sent before.

Here are MEI-related messages from there:

---------------------------------------
[    1.011579] mei_me 0000:00:16.0: setting latency timer to 64
[    1.011616] mei_me 0000:00:16.0: irq 40 for MSI/MSI-X
[  215.552616] mei_me 0000:00:16.0: suspend
[  216.675402] mei_me 0000:00:16.0: irq 40 for MSI/MSI-X
[  250.390001] mei_me 0000:00:16.0: suspend
[  251.519709] mei_me 0000:00:16.0: irq 40 for MSI/MSI-X
[  289.780943] mei_me 0000:00:16.0: suspend
[  290.781338] mei_me 0000:00:16.0: irq 40 for MSI/MSI-X
[  319.506298] mei_me 0000:00:16.0: suspend
[  320.503153] mei_me 0000:00:16.0: irq 40 for MSI/MSI-X
[  348.110390] mei_me 0000:00:16.0: suspend
[  348.958731] mei_me 0000:00:16.0: irq 40 for MSI/MSI-X
[  386.344351] mei_me 0000:00:16.0: suspend
[  387.461297] mei_me 0000:00:16.0: irq 40 for MSI/MSI-X
[  387.513101] mei_me 0000:00:16.0: reset: properties response hbm wrong 
status.
[  387.513104] mei_me 0000:00:16.0: unexpected reset: dev_state = 
INIT_CLIENTS
[  394.514883] mei_me 0000:00:16.0: wait hw ready failed. status = -110
[  394.514890] mei_me 0000:00:16.0: hw_start failed disabling the device
---------------------------------------

No message flood anymore, which is good, but you are right, the problem 
seems to be somewhere deeper.

As far as kernel 3.11.6 is concerned, I see no message flood there but 
"wait hw ready failed. status = -110" is in the log, same as for 3.10.15.

Regards,
Eugene

-- 
Eugene Shatokhin, ROSA Laboratory.
www.rosalab.com

Download attachment "system_log_20131105.tar.bz2" of type "application/x-bzip" (31901 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ