Bug 101937 - [945GSE] warning in drm_atomic_commit on boot
Summary: [945GSE] warning in drm_atomic_commit on boot
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-26 20:35 UTC by Jan Vesely
Modified: 2018-04-23 19:09 UTC (History)
1 user (show)

See Also:
i915 platform: I945G
i915 features: display/atomic


Attachments
dmesg (49.88 KB, text/plain)
2017-07-26 20:35 UTC, Jan Vesely
no flags Details
dmesg with drm.debug=0xe (58.96 KB, text/plain)
2017-08-02 19:11 UTC, Jan Vesely
no flags Details

Description Jan Vesely 2017-07-26 20:35:38 UTC
Created attachment 133002 [details]
dmesg

I see this warning when booting 4.12.3. No warning on 4.11.1.
[    0.563509] ------------[ cut here ]------------
[    0.563526] WARNING: CPU: 0 PID: 27 at /usr/src/linux-4.12.3-gentoo/drivers/gpu/drm/drm_atomic_helper.c:842 drm_atomic_helper_update_legacy_modeset_state+0x1f8/0x210
[    0.563528] Modules linked in:
[    0.563536] CPU: 0 PID: 27 Comm: kworker/u4:2 Not tainted 4.12.3-gentoo #2
[    0.563539] Hardware name: Acer AOA110/        , BIOS v0.3310 10/06/2008
[    0.563562] Workqueue: events_unbound async_run_entry_fn
[    0.563567] task: f69f2100 task.stack: f6a92000
[    0.563574] EIP: drm_atomic_helper_update_legacy_modeset_state+0x1f8/0x210
[    0.563576] EFLAGS: 00210246 CPU: 0
[    0.563580] EAX: f6037800 EBX: f611dd20 ECX: f60996c0 EDX: f6a34a00
[    0.563583] ESI: 00000000 EDI: 00000000 EBP: f612a400 ESP: f6a93bac
[    0.563587]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[    0.563591] CR0: 80050033 CR2: ffd8d000 CR3: 01b4e000 CR4: 000006c0
[    0.563593] Call Trace:
[    0.563615]  ? intel_atomic_commit_tail+0xb12/0x1090
[    0.563621]  ? check_preempt_curr+0x6b/0x80
[    0.563626]  ? ttwu_do_wakeup.isra.84+0x10/0x160
[    0.563630]  ? ttwu_do_activate.isra.85+0x4c/0x60
[    0.563634]  ? try_to_wake_up+0x37/0x410
[    0.563640]  ? __queue_work+0x102/0x3c0
[    0.563646]  ? __i915_sw_fence_complete+0x10d/0x1b0
[    0.563663]  ? ___preempt_schedule+0x8/0xc
[    0.563669]  ? intel_atomic_commit+0x375/0x460
[    0.563675]  ? drm_mode_object_get+0x37/0x50
[    0.563681]  ? refcount_inc+0x9/0x40
[    0.563687]  ? drm_atomic_commit+0x44/0x50
[    0.563693]  ? restore_fbdev_mode+0x14b/0x280
[    0.563713]  ? drm_fb_helper_restore_fbdev_mode_unlocked+0x1f/0x60
[    0.563719]  ? drm_fb_helper_set_par+0x26/0x60
[    0.563725]  ? intel_fbdev_set_par+0xd/0x50
[    0.563730]  ? fbcon_init+0x57d/0x5d0
[    0.563734]  ? con_release_unimap+0x9c/0xc0
[    0.563741]  ? visual_init+0xb0/0x110
[    0.563746]  ? do_bind_con_driver+0x166/0x350
[    0.563765]  ? do_take_over_console+0x126/0x190
[    0.563769]  ? do_fbcon_takeover+0x4f/0xc0
[    0.563775]  ? notifier_call_chain+0x43/0x60
[    0.563781]  ? __blocking_notifier_call_chain+0x36/0x60
[    0.563786]  ? blocking_notifier_call_chain+0x18/0x20
[    0.563791]  ? register_framebuffer+0x1e3/0x320
[    0.563798]  ? drm_fb_helper_initial_config+0x23d/0x3f0
[    0.563805]  ? intel_fbdev_initial_config+0xe/0x30
[    0.563822]  ? async_run_entry_fn+0x32/0xf0
[    0.563827]  ? process_one_work+0x108/0x340
[    0.563832]  ? worker_thread+0x31/0x3a0
[    0.563836]  ? kthread+0xd3/0x100
[    0.563841]  ? process_one_work+0x340/0x340
[    0.563844]  ? kthread_create_on_node+0x30/0x30
[    0.563850]  ? call_usermodehelper_exec_work+0x50/0xb0
[    0.563856]  ? ret_from_fork+0x19/0x24
[    0.563858] Code: 74 26 00 0f b7 4a 22 89 88 f0 01 00 00 0f b7 52 26 89 90 f4 01 00 00 eb d5 66 90 8d 64 24 10 5b 5e 5f 5d c3 8d b4 26 00 00 00 00 <0f> ff e9 79 fe ff ff 90 0f ff e9 28 ff ff ff 89 f6 8d bc 27 00
[    0.563939] ---[ end trace b679e49ee454f6d0 ]---
Comment 1 Elizabeth 2017-07-28 15:43:08 UTC
Good morning Jan,
Could you please attach dmesg with drm.debug=0xe parameter on grub?
Thank you.
Comment 2 Jan Vesely 2017-08-02 19:11:20 UTC
Created attachment 133210 [details]
dmesg with drm.debug=0xe
Comment 3 Elizabeth 2017-08-04 16:52:19 UTC
(In reply to Jan Vesely from comment #2)
> Created attachment 133210 [details]
> dmesg with drm.debug=0xe
Thanks for the update Jan,
Any other information needed will be requested below.

Adding tag into "Whiteboard" field - ReadyForDev
*Status is correct
*Platform is included
*Feature is included
*Priority and Severity correctly set
*Logs included
Comment 4 Elizabeth 2017-10-23 22:48:14 UTC
(In reply to Jan Vesely from comment #0)
> I see this warning when booting 4.12.3. No warning on 4.11.1.
> ...
Hello Jan, any change with latest mainline? Right now 4.14.
https://www.kernel.org
Comment 5 Jan Vesely 2017-10-24 01:16:00 UTC
(In reply to Elizabeth from comment #4)
> (In reply to Jan Vesely from comment #0)
> > I see this warning when booting 4.12.3. No warning on 4.11.1.
> > ...
> Hello Jan, any change with latest mainline? Right now 4.14.
> https://www.kernel.org

Hi, 4.14 is on rc6 now. I'll test when it gets released (compiling is rather slow on this machine). 4.13.9 suffers from bug #102931 on the same machine
Comment 6 Jan Vesely 2017-11-16 00:20:46 UTC
(In reply to Jan Vesely from comment #5)
> (In reply to Elizabeth from comment #4)
> > (In reply to Jan Vesely from comment #0)
> > > I see this warning when booting 4.12.3. No warning on 4.11.1.
> > > ...
> > Hello Jan, any change with latest mainline? Right now 4.14.
> > https://www.kernel.org
> 
> Hi, 4.14 is on rc6 now. I'll test when it gets released (compiling is rather
> slow on this machine). 4.13.9 suffers from bug #102931 on the same machine

no change running 4.14. still suffers from bug #102931
Comment 7 Jani Saarinen 2018-03-29 07:10:55 UTC
First of all. Sorry about spam.
This is mass update for our bugs. 

Sorry if you feel this annoying but with this trying to understand if bug still valid or not.
If bug investigation still in progress, please ignore this and I apologize!

If you think this is not anymore valid, please comment to the bug that can be closed.
If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Comment 8 Jani Saarinen 2018-04-23 19:08:43 UTC
Jan, Closing, please re-open if still occurs.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.