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 81363] New: Black screen after UDEV is intialized
Date: Mon, 14 Jul 2014 22:42:38 +0000	[thread overview]
Message-ID: <bug-81363-8800@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 81363
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: Black screen after UDEV is intialized
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
          Severity: major
    Classification: Unclassified
                OS: Linux (All)
          Reporter: jrsx13-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: 7.7 (2011)
         Component: Driver/nouveau
           Product: xorg

Created attachment 102804
  --> https://bugs.freedesktop.org/attachment.cgi?id=102804&action=edit
Dmesg output

When I boot my computer with nouveau and KMS, I get a black screen after UDEV
starts on Debian Testing. I've attached some logs.

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

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

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

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

             reply	other threads:[~2014-07-14 22:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 22:42 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-81363-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-07-14 22:43   ` [Bug 81363] Black screen after UDEV is intialized bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-14 22:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-14 22:51   ` [Bug 81363] [NV84] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-15  0:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-15 23:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-15 23:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-15 23:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-15 23:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-16  0:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-02  2:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-12-19  0:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-12-19 18:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-12-20  3:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:47   ` 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-81363-8800@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