Debugging a suspend to ram issue with PM_TRACE
3
So I've been debugging a hairy suspend-to-ram issue, where I get
Oct 12 15:41:23 arjundesktop dbus[2863]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Oct 12 15:41:23 arjundesktop systemd[1]: Reached target Sleep.
Oct 12 15:41:23 arjundesktop systemd[1]: Starting Suspend...
Oct 12 15:41:23 arjundesktop systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 12 15:41:23 arjundesktop systemd-sleep[17199]: Suspending system...
�������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������May 21 16:33:31 arjundesktop rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="2929" x-info="http://www.rsyslog.com"] start
When this happens, I can no longer wakeup my system. I've run this on debian and ubuntu, with kernels ranging from 3.16 - 4.7. My current kernel is
Linux arjundesktop 4.7.6 #1 SMP Sat Oct 8 13:00:22 MDT 2016 x86_64 GNU/Linux
I've been following this basic guide to suspend debugging. My dmesg log shows
May 21 16:33:31 arjundesktop kernel: [ 1.225463] initcall deferred_probe_initcall+0x0/0x70 returned 0 after 87 usecs
May 21 16:33:31 arjundesktop kernel: [ 1.225863] calling late_resume_init+0x0/0x1a0 @ 1
May 21 16:33:31 arjundesktop kernel: [ 1.226255] Magic number: 14:34:278
May 21 16:33:31 arjundesktop kernel: [ 1.226655] tty tty15: hash matches
May 21 16:33:31 arjundesktop kernel: [ 1.227075] initcall late_resume_init+0x0/0x1a0 returned 0 after 799 usecs
May 21 16:33:31 arjundesktop kernel: [ 1.227466] calling rtc_hctosys+0x0/0x101 @ 1
May 21 16:33:31 arjundesktop kernel: [ 1.227889] rtc_cmos 00:02: setting system clock to 2014-01-01 12:16:03 UTC (1388578563)
May 21 16:33:31 arjundesktop kernel: [ 1.228291] initcall rtc_hctosys+0x0/0x101 returned 0 after 423 usecs
What does this magic number mean? Why is saying the crash happened from my tty? When I run
cat /sys/power/pm_trace_dev_match
I get
usb
tty
What does this mean? How would I proceed? Output of lsusb
Bus 004 Device 002: ID 8087:8001 Intel Corp.
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 8087:8009 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 062a:4101 Creative Labs
Bus 001 Device 002: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0
Bus 001 Device 005: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
linux-kernel kernel-modules debugging suspend
asked Oct 12 '16 at 23:20
user128063user128063
374310
add a comment |
3
So I've been debugging a hairy suspend-to-ram issue, where I get
Oct 12 15:41:23 arjundesktop dbus[2863]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Oct 12 15:41:23 arjundesktop systemd[1]: Reached target Sleep.
Oct 12 15:41:23 arjundesktop systemd[1]: Starting Suspend...
Oct 12 15:41:23 arjundesktop systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 12 15:41:23 arjundesktop systemd-sleep[17199]: Suspending system...
�������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������May 21 16:33:31 arjundesktop rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="2929" x-info="http://www.rsyslog.com"] start
When this happens, I can no longer wakeup my system. I've run this on debian and ubuntu, with kernels ranging from 3.16 - 4.7. My current kernel is
Linux arjundesktop 4.7.6 #1 SMP Sat Oct 8 13:00:22 MDT 2016 x86_64 GNU/Linux
I've been following this basic guide to suspend debugging. My dmesg log shows
May 21 16:33:31 arjundesktop kernel: [ 1.225463] initcall deferred_probe_initcall+0x0/0x70 returned 0 after 87 usecs
May 21 16:33:31 arjundesktop kernel: [ 1.225863] calling late_resume_init+0x0/0x1a0 @ 1
May 21 16:33:31 arjundesktop kernel: [ 1.226255] Magic number: 14:34:278
May 21 16:33:31 arjundesktop kernel: [ 1.226655] tty tty15: hash matches
May 21 16:33:31 arjundesktop kernel: [ 1.227075] initcall late_resume_init+0x0/0x1a0 returned 0 after 799 usecs
May 21 16:33:31 arjundesktop kernel: [ 1.227466] calling rtc_hctosys+0x0/0x101 @ 1
May 21 16:33:31 arjundesktop kernel: [ 1.227889] rtc_cmos 00:02: setting system clock to 2014-01-01 12:16:03 UTC (1388578563)
May 21 16:33:31 arjundesktop kernel: [ 1.228291] initcall rtc_hctosys+0x0/0x101 returned 0 after 423 usecs
What does this magic number mean? Why is saying the crash happened from my tty? When I run
cat /sys/power/pm_trace_dev_match
I get
usb
tty
What does this mean? How would I proceed? Output of lsusb
Bus 004 Device 002: ID 8087:8001 Intel Corp.
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 8087:8009 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 062a:4101 Creative Labs
Bus 001 Device 002: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0
Bus 001 Device 005: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
linux-kernel kernel-modules debugging suspend
asked Oct 12 '16 at 23:20
user128063user128063
374310
add a comment |
3
3
3
So I've been debugging a hairy suspend-to-ram issue, where I get
Oct 12 15:41:23 arjundesktop dbus[2863]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Oct 12 15:41:23 arjundesktop systemd[1]: Reached target Sleep.
Oct 12 15:41:23 arjundesktop systemd[1]: Starting Suspend...
Oct 12 15:41:23 arjundesktop systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 12 15:41:23 arjundesktop systemd-sleep[17199]: Suspending system...
�������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������May 21 16:33:31 arjundesktop rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="2929" x-info="http://www.rsyslog.com"] start
When this happens, I can no longer wakeup my system. I've run this on debian and ubuntu, with kernels ranging from 3.16 - 4.7. My current kernel is
Linux arjundesktop 4.7.6 #1 SMP Sat Oct 8 13:00:22 MDT 2016 x86_64 GNU/Linux
I've been following this basic guide to suspend debugging. My dmesg log shows
May 21 16:33:31 arjundesktop kernel: [ 1.225463] initcall deferred_probe_initcall+0x0/0x70 returned 0 after 87 usecs
May 21 16:33:31 arjundesktop kernel: [ 1.225863] calling late_resume_init+0x0/0x1a0 @ 1
May 21 16:33:31 arjundesktop kernel: [ 1.226255] Magic number: 14:34:278
May 21 16:33:31 arjundesktop kernel: [ 1.226655] tty tty15: hash matches
May 21 16:33:31 arjundesktop kernel: [ 1.227075] initcall late_resume_init+0x0/0x1a0 returned 0 after 799 usecs
May 21 16:33:31 arjundesktop kernel: [ 1.227466] calling rtc_hctosys+0x0/0x101 @ 1
May 21 16:33:31 arjundesktop kernel: [ 1.227889] rtc_cmos 00:02: setting system clock to 2014-01-01 12:16:03 UTC (1388578563)
May 21 16:33:31 arjundesktop kernel: [ 1.228291] initcall rtc_hctosys+0x0/0x101 returned 0 after 423 usecs
What does this magic number mean? Why is saying the crash happened from my tty? When I run
cat /sys/power/pm_trace_dev_match
I get
usb
tty
What does this mean? How would I proceed? Output of lsusb
Bus 004 Device 002: ID 8087:8001 Intel Corp.
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 8087:8009 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 062a:4101 Creative Labs
Bus 001 Device 002: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0
Bus 001 Device 005: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
linux-kernel kernel-modules debugging suspend
asked Oct 12 '16 at 23:20
user128063user128063
374310
So I've been debugging a hairy suspend-to-ram issue, where I get
Oct 12 15:41:23 arjundesktop dbus[2863]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Oct 12 15:41:23 arjundesktop systemd[1]: Reached target Sleep.
Oct 12 15:41:23 arjundesktop systemd[1]: Starting Suspend...
Oct 12 15:41:23 arjundesktop systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 12 15:41:23 arjundesktop systemd-sleep[17199]: Suspending system...
�������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������May 21 16:33:31 arjundesktop rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="2929" x-info="http://www.rsyslog.com"] start
When this happens, I can no longer wakeup my system. I've run this on debian and ubuntu, with kernels ranging from 3.16 - 4.7. My current kernel is
Linux arjundesktop 4.7.6 #1 SMP Sat Oct 8 13:00:22 MDT 2016 x86_64 GNU/Linux
I've been following this basic guide to suspend debugging. My dmesg log shows
May 21 16:33:31 arjundesktop kernel: [ 1.225463] initcall deferred_probe_initcall+0x0/0x70 returned 0 after 87 usecs
May 21 16:33:31 arjundesktop kernel: [ 1.225863] calling late_resume_init+0x0/0x1a0 @ 1
May 21 16:33:31 arjundesktop kernel: [ 1.226255] Magic number: 14:34:278
May 21 16:33:31 arjundesktop kernel: [ 1.226655] tty tty15: hash matches
May 21 16:33:31 arjundesktop kernel: [ 1.227075] initcall late_resume_init+0x0/0x1a0 returned 0 after 799 usecs
May 21 16:33:31 arjundesktop kernel: [ 1.227466] calling rtc_hctosys+0x0/0x101 @ 1
May 21 16:33:31 arjundesktop kernel: [ 1.227889] rtc_cmos 00:02: setting system clock to 2014-01-01 12:16:03 UTC (1388578563)
May 21 16:33:31 arjundesktop kernel: [ 1.228291] initcall rtc_hctosys+0x0/0x101 returned 0 after 423 usecs
What does this magic number mean? Why is saying the crash happened from my tty? When I run
cat /sys/power/pm_trace_dev_match
I get
usb
tty
What does this mean? How would I proceed? Output of lsusb
Bus 004 Device 002: ID 8087:8001 Intel Corp.
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 8087:8009 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 062a:4101 Creative Labs
Bus 001 Device 002: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0
Bus 001 Device 005: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
linux-kernel kernel-modules debugging suspend
linux-kernel kernel-modules debugging suspend
asked Oct 12 '16 at 23:20
user128063user128063
374310
asked Oct 12 '16 at 23:20
user128063user128063
374310
edited Oct 13 '16 at 0:04
user128063
asked Oct 12 '16 at 23:20
user128063user128063
374310
asked Oct 12 '16 at 23:20
user128063user128063
374310
asked Oct 12 '16 at 23:20
user128063user128063
374310
374310
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
0
I have no real answers, but I changed my graphics card from an AMD 7950 to a AMD Vega 64. Now suspend to ram works fine on the amdgpu driver, so I suspect it was a graphics driver issue.
answered 4 hours ago
user128063user128063
374310
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
});
}
});
draft saved
draft discarded
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%2f316055%2fdebugging-a-suspend-to-ram-issue-with-pm-trace%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
0
I have no real answers, but I changed my graphics card from an AMD 7950 to a AMD Vega 64. Now suspend to ram works fine on the amdgpu driver, so I suspect it was a graphics driver issue.
answered 4 hours ago
user128063user128063
374310
add a comment |
0
I have no real answers, but I changed my graphics card from an AMD 7950 to a AMD Vega 64. Now suspend to ram works fine on the amdgpu driver, so I suspect it was a graphics driver issue.
answered 4 hours ago
user128063user128063
374310
add a comment |
0
0
0
I have no real answers, but I changed my graphics card from an AMD 7950 to a AMD Vega 64. Now suspend to ram works fine on the amdgpu driver, so I suspect it was a graphics driver issue.
answered 4 hours ago
user128063user128063
374310
I have no real answers, but I changed my graphics card from an AMD 7950 to a AMD Vega 64. Now suspend to ram works fine on the amdgpu driver, so I suspect it was a graphics driver issue.
answered 4 hours ago
user128063user128063
374310
answered 4 hours ago
user128063user128063
374310
answered 4 hours ago
user128063user128063
374310
answered 4 hours ago
user128063user128063
374310
374310
add a comment |
add a comment |
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f316055%2fdebugging-a-suspend-to-ram-issue-with-pm-trace%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
