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 101164] [GP107] Failed to create kernel channel, -22
Date: Wed, 24 May 2017 15:31:17 +0000	[thread overview]
Message-ID: <bug-101164-8800-2PqetrIH70@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101164-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #5 from Pacho Ramos <pachoramos1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
OK, I will then try to focus on why xorg server is crashing for me each time I
try to effectively get the reverse prime to work ;) 

Best regards!

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

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

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

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

      parent reply	other threads:[~2017-05-24 15:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24  9:22 [Bug 101164] New: nouveau 0000:01:00.0: DRM: failed to create kernel channel, -22 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-101164-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-05-24  9:22   ` [Bug 101164] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-24 10:26   ` [Bug 101164] [GP107] Failed " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-24 11:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-24 15:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-24 15:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]

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-101164-8800-2PqetrIH70@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.