Re: Skylake / (EE) modeset(0): present flip failed loop

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jul 07, 2017 at 11:47:25AM +0100, Chris Wilson wrote:
> Quoting Marc MERLIN (2017-07-07 06:40:51)
> > Is this the right place to send this?
> > Can anyone help?
> > 
> > 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.

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/                         | PGP 1024R/763BE901
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx




[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux