[Intel-gfx] i915: pipe B vblank wait timed out

Borislav Petkov bp at alien8.de
Mon Nov 6 15:23:27 UTC 2017


Hi,

I see this on an 32-bit acer atom mini-laptop with -rc8+tip:

[    2.399416] pipe B vblank wait timed out
[    2.399506] ------------[ cut here ]------------
[    2.399533] WARNING: CPU: 1 PID: 22 at /mnt/kernel/kernel/linux-2.6/drivers/gpu/drm/i915/intel_display.c:12176 intel_atomic_commit_tail+0xe0d/0xe20
[    2.399545] Modules linked in:
[    2.399574] CPU: 1 PID: 22 Comm: kworker/1:1 Not tainted 4.14.0-rc8+ #2
[    2.399583] Hardware name: Acer AOA150/        , BIOS v0.3309 10/06/2008
[    2.399597] Workqueue: events output_poll_execute
[    2.399613] task: f65a3780 task.stack: f65aa000
[    2.399625] EIP: intel_atomic_commit_tail+0xe0d/0xe20
[    2.399634] EFLAGS: 00210286 CPU: 1
[    2.399643] EAX: 0000001c EBX: 00000000 ECX: 00200046 EDX: c18f6926
[    2.399652] ESI: 000001a8 EDI: 00000001 EBP: f65abdc0 ESP: f65abd40
[    2.399662]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[    2.399671] CR0: 80050033 CR2: 00000000 CR3: 01c81000 CR4: 000006f0
[    2.399680] Call Trace:
[    2.399699]  ? trace_hardirqs_on_caller+0xdc/0x1c0
[    2.399713]  ? wait_woken+0x80/0x80
[    2.399725]  ? wait_woken+0x80/0x80
[    2.399739]  intel_atomic_commit+0x18f/0x250
[    2.399751]  ? intel_atomic_commit+0x18f/0x250
[    2.399766]  drm_atomic_commit+0x3a/0x50
[    2.399782]  restore_fbdev_mode_atomic+0x15b/0x1a0
[    2.399798]  ? intel_atomic_commit_tail+0xe20/0xe20
[    2.399811]  restore_fbdev_mode+0x2c/0x140
[    2.399824]  drm_fb_helper_restore_fbdev_mode_unlocked.part.19+0x23/0x70
[    2.399836]  drm_fb_helper_set_par+0x45/0x80
[    2.399848]  drm_fb_helper_hotplug_event.part.18+0x86/0xb0
[    2.399861]  drm_fb_helper_hotplug_event+0x20/0x30
[    2.399874]  intel_fbdev_output_poll_changed+0x17/0x20
[    2.399885]  drm_kms_helper_hotplug_event+0x21/0x30
[    2.399897]  output_poll_execute+0x8c/0x190
[    2.399912]  process_one_work+0x1c5/0x5c0
[    2.399927]  worker_thread+0x39/0x3c0
[    2.399939]  ? preempt_count_sub+0x98/0xf0
[    2.399952]  ? process_one_work+0x5c0/0x5c0
[    2.399964]  kthread+0x10b/0x140
[    2.399975]  ? process_one_work+0x5c0/0x5c0
[    2.399987]  ? kthread_create_on_node+0x20/0x20
[    2.399998]  ? umh_complete+0x40/0x40
[    2.400233]  ret_from_fork+0x19/0x24
[    2.400246] Code: 4d 94 8d 55 c4 8b 81 30 02 00 00 01 f0 83 c0 04 e8 f9 a6 c0 ff 85 db 0f 85 e2 fb ff ff 8d 47 41 50 68 08 28 95 c1 e8 90 de c2 ff <0f> ff 58 5a e9 cb fb ff ff 8d 76 00 8d bc 27 00 00 00 00 3e 8d
[    2.400722] ---[ end trace b8984f1a73a52375 ]---


-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.


More information about the Intel-gfx mailing list