From: Woody Suwalski <terraluna977@gmail.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3.12 regression: i915 warnings
Date: Sat, 28 Sep 2013 16:33:32 -0400 [thread overview]
Message-ID: <52473D1C.5010003@gmail.com> (raw)
In-Reply-To: <CAKMK7uFZ35gruMYHB+LXEDVoAof7n-1oYGxWkky_tLe3ELLxWQ@mail.gmail.com>
Daniel Vetter wrote:
> On Fri, Sep 27, 2013 at 7:27 PM, Woody Suwalski <terraluna977@gmail.com> wrote:
>> Daniel Vetter wrote:
>>> On Thu, Sep 26, 2013 at 2:36 PM, Woody Suwalski <terraluna977@gmail.com>
>>> wrote:
>>>> Daniel, I have noticed these warnings on 3.12-rc1, did not go away on
>>>> 3.12-rc2.
>>>> I see it only on EeePC with i915,not on ThinkPad with Radeon.
>>>> It is a 32-bit kernel with overlayfs and TuxOnIce patches, so not
>>>> perfectly
>>>> clean, however same config and patches on 3.11 do not show these issues.
>>>> No,sorry, did not have time to investigate further or bisect.If you have
>>>> a
>>>> quick test in mind - I will try ;-)
>>>
>>> a) Please always cc: relevant mailing lists, not just your maintainer.
>>> b) Please retest with latest drm-intel-fixes from
>>> http://cgit.freedesktop.org/~danvet/drm-intel/
>>> c) If that doesn't help please boot with drm.debug=0xe, reproduce the
>>> issue once and attach the complete dmesg. Please make sure that it
>>> contains everything from boot-up to the WARN.
>>>
>>> Thanks, Daniel
>> For now I can do the last - a complete dmesg with drm.debug attached...
>> I have hoped that you were to reply "Yawn, an old issue..." 8-)
> Here we go: Mode flag mismatch in the tv encoder, should be fixed with
>
> http://cgit.freedesktop.org/~danvet/drm-intel/commit/?id=1062b81598bc00e2f6620e6f3788f8f8df2f01e7
>
> Pull request is already out and patch is cc: stable, so should show up
> in a kernel near you soon.
> -Daniel
Warnings are gone with this patch (and other 4 patches since 3.2.12-rc2
from drm tree).
Thanks, Woody
next prev parent reply other threads:[~2013-09-28 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52442A3C.3010407@gmail.com>
[not found] ` <CAKMK7uFvP7zisHL4UFjRqBX8mxS4DtosF2AFnwZDSdMgnDf4Lw@mail.gmail.com>
2013-09-27 17:27 ` 3.12 regression: i915 warnings Woody Suwalski
2013-09-27 19:03 ` Daniel Vetter
2013-09-28 20:33 ` Woody Suwalski [this message]
2013-09-28 20:40 ` Daniel Vetter
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=52473D1C.5010003@gmail.com \
--to=terraluna977@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--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