From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>, Dave Airlie <airlied@gmail.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Meyer <thomas@m3y3r.de>
Subject: Re: 3.15-rc5: Regression in i915 driver?
Date: Mon, 12 May 2014 10:09:54 +0300 [thread overview]
Message-ID: <87tx8v322l.fsf@intel.com> (raw)
In-Reply-To: <CAKMK7uG4Gnn_sY44Ci8VbRhJQf8=5s_dod4tRX+PDYYs1EYFsQ@mail.gmail.com>
On Sun, 11 May 2014, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> On Sun, May 11, 2014 at 11:02 AM, Dave Airlie <airlied@gmail.com> wrote:
>> On 11 May 2014 18:28, Thomas Meyer <thomas@m3y3r.de> wrote:
>>> Hi,
>>>
>>> 3.14.3 works as expected.
>>> 3.15-rc5 shows a strange behaviour: When resuming from ram the X server
>>> seems to be disfunctional.
>>>
>>> I see this WARNING in the kernel log before suspend to ram in the early
>>> boot process:
>
> Doesn't ring a bell really.
> - Is there anything in dmesg after resume?
> - How exactly does X misbehave? Is fbcon still working? Does X
> behaviour get restored if you restart X?
> - Can you please try to bisect this issue? Note that the backlight
> issue might be unrelated to the issues with X misbehaving after
> resume. You might need to do a bisect for both if the symptoms don't
> agree.
I agree the WARNING from i965_enable_backlight() is unrelated. Focus on
the other symptoms first.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>, Dave Airlie <airlied@gmail.com>
Cc: "intel-gfx\@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Meyer <thomas@m3y3r.de>
Subject: Re: [Intel-gfx] 3.15-rc5: Regression in i915 driver?
Date: Mon, 12 May 2014 10:09:54 +0300 [thread overview]
Message-ID: <87tx8v322l.fsf@intel.com> (raw)
In-Reply-To: <CAKMK7uG4Gnn_sY44Ci8VbRhJQf8=5s_dod4tRX+PDYYs1EYFsQ@mail.gmail.com>
On Sun, 11 May 2014, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> On Sun, May 11, 2014 at 11:02 AM, Dave Airlie <airlied@gmail.com> wrote:
>> On 11 May 2014 18:28, Thomas Meyer <thomas@m3y3r.de> wrote:
>>> Hi,
>>>
>>> 3.14.3 works as expected.
>>> 3.15-rc5 shows a strange behaviour: When resuming from ram the X server
>>> seems to be disfunctional.
>>>
>>> I see this WARNING in the kernel log before suspend to ram in the early
>>> boot process:
>
> Doesn't ring a bell really.
> - Is there anything in dmesg after resume?
> - How exactly does X misbehave? Is fbcon still working? Does X
> behaviour get restored if you restart X?
> - Can you please try to bisect this issue? Note that the backlight
> issue might be unrelated to the issues with X misbehaving after
> resume. You might need to do a bisect for both if the symptoms don't
> agree.
I agree the WARNING from i965_enable_backlight() is unrelated. Focus on
the other symptoms first.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-05-12 7:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 8:28 3.15-rc5: Regression in i915 driver? Thomas Meyer
2014-05-11 9:02 ` Dave Airlie
2014-05-11 9:02 ` Dave Airlie
2014-05-11 17:40 ` Daniel Vetter
2014-05-11 17:40 ` Daniel Vetter
2014-05-12 6:33 ` Chris Wilson
2014-05-12 6:33 ` [Intel-gfx] " Chris Wilson
2014-05-12 16:52 ` Daniel Vetter
2014-05-12 16:52 ` [Intel-gfx] " Daniel Vetter
2014-05-18 19:08 ` Thomas Meyer
2014-05-18 19:08 ` [Intel-gfx] " Thomas Meyer
2014-05-18 19:13 ` Chris Wilson
2014-05-18 19:13 ` [Intel-gfx] " Chris Wilson
2014-05-19 7:07 ` Daniel Vetter
2014-05-19 7:07 ` [Intel-gfx] " Daniel Vetter
2014-06-14 15:30 ` Thomas Meyer
2014-06-14 15:30 ` [Intel-gfx] " Thomas Meyer
2014-05-12 7:09 ` Jani Nikula [this message]
2014-05-12 7:09 ` Jani Nikula
2014-05-12 16:54 ` Daniel Vetter
2014-05-12 16:54 ` [Intel-gfx] " 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=87tx8v322l.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@m3y3r.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.