From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106851] WARNING: CPU: 0 PID: 686 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x68/0x80() + drm:radeon_pm_late_init [radeon]] *ERROR*
Date: Fri, 30 Oct 2015 16:52:56 +0000 [thread overview]
Message-ID: <bug-106851-2300-Yo6iezusLN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-106851-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=106851
Holger Hoffstätte <holger.hoffstaette@googlemail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |holger.hoffstaette@googlema
| |il.com
--- Comment #2 from Holger Hoffstätte <holger.hoffstaette@googlemail.com> ---
This (and similar) messages were supposed to be fixed by commit:
http://cgit.freedesktop.org/~airlied/linux/commit/?h=drm-fixes&id=49abb26651167c892393cd9f2ad23df429645ed9
(should be in the next -stable), but merging that into my 4.1.12+ kernel hasn't
fixed anything.
After reading the patch it seems that the sysfs_initialized flag is only ever
set to true when the last sysfs entry was successfully created; in my case that
particular setting (dev_attr_power_method) seems to fail, so the "all is done"
flag is never set. For some reason I get the "power method" failure message 4
times on each resume.
ISTM that setting the sysfs_initialized flag should be independent of previous
failures; do it once and then stop.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-10-30 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-106851-2300@https.bugzilla.kernel.org/>
2015-10-30 1:48 ` [Bug 106851] WARNING: CPU: 0 PID: 686 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x68/0x80() + drm:radeon_pm_late_init [radeon]] *ERROR* bugzilla-daemon
2015-10-30 16:52 ` bugzilla-daemon [this message]
2015-10-31 9:34 ` bugzilla-daemon
2015-10-31 14:25 ` bugzilla-daemon
2015-11-01 10:47 ` bugzilla-daemon
2015-11-01 10:47 ` bugzilla-daemon
2015-11-02 22:49 ` bugzilla-daemon
2015-11-07 6:13 ` bugzilla-daemon
2015-11-10 6:49 ` bugzilla-daemon
2015-11-11 10:32 ` 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-106851-2300-Yo6iezusLN@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).