All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111448] [AMD TAHITI XT] IO_PAGE_FAULT
Date: Wed, 21 Aug 2019 03:49:23 +0000	[thread overview]
Message-ID: <bug-111448-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 111448
           Summary: [AMD TAHITI XT] IO_PAGE_FAULT
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: sylvain.bertrand@gmail.com

Updated my gfx stack this week, and in the kernel log I get tons of
IO_PAGE_FAULT . Everything git from last sunday/monday.
linux amd-staging-drm-next 6c7a8d5c0772d8a389997cd5e35e8fa83f830f41
drm 14922551aa33e7592d2421cc89cf20a860a65310
llvm c81cf445a3132cf48fbe8f75f0314cbd346d87ab
mesa c550d367a747472ee71ed4c99e210174730aa82b
xserver aed62f8fbea3f618f97ee0105b2d430c8cddf8f5
xf86-video-amdgpu e6fce59a071220967fcd4e2c9e4a262c72870761

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

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

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

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

             reply	other threads:[~2019-08-21  3:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-21  3:49 bugzilla-daemon [this message]
2019-08-21  3:50 ` [Bug 111448] [AMD TAHITI XT] IO_PAGE_FAULT bugzilla-daemon
2019-08-21  3:51 ` bugzilla-daemon
2019-08-25 18:41 ` 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-111448-502@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 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.