From: Holger Brunck <holger.brunck@keymile.com>
To: Christophe Leroy <christophe.leroy@c-s.fr>,
Dave Hansen <dave.hansen@linux.intel.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: debug problems on ppc 83xx target due to changed struct task_struct
Date: Fri, 19 Aug 2016 18:26:57 +0200 [thread overview]
Message-ID: <36769735-4935-a7b3-d3bb-15ad53604d28@keymile.com> (raw)
In-Reply-To: <64742682-140b-6daa-6d38-6107f2d7ecf3@c-s.fr>
On 19/08/16 15:44, Christophe Leroy wrote:
>>>
>>> I just tried it on an 885 and on an 8323, it work properly on both targets.
>>>
>>> You can see below the Debug Option that are active on my 8323 target.
>>>
>>
>>
>> thanks for trying it.
>>
>> Could you completely disable FTRACE? As it also works on my side when I have
>> FTRACE enabled.
>>
>>
> I have now disabled completly FTRACE, the behaviour is still OK.
>
I double-checked it on my 8321 board and on this board it's also not
reproducible with my test program. Also on a board with QorIQ P2041 it's not
reproducible so easy, but we see the error with our application code. Easy
reproducible with the mainline kernel for me it's only on my MPC8360 board.
Best regards
Holger
next prev parent reply other threads:[~2016-08-19 16:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 14:50 debug problems on ppc 83xx target due to changed struct task_struct Holger Brunck
2016-08-12 15:14 ` Dave Hansen
2016-08-12 15:47 ` Holger Brunck
2016-08-12 16:09 ` Dave Hansen
2016-08-15 14:35 ` Holger Brunck
2016-08-15 16:19 ` Dave Hansen
2016-08-16 17:27 ` christophe leroy
2016-08-16 17:36 ` Dave Hansen
2016-08-17 8:22 ` Christophe Leroy
2016-08-17 15:27 ` Holger Brunck
2016-08-18 8:23 ` Christophe Leroy
2016-08-19 11:03 ` Christophe Leroy
2016-08-19 11:14 ` Holger Brunck
2016-08-19 13:44 ` Christophe Leroy
2016-08-19 16:26 ` Holger Brunck [this message]
2016-08-16 22:13 ` Benjamin Herrenschmidt
2016-08-17 15:05 ` Holger Brunck
2016-08-17 14:59 ` Holger Brunck
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=36769735-4935-a7b3-d3bb-15ad53604d28@keymile.com \
--to=holger.brunck@keymile.com \
--cc=christophe.leroy@c-s.fr \
--cc=dave.hansen@linux.intel.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).