dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 208647] New: persistent amdgpu: [mmhub] page faults
Date: Tue, 21 Jul 2020 14:35:45 +0000	[thread overview]
Message-ID: <bug-208647-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=208647

            Bug ID: 208647
           Summary: persistent amdgpu: [mmhub] page faults
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.4.0-42-generic
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: jay.foad@gmail.com
        Regression: No

Whenever X is running I get persistent page faults like this:

Jul 21 15:19:16 jay-X470-AORUS-ULTRA-GAMING kernel: amdgpu 0000:0c:00.0:
amdgpu: [mmhub] page fault (src_id:0 ring:169 vmid:0 pasid:0, for process  pid
0 thread  pid 0)
Jul 21 15:19:16 jay-X470-AORUS-ULTRA-GAMING kernel: amdgpu 0000:0c:00.0:
amdgpu:   in page starting at address 0x00000000fffb0000 from client 18
Jul 21 15:19:16 jay-X470-AORUS-ULTRA-GAMING kernel: amdgpu 0000:0c:00.0:
amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00041F52
Jul 21 15:19:16 jay-X470-AORUS-ULTRA-GAMING kernel: amdgpu 0000:0c:00.0:
amdgpu:          Faulty UTCL2 client ID: 0xf
Jul 21 15:19:16 jay-X470-AORUS-ULTRA-GAMING kernel: amdgpu 0000:0c:00.0:
amdgpu:          MORE_FAULTS: 0x0
Jul 21 15:19:16 jay-X470-AORUS-ULTRA-GAMING kernel: amdgpu 0000:0c:00.0:
amdgpu:          WALKER_ERROR: 0x1
Jul 21 15:19:16 jay-X470-AORUS-ULTRA-GAMING kernel: amdgpu 0000:0c:00.0:
amdgpu:          PERMISSION_FAULTS: 0x5
Jul 21 15:19:16 jay-X470-AORUS-ULTRA-GAMING kernel: amdgpu 0000:0c:00.0:
amdgpu:          MAPPING_ERROR: 0x1
Jul 21 15:19:16 jay-X470-AORUS-ULTRA-GAMING kernel: amdgpu 0000:0c:00.0:
amdgpu:          RW: 0x1

Sometimes I get several of these per second. Sometimes there are none for a few
minutes.

If I boot into runlevel 3 (i.e. without starting X) I get one of these during
boot, but then there are no more after that.

I'm running Ubuntu 20.04 but I also saw this on 18.04.

Kernel version is 5.4.0-42-generic but I also saw this with 5.3.0-51-generic.

I'm using the amdgpu-pro drivers.

Graphics card is a Navi 10.

Motherboard is a Gigabyte X470 AORUS ULTRA GAMING.

CPU is an AMD Ryzen 9 3900X.

A very similar sounding bug was reported here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888116

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2020-07-21 14:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 14:35 bugzilla-daemon [this message]
2020-07-21 15:13 ` [Bug 208647] persistent amdgpu: [mmhub] page faults bugzilla-daemon
2020-07-21 15:15 ` bugzilla-daemon
2020-07-21 15:22 ` bugzilla-daemon
2020-07-21 15:26 ` bugzilla-daemon
2020-07-21 15:34 ` bugzilla-daemon
2020-09-28 15:17 ` bugzilla-daemon
2020-09-28 15:18 ` 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-208647-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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