dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100437] IO_PAGE_FAULT is spammed in dmesg
Date: Mon, 22 May 2017 22:00:12 +0000	[thread overview]
Message-ID: <bug-100437-502-dQ0AAj9IaB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100437-502@http.bugs.freedesktop.org/>


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

https://bugs.freedesktop.org/show_bug.cgi?id=100437

--- Comment #9 from Greg Turner <gmt@be-evil.net> ---
Just another datapoint on this...

I have this disease with a (non-reference) Asus RX480 in an Asus Sabertooth
Gen3 R2.0 (or something like that, I can never remember exactly what it's
called).  It does not fix itself when I reboot.

If I turn off IOMMU entirely in the BIOS (not just the memory hole), then it
goes away (along, of course, with my iommu functionality, which I'm not
thrilled about).

I can also boot and avoid the spam with iommu=pt or iommu=soft.

I have also seen brief "flashing screen" artifacts in xorg, which get more
frequent if I stress the system (doesn't need to be graphics related).  Whether
these correlate with the log spam, I'm not entirely sure.  I think it may, but
it might instead have been related to a firmware loading problem that I've
since resolved... I'd have to try it again to be sure.

Like the OP, when I get the log spam I also see this:

May 22 14:23:21 moneypit kernel: amdgpu: [powerplay] [AVFS] Something is
broken. See log!
May 22 14:23:21 moneypit kernel: amdgpu: [powerplay] Can't find requested
voltage id in vdd_dep_on_sclk table!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2075 bytes --]

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

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-05-22 22:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-100437-502@http.bugs.freedesktop.org/>
2017-03-29  1:46 ` [Bug 100437] IO_PAGE_FAULT is spammed in dmesg, powerplay error bugzilla-daemon
2017-03-29  8:05 ` [Bug 100437] IO_PAGE_FAULT is spammed in dmesg bugzilla-daemon
2017-03-29 20:07 ` bugzilla-daemon
2017-05-07  6:15 ` bugzilla-daemon
2017-05-08 11:42 ` bugzilla-daemon
2017-05-08 21:37 ` bugzilla-daemon
2017-05-17 14:12 ` bugzilla-daemon
2017-05-18 15:43 ` bugzilla-daemon
2017-05-22 22:00 ` bugzilla-daemon [this message]
2017-05-23  9:23 ` bugzilla-daemon
2017-06-12 11:31 ` bugzilla-daemon
2017-12-15  8:04 ` bugzilla-daemon

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=bug-100437-502-dQ0AAj9IaB@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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