Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marius Vlad <marius.c.vlad@intel.com>
To: Vladimir Miloserdov <milosvova@gmail.com>
Cc: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Subject: DMAR error -> GPU hang, [WAS Re: i915 bug]
Date: Fri, 3 Jun 2016 13:46:01 +0300	[thread overview]
Message-ID: <20160603104601.GA15522@mcvlad-wk.rb.intel.com> (raw)
In-Reply-To: <CAD1WXGzuwUycGzUWUqqE5pTqGcP3N3a7qMer_KkYLHTK2UUrQw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 830 bytes --]

Hi,

Thanks for the feedback. Have you tried with drm-intel-nightly [1] to see if
this still happens?

[1] https://anongit.freedesktop.org/git/drm-intel.git

CC'ing the list. Maybe someone is aware of this. Seems there are bunch
of duplicates for it.

On Thu, Jun 02, 2016 at 09:06:05PM +0300, Vladimir Miloserdov wrote:
> Hello
> 
> I am writing with the reference to this bug:
> https://bugs.freedesktop.org/show_bug.cgi?id=89360. It has been
> reported more than year ago and has not yet been even commented by a
> developer. I want to help as this bug is critical for me, but I don't
> know how. I've seen your email somewhere at bugzilla. Do you know
> someone, who could help? What can I do to help fixing this bug?
> 
> Thanks for your time and patience
> 
> Yours faithfully,
> Vladimir Miloserdov

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

           reply	other threads:[~2016-06-03 10:42 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAD1WXGzuwUycGzUWUqqE5pTqGcP3N3a7qMer_KkYLHTK2UUrQw@mail.gmail.com>]

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=20160603104601.GA15522@mcvlad-wk.rb.intel.com \
    --to=marius.c.vlad@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=milosvova@gmail.com \
    /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