From: Jonathan <jonathan.625266@earthlink.net>
To: linux-scsi@vger.kernel.org
Cc: Hans de Goede <hdegoede@redhat.com>
Subject: Re: uas - kernel panic on drive connection
Date: Wed, 9 Jul 2014 19:31:39 -0400 [thread overview]
Message-ID: <20140709193139.32049945@earthlink.net> (raw)
In-Reply-To: <53BCEA03.30304@redhat.com>
Hans,
Thanks for getting back to me. It looks like the USB 3.0 controller is an Etron.
Here is the output from lspci:
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5)
00:1c.4 PCI bridge: Intel Corporation 82801 PCI Bridge (rev b5)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation Z68 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
02:00.0 USB controller: Etron Technology, Inc. EJ168 USB 3.0 Host Controller (rev 01)
03:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 01)
04:00.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394 Controller (Link)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
Best,
Jonathan
On Wed, 09 Jul 2014 09:06:43 +0200
Hans de Goede <hdegoede@redhat.com> wrote:
>
> This looks like something is going wrong in the XHCI code, likely something
> related to bulk-streams.
>
> I've a dock with an ASMedia ASM1053E chipset myself and that one works fine with both
> Nec and Intel XHCI controllers. What type of XHCI controller do you have ?
>
> Can you please do "lspci" on the machine in question and include the output in your
> next mail ?
>
> Regards,
>
> Hans
next prev parent reply other threads:[~2014-07-09 23:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 14:40 uas - kernel panic on drive connection Jonathan
2014-07-08 23:58 ` Jonathan
2014-07-09 7:06 ` Hans de Goede
2014-07-09 23:31 ` Jonathan [this message]
2014-07-11 9:36 ` Hans de Goede
2014-07-12 0:40 ` Jonathan
2014-07-12 10:16 ` Hans de Goede
-- strict thread matches above, loose matches on Subject: below --
2014-07-04 14:46 Jonathan
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=20140709193139.32049945@earthlink.net \
--to=jonathan.625266@earthlink.net \
--cc=hdegoede@redhat.com \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox