New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 692768 link

Starred by 2 users
Status: WontFix
Owner:
█ tutankhamen@chromium.org
Last visit 28 days ago
Closed: Sep 2017
Cc:
snanda@chromium.org
█ yungleem@chromium.org
█ marc...@chromium.org
semenzato@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Kernel warning: a339c635-intel_mmio_flip_work_func+0x6d/0x315()

Project Member Reported by keta...@chromium.org, Feb 15 2017 
Product, versionChromeOS, 9202.12.0
Report ID9f5dc69840000000
Process typekernel-warning
Magic Signaturenon_fatal ( bug 61079 )

Stable Signaturea339c635-intel_mmio_flip_work_func+0x6d/0x315()edit bugs&comments
Report TimeWed, 15 Feb 2017 20:15:48 GMT
Client ID47879112E5234F309D8980DF414369CA

a339c635-intel_mmio_flip_work_func+0x6d/0x315()

/mnt/host/source/src/third_party/kernel/v3.18/drivers/gpu/drm/i915/intel_display.c:11178 intel_mmio_flip_work_func+0x6d/0x315()
2017-02-15T14:12:11.278724-05:00 WARNING kernel: [72861.509211] WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, NULL, &mmio_flip->i915->rps.mmioflips))
2017-02-15T14:12:11.280365-05:00 WARNING kernel: [72861.509228] Modules linked in: snd_seq_dummy ip6t_REJECT nf_reject_ipv6 rfcomm uinput btusb btrtl btbcm btintel uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core snd_hda_codec_hdmi ipt_MASQUERADE nf_nat_masquerade_ipv4 snd_hda_intel snd_hda_codec iptable_nat snd_hwdep snd_hda_core snd_soc_sst_cht_bsw_max98090_ti nf_nat_ipv4 nf_nat snd_intel_sst_acpi snd_soc_sst_acpi snd_intel_sst_core xt_mark snd_soc_sst_mfld_platform memconsole_x86_legacy memconsole snd_soc_max98090 bridge bluetooth stp llc fuse zram ccm ip6table_filter snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm iwlwifi iwl7000_mac80211 cfg80211 iio_trig_sysfs joydev cros_ec_sensors_ring cros_ec_sensors cros_ec_sensors_core industrialio_triggered_buffer kfifo_buf industrialio
2017-02-15T14:12:11.280391-05:00 WARNING kernel: [72861.509501] CPU: 3 PID: 8187 Comm: kworker/3:0 Tainted: G        W      3.18.0-13739-gbf5e73b #1
2017-02-15T14:12:11.280394-05:00 WARNING kernel: [72861.509515] Hardware name: GOOGLE Cyan, BIOS Google_Cyan.7287.57.100 01/01/2017
2017-02-15T14:12:11.280396-05:00 WARNING kernel: [72861.509532] Workqueue: events intel_mmio_flip_work_func
2017-02-15T14:12:11.282562-05:00 WARNING kernel: [72861.509544]  0000000000000000 00000000bd26f045 ffff880155283cd8 ffffffff978a0b67
2017-02-15T14:12:11.282575-05:00 WARNING kernel: [72861.509564]  0000000000000000 ffff880155283d30 ffff880155283d18 ffffffff97263c4c
2017-02-15T14:12:11.282577-05:00 WARNING kernel: [72861.509583]  ffff880155283ce8 ffffffff975b9ebd ffff8801591bd480 ffff88001c8b83c0
2017-02-15T14:12:11.282579-05:00 WARNING kernel: [72861.509602] Call Trace:
2017-02-15T14:12:11.282581-05:00 WARNING kernel: [72861.509617]  [<ffffffff978a0b67>] dump_stack+0x4e/0x71
2017-02-15T14:12:11.282583-05:00 WARNING kernel: [72861.509632]  [<ffffffff97263c4c>] warn_slowpath_common+0x81/0x9b
2017-02-15T14:12:11.282585-05:00 WARNING kernel: [72861.509647]  [<ffffffff975b9ebd>] ? intel_mmio_flip_work_func+0x6d/0x315
2017-02-15T14:12:11.282587-05:00 WARNING kernel: [72861.509662]  [<ffffffff97263cbb>] warn_slowpath_fmt+0x55/0x6b
2017-02-15T14:12:11.282589-05:00 WARNING kernel: [72861.509677]  [<ffffffff975b9ebd>] intel_mmio_flip_work_func+0x6d/0x315
2017-02-15T14:12:11.282591-05:00 WARNING kernel: [72861.509693]  [<ffffffff972837d4>] ? finish_task_switch+0x5b/0xba
2017-02-15T14:12:11.282592-05:00 WARNING kernel: [72861.509709]  [<ffffffff97278993>] process_one_work+0x176/0x2d4
2017-02-15T14:12:11.282594-05:00 WARNING kernel: [72861.509723]  [<ffffffff97279318>] worker_thread+0x1ec/0x2bf
2017-02-15T14:12:11.282596-05:00 WARNING kernel: [72861.509737]  [<ffffffff9727912c>] ? rescuer_thread+0x2db/0x2db
2017-02-15T14:12:11.282613-05:00 WARNING kernel: [72861.509751]  [<ffffffff9727d3e2>] kthread+0x10e/0x116
2017-02-15T14:12:11.282616-05:00 WARNING kernel: [72861.509764]  [<ffffffff9727d2d4>] ? __kthread_parkme+0x67/0x67
2017-02-15T14:12:11.282618-05:00 WARNING kernel: [72861.509778]  [<ffffffff978a5cec>] ret_from_fork+0x7c/0xb0
2017-02-15T14:12:11.282620-05:00 WARNING kernel: [72861.509791]  [<ffffffff9727d2d4>] ? __kthread_parkme+0x67/0x67
2017-02-15T14:12:11.282621-05:00 WARNING kernel: [72861.509803] ---[ end trace 280d5bb145a978e5 ]---
upload_file_kcrash-9f5dc69840000000.kcrash
3.6 KB Download

