You are not logged in.

Pages: 1

#1 2020-07-04 13:23:09

X04D
Member
Registered: 2008-01-20
Posts: 22

System doesn't wake up from sleep/suspend

Hey all,

I usually turn my computer off but last night I left it on with the monitor off.  In the morning I wasn't able to wake it and had to hard reboot.

Here's the last portion of my journal, not sure at all if it's relevant:

Jul 03 21:25:46 wu kernel: WARNING: CPU: 4 PID: 811 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_resource.c:3126 dcn20_validate_bandwidth_fp+0x6d/0xb0 [amdgpu]
Jul 03 21:25:46 wu kernel: Modules linked in: fuse xt_mark xt_tcpudp xt_cgroup ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_multiport xt_owner ip6table_mangle iptable_mangle ip6table_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_d>
Jul 03 21:25:46 wu kernel:  vmmon(OE) vmw_vmci pkcs8_key_parser crypto_user ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid dm_crypt dm_mod crct10dif_pclmul crc32_pclmul crc32c_inte>
Jul 03 21:25:46 wu kernel: CPU: 4 PID: 811 Comm: Xorg Tainted: G           OE     5.7.7-1-ck #1
Jul 03 21:25:46 wu kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B450 Gaming-ITX/ac, BIOS P3.70 11/18/2019
Jul 03 21:25:46 wu kernel: RIP: 0010:dcn20_validate_bandwidth_fp+0x6d/0xb0 [amdgpu]
Jul 03 21:25:46 wu kernel: Code: 00 7b 35 22 85 e8 1d 00 00 75 2f 31 d2 f2 0f 11 85 18 25 00 00 48 89 ee 4c 89 e7 e8 7d f6 ff ff 89 c2 22 95 e8 1d 00 00 75 2a <0f> 0b 48 89 9d 18 25 00 00 5b 5d 41 5c c3 75 c9 48 89 9d 18 25 00
Jul 03 21:25:46 wu kernel: RSP: 0018:ffffb79880f33ab8 EFLAGS: 00010246
Jul 03 21:25:46 wu kernel: RAX: 0000000000000001 RBX: 4079400000000000 RCX: 0000000000cd2e04
Jul 03 21:25:46 wu kernel: RDX: 0000000000000000 RSI: 09953b6f74511f6e RDI: 00000000000311a0
Jul 03 21:25:46 wu kernel: RBP: ffff959567340000 R08: ffff9593e3d49000 R09: ffff9595bfe60000
Jul 03 21:25:46 wu kernel: R10: ffff9593e3d49000 R11: 0000000100000001 R12: ffff9595bfe60000
Jul 03 21:25:46 wu kernel: R13: ffff9594af6eaf80 R14: ffff9595c3089000 R15: ffff959567340000
Jul 03 21:25:46 wu kernel: FS:  00007f39cdfff280(0000) GS:ffff9595ce900000(0000) knlGS:0000000000000000
Jul 03 21:25:46 wu kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 03 21:25:46 wu kernel: CR2: 00007ff400fa7000 CR3: 00000004072b0000 CR4: 0000000000340ee0
Jul 03 21:25:46 wu kernel: Call Trace:
Jul 03 21:25:46 wu kernel:  dcn20_validate_bandwidth+0x24/0x40 [amdgpu]
Jul 03 21:25:46 wu kernel:  dc_validate_global_state+0x2f2/0x390 [amdgpu]
Jul 03 21:25:46 wu kernel:  amdgpu_dm_atomic_check+0xe77/0xfb0 [amdgpu]
Jul 03 21:25:46 wu kernel:  drm_atomic_check_only+0x55a/0x7d0 [drm]
Jul 03 21:25:46 wu kernel:  ? _raw_spin_unlock_irqrestore+0x20/0x40
Jul 03 21:25:46 wu kernel:  drm_atomic_commit+0x13/0x50 [drm]
Jul 03 21:25:46 wu kernel:  drm_atomic_connector_commit_dpms+0xda/0x100 [drm]
Jul 03 21:25:46 wu kernel:  drm_mode_obj_set_property_ioctl+0x196/0x2d0 [drm]
Jul 03 21:25:46 wu kernel:  ? drm_connector_set_obj_prop+0x90/0x90 [drm]
Jul 03 21:25:46 wu kernel:  drm_connector_property_set_ioctl+0x37/0x60 [drm]
Jul 03 21:25:46 wu kernel:  drm_ioctl_kernel+0xaa/0xf0 [drm]
Jul 03 21:25:46 wu kernel:  drm_ioctl+0x206/0x390 [drm]
Jul 03 21:25:46 wu kernel:  ? drm_connector_set_obj_prop+0x90/0x90 [drm]
Jul 03 21:25:46 wu kernel:  ? __hrtimer_init+0xd0/0xd0
Jul 03 21:25:46 wu kernel:  ? preempt_count_add+0x68/0xa0
Jul 03 21:25:46 wu kernel:  ? _raw_write_lock_irq+0x1a/0x40
Jul 03 21:25:46 wu kernel:  amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
Jul 03 21:25:46 wu kernel:  ksys_ioctl+0x82/0xc0
Jul 03 21:25:46 wu kernel:  __x64_sys_ioctl+0x16/0x20
Jul 03 21:25:46 wu kernel:  do_syscall_64+0x49/0x90
Jul 03 21:25:46 wu kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jul 03 21:25:46 wu kernel: RIP: 0033:0x7f39cec3a8eb
Jul 03 21:25:46 wu kernel: Code: 0f 1e fa 48 8b 05 a5 95 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 75 95 0c 00 f7 d8 64 89 01 48
Jul 03 21:25:46 wu kernel: RSP: 002b:00007ffc2d90eee8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Jul 03 21:25:46 wu kernel: RAX: ffffffffffffffda RBX: 00007ffc2d90ef20 RCX: 00007f39cec3a8eb
Jul 03 21:25:46 wu kernel: RDX: 00007ffc2d90ef20 RSI: 00000000c01064ab RDI: 000000000000000d
Jul 03 21:25:46 wu kernel: RBP: 00000000c01064ab R08: 0000000000000000 R09: 00007f39ced48d10
Jul 03 21:25:46 wu kernel: R10: 00007f39ced48d20 R11: 0000000000000246 R12: 0000563d83179e30
Jul 03 21:25:46 wu kernel: R13: 000000000000000d R14: 0000000000000000 R15: 0000000000000000
Jul 03 21:25:46 wu kernel: ---[ end trace 1e7967e7385bf4fe ]---
-- Reboot --

