From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102507] WARNING: CPU: 1 PID: 336 at drivers/gpu/drm/drm_mode_object.c:237 drm_object_property_set_value+0x5d/0x70 [drm]
Date: Sat, 04 Nov 2017 15:48:28 +0000 [thread overview]
Message-ID: <bug-102507-502-QPebmVUJBT@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102507-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 554 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102507
--- Comment #6 from dwagner <jb5sgc1n.nya@20mm.eu> ---
The recent patches to amdgpu made those annoying kernel warning messages go
away for me, too. Along with them went some initialization and self-test
messages, such as e.g.
> [drm] GPU post is not needed
> [drm] amdgpu: irq initialized.
> amdgpu: [powerplay] amdgpu: powerplay sw initialized
... which probably (hopefully) were not really relevant, either.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1494 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-11-04 15:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 7:55 [Bug 102507] WARNING: CPU: 1 PID: 336 at drivers/gpu/drm/drm_mode_object.c:237 drm_object_property_set_value+0x5d/0x70 [drm] bugzilla-daemon
2017-09-01 8:01 ` bugzilla-daemon
2017-09-01 15:23 ` bugzilla-daemon
2017-09-01 15:32 ` bugzilla-daemon
2017-09-01 15:43 ` bugzilla-daemon
2017-09-01 15:47 ` bugzilla-daemon
2017-11-03 22:24 ` bugzilla-daemon
2017-11-04 15:48 ` bugzilla-daemon [this message]
2017-11-04 21:33 ` bugzilla-daemon
2017-11-04 23:48 ` 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-102507-502-QPebmVUJBT@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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).