Resuming Linux from hibernate on ThinkPad X220 fails with black screen or reboot
I have installed Debian 8 with sysvinit and Xfce on a ThinkPad X220. The video card is Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)/Integrated Graphics Chipset: Intel(R) HD Graphics 3000. Kernel versions available to me are 4.7 from backports and 3.16 (heavily patched by Canonical kernel team) from stable.
When I hibernate using pure kernel (echo disk > /sys/power/state done by pm-hibernate run by xfce4-pm-helper) and XScreenSaver turns the screen off, on resume the screen is still turned off (not just the backlight: I checked with a flashlight), and nothing seems to turn it on again (I tried Ctrl+Alt+F* suggested at ThinkWiki and Alt+SysRq+V), but the remaining system seems to be working (at least, when I do an Alt+SysRq+E,I,S,U,B, I can find messages from a successful resume and syslogd being terminated by signal 15 in /var/log/syslog).
I'm able to connect via ssh, but both chvt 1; chvt 7 and various combinations of export DISPLAY=:0; xrandr --output LVDS1 --off; xrandr --output LVDS1 --auto do nothing. I disabled LVDS1 and tried to reenable it, I got: xrandr: Configure crtc 0 failed and the following lines in dmesg:
[ 390.432051] [drm:drm_framebuffer_remove [drm]] *ERROR* failed to reset crtc ffff9ae6caa2f000 when fb was deleted
[ 390.432066] [drm:drm_plane_force_disable [drm]] *ERROR* failed to disable plane with busy fb
Some people suggested ddccontrol, but it doesn't detect DDC on my system. Is screen is on while hibernating, it stays working after resume.
If I install uswsusp, hibernate works (as a bonus, I get some form of compression and ability to cancel hibernating at the last second), but only most of the time. The usual resume procedure looks like this:
resume: Loading image data pages(in default video mode)- Video mode is switched to native resolution, screen is filled with noise (full screen when EFI-booting, a small horizontal stripe on the top when BIOS-booting)
- Loud click from speakers, screen momentarily turns black with
s2disk: returned to userspace, then I get my XScreenSaver lock dialog.
Sooner or later, right after the Loading data pages screen turns black and the laptop resets (I see the BIOS boot logo).
I installed grub-efi on a thumbdrive (to avoid repartitioning) for the sake of efi-backed pstore. For a week, I hibernated and resumed the laptop once or twice per day without problems and almost beleived that EFI has solved the problem, but then the failure occured again, and no logs were found in /sys/fs/pstore (pstore: Registered efi as persistent store backend is visible in dmesg). I think that when resuming successfully for the last time before the next one failed the screen was not fully filled with noise and a black stripe was wisible on the bottom before I got returned to userspace and X screen back.
As far as I know, suspend to RAM works flawlessly both with echo mem > /sys/power/state and s2ram. I do that more frequently than hibernating (several times per day) and so far, no glitches have occured.
For now, I set up XScreenSaver to never turn the screen off, thus preventing the most common cause of the failure (XScreenSaver locking and turning screen off before hibernation), but I'm still able to encounter the glitch by closing the lid fast enough after choosing "hibernate".
UPD: I've been using pure kernel hibernate for some time now, and I've just encountered the same reset after loading saved image which has been happening to me when using uswsusp. Apparently I've never used it on this X220 for long enough for it to happen before. So, as it turns out, I have no reliable ways to hibernate: both echo disk > /sys/power/state and s2disk fail after 5-7 hibernations, but pure kernel doesn't restore video card state properly, too.
What else can I try to make some form of hibernate working?
linux debian hibernate sysvinit thinkpad
edited Feb 27 '17 at 10:56
Stephen Kitt
171k24386462
asked Dec 3 '16 at 11:29
aitapaitap
56838
bumped to the homepage by Community♦ 3 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
|
show 1 more comment
I have installed Debian 8 with sysvinit and Xfce on a ThinkPad X220. The video card is Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)/Integrated Graphics Chipset: Intel(R) HD Graphics 3000. Kernel versions available to me are 4.7 from backports and 3.16 (heavily patched by Canonical kernel team) from stable.
When I hibernate using pure kernel (echo disk > /sys/power/state done by pm-hibernate run by xfce4-pm-helper) and XScreenSaver turns the screen off, on resume the screen is still turned off (not just the backlight: I checked with a flashlight), and nothing seems to turn it on again (I tried Ctrl+Alt+F* suggested at ThinkWiki and Alt+SysRq+V), but the remaining system seems to be working (at least, when I do an Alt+SysRq+E,I,S,U,B, I can find messages from a successful resume and syslogd being terminated by signal 15 in /var/log/syslog).
I'm able to connect via ssh, but both chvt 1; chvt 7 and various combinations of export DISPLAY=:0; xrandr --output LVDS1 --off; xrandr --output LVDS1 --auto do nothing. I disabled LVDS1 and tried to reenable it, I got: xrandr: Configure crtc 0 failed and the following lines in dmesg:
[ 390.432051] [drm:drm_framebuffer_remove [drm]] *ERROR* failed to reset crtc ffff9ae6caa2f000 when fb was deleted
[ 390.432066] [drm:drm_plane_force_disable [drm]] *ERROR* failed to disable plane with busy fb
Some people suggested ddccontrol, but it doesn't detect DDC on my system. Is screen is on while hibernating, it stays working after resume.
If I install uswsusp, hibernate works (as a bonus, I get some form of compression and ability to cancel hibernating at the last second), but only most of the time. The usual resume procedure looks like this:
resume: Loading image data pages(in default video mode)- Video mode is switched to native resolution, screen is filled with noise (full screen when EFI-booting, a small horizontal stripe on the top when BIOS-booting)
- Loud click from speakers, screen momentarily turns black with
s2disk: returned to userspace, then I get my XScreenSaver lock dialog.
Sooner or later, right after the Loading data pages screen turns black and the laptop resets (I see the BIOS boot logo).
I installed grub-efi on a thumbdrive (to avoid repartitioning) for the sake of efi-backed pstore. For a week, I hibernated and resumed the laptop once or twice per day without problems and almost beleived that EFI has solved the problem, but then the failure occured again, and no logs were found in /sys/fs/pstore (pstore: Registered efi as persistent store backend is visible in dmesg). I think that when resuming successfully for the last time before the next one failed the screen was not fully filled with noise and a black stripe was wisible on the bottom before I got returned to userspace and X screen back.
As far as I know, suspend to RAM works flawlessly both with echo mem > /sys/power/state and s2ram. I do that more frequently than hibernating (several times per day) and so far, no glitches have occured.
For now, I set up XScreenSaver to never turn the screen off, thus preventing the most common cause of the failure (XScreenSaver locking and turning screen off before hibernation), but I'm still able to encounter the glitch by closing the lid fast enough after choosing "hibernate".
UPD: I've been using pure kernel hibernate for some time now, and I've just encountered the same reset after loading saved image which has been happening to me when using uswsusp. Apparently I've never used it on this X220 for long enough for it to happen before. So, as it turns out, I have no reliable ways to hibernate: both echo disk > /sys/power/state and s2disk fail after 5-7 hibernations, but pure kernel doesn't restore video card state properly, too.
What else can I try to make some form of hibernate working?
linux debian hibernate sysvinit thinkpad
edited Feb 27 '17 at 10:56
Stephen Kitt
171k24386462
asked Dec 3 '16 at 11:29
aitapaitap
56838
bumped to the homepage by Community♦ 3 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
1
I would try stretch first before losing much sleep debugging complicated problems with Jessie.
– Rui F Ribeiro
Dec 3 '16 at 12:53
I'm already using kernel 4.7 from backports. I will try 4.8 from stretch, but I'm not sure how it should make a difference on 2011 hardware.
– aitap
Dec 4 '16 at 11:34
1
Granted, but I would prefer 1) to use new and improved versions of software (could it be luckily a bug already ironed out? who knows) 2) To debug already the problem for Strech which is getting out in a matter of weeks.
– Rui F Ribeiro
Dec 4 '16 at 11:37
1
Oh well. Kernel 4.8, hibernating without uswsusp. 1) xfce4-session-logout --hibernate - works OK 2) Fn+F12 (hibernate button): screen blanks before suspend (XScreenSaver lock in action), completely turned off on resume.
– aitap
Dec 4 '16 at 12:51
I have similar behavior when i close the lid in my Debian Sid with LXDE ( screen saver disabled). In my case , my pc was not actually hybernating. It was just the screen who goes black and refuse to light up again if i lift the lide. Ugly Solution in my case: Switch to tty1 (ctrl-alt-1) and back to tty7 (ctrl-alt-7) wakes up my screen and i can keep working.
– George Vasiliou
Dec 7 '16 at 9:04
|
show 1 more comment
I have installed Debian 8 with sysvinit and Xfce on a ThinkPad X220. The video card is Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)/Integrated Graphics Chipset: Intel(R) HD Graphics 3000. Kernel versions available to me are 4.7 from backports and 3.16 (heavily patched by Canonical kernel team) from stable.
When I hibernate using pure kernel (echo disk > /sys/power/state done by pm-hibernate run by xfce4-pm-helper) and XScreenSaver turns the screen off, on resume the screen is still turned off (not just the backlight: I checked with a flashlight), and nothing seems to turn it on again (I tried Ctrl+Alt+F* suggested at ThinkWiki and Alt+SysRq+V), but the remaining system seems to be working (at least, when I do an Alt+SysRq+E,I,S,U,B, I can find messages from a successful resume and syslogd being terminated by signal 15 in /var/log/syslog).
I'm able to connect via ssh, but both chvt 1; chvt 7 and various combinations of export DISPLAY=:0; xrandr --output LVDS1 --off; xrandr --output LVDS1 --auto do nothing. I disabled LVDS1 and tried to reenable it, I got: xrandr: Configure crtc 0 failed and the following lines in dmesg:
[ 390.432051] [drm:drm_framebuffer_remove [drm]] *ERROR* failed to reset crtc ffff9ae6caa2f000 when fb was deleted
[ 390.432066] [drm:drm_plane_force_disable [drm]] *ERROR* failed to disable plane with busy fb
Some people suggested ddccontrol, but it doesn't detect DDC on my system. Is screen is on while hibernating, it stays working after resume.
If I install uswsusp, hibernate works (as a bonus, I get some form of compression and ability to cancel hibernating at the last second), but only most of the time. The usual resume procedure looks like this:
resume: Loading image data pages(in default video mode)- Video mode is switched to native resolution, screen is filled with noise (full screen when EFI-booting, a small horizontal stripe on the top when BIOS-booting)
- Loud click from speakers, screen momentarily turns black with
s2disk: returned to userspace, then I get my XScreenSaver lock dialog.
Sooner or later, right after the Loading data pages screen turns black and the laptop resets (I see the BIOS boot logo).
I installed grub-efi on a thumbdrive (to avoid repartitioning) for the sake of efi-backed pstore. For a week, I hibernated and resumed the laptop once or twice per day without problems and almost beleived that EFI has solved the problem, but then the failure occured again, and no logs were found in /sys/fs/pstore (pstore: Registered efi as persistent store backend is visible in dmesg). I think that when resuming successfully for the last time before the next one failed the screen was not fully filled with noise and a black stripe was wisible on the bottom before I got returned to userspace and X screen back.
As far as I know, suspend to RAM works flawlessly both with echo mem > /sys/power/state and s2ram. I do that more frequently than hibernating (several times per day) and so far, no glitches have occured.
For now, I set up XScreenSaver to never turn the screen off, thus preventing the most common cause of the failure (XScreenSaver locking and turning screen off before hibernation), but I'm still able to encounter the glitch by closing the lid fast enough after choosing "hibernate".
UPD: I've been using pure kernel hibernate for some time now, and I've just encountered the same reset after loading saved image which has been happening to me when using uswsusp. Apparently I've never used it on this X220 for long enough for it to happen before. So, as it turns out, I have no reliable ways to hibernate: both echo disk > /sys/power/state and s2disk fail after 5-7 hibernations, but pure kernel doesn't restore video card state properly, too.
What else can I try to make some form of hibernate working?
linux debian hibernate sysvinit thinkpad
edited Feb 27 '17 at 10:56
Stephen Kitt
171k24386462
asked Dec 3 '16 at 11:29
aitapaitap
56838
I have installed Debian 8 with sysvinit and Xfce on a ThinkPad X220. The video card is Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)/Integrated Graphics Chipset: Intel(R) HD Graphics 3000. Kernel versions available to me are 4.7 from backports and 3.16 (heavily patched by Canonical kernel team) from stable.
When I hibernate using pure kernel (echo disk > /sys/power/state done by pm-hibernate run by xfce4-pm-helper) and XScreenSaver turns the screen off, on resume the screen is still turned off (not just the backlight: I checked with a flashlight), and nothing seems to turn it on again (I tried Ctrl+Alt+F* suggested at ThinkWiki and Alt+SysRq+V), but the remaining system seems to be working (at least, when I do an Alt+SysRq+E,I,S,U,B, I can find messages from a successful resume and syslogd being terminated by signal 15 in /var/log/syslog).
I'm able to connect via ssh, but both chvt 1; chvt 7 and various combinations of export DISPLAY=:0; xrandr --output LVDS1 --off; xrandr --output LVDS1 --auto do nothing. I disabled LVDS1 and tried to reenable it, I got: xrandr: Configure crtc 0 failed and the following lines in dmesg:
[ 390.432051] [drm:drm_framebuffer_remove [drm]] *ERROR* failed to reset crtc ffff9ae6caa2f000 when fb was deleted
[ 390.432066] [drm:drm_plane_force_disable [drm]] *ERROR* failed to disable plane with busy fb
Some people suggested ddccontrol, but it doesn't detect DDC on my system. Is screen is on while hibernating, it stays working after resume.
If I install uswsusp, hibernate works (as a bonus, I get some form of compression and ability to cancel hibernating at the last second), but only most of the time. The usual resume procedure looks like this:
resume: Loading image data pages(in default video mode)- Video mode is switched to native resolution, screen is filled with noise (full screen when EFI-booting, a small horizontal stripe on the top when BIOS-booting)
- Loud click from speakers, screen momentarily turns black with
s2disk: returned to userspace, then I get my XScreenSaver lock dialog.
Sooner or later, right after the Loading data pages screen turns black and the laptop resets (I see the BIOS boot logo).
I installed grub-efi on a thumbdrive (to avoid repartitioning) for the sake of efi-backed pstore. For a week, I hibernated and resumed the laptop once or twice per day without problems and almost beleived that EFI has solved the problem, but then the failure occured again, and no logs were found in /sys/fs/pstore (pstore: Registered efi as persistent store backend is visible in dmesg). I think that when resuming successfully for the last time before the next one failed the screen was not fully filled with noise and a black stripe was wisible on the bottom before I got returned to userspace and X screen back.
As far as I know, suspend to RAM works flawlessly both with echo mem > /sys/power/state and s2ram. I do that more frequently than hibernating (several times per day) and so far, no glitches have occured.
For now, I set up XScreenSaver to never turn the screen off, thus preventing the most common cause of the failure (XScreenSaver locking and turning screen off before hibernation), but I'm still able to encounter the glitch by closing the lid fast enough after choosing "hibernate".
UPD: I've been using pure kernel hibernate for some time now, and I've just encountered the same reset after loading saved image which has been happening to me when using uswsusp. Apparently I've never used it on this X220 for long enough for it to happen before. So, as it turns out, I have no reliable ways to hibernate: both echo disk > /sys/power/state and s2disk fail after 5-7 hibernations, but pure kernel doesn't restore video card state properly, too.
What else can I try to make some form of hibernate working?
linux debian hibernate sysvinit thinkpad
linux debian hibernate sysvinit thinkpad
edited Feb 27 '17 at 10:56
Stephen Kitt
171k24386462
asked Dec 3 '16 at 11:29
aitapaitap
56838
edited Feb 27 '17 at 10:56
Stephen Kitt
171k24386462
asked Dec 3 '16 at 11:29
aitapaitap
56838
edited Feb 27 '17 at 10:56
Stephen Kitt
171k24386462
edited Feb 27 '17 at 10:56
Stephen Kitt
171k24386462
edited Feb 27 '17 at 10:56
Stephen Kitt
171k24386462
171k24386462
asked Dec 3 '16 at 11:29
aitapaitap
56838
asked Dec 3 '16 at 11:29
aitapaitap
56838
asked Dec 3 '16 at 11:29
aitapaitap
56838
56838
bumped to the homepage by Community♦ 3 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 3 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
1
I would try stretch first before losing much sleep debugging complicated problems with Jessie.
– Rui F Ribeiro
Dec 3 '16 at 12:53
I'm already using kernel 4.7 from backports. I will try 4.8 from stretch, but I'm not sure how it should make a difference on 2011 hardware.
– aitap
Dec 4 '16 at 11:34
1
Granted, but I would prefer 1) to use new and improved versions of software (could it be luckily a bug already ironed out? who knows) 2) To debug already the problem for Strech which is getting out in a matter of weeks.
– Rui F Ribeiro
Dec 4 '16 at 11:37
1
Oh well. Kernel 4.8, hibernating without uswsusp. 1) xfce4-session-logout --hibernate - works OK 2) Fn+F12 (hibernate button): screen blanks before suspend (XScreenSaver lock in action), completely turned off on resume.
– aitap
Dec 4 '16 at 12:51
I have similar behavior when i close the lid in my Debian Sid with LXDE ( screen saver disabled). In my case , my pc was not actually hybernating. It was just the screen who goes black and refuse to light up again if i lift the lide. Ugly Solution in my case: Switch to tty1 (ctrl-alt-1) and back to tty7 (ctrl-alt-7) wakes up my screen and i can keep working.
– George Vasiliou
Dec 7 '16 at 9:04
|
show 1 more comment
1
I would try stretch first before losing much sleep debugging complicated problems with Jessie.
– Rui F Ribeiro
Dec 3 '16 at 12:53
I'm already using kernel 4.7 from backports. I will try 4.8 from stretch, but I'm not sure how it should make a difference on 2011 hardware.
– aitap
Dec 4 '16 at 11:34
1
Granted, but I would prefer 1) to use new and improved versions of software (could it be luckily a bug already ironed out? who knows) 2) To debug already the problem for Strech which is getting out in a matter of weeks.
– Rui F Ribeiro
Dec 4 '16 at 11:37
1
Oh well. Kernel 4.8, hibernating without uswsusp. 1) xfce4-session-logout --hibernate - works OK 2) Fn+F12 (hibernate button): screen blanks before suspend (XScreenSaver lock in action), completely turned off on resume.
– aitap
Dec 4 '16 at 12:51
I have similar behavior when i close the lid in my Debian Sid with LXDE ( screen saver disabled). In my case , my pc was not actually hybernating. It was just the screen who goes black and refuse to light up again if i lift the lide. Ugly Solution in my case: Switch to tty1 (ctrl-alt-1) and back to tty7 (ctrl-alt-7) wakes up my screen and i can keep working.
– George Vasiliou
Dec 7 '16 at 9:04
1
1
I would try stretch first before losing much sleep debugging complicated problems with Jessie.
– Rui F Ribeiro
Dec 3 '16 at 12:53
I would try stretch first before losing much sleep debugging complicated problems with Jessie.
– Rui F Ribeiro
Dec 3 '16 at 12:53
I'm already using kernel 4.7 from backports. I will try 4.8 from stretch, but I'm not sure how it should make a difference on 2011 hardware.
– aitap
Dec 4 '16 at 11:34
I'm already using kernel 4.7 from backports. I will try 4.8 from stretch, but I'm not sure how it should make a difference on 2011 hardware.
– aitap
Dec 4 '16 at 11:34
1
1
Granted, but I would prefer 1) to use new and improved versions of software (could it be luckily a bug already ironed out? who knows) 2) To debug already the problem for Strech which is getting out in a matter of weeks.
– Rui F Ribeiro
Dec 4 '16 at 11:37
Granted, but I would prefer 1) to use new and improved versions of software (could it be luckily a bug already ironed out? who knows) 2) To debug already the problem for Strech which is getting out in a matter of weeks.
– Rui F Ribeiro
Dec 4 '16 at 11:37
1
1
Oh well. Kernel 4.8, hibernating without uswsusp. 1) xfce4-session-logout --hibernate - works OK 2) Fn+F12 (hibernate button): screen blanks before suspend (XScreenSaver lock in action), completely turned off on resume.
– aitap
Dec 4 '16 at 12:51
Oh well. Kernel 4.8, hibernating without uswsusp. 1) xfce4-session-logout --hibernate - works OK 2) Fn+F12 (hibernate button): screen blanks before suspend (XScreenSaver lock in action), completely turned off on resume.
– aitap
Dec 4 '16 at 12:51
I have similar behavior when i close the lid in my Debian Sid with LXDE ( screen saver disabled). In my case , my pc was not actually hybernating. It was just the screen who goes black and refuse to light up again if i lift the lide. Ugly Solution in my case: Switch to tty1 (ctrl-alt-1) and back to tty7 (ctrl-alt-7) wakes up my screen and i can keep working.
– George Vasiliou
Dec 7 '16 at 9:04
I have similar behavior when i close the lid in my Debian Sid with LXDE ( screen saver disabled). In my case , my pc was not actually hybernating. It was just the screen who goes black and refuse to light up again if i lift the lide. Ugly Solution in my case: Switch to tty1 (ctrl-alt-1) and back to tty7 (ctrl-alt-7) wakes up my screen and i can keep working.
– George Vasiliou
Dec 7 '16 at 9:04
|
show 1 more comment
1 Answer
1
active
oldest
votes
With linux-image-amd64 version 4.8.0-0.bpo.2 from jessie-backports I've been s2disk-hibernating the X220 in question for 25 days with no mysterious reboot after loading image (I'm going to reboot now to upgrade the kernel to 4.9.0-0.bpo.1).
A bug report has been filed about the backlight issue, but is unlikely to receive activity, since s2disk method apparently works.
answered Feb 18 '17 at 20:17
aitapaitap
56838
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f327755%2fresuming-linux-from-hibernate-on-thinkpad-x220-fails-with-black-screen-or-reboot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
With linux-image-amd64 version 4.8.0-0.bpo.2 from jessie-backports I've been s2disk-hibernating the X220 in question for 25 days with no mysterious reboot after loading image (I'm going to reboot now to upgrade the kernel to 4.9.0-0.bpo.1).
A bug report has been filed about the backlight issue, but is unlikely to receive activity, since s2disk method apparently works.
answered Feb 18 '17 at 20:17
aitapaitap
56838
add a comment |
With linux-image-amd64 version 4.8.0-0.bpo.2 from jessie-backports I've been s2disk-hibernating the X220 in question for 25 days with no mysterious reboot after loading image (I'm going to reboot now to upgrade the kernel to 4.9.0-0.bpo.1).
A bug report has been filed about the backlight issue, but is unlikely to receive activity, since s2disk method apparently works.
answered Feb 18 '17 at 20:17
aitapaitap
56838
add a comment |
With linux-image-amd64 version 4.8.0-0.bpo.2 from jessie-backports I've been s2disk-hibernating the X220 in question for 25 days with no mysterious reboot after loading image (I'm going to reboot now to upgrade the kernel to 4.9.0-0.bpo.1).
A bug report has been filed about the backlight issue, but is unlikely to receive activity, since s2disk method apparently works.
answered Feb 18 '17 at 20:17
aitapaitap
56838
With linux-image-amd64 version 4.8.0-0.bpo.2 from jessie-backports I've been s2disk-hibernating the X220 in question for 25 days with no mysterious reboot after loading image (I'm going to reboot now to upgrade the kernel to 4.9.0-0.bpo.1).
A bug report has been filed about the backlight issue, but is unlikely to receive activity, since s2disk method apparently works.
answered Feb 18 '17 at 20:17
aitapaitap
56838
answered Feb 18 '17 at 20:17
aitapaitap
56838
answered Feb 18 '17 at 20:17
aitapaitap
56838
answered Feb 18 '17 at 20:17
aitapaitap
56838
56838
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f327755%2fresuming-linux-from-hibernate-on-thinkpad-x220-fails-with-black-screen-or-reboot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
I would try stretch first before losing much sleep debugging complicated problems with Jessie.
– Rui F Ribeiro
Dec 3 '16 at 12:53
I'm already using kernel 4.7 from backports. I will try 4.8 from stretch, but I'm not sure how it should make a difference on 2011 hardware.
– aitap
Dec 4 '16 at 11:34
1
Granted, but I would prefer 1) to use new and improved versions of software (could it be luckily a bug already ironed out? who knows) 2) To debug already the problem for Strech which is getting out in a matter of weeks.
– Rui F Ribeiro
Dec 4 '16 at 11:37
1
Oh well. Kernel 4.8, hibernating without uswsusp. 1) xfce4-session-logout --hibernate - works OK 2) Fn+F12 (hibernate button): screen blanks before suspend (XScreenSaver lock in action), completely turned off on resume.
– aitap
Dec 4 '16 at 12:51
I have similar behavior when i close the lid in my Debian Sid with LXDE ( screen saver disabled). In my case , my pc was not actually hybernating. It was just the screen who goes black and refuse to light up again if i lift the lide. Ugly Solution in my case: Switch to tty1 (ctrl-alt-1) and back to tty7 (ctrl-alt-7) wakes up my screen and i can keep working.
– George Vasiliou
Dec 7 '16 at 9:04