Some information in case it helps:

wu% uname -a
Linux wu 5.7.7-1-ck #1 SMP PREEMPT Thu, 02 Jul 2020 11:46:40 +0000 x86_64 GNU/Linux

CPU: Ryzen 5 3600
GPU: AMD 5700 XT (AMDGPU drivers)

0c:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c1) (prog-if 00 [VGA controller])
        Subsystem: Tul Corporation / PowerColor Device 2398
        Flags: bus master, fast devsel, latency 0, IRQ 84
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Memory at f0000000 (64-bit, prefetchable) [size=2M]
        I/O ports at e000 [size=256]
        Memory at fcb00000 (32-bit, non-prefetchable) [size=512K]
        Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu

Please let me know if I can provide any more information to help you help me!

Last edited by X04D (2020-07-04 15:15:57)

Offline

#2 2020-07-04 14:52:35

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,642

Re: System doesn't wake up from sleep/suspend

Whatever happened, happened earlier in the log that you posted.  Note the times, things were going pear shaped at 21:25:46.  A lot happened in that second.  Search back for what triggered the event.

What time did you turn the monitor off?

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Online

#3 2020-07-04 15:10:18

X04D
Member
Registered: 2008-01-20
Posts: 22

Re: System doesn't wake up from sleep/suspend

ewaller wrote:

Whatever happened, happened earlier in the log that you posted.  Note the times, things were going pear shaped at 21:25:46.  A lot happened in that second.  Search back for what triggered the event.

What time did you turn the monitor off?

Thanks for the reply!  I can't say for certain what time I turned off the monitor, but I'll see if I can reproduce it shortly.

Until then, here's more of the journal, hopefully it helps shed some light:

