public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: David Weinehall <david.weinehall@linux.intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Cc: "kyle@infradead.org" <kyle@infradead.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"linux-firmware@kernel.org" <linux-firmware@kernel.org>,
	"ben@decadent.org.uk" <ben@decadent.org.uk>,
	"kmcmarti@redhat.com" <kmcmarti@redhat.com>
Subject: Re: linux-firmware-i915 pull request (bxt dmc, kbl dmc)
Date: Thu, 4 Aug 2016 21:38:31 +0300	[thread overview]
Message-ID: <20160804183831.GC3542@boom> (raw)
In-Reply-To: <1470239273.5637.72.camel@intel.com>

On Wed, Aug 03, 2016 at 03:48:02PM +0000, Vivi, Rodrigo wrote:
> On Wed, 2016-08-03 at 17:26 +0200, Daniel Vetter wrote:
> > On Wed, Aug 3, 2016 at 5:12 PM, Vivi, Rodrigo <rodrigo.vivi@intel.com
> > > wrote:
> > > 
> > > 
> > > But we know that 1.23 is bad and cause issues regardless the kernel
> > > version. And please keep in mind this is the most common case.
> > > Usually a previous minor version was dropped in favor of a new one
> > > because we found a bug that got fixed in a following minor version.
> > > This is the minor version idea. So regardless the kernel version,
> > > the
> > > newest minor is probably safest than the previous one.
> > > 
> > > So, I don't want to keep all versions in linux-firmware.git,
> > > specially
> > > those that we know that cause bad issues.
> > > 
> > > And here is the case were only symbolic link would help imho.
> > If a system goes from "mostly works" to "fails because DMC isn't
> > there
> > any more" then that's a regression. Which means we _must_ resstore
> > 1.23.
> 
> From what I can remember it causes GPU Hangs depending on what you are
> running on the GPU.

Sounds like we should submit a fix to stable that makes the minimum
required version 1.26 if that's indeed the case. I wonder if this
the cause of all the hangs I've seen on my Skylake laptop lately;
I have both 1.23 and 1.26 installed, so I hadn't noticed that it's
loading 1.23 instead of 1.26.


Kind regards, David Weinehall
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2016-08-04 18:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-01 23:20 linux-firmware-i915 pull request (bxt dmc, kbl dmc) Vivi, Rodrigo
2016-07-05 13:43 ` Kyle McMartin
2016-07-06 23:36   ` Vivi, Rodrigo
2016-08-02 11:04 ` Jani Nikula
2016-08-02 20:48   ` Vivi, Rodrigo
2016-08-03  0:09     ` Ben Hutchings
2016-08-03  9:08       ` Jani Nikula
2016-08-03 15:02         ` Daniel Vetter
2016-08-03 15:06           ` Vivi, Rodrigo
2016-08-03 15:08             ` Daniel Vetter
2016-08-03 15:12               ` Vivi, Rodrigo
2016-08-03 15:26                 ` Daniel Vetter
2016-08-03 15:48                   ` Vivi, Rodrigo
2016-08-04 18:38                     ` David Weinehall [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=20160804183831.GC3542@boom \
    --to=david.weinehall@linux.intel.com \
    --cc=ben@decadent.org.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kmcmarti@redhat.com \
    --cc=kyle@infradead.org \
    --cc=linux-firmware@kernel.org \
    --cc=rodrigo.vivi@intel.com \
    /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