From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 45641] Screen goes black randomly
Date: Tue, 19 Mar 2013 14:01:23 +0000 [thread overview]
Message-ID: <bug-45641-502-0brKzFf8eM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-45641-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 604 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=45641
--- Comment #11 from Alex Deucher <agd5f@yahoo.com> ---
(In reply to comment #10)
> > For systems where this is a regression, can you bisect?
>
> I don't understand. Could you explain this question please (if it was to me)?
If it worked with an older kernel, you can use git to bisect between working
kernel and the the broken one. Bisecting allows you to pinpoint the change
that caused the problem. There are a number of good tutorials on using git to
bisect a problem.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1408 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-03-19 14:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-45641-502@http.bugs.freedesktop.org/>
2012-02-07 18:13 ` [Bug 45641] Screen goes black randomly bugzilla-daemon
2012-02-07 20:22 ` bugzilla-daemon
2012-06-15 23:36 ` bugzilla-daemon
2013-03-19 10:16 ` bugzilla-daemon
2013-03-19 12:53 ` bugzilla-daemon
2013-03-19 13:43 ` bugzilla-daemon
2013-03-19 14:01 ` bugzilla-daemon [this message]
2013-03-19 14:06 ` bugzilla-daemon
2013-03-19 14:22 ` bugzilla-daemon
2013-03-19 14:49 ` bugzilla-daemon
2013-03-19 16:35 ` bugzilla-daemon
2013-03-22 12:24 ` bugzilla-daemon
2013-03-22 14:15 ` bugzilla-daemon
2013-04-01 1:05 ` bugzilla-daemon
2013-10-03 17:57 ` bugzilla-daemon
2018-07-20 8:57 ` bugzilla-daemon
2018-07-20 8:57 ` 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-45641-502-0brKzFf8eM@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).