From: Cao Minh Hiep <cm-hiep@jinso.co.jp>
To: linux-sh@vger.kernel.org
Subject: Re: Can't mount QSPI-FLASH to userland on Lager
Date: Wed, 25 Mar 2015 01:14:54 +0000 [thread overview]
Message-ID: <55120C0E.1000703@jinso.co.jp> (raw)
In-Reply-To: <550F6E10.8010907@jinso.co.jp>
Hi Mark-san
Thanks for your comments,
On 2015年03月25日 01:24, Mark Brown wrote:
> On Tue, Mar 24, 2015 at 04:17:32PM +0900, Cao Minh Hiep wrote:
>> On 2015年03月24日 01:27, Mark Brown wrote:
>>> Interesting... nobody else has reported any problems. Can you collect
>>> traces from the failing and successful systems with ftrace (turn on
>>> /sys/kernel/debug/tracing/events/spi/enable to get all the SPI logging)
>>> please?
>> I attached the traces logs file of failing and successful systems:
>> file1: qspi_v4.0-rc2_added_tracer_test_logs_lager.txt
>> file2: qspi_v4.0-rc2_added_tracer_and_reverting_patches_test_logs_lager.txt
>> And also attached the logs file of 10times for testing in before/after
>> reverting patches without tracer.
>> file3: qspi_v4.0-rc2_test_logs_for_10times_lager.txt
>> file4: qspi_v4.0-rc2_after_reverting_patches_test_logs_for_10times_lager.txt
> These all look like console logs, not ftrace logs?
The file3 and file4 are logs of normal 10times test which enabled ext3,
ext4 in configuration.
The file1 and file2 are logs after enabling Kernel Function Tracer and
Trace syscalls
...debug/tracing/events/spi/enable is not showed in default config.
Could you please tell me the correct way to get ftrace logs?
Thank you!
Hiep.
next prev parent reply other threads:[~2015-03-25 1:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 1:36 Can't mount QSPI-FLASH to userland on Lager Cao Minh Hiep
2015-03-23 1:59 ` Geert Uytterhoeven
2015-03-23 10:02 ` Cao Minh Hiep
2015-03-23 16:27 ` Mark Brown
2015-03-24 15:42 ` Geert Uytterhoeven
2015-03-24 16:24 ` Mark Brown
2015-03-24 16:27 ` Mark Brown
2015-03-25 0:55 ` Cao Minh Hiep
2015-03-25 1:14 ` Cao Minh Hiep [this message]
2015-03-25 4:42 ` Mark Brown
2015-03-25 4:54 ` Geert Uytterhoeven
2015-03-25 5:02 ` Mark Brown
2015-03-25 16:32 ` Mark Brown
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=55120C0E.1000703@jinso.co.jp \
--to=cm-hiep@jinso.co.jp \
--cc=linux-sh@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.