From: "Oleksij Rempel (fishor)" <bug-track@fisher-privat.net>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: nasty suspend resume problem with sandybridge
Date: Mon, 13 Feb 2012 17:53:19 +0100 [thread overview]
Message-ID: <4F393FFF.7050608@fisher-privat.net> (raw)
In-Reply-To: <20120213164106.GH5301@phenom.ffwll.local>
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?
next prev parent reply other threads:[~2012-02-13 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-04 18:17 nasty suspend resume problem with sandybridge Oleksij Rempel (fishor)
2012-02-13 10:18 ` Daniel Vetter
2012-02-13 10:44 ` Oleksij Rempel (Alexey Fisher)
2012-02-13 16:41 ` Daniel Vetter
2012-02-13 16:53 ` Oleksij Rempel (fishor) [this message]
2012-02-13 17:06 ` Daniel Vetter
2012-02-13 18:42 ` Oleksij Rempel (Alexey Fisher)
2012-02-13 18:52 ` Daniel Vetter
2012-02-13 20:12 ` Oleksij Rempel (Alexey Fisher)
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=4F393FFF.7050608@fisher-privat.net \
--to=bug-track@fisher-privat.net \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox