linux-kernel - RE: [Intel-gift] Linux 3.10-rc7

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-next>] [day] [month] [year] [list]

Message-ID: <5B8DA87D05A7694D9FA63FD143655C1B028E5075@HASMSX106.ger.corp.intel.com>
Date:	Wed, 10 Jul 2013 15:17:31 +0000
From:	"Winkler, Tomas" <tomas.winkler@...el.com>
To:	Shuah Khan <shuah.kh@...sung.com>
CC:	Daniel Vetter <daniel.vetter@...ll.ch>,
	intel-gfx <intel-gfx@...ts.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"shuahkhan@...il.com" <shuahkhan@...il.com>,
	Dave Airlie <airlied@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"rjw@...k.pl" <rjw@...k.pl>
Subject: RE: [Intel-gift] Linux 3.10-rc7

> > suspend complete.
> >
> > I can start bi-sect of this problem on intel-display scope if you
> > would like me to. Please let me know if the bisect scope should be larger.
> >
> > -- Shuah
> 
> I got finally an older system where this reproduces consistently, I'm trying to
> root cause that now.
> As soon I have something to test I will send it out.
>

I'm not sure why but I'm not able to get the interrupt from the device until all the devices has resumed after that the mei reset is successful and device work as expected.
I need to fix the state machine so the reset won't go crazy on resetting  actually I did that and it reduces resets into two but I'm still trying to figure out what's going on.
The regression coming from the fact that I've linearize the reset flow, it waits for interrupt to arrive, before that the flow gave up and  has restarted directly from the interrupt thread.

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/