Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1182791 > unrolled thread

[-next] WARNING at i915_gem_track_fb

Back to article view | Back to linux.kernel

Contents

  [-next] WARNING at i915_gem_track_fb Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2015-07-13 15:00 +0200
    Re: [Intel-gfx] [-next] WARNING at i915_gem_track_fb Michel Dänzer <michel@daenzer.net> - 2015-07-15 05:00 +0200
      Re: [Intel-gfx] [-next] WARNING at i915_gem_track_fb Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2015-07-15 13:20 +0200

#1182791 — [-next] WARNING at i915_gem_track_fb

4.2.0-rc2-next-20150713

[ 1239.783862] ------------[ cut here ]------------
[ 1239.783892] WARNING: CPU: 0 PID: 364 at drivers/gpu/drm/i915/i915_gem.c:5368 i915_gem_track_fb+0xdc/0x106 [i915]()
[ 1239.783894] WARN_ON(new->frontbuffer_bits & frontbuffer_bits)
[ 1239.783895] Modules linked in:
[ 1239.783897]  zram lz4_decompress lz4_compress lzo_compress lzo_decompress zsmalloc sha256_ssse3 sha256_generic hmac drbg ctr ccm mousedev arc4 nls_iso8859_1 nls_cp437 vfat fat coretemp hwmon iwlmvm i915 mac80211 cfbfillrect cfbimgblt intel_powerclamp i2c_algo_bit crc32c_intel iwlwifi i2c_i801 serio_raw cfbcopyarea psmouse drm_kms_helper ie31200_edac cfg80211 lpc_ich r8169 atkbd mfd_core mii thermal drm edac_core libps2 mxm_wmi wmi i8042 evdev video serio backlight processor ext4 crc16 mbcache jbd2 sd_mod ehci_pci ehci_hcd ahci libahci libata xhci_pci xhci_hcd scsi_mod usbcore usb_common
[ 1239.783942] CPU: 0 PID: 364 Comm: Xorg Not tainted 4.2.0-rc2-next-20150713-dbg-00017-g16b87ed-dirty #183
[ 1239.783944]  0000000000000009 ffff88041c5379d8 ffffffff813a19ac ffffffff81077163
[ 1239.783947]  ffff88041c537a28 ffff88041c537a18 ffffffff8103b5d9 ffff88041c5379f8
[ 1239.783950]  ffffffffa0533273 0000000000000002 ffff88041c578000 ffff88041c578000
[ 1239.783953] Call Trace:
[ 1239.783961]  [<ffffffff813a19ac>] dump_stack+0x4c/0x65
[ 1239.783965]  [<ffffffff81077163>] ? up+0x39/0x3e
[ 1239.783968]  [<ffffffff8103b5d9>] warn_slowpath_common+0x9b/0xb5
[ 1239.783986]  [<ffffffffa0533273>] ? i915_gem_track_fb+0xdc/0x106 [i915]
[ 1239.783987]  [<ffffffff8103b639>] warn_slowpath_fmt+0x46/0x48
[ 1239.784002]  [<ffffffffa0533273>] i915_gem_track_fb+0xdc/0x106 [i915]
[ 1239.784026]  [<ffffffffa0575928>] intel_prepare_plane_fb+0xb1/0x101 [i915]
[ 1239.784033]  [<ffffffffa0261f0f>] drm_atomic_helper_prepare_planes+0x5b/0xb8 [drm_kms_helper]
[ 1239.784055]  [<ffffffffa0585596>] intel_atomic_commit+0x46/0xc0 [i915]
[ 1239.784072]  [<ffffffffa02d2139>] drm_atomic_commit+0x4d/0x52 [drm]
[ 1239.784078]  [<ffffffffa0262f32>] drm_atomic_helper_update_plane+0xca/0x119 [drm_kms_helper]
[ 1239.784092]  [<ffffffffa02c7572>] __setplane_internal+0x24e/0x2ae [drm]
[ 1239.784103]  [<ffffffffa02c771b>] drm_mode_cursor_universal+0x149/0x197 [drm]
[ 1239.784113]  [<ffffffffa02c7e58>] ? drm_mode_setcrtc+0x428/0x428 [drm]
[ 1239.784122]  [<ffffffffa02c781e>] drm_mode_cursor_common+0xb5/0x156 [drm]
[ 1239.784132]  [<ffffffffa02c7e8f>] drm_mode_cursor_ioctl+0x37/0x39 [drm]
[ 1239.784140]  [<ffffffffa02bae85>] drm_ioctl+0x287/0x415 [drm]
[ 1239.784143]  [<ffffffff81078580>] ? __lock_is_held+0x3c/0x57
[ 1239.784146]  [<ffffffff8114c3d1>] ? __fget+0x170/0x1a1
[ 1239.784148]  [<ffffffff811422c1>] do_vfs_ioctl+0x455/0x4dd
[ 1239.784151]  [<ffffffff8114c48e>] ? __fget_light+0x65/0x75
[ 1239.784153]  [<ffffffff8114238d>] SyS_ioctl+0x44/0x63
[ 1239.784155]  [<ffffffff813a8057>] entry_SYSCALL_64_fastpath+0x12/0x6f
[ 1239.784157] ---[ end trace 67b32b389e7fe7df ]---

	-ss
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1184219 — Re: [Intel-gfx] [-next] WARNING at i915_gem_track_fb

On 14.07.2015 22:41, Sergey Senozhatsky wrote:
> 
> sometimes `xset dpms force off' just turns off the panel for a second,
> sometimes -- until I generate a `wakeup' event (key press, etc.)

FWIW, the former case is because releasing the enter key generates an
input event, which changes the DPMS state to on again. You can avoid
that with something like "sleep 1 && xset dpms force off".


-- 
Earthling Michel Dänzer               |               http://www.amd.com
Libre software enthusiast             |             Mesa and X developer
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1184692 — Re: [Intel-gfx] [-next] WARNING at i915_gem_track_fb

On (07/15/15 11:51), Michel Dänzer wrote:
> On 14.07.2015 22:41, Sergey Senozhatsky wrote:
> > 
> > sometimes `xset dpms force off' just turns off the panel for a second,
> > sometimes -- until I generate a `wakeup' event (key press, etc.)
> 
> FWIW, the former case is because releasing the enter key generates an
> input event, which changes the DPMS state to on again. You can avoid
> that with something like "sleep 1 && xset dpms force off".
> 

Yeah, sure. That's the expected behaviour. 'turns off the panel for a second'
is sort of wrong here.

	-ss
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web