From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 190021] New: WARNING: CPU: 0 PID: 38 at drivers/gpu/drm/drm_atomic_helper.c:1549 drm_atomic_helper_commit_hw_done+0xa6/0xb0 [drm_kms_helper]
Date: Sat, 10 Dec 2016 15:48:35 +0000 [thread overview]
Message-ID: <bug-190021-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=190021
Bug ID: 190021
Summary: WARNING: CPU: 0 PID: 38 at
drivers/gpu/drm/drm_atomic_helper.c:1549
drm_atomic_helper_commit_hw_done+0xa6/0xb0
[drm_kms_helper]
Product: Drivers
Version: 2.5
Kernel Version: 4.8.12
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: jfrieben@hotmail.com
Regression: No
This bug was initially reported as
https://bugzilla.redhat.com/show_bug.cgi?id=1366820:
Additional info:
reporter: libreport-2.7.2
WARNING: CPU: 0 PID: 95 at drivers/gpu/drm/drm_atomic_helper.c:1549
drm_atomic_helper_commit_hw_done+0xab/0xb0 [drm_kms_helper]
Modules linked in: uinput nf_conntrack_netbios_ns nf_conntrack_broadcast
ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter xt_conntrack ip_set nfnetlink
ebtable_broute bridge stp llc ebtable_nat ip6table_mangle ip6table_security
ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_raw
iptable_mangle iptable_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4
nf_nat_ipv4 nf_nat nf_conntrack iptable_raw ebtable_filter ebtables
ip6table_filter ip6_tables ppdev snd_intel8x0 snd_ac97_codec ac97_bus snd_seq
snd_seq_device joydev snd_pcm virtio_balloon virtio_gpu ttm drm_kms_helper
parport_pc snd_timer drm parport acpi_cpufreq snd tpm_tis tpm_tis_core
qemu_fw_cfg i2c_piix4 soundcore tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc
virtio_console 8139too serio_raw 8139cp mii virtio_pci
virtio_ring virtio ata_generic pata_acpi
CPU: 0 PID: 95 Comm: kworker/0:1 Not tainted 4.8.0-0.rc1.git3.1.fc25.x86_64 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.9.1-1.fc24
04/01/2014
Workqueue: events drm_mode_rmfb_work_fn [drm]
0000000000000286 000000006be66137 ffff9dbf75d8bb40 ffffffff98467a83
0000000000000000 0000000000000000 ffff9dbf75d8bb80 ffffffff980ae70b
0000060d00000000 ffff9dbf9aa70d18 0000000000000000 ffff9dbf86f9ac00
Call Trace:
[<ffffffff98467a83>] dump_stack+0x86/0xc3
[<ffffffff980ae70b>] __warn+0xcb/0xf0
[<ffffffff980ae83d>] warn_slowpath_null+0x1d/0x20
[<ffffffffc037961b>] drm_atomic_helper_commit_hw_done+0xab/0xb0
[drm_kms_helper]
[<ffffffffc0352b40>] vgdev_atomic_commit_tail+0x40/0x60 [virtio_gpu]
[<ffffffffc037c51c>] commit_tail+0x3c/0x60 [drm_kms_helper]
[<ffffffffc037c5f0>] drm_atomic_helper_commit+0xb0/0xd0 [drm_kms_helper]
[<ffffffffc031baa7>] drm_atomic_commit+0x37/0x60 [drm]
[<ffffffffc037cded>] drm_atomic_helper_set_config+0x7d/0xb0 [drm_kms_helper]
[<ffffffffc03096e5>] drm_mode_set_config_internal+0x65/0x110 [drm]
[<ffffffffc0309a16>] drm_framebuffer_remove+0x106/0x150 [drm]
[<ffffffffc0309aa3>] drm_mode_rmfb_work_fn+0x43/0x60 [drm]
[<ffffffff980ce99e>] process_one_work+0x23e/0x6f0
[<ffffffff980ce91a>] ? process_one_work+0x1ba/0x6f0
[<ffffffff980cee9e>] worker_thread+0x4e/0x490
[<ffffffff980cee50>] ? process_one_work+0x6f0/0x6f0
[<ffffffff980cee50>] ? process_one_work+0x6f0/0x6f0
[<ffffffff980d6201>] kthread+0x101/0x120
[<ffffffff9810e685>] ? trace_hardirqs_on_caller+0xf5/0x1b0
[<ffffffff988f9def>] ret_from_fork+0x1f/0x40
[<ffffffff980d6100>] ? kthread_create_on_node+0x250/0x250
--
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
reply other threads:[~2016-12-10 15:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-190021-2300@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