Bug 1305273 - [abrt] WARNING: CPU: 0 PID: 88 at drivers/gpu/drm/drm_atomic.c:491 drm_atomic_check_only+0x46e/0x540 [drm]() [drm]
Summary: [abrt] WARNING: CPU: 0 PID: 88 at drivers/gpu/drm/drm_atomic.c:491 drm_atomic...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 22
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:1f8f58068fdadbf3a0dc28f8bea...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-06 15:14 UTC by Stan King
Modified: 2016-10-31 17:33 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 18:42:16 UTC
Type: ---


Attachments (Terms of Use)
File: dmesg (66.29 KB, text/plain)
2016-02-06 15:14 UTC, Stan King
no flags Details

Description Stan King 2016-02-06 15:14:33 UTC
Description of problem:
I had just booted into the new 4.3.4.200 kernel with Fedora 22.

Additional info:
reporter:       libreport-2.6.4
WARNING: CPU: 0 PID: 88 at drivers/gpu/drm/drm_atomic.c:491 drm_atomic_check_only+0x46e/0x540 [drm]()
Modules linked in: 8021q garp stp llc mrp i915(+) tg3 firewire_ohci sdhci_pci sdhci firewire_core serio_raw mmc_core crc_itu_t ata_generic pata_acpi i2c_algo_bit drm_kms_helper drm ptp pps_core video
CPU: 0 PID: 88 Comm: kworker/u4:3 Not tainted 4.3.4-200.fc22.x86_64 #1
Hardware name: Dell Inc. Inspiron 1420                   /0DT492, BIOS A10 12/19/2008
Workqueue: events_unbound async_run_entry_fn
 0000000000000000 000000002b9b4387 ffff88003684fa38 ffffffff813a625f
 0000000000000000 ffff88003684fa70 ffffffff810a07c2 ffff880036bb0000
 ffff880036d01800 0000000000000001 0000000000000000 ffff880036cf3200
Call Trace:
 [<ffffffff813a625f>] dump_stack+0x44/0x55
 [<ffffffff810a07c2>] warn_slowpath_common+0x82/0xc0
 [<ffffffff810a090a>] warn_slowpath_null+0x1a/0x20
 [<ffffffffa003f65e>] drm_atomic_check_only+0x46e/0x540 [drm]
 [<ffffffffa003f81d>] ? drm_atomic_set_fb_for_plane+0x2d/0x90 [drm]
 [<ffffffffa003f747>] drm_atomic_commit+0x17/0x60 [drm]
 [<ffffffffa01b2855>] intel_get_load_detect_pipe+0x3d5/0x530 [i915]
 [<ffffffffa01eab5d>] intel_tv_detect+0x13d/0x5e0 [i915]
 [<ffffffffa0039f7e>] ? drm_get_edid+0x3e/0x3f0 [drm]
 [<ffffffff817807b6>] ? schedule_hrtimeout_range_clock.part.23+0xa6/0x150
 [<ffffffffa008dd15>] drm_helper_probe_single_connector_modes_merge_bits+0x235/0x4d0 [drm_kms_helper]
 [<ffffffffa008dfc3>] drm_helper_probe_single_connector_modes+0x13/0x20 [drm_kms_helper]
 [<ffffffffa0099853>] drm_fb_helper_initial_config+0x83/0x400 [drm_kms_helper]
 [<ffffffff810146f1>] ? __switch_to+0x261/0x4b0
 [<ffffffffa01c387b>] intel_fbdev_initial_config+0x1b/0x20 [i915]
 [<ffffffff810c171a>] async_run_entry_fn+0x4a/0x140
 [<ffffffff810b8cde>] process_one_work+0x19e/0x3f0
 [<ffffffff810b8f7e>] worker_thread+0x4e/0x450
 [<ffffffff810b8f30>] ? process_one_work+0x3f0/0x3f0
 [<ffffffff810bede8>] kthread+0xd8/0xf0
 [<ffffffff810bed10>] ? kthread_worker_fn+0x160/0x160
 [<ffffffff81781b9f>] ret_from_fork+0x3f/0x70
 [<ffffffff810bed10>] ? kthread_worker_fn+0x160/0x160

Potential duplicate: bug 1298878

Comment 1 Stan King 2016-02-06 15:14:40 UTC
Created attachment 1121667 [details]
File: dmesg

Comment 2 Stan King 2016-02-28 16:38:09 UTC
Still occurs after upgrading to 4.4.2-301.fc23.x86_64.

However, the source code reference on the WARNING line now says "drivers/gpu/drm/drm_irq.c:1268 drm_wait_one_vblank+0x1b5/0x1c0 [drm]()".

The error repeats a few times during start-up and possibly during shut-down too.

Comment 3 Fedora End Of Life 2016-07-19 18:42:16 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.