Re: broken suspend [Was: 2.6.24-rc2-mm1]

Rafael J. Wysocki
2007-11-18T22:10:50Z

On Sunday, 18 of November 2007, Jiri Slaby wrote:
> On 11/18/2007 06:07 PM, Alan Stern wrote:
> > You'll get more useful results if you redo your changes to
> > notifier_call_chain(). Have it print out the address of the routine
> > _before_ making the call, and don't limit it to 20. That way you'll
> > know exactly which notifier routine ends up hanging.
>
> The problem is, that notifier_call_chain is called again and again zillion times
> by somebody else...

You can use a global variable to switch the logging only before the CPU
hotunplug done by the suspend code. You just need to hack
disable_nonboot_cpus() for that.