From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 200531] amdgpu: *ERROR* REG_WAIT timeout when a display is put to sleep
Date: Tue, 04 Sep 2018 14:35:31 +0000 [thread overview]
Message-ID: <bug-200531-2300-pCM9OM1N6f@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200531-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200531
Barry G (barry@grussling.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |barry@grussling.com
--- Comment #8 from Barry G (barry@grussling.com) ---
My Archlinux system just update to 4.18 and now I also can't resume a display.
SSH yields the following in my dmesg:
[ 3317.637991] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us *
6000 tries - dce_mi_allocate_dmif line:599
[ 3317.638034] WARNING: CPU: 10 PID: 5473 at
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:254
generic_reg_wait+0xe7/0x160 [amdgpu]
[ 3317.638034] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4
dns_resolver nfs lockd grace sunrpc fscache nls_iso8859_1 nls_cp437 vfat fat
wmi_bmof mxm_wmi edac_mce_amd pl2303 kvm usbserial irqbypass xpad ff_memless
snd_hda_codec_realtek uvcvideo joydev cdc_acm snd_hda_codec_hdmi
snd_hda_codec_generic videobuf2_vmalloc snd_usb_audio videobuf2_memops
videobuf2_v4l2 videobuf2_common input_leds snd_usbmidi_lib pcspkr led_class
videodev snd_hda_intel mousedev snd_rawmidi snd_hda_codec media snd_seq_device
ixgbe snd_hda_core snd_hwdep snd_pcm igb snd_timer snd sp5100_tco mdio k10temp
dca i2c_piix4 soundcore rtc_cmos wmi pinctrl_amd gpio_amdpt evdev mac_hid
pcc_cpufreq acpi_cpufreq sg crypto_user ip_tables x_tables ext4 crc32c_generic
crc16 mbcache jbd2 fscrypto algif_skcipher af_alg dm_crypt dm_mod
[ 3317.638052] sd_mod uas usb_storage hid_generic usbhid hid crct10dif_pclmul
crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64
crypto_simd xhci_pci ahci cryptd glue_helper libahci mpt3sas xhci_hcd
raid_class libata scsi_transport_sas ccp rng_core usbcore scsi_mod usb_common
amdgpu chash i2c_algo_bit gpu_sched drm_kms_helper syscopyarea sysfillrect
sysimgblt fb_sys_fops ttm drm agpgart
[ 3317.638064] CPU: 10 PID: 5473 Comm: Xorg Tainted: G W
4.18.5-arch1-1-ARCH #1
[ 3317.638064] Hardware name: Micro-Star International Co., Ltd. MS-7B09/X399
GAMING PRO CARBON AC (MS-7B09), BIOS 1.70 12/18/2017
[ 3317.638089] RIP: 0010:generic_reg_wait+0xe7/0x160 [amdgpu]
[ 3317.638089] Code: 44 24 58 8b 54 24 48 89 de 44 89 4c 24 08 48 8b 4c 24 50
48 c7 c7 18 ff 50 c0 e8 04 30 d5 ff 83 7d 20 01 44 8b 4c 24 08 74 02 <0f> 0b 48
83 c4 10 44 89 c8 5b 5d 41 5c 41 5d 41 5e 41 5f c3 41 0f
[ 3317.638102] RSP: 0018:ffffa5ad07b7b980 EFLAGS: 00010297
[ 3317.638103] RAX: 0000000000000000 RBX: 000000000000000a RCX:
0000000000000001
[ 3317.638104] RDX: 0000000000000000 RSI: ffffffff8c0811ce RDI:
00000000ffffffff
[ 3317.638104] RBP: ffff9063efd12e80 R08: ffffffff8b6ddf10 R09:
0000000000000000
[ 3317.638105] R10: 0000000000000004 R11: ffffffff8c804f2d R12:
0000000000001771
[ 3317.638105] R13: 00000000000035b1 R14: 0000000000000010 R15:
0000000000000001
[ 3317.638106] FS: 00007f58f677ee00(0000) GS:ffff9063fcc80000(0000)
knlGS:0000000000000000
[ 3317.638106] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 3317.638107] CR2: 00007f994ae51000 CR3: 0000000fd3e1a000 CR4:
00000000003406e0
[ 3317.638107] Call Trace:
[ 3317.638135] dce_mi_allocate_dmif+0xf6/0x220 [amdgpu]
[ 3317.638162] dce110_apply_ctx_for_surface+0xf1/0x260 [amdgpu]
[ 3317.638187] dc_commit_state+0x350/0x550 [amdgpu]
[ 3317.638214] amdgpu_dm_atomic_commit_tail+0x37c/0xd70 [amdgpu]
[ 3317.638216] ? preempt_count_add+0x68/0xa0
[ 3317.638217] ? _raw_spin_lock_irq+0x1a/0x40
[ 3317.638218] ? _raw_spin_unlock_irq+0x1d/0x30
[ 3317.638219] ? wait_for_common+0x113/0x190
[ 3317.638220] ? _raw_spin_unlock_irq+0x1d/0x30
[ 3317.638221] ? wait_for_common+0x113/0x190
[ 3317.638226] commit_tail+0x3d/0x70 [drm_kms_helper]
[ 3317.638230] drm_atomic_helper_commit+0x103/0x110 [drm_kms_helper]
[ 3317.638237] drm_mode_atomic_ioctl+0x7b1/0x920 [drm]
[ 3317.638244] ? drm_mode_gamma_set_ioctl+0x1a4/0x1e0 [drm]
[ 3317.638250] ? drm_atomic_set_property+0x510/0x510 [drm]
[ 3317.638255] drm_ioctl_kernel+0xa7/0xf0 [drm]
[ 3317.638260] drm_ioctl+0x30e/0x3c0 [drm]
[ 3317.638266] ? drm_atomic_set_property+0x510/0x510 [drm]
[ 3317.638282] amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
[ 3317.638285] do_vfs_ioctl+0xa4/0x620
[ 3317.638286] ? syscall_slow_exit_work+0x19b/0x1b0
[ 3317.638287] ksys_ioctl+0x60/0x90
[ 3317.638288] __x64_sys_ioctl+0x16/0x20
[ 3317.638289] do_syscall_64+0x5b/0x170
[ 3317.638291] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 3317.638292] RIP: 0033:0x7f58fa55079b
[ 3317.638292] Code: 0f 1e fa 48 8b 05 c5 b6 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 95 b6 0c 00 f7 d8 64 89 01 48
[ 3317.638305] RSP: 002b:00007fffdf163ed8 EFLAGS: 00000246 ORIG_RAX:
0000000000000010
[ 3317.638306] RAX: ffffffffffffffda RBX: 0000561db012e740 RCX:
00007f58fa55079b
[ 3317.638307] RDX: 00007fffdf163f20 RSI: 00000000c03864bc RDI:
000000000000000e
[ 3317.638307] RBP: 00007fffdf163f20 R08: 0000561db06b29a0 R09:
0000000000000002
[ 3317.638308] R10: 0000000000000002 R11: 0000000000000246 R12:
00000000c03864bc
[ 3317.638308] R13: 000000000000000e R14: 0000000000000000 R15:
0000561db007ec20
[ 3317.638309] ---[ end trace 7afdbaeea0334919 ]---
I wasn't having these issues with 4.17 as far as I could tell.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-09-04 14:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 0:41 [Bug 200531] New: amdgpu: *ERROR* REG_WAIT timeout when a display is put to sleep bugzilla-daemon
2018-07-18 0:41 ` [Bug 200531] " bugzilla-daemon
2018-07-18 0:56 ` bugzilla-daemon
2018-07-18 0:58 ` bugzilla-daemon
2018-07-18 7:36 ` bugzilla-daemon
2018-07-18 7:36 ` bugzilla-daemon
2018-07-22 13:16 ` bugzilla-daemon
2018-07-22 16:24 ` bugzilla-daemon
2018-08-26 0:53 ` bugzilla-daemon
2018-09-03 5:20 ` bugzilla-daemon
2018-09-04 14:35 ` bugzilla-daemon [this message]
2018-09-05 9:14 ` bugzilla-daemon
2018-09-11 14:15 ` bugzilla-daemon
2018-12-10 2:44 ` bugzilla-daemon
2018-12-31 15:16 ` bugzilla-daemon
2025-02-05 11:09 ` bugzilla-daemon
2025-05-26 13:15 ` bugzilla-daemon
2025-05-27 21:39 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-200531-2300-pCM9OM1N6f@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).