All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 39498] nouveau hangs on unresponsive black screen at startup
Date: Mon, 25 Jul 2011 10:59:16 -0700 (PDT)	[thread overview]
Message-ID: <20110725175916.79C061300CB@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-39498-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>

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

--- Comment #20 from Guido Trentalancia <guido-D1bseh+SzQikhjTqA1DzBQ@public.gmane.org> 2011-07-25 10:59:15 PDT ---
Emil, unfortunately (and as I was expecting) the "video" option in the kernel
boot parameters did not sort out anything other than changing the resolution of
the initial framebuffer console. The last option that you proposed was to
disseminate printk() in the kernel module and try to trace the code path and
try to understand where it gets stuck. That's not easy to do without any
indication at all, because the it's several drivers (drm, drm_kms_helper,
nouveau, ttm). Also there is no crash as in kernel oops or userspace segfault
and I have already debug output from drm. I bet the problem lies there (drm or
drm_kms_helper), but I really do not know where to begin without the assistance
of one of the developers.

Felix, I am glad to hear that you managed to sort out your issues. I am quite
sure mine are not exactly related to yours and I am not using openSUSE,
therefore trying the same packages has a very low priority for me now. I would
really need to hear back from the developers...

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2011-07-25 17:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-23 22:37 [Bug 39498] New: nouveau hangs on unresponsive black screen at startup bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-39498-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-07-23 22:37   ` [Bug 39498] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-23 22:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-23 22:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-23 22:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-23 22:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-24 12:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-24 12:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-24 17:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-24 17:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-24 19:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-24 19:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-24 19:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-24 20:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-24 22:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-24 22:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-24 23:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-24 23:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-24 23:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-25 13:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-25 17:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-25 17:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2011-07-25 18:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-26  5:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-26  6:03   ` 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=20110725175916.79C061300CB@annarchy.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.