From: Daniel Vetter <daniel@ffwll.ch>
To: Felix Miata <mrmazda@earthlink.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: 3.14 issue with i810 graphic card bisected
Date: Thu, 15 May 2014 09:08:55 +0200 [thread overview]
Message-ID: <20140515070855.GN8790@phenom.ffwll.local> (raw)
In-Reply-To: <537410C1.4080406@earthlink.net>
On Wed, May 14, 2014 at 08:56:33PM -0400, Felix Miata wrote:
> On 2014-04-19 22:19 (GMT-0400) Felix Miata composed:
>
> >Has no one opened a freedesktop.org bug for this? I couldn't find one for
> >i810 changed more recently than 18 months ago.
>
> >I have an openSUSE i810E rev03 test system with 1.16.0 RC 2. Newest changelog
> >entry 08 April. Last intel driver 2.99.911.1-123.4 changelog entry 02 April.
>
> >OK with 3.11 kernel
> >http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-201419xorgx11-kern311OK
>
> >Bad with 3.14 kernel
> >http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-xorgx11-20140419-kern314BAD
>
> Bad also with 3.14.3 openSUSE kernel, but working with 3.15.rc5. Is the fix
> produced as a result of the bisection going to make it into 3.14 kernels?
If it's something we can reasonably backport, sure. If it's more invasive
then we need to figure out what to do instead.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-05-15 7:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 6:37 3.14 issue with i810 graphic card bisected Tobias Powalowski
2014-04-18 20:38 ` Tejun Heo
2014-04-19 5:36 ` Tobias Powalowski
2014-04-19 18:00 ` Tobias Powalowski
2014-04-19 19:00 ` Tobias Powalowski
2014-04-20 2:19 ` Felix Miata
2014-05-15 0:56 ` Felix Miata
2014-05-15 7:08 ` Daniel Vetter [this message]
2014-04-20 12:29 ` [PATCH driver-core-linus] kernfs: add back missing error check in kernfs_fop_mmap() Tejun Heo
2014-04-20 16:55 ` Tobias Powalowski
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=20140515070855.GN8790@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mrmazda@earthlink.net \
/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