[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.0910061201210.2646@localhost.localdomain>
Date: Tue, 6 Oct 2009 12:04:54 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: "Mehlan, Markus" <Markus.Mehlan@...ter.info>
cc: linux-kernel@...r.kernel.org
Subject: Re: AW: AW: clock_nanosleep: cyclic POSIX thread freezes during time
setting
On Tue, 6 Oct 2009, Mehlan, Markus wrote:
> #
> # Kernel hacking
> #
> # CONFIG_PRINTK_TIME is not set
> CONFIG_ENABLE_WARN_DEPRECATED=y
> CONFIG_ENABLE_MUST_CHECK=y
> CONFIG_FRAME_WARN=1024
> CONFIG_MAGIC_SYSRQ=y
> # CONFIG_UNUSED_SYMBOLS is not set
> CONFIG_DEBUG_FS=y
> # CONFIG_HEADERS_CHECK is not set
> # CONFIG_DEBUG_KERNEL is not set
> CONFIG_RTMUTEX_CHECK=y
> # CONFIG_DEBUG_BUGVERBOSE is not set
> CONFIG_HAVE_FTRACE=y
> CONFIG_HAVE_DYNAMIC_FTRACE=y
> # CONFIG_EVENT_TRACER is not set
> # CONFIG_WAKEUP_LATENCY_HIST is not set
> # CONFIG_SAMPLES is not set
> # CONFIG_IRQSTACKS is not set
> # CONFIG_VIRQ_DEBUG is not set
> # CONFIG_BOOTX_TEXT is not set
> # CONFIG_PPC_EARLY_DEBUG is not set
CONFIG_FTRACE=y is missing.
I don't remember whether the older -rt kernels had ftrace support for
powerpc.
Can you verify whether later -rt versions (29-rt or 31-rt) have the
same problem ?
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists