From: Thomas Meyer <thomas@m3y3r.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dave Airlie <airlied@gmail.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
" intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] 3.15-rc5: Regression in i915 driver?
Date: Sat, 17 May 2014 19:43:42 +0200 [thread overview]
Message-ID: <E1WlieE-0007VZ-Fr@www17.your-server.de> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1866 bytes --]
3.15-rc2 seems to be good, 3.15-rc5 seems to be bad. Bisecting this the next days.
Am 12.05.2014 18:54 schrieb Daniel Vetter <daniel@ffwll.ch>:
>
> On Mon, May 12, 2014 at 10:09:54AM +0300, Jani Nikula wrote:
> > 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.
>
> The backlight backtrace seems to be a genuine new bug. Bisecting it would
> be highly appreciated. Bisecting on the other issue and appending the
> result to the bug Chris quoated should also really be useful - atm we
> don't have any reported who can reproduce this clearly enough to do a
> bisect.
> -Daniel
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next reply other threads:[~2014-05-17 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 17:43 Thomas Meyer [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-11 8:28 Thomas Meyer
2014-05-11 9:02 ` Dave Airlie
2014-05-11 17:40 ` Daniel Vetter
2014-05-12 6:33 ` [Intel-gfx] " Chris Wilson
2014-05-12 16:52 ` Daniel Vetter
2014-05-18 19:08 ` Thomas Meyer
2014-05-18 19:13 ` Chris Wilson
2014-05-19 7:07 ` Daniel Vetter
2014-06-14 15:30 ` Thomas Meyer
2014-05-12 7:09 ` Jani Nikula
2014-05-12 16:54 ` 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=E1WlieE-0007VZ-Fr@www17.your-server.de \
--to=thomas@m3y3r.de \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--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
all inboxes | Powered by JetHome®