Nouveau Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 67382] [nouveau, nv50] linux 3.9.7-3.10.3: Xorg won't be available
Date: Sat, 27 Jul 2013 10:32:03 +0000	[thread overview]
Message-ID: <bug-67382-8800-ZPRLoXboTy@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-67382-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2397 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=67382

--- Comment #3 from Emil Velikov <emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
(In reply to comment #0)
> After looking at #66129 and testing linux 3.10.3 (includes the patches from
> 66129) and still having problems, I decided to open a bugreport, as the
> problem appears to be something else.
> I'm not sure if the topic describes the problem really well.
> 
> 
> First I should mention, that I wrote a bugreport on the kernel tracker:
> https://bugzilla.kernel.org/show_bug.cgi?id=60071
> Which was probably the wrong place, and a complete different description.
> 
> 
> Machine:
> One from the nv50 (8800 GTS) graphic cards. One monitor.
> 
So in case of 3.9.7 your system seems to be detecting a ghost monitor, hooked
up to your DVI-I-2. Did I get that right?

> Notes:
> *early KMS
> 
> 
> Issue:
> With 3.9.6 everything is working fine. Systems boots and I'm getting my DM
> 
> 3.9.7 introduced following changes:
> commit aed4802d2a0d2f6c7179a2c03e184860741788c0
> Author: Ben Skeggs <bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> Date: Mon Jun 3 16:40:14 2013 +1000
> 
> drm/nv50/kms: use dac loadval from vbios, where it's available
> 
> commit d40ee48acde16894fb3b241d7e896d5fa84e0f10 upstream.
> -------
> commit b242745947ed7562ad91dad9e9fde1a92e40d666
> Author: Ben Skeggs <bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> Date: Mon Jun 3 16:07:06 2013 +1000
> 
> drm/nv50/disp: force dac power state during load detect
> 
> commit ea9197cc323839ef3d5280c0453b2c622caa6bc7 upstream.
I would suspect this ^^ commit to be the one causing the issue. Can you please
revert it on top of 3.9.7 and confirm ?
How many monitors does that kernel detect ?

> -------
> 
> Since 3.9.7 (also tested with 3.9.8 and 3.10.3) the X-server won't be
> accessible. If that's the right description. I'm just seeing a black screen
> and I just can switch back to a tty (which takes it time).
> Tried it with a DM and without (plain xinit/startx from tty).
> 
A brief explanation what happens here:
Nouveau detects a phantom/ghost monitor hooked up to DVI-I-2, which on it's own
causes the DISPLAY engine to hang. Leading to the kernel being unable to change
the resolution(modesetting), and X failing to start and VT switch being dead
slow

Cheers
Emil

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3534 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2013-07-27 10:32 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-27  1:35 [Bug 67382] New: [nouveau, nv50] linux 3.9.7-3.10.3: Xorg won't be available bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-67382-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-07-27  2:00   ` [Bug 67382] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-27  2:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-27 10:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2013-07-27 10:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-27 11:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-27 16:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-27 21:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-28 20:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-29 18:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-29 18:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-29 20:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-29 20:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-30 15:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-30 18:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-30 18:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-30 22:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-31 12:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-31 15:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-31 23:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-01 15:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-01 17:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-01 18:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-01 19:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-01 19:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-02 17:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-03  1:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-03 11:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-03 14:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-04  0:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-22  1:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-22  2:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-22  7:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-22 22:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-22 22:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-23 17:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-23 17:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-23 17:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-04 16:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-06  2:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-14 18:41   ` 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-67382-8800-ZPRLoXboTy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox