From: Peter Zijlstra <peterz@infradead.org>
To: "Souza, Jose" <jose.souza@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Wilson, Chris P" <chris.p.wilson@intel.com>
Subject: Re: [Intel-gfx] [drm:gen8_de_irq_handler [i915]] *ERROR* Fault errors on pipe B: 0x00000080
Date: Tue, 2 Jun 2020 20:27:10 +0200 [thread overview]
Message-ID: <20200602182710.GD2604@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <5a40182c8a865d6c5603de4a1ff72c450ff403c3.camel@intel.com>
On Tue, Jun 02, 2020 at 06:08:03PM +0000, Souza, Jose wrote:
> Hi Peter
> Please file a bug by follow this instructions: https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs
*sigh*, top posting and webforms :-(
Steps to reproduce: Boot into X
How often: Always
uname -r: 5.6.0-2-amd64
Machine: Supermicro X11SSZ-F
Display connector:
[ 14.907] (II) intel(0): switch to mode 3840x2160@60.0 on DP2 using pipe 0, position (0, 0), rotation normal, reflection none
[ 14.918] (II) intel(0): switch to mode 3840x2160@60.0 on DP3 using pipe 1, position (0, 0), rotation normal, reflection none
I'll add the kernel parameters next time I reboot this thing, I'll also
add the latest drm next time I build a kernel for this machine.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-06-02 18:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 17:46 [Intel-gfx] [drm:gen8_de_irq_handler [i915]] *ERROR* Fault errors on pipe B: 0x00000080 Peter Zijlstra
2020-06-02 18:08 ` Souza, Jose
2020-06-02 18:27 ` Peter Zijlstra [this message]
2020-06-04 10:11 ` Peter Zijlstra
2020-06-05 22:46 ` Rodrigo Vivi
2021-04-07 13:18 ` Rodrigo Vivi
2021-04-07 15:48 ` Peter Zijlstra
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=20200602182710.GD2604@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=chris.p.wilson@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jose.souza@intel.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 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.