From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 58667] Random crashes on CAYMAN
Date: Sat, 05 Jan 2013 20:26:53 +0000 [thread overview]
Message-ID: <bug-58667-502-ymvxzsyyPb@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-58667-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1242 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=58667
--- Comment #24 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
(In reply to comment #23)
> (In reply to comment #22)
> > "Is this a regression? Does it happen with older versions of mesa or
> > kernel?"
> > Yes. Previous kernel 3.7 doesn't show this problem.
>
> Can you bisect? Is it the same commit Thomas landed on or another one?
Pretty sure it is the same problem. With kernel 3.8.0-rcx, just launching Gnome
Shell starts flooding my logs of:
radeon 0000:0X:00.0: GPU fault detected: 146 0x00xxxxxx
radeon 0000:0X:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000
radeon 0000:0X:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
I'll bisect between 3.7 and 3.8-rc1 and see if I end up at the same thing.
Having a crash here and there from time to time may be coming from something
different, but the incessant flood is a big one. In a single session, I end up
with kernel.log and everything.log being over 52GB each. I'm also sure this
message have to be triggered is something wrong is going on. I'll let you know
when I'm done bisecting to figure out what is triggering this flood.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2124 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:[~2013-01-05 20:26 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-23 0:05 [Bug 58667] New: Random crashes on CAYMAN bugzilla-daemon
2012-12-23 0:07 ` [Bug 58667] " bugzilla-daemon
2012-12-23 0:08 ` bugzilla-daemon
2012-12-23 0:13 ` bugzilla-daemon
2012-12-23 1:28 ` bugzilla-daemon
2012-12-23 1:30 ` bugzilla-daemon
2012-12-23 19:15 ` bugzilla-daemon
2012-12-23 19:35 ` bugzilla-daemon
2012-12-23 19:45 ` bugzilla-daemon
2012-12-23 21:45 ` bugzilla-daemon
2012-12-23 22:29 ` bugzilla-daemon
2012-12-25 19:21 ` bugzilla-daemon
2012-12-25 23:25 ` bugzilla-daemon
2012-12-25 23:46 ` bugzilla-daemon
2012-12-25 23:59 ` bugzilla-daemon
2012-12-26 0:20 ` bugzilla-daemon
2012-12-26 0:31 ` bugzilla-daemon
2012-12-26 0:32 ` bugzilla-daemon
2012-12-26 0:37 ` bugzilla-daemon
2012-12-26 6:40 ` bugzilla-daemon
2012-12-26 7:08 ` bugzilla-daemon
2012-12-26 7:42 ` bugzilla-daemon
2013-01-03 22:08 ` bugzilla-daemon
2013-01-03 22:10 ` bugzilla-daemon
2013-01-04 15:20 ` bugzilla-daemon
2013-01-05 20:26 ` bugzilla-daemon [this message]
2013-01-05 20:47 ` bugzilla-daemon
2013-01-05 20:57 ` bugzilla-daemon
2013-01-06 0:11 ` bugzilla-daemon
2013-01-06 3:30 ` bugzilla-daemon
2013-01-06 20:39 ` bugzilla-daemon
2013-01-06 20:43 ` bugzilla-daemon
2013-01-07 20:33 ` bugzilla-daemon
2013-01-08 4:59 ` bugzilla-daemon
2013-01-09 1:49 ` bugzilla-daemon
2013-01-09 13:59 ` bugzilla-daemon
2013-01-12 10:41 ` bugzilla-daemon
2013-01-12 11:59 ` bugzilla-daemon
2013-01-14 15:48 ` bugzilla-daemon
2013-01-17 0:21 ` bugzilla-daemon
2013-01-17 17:28 ` bugzilla-daemon
2013-01-17 18:42 ` bugzilla-daemon
2013-01-17 19:27 ` bugzilla-daemon
2013-01-23 7:10 ` bugzilla-daemon
2013-01-30 8:40 ` bugzilla-daemon
2013-01-30 9:13 ` bugzilla-daemon
2013-01-30 9:26 ` bugzilla-daemon
2014-01-23 15:14 ` bugzilla-daemon
2014-01-23 15:18 ` [Bug 58667] VM-related " bugzilla-daemon
2014-01-23 15:20 ` bugzilla-daemon
2014-01-26 10:19 ` 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-58667-502-ymvxzsyyPb@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