From: David Daney <ddaney.cavm@gmail.com>
To: "Lluís Batlle i Rossell" <viric@viric.name>,
"Ralf Baechle" <ralf@linux-mips.org>,
"Al Cooper" <alcooperx@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: FTRACE makes the kernel not boot
Date: Mon, 01 Apr 2013 09:48:23 -0700 [thread overview]
Message-ID: <5159BA57.5030504@gmail.com> (raw)
In-Reply-To: <20130330232944.GR10445@vicerveza.homeunix.net>
On 03/30/2013 04:29 PM, Lluís Batlle i Rossell wrote:
> Hello,
>
> For a fuloong (loongson2f) I had two configs, one booted and the other not, on
> a linux 3.8. I narrowed down the difference to enabling CONFIG_FTRACE.
>
> Enabling CONFIG_FTRACE makes the kernel not load at all; it even does not print
> any early printk to the serial port.
>
> Do you agree there is a problem with FTRACE? Maybe it is solved already
> in the mips git branch?
>
This is caused by 58b69401c797e (MIPS: Function tracer: Fix broken
function tracing), which broke ftrace for 64-bit kernels. The subject
of the patch is a bit misleading in this respect, it probably should
have been something like 'MIPS: Function tracer: Break function tracing
that used to work'
David Daney
> Regards,
> Lluís.
>
>
>
prev parent reply other threads:[~2013-04-01 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-30 23:29 FTRACE makes the kernel not boot Lluís Batlle i Rossell
2013-04-01 16:48 ` David Daney [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5159BA57.5030504@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=alcooperx@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=viric@viric.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox