Ubuntu Server 17 can't suspend with systemctl
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
0
down vote
favorite
I installed an Ubuntu Server 17 but it seems I can't put it in sleep/suspend mode. When I use systemctl suspend
, HDD restarts several times, each time monitor blinks for a moment and multi-line message appears for a second and then original command line returns . the message is this:
dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -38
PM: device 0000:04:00.0 failed to suspend async: error -38
PM: Some devices failed to suspend, or early wake event detected
[drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fenece wait timed out.
[drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-110).
pci_legacy_suspend(): hpsa_suspend+0x0/0x10 [hpsa] returns -38
dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -38
By the way the HDD that restarts seems to be connected to a HP Array: P410
suspend radeon
add a comment |Â
up vote
0
down vote
favorite
I installed an Ubuntu Server 17 but it seems I can't put it in sleep/suspend mode. When I use systemctl suspend
, HDD restarts several times, each time monitor blinks for a moment and multi-line message appears for a second and then original command line returns . the message is this:
dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -38
PM: device 0000:04:00.0 failed to suspend async: error -38
PM: Some devices failed to suspend, or early wake event detected
[drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fenece wait timed out.
[drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-110).
pci_legacy_suspend(): hpsa_suspend+0x0/0x10 [hpsa] returns -38
dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -38
By the way the HDD that restarts seems to be connected to a HP Array: P410
suspend radeon
Ubuntu 17.04 crossed EOL in January. Please upgrade.
â Melebius
Apr 26 at 12:29
1
@Melebius I'm having a hard time understanding why ponsfrilus added the 17.04 tag to the question when there was no apparent reason to add it, so I have rollback-ed this question to the author's original unedited version.
â karel
Apr 26 at 13:09
of course i upgraded . this is what happens after the upgrade .
â Muhammad Riazi
Apr 26 at 20:56
I confirmed it , it is the problem with the p410 . by removing it i can suspend the system . but the hardware itself has no problem (or at least i don't think it has) because i worked with it in windows 7 and there was no problem there , so i think the problem must be something operating system-wise .
â Muhammad Riazi
Apr 27 at 15:20
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I installed an Ubuntu Server 17 but it seems I can't put it in sleep/suspend mode. When I use systemctl suspend
, HDD restarts several times, each time monitor blinks for a moment and multi-line message appears for a second and then original command line returns . the message is this:
dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -38
PM: device 0000:04:00.0 failed to suspend async: error -38
PM: Some devices failed to suspend, or early wake event detected
[drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fenece wait timed out.
[drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-110).
pci_legacy_suspend(): hpsa_suspend+0x0/0x10 [hpsa] returns -38
dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -38
By the way the HDD that restarts seems to be connected to a HP Array: P410
suspend radeon
I installed an Ubuntu Server 17 but it seems I can't put it in sleep/suspend mode. When I use systemctl suspend
, HDD restarts several times, each time monitor blinks for a moment and multi-line message appears for a second and then original command line returns . the message is this:
dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -38
PM: device 0000:04:00.0 failed to suspend async: error -38
PM: Some devices failed to suspend, or early wake event detected
[drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fenece wait timed out.
[drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-110).
pci_legacy_suspend(): hpsa_suspend+0x0/0x10 [hpsa] returns -38
dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -38
By the way the HDD that restarts seems to be connected to a HP Array: P410
suspend radeon
edited Apr 27 at 10:46
![](https://i.stack.imgur.com/8CW8e.png?s=32&g=1)
![](https://i.stack.imgur.com/8CW8e.png?s=32&g=1)
Zanna
48k13119227
48k13119227
asked Apr 26 at 11:21
![](https://lh3.googleusercontent.com/-XdUIqdMkCWA/AAAAAAAAAAI/AAAAAAAAAAA/4252rscbv5M/photo.jpg?sz=32)
![](https://lh3.googleusercontent.com/-XdUIqdMkCWA/AAAAAAAAAAI/AAAAAAAAAAA/4252rscbv5M/photo.jpg?sz=32)
Muhammad Riazi
11
11
Ubuntu 17.04 crossed EOL in January. Please upgrade.
â Melebius
Apr 26 at 12:29
1
@Melebius I'm having a hard time understanding why ponsfrilus added the 17.04 tag to the question when there was no apparent reason to add it, so I have rollback-ed this question to the author's original unedited version.
â karel
Apr 26 at 13:09
of course i upgraded . this is what happens after the upgrade .
â Muhammad Riazi
Apr 26 at 20:56
I confirmed it , it is the problem with the p410 . by removing it i can suspend the system . but the hardware itself has no problem (or at least i don't think it has) because i worked with it in windows 7 and there was no problem there , so i think the problem must be something operating system-wise .
â Muhammad Riazi
Apr 27 at 15:20
add a comment |Â
Ubuntu 17.04 crossed EOL in January. Please upgrade.
â Melebius
Apr 26 at 12:29
1
@Melebius I'm having a hard time understanding why ponsfrilus added the 17.04 tag to the question when there was no apparent reason to add it, so I have rollback-ed this question to the author's original unedited version.
â karel
Apr 26 at 13:09
of course i upgraded . this is what happens after the upgrade .
â Muhammad Riazi
Apr 26 at 20:56
I confirmed it , it is the problem with the p410 . by removing it i can suspend the system . but the hardware itself has no problem (or at least i don't think it has) because i worked with it in windows 7 and there was no problem there , so i think the problem must be something operating system-wise .
â Muhammad Riazi
Apr 27 at 15:20
Ubuntu 17.04 crossed EOL in January. Please upgrade.
â Melebius
Apr 26 at 12:29
Ubuntu 17.04 crossed EOL in January. Please upgrade.
â Melebius
Apr 26 at 12:29
1
1
@Melebius I'm having a hard time understanding why ponsfrilus added the 17.04 tag to the question when there was no apparent reason to add it, so I have rollback-ed this question to the author's original unedited version.
â karel
Apr 26 at 13:09
@Melebius I'm having a hard time understanding why ponsfrilus added the 17.04 tag to the question when there was no apparent reason to add it, so I have rollback-ed this question to the author's original unedited version.
â karel
Apr 26 at 13:09
of course i upgraded . this is what happens after the upgrade .
â Muhammad Riazi
Apr 26 at 20:56
of course i upgraded . this is what happens after the upgrade .
â Muhammad Riazi
Apr 26 at 20:56
I confirmed it , it is the problem with the p410 . by removing it i can suspend the system . but the hardware itself has no problem (or at least i don't think it has) because i worked with it in windows 7 and there was no problem there , so i think the problem must be something operating system-wise .
â Muhammad Riazi
Apr 27 at 15:20
I confirmed it , it is the problem with the p410 . by removing it i can suspend the system . but the hardware itself has no problem (or at least i don't think it has) because i worked with it in windows 7 and there was no problem there , so i think the problem must be something operating system-wise .
â Muhammad Riazi
Apr 27 at 15:20
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1028378%2fubuntu-server-17-cant-suspend-with-systemctl%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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
Ubuntu 17.04 crossed EOL in January. Please upgrade.
â Melebius
Apr 26 at 12:29
1
@Melebius I'm having a hard time understanding why ponsfrilus added the 17.04 tag to the question when there was no apparent reason to add it, so I have rollback-ed this question to the author's original unedited version.
â karel
Apr 26 at 13:09
of course i upgraded . this is what happens after the upgrade .
â Muhammad Riazi
Apr 26 at 20:56
I confirmed it , it is the problem with the p410 . by removing it i can suspend the system . but the hardware itself has no problem (or at least i don't think it has) because i worked with it in windows 7 and there was no problem there , so i think the problem must be something operating system-wise .
â Muhammad Riazi
Apr 27 at 15:20