On Sun, 2008-08-24 at 16:46 +0200, Andreas Schwab wrote:
> Michael Buesch <[EMAIL PROTECTED]> writes:
> 
> > The following workaround seems to fix the crashes on powerpc.
> > However, this patch is clearly not what we want for other architectures,
> > as they might need -fno-omit-frame-pointer to function properly.
> 
> This has a better chance to be accepted. :-)

Unfortunately, that won't solve the FTRACE problem.

Ben.

> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index 8b5a7d3..f9a2e48 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -394,7 +394,7 @@ config LOCKDEP
>       bool
>       depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT 
> && LOCKDEP_SUPPORT
>       select STACKTRACE
> -     select FRAME_POINTER if !X86 && !MIPS
> +     select FRAME_POINTER if !X86 && !MIPS && !PPC
>       select KALLSYMS
>       select KALLSYMS_ALL
>  
> 
> > Index: linux-2.6/kernel/Makefile
> > ===================================================================
> > --- linux-2.6.orig/kernel/Makefile  2008-08-24 11:50:23.000000000 +0200
> > +++ linux-2.6/kernel/Makefile       2008-08-24 12:15:54.000000000 +0200
> > @@ -92,13 +92,13 @@ obj-$(CONFIG_SMP) += sched_cpupri.o
> >  ifneq ($(CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER),y)
> >  # According to Alan Modra <[EMAIL PROTECTED]>, the -fno-omit-frame-pointer 
> > is
> >  # needed for x86 only.  Why this used to be enabled for all architectures 
> > is beyond
> >  # me.  I suspect most platforms don't need this, but until we know that 
> > for sure
> >  # I turn this off for IA-64 only.  Andreas Schwab says it's also needed on 
> > m68k
> >  # to get a correct value for the wait-channel (WCHAN in ps). --davidm
> > -CFLAGS_sched.o := $(PROFILING) -fno-omit-frame-pointer
> > +CFLAGS_sched.o := $(PROFILING)
> 
> CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER is already enabled on powerpc.
> 
> Andreas.
> 

_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev

Reply via email to