public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jack Coulter <jscinoz@jscinoz.so>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: 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>
Subject: Re: Thunderbolt 3 (Skylake / Alpine Ridge) hotplug
Date: Tue, 22 Mar 2016 19:26:42 +1100	[thread overview]
Message-ID: <56F101C2.7010904@jscinoz.so> (raw)
In-Reply-To: <20160315172909.GF19974@localhost>


[-- Attachment #1.1: Type: text/plain, Size: 1107 bytes --]

Hi Bjorn,

> Can you open a report at http://bugzilla.kernel.org, category
> drivers/PCI, and attach complete "lspci -vv" output (run as root) and
> complete dmesg logs, both when hub is attached at boot, and when
> booting without hub and attaching hub later?
>
> 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.
>
> Since you don't see that, I suspect we're getting ACPI notifications
> via the acpiphp driver.  I'm not as familiar with that, so I don't
> know what if anything it logs.  If you're inclined, you could add some
> printks in
>
>   acpiphp_add_context()
>   acpi_device_hotplug()
>   acpiphp_hotplug_notify()
>   hotplug_event()
>
> Then we'd at least see if we get any ACPI notifications.
>
> Bjorn

I've logged a report with the requested details; it can be found here:

https://bugzilla.kernel.org/show_bug.cgi?id=115121



Kind regards,
Jack



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2016-03-22  8:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26  8:10 Thunderbolt 3 (Skylake / Alpine Ridge) hotplug Jack Coulter
2016-03-15 17:29 ` Bjorn Helgaas
2016-03-16 13:22   ` Lukas Wunner
2016-03-22  8:06     ` Jack Coulter
2016-03-22  8:26   ` Jack Coulter [this message]
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=56F101C2.7010904@jscinoz.so \
    --to=jscinoz@jscinoz.so \
    --cc=andreas.noever@gmail.com \
    --cc=helgaas@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --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