From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 100423] MMIO read of 00000000 FAULT at 022554 [ IBUS ]
Date: Mon, 29 Jan 2018 12:30:27 +0000 [thread overview]
Message-ID: <bug-100423-8800-VwxPkbpAHT@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100423-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 533 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100423
--- Comment #9 from Rhys Kidd <rhyskidd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
(In reply to Bruno Pagani from comment #8)
>
> Should I open a new issue for this one?
Yes please, where there appears a new register on differing hardware family.
It's an easy operation to merge bugs later on should they be due to the same
underlying cause, but almost impossible to separate them out.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1350 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:[~2018-01-29 12:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 20:42 [Bug 100423] New: MMIO read of 00000000 FAULT at 022554 [ IBUS ] bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-100423-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-04-07 13:37 ` [Bug 100423] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-13 13:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-02 13:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-12 17:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-10 2:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-19 19:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-19 22:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-28 21:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-29 12:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2018-01-29 13:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-05 9:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-05 15:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-05 15:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-05 15:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-05 16:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-25 21:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-23 8:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-23 13:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-10-29 7:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-10-29 12:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-05 15:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-05 15:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-05 15:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-07 11:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-08 16:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-29 18:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-01 13:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-01 22:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-04-29 14:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-08 8:46 ` 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-100423-8800-VwxPkbpAHT@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