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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
