From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109628] WARNING at dcn10_hw_sequencer.c:868 dcn10_verify_allow_pstate_change_high()
Date: Wed, 16 Oct 2019 17:31:42 +0000 [thread overview]
Message-ID: <bug-109628-502-TYu7QZ101f@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109628-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 3810 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #30 from peter m <malkovjohnny@ukr.net> ---
kernel 5.3.5-200.fc30.x86_64 (mockbuild@bkernel04.phx2.fedoraproject.org)
xfce - 4.14
kernel still crushing
------------[ cut here ]------------
WARNING: CPU: 2 PID: 184 at
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hw_sequencer.c:932
dcn10_verify_allow_pstate_change_high.cold+0xc/0x229 [amdgpu]
Modules linked in: ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT
nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_nat
ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat
iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6
nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables
ip6table_filter ip6_tables iptable_filter ip_tables sunrpc
snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi
snd_hda_intel edac_mce_amd snd_hda_codec snd_hda_core ccp kvm snd_hwdep snd_seq
snd_seq_device irqbypass snd_pcm snd_timer joydev snd soundcore
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel wmi_bmof sp5100_tco k10temp
i2c_piix4 gpio_amdpt gpio_generic acpi_cpufreq amdgpu amd_iommu_v2 gpu_sched
i2c_algo_bit ttm drm_kms_helper crc32c_intel drm r8169 wmi video pinctrl_amd
CPU: 2 PID: 184 Comm: kworker/u32:8 Not tainted 5.3.5-200.fc30.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. A320M-S2H V2/A320M-S2H V2-CF, BIOS
F2 12/25/2018
Workqueue: events_unbound commit_work [drm_kms_helper]
RIP: 0010:dcn10_verify_allow_pstate_change_high.cold+0xc/0x229 [amdgpu]
Code: 83 c8 ff e9 00 1c f8 ff 48 c7 c7 70 6b 5a c0 e8 71 09 c6 de 0f 0b 83 c8
ff e9 ea 1b f8 ff 48 c7 c7 70 6b 5a c0 e8 5b 09 c6 de <0f> 0b 80 bb 9f 01 00 00
00 75 05 e9 d2 42 f8 ff 48 8b 83 f8 02 00
RSP: 0018:ffffbc69803c7af0 EFLAGS: 00010246
RAX: 0000000000000024 RBX: ffff96890d220000 RCX: 0000000000000006
RDX: 0000000000000000 RSI: 0000000000000096 RDI: ffff968918a97900
RBP: ffff96890d220000 R08: 0000000000000001 R09: 0000000000000401
R10: 00000000000169fc R11: 0000000000000003 R12: ffff9688f09501b8
R13: ffff96890b32f800 R14: 0000000000000001 R15: 0000000000000004
FS: 0000000000000000(0000) GS:ffff968918a80000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9eba01c000 CR3: 00000001e4092000 CR4: 00000000003406e0
Call Trace:
dcn10_pipe_control_lock.part.0+0x69/0x70 [amdgpu]
dc_commit_updates_for_stream+0xfa5/0x1460 [amdgpu]
amdgpu_dm_atomic_commit_tail+0xb61/0x1c40 [amdgpu]
? cpumask_next_and+0x1a/0x20
? load_balance+0x1a4/0xb50
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? _cond_resched+0x15/0x30
? wait_for_completion_timeout+0x38/0x170
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to+0x152/0x440
? commit_tail+0x3c/0x70 [drm_kms_helper]
commit_tail+0x3c/0x70 [drm_kms_helper]
process_one_work+0x19d/0x340
worker_thread+0x50/0x3b0
kthread+0xfb/0x130
? process_one_work+0x340/0x340
? kthread_park+0x80/0x80
ret_from_fork+0x22/0x40
---[ end trace 76057b23d3d7f433 ]---
[drm] pstate TEST_DEBUG_DATA: 0x36F60000
------------[ cut here ]------------
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4720 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-10-16 17:31 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 9:56 [Bug 109628] WARNING at dcn10_hw_sequencer.c:868 dcn10_verify_allow_pstate_change_high() bugzilla-daemon
2019-02-14 9:58 ` bugzilla-daemon
2019-02-14 9:59 ` bugzilla-daemon
2019-02-14 10:08 ` bugzilla-daemon
2019-02-14 14:29 ` bugzilla-daemon
2019-03-05 9:49 ` bugzilla-daemon
2019-08-29 21:54 ` bugzilla-daemon
2019-08-30 10:34 ` bugzilla-daemon
2019-08-30 11:46 ` bugzilla-daemon
2019-08-30 15:01 ` bugzilla-daemon
2019-08-30 15:13 ` bugzilla-daemon
2019-08-30 15:43 ` bugzilla-daemon
2019-08-30 17:13 ` bugzilla-daemon
2019-08-30 23:31 ` bugzilla-daemon
2019-09-04 18:07 ` bugzilla-daemon
2019-09-04 18:10 ` bugzilla-daemon
2019-09-10 15:34 ` bugzilla-daemon
2019-09-11 17:25 ` bugzilla-daemon
2019-09-16 14:17 ` bugzilla-daemon
2019-09-16 15:06 ` bugzilla-daemon
2019-09-19 17:49 ` bugzilla-daemon
2019-09-20 15:57 ` bugzilla-daemon
2019-09-22 9:02 ` bugzilla-daemon
2019-09-22 9:05 ` bugzilla-daemon
2019-09-22 20:13 ` bugzilla-daemon
2019-09-26 8:37 ` bugzilla-daemon
2019-10-06 19:38 ` bugzilla-daemon
2019-10-06 20:13 ` bugzilla-daemon
2019-10-07 5:59 ` bugzilla-daemon
2019-10-07 8:16 ` bugzilla-daemon
2019-10-16 17:31 ` bugzilla-daemon [this message]
2019-11-04 10:31 ` bugzilla-daemon
2019-11-05 17:42 ` bugzilla-daemon
2019-11-10 5:34 ` bugzilla-daemon
2019-11-10 6:20 ` bugzilla-daemon
2019-11-14 16:27 ` bugzilla-daemon
2019-11-19 9:13 ` 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-109628-502-TYu7QZ101f@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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