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: [Intel-gfx] i951 ERRORs and WARN_ON()s (was: blank screen on boot with i915/DRM_FBDEV_EMULATION)
Date: Wed, 27 Apr 2016 14:40:45 +0200 [thread overview]
Message-ID: <20160427124045.GF26959@florz.florz.de> (raw)
In-Reply-To: <20160427100340.GA14968@mcvlad-wk.rb.intel.com>
Hi,
> Florian, if you're using drm-intel-nigthly submit a bug at
> https://bugs.freedesktop.org/enter_bug.cgi?product=DRI, with DRM/intel
> as component. This way we can track some kind of progress/regress. The FIFO
Gee ... is there any way without "creating an account"? Having to create
accounts everywhere to be able to communicate with people just sucks. I
mean, do you want to create an account in my todo tracker and use my todo
tracker's web interface to coordinate the bug investigation? Use whatever
software you like for managing your todo lists, but please, don't bother me
with having to use it for you.
> underruns should've have been fixed, but maybe there's something related
> to your platform.
You mean the ones I reported a month ago should be fixed? Should I try a
newer nightly to check?
What about the Xv stuttering?
Regards, Florian
prev parent reply other threads:[~2016-04-27 12:40 UTC|newest]
Thread overview: 8+ 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 ` [Intel-gfx] " 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
2016-04-27 10:03 ` [Intel-gfx] " Marius Vlad
2016-04-27 12:40 ` Florian Zumbiehl [this message]
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=20160427124045.GF26959@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
all inboxes | Powered by JetHome®