From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 99900] [NVC1] nouveau: freeze / crash after kernel update to 4.10
Date: Mon, 27 Feb 2017 21:14:28 +0000 [thread overview]
Message-ID: <bug-99900-8800-rF2GHd9nAT@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99900-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 916 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99900
Joshua Baergen <joshuabaergen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |joshuabaergen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
--- Comment #2 from Joshua Baergen <joshuabaergen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
I've also had nouveau issues after upgrading to 4.10(.1), but in my case syslog
is spammed with:
Feb 27 14:02:31 baergj kernel: nouveau 0000:01:00.0: fifo: PBDMA0: 04000000
[ACQUIRE] ch 2 [007f9bb000 X[2107]] subc 0 mthd 0000 data 00000000
This appears to happen after screen blank at some point. Like Torsten, I don't
have a problem with the 4.9 series.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2190 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2017-02-27 21:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-99900-8800@http.bugs.freedesktop.org/>
[not found] ` <bug-99900-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-02-22 13:56 ` [Bug 99900] nouveau: freeze / crash after kernel update to 4.10 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-22 13:58 ` [Bug 99900] [NVC1] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-27 21:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2017-02-27 21:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-28 7:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-28 8:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-28 8:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-28 9:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-03 9:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-04 7:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-04 7:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-06 7:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-14 12:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-10 23:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-11 18:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-26 16:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-26 16:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-26 16:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-19 21:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-19 22:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-19 23:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-20 22:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-20 22:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-21 0:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-21 4:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-05 21:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-05 21:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-08 11:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-08 11:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-08 11:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-23 23:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:24 ` 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-99900-8800-rF2GHd9nAT@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.