mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] Graphics on thinkpad x270 after dock/undock works only for the first time (CPU pipe B FIFO underrun)
Date: Tue, 2 Jan 2018 11:21:08 -0800	[thread overview]
Message-ID: <20180102192108.nrs4xdcyihpwbvuk@intel.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1712301348440.3572@cbobk.fhfr.pm>

On Sat, Dec 30, 2017 at 12:53:58PM +0000, Jiri Kosina wrote:
> On Sat, 30 Dec 2017, Jiri Kosina wrote:
> 
> > Seems like disabling RC6 on the kernel command line works this around, and 
> > I can dock / undock several times in a row with the image always coming 
> > up properly on the external display.
> > 
> > On the first undock, the WARN_ONCE() below triggers, so I believe each 
> > undock leaks memory.
> > 
> > [   38.755084] Failed to release pages: bind_count=1, pages_pin_count=1, pin_global=0
> > [   38.755138] WARNING: CPU: 3 PID: 96 at ../drivers/gpu/drm/i915/i915_gem_userptr.c:89 cancel_userptr+0xe5/0xf0 [i915]
> 
> OK, I am seeing this warning with current Linus' tree (5aa90a845) even 
> without any attempt to dock/undock, so it's probably unrelated to external 
> outputs and it only by coincidence appeared originally at the same time I 
> docked the machine.
> 
> So there are two separate issues on this machine with latest kernel 
> (neither of them probably being regression):
> 
> - I have to disable i915 RC6 at the kernel cmdline, otherwise external 
>   (dock) display gets output only randomly (seems like always only on 
>   first dock)

Joonas, Chris, time to bring rc6_enable back on next-fixes before we
remove this support entirely?

> 
> - the warning, which triggers at not really deterministic time after boot, 
>   but usually rather quickly

Jiri, could you please report these issues separately on bugs.freedesktop.org?
Are them regressions? Possible bisect?
Please attach the dmesg booting with drm.debug=0x1e

> 
> -- 
> Jiri Kosina
> SUSE Labs
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-01-02 19:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-29 21:10 Jiri Kosina
2017-12-29 22:06 ` Jiri Kosina
2017-12-30  9:44 ` Jiri Kosina
2017-12-30 12:53   ` Jiri Kosina
2018-01-02 19:21     ` Rodrigo Vivi [this message]
2018-01-02 19:35       ` [Intel-gfx] " Chris Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180102192108.nrs4xdcyihpwbvuk@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=jikos@kernel.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®