From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 3661CDDDDC for ; Mon, 25 Aug 2008 08:39:58 +1000 (EST) Subject: Re: Random crashes with 2.6.27-rc3 on PPC From: Benjamin Herrenschmidt To: Andreas Schwab In-Reply-To: References: <200808231610.46473.mb@bu3sch.de> <1219531969.21386.205.camel@pasglop> <200808241544.12412.mb@bu3sch.de> Content-Type: text/plain Date: Mon, 25 Aug 2008 08:39:46 +1000 Message-Id: <1219617586.21386.228.camel@pasglop> Mime-Version: 1.0 Cc: linuxppc-dev@ozlabs.org, Linus Torvalds , linux-kernel Reply-To: benh@kernel.crashing.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sun, 2008-08-24 at 16:46 +0200, Andreas Schwab wrote: > Michael Buesch 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 , 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. >