From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
Date: Mon, 15 Oct 2012 14:27:57 +0000 [thread overview]
Message-ID: <bug-55692-502-ifoXf6J7Mp@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-55692-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 493 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=55692
--- Comment #18 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
Is VM enabled or disabled on your system? I'm experiencing a similar bug with
kernel 3.7-rc1, but it is working fine with 3.6. VM is enabled on my system,
I'll try to disable it when I'll get home to see if that helps and I'll also
try to bisect the kernel commit that screwed things for me.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1374 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-10-15 14:27 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 11:48 [Bug 55692] New: [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0) bugzilla-daemon
2012-10-06 11:48 ` [Bug 55692] " bugzilla-daemon
2012-10-06 11:49 ` bugzilla-daemon
2012-10-06 11:49 ` bugzilla-daemon
2012-10-06 11:53 ` bugzilla-daemon
2012-10-06 11:55 ` bugzilla-daemon
2012-10-06 12:07 ` bugzilla-daemon
2012-10-06 12:51 ` bugzilla-daemon
2012-10-06 13:40 ` bugzilla-daemon
2012-10-07 13:23 ` bugzilla-daemon
2012-10-13 10:31 ` bugzilla-daemon
2012-10-13 10:37 ` bugzilla-daemon
2012-10-13 12:18 ` bugzilla-daemon
2012-10-13 12:52 ` bugzilla-daemon
2012-10-13 12:54 ` bugzilla-daemon
2012-10-13 19:31 ` bugzilla-daemon
2012-10-13 19:33 ` bugzilla-daemon
2012-10-14 4:30 ` bugzilla-daemon
2012-10-15 14:27 ` bugzilla-daemon [this message]
2012-10-15 14:31 ` bugzilla-daemon
2012-10-15 14:49 ` bugzilla-daemon
2012-10-15 15:22 ` bugzilla-daemon
2012-10-15 15:27 ` bugzilla-daemon
2012-10-16 15:09 ` bugzilla-daemon
2012-10-16 23:37 ` bugzilla-daemon
2012-10-16 23:38 ` bugzilla-daemon
2012-10-17 3:44 ` bugzilla-daemon
2012-10-17 14:10 ` bugzilla-daemon
2012-10-17 14:16 ` bugzilla-daemon
2012-10-17 15:41 ` bugzilla-daemon
2012-10-17 15:58 ` bugzilla-daemon
2012-10-17 16:02 ` bugzilla-daemon
2012-10-17 18:15 ` bugzilla-daemon
2012-10-17 18:17 ` bugzilla-daemon
2012-10-17 19:45 ` bugzilla-daemon
2012-10-17 22:06 ` bugzilla-daemon
2012-10-17 22:10 ` bugzilla-daemon
2012-10-17 22:11 ` bugzilla-daemon
2012-10-17 22:43 ` bugzilla-daemon
2012-10-17 22:53 ` bugzilla-daemon
2012-10-18 6:29 ` bugzilla-daemon
2012-10-18 8:33 ` bugzilla-daemon
2012-10-18 8:40 ` bugzilla-daemon
2012-10-19 12:46 ` bugzilla-daemon
2012-10-19 22:39 ` bugzilla-daemon
2012-10-20 18:23 ` bugzilla-daemon
2012-10-22 9:00 ` bugzilla-daemon
2012-10-22 22:39 ` bugzilla-daemon
2012-10-22 22:39 ` bugzilla-daemon
2012-10-22 22:40 ` bugzilla-daemon
2012-10-22 22:42 ` bugzilla-daemon
2013-01-05 19:43 ` bugzilla-daemon
2013-01-05 20:16 ` bugzilla-daemon
2013-01-31 13:35 ` bugzilla-daemon
2013-01-31 13:37 ` 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-55692-502-ifoXf6J7Mp@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).