From: Mika Kahola <mika.kahola@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [BUGFIX] drm/i915: Fix for VBT expected size
Date: Thu, 13 Aug 2015 09:13:19 +0300 [thread overview]
Message-ID: <1439446399.5991.9.camel@sorvi> (raw)
In-Reply-To: <20150812134357.GX17734@phenom.ffwll.local>
On Wed, 2015-08-12 at 15:43 +0200, Daniel Vetter wrote:
> On Wed, Aug 12, 2015 at 04:42:53PM +0300, Jani Nikula wrote:
> > On Wed, 12 Aug 2015, Daniel Vetter <daniel@ffwll.ch> wrote:
> > > On Tue, Aug 11, 2015 at 04:49:33PM +0300, Mika Kahola wrote:
> > >> Depending on the VBT BDB version the maximum size
> > >> can be up to 38 bytes.
> > >>
> > >> This fix increases the maximum of the VBT expected size
> > >> from 33 bytes to 38 bytes and by doing so cures the kernel
> > >> hang on BSW box.
> > >>
> > >> Signed-off-by: Mika Kahola <mika.kahola@intel.com>
> > >
> > > We already have David's patch in -fixes, how does this relate? How does it
> > > blow up? Is this a regression? If so which commit created it? Where's the
> > > bugzilla link from QA?
> >
> > There's no bugzilla link from QA because Mika found the bug and I told
> > him to just send the patch.
>
> so bsw doesn't boot and QA didn't notice? That's fail too, just different
> kind of fail ...
> -Daniel
Well, there is now a bug report now which can be found
https://bugs.freedesktop.org/show_bug.cgi?id=91613
In addition, David refined his patch series, which relates to this issue
and therefore my bugfix can be ignored.
https://patchwork.freedesktop.org/patch/56911/
-Mika-
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-08-13 6:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 13:49 [BUGFIX] drm/i915: Fix for VBT expected size Mika Kahola
2015-08-12 13:18 ` Daniel Vetter
2015-08-12 13:42 ` Jani Nikula
2015-08-12 13:43 ` Daniel Vetter
2015-08-13 6:13 ` Mika Kahola [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=1439446399.5991.9.camel@sorvi \
--to=mika.kahola@intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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