[Intel-gfx] Skylake / (EE) modeset(0): present flip failed loop

Mon Jul 17 20:55:36 UTC 2017

Marc, please file a bug on freedesktop.org.

We expect the modesetting driver to work well and if it's not, it should have a
bug associated with it.

Sorry for your frustration.

On 17-07-17 12:22:00, Marc MERLIN wrote:
>Ok, there must be a problem, sent 5 messages to the list with clear details
>on how the intel driver is failing for me, got one answer from Chris which
>sadly was a bit too short to give me a good hint of what I should try next
>or what further debugging I should give to help fix/improve the driver, and
>then nothing.
>I'm not sure if the messages are being dropped or what's going on, so I've
>added a bunch of intel folks who have posted to the list. I realize it's a
>bit rude, and I apologize for this, but since I've gotten no acknowledgement
>that my multiple messages are even being seen, that's my only recourse left.
>
>Again, I was sent to this list to report issues with the xorg intel driver.
>If this is not the correct place to report issues, please tell me where I
>should do so.
>
>As for the issue, from Chris' answer I think he said I shouldn't be using
>the KMS intel driver, except it seems to be the only option in debian.
>I'm not super sure what he meant or what I'm supposed to do next.
>Details below:
>
>Thanks for your help, the current driver setup is working badly and is
>filling my disk with log spam which gets reset when it finally crashes
>every few days:
>saruman:/tmp$ du -sh /var/log/Xorg.0.log
>1.1G	/var/log/Xorg.0.log
>
>On Fri, Jul 14, 2017 at 01:50:55PM -0700, Marc MERLIN wrote:
>> I'll try a more basic question: am I supposed not to use the modesetting
>> driver if I want a working setup?
>> While debian seems to default to or kind of force the use of the modesetting
>> driver, if you confirm I shouldn't be using it, I can look at how to switch
>> away from it.
>>
>> > > > On Wed, Jul 05, 2017 at 11:33:01PM -0700, Marc MERLIN wrote:
>> > > > > Howdy,
>> > > > >
>> > > > > I have a thinkpad P70 with debian testing and 4.11.6 kernel.
>> > > > > A recent-ish upgrade broke something and now I'm getting loads of spam
>> > > > > in my Xorg.log
>> > > > >
>> > > > > [  5031.435] (WW) modeset(0): flip queue failed: Invalid argument
>> > > > > [  5031.435] (WW) modeset(0): Page flip failed: Invalid argument
>> > > > > [  5031.435] (EE) modeset(0): present flip failed
>> > > > > [  5031.519] (WW) modeset(0): flip queue failed: Invalid argument
>> > > > > [  5031.519] (WW) modeset(0): Page flip failed: Invalid argument
>> > > > > [  5031.519] (EE) modeset(0): present flip failed
>> > > > > (...)
>> > > > >
>> > > > > system info:
>> > > > > ii  libdrm-intel1:amd64        2.4.74-1
>> > > > > ii  xserver-xorg-core          2:1.19.2-1
>> > > > > ii  xserver-xorg-video-intel   2:2.99.917+git20161206-1
>> > >
>> > > If you were indeed using -intel then I would be more concerned.
>> >
>> > Thanks for the reply.
>> > Sorry, I'm not quite parsing what you wrote here. Are you saying that I
>> > should be disable the modesetting driver?
>> > To be honest, I didn't actually choose it, it seems that Debian forced
>> > the switch to it.
>> >
>> > xserver-xorg-video-intel (2:2.13.0-2) unstable; urgency=low
>> >
>> >   * Starting from 2.10, the Intel X driver depends on a kernel driver for
>> >     mode setting (that's called KMS). The corresponding kernel option is
>> >     CONFIG_DRM_I915, and is enabled in Debian kernels.
>> >   * To enable KMS, either of those should be sufficient:
>> >      + /etc/modprobe.d/i915-kms.conf should contain:
>> >          options i915 modeset=1
>> >
>> > If so, how do you recommend I switch back if that's what you meant I should do?
>> >
>> > > But at the very least you need to dig into dmesg (with drm.debug=fe) to
>> > > find out why it failed. (One way is to run -intel with debugging enabled
>> > > so that it includes the kernel error messages along with the failure
>> > > message.)
>> >
>> > Sounds like I need to switch drivers?
>> > Right now I have no xorg.conf and it just autodetects/sets the KMS driver.
>> > Sorry if I'm kind of a NOOB here, but if you give me a short pointer to
>> > how you'd like me to switch, I'll happily do so.
>
>
>Original message:
>> Howdy,
>>
>> I have a thinkpad P70 with debian testing and 4.11.6 kernel.
>> A recent-ish upgrade broke something and now I'm getting loads of spam
>> in my Xorg.log
>>
>> [  5031.435] (WW) modeset(0): flip queue failed: Invalid argument
>> [  5031.435] (WW) modeset(0): Page flip failed: Invalid argument
>> [  5031.435] (EE) modeset(0): present flip failed
>> [  5031.519] (WW) modeset(0): flip queue failed: Invalid argument
>> [  5031.519] (WW) modeset(0): Page flip failed: Invalid argument
>> [  5031.519] (EE) modeset(0): present flip failed
>> (...)
>>
>> system info:
>> ii  libdrm-intel1:amd64        2.4.74-1
>> ii  xserver-xorg-core          2:1.19.2-1
>> ii  xserver-xorg-video-intel   2:2.99.917+git20161206-1
>>
>> 4.11.6-amd64-preempt
>>
>> saruman:~$ xrandr --listproviders
>> Providers: number : 2
>> Provider 0: id: 0x7a cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 3 outputs: 1 associated providers: 0 name:modesetting
>> Provider 1: id: 0x46 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 4 outputs: 3 associated providers: 0 name:modesetting
>>
>> [    73.575] (II) xfree86: Adding drm device (/dev/dri/card1)
>> [    73.576] (II) xfree86: Adding drm device (/dev/dri/card0)
>> [    73.588] (--) PCI:*(0:0:2:0) 8086:191b:17aa:222d rev 6, Mem @ 0xd2000000/16777216, 0x60000000/536870912, I/O @ 0x00006000/64, BIOS @ 0x????????/131072
>> [    73.588] (--) PCI: (0:1:0:0) 10de:13b2:17aa:222d rev 162, Mem @ 0xd3000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00005000/128, BIOS @ 0x????????/524288
>> [    73.597] (II) LoadModule: "modesetting"
>> [    73.597] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
>> [    73.598] (II) Module modesetting: vendor="X.Org Foundation"
>> [    73.598]    compiled for 1.19.2, module version = 1.19.2
>> [    73.598]    Module class: X.Org Video Driver
>> [    73.598]    ABI class: X.Org Video Driver, version 23.0
>> [    73.598] (II) LoadModule: "fbdev"
>> [    73.598] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
>> [    73.598] (II) Module fbdev: vendor="X.Org Foundation"
>> [    73.598]    compiled for 1.19.0, module version = 0.4.4
>> [    73.598]    Module class: X.Org Video Driver
>> [    73.598]    ABI class: X.Org Video Driver, version 23.0
>> [    73.598] (II) LoadModule: "vesa"
>> [    73.598] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
>> [    73.599] (II) Module vesa: vendor="X.Org Foundation"
>> [    73.599]    compiled for 1.19.0, module version = 2.3.4
>> [    73.599]    Module class: X.Org Video Driver
>> [    73.599]    ABI class: X.Org Video Driver, version 23.0
>> [    73.599] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
>> [    73.599] (II) FBDEV: driver for framebuffer: fbdev
>> [    73.599] (II) VESA: driver for VESA chipsets: vesa
>> [    73.637] (II) modeset(0): using drv /dev/dri/card0
>> [    73.637] (II) modeset(G0): using drv /dev/dri/card1
>>
>> In case it helps:
>> saruman:~#  grep . /sys/module/i915/parameters/*
>> /sys/module/i915/parameters/alpha_support:0
>> /sys/module/i915/parameters/disable_display:N
>> /sys/module/i915/parameters/disable_power_well:1
>> /sys/module/i915/parameters/edp_vswing:0
>> /sys/module/i915/parameters/enable_cmd_parser:Y
>> /sys/module/i915/parameters/enable_dc:-1
>> /sys/module/i915/parameters/enable_dpcd_backlight:N
>> /sys/module/i915/parameters/enable_dp_mst:Y
>> /sys/module/i915/parameters/enable_execlists:1
>> /sys/module/i915/parameters/enable_fbc:1
>> /sys/module/i915/parameters/enable_guc_loading:0
>> /sys/module/i915/parameters/enable_guc_submission:0
>> /sys/module/i915/parameters/enable_gvt:N
>> /sys/module/i915/parameters/enable_hangcheck:Y
>> /sys/module/i915/parameters/enable_ips:1
>> /sys/module/i915/parameters/enable_ppgtt:3
>> /sys/module/i915/parameters/enable_psr:0
>> /sys/module/i915/parameters/enable_rc6:1
>> /sys/module/i915/parameters/error_capture:Y
>> /sys/module/i915/parameters/fastboot:N
>> /sys/module/i915/parameters/force_reset_modeset_test:N
>> /sys/module/i915/parameters/guc_log_level:-1
>> /sys/module/i915/parameters/inject_load_failure:0
>> /sys/module/i915/parameters/invert_brightness:0
>> /sys/module/i915/parameters/load_detect_test:N
>> /sys/module/i915/parameters/lvds_channel_mode:0
>> /sys/module/i915/parameters/lvds_use_ssc:-1
>> /sys/module/i915/parameters/mmio_debug:0
>> /sys/module/i915/parameters/modeset:1
>> /sys/module/i915/parameters/nuclear_pageflip:N
>> /sys/module/i915/parameters/panel_ignore_lid:1
>> /sys/module/i915/parameters/prefault_disable:N
>> /sys/module/i915/parameters/reset:Y
>> /sys/module/i915/parameters/semaphores:0
>> /sys/module/i915/parameters/use_mmio_flip:0
>> /sys/module/i915/parameters/vbt_sdvo_panel_type:-1
>> /sys/module/i915/parameters/verbose_state_checks:Y
>>
>> Any idea what to do?
>>
>> Thanks,
>> Marc
>
>
>-- 
>"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
>Microsoft is to operating systems ....
>                                      .... what McDonalds is to gourmet cooking
>Home page: http://marc.merlins.org/
>_______________________________________________
>Intel-gfx mailing list
>Intel-gfx at lists.freedesktop.org
>https://lists.freedesktop.org/mailman/listinfo/intel-gfx