[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*

[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]

https://bugzilla.kernel.org/show_bug.cgi?id=106851

Aaron Lu <aaron.lu@intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aaron.lu@intel.com
          Component|Other                       |Video(DRI - non Intel)
           Assignee|rjw@rjwysocki.net           |drivers_video-dri@kernel-bu
                   |                            |gs.osdl.org
            Product|Power Management            |Drivers

--- Comment #1 from Aaron Lu <aaron.lu@intel.com> ---
Looks like a radeon issue, move there.

-- 
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

[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]

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

[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]

https://bugzilla.kernel.org/show_bug.cgi?id=106851

--- Comment #3 from Holger Hoffstätte <holger.hoffstaette@googlemail.com> ---
(In reply to Holger Hoffstätte from comment #2)
> For some reason I get the "power method" failure message 4 times on each resume.

This was wrong, sorry. I get each sysfs failure once (4 in total).

-- 
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

[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]

https://bugzilla.kernel.org/show_bug.cgi?id=106851

--- Comment #4 from Holger Hoffstätte <holger.hoffstaette@googlemail.com> ---
Created attachment 191741
  --> https://bugzilla.kernel.org/attachment.cgi?id=191741&action=edit
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.

-- 
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

[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]

https://bugzilla.kernel.org/show_bug.cgi?id=106851

--- Comment #5 from lbl <lblmr@yopmail.com> ---
Update: it also happens on kernel 4.2.5

-- 
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

[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]

https://bugzilla.kernel.org/show_bug.cgi?id=106851

lbl <lblmr@yopmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Kernel Version|4.1.12-LTS                  |4.1.12, 4.2.5

-- 
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

[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]

https://bugzilla.kernel.org/show_bug.cgi?id=106851

Hin-Tak Leung <htl10@users.sourceforge.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |htl10@users.sourceforge.net

--- Comment #6 from Hin-Tak Leung <htl10@users.sourceforge.net> ---
me too with 4.2.5 .

-- 
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

[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]

https://bugzilla.kernel.org/show_bug.cgi?id=106851

--- Comment #7 from lbl <lblmr@yopmail.com> ---
It doesn't seem to happen with kernel 4.3

-- 
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

[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]

https://bugzilla.kernel.org/show_bug.cgi?id=106851

lbl <lblmr@yopmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |PATCH_ALREADY_AVAILABLE

--- Comment #8 from lbl <lblmr@yopmail.com> ---
Fixed in kernel 4.1.13. Thanks

-- 
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

[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]

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