From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 98386] [NVE7] bus: MMIO write of FAULT at [ IBUS ], Pointer to {TDMS, flat panel} table invalid
Date: Fri, 08 Feb 2019 01:53:50 +0000 [thread overview]
Message-ID: <bug-98386-8800-C5RPib3JNF@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98386-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 536 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98386
--- Comment #26 from Tolga Cakir <cevelnet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
A followup to comment #22: I'm now running stable kernel 4.20.6 and no longer
experience issues with power management after S3 resume. But I still get
[ 318.816664] nouveau 0000:02:00.0: bus: MMIO write of 00000002 FAULT at
4188ac [ IBUS ]
Looks like they were unrelated. Not aware of any further issues.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1422 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:[~2019-02-08 1:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 16:32 [Bug 98386] New: [NVE7] bus: MMIO write of FAULT at [ IBUS ], Pointer to {TDMS, flat panel) table invalid bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-98386-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-10-22 16:42 ` [Bug 98386] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-22 16:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-22 16:54 ` [Bug 98386] [NVE7] bus: MMIO write of FAULT at [ IBUS ], Pointer to {TDMS, flat panel} " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-22 18:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 17:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 17:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 17:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 17:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 17:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 18:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 20:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 20:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 20:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 20:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 20:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-27 23:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-28 15:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-28 21:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-10 23:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-09 18:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-05-01 19:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-05-01 20:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-11-21 18:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-05 15:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-05 15:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-04 9:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-02-08 1:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2019-07-31 5:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:18 ` 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-98386-8800-C5RPib3JNF@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