From: Eugene Shatokhin <eugene.shatokhin@rosalab.ru>
To: "Winkler, Tomas" <tomas.winkler@intel.com>,
"Usyskin, Alexander" <alexander.usyskin@intel.com>
Cc: "Nicolò Costanza" <abitrules@yahoo.it>,
"Alex Burmashev" <alex.burmashev@rosalab.ru>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: mei: cancel stall timers in mei_reset
Date: Tue, 05 Nov 2013 19:06:48 +0400 [thread overview]
Message-ID: <52790988.3090101@rosalab.ru> (raw)
In-Reply-To: <5B8DA87D05A7694D9FA63FD143655C1B1AF03AB6@HASMSX106.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1857 bytes --]
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
[-- Attachment #2: system_log_20131105.tar.bz2 --]
[-- Type: application/x-bzip, Size: 31901 bytes --]
next prev parent reply other threads:[~2013-11-05 15:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 12:27 mei: cancel stall timers in mei_reset Eugene Shatokhin
2013-11-03 7:53 ` Winkler, Tomas
2013-11-04 15:48 ` Eugene Shatokhin
2013-11-05 8:07 ` Eugene Shatokhin
2013-11-05 9:58 ` Usyskin, Alexander
2013-11-05 11:46 ` Eugene Shatokhin
2013-11-05 11:49 ` Winkler, Tomas
2013-11-05 15:06 ` Eugene Shatokhin [this message]
2013-11-06 7:13 ` Eugene Shatokhin
2013-11-06 20:03 ` Winkler, Tomas
2013-11-07 6:37 ` Eugene Shatokhin
2013-11-07 12:52 ` Winkler, Tomas
2013-11-09 18:20 ` Eugene Shatokhin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52790988.3090101@rosalab.ru \
--to=eugene.shatokhin@rosalab.ru \
--cc=abitrules@yahoo.it \
--cc=alex.burmashev@rosalab.ru \
--cc=alexander.usyskin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas.winkler@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.