From: Ulrich Eckhardt <usb@uli-eckhardt.de>
To: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Cc: Ming Lei <ming.lei@canonical.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Bjorn Helgaas <bhelgaas@google.com>,
Sarah Sharp <sarah.a.sharp@linux.intel.com>,
linux-pci@vger.kernel.org, Alan Stern <stern@rowland.harvard.edu>
Subject: Re: Unreliable USB3 with NEC uPD720200 and Delock Cardreader
Date: Thu, 25 Oct 2012 19:43:12 +0200 [thread overview]
Message-ID: <50897A30.1040207@uli-eckhardt.de> (raw)
In-Reply-To: <CACVXFVNnrCLo76rh8-hxTdf3C=kvw3ejY6Jg1==COqFC+UHMBg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]
Am 25.10.2012 03:24, schrieb Ming Lei:
>> Lei, do you have any doc describing how to use those tracepoints?
>
> Hi Bjorn Helgaas,
>
> Firstly, please enable these tracepoints via below
>
> echo 1 > /sys/kernel/debug/tracing/events/rpm/enable
>
> then store the trace event result by below once you make sure your interested
> events are completed:
>
> echo 0 > /sys/kernel/debug/tracing/events/rpm/enable
> cp /sys/kernel/debug/tracing/trace /media/ram/rpm-trace
>
Hi,
I have created a trace according this description. Therefore I have
rebooted my system, enabled the trace and inserted and removed the
SD-card until the controller stops working. During this procedure I
observed that the controller seems to be more stable. I had to insert
and remove the SD-card several times until the controller stopped
working. Normally the controller will fail on the first attempt. Also I
had the impression (not sure about this since I have not measured it)
that the card reader reads the data faster.
I append the gzipped trace and the corresponding dmesg output.
Best Regards
Uli
--
Ulrich Eckhardt http://www.uli-eckhardt.de
Ein Blitzableiter auf dem Kirchturm ist das denkbar stärkste
Misstrauensvotum gegen den lieben Gott. (Karl Krauss)
[-- Attachment #2: trace.txt.gz --]
[-- Type: application/x-gunzip, Size: 6026 bytes --]
[-- Attachment #3: dmesg.txt.gz --]
[-- Type: application/x-gunzip, Size: 16832 bytes --]
next prev parent reply other threads:[~2012-10-25 17:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50841CCC.9030809@uli-eckhardt.de>
2012-10-22 23:40 ` Unreliable USB3 with NEC uPD720200 and Delock Cardreader Sarah Sharp
2012-10-23 13:54 ` Bjorn Helgaas
2012-10-23 17:14 ` Ulrich Eckhardt
2012-10-24 20:18 ` Bjorn Helgaas
2012-10-24 21:10 ` Rafael J. Wysocki
2012-10-24 21:13 ` Bjorn Helgaas
2012-10-24 21:31 ` Rafael J. Wysocki
2012-10-25 1:24 ` Ming Lei
2012-10-25 13:33 ` Bjorn Helgaas
2012-10-25 17:43 ` Ulrich Eckhardt [this message]
2012-10-25 18:19 ` Alan Stern
2012-10-27 13:02 ` Ulrich Eckhardt
2012-10-25 17:15 ` Ulrich Eckhardt
2012-10-25 20:11 ` Rafael J. Wysocki
2012-10-26 16:41 ` Ulrich Eckhardt
2012-10-25 20:09 ` Rafael J. Wysocki
[not found] <20121126191002.GE6504@xanatos>
2012-11-26 21:48 ` Bjørn Mork
2012-11-28 22:54 ` Sarah Sharp
2012-12-06 0:33 ` Sarah Sharp
2012-12-06 0:43 ` Rafael J. Wysocki
2012-12-07 0:28 ` Sarah Sharp
2012-12-07 21:00 ` Rafael J. Wysocki
2012-12-12 2:32 ` Huang Ying
2012-12-12 2:34 ` Andrew Lutomirski
2012-12-12 3:18 ` huang ying
2012-12-13 19:53 ` Sarah Sharp
2012-12-06 7:17 ` Huang Ying
2012-12-06 12:43 ` Rafael J. Wysocki
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=50897A30.1040207@uli-eckhardt.de \
--to=usb@uli-eckhardt.de \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=rjw@sisk.pl \
--cc=sarah.a.sharp@linux.intel.com \
--cc=stern@rowland.harvard.edu \
/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.