mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Jack Coulter <jscinoz@jscinoz.so>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	Andreas Noever <andreas.noever@gmail.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-acpi@vger.kernel.org,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Martin Andersson <martin.andersson@purplescout.se>
Subject: Re: Thunderbolt 3 (Skylake / Alpine Ridge) hotplug
Date: Wed, 16 Mar 2016 14:22:28 +0100	[thread overview]
Message-ID: <20160316132228.GB28222@wunner.de> (raw)
In-Reply-To: <20160315172909.GF19974@localhost>

Hi Jack,

On Tue, Mar 15, 2016 at 12:29:09PM -0500, Bjorn Helgaas wrote:
> On Fri, Feb 26, 2016 at 07:10:03PM +1100, Jack Coulter wrote:
> > I'm attempting to use the Thunderbolt 3 (which has a USB Type-C
> > connector) port on my laptop, a Dell XPS 15 (9550). The external device
> > I'm attempting to use is a gigabit ethernet + USB 3.0 hub, of an unknown
> > / generic brand, but bears model number KY-688 if that's of any use.
> > 
> > When the device is present at system startup, everything works
> > correctly, and shows up in lspci as a USB controller, which lsusb shows
> > having a hub and ethernet NIC attached, which the r8152 driver binds and
> > uses without issue: [...]
> > 
> > However, if the device is connected after the system boots (or
> > disconnected and reconnected), it is not detected at all. No messages
> > show up in dmesg upon connection and no additional devices show up in
> > the output of lspci & lsusb. Strangely enough, USB devices connected to
> > the external hub do still receive power.
>
> I don't know much about Thunderbolt.  But since it appears as a PCI
> device, I would expect some sort of hotplug notification when you
> attach the hub.  If pciehp handles hotplug, it looks like we should
> see something from pcie_isr() in the dmesg log.

Try booting with: pcie_hp=nomsi

This is needed with the Light Ridge controller built into 2011/2012 Macs
to receive hotplug notifications.

Best regards,

Lukas

  reply	other threads:[~2016-03-16 13:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26  8:10 Jack Coulter
2016-03-15 17:29 ` Bjorn Helgaas
2016-03-16 13:22   ` Lukas Wunner [this message]
2016-03-22  8:06     ` Jack Coulter
2016-03-22  8:26   ` Jack Coulter
2016-03-15 18:03 ` Andreas Noever
2016-03-22  8:11   ` Jack Coulter

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=20160316132228.GB28222@wunner.de \
    --to=lukas@wunner.de \
    --cc=andreas.noever@gmail.com \
    --cc=helgaas@kernel.org \
    --cc=jscinoz@jscinoz.so \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=martin.andersson@purplescout.se \
    --cc=rafael@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

all inboxes | Powered by JetHome®