From: Ulrich Eckhardt <usb@uli-eckhardt.de>
To: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Cc: Sarah Sharp <sarah.a.sharp@linux.intel.com>,
linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: Unreliable USB3 with NEC uPD720200 and Delock Cardreader
Date: Tue, 23 Oct 2012 19:14:15 +0200 [thread overview]
Message-ID: <5086D067.4000900@uli-eckhardt.de> (raw)
In-Reply-To: <20121022234057.GA20265@xanatos>
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
Am 23.10.2012 01:40, schrieb Sarah Sharp:
> On Sun, Oct 21, 2012 at 06:03:24PM +0200, Ulrich Eckhardt wrote:
>> I have tested it with Kernel 3.6.2. The USB3 port is the one built
>> in the Mainboard M4A87DT EVO.
>
> Did a previous kernel version work?
Yes, I tried the Kernel shipped with OpenSUSE (3.4.11) several 3.5 and
all available 3.6 kernel versions.
>> Here is a dmesg output, when the cardreader stops working during
>> copying data:
>
> Is there anything before that line in the dmesg? Because it seems that
> the whole xHCI host gets unregistered, and it would be good to know why.
I attach the complete dmesg logs and the lspci -vv output as requested
by Bjorn for the situations when the controller does not work after
startup (extension notworking), when the controller is working
(extension OK), and after stopping (extension stop).
Due to the size, I have gziped the log files. I hope this is OK for you.
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: dmesg.notworking.gz --]
[-- Type: application/x-gunzip, Size: 16736 bytes --]
[-- Attachment #3: dmesg.OK.gz --]
[-- Type: application/x-gunzip, Size: 16618 bytes --]
[-- Attachment #4: dmesg.stop.gz --]
[-- Type: application/x-gunzip, Size: 16853 bytes --]
[-- Attachment #5: lspci.notworking.gz --]
[-- Type: application/x-gunzip, Size: 5095 bytes --]
[-- Attachment #6: lspci.OK.gz --]
[-- Type: application/x-gunzip, Size: 5253 bytes --]
[-- Attachment #7: lspci.stop.gz --]
[-- Type: application/x-gunzip, Size: 5255 bytes --]
next prev parent reply other threads:[~2012-10-23 17:22 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 [this message]
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
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=5086D067.4000900@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=sarah.a.sharp@linux.intel.com \
/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.