[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5B8DA87D05A7694D9FA63FD143655C1B028DB36B@HASMSX106.ger.corp.intel.com>
Date: Wed, 26 Jun 2013 22:11:13 +0000
From: "Winkler, Tomas" <tomas.winkler@...el.com>
To: Shuah Khan <shuah.kh@...sung.com>
CC: Jesse Barnes <jbarnes@...tuousgeek.org>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Chris Wilson <chris@...is-wilson.co.uk>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"shuahkhan@...il.com" <shuahkhan@...il.com>,
Dave Airlie <airlied@...hat.com>,
intel-gfx <intel-gfx@...ts.freedesktop.org>
Subject: RE: Linux 3.10-rc7
> > Can you please send me the log part when this starts?
> >
> > Thanks
> >
>
> It rolled over and I don't have prior messages. I tried reproducing twice and
> didn't see it again. I will try a few more times and see if I can get it to happen
> again.
>
> This is what I could save before dmesg rolled over:
>
> [ 78.709014] mei_me 0000:00:16.0: reset: wrong host start response
> [ 78.709016] mei_me 0000:00:16.0: unexpected reset: dev_state =
> RESETTING
> [ 78.709029] mei_me 0000:00:16.0: reset: unexpected enumeration
> response hbm.
> [ 78.709031] mei_me 0000:00:16.0: unexpected reset: dev_state =
> RESETTING
> [ 78.709069] mei_me 0000:00:16.0: reset: wrong host start response
>
So far I was able to positively reproduce it with 3.10-rc5 but not with 3.10-rc7 and above.
There are 3 patches that went in to fix this issue
42f132f mei: me: clear interrupts on the resume path
2753ff5 mei: nfc: fix nfc device freeing
5e85b36 mei: init: Flush scheduled work before resetting the device
Are you sure you have these 3 in?
Thanks
Tomas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists