From: Peter Zijlstra <peterz@infradead.org>
To: jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
rodrigo.vivi@intel.com
Cc: intel-gfx@lists.freedesktop.org, chris.p.wilson@intel.com
Subject: [Intel-gfx] [drm:gen8_de_irq_handler [i915]] *ERROR* Fault errors on pipe B: 0x00000080
Date: Tue, 2 Jun 2020 19:46:39 +0200 [thread overview]
Message-ID: <20200602174639.GB2604@hirez.programming.kicks-ass.net> (raw)
Hi All,
My desktop (Intel(R) Xeon(R) CPU E3-1245 v5 @ 3.50GHz) is spewing tons
and tons of:
[ 778.461227] [drm:gen8_de_irq_handler [i915]] *ERROR* Fault errors on pipe B: 0x00000080
[ 778.477763] [drm:gen8_de_irq_handler [i915]] *ERROR* Fault errors on pipe B: 0x00000080
[ 778.577718] [drm:gen8_de_irq_handler [i915]] *ERROR* Fault errors on pipe B: 0x00000080
[ 778.577824] [drm:gen8_de_irq_handler [i915]] *ERROR* Fault errors on pipe B: 0x00000080
at a rate of ~3 per second, and X isn't as stable as one would like (it
crashes every few days, sometimes taking the whole kernel along). Sadly,
this being my desktop, I don't actually have a serial line connected to
it, although I could hook one up if required.
It is currently running 5.6.14-1 (as per debian testing), but it seems
to have done this for a while, I only now got around to reporting it :/
What else I you need to know, want me to try etc.. ?
~ Peter
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2020-06-02 17:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 17:46 Peter Zijlstra [this message]
2020-06-02 18:08 ` [Intel-gfx] [drm:gen8_de_irq_handler [i915]] *ERROR* Fault errors on pipe B: 0x00000080 Souza, Jose
2020-06-02 18:27 ` Peter Zijlstra
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=20200602174639.GB2604@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=chris.p.wilson@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=rodrigo.vivi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox