<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - [gm45] hotplug storm after S3 resume (udev spins on drm device after wakeup)" href="https://bugs.freedesktop.org/show_bug.cgi?id=27941#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - [gm45] hotplug storm after S3 resume (udev spins on drm device after wakeup)" href="https://bugs.freedesktop.org/show_bug.cgi?id=27941">bug 27941</a> from <a class="email" href="mailto:jani.nikula@intel.com" title="Jani Nikula <jani.nikula@intel.com>"> Jani Nikula</a> <pre>(In reply to <a href="show_bug.cgi?id=27941#c11">comment #11</a>) > Trying newer kernels is generally good advice for the restless, but I also > want to point your attention to existing data in this same bug: > > | Since 3.2.12 is newer than 2.6.35, it sounds like the fix from <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - udev takes almost 100% CPU on resume from suspend (and Xorg is blamed)" href="show_bug.cgi?id=25259">bug 25259</a> > | doesn't take care of these symptoms. Thanks, I missed that somehow. Even so, the kernel is a fast moving target, and IMHO trying, say, current upstream master is much more productive than trying to go through all the changes since 3.2 in our irq/hotplug/suspend code that might have affected this bug. Also, if the problem still persists, I think debugging on current kernels that we work on is more likely to lead to correct conclusions anyway.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>