public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Nicolae Rosia <nicolae.rosia.oss@gmail.com>
Cc: Daniel Vetter <daniel@ffwll.ch>, David Weinehall <tao@kernel.org>,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: [Intel-gfx] i915 monitor hotplug on 4.1/4.4 PREEMPT
Date: Fri, 21 Oct 2016 20:14:08 +0200	[thread overview]
Message-ID: <20161021181408.GM20761@phenom.ffwll.local> (raw)
In-Reply-To: <CAKP5S=3Fwws3tMFcijT+PfBFQnCqNLhXL89_SVPv4iWmu0YDYA@mail.gmail.com>

On Fri, Oct 21, 2016 at 04:21:53PM +0300, Nicolae Rosia wrote:
> Hello,
> 
> On Fri, Oct 21, 2016 at 3:27 PM, Daniel Vetter <daniel@ffwll.ch> wrote:
> > So yeah, "upgrade" is very likely is.
> I see...
> 
> i915.disable_power_well=0 seems to do the trick.
> Is it safe to use? The kernel gets tainted because of this.

We taint the kernel on principle if you touch any of these debug options,
i.e. don't send us bug reports if it blows up. Because it'll be running
untested codepaths.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

      reply	other threads:[~2016-10-21 18:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-20 12:15 i915 monitor hotplug on 4.1/4.4 PREEMPT Nicolae Rosia
2016-10-20 12:28 ` Jani Nikula
2016-10-20 12:57   ` David Weinehall
2016-10-20 14:08     ` [Intel-gfx] " Jani Nikula
2016-10-20 14:09     ` Nicolae Rosia
2016-10-21 12:27       ` Daniel Vetter
2016-10-21 13:21         ` Nicolae Rosia
2016-10-21 18:14           ` Daniel Vetter [this message]

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=20161021181408.GM20761@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=nicolae.rosia.oss@gmail.com \
    --cc=tao@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