From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 111463] New: [NV49] MMIO write FAULT at 00c200
Date: Thu, 22 Aug 2019 09:29:35 +0000 [thread overview]
Message-ID: <bug-111463-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1583 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111463
Bug ID: 111463
Summary: [NV49] MMIO write FAULT at 00c200
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: not set
Priority: not set
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: morpheus2051-S0/GAf8tV78@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 145128
--> https://bugs.freedesktop.org/attachment.cgi?id=145128&action=edit
dmesg with write fault
Hello,
on my HP NW9440 Laptop with the following GPU:
01:00.0 VGA compatible controller: NVIDIA Corporation G71GLM [Quadro FX 1500M]
(rev a1)
I am getting MMIO write faults always at the same address. I think these write
faults lock up my machine sometimes. I use plasma desktop environment. To
trigger the MMIO write faults I have to just use the machine. I have not found
a pattern to provoke a hard lockup.
Known good kernel version: none
Known bad kernel versions: 4.19, 5.0, 5.1, 5.2
Relevant software versions:
media-libs/mesa 19.0.8
sys-kernel/gentoo-sources 5.2.9
x11-base/xorg-server 1.20.5
x11-libs/libdrm 2.4.97
x11-drivers/xf86-video-nouveau 1.0.16
kde-plasma 5.15.5
kde-frameworks 5.60.0
qt 5.12.3
Distribution is gentoo.
Greetings
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2999 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2019-08-22 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 9:29 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-111463-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2019-08-22 9:30 ` [Bug 111463] [NV49] MMIO write FAULT at 00c200 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-22 9:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-22 9:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-22 9:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:51 ` 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-111463-8800@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.