From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 58354] [bisected] r600g: use DMA engine for VM page table updates on cayman locks in Unigine Tropics
Date: Sun, 23 Dec 2012 07:17:05 +0000 [thread overview]
Message-ID: <bug-58354-502-uwknm0HRKw@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-58354-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 5030 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=58354
--- Comment #9 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
Doesn't fix it, it locks as before. Sadly, dmesg seems to loose the count
because of another bug introduced in 3.8-rc1. Now that I moved to 3.8-rc1,
there is a huge amount of messages appearing in errors.log and dmesg (when
typed in the terminal):
...
[ 6223.054880] radeon 0000:01:00.0: GPU fault detected: 146 0x00239514
[ 6223.054882] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 6223.054883] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 6223.054885] radeon 0000:01:00.0: GPU fault detected: 146 0x00135514
[ 6223.054887] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 6223.054889] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 6223.054891] radeon 0000:01:00.0: GPU fault detected: 146 0x00239514
[ 6223.054893] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 6223.054895] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 6223.054897] radeon 0000:01:00.0: GPU fault detected: 146 0x0033a514
[ 6223.054899] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 6223.054900] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 6223.054902] radeon 0000:01:00.0: GPU fault detected: 146 0x00136514
[ 6223.054904] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 6223.054906] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 6223.054908] radeon 0000:01:00.0: GPU fault detected: 146 0x0033a514
[ 6223.054910] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 6223.054912] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 6223.054914] radeon 0000:01:00.0: GPU fault detected: 146 0x0033a514
[ 6223.054916] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 6223.054918] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 6223.054920] radeon 0000:01:00.0: GPU fault detected: 146 0x00232514
[ 6223.054922] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 6223.054923] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 6223.054925] radeon 0000:01:00.0: GPU fault detected: 146 0x00232514
[ 6223.054927] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 6223.054930] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 6223.054932] radeon 0000:01:00.0: GPU fault detected: 146 0x0033d514
[ 6223.054934] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 6223.054936] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 6223.054938] radeon 0000:01:00.0: GPU fault detected: 146 0x0033d514
[ 6223.054940] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 6223.054942] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 6223.054944] radeon 0000:01:00.0: GPU fault detected: 146 0x00235514
[ 6223.054946] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 6223.054948] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 6223.054950] radeon 0000:01:00.0: GPU fault detected: 146 0x00235514
[ 6223.054952] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 6223.054954] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 6223.054956] radeon 0000:01:00.0: GPU fault detected: 146 0x0033e514
[ 6223.054958] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 6223.054960] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 6223.054962] radeon 0000:01:00.0: GPU fault detected: 146 0x0033e514
[ 6223.054963] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 6223.054965] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 6223.054967] radeon 0000:01:00.0: GPU fault detected: 146 0x00339514
[ 6223.054969] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 6223.054971] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 6223.054973] radeon 0000:01:00.0: GPU fault detected: 146 0x00339514
[ 6223.054975] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 6223.054977] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 6223.054979] radeon 0000:01:00.0: GPU fault detected: 146 0x00236514
[ 6223.054980] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 6223.054982] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
...
I'm sure it is a different bug, can you confirm? dmesg.log stops to be
populated when X/Gnome start, but typing dmesg in a terminal outputs tons of
the reported messages. Should I open a new bug for it or has it been already
reported?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 5904 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2012-12-23 7:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 6:26 [Bug 58354] New: r600g locks up in Unigine Tropics with drm-next bugzilla-daemon
2012-12-16 17:40 ` [Bug 58354] [bisected] " bugzilla-daemon
2012-12-16 17:45 ` bugzilla-daemon
2012-12-18 6:29 ` [Bug 58354] [bisected] r600g: use DMA engine for VM page table updates on cayman locks in Unigine Tropics bugzilla-daemon
2012-12-23 0:12 ` bugzilla-daemon
2012-12-23 0:58 ` bugzilla-daemon
2012-12-23 2:27 ` bugzilla-daemon
2012-12-23 3:45 ` bugzilla-daemon
2012-12-23 3:46 ` bugzilla-daemon
2012-12-23 4:07 ` bugzilla-daemon
2012-12-23 7:17 ` bugzilla-daemon [this message]
2012-12-23 7:23 ` bugzilla-daemon
2013-01-03 22:05 ` bugzilla-daemon
2013-01-03 22:08 ` bugzilla-daemon
2013-01-08 5:58 ` bugzilla-daemon
2013-01-08 13:50 ` bugzilla-daemon
2013-01-09 1:24 ` bugzilla-daemon
2013-01-09 1:27 ` bugzilla-daemon
2013-01-09 13:58 ` bugzilla-daemon
2013-01-10 3:03 ` bugzilla-daemon
2013-01-10 18:04 ` bugzilla-daemon
2013-01-11 0:58 ` bugzilla-daemon
2013-01-11 1:01 ` bugzilla-daemon
2013-01-17 4:07 ` bugzilla-daemon
2013-01-31 20:22 ` bugzilla-daemon
2013-01-31 20:23 ` bugzilla-daemon
2013-02-01 3:58 ` bugzilla-daemon
2013-02-01 13:48 ` bugzilla-daemon
2013-02-23 10:28 ` bugzilla-daemon
2013-02-24 16:28 ` bugzilla-daemon
2014-01-26 11:33 ` 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-58354-502-uwknm0HRKw@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;
as well as URLs for NNTP newsgroup(s).