From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205497] Attempt to read amd gpu id causes a freeze
Date: Sat, 16 Nov 2019 06:30:13 +0000 [thread overview]
Message-ID: <bug-205497-2300-OICFSbAGpM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205497-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205497
--- Comment #14 from Trek (trek00@inbox.ru) ---
(In reply to Alex Deucher from comment #11)
> If you access the BAR directly you will likely have problems in certain
> power saving modes.
thank you, I'll add a warning message when accessing BAR directly
--
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-11-16 6:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 5:20 [Bug 205497] New: Attempt to read amd gpu id causes a freeze bugzilla-daemon
2019-11-12 8:29 ` [Bug 205497] " bugzilla-daemon
2019-11-12 11:58 ` bugzilla-daemon
2019-11-12 14:54 ` bugzilla-daemon
2019-11-12 15:12 ` bugzilla-daemon
2019-11-12 16:52 ` bugzilla-daemon
2019-11-14 16:41 ` bugzilla-daemon
2019-11-15 8:45 ` bugzilla-daemon
2019-11-15 8:58 ` bugzilla-daemon
2019-11-15 9:07 ` bugzilla-daemon
2019-11-15 9:15 ` bugzilla-daemon
2019-11-15 15:43 ` bugzilla-daemon
2019-11-15 16:35 ` bugzilla-daemon
2019-11-16 3:32 ` bugzilla-daemon
2019-11-16 6:30 ` bugzilla-daemon [this message]
2019-11-16 18:52 ` bugzilla-daemon
2019-11-16 18:53 ` bugzilla-daemon
2019-11-16 19:01 ` bugzilla-daemon
2019-11-16 20:06 ` bugzilla-daemon
2019-11-18 15:13 ` bugzilla-daemon
2019-11-30 1:12 ` bugzilla-daemon
2020-01-25 14:42 ` bugzilla-daemon
2020-04-12 17:24 ` bugzilla-daemon
2020-04-12 19:33 ` bugzilla-daemon
2020-06-15 13:01 ` 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-205497-2300-OICFSbAGpM@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).