From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 64776] [9.1.2]"GPU fault detected" whit "eclipse juno" crash system
Date: Mon, 20 May 2013 14:15:47 +0000 [thread overview]
Message-ID: <bug-64776-502-vxPnVUFLgS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-64776-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1519 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=64776
--- Comment #5 from mombelli.mauro@gmail.com ---
ok, never heard of this git's feature, really nice and useful!
I'll try to bisect when i'll have some spare time.
2013/5/20 <bugzilla-daemon@freedesktop.org>
> *Comment # 4 <https://bugs.freedesktop.org/show_bug.cgi?id=64776#c4> on bug
> 64776 <https://bugs.freedesktop.org/show_bug.cgi?id=64776> from Alex
> Deucher <agd5f@yahoo.com> *
>
> (In reply to comment #3 <https://bugs.freedesktop.org/show_bug.cgi?id=64776#c3>)
> > I have no idea where to start.
> > I know how to compile code and debug program, but i have no clue on the
> > mesa's code structure, and how it works.
> > I don't know what CB6 is, i'm not sure about page meaning (is it similar to
> > "classic" RAM page?) etc..
> > can you tell me at least witch bunch of file/operation i have to debug, and
> > how?
>
>
> CB6 is the 6th color buffer and the GPU has a VM page table just like the CPU.
> That info is not really important for you, I mentioned it for other developers.
> If you could bisect mesa using git, that would be great. There are a lot of
> howtos for using git to bisect. E.g.,https://wiki.ubuntu.com/X/BisectingMesa
>
> In your case, it would be something like:
> git bisect start
> git bisect bad mesa-9.1.2
> git bisect good mesa-9.1.1
>
> ------------------------------
> You are receiving this mail because:
>
> - You reported the bug.
>
>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3468 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-05-20 14:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 0:01 [Bug 64776] New: [9.1.2]"GPU fault detected" whit "eclipse juno" crash system bugzilla-daemon
2013-05-20 0:02 ` [Bug 64776] " bugzilla-daemon
2013-05-20 13:18 ` bugzilla-daemon
2013-05-20 13:29 ` bugzilla-daemon
2013-05-20 13:44 ` bugzilla-daemon
2013-05-20 14:15 ` bugzilla-daemon [this message]
2013-05-22 11:27 ` bugzilla-daemon
2013-05-23 0:01 ` bugzilla-daemon
2013-05-29 20:07 ` bugzilla-daemon
2013-05-30 7:16 ` bugzilla-daemon
2013-05-30 21:24 ` bugzilla-daemon
2013-05-31 9:14 ` bugzilla-daemon
2013-05-31 21:55 ` bugzilla-daemon
2013-05-31 22:03 ` bugzilla-daemon
2016-05-24 14:05 ` bugzilla-daemon
2017-03-17 2:06 ` 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-64776-502-vxPnVUFLgS@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