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 105319] DRM: EVO timeout with kernel 4.15.x
Date: Fri, 02 Mar 2018 00:02:35 +0000	[thread overview]
Message-ID: <bug-105319-8800-I7gYBMIlcN@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105319-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #6 from Sérgio M. Basto <sergio-iCFKjj3otdHQT0dZR+AlfA@public.gmane.org> ---
 I tried just over and boot with kernel 4.16-rc3 [1], which also don't boot

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

[-- Attachment #1.2: Type: text/html, Size: 1029 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:[~2018-03-02  0:02 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01 23:05 [Bug 105319] New: DRM: EVO timeout with kernel 4.15.x bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-105319-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2018-03-01 23:05   ` [Bug 105319] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-01 23:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-01 23:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-01 23:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-02  0:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-02  0:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2018-03-02  1:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-02 17:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-17 15:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-22 17:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-22 17:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-22 17:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-22 21:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-24  1:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-24  1:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-26 11:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-27 18:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-27 19:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-04-03 13:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-01 18:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-01 18:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-17 10:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-17 12:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-20 12:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-20 17:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-08-18  0:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-08-18  1:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-08-19 22:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-08-20 13:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-08-21 16:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-08-21 17:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-08-29  0:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-08-29  0:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-04 13:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-13  7:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-13  7:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-31  2:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-03-18 21:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:36   ` 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-105319-8800-I7gYBMIlcN@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.