From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 63135] [bisected] G69/nv50 DisplayPort dual-head fails to switch to KMS
Date: Wed, 05 Jun 2013 12:57:30 +0000 [thread overview]
Message-ID: <bug-63135-8800-gZ0ozP6DO2@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-63135-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 644 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=63135
--- Comment #10 from Emil Velikov <emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Nooo, why did it have to lead to that commit :(
Devin I don't suppose you have a debug dmesg closer to the offending commit, do
you ? The delta between these two is quite substantial
My initial suspect is that the DP data stored(or it's parsing) in is to blame
for your issue
Working
* Appears to be parsed properly?
* unknown opcode 0x44
Failing
* nouveau E[ PDISP][0000:03:00.0] DP:0006:0382: bios data not found
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1423 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2013-06-05 12:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 21:17 [Bug 63135] New: [bisected] G69/nv50 DisplayPort dual-head fails to switch to KMS bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-63135-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-04-04 21:17 ` [Bug 63135] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-04-04 21:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-04-04 21:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-13 17:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-16 8:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-28 22:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-28 22:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-29 11:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-30 1:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-03 17:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-05 12:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2013-06-05 13:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-05 14:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-05 15:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-06 22:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-06 22:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-06 22:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-06 22:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-06 22:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-06 22:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-07 14:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-13 20:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-26 17:23 ` [Bug 63135] [NV96] [bisected] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-26 22:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 2:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 2:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 2:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-63135-8800-gZ0ozP6DO2@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.