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: Wed, 11 Nov 2015 10:32:23 +0000 [thread overview]
Message-ID: <bug-106851-2300-Z5zY49VLig@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-106851-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=106851
--- Comment #9 from Holger Hoffstätte <holger.hoffstaette@googlemail.com> ---
(In reply to Holger Hoffstätte from comment #4)
> Created attachment 191741 [details]
> Unconditionally set sysfs_initialized
>
> This patch removes the conditional around setting sysfs_initialized and
> works for me - no more spew on resume. Also fixes a previously duplicate
> message text.
So it turns out that *in my case* - even with the original patch - these
messages apparently (?) were caused because my monitor was dying
(it's completely dead now) and reacting too slowly, i.e. not waking up
properly.
I got a new one and now the original patch - which is in 4.1.13 - does
indeed work fine: no more errors on resume.
--
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
prev parent reply other threads:[~2015-11-11 10:32 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
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 [this message]
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-Z5zY49VLig@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.