From: Florian Zumbiehl <florz@florz.de>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Daniel Vetter <daniel.vetter@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
David Airlie <airlied@linux.ie>
Subject: Re: i951 ERRORs and WARN_ON()s (was: blank screen on boot with i915/DRM_FBDEV_EMULATION)
Date: Tue, 12 Apr 2016 03:23:08 +0200 [thread overview]
Message-ID: <20160412012308.GD4861@florz.florz.de> (raw)
In-Reply-To: <20160330231430.GC6652@florz.florz.de>
Hi,
> > We've fixed piles of those in recent kernels, but didn't backport all the
> > fixes (since usually it's a silent failure, but it can correlate with
> > black screens).
>
> Not quite completely, it seems ...
>
> I have built drm-intel-nightly (f261f82359), and I'm getting this:
[...]
ping?
Regards, Florian
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-04-12 1:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 11:21 blank screen on boot with i915/DRM_FBDEV_EMULATION Florian Zumbiehl
2016-03-29 12:01 ` Daniel Vetter
2016-03-29 16:44 ` Florian Zumbiehl
2016-03-30 6:29 ` Daniel Vetter
2016-03-30 23:14 ` i951 ERRORs and WARN_ON()s (was: blank screen on boot with i915/DRM_FBDEV_EMULATION) Florian Zumbiehl
2016-04-12 1:23 ` Florian Zumbiehl [this message]
2016-04-27 10:03 ` Marius Vlad
2016-04-27 12:40 ` [Intel-gfx] " Florian Zumbiehl
2016-04-27 13:30 ` Jani Nikula
2016-04-29 2:27 ` i915 ERRORs and WARN_ON()s Florian Zumbiehl
2016-04-29 10:30 ` [Intel-gfx] " David Weinehall
2016-05-01 0:11 ` Florian Zumbiehl
2016-05-01 9:37 ` Daniel Vetter
2016-05-02 0:35 ` Florian Zumbiehl
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=20160412012308.GD4861@florz.florz.de \
--to=florz@florz.de \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--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