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 94242] [radeonsi] Crash while running Fedora mock tool for prompting root (gtksu)
Date: Mon, 22 Feb 2016 02:49:30 +0000	[thread overview]
Message-ID: <bug-94242-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 94242
           Summary: [radeonsi] Crash while running Fedora mock tool for
                    prompting root (gtksu)
           Product: Mesa
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: shawn.starr@rogers.com
        QA Contact: dri-devel@lists.freedesktop.org

Kernel: 4.5.0-0.rc4.git2.2.fc24.x86_64
MESA: git master, Feb 19-20th builds
LLVM: trunk 3.9, Feb 19-20th builds
DDX: 

For some reason, X crashes with radeonsi triggering VM fault, when in GNOME or
KDE environments:


If you open up a shell console (gnome-terminal, konsole etc), run mock as
non-root, as soon as an attempt to prompt for root happens (with gtksu) it
locks up system.

[   38.111551] radeon 0000:01:00.0: GPU fault detected: 146 0x0008480c
[   38.111861] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00000000
[   38.112219] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0804800C
[   38.112576] VM fault (0x0c, vmid 4) at page 0, read from 'TC2' (0x54433200)
(72)
[   38.112931] radeon 0000:01:00.0: GPU fault detected: 146 0x0008440c
[   38.113229] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x08000000
[   38.113587] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x08044001
[   38.113945] VM fault (0x01, vmid 4) at page 134217728, read from 'TC3'
(0x54433300) (68)

I've attached a VM fault debug of crash

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

[-- Attachment #1.2: Type: text/html, Size: 3036 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

             reply	other threads:[~2016-02-22  2:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22  2:49 bugzilla-daemon [this message]
2016-02-22  2:50 ` [Bug 94242] [radeonsi] Crash while running Fedora mock tool for prompting root (gtksu) bugzilla-daemon
2016-02-22  7:04 ` bugzilla-daemon
2016-02-23  7:19 ` bugzilla-daemon
2016-02-23 15:39 ` bugzilla-daemon
2016-02-24  1:43 ` bugzilla-daemon
2016-02-25 16:55 ` bugzilla-daemon
2016-02-26  9:08 ` bugzilla-daemon
2016-02-26 11:20 ` bugzilla-daemon
2016-02-26 15:12 ` bugzilla-daemon
2016-02-26 16:21 ` bugzilla-daemon
2016-02-26 16:29 ` bugzilla-daemon
2016-03-07  6:02 ` bugzilla-daemon
2016-03-09 18:37 ` bugzilla-daemon
2016-03-10 17:02 ` bugzilla-daemon
2016-03-15  7:17 ` 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-94242-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox