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 110572] Regularly System Crash: (ca. 1 hour) nouveau 0000:08:00.0: gr: PGRAPH TLB flush idle timeout fail and nouveau 0000:08:00.0: mmu: ce0 mmu invalidate timeout
Date: Thu, 16 May 2019 17:01:36 +0000	[thread overview]
Message-ID: <bug-110572-8800-DnngSY4paX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110572-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #14 from Linux Freak <Linuxfreak-RbZlAiThDcE@public.gmane.org> ---
Created attachment 144284
  --> https://bugs.freedesktop.org/attachment.cgi?id=144284&action=edit
crash   nouveau 0000:08:00.0: timeout

crash    nouveau 0000:08:00.0: timeout

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

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

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

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

  parent reply	other threads:[~2019-05-16 17:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01  7:52 [Bug 110572] New: System Crash: nouveau 0000:08:00.0: gr: PGRAPH TLB flush idle timeout fail and nouveau 0000:08:00.0: mmu: ce0 mmu invalidate timeout bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-110572-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2019-05-08 22:12   ` [Bug 110572] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-08 22:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-08 22:17   ` [Bug 110572] Regularly System Crash: (ca. 1 hour) " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-09  8:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-09 12:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-11 18:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-11 18:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-11 18:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-11 19:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-11 19:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-14 14:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-14 14:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-14 14:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-14 16:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-14 16:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-15  8:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-16 17:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2019-05-19 12:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-24  8:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-05  8:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-05  8:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-05  8:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-11-10 20:54   ` 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-110572-8800-DnngSY4paX@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