From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 70388] [NV34] failed to idle channel 0xcccc0000
Date: Sat, 14 Jun 2014 15:10:58 +0000 [thread overview]
Message-ID: <bug-70388-8800-YCkxs2Hfth@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-70388-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 455 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=70388
--- Comment #18 from Rostislav Krasny <rosti.bsd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Any progress? More than six months have passed since the last message in this
bug report. In that time NVidia has published some of their specifications. Did
it help you to understand how NV34 works and how to fix this critical bug?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1185 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2014-06-14 15:10 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 19:17 [Bug 70388] New: [NV34] failed to idle channel 0xcccc0000 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-70388-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-10-11 19:20 ` [Bug 70388] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-11 19:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-12 16:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-12 16:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-12 16:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-12 17:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-13 1:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-13 20:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-15 23:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-18 18:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-18 18:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-18 19:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-18 19:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-18 19:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-23 17:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-09 20:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-04 21:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-04 21:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-14 15:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-09-02 19:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-02 19:48 ` [Bug 70388] [NV34] failed to idle channel 0xcccc0000 (also NV44A) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-02 19:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-02 20:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-02 20:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-02 20:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-03 4:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-03 4:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-03 4:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-03 4:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-03 4:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-05 16:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-12 13:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-12 15:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-15 7:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-31 20:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-31 22:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-11 1:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-18 20:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-26 11:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:38 ` 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-70388-8800-YCkxs2Hfth@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.