Jul 03 21:12:49 wu rtkit-daemon[1447]: Supervising 1 threads of 1 processes of 1 users.
Jul 03 21:12:49 wu rtkit-daemon[1447]: Supervising 1 threads of 1 processes of 1 users.
Jul 03 21:12:49 wu rtkit-daemon[1447]: Supervising 1 threads of 1 processes of 1 users.
Jul 03 21:12:49 wu rtkit-daemon[1447]: Supervising 1 threads of 1 processes of 1 users.
Jul 03 21:12:49 wu rtkit-daemon[1447]: Successfully made thread 60341 of process 60119 owned by '1000' RT at priority 10.
Jul 03 21:12:49 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:12:49 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:12:49 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:12:49 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:12:49 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:12:50 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:12:50 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:12:52 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:12:52 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:12:52 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:12:52 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:12:52 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:12:52 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:12:56 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:12:56 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:13:10 wu audit[60926]: USER_AUTH pid=60926 uid=1000 auid=1000 ses=1 msg='op=PAM:authentication grantors=pam_unix,pam_permit acct="whiskeyjack" exe="/usr/>
Jul 03 21:13:10 wu kernel: audit: type=1100 audit(1593832390.385:340): pid=60926 uid=1000 auid=1000 ses=1 msg='op=PAM:authentication grantors=pam_unix,pam_permit a>
Jul 03 21:13:10 wu kernel: audit: type=1101 audit(1593832390.395:341): pid=60926 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_t>
Jul 03 21:13:10 wu kernel: audit: type=1110 audit(1593832390.395:342): pid=60926 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit acct="root">
Jul 03 21:13:10 wu audit[60926]: USER_ACCT pid=60926 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="whiskeyjack" exe=">
Jul 03 21:13:10 wu audit[60926]: CRED_REFR pid=60926 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostnam>
Jul 03 21:13:10 wu sudo[60926]: whiskeyjack : TTY=pts/2 ; PWD=/home/whiskeyjack ; USER=root ; COMMAND=/usr/bin/pacman -R anbox-binder
Jul 03 21:13:10 wu sudo[60926]: pam_unix(sudo:session): session opened for user root by whiskeyjack(uid=0)
Jul 03 21:13:10 wu audit[60926]: USER_START pid=60926 uid=0 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/>
Jul 03 21:13:10 wu kernel: audit: type=1105 audit(1593832390.395:343): pid=60926 uid=0 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_pe>
Jul 03 21:13:10 wu sudo[60926]: pam_unix(sudo:session): session closed for user root
Jul 03 21:13:10 wu audit[60926]: USER_END pid=60926 uid=0 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/b>
Jul 03 21:13:10 wu audit[60926]: CRED_DISP pid=60926 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostnam>
Jul 03 21:13:10 wu kernel: audit: type=1106 audit(1593832390.405:344): pid=60926 uid=0 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_p>
Jul 03 21:13:10 wu kernel: audit: type=1104 audit(1593832390.405:345): pid=60926 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit acct="root">
Jul 03 21:13:28 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:13:28 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:13:42 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:13:42 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:13:58 wu audit[61469]: USER_ACCT pid=61469 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="whiskeyjack" exe=">
Jul 03 21:13:58 wu audit[61469]: CRED_REFR pid=61469 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acct="root" exe="/usr/bin/sudo">
Jul 03 21:13:58 wu sudo[61469]: whiskeyjack : TTY=pts/2 ; PWD=/usr/src ; USER=root ; COMMAND=/usr/bin/dkms status
Jul 03 21:13:58 wu sudo[61469]: pam_unix(sudo:session): session opened for user root by whiskeyjack(uid=0)
Jul 03 21:13:58 wu audit[61469]: USER_START pid=61469 uid=0 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/>
Jul 03 21:13:59 wu kernel: audit: type=1101 audit(1593832438.985:346): pid=61469 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_t>
Jul 03 21:13:59 wu kernel: audit: type=1110 audit(1593832438.985:347): pid=61469 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acc>
Jul 03 21:13:59 wu kernel: audit: type=1105 audit(1593832438.985:348): pid=61469 uid=0 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_pe>
Jul 03 21:13:59 wu sudo[61469]: pam_unix(sudo:session): session closed for user root
Jul 03 21:13:59 wu audit[61469]: USER_END pid=61469 uid=0 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/b>
Jul 03 21:13:59 wu audit[61469]: CRED_DISP pid=61469 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acct="root" exe="/usr/bin/sudo">
Jul 03 21:13:59 wu kernel: audit: type=1106 audit(1593832439.875:349): pid=61469 uid=0 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_p>
Jul 03 21:13:59 wu kernel: audit: type=1104 audit(1593832439.875:350): pid=61469 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acc>
Jul 03 21:14:20 wu audit[64940]: USER_ACCT pid=64940 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="whiskeyjack" exe=">
Jul 03 21:14:20 wu audit[64940]: CRED_REFR pid=64940 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acct="root" exe="/usr/bin/sudo">
Jul 03 21:14:20 wu sudo[64940]: whiskeyjack : TTY=pts/2 ; PWD=/var/lib/dkms ; USER=root ; COMMAND=/usr/bin/rm -rf anbox-ashmem anbox-binder anbox-modules-ashmem an>
Jul 03 21:14:20 wu sudo[64940]: pam_unix(sudo:session): session opened for user root by whiskeyjack(uid=0)
Jul 03 21:14:20 wu audit[64940]: USER_START pid=64940 uid=0 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/>
Jul 03 21:14:20 wu kernel: audit: type=1101 audit(1593832460.065:351): pid=64940 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_t>
Jul 03 21:14:20 wu kernel: audit: type=1110 audit(1593832460.065:352): pid=64940 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acc>
Jul 03 21:14:20 wu kernel: audit: type=1105 audit(1593832460.065:353): pid=64940 uid=0 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_pe>
Jul 03 21:14:20 wu sudo[64940]: pam_unix(sudo:session): session closed for user root
Jul 03 21:14:20 wu audit[64940]: USER_END pid=64940 uid=0 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/b>
Jul 03 21:14:20 wu audit[64940]: CRED_DISP pid=64940 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acct="root" exe="/usr/bin/sudo">
Jul 03 21:14:20 wu kernel: audit: type=1106 audit(1593832460.095:354): pid=64940 uid=0 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_p>
Jul 03 21:14:20 wu kernel: audit: type=1104 audit(1593832460.095:355): pid=64940 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acc>
Jul 03 21:14:26 wu audit[64996]: USER_ACCT pid=64996 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="whiskeyjack" exe=">
Jul 03 21:14:26 wu audit[64996]: CRED_REFR pid=64996 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acct="root" exe="/usr/bin/sudo">
Jul 03 21:14:26 wu sudo[64996]: whiskeyjack : TTY=pts/2 ; PWD=/var/lib/dkms ; USER=root ; COMMAND=/usr/bin/dkms status
Jul 03 21:14:26 wu sudo[64996]: pam_unix(sudo:session): session opened for user root by whiskeyjack(uid=0)
Jul 03 21:14:26 wu audit[64996]: USER_START pid=64996 uid=0 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/>
Jul 03 21:14:26 wu kernel: audit: type=1101 audit(1593832466.215:356): pid=64996 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_t>
Jul 03 21:14:26 wu kernel: audit: type=1110 audit(1593832466.215:357): pid=64996 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acc>
Jul 03 21:14:26 wu kernel: audit: type=1105 audit(1593832466.215:358): pid=64996 uid=0 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_pe>
Jul 03 21:14:26 wu sudo[64996]: pam_unix(sudo:session): session closed for user root
Jul 03 21:14:26 wu audit[64996]: USER_END pid=64996 uid=0 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/b>
Jul 03 21:14:26 wu audit[64996]: CRED_DISP pid=64996 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acct="root" exe="/usr/bin/sudo">
Jul 03 21:14:26 wu kernel: audit: type=1106 audit(1593832466.435:359): pid=64996 uid=0 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_p>
Jul 03 21:14:26 wu kernel: audit: type=1104 audit(1593832466.435:360): pid=64996 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acc>
Jul 03 21:14:46 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:14:46 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:14:47 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:14:47 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:14:48 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:14:48 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:14:49 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:14:49 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:14:50 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:14:50 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:14:54 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:14:54 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:14:54 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:14:54 wu rtkit-daemon[1447]: Supervising 2 threads of 2 processes of 1 users.
Jul 03 21:14:54 wu rtkit-daemon[1447]: Successfully made thread 66167 of process 65992 owned by '1000' RT at priority 10.
Jul 03 21:14:54 wu rtkit-daemon[1447]: Supervising 3 threads of 3 processes of 1 users.
Jul 03 21:15:21 wu vmnetBridge[685]: RTM_NEWLINK: name:wlp8s0 index:3 flags:0x00001002
Jul 03 21:15:21 wu vmnet-natd[709]: RTM_NEWLINK: name:wlp8s0 index:3 flags:0x00001002
Jul 03 21:15:21 wu NetworkManager[628]: <info>  [1593832521.8226] device (wlp8s0): set-hw-addr: set MAC address to 26:94:A4:4D:09:1C (scanning)
Jul 03 21:15:21 wu vmnet-natd[709]: RTM_NEWLINK: name:wlp8s0 index:3 flags:0x00001002
Jul 03 21:15:21 wu vmnetBridge[685]: RTM_NEWLINK: name:wlp8s0 index:3 flags:0x00001002
Jul 03 21:15:21 wu dhcpcd[645]: wlp8s0: new hardware address: 26:94:a4:4d:09:1c
Jul 03 21:15:21 wu vmnet-natd[709]: RTM_NEWLINK: name:wlp8s0 index:3 flags:0x00001003
Jul 03 21:15:21 wu vmnetBridge[685]: RTM_NEWLINK: name:wlp8s0 index:3 flags:0x00001003
Jul 03 21:15:21 wu NetworkManager[628]: <info>  [1593832521.8822] device (wlp8s0): supplicant interface state: inactive -> disconnected
Jul 03 21:15:21 wu NetworkManager[628]: <info>  [1593832521.8822] device (p2p-dev-wlp8s0): supplicant management interface state: inactive -> disconnected
Jul 03 21:15:21 wu NetworkManager[628]: <info>  [1593832521.8873] device (wlp8s0): supplicant interface state: disconnected -> inactive
Jul 03 21:15:21 wu NetworkManager[628]: <info>  [1593832521.8873] device (p2p-dev-wlp8s0): supplicant management interface state: disconnected -> inactive
Jul 03 21:17:50 wu rtkit-daemon[1447]: Supervising 3 threads of 3 processes of 1 users.
Jul 03 21:17:50 wu rtkit-daemon[1447]: Supervising 3 threads of 3 processes of 1 users.
Jul 03 21:17:51 wu rtkit-daemon[1447]: Supervising 3 threads of 3 processes of 1 users.
Jul 03 21:17:51 wu rtkit-daemon[1447]: Supervising 3 threads of 3 processes of 1 users.
Jul 03 21:19:22 wu kernel: usb 1-7.3: reset full-speed USB device number 7 using xhci_hcd
Jul 03 21:22:14 wu vmnetBridge[685]: RTM_NEWLINK: name:wlp8s0 index:3 flags:0x00001002
Jul 03 21:22:14 wu vmnet-natd[709]: RTM_NEWLINK: name:wlp8s0 index:3 flags:0x00001002
Jul 03 21:22:14 wu NetworkManager[628]: <info>  [1593832934.7501] device (wlp8s0): set-hw-addr: set MAC address to 3E:39:C1:E9:73:03 (scanning)
Jul 03 21:22:14 wu vmnetBridge[685]: RTM_NEWLINK: name:wlp8s0 index:3 flags:0x00001002
Jul 03 21:22:14 wu vmnet-natd[709]: RTM_NEWLINK: name:wlp8s0 index:3 flags:0x00001003
Jul 03 21:22:14 wu vmnetBridge[685]: RTM_NEWLINK: name:wlp8s0 index:3 flags:0x00001003
Jul 03 21:22:14 wu NetworkManager[628]: <info>  [1593832934.9026] device (wlp8s0): supplicant interface state: inactive -> disconnected
Jul 03 21:22:14 wu NetworkManager[628]: <info>  [1593832934.9026] device (p2p-dev-wlp8s0): supplicant management interface state: inactive -> disconnected
Jul 03 21:22:14 wu NetworkManager[628]: <info>  [1593832934.9077] device (wlp8s0): supplicant interface state: disconnected -> inactive
Jul 03 21:22:14 wu NetworkManager[628]: <info>  [1593832934.9077] device (p2p-dev-wlp8s0): supplicant management interface state: disconnected -> inactive
Jul 03 21:22:21 wu kernel: usb 1-7.3: reset full-speed USB device number 7 using xhci_hcd
Jul 03 21:22:52 wu kernel: usb 1-7.3: reset full-speed USB device number 7 using xhci_hcd
Jul 03 21:23:03 wu kernel: usb 1-7.3: reset full-speed USB device number 7 using xhci_hcd
Jul 03 21:23:35 wu kernel: usb 1-7.3: reset full-speed USB device number 7 using xhci_hcd
Jul 03 21:25:46 wu kernel: ------------[ cut here ]------------
Jul 03 21:25:46 wu kernel: WARNING: CPU: 4 PID: 811 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_resource.c:3126 dcn20_validate_bandwidth_fp+0x6d/0xb0 [amdgpu]
Jul 03 21:25:46 wu kernel: Modules linked in: fuse xt_mark xt_tcpudp xt_cgroup ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_multiport xt_owner ip6table_mangle iptable_mangle ip6table_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c>
Jul 03 21:25:46 wu kernel:  vmmon(OE) vmw_vmci pkcs8_key_parser crypto_user ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid dm_crypt dm_mod crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_inte>
Jul 03 21:25:46 wu kernel: CPU: 4 PID: 811 Comm: Xorg Tainted: G           OE     5.7.7-1-ck #1
Jul 03 21:25:46 wu kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B450 Gaming-ITX/ac, BIOS P3.70 11/18/2019
Jul 03 21:25:46 wu kernel: RIP: 0010:dcn20_validate_bandwidth_fp+0x6d/0xb0 [amdgpu]
Jul 03 21:25:46 wu kernel: Code: 00 7b 35 22 85 e8 1d 00 00 75 2f 31 d2 f2 0f 11 85 18 25 00 00 48 89 ee 4c 89 e7 e8 7d f6 ff ff 89 c2 22 95 e8 1d 00 00 75 2a <0f> 0b 48 89 9d 18 25 00 00 5b 5d 41 5c c3 75 c9 48 89 9d 18 25 00
Jul 03 21:25:46 wu kernel: RSP: 0018:ffffb79880f33ab8 EFLAGS: 00010246
Jul 03 21:25:46 wu kernel: RAX: 0000000000000001 RBX: 4079400000000000 RCX: 0000000000cd2e04
Jul 03 21:25:46 wu kernel: RDX: 0000000000000000 RSI: 09953b6f74511f6e RDI: 00000000000311a0
Jul 03 21:25:46 wu kernel: RBP: ffff959567340000 R08: ffff9593e3d49000 R09: ffff9595bfe60000
Jul 03 21:25:46 wu kernel: R10: ffff9593e3d49000 R11: 0000000100000001 R12: ffff9595bfe60000

