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 100228] [NV137] bus: MMIO read of 00000000 FAULT at 409800 [ TIMEOUT ]
Date: Tue, 04 Sep 2018 17:21:45 +0000	[thread overview]
Message-ID: <bug-100228-8800-CP25dIxNdV@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100228-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #22 from Rhys Kidd <rhyskidd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
So there's updated low-level firmware shipped by NVIDIA for the GP107 (and
other pre-GP108 Pascal GPUs) [0]. This might resolve or improve the situation
for mobile GP107 users.

   nvidia: switch GP10[2467] to newer scrubber/ACR firmware (from GP108)

   This is being done to resolve issues being seen on a number of newer
   laptop systems which aren't compatible with the older binaries.

Users will likely need to wait for their distribution to ship the updated
firmware through the usual package update process, or get the firmware directly
from upstream linux-firmware.git.

[0]
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=85c5d90fc155d78531efa5d2b02e92aaef7e4b88

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

[-- Attachment #1.2: Type: text/html, Size: 1866 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-09-04 17:21 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-16 11:38 [Bug 100228] New: [NV137] unknown chipset (137000a1) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-100228-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-03-16 17:12   ` [Bug 100228] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-05  4:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-21  3:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-21  3:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-22 15:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-23 21:21   ` [Bug 100228] [NV137] bus: MMIO read of 00000000 FAULT at 409800 [ TIMEOUT ] bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-24 14:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-24 14:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-24 21:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-20 14:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-20 14:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-31  7:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-31  7:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-08 20:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-13  7:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-13 10:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-13 13:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-17 15:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-31 22:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-29  0:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-29  0:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-29  1:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-14 14:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-17  4:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-03 13:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-04  5:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-09-03 20:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-09-04 17:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2018-09-05  4:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-09-05  5:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-09-05  5:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-09-11 14:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-10-04 12:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-10-06  7:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-10-15 10:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-10-15 10:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-11-12 15:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-11-21 12:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-07  3:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-07  3:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-27 20:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-27 20:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-27 20:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-01 14:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-31  9:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-02 20:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-12 18:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-12 18:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-12 18:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-11-02 15:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-11-16 14:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:25   ` 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-100228-8800-CP25dIxNdV@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.