linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: Coresight ETF trace dump failed in Juno r1 with 4.8-rc8
Date: Mon, 3 Oct 2016 14:14:00 +0100	[thread overview]
Message-ID: <42c2ac9c-abdf-5341-01b5-3f342c5164b7@arm.com> (raw)
In-Reply-To: <CAGhh56F-VWCCy82msQ8CimZ4a0a2h=tqR2qv1KcfeyuQXo=R1w@mail.gmail.com>

Hi Venkatesh,

On 03/10/16 12:36, Venkatesh Vivekanandan wrote:
> Hi All,
>
> I am trying to collect ETF trace from Juno R1 and could see "cpu
> stall" while dumping the trace. Attached is the log of sequence
> followed. Was trying to collect the trace data from hardware and see
> if it is any valid data. Am I missing anything here?.
>

There are few fixes from me and Suzuki queued for v4.9.
Can you check if this issue persists even on linux-next ?

-- 
Regards,
Sudeep

  reply	other threads:[~2016-10-03 13:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-03 11:36 Coresight ETF trace dump failed in Juno r1 with 4.8-rc8 Venkatesh Vivekanandan
2016-10-03 13:14 ` Sudeep Holla [this message]
2016-10-04  5:37   ` Venkatesh Vivekanandan
2016-10-04 10:30     ` Sudeep Holla
2016-10-04 12:14       ` Venkatesh Vivekanandan
2016-10-04 12:51         ` Sudeep Holla
2016-10-04 14:29     ` Suzuki K Poulose
2016-10-05  5:27       ` Venkatesh Vivekanandan
2016-10-05 10:42         ` Sudeep Holla
2016-10-06  5:21           ` Venkatesh Vivekanandan
2016-10-06  9:59             ` Sudeep Holla
2016-10-05 17:17         ` Suzuki K Poulose
2016-10-06  6:01           ` Venkatesh Vivekanandan

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=42c2ac9c-abdf-5341-01b5-3f342c5164b7@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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).