From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 79696] 10.2.x GPU stall & Xorg crash while using Geeqie
Date: Fri, 04 Jul 2014 11:16:09 +0000 [thread overview]
Message-ID: <bug-79696-502-NPpuBGInwL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-79696-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1064 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=79696
--- Comment #17 from Marek Olšák <maraeo@gmail.com> ---
(In reply to comment #16)
> My most stable test case is unfortunately the Mathematica welcome screen.
> After some 5 mins of work in Chrome followed by a couple of Mathematica
> restarts, like 5-10, the lockup or segfault happens. Geeqie didn't do
> anything for me.
>
> I haven't made any good progress with bisecting other than reconfirming that
>
> http://cgit.freedesktop.org/mesa/mesa/commit/
> ?id=cb4ad1368551b64756c7b6e2007588e34739b188
>
> fixes a segfault. This fix uncovers the lockup behavior.
The commit fixes code which isn't used by radeonsi. I guess the bisection went
wrong.
>
> Maybe apitrace is a way forward to generate something more testable.
>
> Marek: Can you provide more information on the other known problem?
Kernel 3.15-rc1 and later locks up randomly. There is a memory corruption when
page tables are moved.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2063 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:[~2014-07-04 11:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 18:34 [Bug 79696] New: 10.2.0rc5 GPU stall & Xorg crash while using Geeqie bugzilla-daemon
2014-06-05 18:35 ` [Bug 79696] " bugzilla-daemon
2014-06-05 18:35 ` bugzilla-daemon
2014-06-06 3:18 ` bugzilla-daemon
2014-06-06 10:57 ` bugzilla-daemon
2014-06-06 14:20 ` bugzilla-daemon
2014-06-06 22:37 ` bugzilla-daemon
2014-06-06 22:52 ` bugzilla-daemon
2014-06-09 7:38 ` bugzilla-daemon
2014-06-11 21:17 ` bugzilla-daemon
2014-06-12 3:19 ` bugzilla-daemon
2014-06-12 9:31 ` bugzilla-daemon
2014-06-12 13:44 ` bugzilla-daemon
2014-06-30 7:25 ` bugzilla-daemon
2014-07-01 11:37 ` bugzilla-daemon
2014-07-01 12:33 ` bugzilla-daemon
2014-07-01 13:55 ` [Bug 79696] 10.2.x " bugzilla-daemon
2014-07-04 9:10 ` bugzilla-daemon
2014-07-04 11:16 ` bugzilla-daemon [this message]
2014-07-04 18:12 ` bugzilla-daemon
2014-08-11 19:52 ` bugzilla-daemon
2014-08-31 19:37 ` bugzilla-daemon
2014-09-01 6:04 ` bugzilla-daemon
2014-09-01 6:17 ` bugzilla-daemon
2014-12-11 20:11 ` bugzilla-daemon
2014-12-11 20: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-79696-502-NPpuBGInwL@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