From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 204227] Visual artefacts and crash from suspend on amdgpu
Date: Wed, 28 Aug 2019 01:48:51 +0000 [thread overview]
Message-ID: <bug-204227-2300-gpU8JoR6KD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204227-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204227
--- Comment #9 from tones111@hotmail.com ---
(In reply to tones111 from comment #8)
> I applied this to 5.2.10 and I'm still seeing artifacts.
Sorry, I realized that statement doesn't give much context to work with. My
system has an R5 2500U. lspci shows the following:
05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven
Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c4) (prog-if 00
[VGA controller])
Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile
Series]
Flags: bus master, fast devsel, latency 0, IRQ 51
Memory at b0000000 (64-bit, prefetchable) [size=256M]
Memory at c0000000 (64-bit, prefetchable) [size=2M]
I/O ports at 1000 [size=256]
Memory at c0600000 (32-bit, non-prefetchable) [size=512K]
Capabilities: [48] Vendor Specific Information: Len=08 <?>
Capabilities: [50] Power Management version 3
Capabilities: [64] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/4 Maskable- 64bit+
Capabilities: [c0] MSI-X: Enable- Count=3 Masked-
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010
<?>
Capabilities: [200] Resizable BAR <?>
Capabilities: [270] Secondary PCI Express <?>
Capabilities: [2b0] Address Translation Service (ATS)
Capabilities: [2c0] Page Request Interface (PRI)
Capabilities: [2d0] Process Address Space ID (PASID)
Capabilities: [320] Latency Tolerance Reporting
Kernel driver in use: amdgpu
Kernel modules: amdgpu
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-08-28 1:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 22:49 [Bug 204227] New: Visual artefacts and crash from suspend on amdgpu bugzilla-daemon
2019-07-18 22:50 ` [Bug 204227] " bugzilla-daemon
2019-07-19 19:16 ` bugzilla-daemon
2019-07-20 15:27 ` bugzilla-daemon
2019-08-26 23:42 ` bugzilla-daemon
2019-08-27 13:12 ` bugzilla-daemon
2019-08-27 18:07 ` bugzilla-daemon
2019-08-27 18:31 ` bugzilla-daemon
2019-08-28 0:47 ` bugzilla-daemon
2019-08-28 1:48 ` bugzilla-daemon [this message]
2019-09-09 8:29 ` bugzilla-daemon
2019-09-09 11:07 ` bugzilla-daemon
2019-09-09 11:14 ` bugzilla-daemon
2019-09-19 21:09 ` bugzilla-daemon
2019-09-19 21:11 ` bugzilla-daemon
2019-09-23 7:36 ` bugzilla-daemon
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-204227-2300-gpU8JoR6KD@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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.