From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
Subject: [Bug 63135] [bisected] G69/nv50 DisplayPort dual-head
fails to switch to KMS
Date: Thu, 06 Jun 2013 22:37:01 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1949047466=="
Return-path:
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: nouveau-bounces+gcfxn-nouveau=m.gmane.org-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Errors-To: nouveau-bounces+gcfxn-nouveau=m.gmane.org-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
List-Id: nouveau.vger.kernel.org
--===============1949047466==
Content-Type: multipart/alternative; boundary="1370558220.ae7EC1.7058"; charset="us-ascii"
--1370558220.ae7EC1.7058
Date: Thu, 6 Jun 2013 22:37:00 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
https://bugs.freedesktop.org/show_bug.cgi?id=63135
--- Comment #18 from Devin J. Pohly ---
No, the original problem was not 100% reproducible. It always felt (this is
only a guess) like it had something to do with how long the KMS switch took...
if it took too long, the monitors went into powersave, and the system would
almost certainly hang.
There seem to be three possibilities for a boot on a bugged revision:
1. Everything works.
2. Displays go into powersave, system hangs, and you can't ssh or use SysRq.
3. (Rare.) Displays go into powersave but you can still use SysRq.
For the latest attachments, I used a serial console to reliably get logs from
cases 1 and 2. The original logs (from a 3.9-series kernel) relied on getting
case 3 so I could REISUB and read the logs on next boot, but this may not show
the bug properly. Would you like me to get logs from a recent kernel using the
serial console so you can compare?
--
You are receiving this mail because:
You are the assignee for the bug.
--1370558220.ae7EC1.7058
Date: Thu, 6 Jun 2013 22:37:00 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Comment # 18
on bug 63135
from Devin J. Pohly
No, the original problem was not 100% reproducible. It always felt (this is
only a guess) like it had something to do with how long the KMS switch took...
if it took too long, the monitors went into powersave, and the system would
almost certainly hang.
There seem to be three possibilities for a boot on a bugged revision:
1. Everything works.
2. Displays go into powersave, system hangs, and you can't ssh or use SysRq.
3. (Rare.) Displays go into powersave but you can still use SysRq.
For the latest attachments, I used a serial console to reliably get logs from
cases 1 and 2. The original logs (from a 3.9-series kernel) relied on getting
case 3 so I could REISUB and read the logs on next boot, but this may not show
the bug properly. Would you like me to get logs from a recent kernel using the
serial console so you can compare?
You are receiving this mail because:
- You are the assignee for the bug.
--1370558220.ae7EC1.7058--
--===============1949047466==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
--===============1949047466==--