Offline

#4 2020-07-04 15:39:20

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,642

Re: System doesn't wake up from sleep/suspend

I see two things.  The primary thing is the AMD GPU pitched an error and I think it took out xorg.  That could be related to the monitor going away.

The other thing was a USB device at address 7 on the first USB controller reset four times over the course of a couple minutes.  Any idea what that device is?

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Online

#5 2020-07-04 16:07:37

X04D
Member
Registered: 2008-01-20
Posts: 22

Re: System doesn't wake up from sleep/suspend

ewaller wrote:

I see two things.  The primary thing is the AMD GPU pitched an error and I think it took out xorg.  That could be related to the monitor going away.

The other thing was a USB device at address 7 on the first USB controller reset four times over the course of a couple minutes.  Any idea what that device is?

Noticed the USB device as well.  If I were a betting man I'd say that was my USB hub, though the only thing connected is a stream deck and keyboard, but I'll mess with it and see if it needs to be replaced or simple use a different port.

Not sure what would cause the AMD GPU error, but that would make some sense.  I'll see if I can reproduce it and then I'll check the xorg logs.

Thanks!

Offline

#6 2020-07-05 14:03:46

X04D
Member
Registered: 2008-01-20
Posts: 22

Re: System doesn't wake up from sleep/suspend

I manually invoked systemctl-suspend and I was unable to wake the system immediately after.  Only a hard reboot worked.

