Skip to contentSkip to conversation

nasty suspend resume problem with sandybridge

DISCUSSION Oleksij Rempel (fishor) 2 participants 9 messages Feb 4, 2012 – Feb 13, 2012

lore
Share & tools
lore
#1 lore raw
Quoted 5 lines · Oleksij Rempel (fishor)

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

Cheers, Daniel

Signature · 3 lines
Daniel Vetter
Mail: [email protected]
Mobile: +41 (0)79 365 57 48
#2 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 13.02.2012 11:18, schrieb Daniel Vetter:

Quoted 8 lines
Quoted 5 lines · Oleksij Rempel (fishor)

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

Quoted 8 lines

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?

- --
Regards,
Alexey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk846WwACgkQw8E0jNwoJm9aSACff98J6FRYmMFnGcBJgkWjvtHh 5RwAnRIgf//XDxyIhNLuIAtIJ1ouKKw+
=Dfzb
-----END PGP SIGNATURE-----

#3 lore raw
Quoted 30 lines · Oleksij Rempel (Alexey Fisher)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 13.02.2012 11:18, schrieb Daniel Vetter:

Quoted 8 lines
Quoted 5 lines · Oleksij Rempel (fishor)

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

Quoted 8 lines

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?

Quoted 2 lines

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

Signature · 3 lines
Daniel Vetter
Mail: [email protected]
Mobile: +41 (0)79 365 57 48
#4 lore raw

Am 13.02.2012 17:41, schrieb Daniel Vetter:

Quoted 31 lines · Oleksij Rempel (Alexey Fisher)
Quoted 30 lines

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 13.02.2012 11:18, schrieb Daniel Vetter:

Quoted 8 lines
Quoted 5 lines · Oleksij Rempel (fishor)

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

Quoted 8 lines

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?

Quoted 7 lines
Quoted 2 lines

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?

#5 lore raw
Quoted 35 lines · Oleksij Rempel (fishor)

Am 13.02.2012 17:41, schrieb Daniel Vetter:

Quoted 34 lines · Oleksij Rempel (Alexey Fisher)
Quoted 32 lines

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 13.02.2012 11:18, schrieb Daniel Vetter:

Quoted 8 lines
Quoted 5 lines · Oleksij Rempel (fishor)

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

Quoted 8 lines

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?

Quoted 8 lines
Quoted 4 lines

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?

Well, if you've checked that none of the i915, drm and intel-agp modules are loaded with lsmod there really shouldn't be any difference cause by modeset or nomodeset. I.e. if that's the case, your black screen is cause by a suspend/resume failure caused by another driver. -Daniel

Signature · 2 lines
Daniel Vetter
[email protected] - +41 (0) 79 364 57 48 - http://blog.ffwll.ch
#6 lore raw

Am 13.02.2012 18:06, schrieb Daniel Vetter:

Quoted 46 lines
Quoted 35 lines · Oleksij Rempel (fishor)

Am 13.02.2012 17:41, schrieb Daniel Vetter:

Quoted 34 lines · Oleksij Rempel (Alexey Fisher)
Quoted 32 lines

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 13.02.2012 11:18, schrieb Daniel Vetter:

Quoted 8 lines
Quoted 5 lines · Oleksij Rempel (fishor)

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

Quoted 8 lines

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?

Quoted 8 lines
Quoted 4 lines

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?

Quoted 5 lines

Well, if you've checked that none of the i915, drm and intel-agp modules are loaded with lsmod there really shouldn't be any difference cause by modeset or nomodeset. I.e. if that's the case, your black screen is cause by a suspend/resume failure caused by another driver. -Daniel

ufff... again not understood.

Quoted 1 line
Quoted 1 line
Quoted 1 line

i know this issue isn't fault of intel graphic <<<

with my older intel laptop i was able to get oops trace in such case. With new intel hardware i get blank screen with cursor in left top corner.

Quoted 1 line
Quoted 1 line
Quoted 1 line

Instead of cursor i expect oops trace! <<<

Is it possible? If not please say so. If yes, then is is a bug.

Signature · 2 lines
Regards,
Alexey
#7 lore raw
Quoted 9 lines · Oleksij Rempel (Alexey Fisher)

Am 13.02.2012 18:06, schrieb Daniel Vetter:

Quoted 5 lines

Well, if you've checked that none of the i915, drm and intel-agp modules are loaded with lsmod there really shouldn't be any difference cause by modeset or nomodeset. I.e. if that's the case, your black screen is cause by a suspend/resume failure caused by another driver. -Daniel

ufff... again not understood.

Quoted 7 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line

i know this issue isn't fault of intel graphic <<<

with my older intel laptop i was able to get oops trace in such case. With new intel hardware i get blank screen with cursor in left top corner.

Quoted 1 line
Quoted 1 line
Quoted 1 line

Instead of cursor i expect oops trace! <<<

Is it possible? If not please say so. If yes, then is is a bug.

Well, I'm not a suspend/resume expert, so I don't quite know whether you should get an oops. Also the bios might do funky stuff or the suspend/resume ordering changed meanwhile. So I have no idea :( -Daniel

Signature · 3 lines
Daniel Vetter
Mail: [email protected]
Mobile: +41 (0)79 365 57 48
#8 lore raw

Am 13.02.2012 19:52, schrieb Daniel Vetter:

Quoted 17 lines
Quoted 15 lines · Oleksij Rempel (Alexey Fisher)

Am 13.02.2012 18:06, schrieb Daniel Vetter:

Quoted 5 lines

Well, if you've checked that none of the i915, drm and intel-agp modules are loaded with lsmod there really shouldn't be any difference cause by modeset or nomodeset. I.e. if that's the case, your black screen is cause by a suspend/resume failure caused by another driver. -Daniel

ufff... again not understood.

Quoted 1 line
Quoted 1 line
Quoted 1 line

i know this issue isn't fault of intel graphic <<<

with my older intel laptop i was able to get oops trace in such case. With new intel hardware i get blank screen with cursor in left top corner.

Quoted 7 lines
Quoted 2 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line

Instead of cursor i expect oops trace! <<<

Is it possible? If not please say so. If yes, then is is a bug.

Well, I'm not a suspend/resume expert, so I don't quite know whether you should get an oops. Also the bios might do funky stuff or the suspend/resume ordering changed meanwhile. So I have no idea :( -Daniel

ok, thx.
then i will need to look for other way to get some debug info. I have this port on my laptop:
https://bugzilla.kernel.org/attachment.cgi?id=72351
do you accidental know some thing about it?

Signature · 2 lines
Regards,
Alexey