Comment 1 by snanda@chromium.org, May 15 2017

Cc: yungleem@chromium.org
Owner: marc...@chromium.org
Seeing bunch of warnings with this signature on Chell with some users complaining about Chrome crashing.  Got to this issue wile tracking reports from here: https://bugs.chromium.org/p/chromium/issues/detail?id=708005#c61

Stephane, thoughts?

https://crash.corp.google.com/browse?q=ClientID%3D%273ef8f6df38c14b099b0d6b7a59596a7a%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D&stbtiq=&reportid=18a2e52470000000&index=5#0

Comment 2 by marc...@chromium.org, Jul 20 2017

Cc: marc...@chromium.org
Owner: tutankhamen@chromium.org

Comment 3 by tutankhamen@chromium.org, Jul 31 2017 

Looking into it...

Comment 4 by tutankhamen@chromium.org, Jul 31 2017 

Any tip about repro steps? I don't see anything in my Cyan's logs. I have some ideas why it could happen, but I need reliable repro steps to prove it.
Project Member

Comment 5 by bugdroid1@chromium.org, Aug 11 2017

Labels: merge-merged-chromeos-3.14
The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/8b0a5a88939f979ab5125b0a5993b6d3e6ad1d02

commit 8b0a5a88939f979ab5125b0a5993b6d3e6ad1d02
Author: Robert Tarasov <tutankhamen@google.com>
Date: Fri Aug 11 05:47:30 2017

CHROMIUM: drm/i915: Get rid of _wait for vblank timeout_ warning

Fixed issue when wait_for_vblank could be invoked during crtc
deinitialization when planes are already inactive

BUG= chromium:692768 
TEST=cat /var/log/messages | grep "vblank wait timed out"

Change-Id: I70710f323f6c452030db09503f835b0c6001c7ee
Signed-off-by: Robert Tarasov <tutankhamen@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/599207
Commit-Ready: Stéphane Marchesin <marcheu@chromium.org>
Tested-by: Stéphane Marchesin <marcheu@chromium.org>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

[modify] https://crrev.com/8b0a5a88939f979ab5125b0a5993b6d3e6ad1d02/drivers/gpu/drm/i915/intel_display.c
Project Member

Comment 6 by bugdroid1@chromium.org, Aug 17 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/bdf7444566e0967f58715c1879db7e5eee1f542c

commit bdf7444566e0967f58715c1879db7e5eee1f542c
Author: Ningning Xia <nxia@chromium.org>
Date: Thu Aug 17 17:50:15 2017

Revert "CHROMIUM: drm/i915: Get rid of _wait for vblank timeout_ warning"

This reverts commit 8b0a5a88939f979ab5125b0a5993b6d3e6ad1d02.

Reason for revert:   crbug.com/755461 

Original change's description:
> CHROMIUM: drm/i915: Get rid of _wait for vblank timeout_ warning
> 
> Fixed issue when wait_for_vblank could be invoked during crtc
> deinitialization when planes are already inactive
> 
> BUG= chromium:692768 
> TEST=cat /var/log/messages | grep "vblank wait timed out"
> 
> Change-Id: I70710f323f6c452030db09503f835b0c6001c7ee
> Signed-off-by: Robert Tarasov <tutankhamen@chromium.org>
> Reviewed-on: https://chromium-review.googlesource.com/599207
> Commit-Ready: Stéphane Marchesin <marcheu@chromium.org>
> Tested-by: Stéphane Marchesin <marcheu@chromium.org>
> Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

Bug:  chromium:692768 
Change-Id: Id94c3a0e1d21cad550b8053c4d5d2099e994f96e
Reviewed-on: https://chromium-review.googlesource.com/618221
Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org>
Tested-by: Ningning Xia <nxia@chromium.org>

[modify] https://crrev.com/bdf7444566e0967f58715c1879db7e5eee1f542c/drivers/gpu/drm/i915/intel_display.c

Comment 7 by textor@chromium.org, Aug 18 2017 

Is this bug still untriaged, or is it being worked on?

Comment 8 by tutankhamen@chromium.org, Sep 18 2017

Status: WontFix (was: Untriaged)
Can't reproduce this bug.
Project Member

Comment 9 by bugdroid1@chromium.org, Nov 2 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/98924ed38cb51567307821298f4121b5b0c1e494

commit 98924ed38cb51567307821298f4121b5b0c1e494
Author: Robert Tarasov <tutankhamen77@gmail.com>
Date: Thu Nov 02 07:12:59 2017

CHROMIUM: drm/i915: Fixed "wait_for_vblank" timeout and "wait_for_pending_flips" timeout

Fixed issue when wait_for_vblank could be invoked during crtc
deinitialization when planes are already inactive. Also, fixed
an issue with possible intel_crtc_wait_for_pending_flips()
timeout during crtc deinitialization by adding one frame delay.

BUG= chromium:692768 , chromium:755461 
TEST=cat /var/log/messages | grep "vblank wait timed out"

Change-Id: If65aff20945175dba64fea1b59565f840d8bbf27
Signed-off-by: Robert Tarasov <tutankhamen77@gmail.com>
Reviewed-on: https://chromium-review.googlesource.com/626940
Commit-Ready: Robert Tarasov <tutankhamen@chromium.org>
Tested-by: Robert Tarasov <tutankhamen@chromium.org>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

[modify] https://crrev.com/98924ed38cb51567307821298f4121b5b0c1e494/drivers/gpu/drm/i915/intel_display.c
►

Sign in to add a comment