Here's the journal from that period:

Jul 04 21:37:33 wu rtkit-daemon[1444]: Supervising 5 threads of 5 processes of 1 users.
Jul 04 21:37:33 wu rtkit-daemon[1444]: Supervising 5 threads of 5 processes of 1 users.
Jul 04 21:37:34 wu rtkit-daemon[1444]: Supervising 5 threads of 5 processes of 1 users.
Jul 04 21:37:34 wu rtkit-daemon[1444]: Supervising 5 threads of 5 processes of 1 users.
Jul 04 21:38:09 wu rtkit-daemon[1444]: Supervising 5 threads of 5 processes of 1 users.
Jul 04 21:38:09 wu rtkit-daemon[1444]: Supervising 5 threads of 5 processes of 1 users.
Jul 04 21:39:11 wu polkitd[1447]: Registered Authentication Agent for unix-process:508741:5053068 (system bus name :1.5708 [/usr/bin/pkttyag>
Jul 04 21:39:11 wu NetworkManager[624]: <info>  [1593920351.5199] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jul 04 21:39:11 wu NetworkManager[624]: <info>  [1593920351.5200] device (p2p-dev-wlp8s0): state change: disconnected -> unmanaged (reason '>
Jul 04 21:39:11 wu polkitd[1447]: Unregistered Authentication Agent for unix-process:508741:5053068 (system bus name :1.5708, object path /o>
Jul 04 21:39:11 wu NetworkManager[624]: <info>  [1593920351.5213] manager: NetworkManager state is now ASLEEP
Jul 04 21:39:11 wu systemd[1]: Reached target Sleep.
Jul 04 21:39:11 wu systemd[1]: Starting Suspend...
Jul 04 21:39:11 wu systemd-sleep[508746]: Suspending system...
-- Reboot --
Jul 05 07:43:52 wu kernel: Linux version 5.7.7-1-ck (linux-ck@archlinux) (gcc version 10.1.0 (GCC), GNU ld (GNU Binutils) 2.34.0) #1 SMP PRE>

Seems like absolutely nothing between the suspend and the hard reboot.

Offline

#7 2020-07-07 18:04:35

X04D
Member
Registered: 2008-01-20
Posts: 22

Re: System doesn't wake up from sleep/suspend

Experienced a similar powermanagement issue today.  Stepped away from the computer for 15 minutes, returned, was unable to wake it. Yet again, nothing in dmesg that seems related.

Nothing alarming in Xorg log either.

Offline

#8 2020-07-07 19:07:49

vitriol
Member
Registered: 2013-11-19
Posts: 14

Re: System doesn't wake up from sleep/suspend

Can confirm this issue, it's happening because of linux-ck, reverting back to 5.7.4-1-ck-skylake solves the issue.
Does anyone have any ideas where we should report this to the ck dev?

Offline

#9 2020-07-11 06:49:18

kazimir
Member
Registered: 2012-01-20
Posts: 81

Re: System doesn't wake up from sleep/suspend

I have been experiencing a similar issue for some time on a thinkpad laptop using the ck kernel.

The power button LED would blink fast and the mute mic button would stay lit.
No issue was written to journal.
The computer would not get out of sleep, a hard poweroff by pushing the power button for several seconds was required.

I just upgraded to 5.7.8-1-ck-ivybridge and now the suspend to ram works again.

Offline

#10 2020-07-19 13:15:41

vitriol
Member
Registered: 2013-11-19
Posts: 14

Re: System doesn't wake up from sleep/suspend

This should be marked as solved

Offline

Pages: 1

Board footer

Powered by FluxBB