From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Oleksij Rempel (fishor)" Subject: Re: nasty suspend resume problem with sandybridge Date: Mon, 13 Feb 2012 17:53:19 +0100 Message-ID: <4F393FFF.7050608@fisher-privat.net> References: <4F2D761D.8000506@fisher-privat.net> <20120213101804.GE5301@phenom.ffwll.local> <4F38E970.6050504@fisher-privat.net> <20120213164106.GH5301@phenom.ffwll.local> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by gabe.freedesktop.org (Postfix) with SMTP id 6D4219E7E7 for ; Mon, 13 Feb 2012 08:53:24 -0800 (PST) In-Reply-To: <20120213164106.GH5301@phenom.ffwll.local> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Daniel Vetter Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org Am 13.02.2012 17:41, schrieb Daniel Vetter: > On Mon, Feb 13, 2012 at 11:44:00AM +0100, Oleksij Rempel (Alexey Fisher) wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Am 13.02.2012 11:18, schrieb Daniel Vetter: >>> On Sat, Feb 04, 2012 at 07:17:01PM +0100, Oleksij Rempel (fishor) >>> wrote: >>>> i do not know if this is really graphic related problem, so i >>>> need your help. even excluding some thing will help. >>>> >>>> Please take look at this bug: >>>> https://bugzilla.kernel.org/show_bug.cgi?id=42728 >>> >>> Judging from your ehci workaround I think your suspend/resume issue >>> is not i915 related. You mention though somewhere that you also >>> experience memory corruption issues after hibernat (assuming I've >>> read the comments correctly). We are aware of memory corruptions >>> issues due to i915.ko when hibernating, unfortunately no one has >>> yet root-caused this. See e.g. >>> >>> https://bugs.freedesktop.org/show_bug.cgi?id=35648 >> >> thx, for the response. >> >> unfortunately this memory corruption appears not in S4, but after >> filed S3. >> Looks like some part entered S3 state and never come back, even after >> poweroff. I think it, because in some cases power-led blinking after >> poweroff - which indicate S3 state. Are there any thing to check to >> see what is misconfigured? >> >> I agree, that i915 is not the reason of this problem, but i915 make it >> impossible to get oops trace! Any chance to get it work? > > As already mentioned by Jesse in the bugzilla, just blacklist it. We don't > really support nomodeset (because for things like suspend/resume it's > actually impossible to properly support). > -Daniel I did response on the bugzilla - blacklisting the module do not help. i get just black screen, no oops trace. Are there any way to get trace with modeset?